-
Posts
9,303 -
Joined
-
Last visited
-
Days Won
180
Everything posted by phil_m
-
They don't sum the dry signal to mono. They maintain stereo separation of what's coming in. This is easy enough to prove to yourself. Just put a stereo effect in front, and you'll hear the stereo field correctly. What happens, though, is the wet signal isn't two discrete mono paths. It's a blended stereo path. That's to say that there's left and right processing being done on each side of the stereo field. So if you set the mix to 100, all you're hearing is the wet signal that's being generated by the effect block itself, and none of the original stereo dry signal. This is pretty typical of how stereo effects work in general. If you want discrete processing of the left and right signals, the proper way to do that would be to split them into two mono signals and apply mono effects on each. I think, though, for reverbs, it would sound a little weird to have the wet reverb effect isolated on each respective side of the stereo field.
-
Wait, you’re saying that having the mix at 100% defeats the stereo image? That’s probably expected. I thought you were saying you had the mix of the Ping Pong delay at 100%. The dry signal going into the effect is maintained, but the stereo signal from the wet portion of the effect isn’t completely separated. It’s not two completely independent mono effects.
-
It’s a known bug that will dealt with in an upcoming patch.
-
That means there isn't enough DSP left on that processor path. Each of the two main signal paths - Path 1 (1A and 1B) and Path 2 (2A & 2B) - have a dedicated processor. So if you're hitting the DSP limit with everything on Path 1, try moving some of your blocks down to Path 2.
-
You don't need to mess with a parallel path unless you want to do something specific with it. For the 4CM, you would just put all your block in a single serial chain. Any effects that you want before your amp's main input should be placed before the FX Loop block. Any effects you want after your amp's preamp, i.e., in its FX loop, need to be placed after the HX Effects' FX Loop block.
-
They're definitely maintaining stereo separation... Try putting something with a very obvious stereo split in front of the reverb like the Tremolo/Autopan block, and you hear right away that the stereo image is maintained. I hear it even pretty obviously with the Ping Pong delay. Double check that you're not using the mono version of the reverb.
-
There are mono and stereo versions of the 5 new HX reverbs. The reverbs which were previously available have been moved to the Legacy folder. They are, as they always were, all stereo.
-
Where do you have the Mix parameter set on the Auto-Volume Echo in the Helix? That is the one parameter that has definitely changed in behavior. On the DL4 and M-series, the mix control was scaled differently than the Helix.
-
The converters on the Helix are much better than the converters in the DL4 and Echo Pro, and everything is being run at a higher sample rate... So I don't think it's unexpected that they would sound and feel a little different.
-
Wah issue with HX and 2.50 - Wah turns off when I rock the pedal...
phil_m replied to highline-2004's topic in Helix
Sorry, I read your first post too fast. It just sounds like the bypass state of the block was reversed from what it should have been. You can press FS3 in Signal Flow View to change the bypass state of the selected block so that it lines up the way you want it. -
Wah issue with HX and 2.50 - Wah turns off when I rock the pedal...
phil_m replied to highline-2004's topic in Helix
When you insert a wah block, it's automatically configured to be controlled and bypassed by EXP1. The auto-engage feature was something that was carried over from the Helix. Check out pages 29 & 30 of the manual for a more detailed explanation. This is the most pertinent part: -
HX = Helix for all intents and purposes. The HX Effects was actually going to be called the Helix FX at one point, but it got changed for, uh, reasons... But HX is the designation Line 6 is using for stuff developed under the Helix platform. As far as the software, they all use the same editor, so that's kind of the point.
-
Navigation from a specific snapshot in one preset to another SS in another...
phil_m replied to RockManDan's topic in Helix
I can see how it might be useful, but I don't know if it would be of much use to me personally. I never change presets during a song, so it's not really a big deal to change a preset and select a different snapshot if I need to. -
The newest version is 2.51... It's showing up for me.
-
You have to insert the FX Loop block in your preset somewhere in order the send and return connections to work. It isn't like the M13, where the loop was kind of always active.
-
Hmm... Well, that's not normal. I've been using Windows 10 along with Line 6 Updater for the last few years now, and have never had a problem.
-
You can change the value of the CC Instant Command per snapshot, but not the actual CC#. So you could have something like: Snapshot 1: CC 21, Value 0 Snapshot 2: CC 21, Value 30 Snapshot 3: CC 21, Value 64 Snapshot 4: CC 21, Value 127 But, you can have up to 6 Instant Commands per snapshot, so if you need a different CC, you can set that up as a different CC#.
-
I think you are probably misunderstanding how the mix parameter on the Helix reverbs (and, well, every effect that has mix parameter in the Helix) works. It's really a balance knob that controls the relative level of the dry and wet signals. At 50, you have 100% dry and 100% wet. At 0, you have 100% dry and 0% wet. At 100, you have 0% dry and 100% wet. So once you move the mix knob past 50, the dry sound is going start decreasing in level. If you want to have a sound that's more wet than dry, you can compensate for the decreased dry signal by increasing the overall level of the block with the Level parameter. Or the other thing you can do is put the reverb block in a parallel path and try mixing the wet and dry that way. The BigSky mix knob works more like a traditional mix knob where the mix doesn't start get more wet than dry until the very end of the sweep. It also has an analog dry path, so the dry path is never really decreased in volume.
-
Well, let's say you wanted a tremolo effect. With the HX effects, you could choose to use the Mono or Stereo version of that effect depending on your signal path and what you wanted to do. You had the option of choosing whether it would be a mono or stereo block. The mono and stereo versions that effect are actually two separate models in the Helix. With the Legacy effects, there is only one model and the mono/stereo behavior simply follows what it was like in previous Line 6 devices.
-
The other thing I'd add is that with the HX Effects, there are mono and stereo versions of most of them. With the Legacy effects, there is only the one type, so whether you want to use it in mono or stereo, it doesn't really matter. You always only have the one block to use.
-
This is from the HX Effects manual:
-
It's been this way since the Helix was first released.
-
I remember this topic from before... I think that the saturated distortion is just causing the reverb to get washed out. If you listen to the raw signal coming out of the amp model, it has a lot of high end crap, and when you sent that through the reverb, it just becomes a washy mess. Putting the reverb after the cab and adjusting the high cut is probably a much better way to go about it.
-
I think the reason they didn’t classify them is that there are a bunch that don’t fit neatly into either category. There are many mods and delays that are mono in/stereo out (they don’t maintain true stereo separation) for example. All the drives are mono, and all the reverbs and filters are stereo.
-
Yeah, just handles... I think they just made them red in the new editor to make them easier to see when you have the paths split like this.