[Paul Goelz]

I think you mis-understand. I rendered the SAME levels (computer RGB) to the three codecs and got the same results from each. Each one, when the rendered file was placed on the timeline yielded precisely the same levels as the source. So far, so good.

The problem I am trying to work through is that while the waveform monitor seems to be saying that I am outputting and rendering computer RGB levels…. and the rendered files CONTAIN computer RGB levels, when those rendered files are played back outside of Vegas, they seem to play back as if they were expecting studio RGB. That doesn’t make sense given the fact that the same file placed on the timeline shows computer RGB levels. Why doesn’t it play back that way?

One possibility is that my monitor is not calibrated properly and I am simply chopping off the last 7.5% when I play a file in Media Player. However, it displays a built in test pattern (part of the nVidia control panel) correctly. And the Vegas preview window (viewed on the same monitor) correctly shows all gray steps down to the lowest on the pluge…. 1% maybe?

Is there any way I can check my monitor calibration with tools available in Vegas or Photoshop? For example, how about I grab a frame from the pluge and examine it in Photoshop. If it contains the correct levels but they don’t display correctly on my monitor when the file is played, is this just a monitor issue?

Or am I totally mis-understanding the basics….. when presented with a file containing pluge and porch, SHOULD I be able to see all the grey levels during playback on a PC monitor? Like I said, it plays it back as if it was expecting studio RGB…. the 1% (?) and the 7.5% steps are totally black. All others are visible.

Another possibility is that I am not correctly setting or interpreting the waveform display. Both boxes are unchecked. I am assuming that sets it up for computer RGB and in fact, I cannot drive the waveform below 0 or above 100 with the color corrector tool even though the scale extends beyond 0-100.

Thanks for bearing with me. I’d like to get this right.

Paul

[Paul Goelz]

Let me summarize for clarity. Or at least try 😉

I created a project with two seconds of generated “pluge and porch” with the levels set for computer RGB (0% = black and 100% = white). All shades of gray were visible in the preview window.

I then rendered this to three different output formats…. MPEG2 with the YouTube preset, Sony AVC with the YouTube preset and to DV-AVI.

All three renders were placed on the timeline and the preview window and the waveform monitor confirmed that the levels were identical to the original.

All three were played…. the MPEG2 and DV-AVI in Media Player and the Sony AVC in the Quick Time player. All three showed the lower two shades of gray to be black as if the player was expecting NTSC video levels.

This seems to indicate that any level issues I am having are in playbeack and not in rendering, regardless of the codec used??

So…. what to do? Is the easy answer to simply re-adjust my levels to NTSC with 7.5% setup? Easy to do, but is that the correct way to do it? It kinda makes sense, since I have a two part goal…. upload to YouTube and also burn to DVD. Setting levels to 7.5% = black would seem to accomplish both goals?

Paul

[Paul Goelz]

OK, I’m back with another question or two.

I rendered a couple projects to Sony AVC and uploaded them to YouTube. And discovered that YouTube treats them differently than it does MPEG2 uploads for some reason.

They all started out as 720 X 480 and rendered as such. But the MP4 uploads ended up slightly lower resolution than the identical project rendered as MPEG2 and uploaded. I have not looked at the files closely yet…. it may be that they rendered differently.

But I also noticed something else after I rendered a couple seconds of one of the projects to MPEG2 and MP4 using a couple different bitrates each and uploaded them to YouTube. The bitrate affected how YouTube displayed them too. The higher bitrate MP4s displayed with lower resolution. Again, it might be how they actually rendered…. there may be differences in the size of the video vs. the frame size when it renders.

But the last thing I noticed was that there was essentially NO LEVEL DIFFERENCE between the Sony AVC and the Main Concepts MPEG2 renders. They were both rendered from the same project, which was set for computer RGB levels. The MPEG2 was slightly darker but it was so slight that I had to run them both side by side on the same monitor to see it. I’d say maybe 1% at most. So what’s all the fuss about using the correct levels for MPEG2 vs. Sony AVC? There doesn’t seem to be an observable difference in levels, and if anything the MPEG2 was a bit sharper than the Sony AVC at 6Mb/s.

I then created a project with generated media “pluge and porches”. I rendered that to Main Concepts MPEG2, Sony AVC and DV-AVI and found zero difference in levels between any of them when they were added to the timeline and examined with the waveform monitor. I did note, however, that on the preview screen all shades of grey were easily visible. But when played back using Medial Player or QuickTime, only the 10% level was visible. The two below that were solid black. This behavior was identical for all three renders (MPEG2, MP4 or DV-AVI). What am I missing?

Paul

[Paul Goelz]

Later that very same day…..

Worked fine. Thanks. It still amazes me how utterly complicated and initially incomprehensible digital video editing is. It is, after all, just a series of still photos shown in rapid succession.

BTW, I didn’t bother with putting a separate color corrector on the master video track. I just set the waveform monitor to computer RGB levels and used the color corrector on the video track to set levels like I usually do. It was a bit confusing at first because the waveform monitor was set to computer RGB but still displayed reticle markings above and below 100%. But since the waveform never went beyond 0-100% I assume the “headroom” isn’t really there in the computer RGB waveform display.

At the same time I calibrated both my monitors as best I could and now everything seems to track much better, especially because using computer RGB levels, the preview window is also correct.

Paul

[Paul Goelz]

I’d be curious to know the circumstances of those crashes. I’ve been trying to pinpoint the cause of crashes in Vegas 9.0c and 9.0d when editing text media items.

Paul

[Paul Goelz]

Now ya tell me 😉 I’ll try that workflow and see how it goes. Thanks! I’ll be curious to see if it renders faster or slower to Sony AVC vs. MPEG2. I have to use NeatVideo on most of my old stuff and it is veeerrryyyy slow to begin with.

Paul

[Paul Goelz]

I agree, very strange. And I think it is relatively new too…. I don’t recall seeing it months ago.

No, it isn’t necessarily as you suggest on very long projects. For example, this evening after not being able to get the color corrector FX to do anything, I found a keyframe all the way at the right end of the single clip on the timeline. No idea how it got there. It showed up on the FX timeline too, and the cursor was all the way to the left where it belonged. It was the only keyframe…. IOW, it was the keyframe that normally is at the left side of the timeline but it was all the way to the right. Weird?

I am also recently having an issue where Vegas crashes when editing text media items. This too is relatively new, but I can’t see any possible connection.

Paul

[Paul Goelz]

Unfortunately, I tried this fix and it didn’t work. I copied the 9.0C (32 bit) version of aviplug.dll from an archived 9.0C (32 bit) installation into the same folder in the 9.0D (32 bit) installation and it didn’t solve the slow project load.

Reverting to Vegas 9.0C did 😉

Paul

[Paul Goelz]

Unfortunately, I am already aware of that. Sync Cursor is OFF and the cursor in the FX window is always at the far left. But occasionally, I get keyframes in the middle of the timeline. Sometimes I notice them in the FX window and more often I notice them in the keyframe line in the main edit window. I suspect they are where the main cursor was when I either opened the FX window or perhaps where it was when I changed an FX parameter. But like I said, the cursor is at the far left of the FX window timeline, so there shouldn’t be any keyframes generated anywhere else, right?

This seems like a bug?

Paul

[Paul Goelz]

Addendum…. since resetting Vegas, projects sometimes load quickly. But sometimes the same project will load just as slowly as before I reset it. Haven’t found a definitive pattern yet.

Paul