Hi,
Dirk Meyer schrieb:
mike lewis wrote:I'm not sure if this is necessary at all. VDR has its own scheduler which is easily controllable via svdrp (tcpip) access.
Idea: we always use our recordserver. We have a vdr record
plugin. Before a program should be recorded (e.g. 5 minutes before
that, normal padding), the recordserver will call that plugin. Now the
start stop daemon starts vdr and the plugin schedules the recording in
vdr.
So basicly its sufficient to interface vdr to query for scheduled programs whenever a user enters the timer menu.
When one starts/changes a timed recording, freevo can send the data to vdr.
This means: let vdr be the primary scheduler and database for timers because its doing its job very well.
Personally i'm considering vdr+some freevo plugins as just some sort of recordserver implementiation.
You might ask: why should this be the better solution?
- it interfaces also with remote vdr installations (the usual "server" in one's basement)
- its compatible to vdr timer plugins like the tvtv plugin to schedule timers via web interface (http://tvtv.de)
- its (IMHO) cleaner and easier.
- vdr is a very lightweight daemon. Let it run instead of start/stopping it.
- vdr streaming clients rely on a always-on vdr instance.
- vdr has VPS support in the current developer releases. Stopping vdr renders this useless.
However, just my 2 cents :-)
Greetings,
-- Thomas
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
