New Concern-Major In My Book!

Jay Gladwell wrote on 4/19/2005, 2:09 PM

Please, some others of you try this to see if you get the same results.

In V5, I opened a clip, adjusted color curves and color corrected (using a Sony NTSC studio monitor). Rendered to .avi file. Kept the veggie on the timeline and put the rendered .avi file beneath the original veggie from whence it was rendered.

When turning the "solo" button off and on using the lower, rendered .avi track (alternating between the corrected veggie on top and the rendered .avi file below ), there is, of course no difference whatever to be seen.

However, when I did this same thing, using the same clip, same corrections, and rendered out to .avi in V6, and turned the "solo" button off and on there was a clearly visible difference between the two! The rendered .avi file was noticeably more saturated. This, to me, is unacceptable.

Please me know if this happens to you as well.

Thanks!


Comments

jlafferty wrote on 4/19/2005, 2:22 PM
Is it that you're seeing compressed frames from one and not the other?

Not seeing any problem here. I rendered a clip with color corrector and color curves, then dropped the clip beneath the source. Switching between the two they look exactly the same.

Or are you suggesting renders in V5 look different than those in V6?

- jim
Jay Gladwell wrote on 4/19/2005, 2:25 PM
Is it that you're seeing compressed frames from one and not the other?

No.

Or are you suggesting renders in V5 look different than those in V6?

I'm not "suggesting" anything. I'm saying flat out what I am seeing. I'm seeing that a file rendered in Vegas 6 has a greater saturation than the original, corrected file from which it was rendered.

When a clip is color corrected then rendered, there should be absolutely difference between the two. But that is exactly what I am seeing with Vegas 6, and that is unacceptable to me.


jlafferty wrote on 4/19/2005, 2:27 PM
That's what has me confused -- are you dropping a file rendered in V5 onto the V6 timeline? Or are you rendering from V6, then dropping that back into V6 underneath the source event?
FrigidNDEditing wrote on 4/19/2005, 2:33 PM
and, are you using a nested Veg - or a doing everything from scratch in terms of correcting color?
Marco. wrote on 4/19/2005, 2:35 PM
Tried to reproduce it. Can't. On my system a color-corrected and rendered clip looks exactly same compared to the unrendered clip with filter applied.

Marco
Jay Gladwell wrote on 4/19/2005, 2:35 PM

I opened V5, corrected the clip and rendered it in Vegas 5. Both were identical. Everything in 5 stayed in 5.

I opened V6, corrected the clip and rendered it in Vegas 6. Both were not identical. Everything in 6 stayed in 6.

No, no nesting.

jlafferty wrote on 4/19/2005, 2:36 PM
Yeah. Can't help you there, then. Looks OK to me.

- jim
Jay Gladwell wrote on 4/19/2005, 2:46 PM

Now, it's not doing it!

That's the good news.

The bad news is I don't know what I did differently!!!


vitalforce2 wrote on 4/19/2005, 2:59 PM
Are your monitor connections and control buttons good and solid? ;)
BrianStanding wrote on 4/19/2005, 3:22 PM
Firewire connections good and solid, too?

On my NTSC monitor, I have a switch on the back to allow passthrough to a second monitor. If I accidentally leave it on and don't have a BNC connection to the second monitor, I get wildly unpredictable monitor behavior.

Don't know if this helps.

You're not wearing sunglasses, are you? ;-)
rmack350 wrote on 4/19/2005, 3:57 PM
You're talking about monitor termination. Yep, that's important.

Here's a wild guess. Could Vegas have been using the MS DV codec? I doubt that you'd do it on purpose but there are prefs settings to allow it.

Rob Mack
epirb wrote on 4/19/2005, 4:11 PM
Jay sounds like you might of had Correctile-Dysfunction!
Its OK it happens to all of us sometime......

I tried it out and all looks good to me,in V6.
Let us know if it happens again, if symtoms persist ....see your Doctor.
: )
goshep wrote on 4/20/2005, 6:14 AM
Corrections lasting more than four hours.......never mind.