Jump to content

4K HEVC


memeka
Go to solution Solved by Luke,

Recommended Posts

memeka

Hi,

 

My Android TV can play 4K HEVC, however emby server tries to transcode it, and since transcoding 4K HEVC is too much for my server => FAIL.

Can Emby ATV client play 4K/HEVC? How to configure it?

 

Thanks.

 

Link to comment
Share on other sites

Can you please post an ffmpeg and server log from one of these playback attempts?  Thanks.

Link to comment
Share on other sites

memeka

ffmpeg log: http://paste.debian.net/923477/

 

nothing to see there, just slow transcoding

 

server log:

2017-03-22 23:05:29.7907 Info App: Cannot direct play due to unknown content bitrate
2017-03-22 23:05:29.7907 Info App: Cannot direct play due to unknown content bitrate
2017-03-22 23:05:29.7907 Info App: Profile: Unknown Profile, Path: /mnt/samba/movies/Chappie (2015)/Chappie (2015).mkv, isEligibleForDirectPlay: False, isEligibleForDirectStream: False
2017-03-22 23:05:29.7907 Info App: Cannot direct play due to unknown content bitrate
2017-03-22 23:05:29.7907 Info App: Cannot direct play due to unknown content bitrate
2017-03-22 23:05:29.7907 Info App: Profile: Unknown Profile, Path: /mnt/samba/movies/Chappie (2015)/Chappie (2015).mkv, isEligibleForDirectPlay: False, isEligibleForDirectStream: False
2017-03-22 23:05:29.7910 Info App: Cannot direct play due to unknown content bitrate
2017-03-22 23:05:29.7910 Info App: Cannot direct play due to unknown content bitrate
2017-03-22 23:05:29.7910 Info App: Profile: Unknown Profile, Path: /mnt/samba/movies/Chappie (2015)/Chappie (2015).mkv, isEligibleForDirectPlay: False, isEligibleForDirectStream: False
2017-03-22 23:05:29.7931 Info HttpServer: HTTP Response 200 to 192.168.0.12. Time: 10ms. http://192.168.0.26:8096/emby/Items/ce4474fbde9f8f5a42dc0a592aaffebf/PlaybackInfo?UserId=992b0196016947c4ab87d6d518656cbd&StartTimeTicks=0&MaxStreamingBitrate=505263158
2017-03-22 23:05:30.0526 Info HttpServer: HTTP GET http://192.168.0.26:8096/emby/videos/ce4474fbde9f8f5a42dc0a592aaffebf/live.m3u8?DeviceId=2d9cc55cd6100dbdb132ede2ae3f63b1b366bd2d&MediaSourceId=ce4474fbde9f8f5a42dc0a592aaffebf&VideoCodec=h264&AudioCodec=aac,mp3&VideoBitrate=505071158&AudioBitrate=192000&Level=51&Profile=high&PlaySessionId=e6441231bd5a4c3890e91a4b28d5f948&CopyTimestamps=false&TranscodingMaxAudioChannels=6&EnableSubtitlesInManifest=false&Tag=543b6ca4c9f21c87d81daf7a932499c0&RequireAvc=true. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
2017-03-22 23:05:30.0875 Info App: ffmpeg -i file:"/mnt/samba/movies/Chappie (2015)/Chappie (2015).mkv" -map_metadata -1 -map_chapters -1 -threads 0 -sn -codec:v:0 h264_v4l2m2m -pix_fmt nv21  -b:v 505071158 -maxrate 505071158 -bufsize 1010142316 -vsync -1 -force_key_frames "expr:gte(t,n_forced*3)" -flags -global_header -max_delay 5000000 -avoid_negative_ts disabled -start_at_zero -codec:a:0 aac -strict experimental -ac 6 -ab 192000 -af "adelay=1,aresample=async=1" -hls_time 3 -individual_header_trailer 0 -start_number 0 -hls_list_size 0 -hls_base_url "hls/623b9f78ba34cd300039a0f044176347/" -y "/srv/MediaBrowser.Mono.3.2.8.0/ProgramData-Server/transcoding-temp/623b9f78ba34cd300039a0f044176347.m3u8"

Here I can see the issue indeed: Cannot direct play due to unknown content bitrate

 

Is there anything to do to allow direct play?

 

Thanks.

 

EDIT: actually, looking at the ffmpeg log, bitrate sent to encoder is like 500MB! Is this because it cannot read the original file bitrate, and uses a maximum value?

