[mythtv-users] Audio pitch and studder

[luitjens at cs.utah.edu]

Hi all,

After much searching and debugging I found the problem.  The problem is 
with the new video4linux package found on atrpms.  Video4Linux is not 
required by the newer kernels anymore so the fix is to just remove it 
(yum remove video4linux) and reboot.  As a recap the symptoms are choppy 
playback and chimpmunk voices.   To anyone using atrpms be wary of 
upgrading to the latest video4linux.

Justin

luitjens at cs.utah.edu wrote:
> Hi,  after a bit more of experimenting I have determined that the 
> entire recording is faster (thus the pitch is higher).  It is not a 
> playback issue but instead it is actually in the recording.  However 
> if I capture straight from /dev/video0 the speed is normal.  If i play 
> one of the recordings from myth in mplayer it is also fast.
> It seems like some setting in myth is making ivtv record at a 
> different rate.  Anyone have any ideas?
>
> Thanks
>
> luitjens at cs.utah.edu wrote:
>> The frontend is spewing a lot of information here is a bit of it:
>>
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 2 20
>> [mpeg2video @ 0x2de3724]slice mismatch
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 38 4
>> [mpeg2video @ 0x2de3724]00 motion_type at 29 8
>> [mpeg2video @ 0x2de3724]00 motion_type at 20 15
>> 2007-04-30 18:25:55.884 NVP: prebuffering pause
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 43 9
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 4 10
>> [mpeg2video @ 0x2de3724]invalid mb type in B Frame at 7 20
>> [mpeg2video @ 0x2de3724]00 motion_type at 44 19
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 29 12
>> [mpeg2video @ 0x2de3724]mb incr damaged
>> [mpeg2video @ 0x2de3724]00 motion_type at 23 21
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 35 0
>> 2007-04-30 18:25:59.654 NVP: prebuffering pause
>> [mpeg2video @ 0x2de3724]00 motion_type at 13 18
>> [mpeg2video @ 0x2de3724]invalid mb type in B Frame at 43 11
>> [mpeg2video @ 0x2de3724]00 motion_type at 32 13
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 4 22
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 31 27
>> [mpeg2video @ 0x2de3724]00 motion_type at 39 22
>> [mpeg2video @ 0x2de3724]00 motion_type at 43 21
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 44 3
>> [mpeg2video @ 0x2de3724]00 motion_type at 19 18
>> 2007-04-30 18:26:02.062 NVP: prebuffering pause
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 19 16
>> [mpeg2video @ 0x2de3724]00 motion_type at 8 9
>> [mpeg2video @ 0x2de3724]00 motion_type at 10 23
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 44 18
>> [mpeg2video @ 0x2de3724]00 motion_type at 39 9
>> 2007-04-30 18:26:05.385 NVP: prebuffering pause
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 15 9
>> [mpeg2video @ 0x2de3724]00 motion_type at 18 4
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 24 6
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 8 20
>> [mpeg2video @ 0x2de3724]00 motion_type at 24 21
>> [mpeg2video @ 0x2de3724]00 motion_type at 7 18
>> [mpeg2video @ 0x2de3724]00 motion_type at 9 14
>> [mpeg2video @ 0x2de3724]00 motion_type at 12 4
>> [mpeg2video @ 0x2de3724]ac-tex damaged at 43 26
>> [mpeg2video @ 0x2de3724]00 motion_type at 8 14
>> 2007-04-30 18:26:09.763 NVP: prebuffering pause
>> [mpeg2video @ 0x2de3724]00 motion_type at 12 20
>> [mpeg2video @ 0x2de3724]slice mismatch
>> [mpeg2video @ 0x2de3724]invalid cbp at 20 17
>>
>> If anyone has any ideas of what I could do to fix this I would be 
>> greatfull.
>> Thanks
>>
>>
>> luitjens at cs.utah.edu wrote:
>>> Hi,
>>>
>>> Last night i updated to the latest packages from atrpms and the 
>>> latest svn.  Since then I have seen a couple odd problems.  First 
>>> watching live tv causes a studder every couple seconds.  If i press 
>>> record then watch it in the recordings it doesn't have any problems.
>>>
>>> Second new recordings have a really high pitch everyone is talking 
>>> with munchkin voices.  And the voice seems to get higher the longer 
>>> the machine is on.  The time stretch is set at 1.0.  Old recordings 
>>> do not have this problem.
>>>
>>> Anyone seen any of these problems or know how to fix them?
>>>
>>> Thanks,
>>> Justin
>>>
>>
>