Search the Community

I have multiple users reporting no audio when playing some content on their Samsung TVs. I've noticed that this seems to only occur when the Samsung TV users are playing audio under the EAC3 codec. I have posted the the ffmpeg transcode log from one of the streams with no audio on the Samsung TV with the following model number (UN65RU7100FXZA). ffmpeg-transcode-74d42665-51ab-46bc-8340-904a511ab976_1.txt

I want to ask you, if you can please add a configuration option to force my Emby for Windows server to always use HLS streaming. At the moment my only way to force HLS streaming is to enable the "Convert Unsupported Audio" setting in the Android TV client. And I also have to have all the movie and series files with the default audio track with the E-AC3 or DTS codec. This way I force my Emby server to send HLS streams, instead of HTTP. The problem that with this method my Emby server also transcodes the E-AC3 or DTS audio track to AAC. If you add a configuration option in the Emby server to force the server to use HLS streaming, then it doesn't transcode the audio track unnecessarily. HLS transmission in my case solves the problem on my favorite and main television, the problem of constant jumps and jerks in the images. And since the latest version of the client for Android TV has become obsolete due to playback problems with DV and HDR10, and the client for Android 3.2.92 I don't have any option to force the HLS streaming. Thanks, greetings.

I've noticed that both my Chromecast v2 and Ultra are happy to direct play multi-channel audio encoded using either Dolby Digital (AC3) or Dolby Digital Plus (EAC3). Anything else (Dolby True HD, Atmos, DTS, DTS-MA, DTS-X) gets transcoded to Dolby Digital at 384 kbit/s. I'm very impressed with the way Emby handles this - it's even smart enough to transcode EAC3 to AC3 when I turn off the AV receiver (and it's just the TV doing the audio decoding). I'm less impressed that it needs to do this at all for the Chromecast Ultra: why do Google think it's OK to market it as 4K HRD capable and yet only support these two codecs? It's particularly bad when DTS gets transcoded to AC3 (one lossy early 90s format to another). Dolby claim that DD+ is up to twice as efficient as old DD and Netflix are now streaming in DD+ at 640 kbit/s ("the point at which additional quality is imperceivable"). I decided to experiment using Emby's version of ffmpeg on my Synology NAS (a DS918+ running a Celeron J3455). DTS to AC3 at 384k vs. DTS to EAC3 at 640k. I had to set avoid_negative_ts to its default value of "auto" for the EAC3 transcode - Chromecast won't direct play EAC3 streams with negative timestamps. I was concerned that the EAC3 conversion might require more CPU time, but if anything it's faster. The conversion logs are attached. I won't claim to have the best equipment or ears (MP3 at 320k is fine by me), but I can hear the difference. The Mad Men opening theme (test file I used) sounds better to me in the EAC3 version, particularly the cymbals. What do the Emby developers think about transcoding to EAC3 at 640k when it's supported by the playback device? An easy win for better audio quality, or just another wild idea from a clueless audiophile? AC3_transcode.txt EAC3_transcode.txt

Hi all, I just switched from Plex to Emby just to give it a go. I have a WD TV Live that I'm using in the lounge however EAC3 audio isn't supported by WD and I can't for the life of me get Emby to automatically transcode it like Plex does. Here is a screenshot of the media info: https://imgur.com/fJXyJx4 Thanks in advance Nathaniel

Hi! It seems that emby won't allow me to use EAC3 or AC3 with my Chromecast Ultra. Is this intended behaviour? It should be able to passthrough it to my reciever. Best Regards Jonatan!