-
Posts
9,303 -
Joined
-
Last visited
-
Days Won
180
Everything posted by phil_m
-
I think there is a bug in the editor in vintage digital delay
phil_m replied to Paolo_Maina's topic in Helix
The bug is in the editor. The Mix parameter isn't showing up in the editor when you select the mono version of the Vintage Delay model. It actually exists on the Helix itself. And, yes, the mix parameter controls the wet/dry mix. -
Well, you both are saying different things... Robbieb61 is saying that the EXP1/EXP2 toggle gets messed up even when he switches after turning the volume pedal back on, and smythejmd is saying it only happens if you switch snapshots before disengaging (which is what I would expect). FWIW, I tried re-creating this last night, and I couldn't get the EXP1/EXP2 to do anything unexpected in regards to changing snapshots. As long as I toggled back to EXP1 before changing snapshots, everything worked as expected. If I didn't, it would get messed up. I guess all I can say is double-check the bypass states in all you snapshots. If you have the Snapshots Edits parameter under Global Settings > Preferences set to "Recall", any changes made in a snapshot are saved automatically, so it can be quite easy to accidentally change the state of a block.
-
If you can see the parameter changing but the wah block is off, it means you have the wrong controller selected. Engaging the toe switch also toggles the on-board pedal between EXP1 and EXP2, so you just have to get them lined up correctly. As long as you turn your wah on and off before switching snapshots, it should always work correctly. The other thing is to make sure you have the wah block in the same bypass in each snapshot.
-
Can you expand on this? Most of my presets use a volume pedal block as the first thing I the chain, and they all still work fine.
-
Yeah, I don't think the Firehawk can be used as an interface to update the JTV69 at this point. Your JTV69 should have come with a USB interface, and that's what you'd use to update it at this point.
-
Plenty of people using Helix direct - probably the majority, if I had to guess. Sounds to me like you just need to make or find patches you like on the Helix. It's certainly possible to have it sound bad, but it can certainly sound amazing, too. I connect my Helix to my mixer with the XLR out connection all the time - have never had any issues.
-
Is it possible to roll back if 2.0 messes up needed patches?
phil_m replied to billlorentzen's topic in Helix
It's possible to roll back whenever, but the one thing is that if you save patches after loading the newest firmware, those won't be able to be reloaded into an older version. So if you want to do the update with having the option to roll back in your back pocket, just make sure you keep an archived bundle or setlist file to reload. The new firmware shouldn't mess up and of your existing patches, though. All of my pre-snapshot patches work fine with the new firmware. I have quite a few patches in which I haven't set up snapshots. -
No, you shouldn't have to update the Helix again... It's probably not a bad idea to do the reset procedure and reload your presets again, though.
-
Have you installed the latest Helix application?
-
Did you do the reset procedure? That is, power off and when you turn it on again hold footswitches 9 and 10.
-
Go straight to 2.0.
-
That is the expected behavior. Per the manual, pg 34: Snapshots also store and recall the following MIDI, CV, and Ext Amp messages sent to external devices from the Command Center: The value of any Instant MIDI CC, Bank/Prog, MMC, and CV Out messages The state (dim value or lit value) of any CC Toggle or CV Toggle messages assigned to footswitches The state (dim or lit ) of any Ext Amp messages assigned to footswitches You have to have the Ext Amp jacks assigned to a footswitch in order to change them with a snapshot change.
-
Lol, I had the Soundtank TS5, too... Actually, I think I still have it in my basement somewhere. That and the Soundtank Chorus were the first two pedals I bought.
-
Funny thing is I just went against my own advice here... I have a gig tomorrow, and I decided to install the "real" 2.0 update tonight... (I was using the last "release candidate" version prior to this). Update went through fine... I've probably re-flashed my Helix about 2 dozen times or more since having it. It's always been a very smooth process for me.
-
Well, that would make sense... To be honest, if it were me, I wouldn't do the update the day before a gig. I think the chance of something happening is very low, but, still... It's just another thing to worry about. If you're not going to have to time to actually take advantage of the new features before your gig, it's not really going to benefit you much to install the update now. If it were a few days before a show, I'd probably say go ahead. But the night before... I don't know.
-
In this type of scenario, which is probably very common, as long as you set up you snapshots so the volume pedal block is on in every snapshot, you should be fine. Typically, you would be in a snapshot, turn on the wah or filter or whatever you assigned to the expression pedal, use that for a little bit, and then select another snapshot. So as long as you don't change snapshots while you have the other effect activated, you'll be OK.
-
I get what you're saying, although, in a gigging situation, I can't imagine ever switching snapshots while the wah was active. As I said, I've been using snapshots for many months, for dozens of gigs, and it's never been an issue. The only time this happened for me was when I didn't hook up my external expression pedals. Also, that brings up another thing - once you hook up a pedal to the EXP2 jack, it's a total non-issue, because the onboard pedal is always EXP1 at that point. It just seems that assigning effects to the toe switch while you don't have anything attached EXP2 is the one exception... The issue isn't really the bypass state of the block as much as it is the toggling between EXP1 and EXP2.
-
You could always assign the volume pedal bypass to some other footswitch, or you can just leave it unassigned altogether. Bypassing the volume pedal is actually a relatively rare thing unless you're using the onboard expression pedal for wah as well.
-
I just thought of this... Remember that when you hit the toe switch, you are alternating between EXP1 and EXP2 on the Helix (assuming you don't have an external pedal connected to the EXP2 jack). So it could be that when you switch snapshots, you could have the wrong one selected. Actually, I'd be willing to bet that's it. When you turn off the volume pedal with the toe switch you also switch from EXP1 to EXP2 (or vice versa), and if you switch presets while the volume pedal is bypassed, and then it turns on in the new snapshot, the actual controller for it, is inactive... Remembering now, I did have this happen once. The problem is that prior to snapshots, the bypass and EXP toggle were always tied together. Now it's possible to break that link.
-
What you're experiencing isn't the expected behavior. There shouldn't be any issue with using a volume or wah pedal with snapshots. I've been doing this for months now (as a beta tester). It sounds to me that perhaps the JTV volume saved with your snapshot is at zero in the input block. So when you go to a new snapshot, the volume of the guitar is dropping and the volume pedal has nothing to do with it.
-
Well, like I said before, it sounds like you may be running into what's described here about the amp not responding when receiving multiple MIDI messages at once... You could run a MIDI sniffer on the Helix to make sure it's actually sending the correct MIDI CC messages when changing snapshots, I suppose.
-
Was the amp responding to CC messages before? Doing a quick Google search in regards to MIDI CC and these amps, it seems there was an issue with early ones not responding the MIDI CC when there were multiple messages being sent.. A quick test you could do is assigning the MIDI CC to a footswitch on the Helix in Stomp Mode and just sending that message to see if the amp responds.
-
Do you do the reset procedure after installing the update?
-
I suppose we could go back and forth all day about what the designed behavior should be, but as it stands now, what you're describing is simply the way it's designed to work. Nothing you're describing is an actual bug (what this thread is reserved for). So I guess my suggestion would be to create and IdeaScale entry for the behavior you'd like to see and go from there.
-
What exactly are you trying to do with the JVM410HJS? Are you trying to recall presets on it or simply change channels? Looking at the manual for it, it looks like the head can store 128 presets, and those are recalled via PC messages. You can have the Helix send out a different PC message as an Instant Command for each snapshot in a preset in the Command Center - that seems like it might be the easiest thing to do. It also looks like you have the option of selecting a different channel on the amp head by sending a specific CC with a certain value. You can also set that up that in the Command Center, although, that might be a little messier.