rd2rk

Your screenshot is showing one of the new 3.70 models (Dripman), also the new Brit 2203, so I'm not sure what your problem is?

Did you perform a Factory Reset after the update per the update instructions? Reboot holding FS 9&10.

Standard MIDI usage is a Value of 127 (or 64-127) turns something ON, 0 (or 0-63) turns it OFF. It's not clear what exactly you've got going on, but from the HX One manual: "CC#4 Value 0-63: Bypass; 64-127: Engage Bypass/Engage (independent of CC1, which toggles the effect on and off, regardless of current bypass state). Provided primarily for use with MIDI knobs, where moving them past 12:00 will turn the effect on/off" So, if you want it ON use CC#4 Value 127; If you want it OFF use CC#4 Value 0.

As to documentation, basic FS and IC behaviors are covered in the CommandCenter portion of the manual, but the "rules" are not well covered. I learned this stuff through years of sometimes frustrating experimentation.

I assume that the CC that Helix sends to TouchOSC causes it to perform some of those GP and Ableton functions. Why not have the Helix FS call the Snapshot directly and use an IC in that Snapshot to send the CC to TouchOSC? Edit: For that matter, why not use the ICs in Helix to perform the GP/Ableton functions and cut TouchOSC out of the circuit completely?

Behavior confirmed. Makes total sense. The switches send on both PRESS and RELEASE. This allows for messages to be sent on both PRESS and RELEASE, enabling MOMENTARY behavior when, for instance switching SNAPSHOTS. When sending CCs, once a message is sent on PRESS, it is not RESENT on release. This is standard behavior when, for instance, using ICs (Instant Commands). When a SS loads the IC sends the message assigned to it in that SS, and that message is not resent until a different SS sends a different message on that IC. In your case, when you switch to SS2, no PRESS message has been sent, so the message is sent on RELEASE. I suppose that it might be possible for the programmers to create logic to accommodate your situation, but I can't imagine why they would have thought to do so. In what real-world scenario would you want to be HOLDing a FS while switching snapshots from an external device? If I could understand WHY you would want to do this, maybe I could figure out a workaround. At the very least, an explanation of your use case might allow you to make a case on Ideascale for inclusion of such logic in the code.

You won't see the names of the FX, so you might want to print out pages 8&9 of the Pilot's Guide as a reference. 4. Press and hold the EFFECT button for two seconds to enter Effect Selection mode. The AMP SELECTOR encoder LED ring will dim, and you can then use the SELECTOR to scroll through the six different effects within a given category. Press EFFECT again to set that effect within your preset. To change EFFECT categories, press and hold the EFFECT button for two seconds. The Amp SELECTOR light will dim. Then release and use the TAP button to scroll through the three separate effect types (Delay, Modulation, and Pitch/Filter). Press the EFFECT button again to exit selection mode. Remember to press and hold CH A or CH B to save your settings to that preset.

Need more info. The solution depends upon the actual cause, which could be a couple of things. Attach a copy of the Preset (the actual preset, not a screenshot).

I can reassure everyone that I got no buzzy fizzy problems with MY stock speaker. Different ears I guess...

Or you can enable MIDI Over USB on Helix and use routing SW such as MIDIOX to take the USB Output from the S61 to the Helix. You can also do that with most DAWs. I know I can do that in Reaper. The only time you'd need the 5-pin would be if you're not connected to a computer or other host - you can probably use an iPad to do it for that matter.

By default Helix listens on MIDI CH1. Check in your MIDI Monitor if the S61 is transmitting on MIDI Ch1. If YES then all you should need to do is connect the S61 MIDI Out to the Helix MIDI In. If NO then set Helix Global Settings>MIDI/Tempo>MIDI Base Channel to match or vice versa - set the S61 to transmit on the Helix MIDI Base Channel.

Templates are "How To" help. The Templates named for DAWs are CONTROL templates. If you had a HW Helix you would use them to control your DAW. The commands would be found in Command Center, and their names would be reflected on the scribble strips. I suspect that they appear in Native because they just copied that setlist over from the HW without editing it. Happy New Year!

Linux being Open Source means that there is very little money in it outside of the corporate server area. Therefore there's less demand for Linux programmers and, since corporations can pay the big bucks, the ones available are used to big bucks. The digital musical instrument industry is tiny. The number of desktop Linux users is tiny. Also, there's no such thing as "LINUX", just a dozen or so versions which (not positive about this) likely have differences which would need to be accounted for. Considering all of the above, the ROI of developing Linux apps is likely in the negative zone. That's why very few digital music products are developed for Linux vs Windows and MAC. I wish that were not the case. With WIN10 nearing EOL and my present HW being incompatible with WIN11, I'm about to have to buy two new computers when both of my current machines are very much capable of running Linux.

The following is requested for both OP's benefit and my own curiosity. With WIN10 EOL approaching - which will require that I replace BOTH of my older Windows machines - I MIGHT buy a MAC. It is NOT an attack. Please explain WHY it matters - the benefits and possible drawbacks - I've read that there are some drawbacks to using an aggregate device configuration. Thank you in advance.

