bsd512

I do this with a few scripts I wrote. I backup my presets to a directory by exporting them all at once. And I have a "staging" directory for my IRs that I drag into the Helix. The IR order in the Helix is the same as the directory order. One script shows what IRs are used and by how many presets along with which IRs are not used. More verbose output options show which presets specifically use each IR. The input to this script is simply a file that lists the IRs in their slot number order, and the directory that holds all my presets. Since I have a staging directory for my IRs, that list is easy to make - it's simply the directory listing saved to a file. Another script I have is slightly more advanced. If I want to add a bunch of new IRs or remove some, I'll just make a new staging directory that reflects the new IR list. That script takes the old IR list, the new IR list, and the directory of presets. It then examines each preset and updates the IR slot number to reflect the new IR list order. Then it's an easy matter wipe my Helix (like is done with a firmware update), and simply drag all the IRs from the new list folder into the Helix along with the updated presets. Everything links up like it should and while IR slot numbers changed, all presets were updated to match, so it all works out the way it should. This not only makes firmware updates easy because everything is handy in folder to simply drag back into the Helix without worrying about IR slot numbers or having to rename IRs with slot prefix numbers. It also makes adding or removing a bunch of IRs easy as well, again without concern that IR slot numbers may change.

I predict it's the removal of the tuner. That pesky thing has caused more controversy than any other helix feature. :)

Dear Hollis1003 - if that's even your real name, Abby! My Helix has some serious attitude. It often smarts me off in front of my friends, and is very disrepectful to my wife - waking her up late at night with high volume levels, and insists I call it Felix. I hate the name Felix. It's out of control. I'm thinking about making it get a job. I took it's internet away and it nearly melted down. And it has some questionable friends that I think are a bad influence. What can I do?

I am more than impressed by your dedication and tenacity! :)

I also used the Peterson sweetened settings on my Schecter with great results. I now also have a new Les Paul which came with G-Force tuners. I love them and tuning takes about 15-20 seconds for very precise tuning (high accuracy mode and tuning each string individually vs all at once - still very quick). I need to read the G-force manual a little more closely, though, because I think it can get even better. I believe it gives one the ability to do a similar thing with sweetened offsets for each string, either directly or through "calibration" mode where you tune your guitar how you want it, and then G-force has a mode to learn that and reproduce that tuning. FWIW, when coming up for the offsets to apply in my Helix when I tried to do the same thing as the Peterson sweetened tuning with the Helix tuner, I did some googling and came up with these offsets, purportedly to be what Peterson uses for the guitar sweeteners, you can find them posted on TGP and other places if you google for "peterson sweetened tuning offsets": Sweetened Tuning Offsets: E1 = -2.3 cent B2 = 0 G3 = 0 D4 = -0.4 Cent A5 = -2.1 Cent E6 = -2.3 Cent

Ha! Thanks! I need to get out of the Helix room more, I didn't even realize Native had it's own topic area.

I keep expecting an actual informative and tangible Native update when this thread pops to the top of the list. :( You guys keep "making" me click this thread. Please stop. :)

Just some quick math based on the speed of sound in air, wired connection where most folks would say there is zero latency: standing 11 feet from your guitar amp and cabinet = 10ms delay standing 26 feet from your cabinet = 23 ms delay

That's a great idea. Is there an IdeaScale entry for this? I'd vote for it.

There are a number of ideascale submissions all for this same thing. Be sure and vote them up: https://line6.ideascale.com/a/idea-v2/830991 https://line6.ideascale.com/a/idea-v2/824324 https://line6.ideascale.com/a/idea-v2/809273 https://line6.ideascale.com/a/idea-v2/892101 If you count up all the votes, there's a lot!

IR selection UI optimization for Helix Editor https://line6.ideascale.com/a/idea-v2/900516 "While in the Helix Editor application, I believe selecting IRs could be improved by allowing one to double-click the IR slot in the "IMPULSES" pane to the left of the main editor workspace window. One would highlight the IR block to be affected, then when the IR is double-clicked in the IMPULSES pain, that IR's slot number would be selected for the highlighted IR block. This would be especially useful when auditioning IRs for a preset and would be much quicker than using the slot number slider, typing in the number, or using the hardware control knob on the Helix itself."

