Strange video artifacts when using pro DAD Mercalli

uMuffin wrote on 7/1/2018, 9:48 PM

Hello! I'm currently in the process of trying a few different video editors before I purchase. So far, Movie Edit Pro is the smoothest, fastest and simplest video editor I've tried (this is my 5th).

That being said, I'm having strange video artifacts when adding DAD Mercalli V2 (which comes with Movie Edit Pro) stabilizer. On some clips, I get some serious warping (think the image made of jell-o) and on many clips, I get partial black bars at the bottom of my clips. Now, I've been using Mercalli for a number of months on different video editors and I've never seen this before. I've tried pretty much every combination of settings on Mercalli, to no avail (even if I put zoom 100%).

Is this some kind of a bug? If so, will it be addressed? I really like working with Movie Edit Pro but since stabilization is an absolute must for me, this would be a deal breaker.

Thank you all for your help and/or input.

Comments

Scenestealer wrote on 7/2/2018, 6:25 AM

Hi and welcome

Is this some kind of a bug?

No. Mercalli V2 and V4 work superbly in MEP.

The jello effect is the CMOS rolling shutter effect caused by the camera moving while the CMOS sensor, used in most modern digital cameras, is exposing progressively line by line from the top to the bottom of frame in 1/25th of a second. This should be repaired to some extent when Mercalli processes the clip providing the Rolling shutter correction box is ticked. If the camera movement is violent then there is a dedicated Prodad CMOS Fixer Plug in that comes with some Plus and Premium versions of MEP and this should be applied first before the V2 stabiliser.

The black border could be a setting that is not correct, like Avoid border, or you could try the Fill border setting.

Ss

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

johnebaker wrote on 7/2/2018, 7:14 AM

Hi

. . . . I get partial black bars at the bottom of my clips . . . .

ProDad Mercalli is very good at stabilisation, however there are limits to what it can do without having a detrimental effect on the video.

Is the source video from a sportscam and has some severe vibration/shake?

If not from a sportscam and

. . . . stabilization is an absolute must for me . . . .

what are you videoing with, and type of shots are you taking, that you cannot get a reasonably stable image?

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

uMuffin wrote on 7/2/2018, 7:16 AM

Thanks Scenestealer.

Corel VideoStudio, CyberLink PowerDirector and a few others all use Mercalli V2 as a stabilizer, and sadly, I'm getting these issues only and strictly with Magix. Again, I've tried every possible combination of Mercalli settings in Magix, and I still get these artifacts.

Some shots are stills and were shot on a tripod, they do show wiggles and artifacts. I'm starting to think that my installation of Magix is corrupted or something. I'll try to reinstall this week and see if that fixes it.

johnebaker wrote on 7/2/2018, 7:23 AM

Hi

. . . . Some shots are stills and were shot on a tripod . . . .

There is no need to stabilise still images in MEP, similarly if you are shooting video with the camera on a tripod that is on stable ground, then there should be no need for stabilisation in MEP, however there is one exception - some cameras with optical stabilisation need it turned off in camera, otherwise the stabilisation system tends to 'hunt'.

Can upload an original image to somewhere like Dropbox showing the wiggles and artefacts for us to look at.

. . . . I'm starting to think that my installation of Magix is corrupted or something. I'll try to reinstall this week and see if that fixes it. . . . .

This is very unlikely to fix the issue.

HTH

John EB

 

Last changed by johnebaker on 7/2/2018, 7:26 AM, changed a total of 2 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

uMuffin wrote on 7/2/2018, 8:03 AM

This is very unlikely to fix the issue.

 

 

Yep, that didn't fix it.

I have uploaded the source file, a rendered unstabilized and a rendered stabilized which shows the artifacts at the bottom. This is Mercalli V2 with borderless default settings, but like I said, tried every combination of settings...

 

Source: https://www.dropbox.com/s/on8tlr1war78xwi/00028.MTS?dl=0

Unstabilized: https://www.dropbox.com/s/gq0d0fp2cc6fx7t/Magix%20-%20Not%20Stabilized.mp4?dl=0

Stabilized: https://www.dropbox.com/s/4lkpc3mwy8sgs13/Magix%20-%20Mercalli%20V2%20Stabilized.mp4?dl=0

Edit: just to prove my point, here's the same clip stabilized with Mercalli, with the same settings, but using Corel VideoStudio 2018:

Corel: https://www.dropbox.com/s/ubjfafjntlg2x5n/Corel%20-%20Stabilized.mp4?dl=0

RogerGunkel wrote on 7/2/2018, 8:58 AM

It may be helpful to know what format the source footage is in and what your rendered footage is. The rendered footage looks quite low resolution compared with the source.

Do you apply Mercalli to the source footage on the timeline, or do you render the footage first then apply Mercalli? Also, why do you need to apply a stabiliser to a still image as there would be no movement?

Roger

uMuffin wrote on 7/2/2018, 12:01 PM

Hi Roger. The source is an MTS file, rendered in mp4. It was rendered in 720p to save on bandwith, since the resolution is not the issue. You can clearly see the warping and the artifacts in any format, including those that I've uploaded. The footage that I've provided is handheld, not on a tripod.

