<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[RME User Forum — M-1620 Pro as Clock Follower]]></title>
		<link>https://forum.rme-audio.de/viewtopic.php?id=43208</link>
		<atom:link href="https://forum.rme-audio.de/extern.php?action=feed&amp;tid=43208&amp;type=rss" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in M-1620 Pro as Clock Follower.]]></description>
		<lastBuildDate>Sat, 18 Apr 2026 07:25:51 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: M-1620 Pro as Clock Follower]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=251046#p251046</link>
			<description><![CDATA[<div class="quotebox"><cite>MC wrote:</cite><blockquote><p>But they will in the forseeable future, by firmware updates that add such functionality. Please be patient, no date can be given.</p></blockquote></div><p>Great, thanks Matthias.</p>]]></description>
			<author><![CDATA[null@example.com (ramses)]]></author>
			<pubDate>Sat, 18 Apr 2026 07:25:51 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=251046#p251046</guid>
		</item>
		<item>
			<title><![CDATA[Re: M-1620 Pro as Clock Follower]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=251043#p251043</link>
			<description><![CDATA[<p>But they will in the forseeable future, by firmware updates that add such functionality. Please be patient, no date can be given.</p>]]></description>
			<author><![CDATA[null@example.com (MC)]]></author>
			<pubDate>Sat, 18 Apr 2026 02:41:32 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=251043#p251043</guid>
		</item>
		<item>
			<title><![CDATA[Re: M-1620 Pro as Clock Follower]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=251030#p251030</link>
			<description><![CDATA[<p>Network devices (those supporting either AVB or Dante) do not automatically follow the clock of the master.</p><p>See <a href="https://www.tonstudio-forum.de/blog/entry/108-clock-synchronization-background-rme-features-szenarios-en-de/">https://www.tonstudio-forum.de/blog/ent … ios-en-de/</a></p>]]></description>
			<author><![CDATA[null@example.com (ramses)]]></author>
			<pubDate>Fri, 17 Apr 2026 16:30:07 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=251030#p251030</guid>
		</item>
		<item>
			<title><![CDATA[M-1620 Pro as Clock Follower]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=251029#p251029</link>
			<description><![CDATA[<p>I know similar topics have been addressed here before, and the manual for the M-1620 Pro (<a href="https://docs.rme-audio.com/m1620/430-1c_sample_rates/">https://docs.rme-audio.com/m1620/430-1c_sample_rates/</a>) seems to suggest that this behavior is intended, but:</p><p>If my Madiface USB is set as clock master (clock source: internal) and my M-1620 Pro is set as clock follower (via optical or coax), when I change the sample rate in the Fireface USB Settings panel or within my DAW, the M-1620&#039;s sample rate won&#039;t change accordingly (though sometimes, depending on the change and as highlighted in the manual, the two devices will achieve a lock or even a sync anyway). This is particularly noticable when I switch from 48 kHz to 96 kHz or vice versa. Those are the main sample rates I use for my projects.</p><p>I believe this is different behavior from when I&#039;ve used ADAT or AES with other RME interfaces to sync a follower converter.</p><p>Is there any way around this such that I can let my DAW change sample rates on a per-project basis and not have to then manually change the sample rate on my M-1620 Pro?</p><p>And is this a particular limitation of the Madiface USB or does it apply to all MADI-capable RME interfaces?</p><p>Many thanks in advance.</p>]]></description>
			<author><![CDATA[null@example.com (AdamBier)]]></author>
			<pubDate>Fri, 17 Apr 2026 16:25:21 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=251029#p251029</guid>
		</item>
	</channel>
</rss>
