Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro NTSC-DV quality difference from Veg8 to Veg9?

  • NTSC-DV quality difference from Veg8 to Veg9?

    Posted by Dale Spetz on July 31, 2009 at 3:29 pm

    I recently switched from a 32-bit system with Vegas8c to a new 64-bit system with Vegas9a-64bit.

    While rendering to NTSC-DV, I seem to be getting inferior results with my new 64-bit system. The NTSC-DV settings seem to be the same on the old and new system.

    Could Vegas have changed the NTSC-DV codec between Vegas8c and Vegas9a, or is this a 64-bit system anomaly?

    This is very frustrating. Does anyone know what might be causing this difference?

    Mike Kujbida replied 17 years ago 2 Members · 7 Replies
  • 7 Replies
  • Mike Kujbida

    July 31, 2009 at 3:33 pm

    Dale, I haven’t notice any difference.
    Can you be more specific about what “inferior” means?
    Can you post screen shots to demonstrate this?

  • Dale Spetz

    July 31, 2009 at 4:10 pm

    These are sort of small to compare, but I believe that you can see that the bottom image (Vegas9a) is a bit less-sharp than the Veg8c render, above. As far as I can tell, the settings are the same for both.

  • Mike Kujbida

    July 31, 2009 at 7:04 pm

    You’re right Dale.
    Those are small screen grabs 🙁
    Next time, set your Preview Window to Best/Full and then grab a frame.
    I brought the images into Photoshop, zoomed in 300% and can see a slight quality difference but I an’t trust the results of such small screen grabs nor can I trust an image that’s been altered, especially if you’re not positive that you used identical settings..
    If you can post those same images without any FX on them and done at Best/Full, that would be much better.

  • Dale Spetz

    August 1, 2009 at 1:14 pm

    OK These may not be the most dramatic examples, but are slight color bumps and artifacts that jump in, on the Vegas9-64bit renders (lower image with circles).

    Granted, they are not extreme, but they are there.

    Now, the original HDV footage was captured with Vegas8c-32bit. Would this make a difference?

    The gist of it is, I am trying to move my Vegas8c projects over to my new Vegas9a-64bit system—mainly to gain render speed. But, I can’t do so, if I will be losing any quality.

  • Mike Kujbida

    August 1, 2009 at 4:33 pm

    Dale, I’m not aware of any codec changes between the two versions.

    Are the properties in the V9 project set to 32-bit floating point?

    While I can see the differences, I’m wondering if you’re being too fussy as they’re not objectionable to me.
    I’ve “been there, done that” so I don’t say this as a joke.

    Try showing the clip to someone else and see if they see what you see.
    Just tell them you’re interested in the picture quality without being specific.

  • Dale Spetz

    August 1, 2009 at 4:52 pm

    They are, admittedly, relatively minor, but they are new and do not occur on my older system.

    What I have done, temporarily, is install Vegas8.1 (64bit) on my new Vista 64-bit system. So far, it seems to co-exist fine with Vegas9a, on the same computer.

    Vegas8.1 almost renders NTSC-DV well (like old system), except it throws pulsating artifacts onto the bright reds (fixed previous problem, but created new problem). So, even if the NTSC-DV is the same in each version of Vegas, I am concluding that each renders differently. Or, the new 64-bit system is making the NTSC-DV codec behave differently. Or both.

    Anyway, I have now tried using the Cineform 5.1.4 codec for SD 4:3 and it seems to render very well, on each version of Vegas on the Vista 64bit system. Perhaps this is the answer until I complete my old Vegas8c originated projects.

    Thanks for your replies, Mike.

  • Mike Kujbida

    August 1, 2009 at 4:54 pm

    You’re welcome Dale.
    I just wish I had more suggestions for you but you seem to have a good handle on things.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy