PierM

Nope. Auto means "Auto-Sense", so it does automatically switch from external clock as soon as it does receive such a message. If no external clock is being received, then does automatically use its own internal clock. In this scenario, the input isn't your TAP, but the incoming clock.

Cable is nothing magic, just a cheap LAN cable CAT5, that is soooo long that it's pretty much useless (unless you keep the rack far from your position).

I'm sure there is a reason if they added DC IN and USB hardware to the Helix Control. You don't engineer and produce random stuff without a goal and a plan. This means the Helix Control is capable to work as standalone USB controller, as soon as both Controller firmware and host will comunicate properly. Probably won't work as a MIDI controller with non-l6 stuff, but I'm pretty confident it will work with Native. It's 2021, there is a new generation of musicians which are mostly working live with laptops and ableton. Helix Control would be the perfect companion for Native in a rehearsal or a live performance.

I bought a WL-50, to replace my two G10. Well, it's a nice unit, but does affect the tone, especially on hot pickups. Kind of dirty breakin/distortion at any distance from the receiver. I'd suggest to try it before to buy it. ;)

Well, let's say some company are more fair than others. I suffered a swollen battery with a 3 years old iPhone. Brought to service for a repair on a Apple service, they gave me a brand new iPhone (new model as mine was previous gen) for no money. That is the Apple's Quality Program E1.

10ms of round-trip-latency is totally fine (as soon as you are not to far from the speakers) . I'd suggest to read this article and research; http://whirlwindusa.com/support/tech-articles/opening-pandoras-box/

Originally, the official specs were declaring 8hrs of charge duration. Today (and that's since the new firmware), they are saying 6hrs, in the same specs; "The system also includes the compact G10T transmitter, which plugs into your instrument's input and features a rechargeable battery that provides 6 hours of playing time on a single charge." Real life is max 3hrs, with a brand new unit. This is false advertising: https://www.classlawgroup.com/consumer-protection/false-advertising/laws/ In an ideal world, this would be enough for a Class Action for a global refund. That's also more food for lawyers lol! In the real world, is a big L6 shrugs.

Totally true. In fact that entire video sounds totally garbage to my ears, taste, perception etc etc etc.... I mean, I hear nothing to write home about. As for the OP about that AES/EBU Vs XLR, no, there is no tone difference. Nothing we could isolate in a youtube audio stream. Let me also add that trying to share how an amp sounds in the room, with people not actually in that room, is a waste of everyone's time.

Dont hold your breath, since even a brand new unit (flashed with new firmware) will give you less than half of the "old days" battery charge duration.

CC32 inst just a "Bank" message, it's a Setlist message, so it does search for a structure/tree within MSB (0) and LSB (32), and then needs a preset PC, otherwise does nothing. I do reccomend you to read the "unofficial" Helix MIDI guide, to go in depth with that aspect. https://www.dropbox.com/s/8nynknyencnvqar/The Unofficial Helix MIDI Guide.pdf?dl=0 EDIT; @kduck ninja! :)

As far as I know, yes. 3.1 will introduce new stuff. As happens with every bumped firmware version... :)

Piezo, EXA and MIDI guitar are almost 40 years old, and tech behind these things it's still more or less the same as when I was a kid... Apart the Synthaxe and Variax, I cant think of other milestones along these decades. Saying that because this market is niche of the niche (which means snail's pace R&D), and as today, Variax is still a thing, with basically no competition. Would be great to see a new gen, with same tech, but with much more DSP for better sounds and less latency (especially for low tunings). I wouldnt change anything else honestly. Maybe a revamp of the software UI, which looks a bit rusty in 2021...:P

This is a bug, not sure if in the Helix or in the PCabs. I have the same setup, and I get this when Helix power up BEFORE the two PCs completed their own boot, or when the last Powercab in the daisy chain, turns ON before the rest of the rig. Anyway, try a different boot sequence like (starting with everything OFF); 1) Powerup the Powercab A (the one receiving link from Helix) - Wait the boot to complete 2) Powerup the Powercab B (the one receiving link from Powercab A) - Wait the boot to complete 3) Powerup the Helix If doesnt work, try 2), 1), 3). If doesnt work try 3) 1), 2).... Point is, test different sequences, 'til you find the one which works for you. (sounds silly, but Ive read people solving with a different sequence than mine, but that wouldnt work for me....) Important thing is to just wait for every device to complete its own boot, before powering up the others....

