phil_m
-
Posts
9,303 -
Joined
-
Last visited
-
Days Won
180
Everything posted by phil_m
-
There’s no need to do the intermediate updates. You can just update straight to 3.11.
-
I wouldn’t mess with CV for that application. It would be way easier and cleaner to use MIDI.
-
Yeah, this isn’t going to happen… Sorry, not trying to be negative. I just don’t even think this is feasible. If you think about how much more potential information it adds to each preset, it would just be a pretty big architectural change.
-
They do that for some things. When you assign a block to a CC, yes, 0-63 turns it off and 64-128 turns it on, for instance. But the CC messages associated with the footswitches are for the purpose of emulation. You assign that number to a footswitch, and it essentially creates a remote copy of the footswitch. There’s no on/off state associated with it because footswitches can control multiple things and those things just toggle back and forth each time you press the footswitch.
-
No, man, sorry. look at the way the other CCs that are set up as on/off for different values are documented. These are simply a trigger. There’s no on/off state. It’s just like hitting the footswitch. This is how all the Line 6 floor processors have worked going back to at least the X3L.
-
This is the expected behavior… They’re literally emulating the footswitches, which themselves are toggles.
-
If you have a delay block the Trails parameter on and switch to a snapshot where you have that block off, the tails will still continue even though that block is off. How long they continue depends on how you have the Feedback parameter set.
-
If you’re using the same delay and reverb blocks, what you’re talking about is the expected behavior. Like if you’re reducing the feedback parameter in the new snapshot, what’s happening to the repeats is controlled by the value in the new snapshot. The workaround, if you want to call it that, is to use use different delay and/or reverb blocks per snapshot.
-
You wouldn’t need an effects loop or send and return. You just need a single mono Send block to send the signal to your tuner. If you want to mute it while active, just turn the Dry Thru parameter all the way down. There’s no reason have the signal back from the tuner.
-
The vast majority of players are probably playing one guitar, really… Which is probably why it hasn’t come up more often. I have seen this issue mentioned a couple times since the Helix has been out, though. I mean, you can always bend down and turn the knob to switch the setting on the tuner for now. I understand it’s not ideal, though. Having the tuner settings saved per preset would be a nice option.
-
Yes. You can assign whatever MIDI CC you want to the expression pedal in the Command Center, and you can record that CC in Logic. You can send it back to the Stomp from Logic for re-amping. You have to assign that CC as the controller for the wah postion parameter on the Stomp then.
-
Open a support ticket.
-
Helix Native plugin window cropped in Ableton HELP!
phil_m replied to rackles's topic in Helix Native
Hmm... Can't say I've necessarily seen that. I've seen some people have scaling issues, but this is different. One thing is that you're running an old version of Native (there should be a Favorites tab on top along with the Presets and IR tabs). So I'd recommend installing the newest version as a first troubleshooting step. -
These forums aren’t support forums, so people shouldn’t assume that someone from Line 6 is seeing their posts. Opening a support ticket is the best way to get in touch with them. If you were doing the update via Bluetooth, your best bet is try to update again using Line 6 Updater on a PC or Mac.
-
This would require one device to be the USB host, and that wouldn’t be possible with just the USB B port. Beyond that, it probably wouldn’t work without significant latency anyway, even if it were feasible.
-
The Mix control is really a dry/wet balance control. At 50%, both the dry and wet levels are at 100. If you go beyond 50, you start decreasing the dry signal. You can try to compensate by increasing the Level control.
-
You can plug and unplug anything you want while the Helix is powered on. The one wrinkle would be the mic input when using a mic that requires phantom power. It’s best practice to plug the mic in first and then turn phantom power on.
-
This may be a dumb question, but are you using the included power adapter? The way your question is worded makes me think you might be thinking it’s powered over the USB connection. It isn’t… Again, sorry if it’s a dumb question. I’ve learned not to assume anything here, though.
-
Why are you using 2.92? The latest version of HX Edit is 3.11.
-
Hitting the Mode switch in Preset Mode takes you to Stomp Mode. To get back to Snapshot Mode, you have to hit the Up and Down switches together.
-
You’d want to use snapshots for this sort of thing. And now there’s the ability to assign snapshots to Stomp switches in the Command Center, so you can very easily do what you want.
-
Well, both of the Line 6 power supplies are rated at 3A. The Stomp probably draws closer 1000mA, at least in some circumstances. If you’re going with a third party wall wart, I’d try to get one that’s rated for at least 2A. It’s best to have some headroom with switching power supplies.
-
When you say you think the power supply was the issue, what led you to believe that? Is it or is it not working currently? The Line 6 DC-3H will also power the Stomp (that’s the one that ships with the POD Go and Stomp XL). Beyond that, there’s a bunch of third party power supplies that will work. You just have to make sure you have the correct specs.
-
Someone most likely installed new firmware and used the footswitch reset combination that erases all the presets instead of the one that does the factory reset. To do the factory reset, hold down footswitches C & D while powering up. That will give you all the factory presets.
-
The Bleat Chop Trem doesn't have a swing parameter, per se, but you might be able to find a tree pattern in it that works for what you want.
