ATI AIW128pro and huffyuv problem

[cguk]

Hi..

I've just been capturing some footage in Pal D1 (720 x 576) using the
huffyuv codec.

I am capturing fine .. at 25 fps i get no dropped frames (p3 833 fast AV
ATAdrive using vdub) .. but when i come to look back at the avi it is only displaying
like 1 frame a sec sometimes worse.. and very irregular...

Now the thing is I can look at these files in premiere preview windows, and they look fine apart from a wierd effect all over them.. and when I then edit and render them back to, say a VCD standard, they are fine.. so all the information is there and in good quality.. its just that I cant view the source avi files directly very well.

Has anybody any ideas why this is so?

I have just wiped down the video computer a few weeks ago.. and although I couldn't quote totally accurately, I believe I had taken some pal d1 captures in the past with this codec without seeing this problem...


Any ideas would be greatly appreciated..

Cheers

Chris

[kinneera]

Huffyuv is not a codec optimized for playback. Is there some particular reason you need to be able to actually play the source AVI prior to encoding?

[cguk]

Hi Kineera...

Thanks for responding...

I am actually capturing video in the largest format I can for the benefit of editing purposes... I.e. putting together movies from several sources of footage in Premiere.

I understand that Huffyuv is the best lossless codec out there, so thats the one i went for. I can capture and playback at smaller screen resolutions no problem, it's just this Pal D1 size that it struggles with on playback. I know the data rate was 20MB a second.. but my computer should be able to handle that easily.

I can live without looking at the avi's directly, because like I said I can view them in premiere.. but still... even then the files show up with funny aliases everywhere... until they are rendered down..


Thanks anyway.. I'll keep looking into it..


Chris

[kinneera]

I can understand your frustration. Unfortunately, it's not so much the data rate or any other factor so much as the fact that the codec apparently just isn't written for real-time playback of high resolution video. It's safe to assume this is the case because it obviously is intended as an intermediary codec.

I wonder if the "funny little aliases" you refer to are interlacing artifacts? This would be expected when dealing with full D1 video, and would disappear if rendered to half the vertical resolution.