I've edited my previous post by adding the same video stabilized with Mercalli in Corel's, rather than Magix's. You can see that there are no artifacts or warping.

johnebaker wrote on 7/2/2018, 3:45 PM

@uMuffin

Hi

Thanks for the clips.

In your mp4 clips from MEP, I can definitely see the glitches, however when I use the source MTS file in MEP 2016, and 2018, applying the same mp4 parameters for export, I cannot reproduce the glitches with or without Mercalli stabilisation, I also tried it in MEP 2018 with the same result.

Which preferred codec for mp4 export do you have set for export in the Program settings, Import/Export tab

Do you have any all-in-one codec packs installed eg K-Lite codec pack?

We also need to know your computer specfication:

  • Processor make/model, graphics card or chipset make/model, audio card or chipset make/model, RAM,  hard drive configuration and sizes?
  • Windows version and is it up to date?  Press and hold down the Windows key and the R key - in the dialog that opens type in winver and press enter.
  • Software full name and version number - as found under Help, About . . .

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Scenestealer wrote on 7/2/2018, 6:28 PM

To me the disturbance is not with the V2 stabilisation but with the rendering of the file to a lower res and using much more compression, plus changing from an interlaced original to a progressive output, and in the case of the Magix renders, a much longer GOP.

Not to mention the Magix renders are showing a non standard aspect ratio of 768x432 compared to 720x480 in the Corel render, which in itself could be revealing the black edge of frame after stabilisation

As Roger has asked - did you use the down resed. Magix file before applying the stabilisation, and if so did you use that in Corel - I think not because Media Info shows the different pixel dimensions.

Most of your problem seems to be render related because it is in the down resed. Magix render prior to Mercalli application and looks like missing frames or incorrect field order going from interlace to progressive.

Try to match the export parameters of the Magix render to the ones used in the Corel render, and apply Mercalli to the original Hi def .mts before exporting anything.

Peter

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

RogerGunkel wrote on 7/3/2018, 4:09 AM

Completely agree with the other observations, there seems to be a considerable difference between the resolution and size of the Corel and Magix examples. It would be useful to know the rendered resolution, bitrate and size that you used in both rendered examples because you are not comparing like with like.

I don't know Corel at all, but there are a lot of user variables in the Magix programme for output to mp4 that you may not have set to optimum or may not be aware of. If you are using rendered files for stabilisation rather than the source, you will be losing more resolution as the frame is being cropped to stabilise it. It looks very much as though you are using a higher rendered output from Corel than from Magix which would be another reason for a poorer apparent Magix end result.

Roger

Last changed by RogerGunkel on 7/3/2018, 4:09 AM, changed a total of 1 times.

Videographer and Photographer since 1984 from South Lincolnshire UK. Windows 10 Home 64 bit V1803, Intel I7-6700 3.4GHz, Editing on VPX V16.0.1.255,

 

wongck wrote on 7/3/2018, 6:47 AM

Just want to add that I always have these wobbling when I do my Mercalli V2 stabilization, I always thought it was due to the algorithm used to stabilize it. Now I see that these wobbling may be removed. I am interested in the solutions that will come out of this thread. 😉

Casual home video editing just for FUN since MEP 5.5.4.1 (2006??)

  • MEP 17.0.3.177 & unused Vegas Pro 15
  • Win10 2004 i7-4770 3.4GHz, 32GB, 512GB Nvme, 4TB HDD, Nvidia GTX1070 (26.21.14.3160) & an old DVD writer
  • Amateur video equipment: Sony HDR-CX675, JVC GZ-MG330
uMuffin wrote on 7/3/2018, 7:30 AM

I'd like to thank you all for trying to help. Unfortunately, changing resolution of the rendering, the file format, the bit rate and the size of the rendering could not fix the issues: I ended up with the same artifacts, but in high definition.

I think a software should work straight out of the box. Sadly, it didn't for me, so I have to move on.

Cheers again to everyone who tried to help, this is a great community!

wongck wrote on 7/3/2018, 9:19 AM

What !!! No solution ?

Casual home video editing just for FUN since MEP 5.5.4.1 (2006??)

  • MEP 17.0.3.177 & unused Vegas Pro 15
  • Win10 2004 i7-4770 3.4GHz, 32GB, 512GB Nvme, 4TB HDD, Nvidia GTX1070 (26.21.14.3160) & an old DVD writer
  • Amateur video equipment: Sony HDR-CX675, JVC GZ-MG330
johnebaker wrote on 7/3/2018, 9:41 AM

@uMuffin

You have not answered my questions from my previous post ie

  • Which preferred codec for mp4 export do you have set for export in MEPs Program settings, Import/Export tab
  • Do you have any all-in-one codec packs installed eg K-Lite codec pack?

Also are you based in the UK? If so is there a reason for recording in NTSC and does the camera have a Progressive record mode for Full HD?

I recognised the lovely city in the video immediately 😁

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

RogerGunkel wrote on 7/4/2018, 6:30 AM

@uMuffin

Mercalli works fine for me and I have used it on many projects over a number of years.

Although you say that you have changed resolution, size, format etc., you have not answered any of the questions that we have asked regarding more detail, particularly regarding the odd sizes and difference in resolutions. Without more in depth information it is not possible to give meaningful help, which is a shame.

Roger