[vdr] vdr 1.7.4 HD-Recording not working

Klaus Schmidinger Klaus.Schmidinger at cadsoft.de
Wed Mar 11 17:53:26 CET 2009


On 11.03.2009 17:55, Oliver Bardenheier wrote:
> This didn't have any effect on the output:
> 
> Switching to arteHD:
> Mar 11 17:43:09 Coruscant vdr: [15517] cVideoRepacker: operating in MPEG1/2 mode                  
> Mar 11 17:43:12 Coruscant vdr: [15067] switching to channel 36                                    
> Mar 11 17:43:12 Coruscant vdr: [15518] TS buffer on device 1 thread ended (pid=15067, tid=15518)  
> Mar 11 17:43:12 Coruscant vdr: [15517] buffer stats: 138556 (6%) used                             
> Mar 11 17:43:12 Coruscant vdr: [15517] receiver on device 1 thread ended (pid=15067, tid=15517)   
> Mar 11 17:43:12 Coruscant vdr: [15544] receiver on device 1 thread started (pid=15067, tid=15544)
> Mar 11 17:43:12 Coruscant vdr: [15545] TS buffer on device 1 thread started (pid=15067, tid=15545)
> Mar 11 17:43:12 Coruscant kernel: stb6100_set_bandwidth: Bandwidth=39700000                       
> Mar 11 17:43:12 Coruscant kernel: stb6100_get_bandwidth: Bandwidth=40000000                       
> Mar 11 17:43:12 Coruscant kernel: stb6100_set_frequency: Frequency=1611000                        
> Mar 11 17:43:12 Coruscant kernel: stb6100_get_frequency: Frequency=1610982                        
> Mar 11 17:43:12 Coruscant vdr: [15544] TS continuity error (8)                                    
> Mar 11 17:43:12 Coruscant vdr: [15544] TS continuity error (9)                                    
> Mar 11 17:43:12 Coruscant vdr: [15544] cVideoRepacker: operating in H.264 mode                    
> Mar 11 17:43:12 Coruscant vdr: [15544] cAudioRepacker(0xC0): skipped 216 bytes to sync on next audio frame
> Mar 11 17:43:12 Coruscant vdr: [15544] SetBrokenLink: no GOP header found in video packet                 
> Mar 11 17:43:12 Coruscant vdr: [15544] PES packet shortened to 5606 bytes (expected: 6158 bytes)          
> 
> 
> 
> starting recording:
> 
> Mar 11 17:43:43 Coruscant vdr: [15067] switching device 1 to channel 36
> Mar 11 17:43:43 Coruscant vdr: [15067] timer 21 (36 1743-2043 '@TITLE EPISODE') start
> Mar 11 17:43:43 Coruscant vdr: [15067] Title: 'Mit Schirm, Charme und Melone' Subtitle: 'Einmal Venus hin und zur�ck'
> Mar 11 17:43:43 Coruscant vdr: [15067] record /video/@Mit_Schirm,_Charme_und_Melone_Einmal_Venus_hin_und_zur�ck/2009-03-11.17.43.36-0.rec
> Mar 11 17:43:43 Coruscant vdr: [15067] creating directory /video/@Mit_Schirm,_Charme_und_Melone_Einmal_Venus_hin_und_zur�ck              
> Mar 11 17:43:43 Coruscant vdr: [15067] creating directory /video/@Mit_Schirm,_Charme_und_Melone_Einmal_Venus_hin_und_zur�ck/2009-03-11.17.43.36-0.rec
> Mar 11 17:43:43 Coruscant vdr: [15067] recording to '/video/@Mit_Schirm,_Charme_und_Melone_Einmal_Venus_hin_und_zur�ck/2009-03-11.17.43.36-0.rec/00001.ts'
> Mar 11 17:43:43 Coruscant vdr: [15698] recording thread started (pid=15067, tid=15698)                                                                    
> Mar 11 17:43:43 Coruscant vdr: [15067] info: Aufzeichnung gestartet                                                                                       
> Mar 11 17:43:45 Coruscant vdr: [15067] max. latency time 3 seconds                                                                                        
> Mar 11 17:44:14 Coruscant vdr: [15698] ERROR: video data stream broken                                                                                    
> Mar 11 17:44:14 Coruscant vdr: [15698] initiating emergency exit                                                                                          
> Mar 11 17:44:14 Coruscant vdr: [15067] emergency exit requested - shutting down                                                                           

I did test recording with arteHD when I implemented the frame detector, and
back then it appeared to work (at least I got a *.ts and index file).
Maybe they changed something in their data format in the meantime.

I'll look into this as soon as I find the time.

Klaus

