Beta
The progress bar suddenly just stopped reporting back any playback stats at all and stayed at 0:00 (even though the track was audibly playing). Restarting playback entirely fixed the issue.
Phone
Navidrome
on
on
thekingpin
Your UPnP device did not return the necessary data. Not much I can do.
Ok weird, because, I haven’t had the issue before. Well thanks for checking anyways.
@Tolriq Kindly check new logs uploaded just now. The problem still exists. This time Im listening on my headphones and progress bar end is not showing anything. Will upload screenshot shortly.
Please also check logs named “thekingpin2”, here I have directly replicated the issue. First playback doesnt report any track end, but, when I skip forward/back to track the track end is reported correctly.
If it helps, I cannot seek the track while end is not reported. When I skip forward/back to the track, seeking becomes possible again. It’s almost as if the initial transcode is problematic until the track gets cached. I haven’t changed anything in the Navidrome transcode though.
Coming back to this again, I can confirm that the issue is only present when transcoding. When playing in original format, the track end is reported immediately.
@deluan I am currently on pr-5495, and, Im still having the broken pipe errors, as described in the issue here:
I see it was mentioned in fix(transcoding): place -ss before -i for fast input seeking by deluan · Pull Request #5492 · navidrome/navidrome · GitHub
As my issue is prety clearly related to the transcoding, I am wondering where the issue is exactly, and, how it can be fixed.
I use a custom transcode config but have also tried the default from consts/consts.go with same result, track end duration is not reported upon first playback of any song, and, also results in the track not being seekable, subsequent track plays begin to report track duration.
Please let me know if any other info is needed to assist.
