Jump to content

NVIDIA SHIELD TV Pro Server - Buffering/Choppy Stream


Recommended Posts

1st time user to Emby.  Installed Emby "Premier" version com.emby.embyserver_4.5.4.0.apk on my NVIDIA SHIELD TV Pro with latest NVIDIA updates.

Testing with Avatar 1080p and 1080p 3D in MKV containers or file formats. (My legal ripped content. :) )

I am getting choppy Video stream or buffering not sure.  

image.png.1c4e4ca4270a9d3e0830186c48a517ec.png

I noticed in the attached log file that there are "Could not find codec parameters for stream" items.  Not sure if this has anything to do with the issue.

I ran Emby Server on a standalone windows 10 desktop (AMD Phenom II X6 109T 3.2GHz with 8GB or RAM on the same network and it has a very quick response time. Super fast!  Love it!

Not sure why I cannot get a smooth stream from the Nvidia Shield TV Pro.  Looking for any assistance anyone can provide would be greatly appreciated. 

ffmpeg-transcode-c5befcfc-9d86-401f-9eed-779c55f5426c_1.txt

Link to post
Share on other sites

Been mucking around and made it worse.  Now I am getting this error when trying to play.

image.png.3a701b12dab48b5f4652ebd40cfa89a1.png

Took a look at the log and found this which I assume is not good. 

image.thumb.png.5791a185ecdf59784b9ca593aef448aa.png

 

Link to post
Share on other sites
Happy2Play

From your first post it look like the hardware is choking on burning in psgsub as you are only getting about 14-20 fps.

17:17:45.610 Stream mapping:
17:17:45.610   Stream #0:0 (h264_mediacodecndk) -> overlay:main (graph 0)
17:17:45.610   Stream #0:9 (pgssub) -> scale (graph 0)
17:17:45.610   overlay (graph 0) -> Stream #0:0 (h264_mediacodecndk)
17:17:45.610   Stream #0:1 -> #0:1 (dts (dca) -> mp3 (libmp3lame))

 

Link to post
Share on other sites
ebr
15 hours ago, bhann said:

I am running this on Nvidia TV Shield Pro.  Why would it be running sub par?

Hi.  Because that device isn't really designed as a server and you are asking it to do a fairly large task in transcoding and also burning in graphic subs.  It could also be I/O bound as that process would require a lot of that and, again, the device isn't necessarily designed for it.

If you can eliminate the need to transcode and/or burn in the subtitles (like obtaining text subs for the item) that will probably solve the issue for you.

Link to post
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...