Beside all that technical stuff, i would love to get one file per recording. No one really will use vdr, which is a linux based application, on a fat16 file system or similar which doesn't support files greater than 2 GB. I asked myself many times why vdr splits files, even when saving recordings to filesystems without those limits.Klaus Schmidinger wrote:Wolfgang Fritz wrote:Hello, is there a technical reason why the maximum file size of a .vdr file is limited to 2000MB? Some postprocessing tools accept neither multiple input files nor FIFOs as input file so a time and disk space cosuming "cat"-ing to one big vdr file is required.Keeping the files below 2GB makes sure VDR will work on _any_ system.OK. It's a design decision then.Really? Lets look at an example:Besides, using 64 bit file offsets would cause an unnecessary bloat in the index file.
bash(18)ll
insgesamt 2675148
-rw-r--r-- 1 vdr users 2097411106 Feb 28 16:40 001.vdr
-rw-r--r-- 1 vdr users 640836486 Feb 28 16:41 002.vdr
-rw-r--r-- 1 vdr users 1088688 Feb 28 16:41 index.vdr
-rw-r--r-- 1 vdr users 0 Feb 28 16:46 marks.vdr
-rw-r--r-- 1 vdr users 4 Feb 28 16:47 resume.vdr
-rw-r--r-- 1 vdr users 278 Feb 28 16:36 summary.vdr
A recording of abt 2700MB has an index file of abt 1 MB. Using 64 bit file offsets would double the index file size to 2 MB which gives 1MB/2700MB = 0.03% more data. BTW, 32 bit offsets should be good for 4G files, which could hold most movies in one file (of course that won't work with 32 bit offs_t).