ExSphere wrote:They are both uncompressed data, but zarxgui will only accept YV12 data. ( sorry, im actually explaining this on a different computer than me own, so im trying to remember everything. ) And yea, the quality in screen shot's doesn't look too different, but it is there. You can notice it a lot more when it's in motion and a lot of my beta tester's have mentioned it to me. And I don't think it's lagarith itself, since when I render out lagarith in vdub I never get those issues. But I think I might just be out dated with amvapp and im due for a re download. So i'll give that a shot.
Thanks for all the help guys <3
Colorspace conversions (if only like 1 or 2, not 30) shouldn't make any visible impact unless you have eyes like an electron microscope. And colorspace conversions don't cause motion artifacting in any instance I know of - that screenshot was labeled mp4, are you sure you're not comparing a low-bitrate H.264 or Xvid copy, mayhaps?
But from that, I'm guessing Premiere's internal colorspace handling is the problem, which is what the Recompress option solves. It
forces Premiere to keep to RGB24 (or RGB32?) at all times, and not try to screw with shortcuts. And if Premiere is doing everything in RGB internally, and you have Lagarith set on YV12, you're still forcing Lagarith to do a colorspace conversion anyway - doing it after-the-fact with AviSynth and Uncompressed files won't make a difference, since Lagarith's colorspace conversion routines are
from AviSynth, if I remember correctly.