Jump to content

Shield TV Direct Streaming Playback Freezing


dranderson402

Recommended Posts

dranderson402

Long story short, I've been chasing a problem over the past few weeks that I thought was an OTA reception problem. Now I'm not sure if it is reception or partly my server. I've noticed this mainly only on CBS shows. I've tried a few different antennas, but I'm not convinced anymore the problem is the signal. I'm using 2 HDHR Connects, Emby recording and playback on Shield TV with Emby app. I have a signal strength of 100% and signal quality fluctuates between 93% and 98% for my CBS station. I get the same or better for my ABC, NBC and Fox stations.

 

The problem is the show will freeze during playback. Sometimes I can just jump forward 30 secs and it might resume but usually I have to exit and restart playback. If playback starts a few seconds before the point it froze, it just freezes again at the same point. So while it's froze I will jump forward 30 secs, exit and restart playback and then it works. Not a huge deal but I've missed 30 seconds of the show. Do that multiple times throughout a show and it's really annoying.

 

Last night I was watching NCIS. It froze about 2 mins in right at the point the intro started. As soon as I saw the intro I pressed the right arrow to jump forward 30 seconds and it froze. So I exited out and restarted playback. It started at the beginning as expected so I tapped the right arrow 4 times to jump forward 120 seconds. I let the intro play and it froze about 5 or 10 seconds into the intro playback. So about 130 seconds from the start. I then did a test (don't know why I never thought of this before now) and played it back on my Galaxy S8+ phone. It did not freeze up.

 

That's when I noticed my phone direct plays while the shield direct streams. I did search the forums and understand the shield transcodes .ts files. So this is what got me thinking I may have a server problem. I have included all the ffmpeg transcode files from me stopping and starting playback to get through the show as well as the server log. Below is also the media info from the web interface. All devices are up to date with all stable versions. I'm hoping someone may be able to shed some light on what my problem is or problems are.

 

Media Info
VideoTitle1080i MPEG2VIDEO
CodecMPEG2VIDEO
ProfileMain
Level4
Resolution1920x1080
Aspect ratio16:9
AnamorphicNo
InterlacedYes
Framerate29.97
Bitrate9,102 kbps
Color primariesbt709
Color spacebt709
Color transferbt709
Pixel formatyuv420p
Ref frames1
AudioTitleEnglish Dolby Digital 5.1
LanguageEnglish
CodecAC3
Codec tagAC-3
Layout5.1
Channels6 ch
Bitrate384 kbps
Sample rate48,000 Hz
DefaultNo
Containermpegts
PathD:\Series\NCIS (2003)\Season 17\NCIS S17E03 Going Mobile.ts
Size4031 MB
 
 

 

Emby Logs.zip

Link to comment
Share on other sites

dranderson402

Hi.  If you turn off transcode throttling, does it make a difference?

 

Transcode Throttling? On the server? No, haven't tried that. There were active recordings last night and I didn't want to change any transcoding settings in fear of breaking something. I will have to try that tonight when I get home.

 

I do however have the SD and HD transcode on server app settings unchecked. I tried with HD transcode on server checked and the show played maybe 20 seconds longer before it froze.

Link to comment
Share on other sites

dranderson402

You mean the "Deinterlace" options, correct?

 

Yeah, I believe so. In the android tv app, settings, playback settings, down a little way and there is something about SD and HD transcoding on the server. I think it says something about deinterlace. Not in front of it right now. Going off memory.

Link to comment
Share on other sites

dranderson402

Ok, I unchecked Enable Throttling under transcoding on the server. Played the same show and it froze again at the same spot. I then went in to the app settings, yes I did mean the SD and HD deinterlace, and I checked both. Tried again and still froze at the same point.

 

I've attached the latest logs.

Emby Logs.zip

Link to comment
Share on other sites

dranderson402

As a test, if you disable hardware transcoding, how does that compare?

 

I will give that a try tonight when I get home from work.

 

On that note, I do have a question about hardware transcoding. How does one know if it's working? I've noticed when I'm playing a recorded show that is direct streaming that ffmpeg is running and my cpu usage jumps up. Sometimes to 90-95%. Especially if I bail out of a frozen playback and get back in. Then I see 2 instances of ffmpeg.

 

Am I wrong in thinking that hardware transcoding should be using my video card and not the cpu? All preferred hardware decoders and encoders are set to use NVDEC GeForce GT 630.

Link to comment
Share on other sites

dranderson402

I was just now reading up on hardware transcoding and see where you recommend using the Nvidia drivers and not the Windows drivers. I'm currently using the drivers supplied by Windows. So I'm downloading the latest from Nvidia and will install them.

Link to comment
Share on other sites

dranderson402

Ok, ran some tests by connecting to my home network via my openvpn. Using my family room camera and harmony hub, I powered up the tv and started the same recorded show in question. I found some interesting results. For starters, I upgraded my nvidia drivers to the latest, v436.48. So I left all the hardware transcoding settings as they were for my first test. I opened up task manager on the server and saw the GPU running at 90+% while watching the recording. The show froze at the same time as always. This is where I saw something strange.

 

I was looking at the server dashboard on the web. Even though the playback froze and I backed out of it, the dashboard showed it was still playing and task manager on the server still showed the GPU at 90+%. So I clicked on the stop button on the dashboard but the GPU still at 90%. I manually ended the ffmpeg task but GPU still 90%. Restarted emby server and GPU is now 0%.

 

Next test was to turn off hardware transcoding and start playback again. Same results except it was the CPU running at 90ish%. Playback still froze at the same point. Backed out and dashboard still showed playback was running. CPU still running away with ffmpeg.

 

Here are all the logs again. I included all the logs from my first test through the server restart. Not sure what you may need to look at.

Emby Logs.zip

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...