Closed unhammer closed 2 months ago
This looks a lot of like this issue report in my client https://github.com/dweymouth/supersonic/issues/401 which was happening with Ampache. In the ticket there is examples for the HTTP headers that Navidrome returns when serving a transcoded file and a raw file, both which work well with MPV, compared to the improper headers Ampache was returning. Perhaps Gonic is returning similarly improper HTTP headers?
oh wait you're just seeing 404s, that's a bit different
looks like it's not a gonic issue right? can i close in favour of #538
gonic version: 16.4 from AUR arch linux
15.2 was working fine, but after upgrading to 16.4, I first got errors that I had to add a transcoding profile since dsub requested maxbitrate (dsub would just "skip" the song as if it was 0 seconds long), so I added transcode
*
client to ogg (also tried mp3) to my user and then I seein logs as if it's sending data, but dsub just hangs with
Downloading – 0 B
. (Is that http code 0?)This is when I've set maxbitrate 112 in dsub to force transcoding. If I change it to infinite max, it still hangs, but logs now say
(Is that http code 404?)
I tried calling mpv with an url like subsonic.el does, and then I get
Failed to recognize file format. Exiting... (Errors when loading file)
if I set transcoding to mp3. If I turn off transcoding, I get[ffmpeg] https: HTTP error 404 Not Found Failed to open https://…
(so yes, it seems it's actually responding with 404 instead of serving the raw file)