-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Track seeking not working for subsonic provider #3184
Comments
I suspect what is happening here is that Navidrome is advertising that is supports the 'transcodeOffset' extension but it doesn't actually support it. I see something similar on Gonic when I am not transcoding (I cannot use the offset to ask for a mid location in a track when I am not transcoding). As a temporary measure I will probably add a configuration value that will control this instead of relying on the extensions reported by the server. But long term I would ask the Navidrome devs to support supplying an offset when requesting a stream even if no transcoding is happening. This request is outstanding for Gonic here: sentriz/gonic#483 |
Some Subsonic implementations advertise the ability to specify an offset when calling the stream endpoint. This offset should allow a user to seek by setting that value, however, at least on Gonic this value is only honored with transcoding. Allow a user to tell the subsonic provider that their server is broken and provider seek should be used instead. Fixes: music-assistant/hass-music-assistant#3184 Signed-off-by: Eric B Munson <eric@munsonfam.org>
Some Subsonic implementations advertise the ability to specify an offset when calling the stream endpoint. This offset should allow a user to seek by setting that value, however, at least on Gonic this value is only honored with transcoding. Allow a user to tell the subsonic provider that their server is broken and provider seek should be used instead. Fixes: music-assistant/hass-music-assistant#3184 Signed-off-by: Eric B Munson <eric@munsonfam.org>
Some Subsonic implementations advertise the ability to specify an offset when calling the stream endpoint. This offset should allow a user to seek by setting that value, however, at least on Gonic this value is only honored with transcoding. Allow a user to tell the subsonic provider that their server is broken and provider seek should be used instead. Fixes: music-assistant/hass-music-assistant#3184 Signed-off-by: Eric B Munson <eric@munsonfam.org>
Just tried the latest |
Same behaviour here, it seems the fix doesn't work |
What version of Music Assistant has the issue?
2.4.0b4
What version of the Home Assistant Integration have you got installed?
2024.11.4
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?
The problem
Using the subsonic (latest version of Navidrome) as music provider.
When seeking the track using the track progress bar, the progress bar itself slides correctly and also the track time apperently increases correctly but the listening restarts from the beginning of the track instead of jumping forward, despite the progress bar and the time indicator keep going on as the seeking was made correctly.
How to reproduce
Music Providers
subsonic
Player Providers
slimproto
snapcast
Full log output
no errors related in the logfile
Additional information
Not 100% sure the issue is related only to the subsonic provider, didn't try with the filesystem one but I recently switch to the subsonic provider (from a local filesystem provider) and I don't seem to remember this behaviour with the local filesystem provider.
What version of Home Assistant Core are your running
2024.11.1
What type of installation are you running?
Home Assistant Container
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)
The text was updated successfully, but these errors were encountered: