<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Modartt user forum - Modartt audio units not registering with auval on macOS Tahoe]]></title>
		<link>https://forum.modartt.com/viewtopic.php?id=12688</link>
		<description><![CDATA[The most recent posts in Modartt audio units not registering with auval on macOS Tahoe.]]></description>
		<lastBuildDate>Mon, 20 Oct 2025 20:47:12 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Modartt audio units not registering with auval on macOS Tahoe]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=1004398#p1004398</link>
			<description><![CDATA[<p>Meanwhile it seems the problem has resolved itself. I&#039;ll describe what&#039;s happened, in case anyone ever encounters a similar problem and comes across this post.</p><p>I&#039;m not sure what exactly fixed it, but I spent a few hours this afternoon downloading Blackhole and trying to set up an alternative way to use it to access the Pianoteq audio buffer. This involved a lot of setting up aggregate and multi-output devices in Apple&#039;s Audio MIDI Setup utility. None of that worked for what I needed, but in the end, when I went back to check on `auval` again, I&#039;m finally seeing that the Modartt entries are recognized/registered properly: </p><div class="codebox"><pre><code>$ auval -a | grep aumu
aumu Ot2q Mdrt  -  Modartt: Organteq 2
aumu Pt9q Mdrt  -  Modartt: Pianoteq 9</code></pre></div><p>In all that messing around, something fixed it (by updating a cache somewhere maybe?) but I can&#039;t be sure what it was.</p>]]></description>
			<author><![CDATA[null@example.com (kawai_user3535)]]></author>
			<pubDate>Mon, 20 Oct 2025 20:47:12 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=1004398#p1004398</guid>
		</item>
		<item>
			<title><![CDATA[Modartt audio units not registering with auval on macOS Tahoe]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=1004387#p1004387</link>
			<description><![CDATA[<p>I&#039;ve been using <a href="https://github.com/myersm0/midi-audio-streamer">a swift application</a> to capture audio buffer output from Pianoteq for additional processing (such as custom visualization). This was working great on the prior version of macOS, but with the new macOS 26 (Tahoe) I&#039;m running into some problems. It seems that the Pianoteq (8, 9) and Organteq 2 audio unit components are no longer properly registering with the macOS Audio Unit system.</p><p>To be specific:<br />- system-level Audio Unit validation fails<br />- the auval command line tool cannot validate the components</p><p>Some observations towards debugging this:<br />- Running `auval -a | grep -i mdrt` returns no results, so it seems the OS is not seeing any Modartt components at all.<br />- Logic Pro can still load and use Pianoteq and Organteq<br />- The component files exist in the correct locations:<br />&nbsp; &nbsp; - /Library/Audio/Plug-Ins/Components/Pianoteq 9.component<br />&nbsp; &nbsp; - /Library/Audio/Plug-Ins/Components/Organteq 2.component<br />- Running `auval -v aumu Pt9q Mdrt` produces:<br /></p><div class="codebox"><pre><code>ERROR: Cannot get Component&#039;s Name strings
ERROR: Error from retrieving Component Version: -50
FATAL ERROR: didn&#039;t find the component</code></pre></div><p>My best guess is that this is a compatibility issue with macOS 26&#039;s Audio Unit registration or discovery mechanism. The components appear to be properly signed and Logic Pro can still use them, but they&#039;re not being registered with the system&#039;s Audio Unit component registry.</p><p>Thanks in advance if anyone knows a fix for this or can suggest an alternative way to access the audio buffer.</p>]]></description>
			<author><![CDATA[null@example.com (kawai_user3535)]]></author>
			<pubDate>Mon, 20 Oct 2025 14:39:15 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=1004387#p1004387</guid>
		</item>
	</channel>
</rss>
