phil_m

TGP is a bit like a huge Kevin Smith movie or something... Everything becomes a larger than life issue...

If you're using the 4 cable method, it means you're using one of the HXFX's effects loops, so, no true bypass won't work in that case. I mean, you could still get the unit to go into true bypass, but it would be passing the signal straight from the input to its output, thus bypassing your amp's preamp. Because the loops can be moved anywhere in the signal chain, they require AD/DA conversion. As far as the audio differences, those are hard to say. The HXFX is very transparent, and it offers flexibility as far signal levels for the inputs, outputs and loops that the M13 doesn't have.

These are always the type of things that make me think that if were a simple thing to do, it probably would have been that way since the beginning. I mean, I imagine there’s some technical reason for the limits they went with out of the gate.

Yes, it should be possible. You can split the effects loop up so it acts as two mono loops (or two independent sends/outputs and two independent returns/inputs). So what you could do is connect everything like you said, and in the Signal Path view put the IR block in Path B. Then you would set the output of Path B to be Send 2. Send 2 would be the feed you would send to the mixer.

There are only 4 snapshots in a preset, and this is simply a limit of the way the architecture of the unit is set up. You can recall snapshots with an external MIDI controller, but not with a simple N/C or N/O footswitch. Same thing with presets - the 4 preset per bank is "hardwired" into the system architecture, and, again, you can recall presets with a MIDI controller if you want to.

The Legacy effects aren't further subdivided into mono and stereo folders, but they maintain the same sort of mono/stereo operation as they did in the M-series. All distortions are mono, and all filters and reverbs are stereo. There are some mono in/stereo out mods and delays, etc. From the manual:

Hi there, But, yes, any of the Helix models will allow you to do that (the HXFX won't as it doesn't have a VDI input). You can change models and/or tuning on the JTV with preset changes and/or snapshot changes. PS - You may want to edit your post to hide your email address since this is a public forum that's open to the entire internet.

how did you know?

The short answer is that the sort of system architecture needed to create a more complex looper is different than what’s used for creating a multi-FX pedal like the Helix. Look at the Axe FX III that was recently announced. It has a ton of raw processing power, but its max loop time is 44 seconds, iirc.

You could import the track into a DAW and simply add some space before it starts, and then just render it down again. Other than that, there are BlueTooth footswitches out there that let control the play, stop, etc functions on your phone.

I would open a support ticket about the tempo drifting https://line6.com/support/tickets/ As far the re-starting the LFO thing, I imagine that will be coming. That was added in the Helix not long ago.

This thread title always reminds me of this: https://m.youtube.com/watch?v=opOUwDc1O-Q

It seems to me that one of the great advantages of using a multi-FX like the HXFX is having the ability to sync everything together with on tap. What you're describing is more like having several standalone pedals, each with their individual tap tempo control. It's kind of a different use case... I actually don't know of any multi-FX that would really behave in that way. I'm a little confused as to why if you were tapping in a new tempo for the modulation why that tempo would be out of time. Unless, I guess, you're just kind of tapping random intervals. One thing you may want to consider is assigning the modulation's rate parameter to an expression pedal. That way could adjust it without actually tapping. You could set it actual Hz values, or you could use note values and have the expression pedal sweep between the values.

Have you updated to the 2.50 firmware? MIDI clock is kind of has a lot of inherent drift, but I would be surprised it would be that noticeable. When you say it doesn't stay with the click, what exactly is losing sync? What are you using to send the MIDI clock signal? Have you tried other sources? I don't have an HXFX to test, but the MIDI clock on the Helix has been working quite well for me for a long time now.

Well, don't include me... I'm just an expert user/moderator here, a hanger-on if you will. I'm not a Line 6 employee.

Which of Line 6's competitors is announcing release dates for their firmware updates? None that I know of... Dude, we're not people buying enterprise class storage solutions. We're musicians. We should be more chill... No one else in this segment has released updates that rival the scope and scale of the updates that Line 6 has released in the last year and half or so. Fractal updates have been getting progressively smaller and smaller and more infrequent as they were working on the Axe FX III. Anyway, the update should be out next week. They found a few "blocker" bugs in their last rounds of testing today that pushed it out. Line 6 has been fairly transparent as far their deadlines. They said from the get-go regarding 2.50 they were aiming for NAMM. Not sure what the big deal other than that perhaps which such a large user base, it's hard to get the word out to everyone.

Some of the analog delays have maximum delay times that are shorter, so if you tap in a tempo that's longer than the max time, what happens is the delay time will be set to the next note value that works. Check out Ben Adrian's answer here: https://www.thegearpage.net/board/index.php?posts/20724188/ If you want a BBD-style delay with a longer delay time, check out the Adriatic Delay. That has a max delay time of 2000ms. As far as the BPM, you're basically correct - tapping in a tempo effects all the time-based effects with note values in that preset (or snapshot, as I'm about to describe). You might want to check the MIDI/Tempo settings in the Global Settings menu. You can have it so the tap tempo is global - it affects all the presets, per preset - it affects the preset and all snapshots in it, or per snapshot - it only affects the current snapshot. So if you could conceivable tap a tempo in one snapshot and then go to another to tap again, and have the delay time in the first snapshot remain unaffected. If you had the Snapshots Edit parameter set to "Recall", the tempo you tapped in the first snapshot would be saved when you left and be the same when you came back.

Yes... 4 per preset.

Well, I think it's definitely true that the majority of what you hear from a guitar is the initial attack, at least for the most popular styles. But I think the big is trying to hit the string with the same amount of force as you would when you're actually playing. I see some players pluck super lightly when tuning, and then they do that, they tend to be a little sharp when they're actually playing because they hit the strings much harder. If someone is super aggressive in their playing style, they might actually want to tune a little flat to compensate. A lot of interesting stuff in this article: http://www.endino.com/archive/tuningnightmares.html

I think this is the expected behavior. The custom names are tied to the footswitch/scribble strip, not the effects block. This is how it works on the other Helix products as well. You can have multiple effects assigned to a switch, so I imagine that's why it's the way it is.

Line 6 did update the tuner back when the 2.0 update was released... So you can't realistically accuse them of not listening to people. Prior to that update, people complained the tuner wasn't sensitive enough. Honestly, if you want something done about, posting rants here won't do anything. Vote on IdeaScale. That's the mechanism Line 6 uses to evaluate these things and to judge the churn around these items.

Not sure I understand what you mean by this... Could you elaborate a little?

It's the same as it in the other Helix stuff. The controller settings are all per preset.

Well, for one thing, there are some blocks, like the FX loops or noise gates, for example, that you might not want to turn on and off with a footswitch. You also have the ability to assign more than one effect to a footswitch. You have access to editing those effects by going to the Signal Flow view or Pedal Edit Mode. Basically, if you want to use the HXFX as a simple one effect per footswitch pedal, you can. In that case, it would be more like have six stomps in front of you. But, if you want to use as a more advanced multi-FX, and something more like a pedal switcher, you would want to look at using snapshots. That way instead of always turning individual pedals on and off, you are creating custom configurations of the blocks in your preset for each snapshot.

If you want to be able to turn more than just six blocks on and off with the footswitches, the solution to that is snapshots. Then you can arrange the bypass stages of every block in your chain and save that configuration in a snapshot. This requires you to step back from the one effect/one footswitch paradigm. In the end, it’s a lot more convenient. On my Helix, I have some presets where I never even assigned any effects to footswitches because I just do everything with snapshots.