+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions)
+--- Thread: Enable LUFS scan (/t-enable-lufs-scan)
Enable LUFS scan - pixel24 - 2024-06-20
Hello,
My entire collection is in OGG Vorbis. For this format, the normalization process is a bit different. Instead of re-encoding, as it used to be with MP3, a dB correction value is written into the file header in OGG.
This is the case for my entire collection. What exactly does the LUFS scan do, and how does the subsequent audio normalization of the library work? Does it even function with OGG?
with best
RE: Enable LUFS scan - TheDreadPirate - 2024-06-20
I'm not sure about the OGG headers, but for my FLACs and MP3s the audio normalization will put a dB value in the database entry for each song. And the client, Finamp usually in my case, then reads that dB value and adjusts the output accordingly. In the playback information in Finamp it will list the dB normalization value on the far right.
I'm not sure how Finamp would handle there being both an OGG header and a normalization value in the Jellyfin DB.
RE: Enable LUFS scan - pixel24 - 2024-06-20
Ok, I'll just test it out. It would be nice if Jellyfin supported using the correction value already present in OGG files, instead of performing a lengthy scan to determine it.
RE: Enable LUFS scan - Root785 - 2024-10-02
(2024-06-20, 04:43 PM)pixel24 Wrote: Ok, I'll just test it out. It would be nice if Jellyfin supported using the correction value already present in OGG files, instead of performing a lengthy scan to determine it.
Hi! did you test it? I'm not sure what this 'Audio Normalization' task do with 'Enable LUFS scan' on. My understanding it just store metadata of volume in internal DB so it could only be used by jellyfin native clients? Not using REPLAYGAIN_TRACK_GAIN etc standatd tags in file itself?
Thanks