Deployed 91a0419 with MkDocs version: 1.6.1

interfaces/udp-realtime/index.html

@@ -1865,10 +1865,21 @@
 </li>
 
         <li class="md-nav__item">
-  <a href="#udp-realtime" class="md-nav__link">
+  <a href="#udp-sound-sync-v2-v2" class="md-nav__link">
     <span class="md-ellipsis">
 
-        UDP Realtime
+        UDP Sound Sync (v2, v2+)
+      
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#udp-realtime-v1-and-warls" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        UDP Realtime (v1) and WARLS
 
     </span>
   </a>
@@ -2690,10 +2701,21 @@
 </li>
 
         <li class="md-nav__item">
-  <a href="#udp-realtime" class="md-nav__link">
+  <a href="#udp-sound-sync-v2-v2" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        UDP Sound Sync (v2, v2+)
+      
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#udp-realtime-v1-and-warls" class="md-nav__link">
     <span class="md-ellipsis">
 
-        UDP Realtime
+        UDP Realtime (v1) and WARLS
 
     </span>
   </a>
@@ -2748,7 +2770,12 @@ <h3 id="prismatik">Prismatik</h3>
 <h3 id="tpm2net">TPM2.NET</h3>
 <p>Supported in latest master and will be available in WLED 0.10.1.
 Please set the WLED broadcast UDP port to 65506 in Sync settings to enable receiving TPM2.NET data.</p>
-<h3 id="udp-realtime">UDP Realtime</h3>
+<h3 id="udp-sound-sync-v2-v2">UDP Sound Sync (v2, v2+)</h3>
+<p>This feature acts as a sound input and accepts pre-processed sound data on UDP port 11988 (user configurable). 
+Generating and sending this data can be done in multiple ways: 
+there is a <a href="https://github.com/Victoare/SR-WLED-audio-server-win">Windows application</a> or a lower-level <a href="https://github.com/netmindz/WLED-sync">C library</a>. 
+Learn more about this feature in the <a href="https://mm.kno.wled.ge/soundreactive/sync/">documentation of the MM-fork</a>, where it was originally implemented.</p>
+<h3 id="udp-realtime-v1-and-warls">UDP Realtime (v1) and WARLS</h3>
 <p>Additionally, WLED offers a way to directly drive the connected LEDs via UDP. The protocol is referred to as WLED <a href="https://github.com/scottlawsonbc/audio-reactive-led-strip">Audio-Reactive-Led-Strip</a> (WARLS), since the support of that project was its primary goal. However, it can also be used for other realtime applications like an ambilight.</p>
 <p>WARLS uses the same UDP port the notifier uses (default 21324, can be changed in settings).
 At the moment, the web UI will be disabled while active, the HTTP API, Alexa and button control remains functional.