Playback stops when playing long tracks/DJ Mixes

Issue description:

While seeking in a track, the playback will continue where the seek cursor stopped (let’s say the middle of the track), but the cursor itself goes back to the beginning of the track. This is in the expanded now playing view.

Logs:

Upload description: Issues when playing DJ Mixes / long tracks

Additional information:

 
server is Navidrome
 

Reproduction steps:

 
Start playback in Symfonium of a 2h track;
Playback always stops at around 13 minutes. The round icon animation around the play button spins. Eventually playback restarts from the beginning of the track.
 

Media provider:

Subsonic

Screenshots:

     

Check your proxy or navidrome logs.

2024-07-19 09:05:24.108 Error/MusicPlayer: Error reading source (0), retrying [g00.e0: stream was reset: PROTOCOL_ERROR]
2024-07-19 09:05:24.608 Error/MusicPlayer: Error reading source (1), retrying [g00.e0: stream was reset: PROTOCOL_ERROR]
2024-07-19 09:05:25.614 Error/ExoPlayer: internalError [eventTime=42932.98, mediaPos=669.40, window=0, period=0, loadError
  o4.w: g00.e0: stream was reset: PROTOCOL_ERROR
      at q4.b.u(Unknown Source:55)
      at kg.d.u(Unknown Source:93)
      at o4.m.u(Unknown Source:5)
      at kg.b.u(Unknown Source:28)
      at o4.e0.u(Unknown Source:12)
      at p4.e.u(Unknown Source:55)
      at o4.d0.u(Unknown Source:2)
      at i5.l.h(Unknown Source:10)
      at i5.l.a(Unknown Source:30)
      at y5.e.b(Unknown Source:96)
      at y5.d.m(Unknown Source:157)
      at d5.f0.a(Unknown Source:250)
      at g5.l.run(Unknown Source:34)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
      at java.lang.Thread.run(Thread.java:1012)
  Caused by: g00.e0: stream was reset: PROTOCOL_ERROR
      at g00.x.L(Unknown Source:64)
      at d00.g.L(Unknown Source:8)
      at lv.a.read(SourceFile:15)
      at q4.b.u(Unknown Source:34)
      ... 15 more
]

You’re right, sorry about that. The issue happens also on the Navidrome web interface, only when transcoding. I’ll see how I can fix the issue on the Navidrome side. No pertinent log entries appears in the Navidrome logs.