Lots of tuner locks lately (HDHomerun)

Good idea!
Only problem is if tuner sharing is enabled on the clients it will always show the IP of the Channels server as the TargetIP.

I share my Tuners with Emby Plex and Sagetv using Channels M3U and do not have tuner lockups. I know in EMBY if watching on Android device you should use the arrow on upper left corner to close the Streams properly ...

@troyhough I’ll check it out.

I know it's Channels DVR locking the tuners. If I reboot Emby they are still in use. If I update to latest Beta on Channels DVR and reboot it, the tuners are immediately released.

Ya it's almost always ATV sources, if every time. Can't force my kids, wife, etc to properly change channels, back out, etc. Sometimes the garage TV will timeout because the Wifi is super weak out there so maybe that could cause it.

It never ever did it with Channels DVR until it started just semi-recently.

1 Like

I just reproduced it by shutting down EMBY incorrectly it locked the tuner but after a few minutes Channels DVR closed it.... If I remember correctly that is the way it is supposed to work.... The problem with EMBY goes way back ...

My best guess is there’s something wrong with how we handle issues when the HDHR returns a “No Data” error and I have to figure out exactly what the steps are that cause it to happen.

1 Like

@troyhough Please try the latest pre-release and let us know if it's any better.

@eric Just installed 2024.05.26.0350. Will let you know if they stick going forward. Thanks

Hi @eric channel 51.1 is locked up right now. Just sent over logs. Thanks

de75bce7-473a-40af-8947-db3c725c39b9

Just for fun I grabbed my phone and tuned to Ch 51.1 using Channels. It used (shared) the tuner slot that was already locked up, not using a different available slot. I clicked the 'Done' button. The tuner slot is still locked. So apparently tuning to that same channel and stopping it doesn't unlock it. Just an FYI.

Can you send diagnostics again after you did that?

2a617675-19e7-42b2-8c9c-9eda13ef826c

I don't have any solid theories on what is happening for you and unfortunately all of my testing of concurrently opening transcoding streams of the same channel over and over again has been unable to reproduce the issue with a channel never being closed, so there's something going on for you that I'm not seeing in the logs and code.

That said, I have discovered a few places where the situation around concurrently opening streams can be cleaned up to reduce the opportunity for using extra tuners and have some changes to remedy that. I'm not going to be available to monitor for problems with any of the changes for the next few days, so I'm likely going to hold off on putting them into a pre-release until this weekend.

1 Like

I was having issues with locked channels using only one device (remote Apple TV) and can confirm the latest pre-release fixed things for me.

As far as not sharing a tuner that is already being used when another device is asking for the same channel and it instead tying up an additional slot has been an issue forever. I have reported it and was told that's just how it is type of a thing. I kind of gave up on that issue. If you can get that fixed up then great.

However this new thing of tuner locks has NEVER been an issue since I started using Channels close to 2.5 years. It was rock solid on releasing tuners under every possible scenario. My devices and the way I use Channels has not changed. I am guessing the issue started happening around 3-4 weeks ago.

The thing I'm describing that I have a fix for is slightly different. If two clients hit "play" at exactly the same moment, there is a short window where they can both open a new stream before either of them has had a chance to see the other stream, and thus don't use sharing.

The issue you're describing has to do with what happens when your highest priority tuner is completely full, a stream starts on the second priority tuner, all of the streams stop on the highest priority tuner and then someone starts to play the channel that is currently on the second priority tuner.

@eric Right now slots 3.1, 6.1, 7.1, and 51.1 are tied up. I am only watching 1 of them, 7.1.

06530b36-559d-4c42-9bbd-8228d310ed59

Logs sent, thanks.

At this point I don't think I'll need any more diagnostics until I can roll out the fixes I have ready. Thank you for your patience.

1 Like

Ok no problem. Appreciate you looking into it @eric !