You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wavepack files which contain 12 channels aren't played, nothing happens when clicking on a track. They are not being transcoded because they technically are compatible format, but downmixing to stereo would work (it work locally with ffmpeg).
Browsers don't widely support Wavepack in general i think. And probably even less if it's an exotic file with 12 channels.
So this falls in the same category as #1592 really:
Navidrome server understands the file, but the WebUI doesn't
So the only option is server-side transcoding of the file to a supported format (FLAC f.e.). Currently, you can only enable transcoding for all files or none.
There are plans to improve that with #351 and #2051 but it's not implemented as of now
Another "solution" or workaround is to use client apps that can play Wavpack. Supersonic on desktop can. It's possible Symfonium on Android might be able to as well but not sure. In any case, Symfonium is probably more advanced about its transcoding requests than the Navidrome WebUI - asking the server to transcode only if it can't natively play a format. (Note, I don't use Symfonium, I'm guessing a bit at its functionality, knowing it's a pretty advanced app)
So the only option is server-side transcoding of the file to a supported format (FLAC f.e.). Currently, you can only enable transcoding for all files or none.
I confirm that:
Version
0.51.1 (6d25322)
Current Behavior
Wavepack files which contain 12 channels aren't played, nothing happens when clicking on a track. They are not being transcoded because they technically are compatible format, but downmixing to stereo would work (it work locally with ffmpeg).
Expected Behavior
The file should be played or transcoded.
Steps To Reproduce
Environment
How Navidrome is installed?
Binary (from downloads page)
Configuration
Relevant log output
Anything else?
Code of Conduct
The text was updated successfully, but these errors were encountered: