Jump to content

Edit - Atmos transcodes fail


dark_slayer
 Share

Recommended Posts

dark_slayer

Alright, so I mentioned this previously but never logged or created a topic for it

 

@@Luke, normally I'd just throw this into the server support area, and tagged onto someone else's atmos problem topic there a couple weeks ago when I first saw this thinking it was a server issue. I've played a few atmos transcodes back in both the android and web client, so I no longer think this is a server specific issue

 

I can't make any heads or tails how this is Emby for Kodi related, but here is my OpenElec log http://xbmclogs.com/p9xw0gztk Emby for Kodi has a lot of log spew even with logging turned off ;( I did a reboot and played one of my Atmos blu-rays (American Sniper) but I can't find it logged anywhere. Instead there is still a weeks worth of logging it looks like (to me). I may have to do a hard reset :( to get the log manageable unless anyone knows any log cleanup secrets in OE

 

I went ahead and attached a failed Atmos transcode log and a successful TrueHD transcode log (for good measure)

 

Both were using Emby for Kodi http transcoding

 

Fortunately the atmos list is small http://www.dolby.com/us/en/experience/dolby-atmos/bluray-and-streaming.html but I can't understand why these are failing only in this specific client

Atmos fail.txt

TrueHD success.txt

Edited by dark_slayer
Link to comment
Share on other sites

Angelblue05

@@dark_slayer

 

I've left transcoding settings as it was before, which will use h264 and aac audio, but maybe it's missing a necessary setting?

 

This is your American sniper:

18:26:37 T:140220308121344  NOTICE: Parameter string: ?id=df74386baaccd535b128566b314c6c26&mode=play
18:26:37 T:140220308121344  NOTICE: PLAY Called
18:26:37 T:140222174291840  NOTICE: DVDPlayer: Opening: http://x.x.x.x:8096/mediabrowser/Videos/df74386baaccd535b128566b314c6c26/master.m3u8?mediaSourceId=df74386baaccd535b128566b314c6c26&VideoCodec=h264&AudioCodec=aac,ac3&deviceId=7733D5AA11944A8FB7525CEACBC0F2C5&VideoBitrate=1320000&AudioStreamIndex=1
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (truehd (native) -> aac (native))
Error while opening encoder for output stream #0:1 - maybe incorrect parameters such as bit_rate, rate, width or height
Edited by Angelblue05
Link to comment
Share on other sites

dark_slayer

 

@@dark_slayer

 

I've left transcoding settings as it was before, which will use h264 and aac audio, but maybe it's missing a necessary setting?

 

This is your American sniper:

18:26:37 T:140220308121344  NOTICE: Parameter string: ?id=df74386baaccd535b128566b314c6c26&mode=play
18:26:37 T:140220308121344  NOTICE: PLAY Called
18:26:37 T:140222174291840  NOTICE: DVDPlayer: Opening: http://x.x.x.x:8096/mediabrowser/Videos/df74386baaccd535b128566b314c6c26/master.m3u8?mediaSourceId=df74386baaccd535b128566b314c6c26&VideoCodec=h264&AudioCodec=aac,ac3&deviceId=7733D5AA11944A8FB7525CEACBC0F2C5&VideoBitrate=1320000&AudioStreamIndex=1
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (truehd (native) -> aac (native))
Error while opening encoder for output stream #0:1 - maybe incorrect parameters such as bit_rate, rate, width or height

 

Whoops

 

Sorry, post topic was edited ;) Not just a kodi problem

 

I reached the conclusion that it was a Kodi problem by a couple of my own errors in judgement. First, I played American Sniper on my G2, but I didn't realize that my Emby setting for American Sniper from a few weeks ago was saved ?? I had selected the standard 5.1 AC3 track over the Atmos track to get playback to work, and it was still using that. Once I selected the atmos track again, it failed. That was the latest android emby stable app

 

Then there are my two brother in laws. One runs redshirt's old android apk on a fire tv and the other runs openelec w/ emby. The FTV running the old 2.1.39 (final redshirt release) apk played American Sniper just fine. This is a head scratcher, as maybe there was some logic that skipped the TrueHD tracks . . . not sure but nothing special is required for playback. The web client was strange, because as soon as I selected the atmos track playback failed (stuck at the backdrop with no progress)

 

The only thing that was failing before I went through a better sanity check was the brother in law on OE http transcoding.

 

Now I see that Emby still can't do Atmos transcodes anywhere. I recall that Kodi v13 couldn't play either, but the v14 ffmpeg bump fixed that. Is something similar in order for Emby? @@Luke

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...