I also use an 18i20. I've compared recordings made direct from Helix/HXS and through the Scarlett, and I can't perceive a difference, the converters are that good. Using my Helix with SPDIF there should be NO difference, but again, I can't tell.

If you're not PLAYING through plugins, then using Helix as your AI is the way to go, as it allows you to Direct Monitor your playing (zero latency) through Helix while simultaneously recording a wet track and a DI (un-effected) track over USB (no additional AD/DA conversion) which can be used for re-amping through Helix Native or other plugins when latency is not an issue. This configuration is what Helix was designed for. If you're PLAYING through plugins then you might want to use a separate AI, as Helix latency in this configuration can be an issue. For instance, on my ancient i7 laptop system, RTL (Round Trip Latency - AI Input to AI Output) using Helix as AI is <>12.6ms at 64samples (buffer rate) vs <>7.6ms using my Scarlett as AI. If you have the Helix Floor/Rack get an AI that has SPDIF. This eliminates the added latency from the AD/DA conversion between Helix XLR out and the AI's XLR IN. IOW, the signal remains digital end-to-end. The only latency is the processing time (and single AD/DA conversion) in the Helix itself and the computer/DAW/Plugin. As for the sound quality itself, Helix vs external AI, only a "Golden Ears" professional recording engineer will (maybe) hear a difference and eliminating that difference will require a MUCH more expensive AI than the home recordist needs.

Go to Ideascale: https://line6.ideascale.com/c/ SEARCH for variations on "touchscreen". VOTE for all of them! While you're at Ideascale, SEARCH for variations on "wireless". VOTE for all of them! If you read the rest of this thread, you SHOULD understand that nobody will know when "Helix 2" or whatever they decide to call it is coming (or IF it's coming) until shortly before its release. While you roll the dice, I'll be enjoying my Helix and not worrying about the (as always) unpredictable future. ;-)

Yes, I should have said that the "harmony" is relative to the interval, not true harmony relative to a key.

I didn't spend a lot of time with this as it's an effect that I never use, but you may be right that it's the same effect with different default settings, which would explain the identical icons. The default settings cause the "Pitch Shift" to output a single note, pitch shifted, whereas the "Pitch Harmony" results in two distinct notes in harmony. If you play around with the MIX and SHIFT LEVEL you can make either sound like the other. The only parameter that remains the same between them when switching is the INTERVAL.

It definitely requires a strategy. Maybe use your SAVED Snapshot to initialize the other devices, then use your other 7 Snapshots to change their settings as necessary? A Snapshot that changes settings on devices 2, 3 and 4 won't change the setting on device 1 unless the snapshot tells it to, which may be the logic. If it's already set the way you want it, why would you want to send the same setting again? If the setting being sent is a Preset Change it might even be detrimental, as reloading the preset might cause an audio glitch while the preset unloads and reloads. As to L6's actual logic, nobody outside of L6 knows and nobody within L6 will ever tell. It is what it is and ever will be. You could try posting your preferred fix on Ideascale, but don't hold your breath.

What you're seeing is designed behavior. Snapshot ICs won't resend the same message consecutively. A different message must be sent on that IC before it will resend the first message.

ASSUMING that I understand what you want to do, AND ASSUMING that your singer's presets/snapshots are on the HXS, you would want to control that using the InstantCommands (ICs) in the LT's presets. Setting the LT to transmit and receive on MIDI Channel 1 and the HXS to receive on Channel 2, configure the ICs on the LT to send on Ch 2. When LIVE sends a preset change to the LT the saved snapshot will send the configured ICs. When LIVE sends a CC#69 (Snapshot Change) to the LT, the ICs configured in THAT snapshot will send. IOW, LIVE controls the LT via USB and the LT controls the HXS by standard MIDI via the LT's snapshots and ICs. IDK how to get this to work with LIVE, I tried but couldn't get LIVE to record MIDI at all. I know that it will of course, I'm just not familiar enough with LIVE to make it happen. In Reaper it took 2 seconds to set it up, and it works flawlessly. Maybe @DunedinDragoncan tell you how to do it in LIVE.

Keeps it down to just the one FX Loop 1 Block. Simple is better.

I suggested using two loops because the Helix SEND 1>Amp Input needs to be INST, and I said that he MAY have to use Return 2 set to LINE. If the Amp is returning a Line Level signal that would be necessary to prevent overdriving the Return 1 which is set to INST. @NevenThave you set the DRY THROUGH on the FX SEND 1 Block to -120db? That needs to be done to prevent the clean signal from bypassing your Amp, going direct to the RETURN 2 Block and mixing with the RETURN from the amp. Also, on the RETURN 2 Block set the MIX to 100%.

Per the diagram from @MGW-Alberta. Make sure that in Global Settings>Ins/Outs the FX Loop you're using is set to INST. You may need to use SEND 1 (INST) and RETURN 2 (LINE).