[vdr] VDR test series about frame detector

Jochen Heuer jogi-vdr at planetzork.ping.de
Thu Jan 16 17:36:56 CET 2014


Whoops, this was meant to go to Eike only therefore I wrote it in German ...

Basically 6 would be sufficient for 98.5% and 10 for 99.5% on my system.

Best regards,

   Jogi

On Thu, Jan 16, 2014 at 05:32:33PM +0100, Jochen Heuer wrote:
> Hallo,
> 
> anbei mal die Infos über mein Archiv (~1.6 TB - 100MB Maxsize):
> 
> 5  : 9455
> 6  : 6132
> 7  : 57
> 8  : 52
> 9  : 36
> 10 : 23
> 11 : 16
> 12 : 20
> 13 : 6
> 14 : 8
> 15 : 8
> 16 : 6
> 17 : 4
> 19 : 1
> 83 : 1
> 
> ich denke, mit 6 hätte man bereits den Großteil erschlagen (>98.5%) und mit 10
> ist man sogar bei >99.5%.
> 
> Und wer weiß, ob die mit 83 nicht sogar einfach nur defekt ist ...
> 
> Gruß,
> 
>    Jogi
> 
> 
> On Tue, Jan 14, 2014 at 09:34:07PM +0100, Eike wrote:
> > Hello!
> > 
> > I need some help from VDR users - for variety reasons especially from those not in Germany.
> > There's a glitch in the frame detection of VDR. It sometimes misses the first possibility to record a stream. 
> > It looks on frames of at least 5 * 188 bytes, and depending on the stream, sometimes 6 frames are needed. 
> > Trouble is, I'm not sure if 6 is enough for everybody. Thus I need your tests.
> > 
> > You need ot be able to compile a VDR to help. First, in the VDR directory, you do a:
> > > make
> > 
> > Then you compile the attached C++ file (unziped, of course):
> > > g++ -c framedetectortest.cpp
> > 
> > Then you're linking it:
> > g++ -o framedetectortest framedetectortest.o remux.o ringbuffer.o thread.o tools.o i18n.o sections.o channels.o device.o audio.o ci.o receiver.o transfer.o player.o osdbase.o 
> > status.o skins.o osd.o config.o font.o sources.o menu.o recording.o videodir.o timers.o epg.o dvbplayer.o menuitems.o remote.o keys.o interface.o plugin.o cutter.o themes.o 
> > svdrp.o eit.o eitscan.o shutdown.o filter.o sourceparams.o dvbsubtitle.o pat.o sdt.o nit.o dvbdevice.o diseqc.o recorder.o dvbci.o libsi/libsi.a -lfontconfig -lfreetype -lpthread -ldl -
> > ljpeg
> > 
> > Now you've got an application called framedetectortest, which you can feed your vdr recordings (*.ts files) to:
> > > ./framedetectortest 00002.ts
> > 
> > The output looks about like this:
> > 
> > Checking file at offset 0
> > Without frame limit... Found I frame after 99452 bytes
> > With frame limit 5... Found I frame after 220336 bytes
> > With frame limit 6... Found I frame after 99452 bytes
> > TS package frame size needed for this video block: 6
> > Maximum TS package frame size needed for this video recording: 6
> > 
> > I need reports which number your stream resulted in (the "Maximum TS package frame size") and what you've tested 
> > (Cable? Satellite? Terrestrical? HD, SD? Your country?). The result is interesting even if it is 5 or 6.
> > 
> > Thanks in advance,
> > Eike
> 
> 
> 
> 
> 
> > _______________________________________________
> > vdr mailing list
> > vdr at linuxtv.org
> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
> 
> 
> _______________________________________________
> vdr mailing list
> vdr at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
> 



More information about the vdr mailing list