PierM

It may sounds tricky...but still better than iLok. Jeeeez...I once forgot to uninstall couple of eventide plugins from my old laptop before to trash it, and I almost had to write a begging letter to the Pope to get back that activation slot. Took more than a month to get the request approved. Viva L6!

I still see a lot of overthinking here, probably because isnt a typical guitar controller but it's really easy stuff, Just copy from Zoia and be happy, ;)

I see. I'm not aware of any commands being sent at boot, and I remember I used my Helix with many loopers without any issues. Today I only own the Stomp, and as far as I can see, it's not sending any MIDI at boot, apart those commands stored in the presets. You could plug the Helix to a Midi event monitor and see what event is being sent at boot, if any.

Also, many cables and adapters from USB A to USB C are using a chip that needs to be discovered and allowed by MacOS prior any device connected to them. This means you have to unplug the Helix (and any other usb device) from those adapters each time you reboot the Mac, and re-plug after boot has completed.

Can't you just turn the Helix before the looper?

Zero issues with a MBP m1, running latest ventura.

Hi, this is just a community forum, with basically no interactions with the L6 guys. The right place for ideas is https://line6.ideascale.com

This envelope is ALREADY AVAILABLE inside the helix and used in all effects using the signal to drive an effect; Auto Wha. Auto Swells. Compressors, and many of those legacy effects that uses ECFs (Envelope-Controlled Filters). Calling it sensor just makes everything more confusing. Let's take the Helix auto wah blocks. How does it works? A bandpass filter let the guitar signal pass only at a specific peak threshold and then it attenuates its shape above and under this envelope. Then they use the envelope detector (which becomes a dynamic envelope follower) to produce a control voltage from the top end of the input, this CV signal is then used to dynamically sweep the cut-off frequency of the bandpass filter, emulating the behaviour of a wah pedal. Isntead of your foot, it's the envelope detector driving the filter. It's really easy to implememt. Line 6 just need to expose that same envelope for the user on the UI (imho the command area is the right place), and give the user the option to drive whatever parameter of any effect, using such envelope. Again, it's all there already.

You dont need to waste a block slot just to turn it on or off, you can do it with commands. Let's say you want to control a reverb with that "sensor"; you'd go in the Commands section, select a FS to assign then set the Sensor as command, assign the block to listen as audio, assign the reverb block and the parameter(s) to control, and the sensitivity. Done.

A block is meant to process audio and return audio. Has an audio in and an audio out. An envelope detector is meant to process audio and return a control voltage. Has an audio in, and a CV out. Is a controller, not an effect. Wasting a block for a controller would be a huge waste for HX users, even if I wouldnt really need it, as I have infinite envelopes available through the Zoia controlling my HX Stomp presets. Tons of fun and weird things you can do. :)

As i said, these are not my ideas but just how it works. I use the envelope detectors every day to do these things, so Im just suggesting how to better propose the idea without reinventing the wheel. ;) PS; position on the path doesnt matter as you can always just tell the envelope detector where to link, which means the detection will just start at a specific block stage. PS2; if you dont want start an argument, then dont. ;)

Yes, it's an envelope follower, and using it as a block would be a waste as this CV is already available in the Helix, under the hood, just not being exposed for the user. The envelope follower is just a control voltage signal that's composed by the top end of a signal level (envelope detector), and being used to control basically all effects that needs that CV, as compressors, auto wah, auto swell, etc etc... A Control Voltage is doing pretty much what an expression MIDI does, with the difference that the range it's 0 to 1, instead 0 to 127. 0 is no signal, 1 is peak of the given envelope. Using it as a block means wasting room in the path for no reason, and also means you need one of these blocks for each effect you'd want to control. Isn't an efficient way to use a controller, that is virtually DSP free. You may think a block would be nice as you could put wherever you want in the path, but this wouldn't change much, as the envelope would be pretty much the same at any point, just with a different dB level, which is something you could control with a simple strength parameter. All they should do is to expose that Control Voltage that it's already there, and put it somewhere in the controller page, and that you can use to link whatever parameter you want. Think it like an expression pedal, or a CC coming from the outside, but that it's automatically driven by the signal. Then they can add a strength control for each connection, that allow you to set the ratio between the control voltage and the param change. I'm not inventing anything, that's something used every day in any synth, or effect that uses the signal to drive a variable effect. :) I think your description would just confuse the reader, and would make it looking overcomplicated, while it's extremely easy to implement.

