You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was using ppooll today for quite a while, and if I changed the volume on my audio interface (an Apogee Duet 2) after not doing so for a while, all of the sound would stop and I would get the spinning ball on my mac. Eventually, I could turn host@ on and off and sound would come back on. Very strange, it was sort of like something went to sleep and I woke it up by turning the knob on the Duet. I haven't had this issue with previous versions of ppooll (l can't say for sure if it's since the overall 8.5 update, but I think so). Latest source code and Max. Thanks for your help!
The text was updated successfully, but these errors were encountered:
i dont have an apogee duet to test at the moment, but i can get my hands on one. does this happen with any other daw or just regular max (w/out ppooll)? i'm not sure but i remember hearing from someone that apogee devices have some issues with M1/later Mac OSXs (if that applies to you)
Thanks for the response. I've had my Duet for many years, use it almost daily with Ableton and Logic. This is the first time I'm encountering this issue. I don't have a Max license and only use it for ppooll so I couldn't tell you for sure if it's broadly related to Max, sorry about that.
I was using ppooll today for quite a while, and if I changed the volume on my audio interface (an Apogee Duet 2) after not doing so for a while, all of the sound would stop and I would get the spinning ball on my mac. Eventually, I could turn host@ on and off and sound would come back on. Very strange, it was sort of like something went to sleep and I woke it up by turning the knob on the Duet. I haven't had this issue with previous versions of ppooll (l can't say for sure if it's since the overall 8.5 update, but I think so). Latest source code and Max. Thanks for your help!
The text was updated successfully, but these errors were encountered: