Rewinding or fast-forwarding a track causes restarts or errors #3454
Comments
|
I'm sorry but issues aren't the place to ask questions. They are for reporting confirmed faults with MA and must include all of the information in the troubleshooting docs and the issue template. Why? Because we use these to track problems and prioritise them for rectification. This is hard enough with legitimate problems. So if you have a question then ask in the Discussions area or on Discord. |
|
@OzGav Thank you for your response. This is not a query (as it might have been on Discord), but rather a report. I have tested this functionality with other providers (Tidal/fileshare) and it works correctly. I have also tried clean, new installations from scratch, and SoundCloud continues to exhibit the same behavior. I apologize if any documentation or information is missing; I am not accustomed to reporting issues . |
|
the same behavior on snapcast players |
|
You ticked the box to say you read the troubleshooting docs which has a list at the bottom which you are to "include the following in ALL reports" I don't see how this isn't a query when you say
Here is a report which is similar but more importantly is good #3274 edit: note the desciptive title as well. edit2: If you edit your original post with all of the info then I can reopen this. The devs are super busy they don't have time to read through 20 posts of me trying to get all the info for a report hence why we ask for it upfront in the docs and issue template. |
|
I'll complete it with |
jbega
changed the title
Done, I hope that's enough. |
|
@robsonke what do you think? |
|
I have no clue but I noticed this behaviour too. I thought it had something to do with Sonos but later all worked fine using Spotify as source. I'll try to reproduce it, not having clear errors in the log doesn't make it easier. |
It doesn't happen with Tidal or FileShare (nor Spotify according to what I read), it seems to be only Soundcloud. Yamaha, years ago it was used like Sonos for some things (and it would make sense if it fails in one it fails in the other) but they have nothing in common with a Nest or a mobile with Snapcast If there's anything I can do to help |
|
@jbega, I'm able to reproduce it in my normal MA instance but I can't find any related error (like it just silently happens). Though not yet in my local development environment. |
I've spent the whole weekend trying to force it to give me an error, but I can't see any pattern or cause... sometimes it works fine, sometimes it's impossible, sometimes it's one device, sometimes it's another... Sometimes I can pause it, other times it clears the queue, other times it starts again... 2025-01-22 12:14:56.614 DEBUG (MainThread) [ffmpeg.12206] Detected (input) content type: mp3 (mp3,) *Player Sonido Estudio does not support pause, using STOP instead Sometimes I can fast forward or rewind, other times it clears the queue, other times it starts again 2025-01-22 12:18:46.405 DEBUG (MainThread) [music_assistant.webserver] Handling command players/cmd/seek ****** when work, according to the log, it seems that when it receives a seek command, instead of actually seeking, it stops and restarts playback from a different point, doesn't it? |
@robsonke Playing SoundCloud through Ma -If I pause from the original player in Ha (not the one created by Ma), it pauses and if I press play again, it continues from where it was. (no lines on Ma log) -If I pause using the physical button, it pauses and if I press play again, it continues from where it was. (no lines on Ma log) -If I pause it through the player's API > http://xxx.xx.xx.xx/YamahaExtendedControl/v1/netusb/setPlayback?playback=pause > it pauses and if I press play again, it continues from where it was. (no lines on Ma log) *I know it's best to use Ma's media players, I'm just providing this information in case it's useful. If it's irrelevant, please ignore it. **I also know that that issue was opened specifically for the seek function and not for pause, but the Yamaha integration doesn't support seeking and I can't perform this action through the API either (so I can only test using play/pause). Since it seems like I'm observing the same behavior with both actions, I'm sharing this information |
What version of Music Assistant has the issue?
2.3.6
What version of the Home Assistant Integration have you got installed?
2025.1.2
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?
The problem
I've noticed that I can't skip forward or backward within a track in soundcloud, sometimes work but normally, it resets the track . I'm wondering if this has been reported as a bug yet. I've tried searching for it but maybe I didn't use the correct keywords.
Tidal and fileshare works good
How to reproduce
I play a track on SoundCloud -> I scrub the progress bar backwards or forwards -> the track starts from the beginning
Music Providers
Souncloud
Player Providers
Yamaha (Ha integration)
Google Nest (Ha integration)
Snapcast
Full log output
log with 3 situations in this order:
move forward -> stop an clear queque
move forward -> work
move forward - Restart track
info.log
Additional information
I am using Music Assistant as an addon to HAOS on a Intel NUC. I have test on yamaha speakers and google nest (ha integration) and snapcast devices
I have tested this functionality with other providers (Tidal/fileshare) and it works correctly.
I have also tried clean, new installations from scratch, and SoundCloud continues to exhibit the same behavior.
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)
The text was updated successfully, but these errors were encountered: