Ok now seriously

[meleechampion]

What the crap is this?!



Exporting uncompressed doesn't do that. So what goes wrong when I use huffy or lag?

[Slash]

I have this same problem with vegas. (but then i restart and its not there so thus i r happy face)

[Corran]

Any other details?

Resolution, Colorspace, etc?

[mirkosp]

NLEs generally have issues with properly handing colorspace conversions, but even when they do not have to go through those, errors in the export are still possible to happen with lossless codecs. As you already know, exporting uncompressed works, but as for your question, which is what goes wrong with lags/huffy, well, I'm not sure. Colorspace conversion would be my bet, but even if you set everything properly it can still happen - NLEs work in RGB32 only, AFAIK, so perhaps putting a converttoRGB32() line in your scripts and exporting as RGB32 and not YV12 might do the trick? Not too sure though, since the issue might still be there. I guess you're better off biting the bullet and just exporting uncompressed as you're already doing without asking yourself questions, perhaps.

[Qyot27]

What is the format of the footage you're editing with?

Those are very specifically errors from Lagarith - if it shows up in HuffYUV then it's because Lagarith was used at some other part of the process (for instance, if the footage in your editor was in Lagarith but you exported in HuffYUV); HuffYUV's errors don't look like that. It just happens sometimes. Using RGB24 or RGB32 can help the responsiveness and compatibility in the editor, but I'd still recommend the source footage being HuffYUV or Uncompressed. Lagarith is fine for archiving, but I tend to have problems with it if I try to use it as source.

I use Premiere 6.5 on XP, though.