bsd512

Something like this would work perfect: https://www.amazon.com/Hosa-CMP-159-Stereo-Breakout-Cable/dp/B005HGM1D6/ref=sr_1_1?ie=UTF8&qid=1483387384&sr=8-1&keywords=1%2F4%22+to+3.5+stereo

That's what I'd do first. Remove the PC from the equation, it's not needed.

Yep. If Helix were a house, this one is like a little bit of touch-up paint on the inside of a closet. :)

Thanks for the suggestion, that actually looks very nice. But I was thinking more along the lines of adjustable height all the way from the floor (to operate with feet) to around 18-24" or so to for easy no-bend-over-editing while sitting on a chair. And being able to switch back and forth without tangling cables or removing headphones or guitar (strap).

I have the Helix floor model, but mostly use it on my desk for easy editing on the unit. I often wish it was on the floor to operate the button and pedal with my foot the it was designed to be used. So I was considering building a motorized platform that would raise it for editing, and then flick a switch and lower it to the floor for playing. That would be a relatively non-trivial undertaking. I still might do it, as one of my other "hobbies" is robotic control, electronics, firmware/motor control/etc. But the parts aren't that cheap. Then I came across this: https://www.amazon.com/Fancierstudio-Standing-Monitor-Height-Computer/dp/B01NCKIU70/ref=pd_sbs_229_4?_encoding=UTF8&psc=1&refRID=7YJSP8NW0VKE3F3TD6A4 Anyone ever used one of these for your Helix floor model to raise and lower it for editing and playing? Just wondering if it would be sturdy enough. The 17-18 inches it raises would probably be fine. I wonder if it would go all the way to the floor or would be sturdy enough to handle being repeatedly stepped on through the foot switches and volume/wah pedal.

I'll add my voice for trails on as the default. Definitely seems more intuitive to me considering delay and reverb are intended to emulate spaces, and real spaces don't squelch sound abruptly. I always turn trails on, unless I forget - sometimes those are on page two (or three) of an effect and I forget to set them to on.

Sounds like a perfect and very simple use case for snapshots. Snapshot 1 = 3 tone shaping pedals on, overdrive off. Snapshot 2 = 3 tone shaping pedals off, overdrive on. It's very simple to do on the Helix. Press Snapshot 1 button for clean tone, snapshot 2 button for overdrive. I think this would operate exactly like you are wanting.

That was great!

Very nice and great video, thanks!!

Sounded great! That new fuzz pedal you're testing sounded really good, too.

The setlist file contains all the presets, but the presets are compressed within the setlist file, so the setlist file will be smaller than all of the individual presets.

Again, these are very very nice. My favorite is in this group is the SM57 Off-Axis. It's actually very close to Fremen's HG (high gain) IRs - he has a 1-10 numbering for different eq's, but I found it very close to his LX TDR HG3 or thereabouts. Very nice job. Thank you! Merry IR Christmas. :)

You might have looked already, but the preset files are human readable json format. I've done what you suggest above. Some languages, like Python, make it very easy to load a helix preset and programmatically examine and update them, then write them back out. That's how I keep my IR order in sync with my preset slots - with a program I wrote that operates on an entire directory of presets, resetting the IR indexes within all the patches at once to match updates to my IR list loaded in the Helix. And also tells me which IRs I have loaded that are unused, as well as for each IR, which preset uses it, the most-used IRs, etc. It's not too hard if you are willing to experiment a little, and most of the fields are self-explanatory. The preset files are practically self-documenting. I know I'm at the mercy of the next update - the format might change and I'll need to update my program to match. No worries. But once Line 6 documents and publishes it, they'll be locked into the format and it could hinder their ability to redo it. For example, like with the introduction of snapshots, which necessitated updated data structures and fields. Either that, or they then have to document the changes between preset file format versions, and so one. More work for Line 6. As a programmer myself, I find it easy enough just to dig in and see what's there, essentially reverse engineer it. And as far as a reverse engineering effort goes, the helix file format has to be one of the easiest. I don't think they're trying to hide anything. The preset files and formats are practically self-documenting. Anyway, that's what I did to write the utilities I mentioned above for my own use.

That is cool!

Actually, dropping in a parametric eq with a narrow q and sweeping, the problem frequency to my ears appears around 2.6kHz. Resetting the q to .7 and dropping the gain there to about -3.0dB seems to take care of most of it. I also noticed, as compared to the OH IRs I have, the OH's appear to have a lot more low end/body. Not trying to be critical at all, please don't take it that way. Just comparing to what I'm used to in the OH IRs and provide some feedback. All in all, I like it. Nice job! EDIT: Actually, in fact, maybe I'm easy, but with the eq above, this is quickly becoming one of my favorites. :)

Thanks, Roscoe5. I really like the sound of this IR, but compared to the OwnHammer Mesa IR I have (and other cabinets) it is very trebly - just dropping it into the same patch with no other changes. Otherwise, sounds great. I'm using the ANGL Meteor @ default settings if that matters, and IR lo/hi cuts at 72 and 6kHz. Still very trebly, though, almost piercing to my ears. Not sure if that was the intent or not. I would definitely use this IR, I like it that much. But for me, at least, I'll need to tame the very highs with something more aggressive than an IR hi-cut.

