Hi Markus Thanks for reminding me! I dispatched it on the to the main thread, and that seems to have fixed the issue. I was confident I wasn’t updating the UI off the main thread, but perhaps there was something somewhere. Is there a test case for this in auval?
Thanks peter From: Markus Fritze <[email protected]> Date: Monday, 22 January 2024 at 22:30 To: support (One Red Dog Media) <[email protected]> Cc: Oliver Larkin <[email protected]>, CoreAudio API <[email protected]> Subject: Re: Auval real time safety check Are you calling UI code (like drawing) from a non-main thread? That is a strong no-no, you can not do that! Never, ever! This leads to crashes. Markus > On Jan 22, 2024, at 11:20, support (One Red Dog Media) via Coreaudio-api > <[email protected]> wrote: > > H Oli > I don’t know if this is related. But.. > I have noticed a similar issue with JUCE and AUv3 when the plugin first > loads. There is some kind of thread conflict if the plugin and/or its editor > tries to notify the host that parameters have changed, i.e. in JUCE if > setStateInformation() calls setValueNotifyingHost() during the plugin startup > phase. Sorry I haven’t been able to figure out why or what that translates to > in the AU SDK as debugging AUv3 is very hard going. So, I’m currently > switching all my parameter handling to use a polling model. Massive refactor…. > Cheers > peter > From: Oliver Larkin via Coreaudio-api <[email protected]> > Sent: Friday, January 19, 2024 10:38:42 PM > To: CoreAudio API <[email protected]> > Subject: Auval real time safety check > Dear Core Audio folks, I've been experimenting with the relatively new > -real-time-safety flag on auval. > When I try and validate FilterDemoV3GenericUI (macOS) from this repo > https://github.com/apple/AudioUnit-Examples > > auval -v aufx fltg Demo -real-time-safety -stress 10 > > filterdemo-realtimesafety-test.txt > > I get a bunch of violations, the violations seem to relate to objc_msgSend() > but it looks like they might be in the AUv3 hosting code rather than the > plug-in itself. > > Here is the output of the above command: > > https://gist.github.com/olilarkin/98c87ae63485ea2c8fdf0f1ec3ecd1d0 > I get the same violations when testing iPlug2 AUv3s and I developed the > wrapper based on the apple sample code. > > Anyone know if this is fixable? > Thanks, > Oli > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Coreaudio-api mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/coreaudio-api/mfritze%40apple.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
