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 (also with force seek enabled) #3464

Closed
1 task done
de666 opened this issue Jan 16, 2025 · 6 comments
Closed
1 task done

Comments

@de666
Copy link

de666 commented Jan 16, 2025

What version of Music Assistant has the issue?

2.3.6

What version of the Home Assistant Integration have you got installed?

No response

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.
Same behaviour with force seek provider option enabled

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 (Navidrome)

Player Providers

  • slimproto
  • snapcast

Full log output

no errors related in the logfile

Additional information

Opened after verifying the fix for #3184 didn't work

What version of Home Assistant Core are your running

2025.1.2

What type of installation are you running?

Home Assistant OS

On what type of hardware are you running?

Generic x86-64 (e.g. Intel NUC)

@de666 de666 added the triage label Jan 16, 2025
@OzGav
Copy link
Contributor

OzGav commented Jan 16, 2025

@khers

@khers
Copy link

khers commented Jan 16, 2025

This should be fixed in the beta.

You may need to set the option for "Force player provider seek" in the subonsic provider configuration if Navidrome advertises that it support the transcodeOffset parameter but does not honor it. (If seeking doesn't work for you in the beta, try enabling that option)

@de666
Copy link
Author

de666 commented Jan 16, 2025

#3184 (comment)

@khers
Copy link

khers commented Jan 16, 2025 via email

@OzGav
Copy link
Contributor

OzGav commented Jan 18, 2025

@de666 please try the beta

@de666
Copy link
Author

de666 commented Jan 18, 2025

@de666 please try the beta
It works
🙏

@de666 de666 closed this as completed Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants