>> As for the motherboard, its<br>
>> an abit, however, my last board didn't have a nforce chipset either.<br>
<br>
>I didn't say NForce chipsets were the only ones that do DMA properly,<br>
>they just seem to be the only one that do it consistently. With a VIA/<br>
>SIS chipset, it's a crapshoot to see if you get a good one or a<br>
>terribly buggy one. Even with the major brands like Asus/MSI/<br>
>Gigabyte/etc.<br>
<br>
>> Thanks for the info about DMA - I'll look into it - perhaps moving<br>
>> the tv board (PCTV Rave) to another slot may make the difference....<br>
<br>
>Good luck, but I don't expect it will change anything.<br>
<br>
You didn't mention anything about xawtv - as mentioned, I can get full screen with no glitches?<br>
<br>
As a matter of interest, here's the command line I use (in a batch
file) to perform the record - can you see any areas / parameters that
might improve the situation? (When I'm recording, I get a) jerky
frames, but also b) occasional frames that appear 'moved' - e.g. a
person will be standing on the left hand side of the screen, and for a
split second they appear in the middle - it's like the synchronisation
of the screen was off?<br>
<br>
Anyway, here's the command line:<br>
<br>
nice -5 mencoder -tv
driver=v4l:width=720:height=576:input=1:amode=1:adevice=/dev/dsp:forcechan=2:volume=50
-endpos $2:$3:00 -oac mp3lame -ovc lavc -lavcopts
vcodec=mpeg4:vqmin=2:vqscale=2 -o $1.avi tv://<br>
<br>
- the programs run under root, so I can 'nice' the task to have a higher priority <br>
Param 1 ($1) = name of output file<br>
Param 2 = hours to record<br>
Param 3 = minutes to record.<br>
<br>
My old command line is:<br>
nice -5 mencoder -tv
driver=v4l:width=640:height=480:input=1:amode=1:adevice=/dev/dsp:forcechan=2:volume=50
-endpos $2:$3:00 -oac copy-ovc lavc -lavcopts vbitrate=1800 -o
$1.lavc tv://<br>
<br>
Which gives a larger file - also recording at 640 x 480, but still exhibits the same problems....<br>
<br>
Thanks<br>
<br>
Carl.<br>