On 1/7/06, <b class="gmail_sendername">Michael Haan</b> <<a href="mailto:michael.haan@gmail.com">michael.haan@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span class="e" id="q_108a6351e28116cb_0">On 1/7/06, <b class="gmail_sendername">Steve Adeff</b> <<a href="mailto:adeffs@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">adeffs@gmail.com
</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Saturday 07 January 2006 13:15, Michael Haan wrote:<br>> On 1/6/06, Michael Haan <<a href="mailto:michael.haan@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">michael.haan@gmail.com
</a>> wrote:<br>> > 5 of the 6 total recordings, and 4 of the last 4, made with my HD3000
<br>> > consistently freeze in the same exact spot. It looks to be associated<br>> > with a Prebuffering pause message and when it happens, mythfrontend<br>> > starts chewing-up memory until the OS shuts it down. Replaying the
<br>> > recording will produce the exact result in the same exact place.<br>> ><br>> > Some setup specifics:<br>> ><br>> > FC4 and Jarod's guide built about a month ago.<br>> > AMD64 3800+
<br>> > nVidia 6600GT, using XvMC<br>> > 4 250 SATA drives in RAID 5 configuration<br>> ><br>> > For what it's worth, using firewire seems almost flawless, so I don't<br>> > think it's my rig.
<br>><br>> At first, I thought this had something to do with XvMC, so I didabled it.<br>> Same exact thing happened in the same exact place. FWIW, this card has<br>> worked in this rig before under a previous incarnation, so it's something
<br>> software. Anyone?<br><br>I've noticed this lately too with a couple recordings I've made recently, I<br>think its due more to bad data being written since adding my 3rd tuner has<br>overloaded my single drive being used for my recordings.
<br>You say firewire seems to record ok, have you tried doing a manual record with<br>the dvb-tools apps to see if its Myth or something else?<br><br>--<br>Steve<br>_______________________________________________<br>mythtv-users mailing list
<br><a href="mailto:mythtv-users@mythtv.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div></span></div>
<br>Not for an extended time. I'll give that a try. Also, the other night I recorded two shows using both my hd3000 and my pvr-250. Both 3000 recordings froze, but the 250's were fine.<br>
</blockquote></div><br>So, I did a test capture tuning with azap and then played it back using mplayer. Sure enough, same problem. I did this three times and each time is "froze" in the same place. Looking at the logs, I see a ton of "a52: CRC check failed!" but it finally hiccups when this message appears:
<br><br>alsa-space: xrun of at least 0.119 msecs. resetting stream<br><br>Followed by:<br><br>Maybe you are playing a non-interleaved stream/file or the codec failed?4 0<br>For AVI files, try to force non-interleaved mode with the -ni option.
<br><br>And finally:<br><br>alsa-uninit: pcm closed<br><br>I tried using the -ni option and get all the sames messages, except the one about using the -ni option. Finally, I tried watching until just before the hiccup and then skipping forward. As before, this avoided the *freeze* however, unlike with myth where this would result in video with no sound, mplayer had both video and sound.
<br><br>Does that help to track this down?<br>