Norman Black
Forum Replies Created
-
[John Rofrano] “Actually, that’s only true if the formats don’t match.”
Ahh, thanks for the information. Makes sense actually. Given this, then I wonder why Selective pre-render restricts most render as templates from being used. Sony and MC AVC are not there for example. Interestingly XAVC is.
I have always used XDCAM EX 35Mbps as a pre-render and my renders are always AVC, XAVC-S or DNxHD (for AVC via Handbrake).
-
I see increased contrast throughout the sample picture. Increased contrast can increase saturation of colors.
Without any info other than the sample pictures, I would say your source footage used full range levels, typical for video game sources. When you render to AVC MP4 you need to have studio video levels passed to the encoder otherwise you will get increased contrast due to a levels expansion in a video player.
A video player playing back an AVC MP4 file will assume the video contains studio video levels and expand the data to full range for playback on a computer.
You use a levels effect with a computer to studio levels preset to correct full range source to normal video levels.
-
You can do DNxHD by installing the free Avid DNxHD codecs into Quicktime. Of course this means you must have Quicktime installed as well.
You can get the Avid codecs here.
https://avid.force.com/pkb/articles/en_US/download/Avid-Codecs-LE-2-3-9I have never seen any artifacts rendering to DNxHD. My use of DNxHD is as an intermediate format to pass to Handbrake to render AVC playback encodes.
As for ProRes. This is a proprietary codec of Apple which they support in Apple software only. FCP, FCP X, Motion, etc.
Apple does allow decoding of ProRes everywhere, so with Quicktime installed you can playback ProRes in Vegas.
The ffmpeg project has reverse engineered ProRes and supports encoding this. To do this you will have to render an intermediate of some sort, like uncompressed, and the encode to ProRes with an external utility. cliptoolz is one example.
Here is a thread on ProRes.
https://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=889085 -
NewBlue very recently moved TitlerPro into its own process separate from Vegas. TP2 made this change and TP3 is the same. Titler Pro requires GPU support. NewBlue says this change was to get TP out of the compatibility mess that is the Vegas GPU implementation. Not to say that NewBlue has not had their own GPU issues, but at least now any issues are theirs alone and not mixed up with Vegas.
-
Vegas 13 does not come with Titler Pro 1.0. Vegas 12 and Vegas 11 did. You probably got your TP 1.0 from Vegas 11/12. That bundled version of TP 1.0 will not work in Vegas 13. It is licensed only for the version it was bundled with.
As for Vegas 13 and the $99 offer for Titler Pro 3. AFAIK that only is possible at the time of Vegas 13 upgrade. If you already upgraded to 13 but did not go for the titler pro 3, then I’ll bet that you can talk to Sony customer service to get the $99 offer.
-
Titler Pro 3 is not yet for sale at the NewBlue website. Titler Pro 2.0 is for sale at $199 minus the current 20% NAB discount.
NewBlue has taken down the Tiler Pro 1.0 product which did have a price of $99.
Titler Pro 3 is for sale for $99 at the time of Vegas Pro 13 upgrade.
-
The selective pre-render is only used during playback. In a final render the original sources are used.
-
Well, the Vegas smart proxy feature really only intends to proxy high bitrate 1080 and 4K stuff, so 720 is smaller in that sense.
50/60p at 1080 is very difficult to edit. You need a speedy machine. If you are having problems with the Vegas mpeg-2 smart proxies at 50/60p then you really need a faster machine for whatever it is that you are doing in your project(s). Those proxies really decode fast and if you are still having problems then decoding the proxy is not the bottleneck.
You said you still have problems at lowest preview, which is quarter. I have always edited at Preview Half, and with my old core i7 i860 2.8Ghz machine I was able to edit 1080p60 files smoothly using the smart proxy of a high bitrate GoPro AVC source file.
You can proxy in way other than the Vegas smart proxy feature. Utilities like Vegasaur, and others like it, can make this easy for you. Vegasaur will also help you create custom smart proxies.
-
It is a little hard to respond given how little info you have given.
There are a couple of different error dialogs. Which one did you get? Does that dialog have a error details display option?
Any third party plug-ins installed? Video and/or audio. For some people when they uninstalled a certain plug-in Vegas then loaded.
There have been some people who have had problems with Cineform in Vegas 13. A crash related to CFHD.DLL. I have not had such a problem with Cineform.
Some other Video for Windows codecs have caused Vegas a startup problem. Uninstalling and/or updating that codec solved the issue.
-
You are probably getting this by double clicking on an event edge. What you are opening is expanded edit mode. There are other ways to enter this mode, but Esc will get you out.