Let me tell you that, real story; since last year I had a full alexa domotic setup in my house. An echo dot for each room, hubs, smart lights, smart cctvs, air quality sensors per room, and every possible smart crap. After couple of weeks of this is mess online, my cat gradually started going nuts, running away from invisible things...pulling his own fur, stinky pee everywhere. Vet said was suffering of some allergy...so I started changing his diet, and everything...but nothing changed. Pretty young cat, never had a problem before...so after couple of months I started doing some reverse engineering in my head, and I realized the cat started this behaviour just when I setup the smart house. Next day I pulled all the wifi lollipop off, and kept only the router for my daily internet. After a week every single symptom was basically gone. Vet said was a coincidence, I call this BS. I'm 100% sure it was the EM exposure, so all that Alexa crap will stay off and buried in a closet.

What the OP is trying to describe is called Envelope Follower. An Envelope Follower will analyze the incoming audio signal and produce a CV signal based on its signal strength. You can then use this to trigger filter sweeps, audio effects parameter, etc. The connection strength can act as a sensitivity control. In the Helix would be extremely useful for many purposes, like for example link your playing dynamics to a set of reverb block params, to reduce its presence while playing and push more while signal is decaying. You could then setup your own auto volume swell, or create an extremely dynamic tube behaviour etc etc... It would need to be available as a controller, not as a block. What’re some other places envelope followers are used? Envelope followers are actually really common, but are generally built in to other devices. For instance, auto-wah pedals are controlled by envelope followers. Compressors effectively utilize envelope followers to calculate gain reduction (read all about compressors in our post about just that).

2.4 Ghz is a doomed frequency. Every single piece of wireless crap is using it, and even with 11/13 channels this isnt enough to get a solid link without something overlapping your bandwidth and injecting jitter and noise. The huge amount of SSIDs, smart devices, routers, extenders, smartphones, hubs, wifi bulbs, doorbells, cctvs, etc... are everywhere and filling every inch of air. This system isn't good anymore for Wireless audio, and it's time to move on something else. There are companies working on it, as this is a real problem, so I don't think is a commercial move. My L6 Relays also worked perfect for years, but now they are just grabbing dust because totally unreliable due the 2.4Ghz pollution. The only way I can get them working again, is to busk in a desert.

Probably you are expecting a different kind of clipping, more typical on analogue signals. Digital clipping is different and doesn't always produce distortion. In fact, it rarely does. Digital clipping means your signal transients are being "clipped", so everything above that line is being dropped. It can pop, or crackle, or just inject noise...whatever, isn't a good signal you are getting. The "trust your ears" isn't always completely true... ;)

Focusrite ASIO are compliant. Motu ASIO are compliant. Ampero Asio are compliant... :) None of the L6 drivers are compliant, not just ASIO. ;)

Yeah, must be a coincidence the problem does disappear completely when rolling back to the previous firmware, and come back only with 3.5. Suuuuuure. XD

Have you tried to apply a MIDI monitor to that data? I would give it a check to see what's exactly happening at every stage. Maybe you can tame the problem filtering useless information, or hijacking stuff to different channels.

Depends on your Native presets. To make them compatible with the HX Stomp, you should set Native to work in HX Stomp compatibility, otherwise you don't know if HX Stomp will have enough power (DSP) and room (Paths) to execute the same preset.

Variax is pretty much legacy, even if they are still selling few items. Drivers are not usable in last gen OS, there is no firmware updates since ages, guitars are very hard to find, VDI adapters are pretty much gone, batteries distribution is still very erratic, and JTV59 are already legacy in Europe... They still says it's because "shortage of materials" but it can't be true, as anything else it's still being produced and distributed more or less like before the pandemic. I wouldn't be surprised to see the VDI port being abandoned in the next gen products.

Oh yeah, you are right. My head was thinking he was going to send to iphone via BT transmitter, while it's exactly the opposite, so latency isn't an issue.

Glad you solved. Honestly, I was pretty sure would have worked out (specs are the same, with much better protections than the legacy model, and much better idle consumption). Yay. :)

...it wont work unless you are fine getting a backing track with a 250~300ms latency.

In my experience the HX Stomp doesn't really like busy MIDI while receiving clock, and EXP (continuous CC) can indeed unsettle the HX bus. I've experience that a lot of times when trying to receive CCs from Zoia + clock, in fact I gave up trying to feed it with any external clock and at the opposite, I'm using its own clock as master for the other devices on my pedalboard. This kind of solved the problem; the HX clock isn't the best I've seen in terms of jitter tho.