I used proDAD Mercalli 2.0 to do a stabilization on a video and after this, there is screenwriting on it which I could not eliminate as you can see in my attached screenshot.
To add a little to what @CubeAce (Ray) says: footage for which any stabilization is required needs first to be analysed by the plugin. Without this analysis you will see no change (i.e. the footage will still be "wobbly") but you will have that watermark over your footage. Just press the "Run analysis" button and wait for the process to be completed.
I've just run ProDAD Mercalli 2.0 on one of my clips and it is not using the Intel GPU but mainly my CPU and nvidia card but is processing it OK. In the programs settings try disabling any hardware acceleration in the import export section.
If that doesn't work try using 'compatibility mode for Windows' in Display options under the 'Video Mode'.
If either of those solutions work then it is the lack of an effective nvidia graphics card.
If it makes no difference then my assumption was completely wrong and please reset your program to the default settings.
What makes me wonder about this is that under the specifications page it does state some functionality may be impaired on those systems not meeting the minimum specifications to run Movie Edit Pro and noticing the Intel GPU is not in use with this effect on my system. Disabling any hardware acceleration would force the effect to use the CPU and do the converting via software alone if that is the case.
Another possibility is that the effect has not been registered with ProDad and effectively enabled.
Did you follow the link in your support email and register it and make a record of the activation code?
[Edit] I just checked and there should not be an activation code associated with that effect. It should be loaded and functioning without registering it.
Thanks for your kind helps. A member of Magix staff suggested me to do "File>Settings>Reset program settings to default" and I followed. The results are encouraging, but still some troubles there.
I uploaded a 25 seconds video to do the stabilization and after running the analysis the water marks were still there. I then cut the video to 12.30 seconds and the program worked. After running the analysis the watermark disappears and the video shows the effects of stabilization.
I am puzzled at this. Is this my computer's problem or the software can only deal with short video?
I saw there is another one call " Vegas Video stabilization." It works well with my 25 seconds video without water marks. What is the relationship and differences between these two programs? I wish to hear your inside of these two programs.
I see no relationship between length of clip and the ability of either of the plugins to perform on my system but I have always in the past used the ProDAD Mercalli 2.0 within the program to stabilize footage as it gives more control. As both also use my nvidia card it could be a lack of such a suitable card is causing a problem but why one should work while another is having problems is beyond my understanding. I don't think you have a lack of ram or any other obvious bottleneck except for not having an appropriate nvdia card card listed so it could be that but I'm really not sure. As the ProDAD Mercalli 2.0 is not Magix made they possibly do not know the answer either.
The Prodad website does list supported cameras which is news to me. I was not aware it could be limited by camera footage. Here is the current list but be aware the current version of the program is three generations ahead so some listed here may not be available.
ActionPro X7 AEE S51 Braun Master CamOne Canon EOS 60D Canon EOS C100 Canon HFG10 Canon LEGRIA mini X Canon XHA1 Contour HD Mod1300 Contour ROAM3 Contour+2 DJI Phantom 2 Vision DJI Phantom 2 Vision+ Drift Ghost-S Drift Innovations HD170 Drift Stealth Garmin VIRB GoPro Hero 1 GoPro Hero 2 GoPro Hero 3 GoPro Hero 3+ GoPro Hero 4 GoPro Hero+ HP ac200 Ion Air Pro Mobius ActionCam OlympusE-PL3 Panasonic HX-A500 Panasonic LumixDMC T27 Rollei Bullet HD Rollei Bullet S5 Rollei S30 Rollei S40 Rollei S7 Samsung Galaxy S2 Samsung Galaxy S3 Somikon DV800 Sony AS100 V (Steady on/off) Sony X1000V Sony HDR AS10/AS15 Sony HDR AZ1 Sumikon DV78.night Toshiba X-Sports Vivitar-DVR-785HD
Having said that it works on my Nikon camera footage and that is not listed. There must be more to it than that.
Sadly I can't find similar information on the Vegas plugin.
With apologies, but I have edited your latest post to remove the name of a member of Magix staff. Publication of the names of individual members of staff is forbidden under Community rules.
As @CubeAce (Ray) says, given that ProDAD Mercalli is not a Magix product AND the fact that it is now 3 versions old, I doubt whether anything is going to be done to change the situation, but I can reproduce the problem you see.
I placed a one minute video file on my timeline (in MEP 20.0.1.80) and opened Mercalli 2, clicked on "Run analysis", the progress bar completed, but the watermark did not disappear.
I then removed the effect, cut the clip into two halves and reapplied Mercalli 2 to the first 30 seconds. Analysis proceeded and, once complete, the watermark disappeared.
I then removed the effect, rejoined the clips to make one file, opened and applied the Vegas Video Stabilization effect without a problem. Visually, there was not very obvious difference between the two outcomes but I had deliberately chosen a clip which did not require a lot of stabilization.
I should add that, because I also have ProDAD Mercalli 5 I don't think I've ever needed to use either Mercalli 2 or the Vegas plugin.
. . . . The Prodad website does list supported cameras which is news to me. I was not aware it could be limited by camera footage. . . . .
I believe that if you have the full standalone version, the list you posted refers to specific stabilisation presets for those cameras. They correct for the different lens angles, focal length and sensor parameters.
Vegas Stabilisation is an alternative to Mercalli, and in some cases is better at stabilising a video clip, the only downside I see from using it, is that the zoom it applies can be more aggressive than Mercalli - eg using the default settings for Vegas and Mercalli
Do you see the same problem as @sheng and I both seem to experience with Mercalli 2, namely that any clip longer than about 30 seconds or so, after the analysis is completed the watermark fails to be removed?
There are no settings to play with in the Vegas version.
The list quote makes sense although that would be an awful lot of work for those cameras listed that can use a number of different lenses. Maybe the amount of shake in a clip also makes a difference as to whether the Mercalli effect makes it to the end of processing or not. My video clips don't tend to have a lot of shake to start with.
As I wrote earlier, the clip I used to test Mercalli 2 did not have a lot of need for stabilisation, so I suspect the actual "amount" needed may not be relevant.
That's interesting as at present I have both VPX and MEP set to Power saving and the effects are using the nvidia graphics card. Also which display is MEP or VPX mainly displaying the program on (assuming you are using the desktop and not the laptop) ? Mine are currently showing on the Intel powered monitor.
My bad I was testing in both MEP and VPX the settings are only available in VPX - I have adjusted my comment.
. . . . Also which display is MEP or VPX mainly displaying the program on (assuming you are using the desktop and not the laptop) ? . . . .
Main program is on the Intel - Preview monitor is on the RTX - I will check on the laptop.
Added: On the laptop Graphics and MEP settings are the same as the PC. I get the same result, iGPU used - usage 45 - 48%, RTX nothing, CPU on both was 45 - 65%
I have this in video files themselves of ANY size that I try to run the PDM2.0 on from within MEPrem2021. It is a bit tiring after getting asked for update rights every 10-30 days now. :(
Are you saying that after pressing the 'run analysis' button in the effect box that is coming out in the final export as that? Without pressing that button first, the plugin has not applied any stabilization.
[Edit] we seem to be going around in circles. I have no idea why this keeps happening to you.