24
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Nov 2023
24 points (96.2% liked)
Firefox
4015 readers
27 users here now
A community for discussion about Mozilla Firefox.
founded 1 year ago
MODERATORS
As someone else said, it's a bit hard to diagnose without the original file, or at the very least hearing what the distortion sounds like. Chrome does appear to support more wav formats than Firefox according to the listed support on their respective sites. Firefox supports 8 and 16 bit PCM wav files, and chrome supports 32 bit wav as well.
Jellyfin may also be doing conversion of the wav file since streaming wav can use a lot of bandwidth, there's a chance it's converting to a different format for chrome than it does for Firefox.
sorry, I downloaded the original file from here: https://soundcloud.com/dankmus/c-o-m-i-n-g-u-p-m-i-l-h-o-u-s-e/s-8xNXA
I did share link to a video on imgur that shows the difference between the warped audio and the original audio.
As for conversion, Jellyfin converts every lossless audio file to 320kbps AAC if I'm not mistaken.
Regardless, thanks for the informative reply. I'll just listen to it offline for now
Interesting. Unfortunately I'm away and unable to test the file on my own Jellyfin server. But it is a relatively high quality wav file, if for some reason Jellyfin isn't transcoding it, it's big enough to potentially cause that studdering just trying to stream that much data that fast (although that could also potentially happen if Jellyfin is transcoding it on the fly and your server hardware can't keep up).
One suggestion I could make would be to try to convert the file to flac manually, and see if that makes a difference. You shouldn't lose any quality doing that, and between the smaller file size and different format Jellyfin might treat it differently enough that it could work.