duncann

The following is probably not easier and a lot of unknowns abound, but would be less tedious. Patches are text files, so take an unmodified patch and a modified one, and compare the differences to help you figure out what needs to be changed. Once you know that, it would be a fairly simple operation of opening all patches at once in a text editor (something like ultraedit or similar with advanced search and replace capabilities), and batch process what needs to be changed. It's an idea that could hold some risk, maybe even bricking Helix, so beware.

I preferred the soldano lead tone over the shiva. Not exactly sure why, but I get the impression that the soldano fits in better with the rest of the mix. A slight volume boost is about all it needs. The shiva tone sounded a bit harsh and too striking. Could be because it's louder, perhaps a little too loud. The only other thing that stuck out to me is during the choruses, when the rhythm guitar kicks in, it's a bit indistinct and vague, getting buried in the other parts a bit, but maybe that's what you were going for. Overall, it sounds really good to me. Nothing that screams major error. :) Just a few tweaks here and there. Nice song and playing as well. The mesa mark iv amp is my absolute favorite. I don't think I'll use anything else ever again for lead tones. It doesn't even need anything helping it along, just the amp. In fact, I'd say putting an overdrive or distortion in front kills the character of the amp a bit, but that's me.

Really? The links Jakerlund provided and the video you posted sound remarkably different to me. Although they are of the same flavor. The tone in Jakerlund's links do not at all sound like a phaser to me (much more wahish), but I suppose it could have one mixed in along with a wah. It also sounds like most of the modulation is triggered by a note, rather than oscillation (which is what phasers usually do?). Plus there's the octave thing going on.

Well, that's unexpected. I feel deceived. Lol. It's a really cool tone though.

If editing a helix preset in a text editor - even if one were to write a novel in the preset - introduces the possibility of bricking Helix, I'd say Helix has a very serious problem that needs fixing.

Glad to help.

In the edit software, go to the controllers tab, select the model, then FS assign. Do this for both delay blocks. On the device, select the block you want assign to a footswitch, hold the enter key, and use encoder 1 to select the footswitch. Hit view to exit FS assign mode.

I'm a little confused about what you want to achieve. Do you want to assign two delay blicks to the same switch so that when you hit the switch they both turn off? If so, that can be done easily. Just assign both delays to the same switch. If you want to the function of the switch to alternate between 1/4 and dotted 8th, there would be two ways. Assign both delays (one 1/4 and the other dotted 8th) to the same switch, disable one of them, then save the patch. The state of the LED is determined by which delay appears first in the chain. Another way would be to figure out the exact millisecond values you need for the 1/4 and dotted 8th. Turn off the tempo sync, and assign the time parameter to one of the expression controllers. The expression pedal would then effectively go between 1/4 and dotted 8th, heel down and toe down, or vice-versa. The only problem with this is when you set the min and max values, they are displayed in percentages, which means precision could be an issue. Each percentage correlates to 19.8ms.

I would start with an auto-wah (tron up) in combination with a pitch glide (controlled by an expression pedal). Settings for the tron up might include band pass for type, low range, high Q - 90+%, low frequency - <20%, high mix. The really tricky part I hear about this is the really saturated tone. For that you'd probably want to experiment with some of the mid to higher gain amps with a distortion block (try all of them) in front of it. The high Q and mix from the tron up certainly will help with the perceivance of being highly saturated. The pitch glide sounds like an octave is being quickly mixed in - 0 to 80% maybe - via expression pedal. Another thought is in addition to the tron up, use one of the wahs, but don't assign it to an expression controller. Adjust the position and mix until you start to hear the correct wah-like frequency, if the tron up isn't able to do it by itself. Or, alternatively, instead of a tron-up+wah, try a tron-up+Q filter.

If you're using it to just detune, remove the default assignment, which is the position parameter to EXP1, and set it manually. I believe there is a bug associated with this controller and I also read that they have found the problem and will be releasing a fix soon.

