-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: For cue-backed songs, clients are not aware of track changes. They just keep playing. #195
Comments
@yatli |
Sure: Relevant excerpts from
It's a When there should be a track change, nothing is being logged on the server. I also tried D-sub again, the client seems to be able to recognize a track change (sorry about the inaccurate initial report, must've been bad memory of me), but the track lengths are a bit off: the tail of the first track includes a bit of the following track, and when the track is being changed, it "rewinds" a little bit to the correct offset in the disc. Taking a guess, the TTA encoder command is ignoring the lengths? |
@yatli
|
Got it. Thank you! @kagemomiji do I need to refresh the cache on the server somehow? |
@yatli |
looks like it's working now:
Track 1 length is 9:00, 540s |
Todo: Write about this issue to document. |
#195 add troubleshooting for cue sheet tracks do not end
What happened?
First, thank you for this awesome fork! Years of efforts, multiple continuations, it's finally getting there!
I'd like to report an issue with clients, so technically this is not the problem of this fork, but that the clients don't know about CUEs. When a track is finished, the client is not aware, and continues to update the playback timer past the track's total length, without updating "now playing" to the next one. Audio playback works fine. Later content are being served in a gapless way.
Steps to reproduce
Say I have a CUE file backing up multiple tracks:
If a track is launched from the client, the offset will be calculated correctly,
so the playback works as expected.
However, when the track ends, the client continues to playback later content,
without updating the current playing track or reset the seekbar/track time etc.
For example:
I have experimented with Sublime (Linux) and D-sub/Subsonic (Android) and they behave more or less like this.
Version
11.1.1 (Stable)
Version Detail
11.1.1 release
Operating System
Linux, docker image built from source
Java Version
17.something I forgot
Database
Other
DB Detail
Docker default I'm not sure
Configuration paramter
Client problem. Config params not relevant here
Proxy Server
No response
client detail
No response
language
None
Relevant log output
No response
The text was updated successfully, but these errors were encountered: