Hi, How can I determine that from a vdr-1.7.10 recording? Unfortunately vdrsync doesn't work any more :-(. Regards Halim
??? On Sa, Dez 05, 2009 at 09:34:42 +0100, Halim Sahin wrote:
Hi, How can I determine that from a vdr-1.7.10 recording? Unfortunately vdrsync doesn't work any more :-(. Regards Halim
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Halim Sahin E-Mail: halim.sahin (at) t-online.de
On Sat, 5 Dec 2009 21:34:42 +0100 Halim Sahin halim.sahin@t-online.de wrote:
How can I determine that from a vdr-1.7.10 recording? Unfortunately vdrsync doesn't work any more :-(.
I don't know how you could find the length; maybe it's a simple calculation from the size of the index.vdr file?
To find the aspect ratio you could use:
mplayer -ao null -vo null -frames 1 -identify 001.vdr | grep ASPECT
On Wed, Dec 9, 2009 at 10:58 AM, Tony Houghton h@realh.co.uk wrote:
On Sat, 5 Dec 2009 21:34:42 +0100 Halim Sahin halim.sahin@t-online.de wrote:
How can I determine that from a vdr-1.7.10 recording? Unfortunately vdrsync doesn't work any more :-(.
I don't know how you could find the length; maybe it's a simple calculation from the size of the index.vdr file?
If the recordings store PCR, you could just read the first and last PCR and do some quick math?
Hi VDR User, On Mi, Dez 09, 2009 at 11:03:33 -0800, VDR User wrote:
On Wed, Dec 9, 2009 at 10:58 AM, Tony Houghton h@realh.co.uk wrote:
On Sat, 5 Dec 2009 21:34:42 +0100 Halim Sahin halim.sahin@t-online.de wrote:
How can I determine that from a vdr-1.7.10 recording? Unfortunately vdrsync doesn't work any more :-(.
I don't know how you could find the length; maybe it's a simple calculation from the size of the index.vdr file?
If the recordings store PCR, you could just read the first and last PCR and do some quick math?
Does vdr store the pcr? What do you mean with quick math? Can you post an example? Regards halim
On 09.12.2009 20:13, Halim Sahin wrote:
Hi VDR User, On Mi, Dez 09, 2009 at 11:03:33 -0800, VDR User wrote:
On Wed, Dec 9, 2009 at 10:58 AM, Tony Houghton h@realh.co.uk wrote:
On Sat, 5 Dec 2009 21:34:42 +0100 Halim Sahin halim.sahin@t-online.de wrote:
How can I determine that from a vdr-1.7.10 recording? Unfortunately vdrsync doesn't work any more :-(.
I don't know how you could find the length; maybe it's a simple calculation from the size of the index.vdr file?
If the recordings store PCR, you could just read the first and last PCR and do some quick math?
Does vdr store the pcr?
No, it doesn't.
You can take the size of the index file, divide it by 8 and you get the number of frames in the recording. The info file tells you the number of frames per second (at least with newer TS recordings).
Klaus
On Wed, Dec 9, 2009 at 1:32 PM, Klaus Schmidinger Klaus.Schmidinger@tvdr.de wrote:
On 09.12.2009 20:13, Halim Sahin wrote:
Hi VDR User, On Mi, Dez 09, 2009 at 11:03:33 -0800, VDR User wrote:
On Wed, Dec 9, 2009 at 10:58 AM, Tony Houghton h@realh.co.uk wrote:
On Sat, 5 Dec 2009 21:34:42 +0100 Halim Sahin halim.sahin@t-online.de wrote:
How can I determine that from a vdr-1.7.10 recording? Unfortunately vdrsync doesn't work any more :-(.
I don't know how you could find the length; maybe it's a simple calculation from the size of the index.vdr file?
If the recordings store PCR, you could just read the first and last PCR and do some quick math?
Does vdr store the pcr?
No, it doesn't.
You can take the size of the index file, divide it by 8 and you get the number of frames in the recording. The info file tells you the number of frames per second (at least with newer TS recordings).
That makes it pretty easy! :)
Klaus Schmidinger schrieb:
You can take the size of the index file, divide it by 8 and you get the number of frames in the recording. The info file tells you the number of frames per second (at least with newer TS recordings).
I don't think this calculation is always accurate (i.e. for h264/HD recordings) right now. For a 1080i recording the info file contains "F 25" (shouldn't it be 50 frames for 1080i50?)
Example (recorded with vdr 1.7.10): # ls -la insgesamt 7219260 drwxr-xr-x 2 vdr vdr 59 28. Nov 15:04 . drwxr-xr-x 3 vdr vdr 38 22. Nov 20:12 .. -rw-r--r-- 1 vdr vdr 7389603764 22. Nov 22:13 00001.ts -rw-r--r-- 1 vdr vdr 2901984 22. Nov 22:13 index -rw-r--r-- 1 vdr vdr 681 22. Nov 20:12 info
# grep "^F\ " info F 25
2901984 (size of the index file) / 8 = 362748 (frames) 362748 / 25 (framelength according to info) = 241min 49sec (wrong!) 362748 / 50 (real framelength) = 120min 54sec (actual length)
Best regards, Christian
On 10.12.2009 09:41, Christian Tramnitz wrote:
Klaus Schmidinger schrieb:
You can take the size of the index file, divide it by 8 and you get the number of frames in the recording. The info file tells you the number of frames per second (at least with newer TS recordings).
I don't think this calculation is always accurate (i.e. for h264/HD recordings) right now. For a 1080i recording the info file contains "F 25" (shouldn't it be 50 frames for 1080i50?)
Example (recorded with vdr 1.7.10): # ls -la insgesamt 7219260 drwxr-xr-x 2 vdr vdr 59 28. Nov 15:04 . drwxr-xr-x 3 vdr vdr 38 22. Nov 20:12 .. -rw-r--r-- 1 vdr vdr 7389603764 22. Nov 22:13 00001.ts -rw-r--r-- 1 vdr vdr 2901984 22. Nov 22:13 index -rw-r--r-- 1 vdr vdr 681 22. Nov 20:12 info
# grep "^F\ " info F 25
2901984 (size of the index file) / 8 = 362748 (frames) 362748 / 25 (framelength according to info) = 241min 49sec (wrong!) 362748 / 50 (real framelength) = 120min 54sec (actual length)
Can you give me link to a one minute recording where I can see this?
Klaus