Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Single Tuner utilization in .53 #1

Closed
lulsas opened this issue Apr 3, 2020 · 3 comments
Closed

Single Tuner utilization in .53 #1

lulsas opened this issue Apr 3, 2020 · 3 comments

Comments

@lulsas
Copy link

lulsas commented Apr 3, 2020

First thanks for making this. I started out using .53 and it was working on and off. I didn't find a pattern but one of the things I did notice is that if a tuner was in use, and another broadcast stream was requested it would always take over the first tuner leaving the other three unused. If I disabled 1 it would use two, but the same thing, if a second request came in that request took over the tuner and it wouldn't utilize three or four. I downgraded to .52 and it's been working great. Only issue so far is some channels (not sure what is common to them yet) would error out trying to stream and if you back out (in Plex) after the hang it doesn't release the tuner. More of a Plex failure I think but it would be cool if you could kill a stream from the proxy software interface.

I'm new so let me know if I didn't report something right. Again, thanks for making this.

@craigmox
Copy link
Owner

craigmox commented Apr 4, 2020

Thanks for the report. I use NextPVR primarily, and not Plex, so I didn't notice the problem with it taking over tuner 1 repeatedly. I will fix it soon.

I will also try to add a button to kill an active tuner stream. I have also seen NextPVR hang onto a stream forever, so it very possibly could be a cetonproxy issue. I will keep trying to track this down.

@lulsas
Copy link
Author

lulsas commented Apr 4, 2020

Thanks for responding so quickly. Check your Paypal and have a sixer on me. :-)

@craigmox
Copy link
Owner

craigmox commented Apr 4, 2020

Thanks I appreciate it! I just put up a new version that should fix both issues you brought up. I did not add a button to stop a stream. My hope is that it's never needed if it closes the streams when it's supposed to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants