Re: Auval real time safety check
Re: Auval real time safety check
- Subject: Re: Auval real time safety check
- From: "support \(One Red Dog Media\) via Coreaudio-api" <email@hidden>
- Date: Mon, 22 Jan 2024 22:25:11 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=onereddog.com.au; dmarc=pass action=none header.from=onereddog.com.au; dkim=pass header.d=onereddog.com.au; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Su+SLCfgxlJDIu7UZV6oT9y5gilyfeA7dUt3v6cNYFA=; b=e0KxOAgnspLOxzr0RAvl90qEKiPthjPk90GDjmJiXOLX1QowH8C8IW57R+bp/gLmEc2qhEJIvbw+qG6f11tG3O5hdzYhqYb3MTQDCFCLnl94xYsc2+HMVwkWIPdTyMbbOuhu7BwuoBx549itWwgyK5BllIiTVLpmkwUZN6EkX4eggdqRA8x6rZblApWbmWZotfmuk50eovJRWUDjr/UB7d6wpQ13Yek0winU08fyp/4aEqMqk3lETQi3WviYqgMItgDRuXixh6qfkX0iAmvp8FNf0iWDPSW20jmOO73pE3z+zVx3IkGb4f2YyWU0lSMtDmr7AWMS0HQEme5cXuXvHA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Xi/Wo7rT2jMtizkG40RkZYTEtFyWp5vXvFfJWkMUBl5lrr4CwG4kxXOSXwD+jYTMTfG4q0XHcE/ZnLoA+7i5DSZB6nf0cTmi0yNBeEkCjBEk780SdyAfRrWlD4s4QSbBKdFo/8YA8NmNR70hiP991IJzPk0NGz+v6pSmrH05gs4KAYa018vKO96bLbkv5OKt4uUKY8mhuitkhp0Bivq4W1eSQ66Ii94+Mk5ON21Lja3diz6oEd+q03rQ2WRdS8elD1gkiGTfYqGBrRkAHi54nXVAAAIFZd5BlN28p2yYZukOXx5efL9cdCDpMEhuD5n0lzoX3Yh8eCvylwslvdpqmQ==
- Thread-topic: Auval real time safety check
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@hidden>
Date: Monday, 22 January 2024 at 22:30
To: support (One Red Dog Media) <email@hidden>
Cc: Oliver Larkin <email@hidden>, CoreAudio API
<email@hidden>
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@hidden> 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@hidden>
> Sent: Friday, January 19, 2024 10:38:42 PM
> To: CoreAudio API <email@hidden>
> 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@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden