Unexpected 'loop all' added to play queue in Roon (ref#I8GELR) [Roon Investigating]

Support
42

Hello @connor
It was the zone “Laptop” and it was ‘loop’ that was set. I’m not using any other audio software on any device, currently. I’ve made sure over the past few weeks that BT is turned off on most devices if I don’t need it. Today, I did turn BT on on my laptop to connect to a BT speaker. I think the Lyndorf amp was still turned on when the issue occured.

In regards to the log: if the timestamps are correct, that was when I was listening on the Lyngdorf again. I didn’t notice anything, but if I’m reading the logs correctly, that makes sense :slight_smile:

43

Hi @eye,

We weren’t able to see anything in relation to your Laptop receiving similar commands. Are you able to reproduce the behavior again and share a more specific timestamp? We’d be happy to take another look.

44

Hello @benjamin I haven’t been able to reproduce this. Do you have any updates on the investigation?

45

@benjamin Yes, happening again at this moment. It’s on replay without touching the button…

46

Hi @eye,

No updates to share yet - our partners team still has a ticket in for investigation. Please note that progress will likely be on the slower side, you have my apologies here.

@RM_Kamphuis thanks for sharing - we were able to see the timestamp you’ve mentioned:

11/06 ... GOT [4] {"control":{"button":"loop_all"},"status":"Success"}
11/06 ... Lyngdorf received transport control from endpoint integration: loop_all
11/06 ... Lyngdorf received transport control from Lyngdorf TDAI-3400: loop_all
11/06 ... SetLoopLoop

GOT [4] {“control”:{“button”:“loop_all”}} – This is Roon receiving confirmation from the device that the loop_all command has been successfully acknowledged.

The log suggests again that the loop command originated on the device, not Roon. Roon is simply reporting that the device changed its loop state and updating its internal zone state. If Roon had initiated it, we’d see a SENT {… “control”: {“button”:“loop_all”}} line before the GOT/received confirmation.

We’ll continue to keep you updated as soon as any new information is shared our way. If the thread closes before that happens, we’ll manually re-open it to share any updates/next steps. Thanks for the long, ongoing patience here! :folded_hands:

47

Thanks @benjamin for this update. I have also shared this info with my contact at Lyngdorf. Hopefully a fix can be implemented soon.

48

@benjamin Could you elaborate a little why progress will be slow? Is this on Roon’s side or on Lyngdorf’s side? And is there anything I can do to speed this up a little?

49

@benjamin Roon is investigating but still think it’s Roon related. Hope you guys can work on it together…

50

I’ve been running into the issue constantly over the past week.

@benjamin I’ve just run into something I haven’t had/noticed before: I started playing an EP earlier today. When leaving the house, I asked my partner whether a loop command had been added to the play queue - it hadn’t. When returning home, I resumed the play queue (mid track) with the pause/play button and I saw the loop all button being activated in Roon.

Timestamp: 21:25 GMT+2, TRACK Burient Down or Gradofff Burn by Roel Funcken

51

Hi @eye,

Thanks for the fresh timestamp! After reviewing logs, I see when you pause playback:

11/11 11:45:58 Trace: [Lyngdorf] [Enhanced, 24/44 QOBUZ FLAC => 24/44] [100% buf] [PAUSED @ 1:02/3:22] Gradofff Bolm - Roel Funcken

And then, from 11:45 to 12:33, there is no activity from your Roon Server, until a seemly random:

11/11 12:33:29 Trace: [Lyngdorf TDAI-1120 @ 192.168.129.17:58952] [raatclient] GOT [4] {"status":"Success","control":{"button":"shuffle_off"}}
11/11 12:33:29 Trace: [zone] Lyngdorf received transport control from endpoint integration: shuffle_off
11/11 12:33:29 Trace: [zone Lyngdorf] Lyngdorf received transport control from Lyngdorf TDAI-1120: shuffle_off
11/11 12:33:29 Trace: [Lyngdorf TDAI-1120 @ 192.168.129.17:58952] [raatclient] GOT [4] {"status":"Success","control":{"button":"loop_off"}}
11/11 12:33:29 Trace: [zone] Lyngdorf received transport control from endpoint integration: loop_off
11/11 12:33:29 Trace: [zone Lyngdorf] Lyngdorf received transport control from Lyngdorf TDAI-1120: loop_off

Roon received a message from the Lyngdorf saying “shuffle/loop was turned off,”

Outside of that, we see the same behavior later on, at around 9PM:

11/11 21:21:59 Trace: [zone Lyngdorf] PlayPause
11/11 21:21:59 Trace: [zone Lyngdorf] Unpause
11/11 21:21:59 Trace: [zone Lyngdorf] Selecting Source state=Paused
11/11 21:22:00 Trace: [Lyngdorf TDAI-1120 @ 192.168.129.17:58952] [raatclient] GOT [4] {"status":"Success","control":{"button":"shuffle_off"}}
11/11 21:22:00 Trace: [zone] Lyngdorf received transport control from endpoint integration: shuffle_off
11/11 21:22:00 Trace: [zone Lyngdorf] Lyngdorf received transport control from Lyngdorf TDAI-1120: shuffle_off
11/11 21:22:00 Trace: [Lyngdorf TDAI-1120 @ 192.168.129.17:58952] [raatclient] GOT [4] {"status":"Success","control":{"button":"loop_all"}}
11/11 21:22:00 Trace: [Lyngdorf TDAI-1120 @ 192.168.129.17:58952] [raatclient] GOT [5] {"status":"Success","controls":{"volume":{"max":-1.0,"type":"number","min":-99.9,"info":{},"step":0.1,"mute":false,"value":-40.0},"source":{"info":{},"is_standby_supported":true,"value":"selected"}},"action":"Changed"}
11/11 21:22:00 Trace: [Lyngdorf TDAI-1120 @ 192.168.129.17:58952] [raatclient] GOT [3975] {"status":"Success"}
11/11 21:22:00 Trace: [zone] Lyngdorf received transport control from endpoint integration: loop_all
11/11 21:22:00 Trace: [zone Lyngdorf] Lyngdorf received transport control from Lyngdorf TDAI-1120: loop_all

Roon logs that it received these state updates from the Lyngdorf.

We’ll keep you in the loop as things progress, thank you!

1 Like