(other than buying the equipment and paying the hydro bill)
Fascinating. I wasn't aware that this DVR ran on water.
The second would be a much simpler solution where only the recording programming is downloaded to the PVR. The latter could be done in the format of a simple .csv file using any spread sheet software. A very simple format such as “Program name", tuner #, Channel #, Start Date, Start Time, End Date, End Time.
I think this is an excellent idea, but would modify it in two ways: provide a Duration field, instead of EndDate + EndTime. First off, because that's how I normally think of things , and translating to an end point gets annoying. But also because it completely avoids the problem of ambiguity introduced by DST transitions. [e.g. a half-hour program that starts at 1:30am and ends at 1am, because the interval from 1am-2am transpires twice.] And secondly, add a WhichDays field at the end, for regular periodic programming. This contains a list of days, with an empty list meaning 'doesn't repeat'. So "SMTWhFa" would mean every day of the week (with h=Thu, and a=Sat, because their first letter is already taken. Or use lower-case for those.). This makes it easy to specify M-F programming, or shifted Tue-Sat programming (late-nite shows). Or any other combination ("MWF").
Issues like padding etc are then part of the users decision on which start and end times to use etc. The program name and start date and time is used as the name under which the recording is listed on the PVR.
This recording .csv file could even be resident on the HDD or on a USB stick using the second USB port .
Or be located on a network drive, if the DVR was told to look there for it.
When this .csv file is present then the use of (whatever) available PSIP data is restricted to live surfing.
I agree about the override, but I'm not sure whether it makes more sense to have this file "always there" (which makes it a bit more difficult for the DVR to know when it needs to read it because it changed). Or if, like a firmware update, it gets processed when it appears, then automatically gets deleted. That would be quick, simple, and easy for the DVR to handle. And the user only provides a new RecordingList file whenever they want to replace the current EventList in the DVR. [If you wanted to have it just add new items to the existing internal EventList, then you'd need to add a mechanism where you could specify item deletion.]
Free, very simple and certainly a lot less effort to sort out than the unreliable PSIP data.
Absolutely. And it puts a lot of control back into the user's hands. PSIP data dependency will be an unending source of aggravation.
Edited by VideoGrabber - 6/13/12 at 3:01pm