[mythtv-users] Failed radio recordings from dvb-t with 0.26-fixes

[Roger Siddons]

On Wed, 24 Apr 2013 15:39:33 +0100, John Pilkington <J.Pilk at tesco.net>  
wrote:
>
> Something else that is broke now - sometimes - is Audio track selection  
> in my mythDVBcut script.  This is new.  I use
>
> mythffmpeg -i "filename" 2>&1 | grep -C 4 Video > tmp.txt
>
> to find out what's there and grep for Audio  and Video.  Now I'm seeing
>
>> [mpegts @ 0x185e140] Could not find codec parameters (Audio: mp3, 0  
>> channels, s16)
>> [NULL @ 0x1862280] start time is not set in estimate_timings_from_pts
>> Input #0, mpegts, from '1072_20130424093100.mpg':
>>   Duration: 00:26:57.37, start: 51109.892644, bitrate: 1880 kb/s
>>     Stream #0:0[0x1ab1]: Video: mpeg2video (Main), yuv420p, 544x576  
>> [SAR 32:17 DAR 16:9], 15000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc
>>     Stream #0:1[0x1ab2](eng): Audio: mp2, 48000 Hz, stereo, s16, 128  
>> kb/s
>>     Stream #0:2[0x1ab3](eng): Audio: mp3, 0 channels, s16
>>     Stream #0:3[0x1ab6](eng): Subtitle: dvb_subtitle
>> At least one output file must be specified
>
> and the complaint in the first line, which I haven't seem before, breaks  
> it.  Just changing the grep -C 4 may fix it.   It seems quite possible  
> that the radio recording failure has a similar origin...
>

FWIW I've been using 0.26 on DVB-T (incl Radio 4) for 5 months with no  
significant issues (apart from 10833).

However your latter issue does remind me of one, possibly related,  
incident (that I haven't got around to investigating properly):
Successive recordings of the last hour of CBeebies failed to play (video  
buffer failed too many times) even though the filesize was good. The logs  
said Myth couldn't find any video codec parameters, I believe. However  
they would play fine whilst the recording was in progress. When my (3 min)  
padding recorded the MHEG data at channel end it somehow 'corrupted' the  
codec info so that the recording then became unplayable. Reducing the end  
padding solved that problem. That's obviously not the cause of your 9:30am  
failure but, to me, they raise questions about the 'new' ffmpeg in 0.26.  
Their forums may provide some clues...