Short summary: many channels in the UK (and perhaps elsewhere) "timeshare" their bandwidth with other channels, meaning they 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 previously playing channel, again with no OSD.
TimeSharer is a new plugin that lets you change the tuning information for these channels, meaning NPVR can tune into an alternative channel that *is* broadcasting during off-air times. This keeps NPVR nice and responsive.
At the moment, you can control channels by specifying what content they should show (from either the correct channel or an alternative) over a 24 hour period. TimeSharer "fudges" the NPVR tuning cache so that, for example, the EPG entry for "Channel A" can actually show the broadcast of "Channel B". The recording service maintains the correct tuning information at all times.
Posted by: Elmo Putney - 2011-07-13, 04:41 AM - Forum: Hardware
- No Replies
I maybee should have added this to the other TBS card thread but I think this is big news for some that may not have been following the other thread.
TBS just released the 6984 quad card. http://www.tbsdtv.com/english/product/6984.html
I've been recording Falling Skies for a couple of weeks on 2.03. I upgraded to 2.14 and now I've got a1 hour show file that is 16Gb using a Happauge 150MCE. I thought it was just a fluke so I recorded the episode again and it came out at 12Gb. Would a quality setting of "Default" do something like this?
Ok, so I just bought a house and I'm preparing to move and planning out the important things... like a PVR setup! I currently have a single GBPVR setup but I'm planning on starting from scratch and I figured I'd use NPVR. What I'd like to do is have one machine that is the "main" PVR with the really large hard drive and processor and what not, and then a smaller system on the other tv(s) in the house and have them all record to the same drive/database on the main system. I know you can set an NPVR as a client system to another NPVR system via shares and NPVR configuration, but my question is this:
If the recordings and database entries are going to the main machine, can I still schedule each machine for it's own recordings?
I guess another way to ask it is if this is possible:
Main PVR is machine A. Lightweight 2nd PVR is machine B. Machine B is a client to A. If I record something on A, I want to be able to view it on A or B. If I record something on B I want to be able to view it on A or B. I'll be able to schedule recordings on A, but can I still schedule recordings on B? If they all go to the same database how will NPVR know that one recurring recording should be recorded from A and another recurring recording should be recorded from B? Is that possible?
Am I making sense? I know what I want to ask I'm just not sure I'm explaining it right.
The Euro Millions (lottery) jackpot of 185 million Euros was won by a single UK ticket holder.
At the time of the draw, that was the equivalent of about £164.7m but due to fluctuation in exchange rates, it's now worth only £162.5m. That's a loss of £2.2 million in a few hours. The mind boggles.
The 185m Euros is guaranteed but I wonder how I'd feel if I'd won it and knew that in UK terms it was worth over £2m less in such a short time. :eek:
"The Hauppauge WinTV-DCR-2650 dual tuner digital cable card receiver. It's like having a cable TV set top box for your PC! Only $129.- for the dual tuner USB model. Here's the rear view showing where you plug in the cable card.
The WinTV-DCR-2650 is a collaboration between Hauppauge and Silicon Dust."
I'm sure I remember this being mentioned in the release notes a few versions ago that an enhancement was added so that if you deleted the last remaining instance of a recording the screen would return to the same position on the list rather than being thrown back to the start of the list, but it isn't doing this for me on the last couple of versions. Is there maybe a setting for this in config?
I just updated to 2.1.4 from 2.0.3; the first 2 recordings scheduled using the Hauppauge Colossus failed with the error 'Unable to locate crossbar filter (#1)'. The name of the crossbar is 'Hauppauge Colossus Crossbar' (see filtercheck.log), but NPVR is looking for 'Hauppauge HD PVR Crossbar' (NRecord.log). The crossbar entry in npvr.db3 is 'Hauppauge Colossus Crossbar', so I'm really confused about how NPVR identifies the crossbar filter.
