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 10:20:19 +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=LXcEditexZTLAtEhM1gvfsbjTcfzs7TFKy9Wlx4jfd0=; b=g8GeFl/vDMJkCb1vlPLXiARhBVJXetGnEMnfmtK8pVuHkFLOTf3BUSgYo3BZ75Tm/HsHrUuJHSAk6K09wrTNv0qVBcFE9utX63RkRaKl3NNLH+frYHoRjfa7NOCrYKcqfcWExlVNH6tZ1pAmT6LvVA5FhtS2OTuPyehMwAZNUkZlkLLKyq0KKlX+JRBaHlJN9GgseY4AhdJc+C2eNsol5YLiD88/CCndjuW2xcCIFnqhlytDjypKOmq6leTCiAIYnMDyZ08BehccCR7St9gXexCJAtdQAG6+9KzKqi28BdaKP2/cHDOAE3Q2X1S55DVAAbg92wysUsBnK4n8RRNxuw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dQWlDRVSp4mmfv6uqFAqPij8OfVtkeMljRcc5BDrnw/YUtS0Y35Ia0+atwBDiS7yyJgJd+HOoVIR/KzL+2Wus/3Gw1f2ue547ZzZpTgr/Q+HCISDj9iOAFaqKQBVqSKo0z1xtAndtgzgvknA44FnPaBRzfZTJazU3PaPxqdwQ6RBH9wvsGFV5aAL6GoPwGAr6j5s5EuV3TBmqNKHUqGacriuKrYuUvOksep50c3tbtgRXhJno85/3nd53+SDxr3xj46ynmnJDfnTxSdtcEqcWH1fGnRYo9wGEfm16ClUOiFjew3TEjJAGEtiRtHHg6JkS0yXKnYCDDQxpUSGKyXo1Q==
- Thread-topic: Auval real time safety check
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