Skip to content
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

Closed
1 task done
de666 opened this issue Nov 15, 2024 · 4 comments · Fixed by music-assistant/server#1798
Closed
1 task done

Track seeking not working for subsonic provider #3184

de666 opened this issue Nov 15, 2024 · 4 comments · Fixed by music-assistant/server#1798
Assignees
Labels
bug Something isn't working Subsonic

Comments

@de666
Copy link

de666 commented Nov 15, 2024

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?

  • Yes

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

  1. start playing a track from a subsonic music provider
  2. slide the track progress bar at the middle of the track
  3. the track restarts playing from the beginning

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)

@de666 de666 added the triage label Nov 15, 2024
@OzGav
Copy link
Contributor

OzGav commented Nov 15, 2024

@khers

@OzGav OzGav added the Subsonic label Nov 16, 2024
@khers
Copy link

khers commented Nov 18, 2024

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

@OzGav OzGav added bug Something isn't working and removed triage labels Nov 29, 2024
khers added a commit to khers/server that referenced this issue Nov 29, 2024
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>
khers added a commit to khers/server that referenced this issue Dec 3, 2024
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>
khers added a commit to khers/server that referenced this issue Dec 3, 2024
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>
@github-project-automation github-project-automation bot moved this from NEXT to Done/verify in Music Assistant (V2) backlog Dec 4, 2024
@Hukuma1
Copy link

Hukuma1 commented Dec 20, 2024

Just tried the latest 2.3.4 with the fix and it's still not letting me seek? As soon as I click and scrub ahead it just restarts the song from the beginning (the UI shows the song playing in the middle, but the song restarts). Tried streaming to a native Google Home Mini device and an Airplay conversion of one as well (via AirConnect).

@de666
Copy link
Author

de666 commented Dec 21, 2024

Just tried the latest 2.3.4 with the fix and it's still not letting me seek? As soon as I click and scrub ahead it just restarts the song from the beginning (the UI shows the song playing in the middle, but the song restarts). Tried streaming to a native Google Home Mini device and an Airplay conversion of one as well (via AirConnect).

Same behaviour here, it seems the fix doesn't work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Subsonic
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants