Thanks for writing in and for sharing your report! From a fresh diagnostics Roon Server report, we can see the loop commands are being reported as coming from the endpoint device (your Lyngdorf TDAI-1120), not from the Roon Server machine:
[raatclient] GOT [4] {"status":"Success","control":{"button":"loop_all"}}
[zone] Lyngdorf received transport control from endpoint integration: loop_all
A few areas to check:
If you also control the TDAI-1120 through the Lyngdorf Remote App (iOS/Android), check whether it has a repeat/loop mode enabled.
Disable repeat/loop inside the Lyngdorf app to see if it stops sending loop_all to Roon.
Check that your TDAI-1120 firmware is fully up to date (Lyngdorf does issue stability updates).
Consider a factory reset of the TDAI-1120, then re-add it to Roon.
We’ll be on standby for your reply and results - thank you!
Hello @benjamin
Thank you for the log data. I was using Lyngdorf Remote in the past and am using the My Lyngdorf app now - but only for configuration, switching inputs or volume adjustments. I don’t think I’ve used the repeat button, except for maybe when I just got the amp. The ‘loop all’ issue seems to occur pretty much at random, only when playing music from Roon.
I’ll do some more check-ups when the issue reoccurs.
I’m guessing it’s likely the issue will re-occur if I perform a factory reset and then restore my back-up?
We’ve captured several instances in logs where the Lyngdorf Zone sends a burst of changes to both shuffle and loop within a single second.
Unless there’s accidental pressure on a tacticle switch of a remote control (someone sitting on it, etc), these commands from the Zone are erroneous.
The evidence suggests these commands don’t originate within RoonServer - they are transport commands sent from the Lyngdorf endpoint itself, originating within its Roon/RAAT implementation.
Have you reached out to the manufacturer to report this symptom?
We’ll investigate internally in the meantime and let you know our results.
Hello @connor
I can confirm it’s also occured with shuffle. This morning it was a ‘loop 1’ when playing a single track - and no remote in sight I’ll get in touch with Lyngdorf. Interested in what the results are from your side!
To confirm, we have requested the diagnostic data from your server, but it seems to be offline.
Would you kindly bring it back online and let us know here?
Thanks for that! We’re seeing some odd RAATServer-related errors that could be playing a role in the behavior you’re seeing (around playback stopping at least) - let’s see if refreshing your RAATServer helps.
You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings -> Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:
Hello @benjamin
When I logged in to my Roon server, I noticed Windows displayed a firewall notification - it had tried blocking the RAATServer. Could this be related? I’ve followed your steps. Could you check whether this changed anything?
My Audio Tab has been reset, but all zones are still there as before. Only the icon for my Lyngdorf TDAI-1120 has now defaulted to a headphone icon
When you recreated the RAATServer folder, it reset your audio device settings. That’s why the Lyngdorf TDAI-1120 has reverted to the default headphone icon. You can update the icon again by going into the Device Setup menu for that zone.
Also, Roon should normally be listed as an exception in your Windows Firewall by default. You can double-check the setup here: Roon Firewall Help
Please give that a try and let us know if you’re still seeing any odd behavior.
Thank you for following up. Unfortunately, “a few minutes ago” isn’t quite enough for us to pinpoint the issue in the logs. Could you please share the exact timestamp (including date and time) when the random pause occurred, or the track name that was playing at the time?
Also, just to confirm, could you let us know your time zone so we can align the logs correctly?
This information will help us narrow down the cause and move forward with the investigation.
Sorry for the spam, but it’s happened again - so now constantly when queueing tracks. This time with the minced oath album. All tracks were already duplicated in queue straight away.
I will be off the grid for about two weeks starting tomorrow - will we be able to pick up this thread after?
From the logs, we can confirm that the loop settings are coming from the Lyngdorf device during the playback of the song. We clearly see the command SetLoopLoopOne.
We already escalated it with our partner’s team to Lyngdorf. Please feel free to reach out to them from your side.
I’ll get in touch with Lyngdorf. Interested in what the results are from your side!
