4k h.264 transcoded when it is supported by host

[jaredallard 0]

Emby Version: 3.2.70

OS: Ubuntu Server 17.0.10

 

 

Logs: https://gist.github.com/jaredallard/a3b2593e84a03fd5ada6ea09f308bd62 (api keys have been stripped)

Base Media information:

 

Need anything else, let me know!

[Luke 42077]

Hi, what Emby app are you playing from? Can you please discuss the example a little more? thanks.

[jaredallard 0]

Hi, what Emby app are you playing from? Can you please discuss the example a little more? thanks.

 

Playing from web, on a Macbook Pro 2017. High Sierra. Chrome 63.0.3239.132 (Official Build)

Edited January 25, 2018 by jaredallard

[Luke 42077]

and the ffmpeg log?

[jaredallard 0]

and the ffmpeg log?

 

Of the media? or of the transcode? That's included in the gist, just all the way at the bottom (thanks Github) Direct Link: https://gist.github.com/jaredallard/a3b2593e84a03fd5ada6ea09f308bd62/raw/49a6ce0e993ee89c7370bebf378a7bf5e6b438b7/transcode.txt

Edited January 25, 2018 by jaredallard

[Luke 42077]

We currently have chrome allowing up to level 51 h264. this is level 52 which we have not tested yet. it's something we can review for a future update. thanks.

[jaredallard 0]

We currently have chrome allowing up to level 51 h264. this is level 52 which we have not tested yet. it's something we can review for a future update. thanks.

Alright, from my end it's supported. Here's a screen cap of chrome://media-internals for your future impl. if you decide too. I'll convert to level 5.1

render_id: 3292
player_id: 0
origin_url: file:///
frame_url: file:///Users/jaredallard/Kimi%20no%20na%20wa%20(2016).mkv
frame_title: 
url: file:///Users/jaredallard/Kimi%20no%20na%20wa%20(2016).mkv
total_bytes: 5645060295
streaming: false
single_origin: true
passed_cors_access_check: false
range_header_supported: true
pipeline_state: kPlaying
info: FFmpegDemuxer: skipping invalid or unsupported audio track
debug: Warning, FFmpegDemuxer failed to create a valid audio decoder configuration from muxed stream
bitrate: 7061135
found_audio_stream: false
found_video_stream: true
height: 2160
max_duration: 6395.64
start_time: 0
time_base: 1/1000
video_codec_name: h264
video_format: PIXEL_FORMAT_YUV420P10
video_is_encrypted: false
width: 3840
video_dds: false
video_decoder: FFmpegVideoDecoder
video_buffering_state: BUFFERING_HAVE_ENOUGH
pipeline_buffering_state: BUFFERING_HAVE_ENOUGH
event: PLAY
duration: 6395.64

Interestingly enough, it looks like the audio isn't supported by chrome.

[Luke 42077]

Right, there's currently no browser that supports dts audio.

[jaredallard 0]

Right, there's currently no browser that supports dts audio.

 

Didn't know that, but didn't think emby was causing that.  Anyways, dts -> ac3 and level 5.2 -> 5.1 (6 hours later) and it works!

[RanmaCanada 495]

When you're playing stuff, you can check on the server side and it will tell you why it is transcoding.  In this case it should have told you that it was transcoding because the audio format was not supported.  That is IF it is your own server.

[Luke 42077]

You can also check stats for nerds in the video player.

[Guest asrequested]

I like me sum nerdy stats

[jaredallard 0]

You can also check stats for nerds in the video player.

 

 

I like me sum nerdy stats

 

Obviously I checked there first... The log doesn't include the transcode reason in the url to prove that. Regardless, the issue wasn't the audio, emby transcoded because of the level (which we already solved).

Edited January 27, 2018 by jaredallard