+- 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: Browser AAC 5.1 Codec Compatibility (/t-browser-aac-5-1-codec-compatibility)
Browser AAC 5.1 Codec Compatibility - visualblind - 2023-11-10
*edit* I am wrong about everything I said in this post please discard. Sorry I don't know how to delete it.
From what I currently understand, none of the major desktop browsers (Chrome, Firefox, Safari) currently support AAC 5.1 channel audio codec natively. Even if you have all other compatibility pieces in place (container and codec), the end result is a "DIRECT STREAM".
I know on-the-fly audio codec conversion from AAC 5.1channel to AAC stereo is fast and end users don't really notice.
My issue with that is the constant local media writing (since practically everyone's media datastore will usually be networked). I'm using a cheap SSD for the local volume and I know the excessive writing will probably impact its lifespan. I know I could mount the transcoding directory to a datastore backed with HDD's, but imo that would be slower since most of us don't have enterprise class SANS for our local setup.
Is there anything else I could do besides pre-transcoding all my AAC5.1 audio streams to AAC stereo to ensure "DIRECT PLAY"?