Edited by memeka
Link to comment
Share on other sites

  • Solution

It's because we don't have media info for your video file, therefore we used the maximum supported bitrate requested by the emby app. Normally we compare that value to the media info and then figure out the final amount from there.

 

So why don't we have media info? Perhaps you've just added the video file and the library scan hasn't completed yet, or perhaps there was some unknown problem the first time it was scanned. In any event, open the web app, navigate to the detail screen of this video, click the 3-dot menu -> then click refresh. It will now probe the video and hopefully populate media info. 

 

Do this, then try to play again from android tv. let us know how it compares. thanks !

  • Like 1
Link to comment
Share on other sites

  • 1 year later...

It's because we don't have media info for your video file, therefore we used the maximum supported bitrate requested by the emby app. Normally we compare that value to the media info and then figure out the final amount from there.

 

So why don't we have media info? Perhaps you've just added the video file and the library scan hasn't completed yet, or perhaps there was some unknown problem the first time it was scanned. In any event, open the web app, navigate to the detail screen of this video, click the 3-dot menu -> then click refresh. It will now probe the video and hopefully populate media info. 

 

Do this, then try to play again from android tv. let us know how it compares. thanks !

 

 

When you say refresh do you mean refresh metadata?

Link to comment
Share on other sites

Then it may be that the probing is failing for some reason.  Can you please refresh one of these items and then post the server log from that (and tell us what you refreshed and when)?

 

Thanks.

Link to comment
Share on other sites

Ok so stats for nerds says transcode reason unsupported vid the dashboard says the following

 

The media is compatible with the device regarding resolution and media type (H.264, AC3, etc.), but is in an incompatible file container (.mkv, .avi, .wmv, etc.). The video will be re-packaged on the fly before streaming it to the device.
 
Link to comment
Share on other sites

Hi. I don't see a refresh in that log and the playback startup is not there because it is just part of the log but how about we just start with the ffmpeg log that is generated when you play the item in question?

 

 

Can you please refresh one of these items and then post the server log from that (and tell us what you refreshed and when)?

Link to comment
Share on other sites

Hi. I don't see a refresh in that log and the playback startup is not there because it is just part of the log but how about we just start with the ffmpeg log that is generated when you play the item in question?

Posted the logs any idea?

Link to comment
Share on other sites

Hi. I don't see a refresh in that log and the playback startup is not there because it is just part of the log but how about we just start with the ffmpeg log that is generated when you play the item in question?

Posted the logs any idea?

Link to comment
Share on other sites

Hi. I don't see a refresh in that log and the playback startup is not there because it is just part of the log but how about we just start with the ffmpeg log that is generated when you play the item in question?

Posted the logs any idea?

Link to comment
Share on other sites

Hi. I don't see a refresh in that log and the playback startup is not there because it is just part of the log but how about we just start with the ffmpeg log that is generated when you play the item in question?

Posted the logs any idea?

Link to comment
Share on other sites

You've selected a TrueHD audio track which your device/setup doesn't support so we are converting it to plain Dolby Digital.

 

Does that answer your question?

Thank you

 

Do all android based boxes have the same issue. would i have the same problem on a shield tv?

Link to comment
Share on other sites

Thank you

 

Do all android based boxes have the same issue. would i have the same problem on a shield tv?

 

Hi.  It isn't really an "issue" as we are playing the item back in the best way possible.

 

The Shield can support passing TrueHD IF the outbound equipment also supports it.

 

Thanks.

Link to comment
Share on other sites

Hi.  It isn't really an "issue" as we are playing the item back in the best way possible.

 

The Shield can support passing TrueHD IF the outbound equipment also supports it.

 

Thanks.

 

Well the FireTV isnt switching my display to 4k resolution when I play these files i thought it was because of the transcoding.  Is there another issue then?

Link to comment
Share on other sites

Hi.  The Fire TV does not support auto switching.  You would just need to set your Fire to the 4K resolution in its settings.

Link to comment
Share on other sites

Hi.  The Fire TV does not support auto switching.  You would just need to set your Fire to the 4K resolution in its settings.

 

In my FireTV settings it only has the option of SD,HD,4k(Auto) i can not tell it to maintain 4k resolution. When I watch an Amazon prime video it automatically switches to 4k.

Link to comment
Share on other sites

Guest asrequested

If when you set the audio to TrueHD the server is transcoding, then it will be in 1080. Are you connected to a receiver or your TV?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...