2012-10-22, 04:55 AM
I recently upgraded a nextpvr system from 2.4.3 to 2.5.9. It has two Hauppauge analog capture cards which utilize IR blasters to tune cable boxes to the proper channel. With 2.4.3, each request for livetv would utilize a different tuner card. I would have two different instances of VLC, requesting a livetv session with http://localhost:8866/live?channel=xxx. Each session would access a new tuner, and if both were busy, the VLC request would receive an error indicating that a 'tuner' was not available.
With 2.5.9, the first request works fine. However, the second request grabs the same tuner, changes the channel, and freezes the first session. I have attached an nrecord log file that shows the two connection requests, under 2.5.9.
I recall a recent post, about making nextpvr able to more easily change channels for livetv. Perhaps this change may be inadvertantly causing this behavior?
I note also that both tuners are tuned to channel 4, because they are receiving output from the cable boxes on channel 4, so it would seem that perhaps a new request would appear to be utilizing the same channel, even though the cable boxes are tuned to different cable channels?
Thanks for your help.
Kelly M.
With 2.5.9, the first request works fine. However, the second request grabs the same tuner, changes the channel, and freezes the first session. I have attached an nrecord log file that shows the two connection requests, under 2.5.9.
I recall a recent post, about making nextpvr able to more easily change channels for livetv. Perhaps this change may be inadvertantly causing this behavior?
I note also that both tuners are tuned to channel 4, because they are receiving output from the cable boxes on channel 4, so it would seem that perhaps a new request would appear to be utilizing the same channel, even though the cable boxes are tuned to different cable channels?
Thanks for your help.
Kelly M.