bsd512

It was probably was posted over on TGP, they'll get around to us over here eventually :-)

Not sure about page numbers but the round dot (or star if you've posted in the thread) to the left of the topic subject text will take you to the first unread post in the thread.

Do you mean all parameters for all blocks, as well as inputs/outputs also in the patch? Or just one block? If the latter, it's pretty quick to use the shortcut alt+left-click in HXEdit to enable snapshots to control the parameter. Takes a few seconds to click through even the more complicated blocks like an amp, so it's pretty quick. I could see that getting old if you want to enable it on all blocks as well as input/output levels, etc - essentially everything that can be controlled by a snapshot. That would be a lot.

Entropy is a lollipop.

Handles? Let's address the elephant in the room that no one wants to talk about. What it really needs is wheels. :)

Lol. Maybe someone can repost L6's response from over there here so we can find it. :)

He might even suggest you fellas bottle that up. :)

Thanks for passing that along. I hadn't updated yet, but good to know. I kinda wish the Line 6 folks paid as much attention to those of us here on their own forum than over on other forums. A lot of folks don't have time to sort through all the chaff across multiple forums. If not for nice folks like you reposting that kind of thing from TGP and elsewhere, we'd never hear about it.

Good IdeaScale, soundog. Upvoted.

Just guessing here - maybe someone else can answer more definitely. Even if it appears that pathing might not work, it still might be possible. I don't use Cubase, but I'm pretty sure in Logic you can add multiple Helix Native instances to a single track - one following the other. So the output of one would feed the input of the other. If you can do that in Cubase, you could do that and put a MixIR instance in between them. Then set up your path 1 on the first Native instance, and you path 2 on the second Native instance. Maybe?

<sarcasm> This tone is the result of a poorly mic'd cabinet with multiple mics and that's where the phasing is coming from - but it just happened to sound good so they left it. So you're right, it likely can never be reproduced accurately since 1) it was unintentional, and 2) mic positions were never documented so no one will ever come up with that exact poor, but unique, mic'ing job again.

I think you'll need to round to nearest for the Helix since it doesn't go down to 1/10th of a cent. So effectively, -2, 0, 0, 0, -2, -2 from E1-E6 respectively. I play my Les Paul so much these days with it's g-force tuners I feel totally spoiled, though, and rarely use the Helix tuner. Just press a button, pick the strings, and watch the guitar tune itself very accurately. :)

Dang - looks like effects only. I want that form factor but with amp sims + IRs, along with effects. Basically a minimal Helix, cut all the FX loops except for maybe one, drop the expression pedal, midi, xlr, and all that. Maybe even the big screen (simple text LCD would suffice). Include about four footswitches, USB, one guitar input (no aux) and enough internal DSP to run patches from the full sized version. With similar limitations as Native regarding the missing send/returns and similar. My use case: it's in my living room by the fireplace next to my easy chair so when I get inspired, I grab my nearby guitar and have all the patches and tones from my big Helix that's 3 floors up in my house - out of reach. I happen to use an Amplifi TT for that purpose right now - and it works fine for that. But I'd much rather have a tiny Helix.

Very cool, thank you!

Thanks! I was hoping I was missing something and that capability was already there, but I can't find it. And I think the manual specially says Native can't import a Helix backup file. Hopefully there's an implied "yet" in there. It seems like the natural progression, so it may already in their plans for the near future. I hope so! Thanks for voting!

Unless I'm missing something, Helix Native can't restore from a hardware Helix backup file (new backup feature in HX Edit 2.30 and above). It would be great to have this feature, as well as the ability to create an HX Edit compatible backup file from Helix Native. This would make it a lot easier to keep the hardware Helix in sync with the Native plug-in, especially if you use your DAW on a desktop as well as a laptop - keeping them all in sync gets harder. But having a single file to backup from one and restore to the other would make it a lot easier because there would just be one thing to backup and restore, and it would also keep the set-list order and IR list order intact. Sharing across devices would be a lot easier. I searched Ideascale and didn't find anything relevant, so I made this Ideascale request: https://line6.ideascale.com/a/idea-v2/918622 Please vote it up if this would be of interest to you.

