Preview - LiveTV Tuner not releasing

[Vitale4 15]

I was testing the new Roku Beta Preview.  I found that the Tuner is not releasing when I stop and back out of the LiveTV section.  I ended up going into the original ROKU app, going to the LiveTV, selected the same station and then exited.  The Tuner freed up after that.

 

• ROKU Beta Preview Version 1.19.14
• Emby Server 3.2.1.0
• HDHR Prime Firmware Version 20161117

 

Thanks

[ebr 16178]

I'm really not sure how it could be different and I have not noticed my tuners getting used up but can you please reproduce and post the server log?  Thanks.

[Vitale4 15]

Will work on this tonight for you....

[Vitale4 15]

I have attached the logs for your review.  I as tuned to channel 505.  As I backed out, exited Emby, and then went to the Roku Home screen, I looked at my tuners and Tuner 1 showed still connected to Channel 5.  Instead of connecting to the non beta version of EMBY, I waited while exporting the logs and getting to begin uploading as requested, I checked the Tuner again and it has finally released (about 5 minutes later).  So, I think it does release, but is delayed.  The Non Beta version releasing the channel the moment I back out to the guide or to the main EMBY screen.

 

 

server-63622780643.txt&api_key=eb67ec9ce7934243bcfdbb5623035019.txt

ffmpeg-transcode-3fb70517-f0cd-463b-99d2-bc11b156d191.txt&api_key=eb67ec9ce7934243bcfdbb5623035019.txt

[econ 74]

I am seeing this as well. 30 seconds or so to stop ffmpeg and release the tuner. Not a big deal. However, the server dashboard continues to report the live tv stream as active. I will post logs later once a few people are off the server and I can get you a clean set of logs.

[Vitale4 15]

Just tested again.  Started to watch channel 469, then went back to guide and switched to channel 505.  When I looked at the HDHR Prime status, it showed 2 tuners being tied up.  After a bit, Tuner 1 released, but Tuner 2 stayed.  I then went into the original EMBY, went to the liveTV and streamed Channel 505.  Upon exiting EMBY, the tuner was released.  So the problem still exists.

 

I decided to retest because the ROKU Beta Preview was updated to Version 1.19.16

[ebr 16178]

Can you please repeat this test noting the exact times that you start and stop each channel and then post the server log?  I can see the app reporting the stop to the server but can't be sure if it lines up with exactly when you stopped.

 

Thanks.

[Vitale4 15]

will do it later tonight....  

[Vitale4 15]

As requested...

 

here is my timeline:

 

5:21          Started ROKU

5:22          Started EMBY Preview

5:24:39     Started the GUIDE

5:25:38     Started Show (Channel 620 Discovery HD)

5:27:09     Backed out to EMBY Channel Guide

5:27:15     Backed out to EMBY EMBY LiveTV Menu

5:27:37     Backed out to Main Menu

5:27:50     Exited EMBY Preview

5:28:15     Tuner 0 on HDHR Prime still shows being used by EMBY Channel 620

5:28:27     Tuner 0 on HDHR Prime now shows available

 

I have attached the logs as requested, please let me know if you require anything else.

 

Also note:  if I use the Original EMBY or EMBY Blue Neon, it releases the tuner immediately upon backing out of the live stream and getting back to the guide.

 

Thanks

ffmpeg log.txt

Server Logs.txt

[ebr 16178]

When you do this with the other apps is it also transcoding?

 

I can see the last request by the video player here:

2017-02-18 05:27:17.2653 Info HttpServer: HTTP Response 200 to 192.168.100.167. Time: 31ms. http://192.168.100.168:8096/emby/videos/c7e60acbaa233a8400ea8c3c2024f779/hls/a3cf492a8b8d7bfc1b86cf6f810ad4b4/a3cf492a8b8d7bfc1b86cf6f810ad4b430.ts

