PierM

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.

Line 6 isn't reading your posts over here. If you want to ping them about that aspect, contact support. As for the drivers, I don't care anymore, I moved my DAW to MacOS and only use core audio. Bye Bye Micros**t. :)

You can send commands to multiple devices just using the MIDI THRU on every next device, like Helix--->SY1000 (ACTIVE MIDI THRU)--->Vocal Processor Then assign a dedicated MIDI channel to each device to prevent wrong assignments, like Helix on CH1, SY1000 on CH2 and Vocal Processor on CH3. At this point all you have to do is to specify the Midi channel on the command so that only that specific channel will execute. You can send a command per footswitch, one per pedal and six instant commands.

Dont know if it's being used in the Helix, but a direct substitute for the VOF6512 is the ECS65US12. Id contact support for a confirmation, even if they share exactly the same specs. https://www.xppower.com/portals/0/pdfs/SF_ECS65-130.pdf https://www.newark.com/xp-power/ecs65us12/power-supply-ac-dc-medical-12v/dp/67R9479

I wouldnt hold my breath. In more than 20 years I follow this brand, I dont remember a single core product copying something already existent in the market. In fact, it's pretty much the opposite. So, if any Helix 2.0 is in the plans, I believe will be something completely different than what you see around these days, and as the origianal Helix, will be probably looking to the future, not really to what people can already buy now from another brand. Honestly, if they'd release a Helix/HX Mark II, with same core but better construction, top quality parts and less chinese low budget components, Id buy it again and I would be happy. :)

Be sure you are not hearing the picthed tone above the acoustic sound of the strings. :) Also, post a preset so we can check.

I'd try to shape the attack through compressors and a bit of eq and see what you can get, not an easy task. Also depends on the nature of the attack. An heavy and thick pick produce a huge transient at the attack which may be really hard to hide to the Pitch Block. You could also try experimenting with a split dynamic block, placing the pitch only to path A and see if you can manage to send the attack noise transient to path B, without the pitch block. The hard task here is to isolate only the noise transient, without getting any harmonic mix between the two paths, otherwise you'd always get some harmonized transient...:) Split > Dynamic Settings Threshold; Any signal below the Threshold volume level is routed to Path A; any signal above the Threshold is routed to Path B. Attack; Determines how fast the signal is routed to Path B once reaching the Threshold. Decay; Determines how fast the signal returns to Path A once falling below the Threshold. Reverse; When on, reverses the path assignments (any signal above the Threshold value is sent to Path B, any signal below the Threshold value is sent to Path A).

Unfortunately the HX and Helix won't listen for redundant PCs, so once a preset it's loaded into memory, it won't respond to that same PC, which means what's being selected and active (snapshots, FS, params, whatever editing), will stay there until you change preset (or reload from the onboard). Only trick I could think of, is to create an empty preset somewhere (like at the end of your setlist), and send a double PC for each preset (command, wait, command), first is the last empty preset, second is the preset you want to reload. This will send a quick double command, that it will force Helix to unload and reload the memory. That's some extra time gap I know...

This sounds like you were plugging your helix and modeling in front of a guitar amp...which would explain the shrill and the entire tone chase. Anyway, whatever it works for you. :)

Yes, guitar amp (5Khz range vs FF), the guitar (pickup, wiring scheme, pots values, caps, strings, nut, saddles, frets etc...) and - last - but not least - your playing and touch (style, skills, pick material and thickness etc), can make the difference. Especially between what you hear on youtube and your own room.

Post some audio. All this talk without listening it's just a waste of time. It's like talking about the smell of clouds. Sorry didn't want to be harsh, but you use a lot of words, without going into details (that matters!)... On paper, a modeler will always be brighter than a guitar amp, even just because they are two completely different things, and one it's capped to ~5Khz, the other is capable of a full freq response, with mic response and room response involved. Plus there is the guitar, the pickups, your playing, the system you use to monitor and compare etc etc... That's a lot of variables that can't be analyzed through words...so yeah, I'd post some audio just to understand if what you are getting is in the normal and expected range, or you are getting something weird that needs further "investigation".. :) All I hear from that video is that his guitar is out of tune, and he's also adding a lot of extra dBs on the high side because he's saying base tone is too dark. :)

It does give me back pain just watching at it...

IME the Helix/HX ASIO drivers never been good enough for live/low latency use. Even on high performance computers, I never managed to get a solid and reliable low latency performance. Something I could easily achieve with my Scarlett, or MOTU, or the little Jogg. Same story in MacOS. Core Audio works much better than L6 drivers. Again, this is just my own experience, in 8 years I do mess with these devices (I had the Floor, then Rack, now I only own the Stomp). On the other side, these drivers are perfectly good for standard DAW operations, where a super fast round trip isnt a requirement. The drivers are good and reliable, but not fast enough for live VST, that's it. If you really need to use VSTs for live, my suggestion is to find a product with better drivers for this use (like RME).