@Pawel-Rybinski @AAProds @johnebaker

I tried to do use Mercali V5 in VPX 11 and couldn't even get into the starting gate. I could not get the video interlacing under control.

I was seeing this before I even started.

MEP 2022 which is the smaller brother of VPX 13 however fared much better with interlacing.

I got the same results as you have been seeing trying to use the plugin.

There seems to be a work around but you probably won't like it. Change all video processing, Import, Processing, and Export to CPU. It took my machine four and a half minutes compared to under thirty seconds trying to use a GPU.

This was my result.

Ray.

 

 

What a great program !!! Buddy, you are right. Works fine on the CPU itself. Oh, I'm terribly disgusted. So I'm still waiting and working on X12. I don't know not to fix the errors for 9 months? Customers are beta testers. Thanks for the help.

@Pawel-Rybinski

Hi.

What I can't understand is if you can use VPX 12 Why can't I get it to work on VPX 11?

I tried every combination I could think of.

I've also beta tested a few cars in my time as well and paid for the privilege 🤬

I might have thought about switching NLEs but all the others have their own different problems. 😅😏.

Ray.

😁 true

@Pawel-Rybinski, @CubeAce, @AAProds

Hi everyone

I cannot replicate the 'jello' issue using CPU, UHD 630 or RTX 2060 - with VPX 13 - I do not get any tearing, de-interlacing artefacts and also less zooming then Ray is experiencing.

These are the setting for Mercalli Pro v5 I was using:

. . . .  Change all video processing, Import, Processing, and Export to CPU. It took my machine four and a half minutes compared to under thirty seconds trying to use a GPU . . . .

Ray - assuming you were exporting to 50 fps there is something odd going on with the CPU - mine took 37secs.

John EB

@johnebaker

Hi John.

I set the project settings to the files' resolution and frame rate but set the export settings way higher (but same frame rate and resolution) in an effort to retain detail. I suspect if I exported to settings slightly above what was really needed then the export would have been quicker. Still not as quick as using a GPU though. I also added a small amount of sharpening.

In VPX 11 I could not get rid of the very obvious (exaggerated) combing (see image in my reply above) so didn't even try to stabilize the footage. Again sticking to the files data info for the project setup.

Ray.

I did say a few posts ago..

You could try changing the settings for the graphics cards and CPU on the Settings>Device Options tab (Import/Processing/Export).

@AAProds @johnebaker @Pawel-Rybinski

Hi Al.

Indeed you did.

I have done further testing and can report back that the GPUs can be used but not for Importing.

The following also works works with no problems on my system.

Only Import has to change, so I can export at normal expected export rates of performance.

I only tested MP4 as an export option.

[Edit] Using MEP 2022 latest patch and new Intel driver.

Ray.

@Pawel-Rybinski, @CubeAce, @AAProds

Hi

What is the version number of VPX you are using?

All my previous tests were with VPX 13 v 19.0.1.129.

I have just updated to patch 19.0.1.141 and am now getting some jello in MP4 exports when processing is set to use my RTX 2060, looks like there may be a bug introduced with the fix for 'Jerky playback/export on NVidia GPUs'.

Using the settings below

and setting the Processing option to CPU or Intel iGPU - I get no jello/tearing at all.

John EB

patch 19.0.1.141 and patch 19.0.1.138

@Pawel-Rybinski @AAProds @johnebaker @CubeAce

Hi Pawe

I have just loaded some files into MEP2022 with the latest equivalent patch and can see that the bug from one of the the earlier patches/versions is back again, where new clips placed on the timeline have the "Interpolate Intermediate frames" automatically applied. This could be causing at least some of the strange effects you and responders are seeing, especially the double image effect shown in one of Ray's images of attempts to stabilise the footage.

By the way - your Topic heading says Mercalli V5 SAL which stands for the Stand Alone version of the Prodad program, but I believe we are all referring to the Plug in version of Mercalli V5.

If you are seeing a Jello effect in places then this may be due to actual camera movement with a CMOS chip camera, so some improvement may be achieved by applying the Prodad CMOS correction Plug in before the stabilistaion attempt.

Peter

@Scenestealer

Hi Peter.

I'm beginning to think that that importing new clips with Interpolate Intermediate frames on import is deliberate so that Magix can make their claim on the website of

"INFUSION Engine 3 Movie Edit Pro now has a brand-new engine – INFUSION Engine 3! The new engine offers support for modern graphics cards from industry leaders Intel, NVIDIA and AMD. The result is ultra-smooth project previews in real time while editing and fast export for your finished videos."

a reality.

I don't think it is a bug.

Ray.

I also have the Mercalli V5 SAL in the full version, but it stabilizes properly. The X12 version also includes interpolated materials. I had a Sony AX2000 camera and from the X8 version all versions stabilized the material correctly. Unfortunately, X13 seems to be unlucky for MAGIX. Here you can see that everything has fallen apart, so I'm still waiting for corrections. I don't want to predict, but there are too many errors for programmers to be able to do. I would send the program again. There is no point in patching up something that, while trying to fix it, breaks something else. See how many patches are there so far. Is it normal? On MAGIX, I chose the stability of the program. However, it is now highly questionable. The support of other plugs, even with proDAD, is enough. No response from Magix to their requests for bug fixes. I got a proposal from 2 plug-in manufacturers to transfer the license to another program for free. The Mercalli 5 is very useful for handheld shots. Unfortunately, in this form it is useless for me. What are your adventures with Mercalli 5?