VOTE: Easy Preview Button

Comments

farss wrote on 12/5/2012, 3:43 AM
"Isn't that what would happen if Vegas were to "handle levels conversions automatically"? "

Simple answer:

No.

Ppro does handle levels automatically and for your video the outcome is exactly the same as Vegas

For JPEGs where the levels are 0-255 Ppro maps the levels to match your video.

If you didn't know what you were doing with Vegas your still images could very easily end up clipped So in fact Vegas is more likely to give you the problem you're worried about.

Bob.
TeetimeNC wrote on 12/5/2012, 4:25 AM
In Vegas how do you handle something like the "Fade through Black Dissolve" transition which fades through 0 rather than 16?

EDIT: Duh, just create a preset for legal black.

/jerry
WillemT wrote on 12/5/2012, 4:44 AM
The "Dissolve" transition allows you to set the fade through color to anything you like - eg 16,16,16 (I mean .06,.06,.06 or something stupid like that) for black.

Edit: I really like and appreciate the 16/16/16 type entry .dll - many thanks to the author. All we need now is a three decimal awareness in Vegas.

Willem.
TeetimeNC wrote on 12/5/2012, 4:54 AM
>I personally would find automatic source manipulation confusing and distracting because I already know what to expect and what to look for. I actually enjoy working with this stuff. Others probably don't care about any of that; just how it will look in a player.

---

@musicvid, perhaps there is a semi-automated technique that could work in Vegas. What if SCS gave you the option to manually reflag your project media's color space? It could work something like this:

1. When you import your media it could be sorted by color space flag.
2. Vegas would provide the option of respecifying the color space for selected media. For example, if my video cam shoots 16-255 but it gets flagged as 16-235, I could respecify all those clips in one step.
3. Now, given that all media are correctly flagged, wouldn't that resolve concerns about Vegas automatically handling levels (as is claimed that other NLE's do)?

/jerry
Marco. wrote on 12/5/2012, 5:01 AM
"All we need now is a three decimal awareness in Vegas."

I think actually Vegas Pro takes care of even more then three decimals when using the 0-1 values (but it doesn't display all the decimals it uses).
farss wrote on 12/5/2012, 5:06 AM
Jerry,
I was just about to start a new thread about much the same concept .
Regardless, why don't you put this forward in a new thread, this thread is getting too cluttered and diverting attention from Musicvid's excellent idea.

Bob.
WillemT wrote on 12/5/2012, 5:34 AM
@Marco

I played around with it a bit, using a much larger display of the waves scope, and I think you are correct.

Should check things a bit more carefully before posting. Ignore that part of my post.

Willem.
TeetimeNC wrote on 12/5/2012, 6:04 AM
@Bob, good idea - new thread started.

/jerry
Rory Cooper wrote on 12/5/2012, 6:24 AM
As GlennChan said this stuff is too hard even for advanced Vegas users.

I need to have a big red switch COMPOSITING // EDITING in Vegas

If I am in the compositing mode using layers with video and graphics Vegas treat everything as 0 – 255
If I am in editing mode Vegas treats everything as 16 – 235

So if I start a new EDIT project I pull in a nested COMPOSIT veg Vegas will treat the composite correctly and render the final levels automatically.

The preview should then reflect the 2 modes WYSIWYG

+1 for me.

Seriously as an editor I want to spend my time on creative flow, timing, look and feel etc not on chasing my tail.
at this point brain surgery is 10 IQ levels below video editing.

Hey so what do you do?
actually I bombed out of video editing and am at present doing brain surgery….awe shucks man that sux.
GS1966 wrote on 12/5/2012, 7:01 AM
Final Cut Pro is one NLE that can rescue superwhites

Very often, in different languages it is possible to meet the similar phrase. Unfortunately always it only words (slogans), without concrete examples (for example original and processed video).
I very much want to look as FCP can pull out 'super white' and compare as it will make our Vegas...
Digital formats allow no more than 10% excess of a maximum level in 100 IRE then the signal is rigidly limited to absolutely white value. In analog Betacam SP formats the signal exceeding a maximum even for 20% (120 IRE), can contain details still. And at installation of analog recordings it can be "squeezed" to allowed level and to restore details in the brightest places of the image.
For the analog equipment the most admissible level of illumination makes 110 IRE (it is defined by characteristics of electronic blocks of the camera and the VCR).
At digital shooting the signal exceeding 110 IRE, becomes purely white. In it doesn't remain any details which could be restored then.
If it is necessary, Vegas also allows to process and keep all 'super white' (within YUV color space). Any problems in projct '32-bit video levels'
'32-bit full range' - I don't know precisely for what this mode is intended and as it has to work, but I suspect that it is intended for image sequence processing

Now I can open on TL a set of various formats simultaneously - AVCHD, MOV, stills (photo and snapshots) of etc
to lead levels to a uniform denominator (depending on an output format) and to receive video with the necessary levels. For this purpose in Vegas there is all necessary: videoscopes and prewiev on exsternal monitor.
Whether automatic equipment will be able to foresee all possible options - I doubt.
Therefore I against hasty revolutions
Marco. wrote on 12/5/2012, 8:53 AM
"Any problems in projct '32-bit video levels' '32-bit full range' - I don't know precisely for what this mode is intended and as it has to work, but I suspect that it is intended for image sequence processing"

One of the two main purposes of float point processing (doesn't matter if you use video level or full range here) is to avoid clipping during any kind of processing with as little loss (due to rounding errors) as possible.

You can exceed both white and black levels more than a hundred times and you stil will be able to restore any information.
Though it is unlikely you get your signals treated that hard - if you do intesive gradings, use light fx and maybe even combined with further compositing it is likely you do raise your levels much over white or much below black with the one process and vice versa with another process. A big disaster within integer bit processing. No harm if you use float point processing.
GS1966 wrote on 12/5/2012, 11:25 AM
Thank you Marco
Small specification. It is necessary to read so:
If it is necessary, Vegas also allows to process and keep all 'super white' (within YUV color space). Any problems in project '32-bit video levels'.
and
'32-bit full range' - I don't know precisely for what this mode is intended and as it has to work, but I suspect that it is intended for image sequence processing

In the projects '32-bit full range' into delusion enters different behavior of media on TL depending on a format. Some formats "stretch" on 15 points down and on 15 points up therefore it is logical to assume that it is necessary to open media with the studio RGB levels. At Stills (Photo) levels don't change.
Lack of information support from SCS depresses. Unclear "that, as, what and why"
GlennChan wrote on 12/5/2012, 4:22 PM
At digital shooting the signal exceeding 110 IRE, becomes purely white.
This is not entirely true. Also, IRE is an analog unit.


If it is necessary, Vegas also allows to process and keep all 'super white' (within YUV color space). Any problems in projct '32-bit video levels'
It has nothing to do with image sequences.

That setting affects the behaviour of particular video codecs in Vegas (MPEG2, MPEG4; I do not believe that DV is affected, which is very confusing to me). In a 32-bit project (but not 8-bit), the full range setting controls whether video decodes to Vegas' floating point equivalent of studio or computer RGB levels.
For optically correct compositing, you need black to map to 0... you do not want black to map to some value above 0. In full range mode, black maps to 0.