at 5:27:17.  Then the app reports the stop event to the server about 2 seconds later (video segments are about 3 seconds long I think):

2017-02-18 05:27:19.5466 Info HttpServer: HTTP POST http://192.168.100.168:8096/emby/Sessions/Playing/Stopped. UserAgent: Roku/DVP-7.50 (047.50E04099A)
2017-02-18 05:27:19.6247 Info SessionManager: Playback stopped reported by app Roku SG 1.19.16 playing The Discovery Channel HD. Stopped at 72000 ms

If the channel is not releasing at that point, the only thing I can figure is that the server is not stopping ffmpeg right then.  The only way I can figure this could be different with the other apps is if they are not transcoding.

[Vitale4 15]

Let me run the test with the Original EMBY not the EMBY Blue Neon....  I will attach the logs as well

[Vitale4 15]

I ran the test with the original EMBY ROKY app...

 

10:44:05     Started EMBY Original App

10:44:18     Started the Guide

10:44:52     Selected Channel 620 Discover HD from the Guide   -- Tuner 0 on the HDHR Prime Connected to selected Channel

10:45:14     Channel started to play -- (took 22 seconds for channel to appear on the screen and stream)

10:46:00     Backed out of the stream (Stopped playing) - Tuner 0 showed Available the moment the Guide showed

10:46:28     Backed out to Main LiveTV menu

10:46:44     BACKED OUT TO MAIN PAGE

10:46:55     Exited Emby

 

I attached the logs.  But as you can see the Tuner Freed up the moment I closed the stream.

 

Hope this helps

ffmpeg log original emby.txt

Server Logs Original EMBY.txt

[speechles 2055]

If the channel is not releasing at that point, the only thing I can figure is that the server is not stopping ffmpeg right then. The only way I can figure this could be different with the other apps is if they are not transcoding.

Okay, so you are doing .../Sessions/Playing/Stopped

 

But, are you doing .../Videos/ActiveEncodings and using http DELETE to stop the transcoding?

 

You need to stop the transcoding before you stop the session.

Edited February 18, 2017 by speechles

[ebr 16178]

Vitale thanks for your help.  I believe I have this solved for the next update.

 

Speechles - thanks but that shouldn't be necessary.  The server handles shutting down the transcode as long as you give it all the proper parameters it needs to make the connection.

[speechles 2055]

@@ebr you sure? Why on the new beta app when something has to transcode, and I exit the video player, is ffmpeg still going? Ffmpeg continues until it has made all the .ts slices. Then I gotta ask, why is transcoding-temp filled with orphaned files from left over sessions from the new beta app? I think you need to do the paper chasing, the server isnt doing this fast enough.

Edited February 18, 2017 by speechles

[Vitale4 15]

thanks ebr.  I will verify when the next update comes out

[ebr 16178]

@@ebr you sure? Why on the new beta app when something has to transcode, and I exit the video player, is ffmpeg still going? Ffmpeg continues until it has made all the .ts slices. Then I gotta ask, why is transcoding-temp filled with orphaned files from left over sessions from the new beta app? I think you need to do the paper chasing, the server isnt doing this fast enough.

 

...as long as you give it all the proper parameters it needs to make the connection.

 

I wasn't feeding it the information it needed to connect the play session with the ffmpeg instance.

[ebr 16178]

Please test this in 1.19.17

[Vitale4 15]

will test it a little later...

[Vitale4 15]

Ok -- so I tested.  When I first went in, I received an error when trying to connect to the LiveTV Stream - the tuner showed connected, but the EMBY App displayed an error.  I retested with the old app and had some issues as well.  I rebooted the server, Roku, amd HDHR prime, to start fresh.

 

Second test seemed to work as predicted.  the Preview App freed the tuner when backing out of the stream.  Looks lie it has been corrected. 

 

I will continue to test later tonight and through the week.

 

Thanks for addressing this issue.

[Luke 42078]

Thanks for confirming.