As others have suggested, for OwnHammer, head straight for the Quick-Start folder for each cab/speaker combination. There should be about 30 IRs in there that are representative of the several hundred otherwise. And half of those are the "M+" versions which are just a mid-boosted versions, so really about 15 IRs. Those represent the handful+ of single mics, and the handful+ of mixed mic combinations they use to create their IRs. And as most folks said, likely one of the mixes is all you'll need - the OH1 is very nice, same for MDRN for my tastes. And as Doug6 said, don't be afraid to mix a few of the single mics (or even the mixes - hey there are no rules!). The main point is, no need to be overwhelmed with the OwnHammer pack. By focusing on the Quick-Start folder, you'll get a great selection of read-to-use IRs that is not overwhelming. But if you are really particular and want something not there, you can delve into the separate folders for each mic and mix and your options go way up. I never felt the need to do that, though. On the subject of mixing IRs, I've been meaning to pull out a few of the "different" IRs that OwnHammer has, such as their FRED, and also ROOM, REAR, etc, and trying those mixed with others. Might be interesting, for example, a ROOM capture w/an OH1 or other mix might be cool. But I haven't tried it yet.

Yeah, she's not getting a $52,000 purse. The $1000 one was ordered, though. And yes, it does tend to enable my GAS - she never complains when I want something. As long as we budget for it - may have to wait a bit until the "mad money" fund has enough, but we have a sort've agreement - she gets something she wants, I get something I want - within reason. It's a good system - we've been married 27 years and it's worked out well so far. :)

That's only the tip of the iceberg, she was being frugal, lol. Some were $30,000. At least she's not into expensive shoes. EDIT: $52,000 http://us.louisvuitton.com/eng-us/products/capucines-mm-crocodile-brillant-012070#N92509 <shakes head in disbelief>

Your recent acquisitions are giving me serious GAS for one of the gorgeous PRS's. Incidentally, my wife has her beautiful brown eyes [just in case she happens to come across this post, lol] on a purse in the neighborhood of $1000. Don't ask me the appeal, because I do not understand, only that it's important to her. Probably same way she feels about my stuff. :) Anyway, I figure a purse for her = guitar for me. I'm just biding my time. :) Of course, in my case, perhaps the money is better spent on lessons.

Hey it was on sale, so you actually *saved* money by buying that. :) She's a beauty!

May be helpful: http://line6.com/support/topic/27704-4cm-4cm1-wdw/?do=findComment&comment=215000

Time. It sucks that away like nobody's business. I just noodled away 3 hours on the damn thing.

I think that early release information was a test. Based on the fact that thread went on for like 83 pages and endless "is it here yet, is it here yet, when is it going to be released, why didn't you include ...", I think we failed. Therefore, I bet that won't happen ever again. :)

I came across this video from Ritchie Castellano, Blue Oyster Cult's guitarist, on setting up 4CM, 4CM+1 (4CM w/2 amps), and wet-dry-wet setup with the Helix. I found it very informative and made me appreciate the power of the Helix even more. So I thought I'd share it here for folks who want to do this kind of setup. It's a long video, but well worth it. Interestingly I had just watched a different video comparing Helix vs Axe FX 8, and the reviewer's criteria on which one to choose pretty much came down to the number of amp models. But then when you see first hand the amazingly powerful routing capabilities of the Helix, there doesn't seem to be anything out there that can touch it when it comes to stuff like this. And how quickly you're able to do this with the easy to use UI is pretty impressive, too.

Absolutely gorgeous! Want.

So when someone says us Helix folks are "drinking the [Helix] Koolaid" - we can say, "Nah, we have vodka." :)

Here's the main way I'm using the SY-300. This happens to be a dual-amp patch, but that part doesn't matter. See the image: The very first send block is two sends, Send 1/2 - one sending to the SY-300 input, the other to my Mel9 input. My SY-300 dry-out is feeding a Trio+. Their outputs are not used in the guitar signal chain at all - they are not brought back in until Path 2b at the very bottom which has no Helix effect processing. The Trio comes in on the first block of Path 2b which is mono Return 1 (drums and bass). The Mel9 comes in on the second block on Path 2b which is mono Return 2. And the SY-300 L/R stereo out comes back in on the third block of Path 2b which is stereo Return 3/4 which converts the rest of the path to stereo for a nice full stereo sound that the SY-300 is capable of. I've found this to be a good setup for ambients and other synth patches that mix well with the guitar processing above it in Paths 1a, 1b, and 2a.

Nice!

I use Logic so I can't exactly for Reaper, but the concept is probably similar. With your dry track already recorded - set that track's output to be USB3/4. On your new blank track, the one you are about to record into, set it's input to USB1/2. And on the Helix hardware itself in the patch you want to re-amp into, set the Path input to USB3/4. Then just press "record" in your DAW - that should "play" your dry track into USB3/4 which feeds your Helix input Path, and the Helix output block will go out normally to USB1/2 and be recorded. That's the way it works in Logic anyway, and probably in Reaper, too - just the specifics of setting it up are probably slightly different.