Left hand audio cuts out

[theboysmithy]

I had a really weird bug on my old intel MacBook Pro where the left channel audio of Piano v2 would stop mid-way through a session. At the time, I just chalked it down to my old hardware, but have now experienced exactly the same thing on a brand new Mac Mini M1.... has anyone else encountered anything similar?

[MajorFubar]

Mac user here (but not yet M1), can't say I have noticed this. Is it something you can make it do under certain repeatable scenarios or does it happen randomly? Also is this when using it in a DAW or standalone? While I haven't encountered this at all, as much info as possible might help diagnose the problem.

[theboysmithy]

It's in standalone mode - load up the app, play the keyboard for a bit (doesn't matter which preset)  everything fine and dandy, then just cuts out audio on one channel after a couple of minutes. Only happens on Piano V2, none of my other V collection instruments...

I have tried with different headphones too, just to make sure it's not a hardware problem

I might just try reinstalling - though as it's happened on two different machines, am worried that I've just hit on a rare bug of some sort...

[MajorFubar]

That's weird. I can't say I have ever encountered this at all.

It definitely sounds like a rare bug.

Had you only been encountering it on your M1 I would have chalked it up to some likely-unidentifiable consequence of running the app through Rosetta. But you mentioned you had it on your Intel Mac as well, so that's a red herring.

Arturia developers don't come here very often except immediately after the launch of a new product. So I would recommend raising a support ticket through your Arturia account. That won't instantly fix it of course, but at least it will be officially registered as a bug. Tip: don't mention in your ticket that you're running it on an M1 via Rosetta. Arturia apps haven't been optimised for M1 Macs, you don't want Arturia helpdesk to just latch-on to those few words in your ticket and 'kick you into the long grass' with a reply that incorrectly blames M1 incompatibility.

[theboysmithy]

Thanks MajorFubar - yes, think it must be an obscure bug - seems to be OK if I play from within the DAW so at least I have a workaround. Fingers crossed that this gets fixed (but more impatient for M1 native versions of V collection!)