[mythtv-users] Corruption with Mythfrontend on 2GB+ recordings

[Randall Blecher]

Has anyone else been experiencing corruption when playing back
recordings that are greater than 2 GB with Mythfrontend on a remote
frontend?  Up until about 2GB into recordings, mythfrontend skips
around a lot and spits out errors:

[mpeg2video @ 0xb737fa80]warning: first frame is no keyframe
2006-02-17 21:56:21.528 WriteAudio: buffer underrun
[mpeg2video @ 0xb737fa80]mb incr damaged
[mpeg2video @ 0xb737fa80]00 motion_type at 0 8
[mpeg2video @ 0xb737fa80]00 motion_type at 0 9
[mpeg2video @ 0xb737fa80]00 motion_type at 0 10
[mpeg2video @ 0xb737fa80]00 motion_type at 0 11
[mpeg2video @ 0xb737fa80]00 motion_type at 0 12
[mpeg2video @ 0xb737fa80]slice mismatch
[mpeg2video @ 0xb737fa80]00 motion_type at 0 14
[mpeg2video @ 0xb737fa80]00 motion_type at 2 15
.
.
.

If I try playing the recording on the Mythfrontend that is local to
the master backend (i.e. not accessing the recording over the network)
or by accessing the file remotely from an NFS mount in Xine, I have no
problems.  So I don't think the file is actually corrupted.

I just recently upgraded to 0.19, so I'm wondering if this is a bug in 0.19.

Thanks,

Randall