Jump to content

HDHomerun stream crashing


revengineer

Recommended Posts

revengineer

I have had multiple occasions when Live TV streamed from HDHomerun suddenly stops. However, the associated ffmpeg process will continue to run indefinitely, and must be killed with task manager. I am running the latest server version 3.0.5724.5 and I was watching with the web client in chrome. log is attached.

 

Thanks for checking into this.

server-63578719775.txt

Link to comment
Share on other sites

  • 2 weeks later...

I am also experiencing this each and every time I try to stream live TV. The HDHomeRun app works just fine. This is a new setup for me. Server Version 3.0.5724.6

 

It happens in Chrome Web client and Android Phone Emby app. I haven't tried anything else.

 

What I have noticed is the ffmpeg process will use up CPU resources for about 5 seconds then drop to 0 and stay there. The stream plays for about the same length of time just delayed by a few seconds. The transcode log doesn't report anything until the ffmpeg process is killed. The Live TV config screen show a tuner still being used until I kill ffmpeg. So the problem seems to be with ffmpeg. I attached the transcode log.

Edited by gadjex
Link to comment
Share on other sites

I am also experiencing this each and every time I try to stream live TV. The HDHomeRun app works just fine. This is a new setup for me. Server Version 3.0.5724.6

 

It happens in Chrome Web client and Android Phone Emby app. I haven't tried anything else.

 

What I have noticed is the ffmpeg process will use up CPU resources for about 5 seconds then drop to 0 and stay there. The stream plays for about the same length of time just delayed by a few seconds. The transcode log doesn't report anything until the ffmpeg process is killed. The Live TV config screen show a tuner still being used until I kill ffmpeg. So the problem seems to be with ffmpeg. I attached the transcode log.

 

it's possible the player bailed out because the video wasn't being delivered fast enough. it looks like your server just isn't able to transcode it fast enough. chrome web will always need transcoding. the android client will direct stream straight from the tuner if it thinks it's on the same internal network as the HDHR. in this case it's connecting using your external address so that's why it's using the server to transcode. 

 

there are some situations in which the android app will use the external address even when inside your network, this has been corrected for the next release of the app. but the web client in the browser isn't going to work out for you unless your system can transcode it at a playable rate.

  • Like 1
Link to comment
Share on other sites

Thank you. I know my server is on the slow side. I thought a SD channel would work fine when the FFMPEG was maxing out around 80 CPU. I will need to upgrade then if I want more capabilities.

Link to comment
Share on other sites

Also on a different note, maybe having a way to restrict transcoding so other family members do not try a stream needing transcoding. Reason is the ffmpeg continues to run and takes up a tuner and the Emby server will not successfully restart until the ffmpeg task is manually killed. The logs show it cannot open a port as it is already open. Killing the bad ffmpeg process then restarting and it restart fine.

Link to comment
Share on other sites

revengineer

The main bug here is the ffmpeg process not ending when the stream is interrupted. That one needs fixing because as reported above it causes problem with subsequent streams.

Link to comment
Share on other sites

there's no bug. it just depends on how you stop the video in the app you're using. if you stop gracefully using the buttons in the apps, then this will not happen. but if the app crashes, or is abruptly closed, then it will remain open on the server until it eventually times out. the server will eventually realize the client has disconnected, but it is not safe to do it immediately because it's not always trivial to know the difference between things like user pausing and stopping.

 

an example would be in roku if you press the home button on the remote during video playback. the app does not get any notification from the OS that it's being closed, so on the server the transcode will continue for a couple minutes until it eventually times out due to no client activity.

Link to comment
Share on other sites

revengineer

Thank you for the information Luke. I had the impression that the ffmpeg process remains running forever. I may not have been patient enough to wait for the time out to occur. I will take this into consideration in further testing.

 

I think the server becoming non-responsive under these conditions is simply due to the fact that my core i3 server cannot handle the additional ffmeg process running in parallel to the stale one.

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