Search the Community

Hy! I want to convert my TrueHD 7.1 Atmos to Eac3 7.1 Atmos. I know it is not done by free softwares but I have Dolby licensed software but I still don't know how to do it. I watched some movie encoder did this but I don't know how. I have all the tools required like, 1. Dolby Media Encoder 2. Dolby Encoding Engine 3. Dolby Atmos Renderer 4. Dolby Atmos Conversion Tool 5. Dolby Reference Player All these tools are registered legally but I still don't know how to do it. I covert the TrueHD Atmos file to WAVs and put in Dolby Media Encoder but I still dont get EAC3 JOC / DD+ Atmos rather it'll generate only EAC3 / DD+ without Atmos. Can anyone help me here..

Devices tested on: Shield 2017, Shield 2019 Emby Android TV client version: 2.0.83g Emby Server version: 4.7.9.0 I have a TV show here that has Dolby Digital Plus with Dolby Atmos audio as its audio track. Here's the mediainfo of the audio: Audio ID : 2 Format : E-AC-3 JOC Format/Info : Enhanced AC-3 with Joint Object Coding Commercial name : Dolby Digital Plus with Dolby Atmos Codec ID : A_EAC3 Duration : 46 min 18 s Bit rate mode : Constant Bit rate : 768 kb/s Channel(s) : 6 channels Channel layout : L R C LFE Ls Rs Sampling rate : 48.0 kHz Frame rate : 31.250 FPS (1536 SPF) Compression mode : Lossy Stream size : 254 MiB (20%) Language : English Service kind : Complete Main Default : Yes Forced : No Complexity index : 16 Number of dynamic objects : 15 Bed channel count : 1 channel Bed channel configuration : LFE When trying to attempt to play any of the episodes, I get the "Too many errors, giving up" message. Looking at the server logs (attached below), it seems it's related to the audio. The files play fine in VLC on both Shields, and on Emby Theater on my PC as well. Tried looking here in the forums but didn't find anything related to DD+ Atmos audio. embyserver.txt ffmpeg-remux-40ec91c4-c38d-4669-a013-9973fac5c8ea_1.txt

So I have an interesting problem. I'm in the process of setting up my first complete home theater with a C8 as my TV was reading up on the limitations associated with ARC. I plan on using one of LG's internal Emby app. The system I'm setting up is a 5.1.2 system and I was hoping that I could stream lossless audio by connecting my receiver to my C8 through the ARC connection, but I was reading that only eARC is cable of TrueHD. A quick diagram of my connections: LG C8 (Internal Emby App) -> AVR -> Speakers As an example, my Avengers Infinity War file has the following for audio (which looks like no DD+ [E_AC-3]): TrueHD: 5174 kbps | 8 channel A_AC-3: 640 kbps | 6 channel A_AC-3: 192 kbps | 2 channel I definitely want to retain the atmos channels since that's why I got the additional speakers. From my understanding, since the TrueHD can't transfer to my AVR, it would default to the A_AC-3 audio, which would not contain the atmos components (correct me if I'm wrong). So my question is, would it be possible to force my Emby server to transcode the TrueHD with atmos to DD+ with atmos? And if so, is this a fairly hardware intensive transcode? Let me know if I can clarify anything or if I said anything wrong! ~Q

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 Luke, I've been using Emby Theatre for a long time and only just discovered the LG App - it is superb! I'm now using it on my LG OLED65C7 and older 55EC930V running WebOS 1.0. It is lightning fast and has been rock solid for me so far. I would love to be able to put the media PC in the loft and relegate that to being a server, as using the LG Emby app with the native TV remote is a much smoother experience. The snag is that using Emby Theatre has the benefit of allowing me to play HD lossless audio formats through my Denon receiver over HDMI. Because the Emby LG app leverages ARC to send audio to the A/V receiver I get DTS and Dolby Digital due to the ARC bandwidth restrictions in effect. However, when I use the LG's Netflix app I get Dolby Digital Plus (DD+) over ARC (and understand that DD+ Atmos is also possible). Are there any plans to support DD+ and DD+ Atmos audio in the LG App at some point in the future as I understand this is as good as we can hope for in terms of sound quality over ARC at present? Thanks