Mercalli V2: Stand Alone & Plug In differences

Richard Jones wrote on 12/16/2010, 4:15 AM
I raised this issue in the Mercalli V2 thread but thought I'd open a new thread as this concerns a slightly different aspect.

I suggested that, although I hadn't done any any testing, the Stand Alone Version seemed to offer more options/control that the Plug In. I also questioned whether, if I was right and wished to take advantage of this, I would have to render the event I wanted stabilised out from Vegas, post this into Mercalli Stand Alone, do whatever's necessary, render out again and import the finished item back into Veghas.

Jayster kindly replied as follows:-

I didn't see any settings in the SAL that you couldn't transfer to the full Mercalli V2 plugin in the Vegas interface. Thank goodness, because the workflow you just described would be a real headache. The SAL gives you their instrumentation, so that instead of randomly choosing (guessing) settings you can do it with some rhyme and reason.

I'm not sure I follow this as the SAL seems to have more tabs to use when making your adjustments. I'm also not sure how you would transfer and load an event directly from Vegas into SAL and ow to then then transfer the adjusted event backto Vegas again.

Am I missing something here?

Richard

Comments

amendegw wrote on 12/16/2010, 5:24 AM
I'm not quite sure how to answer your questions, but here's some screen shots that might help.

First Mercalli V2 SAL:



Next, the Mercalli V2 Vegas Plugin:


Good Luck!
...Jerry

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

Richard Jones wrote on 12/17/2010, 3:35 AM
Thank you, Jerry. The screen shots bear out what I said in that the Stand Alone version seems to have rather more tabs/controls than are available in the Plug In. If this is right, can anyone help with my point about gaining the maximum advantage when needed by moving an event between the two versions please?

Richard
amendegw wrote on 12/17/2010, 3:51 AM
Richard, I guess I see it a little differently - do you see a setting/adjustment in Mercalli V2 SAL that is not in the Vegas Plugin? There is obviously more stabilization data available to user in SAL, but I don't know of any additional knobs I can tweak.

As far as moving between Mercalli V2 SAL & Vegas, I only know of two ways to do this:

1) Render (i.e. "Export") from Mercalli V2 SAL and drop the result in the Vegas timeline, or...
2) Write down the settings on a piece of paper & re-create the settings in the Vegas Plugin.

Others may know something I don't. If so, please post!

...Jerry

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

Jayster wrote on 12/17/2010, 11:34 AM
I just bought Mercalli recently and don't have enough experience to try to claim to be an expert, but Jerry's #2 (write down the settings) is what I was thinking. The only reason I was suggesting this is to avoid having to render back and forth. The SAL has a lot of visual instrumentation, but the settings seem to boil down to just a few yes/no choices and a few numerical values.

As you know, the SAL doesn't know what an "event" is, so it looks at an entire clip. I ignore what the SAL instrumentation says for time periods that I trimmed out of the clip when I worked on the event in Vegas, but some might prefer to just render the event anyway.

An ugly proposition would be if you had, say, 50+ events that all need to be stabilized. That gets messy regardless of how you want to do it. I guess you could tackle that based on how much time you have to invest.

1) Fastest way would be to complete your project, render it from Vegas, then run the completed file as whole into the SAL to get the best sending. Render directly from SAL or use Vegas plugin.

2) Suppose a couple of different parts of the video are more shaky than others. You could create two or three different regions in Vegas, put each region on its own track and use the Mercalli plugin on those tracks instead of individual events.

Sorry if I'm making this sound more complicated than it should be.
Richard Jones wrote on 12/18/2010, 3:06 AM
Thank you guys. That's a big help.

One last question. When you render out from Vegas to place into Mercalli, what format do you use? And, liokewise, do you have to render out from the SAL to return the piece to the Vegas project and, if so, what format do you use this time?

Hope I'm not being naive about this but I'm easily confused!

Richard
amendegw wrote on 12/18/2010, 4:58 AM
Richard,

First, if you haven't watched this excellent tutorial by John Rofrano, it may answer some of your questions:



If you still have questions, please post back.

...Jerry

PS: In Mercalli V2 SAL, I have been unsuccessful in exporting any of my AVCHD 1920x1080 clips to anything but WMV (and have been less than thrilled with resultant WMV), I emailed Mercalli support and they suggested installing the K-lite codec pack (which I refuse to do because of all the problems sited in this forum). That said, the Vegas Plugin seems to work fine - once you've sorted thru its idiosyncrasies.

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

Grazie wrote on 12/18/2010, 5:21 AM
Spectacular tutorial/demo John. It was a real pleasure to watch, learn and
understand the logic of the s/w

Also, what you did was to compare the versions, by underlining the value to an exsisting user thinking of UG-ing, which I can imagine Prodad wouldn't do, obviously. Did they?

Great stuff, thank you.

Grazie




Richard Jones wrote on 12/18/2010, 6:21 AM
Thank you again, Jerry. And thanks for pointing me to John Rofrano's excellent demo.

I note what you say about the formats for transfer --- oh well, c'est la vie.

Merry Christmas,

Richard