Wayne Waag
2
COW Coins
Forum Replies Created
-
Just to make it clear, the V2 plug-in I refer to and used in the above YT demo is NOT the one that’s included inside of Vegas. The degree of control for the Mercalli V2 plug-in is pretty much the same as V4 except there is no CMOS distortion correction. I must admit that V3 which enabled batch processing did not seem worth the $40 upgrade cost at the time. Dropping the ability to render to an avi and only providing avc options seemed a step backward IMHO. But, the CMOS correction in V4 is really great and well worth the upgrade cost. Hopefully, there will be a V4 plug-in the the future, which will enable batch processing from the timeline.
wwaag
-
[Steve]
Sorry, can never see the need for Mercalli standalone
For once (lol), I have to disagree. Have a look at this 24 sec clip.
Original was filmed 600mm, handheld. Lots of shake. The second is using the Mercalli 2.0 plug-in. Lots of distortion, especially noticeable at the bottom. The 3rd and 4th, with CMOS correction using V4.0 SAL. Not that bad now. MY recommendation is to use V4.0 ONLY for those cases where CMOS correction is required. For one thing, it is very slow. Its biggest application is probably for very shaky GoPro footage. For all other instances, agreed, use the plug-in and save yourself the bother of color correction issues.
wwaag
-
Vegas also supports Quicksync via the Sony AVC encoder.
Only problem is that it doesn’t work for 1080 renders, only 720–at least on my system. You might want to try it.
wwaag
-
Can you use Quick-Sync with your i5? I’ve got an i7 and use it a lot. I mostly use the one-click Send2Handbrake script for rendering–mostly 1080 60P. Quick-sync is roughly twice the speed as CPU only in Handbrake. You could also try TMPGEnc’s Mastering Works, the latest version, which I found their implementation of QS even faster than using Handbrake. The only downside, it’s about $100. These options are certainly faster than rendering inside of Vegas. As others have said, if you only use Vegas, then Sony AVC is faster than Mainconcept AVC.
wwaag
-
I agree with Norman that V13 is a lot more stable. There are two ways that GPU can be beneficial. First effects processing, which can provide better preview performance and also quicker renders, by virtue of the fact that it uses the GPU rather than CPU for processing effects. You can enable GPU for effects processing in Options:Preferences and the Video Tab. The second, is during render template selection when there can be an option for GPU assist for certain rendering formats. In my experience, GPU assist works very well for effects processing which does increase render speed, even with my pretty weak GT 650, but not for assist during the render process itself. I always select CPU only. The result, for me at least–no crashes during render.
wwaag
-
I don’t know if it is because I have ‘snapping’ on
That’s likely the problem. Disable Snapping-F8. That should do it, or select which Snapping you want to disable from the Options Menu.
wwaag
-
Martin,
Sorry that this seems to be going nowhere. Perhaps a set of fresh eyes would help. Since you were able to make it work in a new project for individual clips, a backup would be to copy those events in need of stabilization into a new project with the project properties the same as the media properties, do your stabilization, render each event using a lossless codec, and then import the stabllized clips back into the original project. Although laborious, it would work, but you really shouldn’t have to do it that way. As a final question, I presume that you are redoing the Mercalli analysis after each change? Is all your footage 1280 x 720? If so, you might temporarily change your project settings to that frame size and reanalyze a test clip.
wwaag
-
If this doesn’t work, another thing you might try is to change the overall project settings to 1920 x 1080 and do your Mercalli analysis. At least the aspect ratios would be the same. If it works OK, then change the project settings back to 1920 x 804 and do a short test render.
wwaag
-
Am I missing something
No need to render. Just close. These are the render templates ONLY used by Mercalli. When you do the Mercalli analysis, it should use this template with the selected frame size rather than the Project frame size.
wwaag
-
When the Mecalli clip worked OK in the new project, what were your project settings? The same as the event (1280 x 720) or the 1920 x 804? What may be happening is that during the analysis phase, Mercalli may be rendering at the project setting (1920 x 804) rather than the event setting (1280 x 720) and given the fact that the aspect ratios are different, this may be causing the problem. Under render settings, select avi, and scroll down to the appropriate mercalli template. Select customize and it will display what the frame size is. If it says (Use Project Settings), change that to the actual size (1280×720) and see if that has an effect.
wwaag
