duncann

I've been waiting for some of those same filters. Still hoping, especially now, since Line 6 will be releasing an effects only HX product, if the teasers floating around are true. Assuming this new product has the same effects as Helix currently has, and all Helix products (rack/floor/lt/native/hxfx) share the same functionality, minus each device's obvious design constraints, then it will be an effect unit with a very limited filter selection. What effect only unit is complete with limited filters? This makes me think they might start paying attention to this aspect in at least the near future, if not sooner.

Yes. But make sure to follow the instructions precisely: http://line6.com/support/topic/18284-latest-helix-firmware-230—nov-21-2017/ In particular the section that says 'Updating Helix Floor/Rack/LT Running 2.12.2 or LOWER'. On the other hand, you could wait for just a little bit, as there is a new firmware coming, 2.5, very soon, or so I've read.

For people using the auto engage, be aware that there currently (2.30.0) seems to be a bug with it: http://line6.com/support/topic/30135-wah-auto-engage-glitch/?hl=auto+engage

.

Pfft! The delays in Helix are OLD! We need new ones!

I've not tried a metal zone into Helix, or a guitar into an SV Beast, but I've tried a guitar into a Plexi Jump (Helix model that is) into an 8x10 SV Beast. It was a tone unique enough, and one that I liked enough to use it as the lead part in one of my songs. So for me, the cabinet portion of your suggestion above is usable. Not sure where I originally got the idea from about the 8x10, but I think it was from Aris Laf, a forum member here, quite some time ago. It might even have been pre-Helix. The model-pack era of the HD. lol.

On the amps tab, for a non-preamp only amp (or full amp), they are located right below the tone stack parameters.

Not sure about the POD XT specifically, but if you meant an HD device, then yes, you could adjust those parameters via HD Edit.

What happens if the concept of future no longer exists?

In the past when I tried to set tempo, it was always via Reaper - so there was no human inefficiencies involved - and there were commonly occurring instances when the resulting value was off. Usually not a lot, but enough to bother those with a degree of ocd, or if timing is very important. Sometimes the result was something absurdly off. This was a while ago and probably with a firmware version that was pre-2.0. As an alternative to using the tap-tempo switch, you could change the global variable 'Tempo Select' to per snapshot or per preset (if preset switching isn't an issue for you) and set the bpm accordingly that way.

There should be three, using some combination of an sm57, atm250de, md421, and u47.

I use this specific IR for a bunch of stuff. Decent sounding IR, a bit bass heavy though. Should be on this page: http://www.rosendigitalaudio.com/412cabs/

I can recall encountering a bug where one side of the mixer, the right channel, occasionally went silent for some reason, and the solution was to just move the volume slider, if using HD Edit.

I'm fairly certain the cable that comes with the HD has a ferrite choke on there already.

Try moving the first block on path 2A to the last block on path 1A, if the available DSP allows. Then you'll have a free block space on path 2A. If there's not enough DSP, try to see if you can lower the DSP usage somehow on path 1A/1B by either eliminating one block or selecting lower DSP effects for some others, or perhaps eliminating one block from path 2A.

I've noticed this as well, because I sometimes accidentally assign a parameter to a snapshot.

I think you're on the right track by lower the amp's gain. But instead of adding overdrive or distortion before the amp, try using two panama amps, which each amp having a gain of around 25. Two amps (same or different settings) also have the added benefit of using two cabs and two mics, which significantly increases the tones available for selection. If I remember correctly, in addition to being fizzy, this amp is also quite a bit louder than most others, so you'll probably have to decrease the channel volume a bit. Of course, this two amp suggestion is only if you can spare the DSP.

If I do use one, it's probably the valve driver for me also. Sometimes all it takes is a gain block to push the amp a little harder.

Here's a post from Ben Adrian: https://www.thegearpage.net/board/index.php?threads/line6-helix.1586637/page-2031#post-24493309

Supposedly, the problem on Helix can be compensated for (or outright fixed?) in firmware. Hope that's the case, but it seems dubious to me, since this problem has existed for a number of people since day one. That's more than two years. You may be right about the next gen Helix. But I think that's quite a ways away, years and years and years. Helix is doing too well for them to make a new flagship device. I wouldn't be surprised if they add more to the Helix product line though, in addition to significantly improving the current offerings, which they have been doing all along. S/PDIF Exception. :lol: I agree it's a shame. Part of the appeal of digital is to simplify things. Guess it doesn't always work that way.

I've never had problems with spdif on the HD. Different story on Helix though.

It's not guaranteed, but the chance of sync problems increases. I remember using the editor and the expression pedal simultaneously all the time and very rarely, if ever, encountered any sync problems. So it's not necessarily a positive or negative result.

I remember reading from Frank Ritchotte, that the problem with this is not actually the joystick, but the solder joints.

Just tried with your settings and the onboard pedal. I did notice that if you operate the pedal quickly, going through its range multiple times, starting from the toe position, it takes anywhere from 3 or 4 seconds (with an operating frequency of about 1s per full range and back) before the wah block disengages. What's even weirder is you can be about halfway through the test, stopping at the toe position, come back later and continue the test as if you hadn't stopped at all. So from toe to toe twice (about 2 seconds), stopping at the toe position for however long, then after 1.5 or 2.5 more counts you can see the wah block disable immediately upon hitting the heel postion. This definitely seems like a bug.