So I’m seeing this issue a lot, particularly when I cast to Chromecast. A track will reach the end and then the last 40% or so will start playing again. I’m seeing this across all my devices and even on family member devices and accounts. What’s perplexing is that I’m casting from a playlist that is cached, so it shouldn’t be an issue if it’s not when not casting and somehow. Sometimes though, even non cached tracks repeat
Logs:
Upload description: sabreW4K3
Additional information:
Reproduction steps:
It’s probably not in these logs as I’m presently not casting. I shall get some casting logs in the next hour and hopefully you can see it there. But this has been happening for over a year. It’s not a new thing.
Because when I told you last time what happened, you fobbed it off as a Navidrome issue, so I made sure it preferred playing from the offline cache as it’s a problem that doesn’t go away and I really wanted to provide enough data to ensure you could see it.
I’m not sure how the logs look, but if you look at the last song played in full, the issue exhibits itself there.
Where do you get those files ? Gives different duration on different players, is the cause of the Chromecast issue and can’t be opened in Audacity and other tools.
Nothing else has the issue. Only Symfonium. I uploaded the file again, this time downloaded directly from my NAS rather than via Symfonium. It’s showing an identical checksum.
What questions? I beg you please remain professional. I’m trying to report a bug that has long plagued me.
If long debug logs are an issue, that’s surely a problem on your side, no? I’m not uploading logs and saying, “oh it’s in there somewhere”. I’m uploading the logs when it’s the happened to the last song or at most the one before the last song.
In the last debug log, the problem didn’t happen via Chromecast, but via my Bluetooth headphones. Something I would’ve hoped the debug logs were capable of demonstrating.
I don’t understand why I’m getting hostility for trying to get a bug fixed in an app I paid for? Particularly when I’m not even demanding a fix, I’m literally just here trying to help identify it. Initially you fobbed me off with it being a Navidrome issue, so I made sure the songs were served via cache. Then you imply the issue is the source of the files and so I provide you with a track via a different source all together and you start acting hostile. It’s weird. Surely we should both want to identify what’s happening here?
How am I supposed to provide a video of a random problem?
I can play a track once and it’ll show the issue, the same track will play again via another playlist and it’ll do the repeat thing. There’s no pattern or discernable logic to it, hence why I’ve just had my debug mode on for so long hoping that it can provide a clue to the issue that I’m failing to notice.
You say you are seeing it a lot. And I can play a track once and it’ll show the issue, the same track will play again via another playlist and it’ll do the repeat thing. means you see it all the times But probably a typo.
The reverse works too how am I supposed to fix the issue only you have if you have no reproduction steps?
Again when casting to Chromecast Symfonium is not involved in the rendering it’s all done by Google code, logs shows no actions from Symfonium and since it can happen when casting directly from the server there’s even less Symfonium action that could corrupt the file in the middle … (But the corrupted file above had the same MD5 from Symfonium or Navidrome so was in all cases not modified).
So there’s actually 99,99999% chances that this is not a Symfonium issue.