> -----Ursprüngliche Nachricht-----
> Von: vdr-bounces at linuxtv.org [mailto:vdr-bounces at linuxtv.org] Im Auftrag von Klaus Schmidinger
> Gesendet: Mittwoch, 11. März 2009 17:14
> An: vdr at linuxtv.org
> Betreff: Re: [vdr] vdr 1.7.4 HD-Recording not working
> 
> On 11.03.2009 17:03, Oliver Bardenheier wrote:
>> I just tried to record some HD but found that VDR is crashing after a few
>> secs.
>> Watching HD is no problem, but when going on record VDR exits.
>> First I though it was noad related, but I switched off any unneded plugin
>> and noad, still crashing.
>>
>>
>> I'm running opensuse 11.1 with kernel 2.6.27.17 and liplian sources.
>> (Skystar HD)
>>
>> Here's when I switch to 'arteHD', channel is shown and can be viewed.
>>
>> Mar 11 16:47:27 Coruscant vdr: [8767] switching to channel 36
>> Mar 11 16:47:27 Coruscant vdr: [8914] TS buffer on device 1 thread ended
>> (pid=8767, tid=8914)
>> Mar 11 16:47:27 Coruscant vdr: [8913] buffer stats: 120884 (5%) used
>>
>> Mar 11 16:47:27 Coruscant vdr: [8913] receiver on device 1 thread ended
>> (pid=8767, tid=8913)
>> Mar 11 16:47:27 Coruscant vdr: [9066] receiver on device 1 thread started
>> (pid=8767, tid=9066)
>> Mar 11 16:47:27 Coruscant vdr: [9067] TS buffer on device 1 thread started
>> (pid=8767, tid=9067)
>> Mar 11 16:47:27 Coruscant kernel: stb6100_set_bandwidth: Bandwidth=39700000
>>
>> Mar 11 16:47:27 Coruscant kernel: stb6100_get_bandwidth: Bandwidth=40000000
>>
>> Mar 11 16:47:27 Coruscant kernel: stb6100_set_frequency: Frequency=1611000
>>
>> Mar 11 16:47:27 Coruscant kernel: stb6100_get_frequency: Frequency=1610982
>>
>> Mar 11 16:47:28 Coruscant vdr: [9066] TS continuity error (13)
>>
>> Mar 11 16:47:28 Coruscant vdr: [9066] cVideoRepacker: operating in H.264
>> mode                  
>> Mar 11 16:47:28 Coruscant vdr: [9066] TS continuity error (6)
>>
>> Mar 11 16:47:28 Coruscant vdr: [9066] TS continuity error (9)
>>
>> Mar 11 16:47:28 Coruscant vdr: [9066] SetBrokenLink: no GOP header found in
>> video packet       
>>
>>
>> Now I start the recording and after 30secs I get the exit.
>>
>>
>> Mar 11 16:47:46 Coruscant vdr: [8767] switching device 1 to channel 36
>> Mar 11 16:47:46 Coruscant vdr: [8767] timer 21 (36 1647-1947 '@TITLE
>> EPISODE') start
>> Mar 11 16:47:46 Coruscant vdr: [8767] Title: 'Zu Tisch in ... Asturien'
>> Subtitle: ''
>> Mar 11 16:47:46 Coruscant vdr: [8767] record
>> /video/@Zu_Tisch_in_..._Asturien/2009-03-11.16.47.36-0.rec
>> Mar 11 16:47:46 Coruscant vdr: [8767] creating directory
>> /video/@Zu_Tisch_in_..._Asturien/2009-03-11.16.47.36-0.rec
>> Mar 11 16:47:46 Coruscant vdr: [8767] recording to
>> '/video/@Zu_Tisch_in_..._Asturien/2009-03-11.16.47.36-0.rec/00001.ts'
>> Mar 11 16:47:46 Coruscant vdr: [9170] recording thread started (pid=8767,
>> tid=9170)                                     
>> Mar 11 16:47:46 Coruscant vdr: [8767] info: Aufzeichnung gestartet
>>
>> Mar 11 16:47:48 Coruscant vdr: [8767] max. latency time 2 seconds
>>
>> Mar 11 16:48:17 Coruscant vdr: [9170] ERROR: video data stream broken
>>
>> Mar 11 16:48:17 Coruscant vdr: [9170] initiating emergency exit
>>
>> Mar 11 16:48:17 Coruscant vdr: [8767] emergency exit requested - shutting
>> down                                          
> 
> Looks like the frame detector doesn't kick in.
> Can you compile VDR with
> 
> static bool DebugFrames = true;
> 
> in remux.c and try again?
> What does it print to the console?
> 
> Klaus



More information about the vdr mailing list