I never opened a support ticket for this because I guess I don't care enough about it as I only use this output for monitoring. Currently I have: 6" 75ohm coaxial (I think from monoprice) to one of these, then an optical cable (I think one from Amazon) that goes to a Soundblaster X-FI Titanium (the one with the front panel thingamabob) with an optical input, which is connected to my headphones/speakers. Certainly far from a good system, but it works well enough for monitoring. I can sometimes induce an audio drop out, the kind that requires me to unplug and replug the coaxial cable from Helix, by turning on a florescent light, or sometimes by just touching Helix, such as placing my foot (wearing sneakers) on the expression pedal. Before I had Helix, I used this same setup on a POD HD500 and HD500X with none of the 2-3 second audio dropouts, ever. I did, however, still occasionally get the unplug/replug variety, but only when turning on the florescent light.

In my case, I sometimes (rarely) lose all audio from Helix's spdif output. No idea if it's caused by a sync loss or something external to Helix that might be triggering a sync loss, but as you mention here, the act of unplugging and replugging the cable on the spdif output fixes it.

Thanks. I'll have to check that out. I use a slightly modified Default Commala 5, the non-light version.

As an alternative to this (using a MIDI item on a track) in Reaper, particularly for automating parameters or Helix's expression controllers, you can use the built in plugin, ReaControlMIDI. Use the bottom portion of the plugin (control change) and make sure raw mode is checked. Now you can use the envelopes/automation feature for the track that the plugin resides on.

I suspect that when they release Helix Native, there might be some facility to backup global settings. I vaguely recall DI mentioning something along these lines somewhere in the aether. I could be wrong though, and it might not even be tied to the release of Helix Native, but it makes sense that it could be.

He must have been using 1024. If I remember, Helix doesn't even allow the placing of two 2048 IRs on one path, even with nothing else on the path. So if he used a 2048 IR, he could only have placed one IR. From the video, it looks like a Helix cab is equal to a 1024 length IR.

Can't help for the emulator, but there's gotta be one that works on Windows 10? But for the second, you should really get an ssd. Even a cheap one. And seeing as you have 24GB of memory, you could set up a ramdisk (softperfect) in combination with backup/mirroring software (syncback), directory junctions, and simple batch files, so that when you record it would be to memory to relieve wear on the ssd. The only downside is if your system crashes, you're at risk of losing data for that session. I've been using this setup for a long time on Windows 10 (and Windows 7 before that) and never had anything crash on me yet.

Just to add to phil, I control snapshots using Reaper all the time and have never had any problems like described here.

User adjustable curves for the expression controllers would be a great addition to Helix. For studio use, you could in effect do this in a DAW by sending out some midi to Helix. In Reaper, ReaControlMIDI works great for this. It allows you draw envelops to control a parameter on Helix.

Have the wah selected, then menu, bypass assign, change EXP Toe (the default) to an expression controller, and the wait parameter appears, adjustable from 0 to 1 second. You can also assign the position percentage for when the auto engage starts to occur.

I tried this new function a while a back, and just tried it again now. I kind of agree that it's a bit fidgety, and would take some practice to get used to. You can increase the wait value to something longer and it works ok. The wait value works for both on and off for me here. Not sure why it doesn't for you. I wonder if they could further refine this function by slowly applying the mix of the wah, from zero to whatever the user set it at, for the duration of the wait value. Likewise for deactivation. A quick fade in and fade out, rather than a jolt.

Lol. http://money.cnn.com/2016/11/15/news/companies/nike-hyperadapt-self-lacing/

I've noticed that too. Twelve percent is the absolute minimum I'll ever use because anything below that is basically inaudible. I wonder if it has something to do with the fact that wet signal only goes from 0 to 50. Beyond 50, the wet signal stays the same and the dry signal starts vanishing.

It wasn't my intention to deride your priorities for Helix in any way, or to chide the Kemper Profiler. I've got nothing against any of Helix's competition. In a maybe not so eloquent way, I was more or less trying to get a more specific definition of what variety means in this context, and you've done that. Apologies. It's all good. Kemper's approach to delays sounds interesting, and flexible, more so than how Helix does it, which seems more of a brute force approach. I just think Line 6's time is better spent on other areas for the time being, and was pointing out that there is more delay variety in Helix than a first glance would lead one to believe.

Yep. Same here. And for your idea.