Matt Carlson
Forum Replies Created
-
If I remember correctly you can only delete templates you have customized yourself. Are you trying to delete a standard template?
-
I tried a 4 second clip with defocus 0.5 to 0 in both 8 bit and 32 bit pixel format project properties and both seemed smooth although 8 bit was a little fuzzier. I am assuming radius was the only parameter you changed? Do you have a way to post your clip to the forum?
-
You answered my question about comparison… it was working fine for you in Vegas 10. That was the first version with OFX so back then it was probably the same plugin as it is now. The fact you had CUDA working for you in 10 and not now might be the problem (which would be the opposite of what I thought.) It might be that the CPU calculations of defocus are not as good as the CUDA version for whatever reason.
-
What is your previous non-stepping comparison to? Vegas 11? 10? Earlier? There are several possibilities here. If this is your first go round with an OFX version of Vegas you can be unaware of keyframes being inserted (i.e. the hard stops you are experiencing) because the new interface is slightly different and you were not visually aware that your messing with parameters created new keyframes. Sometimes this happens so close together that visually you only see one keyframe where there are two. The second possibility is that with each update and iteration a few more plugins are made compatible with GPU acceleration. Turning it off may revert defocus back to a CPU calculated gradual curve.
-
On the expanded edit mode…. did Vegas go white? I have had the switch between expanded edit and back take as much as 40 seconds but it eventually got there. I suppose viewing Vegas 12 through the lens of the mess of Vegas 11 gave it a small leg up in the acceptance battle but I will agree with you that 12 still does not rise to the level of “pro” polish which is a shame. I still choose Vegas over everything else for the sheer speed and ease of pulling an edit together but at some point I think the failings may pile up to an unacceptable level.
-
Are your project properties and track frame both 1440×1080? I have noticed that if Vegas has to do any track motion changes or pan/crop changes (especially if project properties are set to Best for Full Resolution Rendering Quality) that GPU acceleration no matter how beefy the graphics card seems to take a holiday.
-
This can be a tricky question and the answer, as with any complex problem, is it depends. Neat Video can reduce noise that the human eye does not detect at low levels so it is not truly necessary to identify the noise with the naked eye. Ultimately using Neat Video as the last plugin in a chain is ideal but sometimes when the footage is heavily noised the end result, to put it bluntly, needs to be pounded by a sledgehammer. Since Neat Video is actually a “morphing” algorithm the question becomes whether or not the “distortion” created by the plugin is useful to you by creating and wrangling dark colors in to a uniform whole to be manipulated later. In extremely low light heavy noise situations applying Neat Video first can have the end result be much more palatable although a huge amount of detail will be lost. Sometimes this is preferable if you plan to keep the end result fairly dark. The clearer the actual footage is in terms of detail (that is if the details are not overly destroyed by noise… the noise is just there) means you can do corrections first and use Neat Video second.
The overriding concern is how the clip will fit in to the rest of your composition. This will help you determine which way to go. Unfortunately Neat Video is absolutely fantastic at removing film grain but only pretty good at codec distortion which is what you are dealing with.
-
Does this happen even with a saved project? I have (and I assume) everyone has the same problem that the default 32 bit transform is always ACES. For me once a project is saved as OFF it remains that way. Also if you are working in 8 bit (and have defaulted that way) there are no separate color space considerations and this will not happen. I always use 32 bit full range so I run in to the ACES default problem and have yet to find a solution… not that it is that big a deal to turn the view transform off at the beginning of a project.
-
The most common way people inadvertently get in to A/B roll editing is to double click on the edge of an event (when trying to resize.) Getting out of A/B is just as easy. Double click the edge of an event again.
-
Twixtor uses algorithms to find edges and the movement direction of those edges to create a whole new frame where none existed before. They say not to use blend because that causes the “base” image that the algorithms work on to be a bit confusing because two different points in time are being fused. Since these points in time are only a fraction of a second apart, however, it is not a big deal when the in frame motion to begin with is not that complicated. This is why your first “blended” output did not seem to look that bad. Interlace blended fast motion or complex movement (for example hair flipping) will start to blur and twitch in Twixtor if blending is being used. It does not break Twixtor, though.
Project settings where interlacing is concerned are for how the editor handles things. The settings should be for what your media IS not what it will be. In your case deinterlacing should be off since your media is progressive. The rendering template options will take care of interlacing the output no matter what the project settings are.