PierM

You need a clock, and Helix looper doesnt respond nor generate any clock or sync pulse. You are just sending midi commands, which isnt enough to keep things in sync.

You probably had a previous silent loop in memory, so you were overdubbing on a pre-existent closed cycle instead recording a new one.

After lot of tests, my suggestion for M1 users is to NOT install the L6 drivers and just use the native core audio from apple. You still have access to all Helix/HX USB channels, but you can only work at 48Khz. M1 doesnt like high buffer numbers (as those you need to use with L6 drivers), as the system think it's a low demanding task and assign the pipeline to the Efficiency Cores, which are weaker and easier to clip. Yes, with M1 the higher the buffer, the worse. At least until they will give devs the proper access to core priority. Just as example, using HXStomp as interface on this macbook (M1 pro CPU10/GPU16), I can go with 32samples at 48Khz with 8ms (4+4) roundtrip. That's great for playing AU plugins and softsynths. With L6 drivers you need much higher buffer, which means more latency and more CPU because it runs on E cores... On the other hand, an old Scarlett 6i6 runs like a rocket on these machines.

100% SCAM Registrar is namcheap.com, which is the loved by scammers; https://shkspr.mobi/blog/2021/05/why-do-scammers-love-namecheap/ Site name has been registered on 26 December 2022, from IS (Iceland). Address is a well known fake address used by hundreds of scam sites. Registrant Contact Information: Name; Redacted for Privacy Organization; Privacy service provided by Withheld for Privacy ehf Address; Kalkofnsvegur 2 City; Reykjavik State / Provincep Capital Region Postal Code; 101 Country; IS Phone; +354.4212434

So in the end I have seen that all HX software for mac is running as "intel" process which means Rosetta is mandatory. As far as I can say, and unless I really missed something obvious, this statement isnt true. Apple Silicon Support Helix Native The Helix Native VST/AU/AAX plug-in now natively supports M1 and newer Apple computers without Rosetta. NOTE: HX Edit software has worked with M1 Macs from day one.

Hi folks, I was excited to install HX Edit and Native on a brand new MacBook Pro M1 (Monterey), and from what I've read around I was sure they were both running native (Universal), without the Rosetta subsystem for the Intel instructions. Reality is I'm being asked to install Rosetta as soon as I try to install HX Edit 3.51 or Native 3.51, which I DON'T WANT TO DO as it does bottleneck Ableton Live and everything else running into it. Am I missing something?

All HX drivers arent compliant with W11 core isolation so the only option you have is to turn memory integrity off.

It will never happen. :)

Yep seems working.

Full backups working fine here.

That's a good starting point

That's not a good approach. You should not use the output block level as this is a boost (post gain), which means pulling hiss from noise floor and squeezing headroom.

It's odd but not impossible. That's why you have the option to buy matched studio monitors, which means the two units are identical and produced in the same batch. Said that, could be they got a very different use (and a different speaker breakup during the first period of life of the speakers, might be the cause of a slightly different timbre or response).

AI and soundcard are the same thing, and you cant aggregate two interface without getting terrible results, especially on a PC (also not possible with native drivers). You just need an audio interface with better drivers. USB is fine, just try to use a port which isnt part of a chipset hub. Not mandatory, but does helps reducing potential extra calls. **Unless you have pro grade expensive stuff in mind, an Internal PCI-e audio card is a thing from the past.

Your Helix DOES NOT HAVE SPDIF, so you cant use that connection. There are many variables to consider, and these are different for every single machine, so we cant tell you for sure what it will give you a solid, low latency click/pop free experience. Latency is just the relationship between buffer and sample rate (this is a simplification I know), but there are many other factor to consider, that could make a great driver unable to deliver its best performance due other system bottlenecks (DPC calls, hard pages faults, CPU spikes, I/O speeds etc...). To make it simple, I would just buy a cheap and solid Scarlett 2i2, (using standard connections, so it's gonna be Helix(A/D/A)---->Scarlett (A/D/A). That said, Im sorry, but I doubt you can go under 10ms for a complete round trip with all these conversions. Another option could be Native VST, running on that DAW, and being processed by a Scarlett 2i2. At that point you'd get pretty much the half of the round trip latency at buffer/sampling parity, because you removed the first ADA cycle from the LT.

WiFi 2.4Ghz pollution is crazy high these days. Hard to find a place with a clean channel, and consumer products like the G10 arent able to filter out interferences, so they are extremely sensible to that aspect. G10 is 7 years old product, and when it has been released the situation was way better than today. Also, this is even worse on those countries with edge channels restrictions. I was a very happy customer for the G10, with 3 of these toys, but these days they are all parked in a closet because the continous drops (g10S even worse).

Helix Drivers are terrible for LIVE playing, that's all you need to know. :) I never use them as latency is way too high, even on top performance machines. I have few other audio interfaces (MOTU, Scarlett, Behringer), and all of them outrun the Helix drivers. Scarett is the one that gives me the best buffer/latency in terms if reliability. As for the Helix drivers, ASIO4All to the rescue. ;)

Action too low Fret buzz/rocking frets Pickups too close to the strings

@datacommando Ideascale seems working fine now. Happy Christmas everybody! EDIT; No, I was wrong. Still not working.

Tactile microswicthes soldered on a PCB are just a good way for these companies to streamline the production and cut the costs. I cant think of any benefit in terms of lifespan, or purity of the contact (these are in fact the worst in terms of electrical switch bouncing). Also, for heavy stompers, this system does transfer energy from the kick to the PCB, which isnt helping. The tap tempo issue that many are facing with these devices, is also caused by the electrical switch bouncing from these tactile swicthes. Said that, there are good tactile swicthes and bad cheap made in china sub level, tactile swicthes. Those in the Helix are the last. I can easily prove that, so Im not just talkin out of my a++. :)

Line 6 should hire some german engineer, like from LEHLE, to learn how to design a footswitch.. Yep they cost 15$ each instead 50 cents as those used in the Helix, but I'd rather pay the extra instead being scared and worried to use it...

The hardware talk is about the browse knobs (presets, blocks etc..), not the params encoders under the displays.

Unfortunately no answers. Ideascale still looks abandoned, pretty much like this place.

Implementing "code side" rotation ballistics on a low resolution 24 step mechanical encoder (tons of switch bouncing), is plain nonsense. I will keep saying that. If they did it, it was a mistake. Even if seems working fine for you guys, adding a ballistic/logic code to a 24 step encoder is a terrible idea. (while it's a good move on the high res encoders under the display). Switch bouncing is already a potential cause of misfiring in a 1:1 behaviour...add to this a ballistic code and there you have a recipe for rotary farts. :) If you really want to do so, you should go for a different and arbitrary (no logic) solution, like pressing a button while rotating to switch from high speed to detail 1:1 speed).