Unless I'm missing something, Helix Native can't restore from a hardware Helix backup file (new backup feature in HX Edit 2.30 and above). It would be great to have this feature, as well as the ability to create an HX Edit compatible backup file from Helix Native. This would make it a lot easier to keep the hardware Helix in sync with the Native plug-in, especially if you use your DAW on a desktop as well as a laptop - keeping them all in sync gets harder. But having a single file to backup from one and restore to the other would make it a lot easier because there would just be one thing to backup and restore, and it would also keep the set-list order and IR list order intact. Sharing across devices would be a lot easier. I searched Ideascale and didn't find anything relevant, so I made this Ideascale request: https://line6.ideascale.com/a/idea-v2/918622 Please vote it up if this would be of interest to you.

Yeah, that was hidden gem, I discovered it by accident. I guess it does help to read the manual sometimes, assuming it's in there - I haven't checked. :)

Are you sure? I tried several times and it didn't work. Just to be clear, I mean drag from the IR list on the left, on top of the IR slot slider for a IR block that is highlighted in the signal routing pane. In the old editor, that would change the selected block's slot number to match the slot number of the one you drug over the IR slot parameter slider.

I think he may have been referring to the ability to drag an IR from the IR list on top of the IR slot number field in the editor to change the slot. That no longer works. But yes, dragging IRs from the computer file system into the IR list works as one would expect.

Cartographer! Thank you, Line 6!

No comment on AXE FX about tweaking more, I don't have one, so I couldn't say. I don't think that fewer updates leads to the conclusion that Line 6 cares less. The (short) dry spell in updates is due to a lot of refactoring and rewriting code so that it is more maintainable and easier to incorporate new features farther into the future, extending the product's life-time with the promise of new features faster. I'd conclude that says they care quite a bit.

ENGL Fireball Archon Lead Soldano Lead Bogner Uber Matchless L6 2204 Brit Plexi Brit 2204 + appropriate IRs of course. :)

1) Yes, just the natural name order. It would actually be a little easier if the Mac didn't sort directory listings kind of weirdly. If it didn't do that, I wouldn't require the directory listing of the IR directory to be in a file, I could just scan the actual IR staging directory and sort it. But if you sort the directory listing using a standard alpha-numeric sort, that's NOT the same order that a Mac will present the files in the Finder window. Even so, even it that wasn't an issue, it would only save about 10 seconds in making the input files. 2) It regens the json file from scratch, so I load it in using json parsing to create the data structure as represented in Python dictionaries - really no work on my part there, the json.load(file) method which does all the heavy lifting. Then I follow the data structure just enough to find the IR blocks, and specifically what slot number is assigned. 3) I'm looking for IR blocks and and also those assigned with snapshots. I'm not looking for footswitches, though, since I'm not using them for that, but I do use snapshots and that changes things a bit. I'd have to experiment and do a footswitch assignment to see how that changes the json and update my search method accordingly. I've had this scripting since before the snapshot capability was available in the firmware, and I remember having to update my script to account for that. 4) Written in Python. The actual loading, updating, and writing back out the presets is very easy in a language like Python, it doesn't take much code at all, a handful or two of lines of code does all that. And while the code for finding the IR blocks in their various forms is not a lot, either, that's the key - basically just decoding the data structure L6 uses to store them. Anyone can get a feel for what that's like just by looking at the json structure they use. It's not hard, but any changes Line 6 does to the preset format in the future and I'll need to adapt. Like when snapshots were introduced. Hopefully in the future they retain the json (or other easily readable and parseable format) for the presets. If they were proprietary binary something or other what I did would not have been practical for me. Thanks! Unfortunately, my method is a couple of command-line scripts that use a couple of data files and the preset directory for input, and another preset directory to write out the updated presets (I use a subdir of the actual preset directory for that - I don't replace them in place just in case something goes wrong I don't destroy the originals). So it's not the most user-friendly - definitely not a nice GUI or anything that would be generally sharable. Sounds what you're working on might be, though - if so, keep going! These scripts have saved me a ton of time over the past two years, so having something like this be user friendly and available for a broad group of folks would likely be very welcome. Mine works great for me, but it's not polished or easy enough to use to be generally sharable, I suspect.

It handles it fine - I've been down that path and automatically update presets to match when my IR slot numbers change. I responded in your other thread with a little more detail. I happen to be using Python and simply use the json module, specifically json.dumps(data, indent=4). Helix loads them fine so you should be good.