The only thing would be is if you backed up your Helix presets and setlist with a "bundle" and then restored with that bundle. I believe that will also backup and restore the pre-update factory presets, and restore those too. Thus, you still have the old factory presets if this is the method you used to backup and restore. Alternatively, if you backed up your presets as individual presets, or your setlists individually, and restored those, that won't touch your factory presets (unless you explicitly backed those up and restored separately), in which case, you should be all set. If you did the former (bundle), and want to make sure you have any updates to the factory presets that came with the new update, I'd do the following: No need to re-do the firmware update - you've already done that. Backup your presets in individual preset format or as setlists. Backup any IRs. Turn off Helix Reboot Helix holding FS9 and FS10 (clears setlists, IRs, and resets globals). Restore your presets from their individual files or setlists. Restore any IRs. Reboot once more to rebuild presets. You should now have the latest factory presets in the factory setlist locations.

I don't know - sounds pretty useful to me. I can think of a lot of times when I'm away but have my laptop and a little time. It'd be great to be able to pull up the editor, create a patch, and save it to load into the Helix later. The suspense for what it sounded like would be killing me. :) I'm betting the reason though, is that the editor just serves as a front end to the Helix hardware through an API and it'd be a major undertaking to make it completely stand-alone.

I wrote a separate program to do it. I have a directory where all my IRs go that I load into the Helix - alphabetical order and load them in that way in bulk. When I add or remove IRs from that directory, I export the directory listing where the order is their slot numbers and save in a file. I then export my presets. Then I add/remove IRs from the IR staging directory and export the new list. Given the old list and order and the new list and order, I wrote a program that opens each of my previously saved presets and automatically updates the IR slot number in the preset JSON file and saves those out back out. Then I re-import the new IR list along with the updated presets. Everything stays in sync and I don't have to change a bunch of presets when my IR order changes within the Helix. Works great. But still looking forward to a bonafide L6 solution. And more IR space. :)

I know you did a global reset, but just to be sure, go into the global settings and make sure that the Volume knob preferences aren't set to something like "digital" in which case it would send full power out the 1/4". It should be set to "multi" I think in order to control both the line 6 link volume as well as the 1/4 and xlr outputs. When set to a specific output (digital, xlr, 1/4) the volumes on the others go to full.

Hi - I apologize if this is not the right place to ask this question, it doesn't seem quite like the right place, but seemed the best of the forum sections here. I currently use Logic Pro X and just do basic recording. I use the built-in drummer in Logic Pro X which is fine. It is tweakable and adjustable to a reasonable degree, but doesn't really give much control if you want to build your own drum track - you pick a drummer style, a drum kit, and it then generally has a handful or two of "beats" that you can choose. And then you can adjust the number of fills, complexity, and "complexity" of the beat. I think I'm out-growing it and looking for a replacement that is relatively easy to use - I don't want to necessary build every drum-line by hand. Having a tool with a number of pre-canned rhythms available would be great. And if I find one that best fits my song, but find that it needs some more adjustment that I'm able to do in Logic built-in, that'd be what I would be looking for. I don't really need to adjust each snare hit/decay/etc. But I'd need more variety than I can get from Logic's built-in with more ability to customize. Yet still pretty easy to use. I've googled around and there seem to be quite a few products. All of them say they are greatest, easiest to use, best sounding, best interface, fully everything. I don't have a lot of experience in this area, so I'd love to get a few first-hand recommendations from folks that actually use the products and are happy with. And I'm assuming I'll be able to use this in conjunction with Logic to create a drum track, similar to the built-in Logic Drummer. Thoughts? Recommendations? Any help or pushing me in the right direction would be much appreciated! Thanks!!!

Outstanding!

Totally agree!

Maybe straying a bit off-topic but what the heck ... In the meantime until Line 6 comes up with a better approach to IR management, I've gone a different route - I don't necessarily recommend it for everyone, but it works for me and because I can. :) I wrote a program to automatically update my presets to reflect changes to my onboard Helix IR list. I have a "staging" directory where I drag the IRs I want loaded into the Helix. Then I just drag the whole list at once into the Helix in file system order, which the Helix preserves on import. At any given time, all my presets reference their respective IRs appropriately. The Helix presets are exported as 'json' files and the IR blocks are identifiable within them as are their slot numbers/indexes. So I when I add any new IRs I just save the current IR list of files in the staging directory and make a new staging directory where the old+new IR's go in whatever filesystem order they happen to be. Now I've got two lists - the old IR order and the new IR order + any new IRs. Then on the Helix, I clear out the old IRs, and load in all the new ones which may be an entirely different order than before, i.e., lots of slot numbers may have changed. I then export the presets to some other directory. Then with my program I wrote, that loads in all of my exported presets, and the two IR lists (old order and new order). Then for each preset, I load in the Helix preset (json format), update the indexes for each IR within the presets appropriately knowing that the presets originally reference the old order and I then map it appropriately to its new slot location based on the new IR order, and save them back out. Then I re-import the presets. So it's just a few mouse clicks to export. Run the program to remap the preset file IR indexes. And load the new IR set. Works like a charm. Things get only slightly more complicated for IRs that controlled through snapshots, but I've got that handled also. No numbering to worry about, etc. Just need to make sure and save the order of the presets in the Helix before and after adding new ones. The best way to do that for me is to use a staging directory where I drag them first, and then into the Helix. Of course, it's subject to breaking if L6 changes the preset file format or structure, but it works great otherwise. And I don't have to worry about renaming IRs with prefixes. Sounds complicated to describe, but it's simple and easy in practice.

Thanks! I'll give that a try.