Norman Black
Forum Replies Created
-
Vegas only uses its own internal codecs except for AVI files for which it uses the Video for Windows (VfW) subsystem and Quicktime MOV files for which it uses Quicktime if you installed Quicktime.
If the file is not AVI or MOV then there is no way to get Vegas to support it if it does not already do so. Also, with Windows you have to be specific. There is no such thing as a “system codec” as is commonly quoted. On the Mac Quicktime IS the system. On Windows we have from oldest to newest, Video for Windows, DirectShow and Media Foundation. Also one can install the Apple Quicktime subsystem. All are independent of each other.
-
Twixtor resampling of video is a very compute intensive operation. It is what it is. Twixtor 6 can use GPU, so if you have a fast GPU that may help.
-
[John Rofrano] “Updated FX: Honestly, the Chroma Keyer is 12 years old!!!!”
Yes, certain core functions should be worked on to make them as good as they can be. General grading functions mostly. One can leave the remainder to the aftermarket. Bright, contrast, curves, levels, color, white balance, sharpening and yes, chroma key.
[John Rofrano] “A good Titler. The last attempt to add a titler was ProType which looks like it came from outer space.”
Protype actually has a ton of power, especially in keyframing, but is very clunky, and of course no 3D. It seems Sony is leaving the “power” titler to the aftermarket since the most recent thing, Titles&Text, is really targeting the basic quick and dirty text. Sadly, Sony has been ignoring the fonts bugs in T&T.
My power titler of choice is NewBlue Titler Pro.
For quick and dirty I use Legacy text due to the font bugs in Titles and Text.[John Rofrano] “Background Rendering:”
Sony probably thinks they have this covered with the Vegas selective prerender feature. But that is clunky and leaves droppings behind on your HD. We also have to manually re-prerender with edit changes.
[John Rofrano] “Compound Clips / Nested Sequences”
Again, Sony sits on their arse since they probably think nested projects have them covered.
[John Rofrano] “Better support for Non-Sony cameras. Honestly, the GoPro is infinitely popular.”
Don’t get me started on the GoPro thing…
-
Since Youtube re-encodes everything you upload, if the file you upload looks good but the Youtube result is bad, then really there is nothing you can do. The Youtube encode is the limiter and not what you are giving them.
High detail with motion is problematic to encode and consumes a lot of bitrate. Internet delivery is very bitrate limited.
Youtube encodes to an average bitrate and the bitrate can spike within constraints. Having infrequent and brief high detail motion sequences may be handled but too much and things start to break down.
With Youtube you can get bad quality or great quality. That depends more on the content of the video, which determines how well it compresses, than it depends on the quality of the encode you send them.
-
This was an instructive thread to read. Thanks to all.
-
[John Smith] “How does correcting White Balance also correct colors?”
Because it removes a color cast. Your examples show a clear color cast that ends up being corrected.
With auto white balance, cameras are guessing what the lighting is when shot. This guess is often not correct. Neutral tones, aka the greys, are the best thing to white balance on since we know the color component primitives are all supposed to be equal. If not, then they, the color primitives, can be equalized which will remove a color cast. This shifts all colors.
Of course, outdoors one can have multiple what balances in a scene. Someone in shade and someone in sunlight. The three controls in the Sony color corrector can help here, but the range of tones considered “low” is fixed and not under our control. The secondary color corrector can help here.
-
I don’t know of any plug-in that can create/use a profile by using a color checker chart. Maybe others have info here.
What you can do and is probably the biggest thing in correction is to get the white balance neutral. You would use the gray patches on a colorchecker or neutral grey card with the White Balance plug-in in Vegas.
-
I agree with this. It is well known that Canon and Nikon DSLRs output full range video, with the AVC VUI full range flag set to Yes. It is also known and Adobe normalizes these to studio video levels on import. Vegas does not. The stretch/compress of levels and cause an issue when your color is at the boundaries, and red can be problem color.
I can see a levels difference between the two photos.
Actually I believe the Nikon generates AVC Quicktime MOV files and not AVCHD format files. A technicality, but worth mentioning. For DSLR QT MOV files Vegas bypasses QT and uses its own AVC decoder.
-
You can edit the MOV files directly. Vegas bypasses Quicktime for typical DSLR MOV files, Canon included, and decodes these directly with its own internal decoders. The 50 file Quicktime issue does not apply.
-
About GoPro and 1080p60. Here is a long thread but includes a lot of info and some workarounds.
The problems with GoPro 1080p60 is in the Vegas 12/13 AVC decoder. V11 is just fine.https://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=878671&Replies=56