kduck

Worth it for the presets alone. Add to that the deep dives on each effect/amp/feature and I'd call it a bargain.

Works on the blackface DR kit that I built. Since your amp has a TRS footswitch jack, I'm assuming it's a modern DR reissue. Looking at the schematic, sleeve = ground, tip = vib, ring = reverb. You will need to set both tip and ring to latching. Schematic for reference: https://www.thetubestore.com/lib/thetubestore/schematics/Fender/Fender-65-Deluxe-Reverb-Schematic.pdf

A cell phone can also cause noise. I remember once I thought my tube amp was picking up noise, but it turned out to be the guitar was picking up noise from the cell phone in my pocket.

Are you using a TRS cable?

Here is how the signal flows in 4CM (your setup): Guitar >> HX L/Mono Input >> (HX pre-send effect blocks) >> HX FX Loop Send >> DC3 Input >> DC3 preamp >> DC3 Channel Master vol >> DC3 FX Loop Send >> HX FX Loop Return >> (HX post-send effect blocks) >> HX L/Mono Output >> DC3 FX Loop Return >> DC3 FX Loop Mix (parallel) >> DC3 Power Amp >> speaker in 4CM, the Stomp FX Loop block is simply your DC3 preamp. The output of the DC3 preamp is controlled by the Master on each channel. With the Stomp mix at 0 this means that your signal is bypassing the DC3 preamp, so your signal chain is effectively: Guitar >> HX L/Mono Input >> (HX pre-send effect blocks) >> (HX post-send effect blocks) >> HX L/Mono Output >> DC3 FX Loop Return >> DC3 Power Amp >> speaker. I would guess that the output from the DC3 preamp is overdriving the Stomp FX Loop Return. I would suggest starting with the following (assuming DC3 mix at 100% and Stomp Mix at 100%): 1. Turn down the DC3 channel volume until there is no unwanted distortion 2. Turn down the stomp FX Loop return level

Thank you, can't wait to dig into the new version!

What @SaschaFranck said is correct. The output impedance of the Helix is very low so that it doesn't get loaded down by the amp. For the JTM45, the high impedance input is 1M and the low is 136k. The low input also sends the signal through a voltage divider, which drops the signal -6db.

True that it would use at least one block, but I think it would be possible to map the CV from a single block to multiple parameters, similar to what can currently be done with an expression pedal. I respectfully disagree. The point in the path that you take the envelope measurement can make a significant difference, both dynamically and temporally. The envelope measured after a compressor/limiter would have a different dynamic range than the dry envelope. The envelope after a delay would be much different, as it would have the dynamics of the decaying repeats. The envelope after an autoswell or reverse delay could be radically different than the dry signal. Definitely some merit to this idea. If that CV was exposed on the output of each block you could have the best of both worlds (no wasted blocks and multiple envelopes. One consideration would be avoiding a feedback loop if CV from one block is fed into a parameter on a block earlier in the chain. Of course, that might be interesting in some cases! Just some thoughts. Not trying to start an argument over an idea that may or may not come to fruition.

That's the way I read the OP as well. Implementing as a block would be pretty flexible. You could put the "sensor block" (not sold on that name btw) after a compressor, for example, to refine the dynamic range of the input to the envelope follower. You could put it on the wet side of a delay to use the delay repeats as a sidechain control. The block approach would also allow multiple envelope followers at different points in the signal chain (dry input, effect output, parallel paths, etc.) Lots of possibilities! Also, seems like it would be pretty easy to implement for L6 since they likely (definitely) already have the envelope follower modeled in the various filter blocks (Mutant filter for example). Hopefully it can get some traction.

What is described in the post sounds (to me) basically like an envelope follower that could be used to control parameters on other effects. Think mutron but instead of the envelope follower controlling the filter, it could control any parameter on any effect (drive, phase depth, reverb amount, etc.). Edit: For the record I like the idea. Basically would let you sidechain any parameter.

@phil_m's approach will definitely work if you are looking to toggle the same parameter values from both the HX footswitch and an RJM footswitch. I use this myself frequently to activate/bypass effects from either my Helix floor footswitches and/or my Morningstar MC8. This effectively makes your RJM a remote FS with the same function as the HX FS it is emulating. Another approach is the one I suggested, which is more complex to set up, but will allow you to send several different values from both your MIDI controller and HX FS (or even use an expression pedal) to control the parameter. Note that I'm assuming that the RJM has similar functionality to the MC8 and that the HX/Helix Floor have the same parameters. Since the HX doesn't have a MIDI loopback option, you will need to set up a few things on both the HX and the RJM. I've tested this on my rig and figured I'd document it for others (and myself :) HX (Global Settings >> MIDI): MIDI base channel must be different than the RJM base channel (mine is set to channel 8) MIDI thru: OFF (otherwise you will get a MIDI loop) MIDI Controller: MIDI base channel must be different than the RJM base channel (mine is set to channel 1) MIDI thru: ON (in order to pass the MIDI CC from HX Command back to HX) MIDI Cables set up for bi-directional communication: RJM MIDI Out to HX MIDI In HX MIDI Out to RJM MIDI In Once the above is set up, you can set up your HX effect parameter and footswitch: Map Effect Parameter to MIDI CC (Scream 808 gain in my example) Set Bypass/Controller Assign to "MIDI CC" Set the MIDI CC# for the parameter as desired (I'm using CC4 in my example) Set up FS in HX Command Center: Select footswitch you want to control the parameter (FS11 in my example) Set command type = CC Toggle Set command MIDI Channel to your HX base channel (ch 8 in my example) or leave on "Base" (both options work for me) Set command CC# to the value you set in step 1 above (CC4 in my example) Set the command Dim/Lit values as desired. You will have to play around to get the MIDI value (0-127) aligned with the parameter values you want Set the type (latching/momentary) At this point, test your HX footswitch. It should toggle the parameter between the 2 values you've set in Command Center. What's happening behind the scenes is this: 1) the HX Command sends a value (0/127) on CC4 Ch. 8; 2) the MIDI controller receives it and passes it back to the HX via MIDI Thru; 3) HX receives the message and applies the value to the parameter. Now you can set up your RJM to control the same parameter. Just make sure you are transmitting on the HX MIDI Channel with the correct CC#. With this approach you can also set up additional HX footswitches set different values for the parameter. For example, I could have one FS to toggle gain between 0 and 10 (example above), then set up a second FS to toggle between 5 & 7 (following step 2 above): You can also set up an expression pedal to sweep the parameter across multiple values: ...and all 3 can be used together on the same preset/snapshot. Anyway, hope this helps and you find it useful.

I haven't tried this (not at my rig currently), but I think that you could assign a command center command to accomplish this. Assign the parameter to a MIDI CC (as you have with your RJM) , then set up a command center MIDI command on the desired HX Stomp footswitch to toggle that CC.

To be clear, the problem I had did NOT disappear/resolve when I rolled back to previous firmware as I stated in my post here:

Update: I shipped my Helix to Line6 for warranty repair (shipping paid by Line6). I got it back 14 days later and everything is now working. The tech support rep was very responsive throughout the process. I did ask the rep, "Just out of curiosity, have you had other units fail post 3.5 upgrade?" The rep's response was, "Its not a common failure, so it's most likely just a coincidence rather than an issue with the update." Just thought I'd share that exchange with the group. All in all, a positive experience for me.

Very strange. Maybe check to make sure that Logic isn't sending a MIDI CC #70 message.