pilottes

That's why a firmware release every 3, 4 , 6 months is not adequate.

Sounds like the signal in not going where you think it's going. Can you describe how the 4CM is hookup?

Select snapshot 1 go to Command center, select one of the botl ligthning (instant MIDI command), and turn the first knob labelled "command" until hyou get to Bank/Prog. You can set the MIDI base channel 2 and Program number 1 or 2. Beware that it can be offset by one since it start at 0 but you'll figure it out. Save patch go to next snap shot and do the same thing again with a different set of parameters, etc. Good luck

I never use the editor but at the Helix, when you push 1 of the 8 knobs, brackets around the value appears and that is the value for that snapshot. You need to save the patch right away. Then go to any other snapshot and the bracket is still there, meaning taht the parameter is assign to the "snapshot" controller. Any value you set at this other snapshot has to be saved as well by saving the pacht again.

You certainly can change the levels, drives, etc. any parameters just push the knob est turn it. After this initial change any of the 8 snapshot can have a different vue of said parameter(s). All the instant midi message in the command center are associated a specific snapshot. So, no there is very little limitations.

Not a bug, not a feature, by design maybe but a quirk for sure. Need to implement exeption in the FW to prevent it. Or to make it more friendly to a guitar player that get lost in music and not limited by footstep's recipe. Did I mentionned I love the 2.0 update? Man it's so much more than just enough.

After 5 months I now have 2 scribble strips with that problem. So far I don't plan to have them replaced since I don't want to loose it for 2 weeks. As long as it's still perfectly readable.

Well, I just set it to 8 presets in global stings and when you press the UP/DOWN you do get 8 snapshots....

So true!

I consider we were the early adopter so I sort of expected some shortcomings but now it's pretty much where I was hoping it was. This MFX was a long time in development and I'm sure you had all the time to dream up all the possible and the impossibly good stuff. Again, thanks for L6 commitment in this category. Now time to fix the dual cab bug ;-)

Alright I'll include this in my settup. Thanks

Same here! I bet that's what they wanted to put to market last year but ran out of time. That is much more of a finished product. Bravo!

Interesting! My JVM is also set at -10dBV. Would'nt be best to simply set the send/return at Line in the Global Settings for 4CM config?

I don't know if it's wide spread but I encountered some patches where the A/B Y is routed evenly and not the way I used them A100 or B100. And Reverbs delay went up to 7. In both cases they were parameters assigned to a footswitch. Stangely, the initial values were none of the min max values. Only had to step on the switch and resaved.

Oh yes, oh yes. It solves my problems for controlling my JVM with PC instant message per snapshot. Great. The snapshots aspect is exactly what was missing. Love the 2204 mod as well and the Cali Mk sound like my my Mark I used to have. You've done it for me. Now I can play the guitar.

I had a quick view of the JVM410HJS again and reread your messages... I feel that you could probably achive what you what without the CC messages. At least I would start simple with only the PC instant message. See if you get a behavior thta make sense. You absolutaly need to disable the PC send/Receive in global setting if you want to have setlist's independance. If it all work the way it should you shoudl be able to copy an paste presets wherever you want after that and the correct JVM sxetup will be recalled. From the manual CC# 12 to 19 do various things like going over the various gain stage, etc. ? It looks you have more than one thing going on at the same time. Just start with a single feature at a time. The way I did this was. Configured say PC 1 on a given HELIX preset (command center instant MIDI message). Turned to JVM and configure the clean green with FX loop. Press twice the learn buton than press the preset on HELIX. The JVM associate the PC 1 to the clean green with FX loop. You can copy that preset anywhere you want it will always select the first memory on the JVM. Once that work OK you can experiemnt with the CC#. Good luck.

You have to disable the PC message sending in the Global setup MIDI section to rely entirely on the MIDI messages you enter in the command center. That's how I use to do with my JVM410H. The JS version support the CC messages, not the base JVM unfortunatly.

Long story short, I upgraded to FW 1.12. All seems fine now. Had a few weird patches that had problems but was able to fix them. It was related to an A/B Y block that linked path 1B to 2B. I did not try to understanhd it but was able to correct thje problem permanently. All is good. I'm happy..... sort of.

Oups! you're in trouble! I think I was the first to feel the water for Summer NAMM and DI replied to the post but never actually infer anything (as usual). But my point is when they decide internally that a feature is doable and they have a beta going. It would be great, I think, to let the fans know about what's coming next. If Line 6 has no clue as to when the next release should it the street that make me worry even more.

I would be super happy to just get an idea of when they are planning a FW release. I don't get this "not talking because of this or that" What I know it's been 4 months since 1.06.5. and yes we've got an editor, i know. If you'de tell me in 3 months you'll get version 2.0 with a new pdf manual improved and updated I'd stop expecting it each day and go on living... my little OCD side. Oh well....

Well that`s enough to convince me to try the 1.12. I'll do it over the weekend and report back. Thanks

Yes exactly! I know how to fix it. I just want to know if this behavior is still present with FW1.12 and 1.12 editor. When you backup and restore the whole thing and have to go over every single patch it is very irritating to say the least. And I can overlook some. There is definetly somethink broken software wise and I'm try to pin it down. If it fixes it in FW1.12 I.ll go and live with the other BPM issue. At least I will have backup fonctionnality.

Anyone ?

No, not at all. I'm simply stating a problem with the backup and reimport the same patch. The assignment of multiple block to one footswitch is old hat, Its a very simple patch. I would have liked someone else to replicate the problem I described above.

In a nutshell. 1 footswitch assigned to 2 FX blocks.Say chorus and distortion. Chorus is on and distortion is off when footswitch is off. When you engage the footwitch it deactivate the chorus and activate the distortion. You can save that patch with a defaulted ring light off corresponding to no distortion. If you back it up and reimport the ring will be ligthed associated to the activated chorus. It is changing the visual state of the patch and not the function of the patch. Unfortunatly. Sorry for the english I already had gone over the first message quite a few times.