Klaus Schmidinger wrote: > Petric Frank wrote: > >> Hello, >> >> On Wednesday 04 January 2006 10:52, Matthias Schniedermeyer wrote: >> >>>>> How to program a recording in VDR which have to run for more than 24 >>>>> hours ? >>>> >>>> >>>> The maximum recording time is 23 hours and 59 minutes. >>> >>> >>> Only when you don't touch the timer. :-) >>> >>> >>>> You could program several overlapping timers. >>> >>> >>> Or you can prolong the already running timer every few hours. >>> >>> But you can't extent a recording indefinetly because there is limit >>> of 255 >>> files into which VDR can record. But under normal circumstances there >>> is at >>> least enough capacity for recording several days. >> >> >> >> So the file naming can go from 001.vdr to 255.vdr. What about 256.vdr >> to 999.vdr ? >> So - if you keep the default of 2GByte sized files - you are limited >> to about 255 hours and a sum size of 512 GBytes. In the shops you >> find 500GByte drives and when it comes to Raid arrays you can get more. >> >> Ok, usually (nearly) no one would go to record such lenghty sessions ... > > Exactly - and that's why I'm not going to change that (any time soon) ;-) I just had a weired idea. index.vdr is for 1 .. 255 and it should be relativly easy (and backward compatible) to extent that schema with index002.vdr for 256 .. 510 and so on. But OTOH who want's a month or year long recording. ;-) -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.