Never had a Pageflip or OnSong on my iPad, so not sure how this is working. From the sound of it, I'm assuming it's a macro available in the Pageflip firmware/software. You can't do these kind of macros with the Helix, you can just either send a momentary or a toggle CC, but the action to scroll through songs while pressing, sounds like a macro to me, something that waits a second or two, then start sending continuous commands to the OnSong application, until you lift. Again, just assuming here... no idea how these things are communicating, neither I know what kind of MIDI messages OnSong can manage. As soon as you have all the toys at home, you can start experimenting on your own. ;)

Ok nevermind. I've found that disabling the hardware compatibility option, does allow me to assign same CCs as the hardware. Which is IMHO a nonsense, as they were already assigned and stored in the preset, exactly to respect the Hardware compatibility mode. Bah?! Anyway, at least this way seems working, even if I have to reassign CCs to blocks, to be exactly the same as they were in the preset, LOL. :) See in this pic. The original assignment are those with dimmed colors, and referring to hardware footswitches. Those can't be used... But then, disabling compatibility mode, does allow me to reassign those same CCs as the hardware, as in the pic. Looks like a bug to me, or a bad design.

Hi guys, as the title says; is there a way to just use the same MIDI mapping as the Helix Control and Helix Stomp/Footswitch CCs? I mean, I do have my Rack in the studio, and Native at home. Is there a way to have my Native just using the hardware CCs, so that I don't have to use extra mapping? I have this option in other devices. For example, my Obehreim Echoplex hardware and its plugin counterpart (from the same engineer), they both use exactly the same stock reserved MIDI mapping, so the virtual version can just reuse same controller presets as the hardware, without have to remap MIDI controllers. I tried to do that, but seems only working for snapshots (they do act correctly, just using same CCs and values, as the hardware), while I can't find a way to do the same with Stomps/FS. They just seems ignoring those CCs that I've programmed in my controllers, and that are those used by the Helix hardware. What's the pros of this? Well, that I can create a virtual setup on my DAW (Ableton Live), that does (almost) perfectly mirror the hardware counterpart, without have to create dedicated mapping on my controllers, for the plugins. Any solution, thoughts?

If you are sending from Helix to the iPad, through the H9, that's a THRU not an OUT. The THRU mode is often filtered (especially on devices with a single THRU/OUT), so you can only hope that H9 has a clean and reliable THRU, otherwise it could be glitchy. Said that, if you are just sending couple of CC messages here and there, it should be fine.

Depends on the iPod. The iPod touch are indeed HOSTs, running iOS, and they can use a Camera Kit. They are like iPhones without Phone...:) If it's an old iPod classic, then no.

Voted. I think the core point here is if the Global EQ which is already available, with its own reserved DSP power and logic, could be hijacked to AES/EBU at the same cost, or if would need extra logic to be asked to the DSP...in which case would break presets. If the first, we have a chance to see it implemented in the future....if the second, I wouldnt hold my breath. Said that; without that option, I cant really see the advantage to use the Link with Powercabs (that are boomy by default, even with the low cut). Not advantageous enough to justify the absence of Global EQ (which is fundamental for gigging people).

Buddy, you are killing me! That was my first suggestion in this thread....:D.

Man, just chill, you risk a stroke lol! They could do it, just not a priority.

HOST needs power and there are not other way to feed it without a DC IN. ...and No, MIDI cant feed VA to an HOST, neither the Helix. And btw, you have already an HOST that can run "without" DC IN....that iPad with its battery. :P

Power is going nowhere, even if you had 100 MIDI devices in a daisy chain. It's current draw that matters, and those BT trasmitters are usually requiring small currents. Should be fine, but dont ask me 100% warranty, as I never tested this specific solution. On paper, it should work.

It should work yes.

If there is something, is under the Legacy section of FILTERS.