TCStuckey3

OK. I think I get how it works now. Did you do anything besides copy FS5 to SS5-7? Because I did that already when I sent my last reply and it was much worse. It was triggering the sample even more. But yours seems to be better (by the way I don't use SS8, I forgot to tell you that.) And now that I go back to my original one it seems to be better since i corrected the FS5 issue, but I still get an CC80 value of 0 coming through on snapshot change. Doesn't seem to have a pattern, just on SS change somtimes. Theoretically, this shouldn't matter because that's the dim value, but still a little concerning. The device I'm controlling is a Boss RC-5 loop station. But I use it to play recorded samples, not as a looper. I've read that it has some weird midi quirks, so maybe that's part of it, but there's no question the Helix is occasionally sending a zero value. But maybe changed some other parameters in your mod, because yours doesn't do it. Thanks again for all the help.

Wow. First of all, thanks for taking the time to comb through that. Much appreciated. The main problem was that FS5 should always be configured to send the toggling message on Ch. 2. Somehow that got messed up on SS5-7 and it went to 0 on base channel. Easy to remedy. Some questions: - You say "On SS1-4 you have FS5 configured to send a Toggling CC#80 on MIDI CH2. That will send on Preset Load but won't send again until you select SS5-7 where FS5 is configured to send CC#0 on your BASE channel (default is 1). After you select one of those Snapshots (5-7), when you select SS1-4 CC#80 will send again, then not again until you select SS5-7." I don't want it to ever send on preset load or SS selection. I want it only to send when I hit FS5 no matter what SS I'm in. Now, it is a toggle that sends 127 when I depress FS5 and then 0 when I come off. The device I'm using needs the 0 to "reset" itself. Is this why it is not sending on preset load or snapshot change? I hope so because for the most part it has been working except for the random send when I go from SS5-7 and back to 1-4. If I fix my mistake you caught as I mentioned above it will hopefully resolve. But I'm confused on why you're saying it should fire on every SS change. - You say "Normally you would not use a Toggling CC attached to a switch whose primary function is to switch Snapshots, though you might want to use a non-Toggling CC to send a Value specific to the needs of THAT SS." Is that even possible? When I assign a FS to choose a snapshot I don't even see a way to also make it a toggling CC. Maybe I'm missing something but command center only lets me assign a FS to Snapshot HX or Toggle CC, not both. But, again, that's fine because I'm not trying to do that. FS5's sole purpose is to send the toggling CC#80 in all snapshots. The other FS have SS assignments. I'm going to fix the SS5-7 problem and see what happens. Thanks again for your time and effort. -

It is a Helix Floor. Can't find it in command center. Every snapshot still has the switches set up to choose another snapshot. Unless there is some way to assign both a snapshot change and a MIDI command to one footswitch, I don't see how this is happening. I've attached one of the presets. Thanks for the help, @rd2rk. Rooster 1.hlx

I have my stomp switches set to change snapshots but sometimes they are also sending weird MIDI messages that are triggering my other devices. I’ve attached a pic of a midi message recorder showing what is sent. I’m just pressing different switches with snapshots assigned. You can see it send the program change 3 each time, which is one of the instant messages assigned to the preset (which, by the way, I would prefer not happen, but as I understand it any snapshot change automatically resends the instant messages), but you can also see random controller messages sent. Some even on midi channel 2. These messages exist in the preset on another stomp switch that is solely used to send them, but they are being sent when I change snapshots. This has been happening prior to 3.70 and still there after updating to 3.70, and even after going to 3.71. Any ideas?

It's all wired in on a pedalboard. The looper starts up quickly, helix takes a bit.

So I have a looper connected to the Return 1 on my helix. I use it to play stored samples by sending CC commands. I have it working pretty well, but when the Helix first starts up and loads the current preset, it plays the sample that is currently loaded on the looper. This does not happen when I change presets, so it is not a default command. Only happens on startup. Not that big of a deal and I can work around it but I was just trying to find out if this is a known behavior and if it can be easily fixed. Any thoughts would be appreciated. Thanks