2011-04-12, 12:49 PM
Background to this here (http://forums.nextpvr.com/showthread.php...oadcasting)
Short summary: many channels in the UK "timeshare" their bandwidth with other channels, meaning the channels don't broadcast 24/7. When NPVR tunes into a non-broadcasting channel, it acts like it's frozen, and usually shows either a black screen with no OSD, or a frozen picture from the preview channel, again with no OSD.
I've been sitting on a plugin solution to this for a while - TimeSharer - which lets the user change the tuning information for these channels so that NPVR tunes into an alternative channel that *is* broadcasting during the times that they are normally off air.
I wanted one last discussion about it before releasing it though.
Here's sub's comment from another thread (http://forums.nextpvr.com/showthread.php...dcasting):
I guess the main question for sub is: is there really nothing (easy) you can do about it? NPVR seems to manage ok with radio stations (which obviously have no video) but perhaps a different type of graph is built for them?
My plugin works by changing the "local" cache of channel data within NextPVR.exe, so only Live TV is effected; scheduled recordings will still have the correct information in the DB.
To do this, it updates the database with these "fake" values, tells NPVR to reload its settings, then instantly resets the database to the correct values. This does mean the database contains the wrong information for a tiny fraction of a second, which worries me slightly, although technically it wouldn't change the database when a recording was scheduled because the channel must be on-air anyway. I still don't like doing it though. Perhaps there's a way I could override NextPVR.exe's details directly via the API, rather than via the DB?
I've tested it with DVB-T and DVB-S (with merged channels between them too). I have no idea how it would perform with anything else, but maybe that doesn't matter if it's a UK-only problem.
There's some basic documentation on it here (http://www.nextpvr.com/nwiki/pmwiki.php?...TimeSharer) that I wrote yonks ago but never finished. It's actually a very simple problem/concept that I find difficult to explain
Iain
Short summary: many channels in the UK "timeshare" their bandwidth with other channels, meaning the channels don't broadcast 24/7. When NPVR tunes into a non-broadcasting channel, it acts like it's frozen, and usually shows either a black screen with no OSD, or a frozen picture from the preview channel, again with no OSD.
I've been sitting on a plugin solution to this for a while - TimeSharer - which lets the user change the tuning information for these channels so that NPVR tunes into an alternative channel that *is* broadcasting during the times that they are normally off air.
I wanted one last discussion about it before releasing it though.
Here's sub's comment from another thread (http://forums.nextpvr.com/showthread.php...dcasting):
Quote:Unfortunately the video renderers typically wont update the screen in any way until it is displaying the next frame of video, so when you switch to a channel with no video currently transmitting, the old frame stays on the screen, with no way to make it go black, and no update to the OSD graphics even though the app is telling the renderer to display them.
I guess the main question for sub is: is there really nothing (easy) you can do about it? NPVR seems to manage ok with radio stations (which obviously have no video) but perhaps a different type of graph is built for them?
My plugin works by changing the "local" cache of channel data within NextPVR.exe, so only Live TV is effected; scheduled recordings will still have the correct information in the DB.
To do this, it updates the database with these "fake" values, tells NPVR to reload its settings, then instantly resets the database to the correct values. This does mean the database contains the wrong information for a tiny fraction of a second, which worries me slightly, although technically it wouldn't change the database when a recording was scheduled because the channel must be on-air anyway. I still don't like doing it though. Perhaps there's a way I could override NextPVR.exe's details directly via the API, rather than via the DB?
I've tested it with DVB-T and DVB-S (with merged channels between them too). I have no idea how it would perform with anything else, but maybe that doesn't matter if it's a UK-only problem.
There's some basic documentation on it here (http://www.nextpvr.com/nwiki/pmwiki.php?...TimeSharer) that I wrote yonks ago but never finished. It's actually a very simple problem/concept that I find difficult to explain
Iain