Currently playing track often not updated

BinarySlave · March 14, 2024, 11:36am

I’ve been using Volumio with a RaspberryPi 4 Model B for five or six months.

I primarily stream via a linked Qobuz account.

I’ve noticed the name of the currently playing track often gets stuck once the track has ended and a new one has started. This usually happens on the first couple of tracks to be played from an album.

For example, I’ll start an album, once track 1 has ended, track 2 starts but Volumio (via web browser, android app or ios app) still shows the track 1 name. Generally, when track 3 starts, it sorts itself out for the remainder of the album.

This is particularly frustrating as I like to ‘scrobble’ all my listens to last.fm, and have ended up with a lot of double/missing scrobbles as a result.

Any ideas if this is a bug? I’ve searched and can see this might have been an issue a few years ago, but was fixed.

Log here: http://logs.volumio.org/volumio/s3QhoyI.html
This should demonstrate exactly what I describe. Started an album, first track played to completion. Second track played but retained the name of first track. It then sorted itself out for the third track.

Many thanks in advance.

Vennesch · March 14, 2024, 12:14pm

I notice the same behaviour quite often with the native ui and app. If I look at the ‘‘third party’’ app Volumio Control it displays the right information

Wheaten · March 14, 2024, 12:16pm

Volumio Control see:

BinarySlave · March 14, 2024, 12:51pm

Thanks

I just tried Volumio Control and it does exactly the same thing. The second track played still shows the name of the first track. Maybe it’s a Qobuz thing.

Wheaten · March 14, 2024, 1:33pm

that is what I was expecting. Both apps follow the web UI information from Volumio.

@DED
Any suggestion on this?

patrickkfkan · March 14, 2024, 6:40pm

I suspect this to be the same issue raised a while ago regarding the YT Music plugin. I tracked this down to a bug in Volumio’s “statemachine” that affects plugins that prefetch tracks and call setConsumeUpdateService('mpd', true) – which seems to be what Qobuz is doing.

If it’s of any help, here’s the description of the bug and workaround I implemented in the YT Music plugin:

github.com

patrickkfkan/volumio-ytmusic/blob/94bc70a543b845ef40fab7df5ff700c9b482eee7/src/lib/controller/play/PlayController.ts#L494


      
                    }
                  }
                };
                return `ytmusic/${ViewHelper.constructUriSegmentFromView(targetView)}`;
              }
          
              return null;
            }
          }
          
          /**
           * Given state is updated by calling `setConsumeUpdateService('mpd', true)` (`consumeIgnoreMetadata`: true), when moving to
           * prefetched track there's no guarantee the state machine will store the correct consume state obtained from MPD. It depends on
           * whether the state machine increments `currentPosition` before or after MPD calls `pushState()`. The intended
           * order is 'before' - but because the increment is triggered through a timer, it is possible that MPD calls `pushState()` first,
           * thereby causing the state machine to store the wrong state info (title, artist, album...obtained from trackBlock at
           * `currentPosition` which has not yet been incremented).
           *
           * See state machine `syncState()` and  `increasePlaybackTimer()`.
           *
           * `PrefetchPlaybackStateFixer` checks whether the state is consistent when prefetched track is played and `currentPosition` updated

Darmur · March 14, 2024, 6:47pm

@volumio please see the above post from @patrickkfkan

Matthew_K · March 21, 2024, 9:23am

I hang on here. I have the same issue when playing from Tidal.
Started with the update to system version 3.xxx.
I use the access via webbrowser, manifest UI.
Not happen when playing from NAS.
Assumed all this months, that this must an issue for me alone, must be seen by others as well. Thank you for bringing in the issue here.
Matthew