VP21 315 Stabilizing Fail

fabianfelder wrote on 11/14/2024, 11:55 PM

Hey there,

as I was working on recent project I figured out, that one or two videos of my drone footage have been shaky, so I tried to work with the video stabilization fx but it did not help. In fact, some options even made it worse! Another option was to try Mocha and track a few trees that haven't been too shaky, but there as well - it does not really help.

I made a short clip of some options I've tried as well as the outcome, it can be found here:

For media information:

Allgemein
Vollständiger Name                       : F:\Fabian\Ausflüge\Drohne\Wolke 7 Wanderung\DJI_20241110135918_0024_D.MP4
Format                                   : MPEG-4
Format-Profil                            : Base Media
Codec-ID                                 : isom (isom/iso2/mp41)
Dateigröße                               : 339 MiB
Dauer                                    : 30s 664 ms
Gesamte Bitrate                          : 92,8 Mb/s
Bildwiederholungsrate                    : 29,970 FPS
Kodierungs-Datum                         : 2024-11-10 12:59:18 UTC
Tagging-Datum                            : 2024-11-10 12:59:18 UTC
Kodierendes Programm                     : DJI Mini4 Pro
Cover                                    : Yes
snal                                     : (Binary)
tnal                                     : (Binary)Video
ID                                       : 1
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format-Profil                            : Main 10@L5@High
Codec-ID                                 : hvc1
Codec-ID/Info                            : High Efficiency Video Coding
Dauer                                    : 30s 664 ms
Bitrate                                  : 90,0 Mb/s
Breite                                   : 3 840 Pixel
Höhe                                     : 2 160 Pixel
Bildseitenverhältnis                     : 16:9
Modus der Bildwiederholungsrate          : konstant
Bildwiederholungsrate                    : 29,970 (30000/1001) FPS
originale Bildwiederholungsrate          : 29,970 (29970/1000) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 10 bits
Bits/(Pixel*Frame)                       : 0.362
Stream-Größe                             : 329 MiB (97%)
Kodierungs-Datum                         : 2024-11-10 12:59:18 UTC
Tagging-Datum                            : 2024-11-10 12:59:18 UTC
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : hvcCAndere #1
ID                                       : 2
Type                                     : meta
Format                                   : djmd
Codec-ID                                 : djmd
Dauer                                    : 30s 664 ms
Bitraten-Modus                           : variabel
Titel                                    : DJI meta
Default                                  : Nein
Alternate group                          : 5
Kodierungs-Datum                         : 2024-11-10 12:59:18 UTC
Tagging-Datum                            : 2024-11-10 12:59:18 UTCAndere #2
ID                                       : 3
Type                                     : meta
Format                                   : dbgi
Codec-ID                                 : dbgi
Dauer                                    : 30s 664 ms
Bitraten-Modus                           : variabel
Titel                                    : DJI dbgi
Default                                  : Nein
Alternate group                          : 5
Kodierungs-Datum                         : 2024-11-10 12:59:18 UTC
Tagging-Datum                            : 2024-11-10 12:59:18 UTC

 

It was shot in D-LOG M on a DJI Mini 4 pro. Except for a little color correction no other measures have been taken with the footage.

 

The Vegas Files properties are the following:

Allgemein
  Name: DJI_20241110135918_0024_D.MP4
  Ordner: F:\Fabian\Ausflüge\Drohne\Wolke 7 Wanderung
  Typ: Intel HEVC
  Größe: 347,42 MB (355.761.909 Byte)
  Erstellt: Sonntag, 10. November 2024, 17:53:43
  Geändert: Sonntag, 10. November 2024, 13:59:50
  Zugriff: Freitag, 15. November 2024, 00:00:00
  Attribute: ArchivierenStreams
  Video: 00:00:30,664, 29,970 fps progressiv, 3840x2160x32, HEVCACID-Informationen
  ACID-Chunk: nein
  Stretch-Chunk: nein
  Stretch-Liste: nein
  Stretch-Info2: nein
  Beat-Marker: nein
  Erkannte Beats: neinWeitere Metadaten
  Regionen/Marker: nein
  Befehlsmarker: neinMedia Manager
  Medientags: neinPlug-In
  Name: mxcompoundplug.dll
  Ordner: C:\Program Files\VEGAS\VEGAS Pro 21.0\FileIO Plug-Ins\mxcompoundplug
  Format: Intel HEVC
  Version: Version 21.0 (Build 315)
  Firma: MAGIX Computer Products Intl. Co.

Am I missing something big or is this an unsolvable issue because of the footage itself?

Thank you very much in advance. ☺️

Comments

RogerS wrote on 11/15/2024, 1:32 AM

Do you want to share the source media and see if anyone can find a better way to stabilize this footage?

Dexcon wrote on 11/15/2024, 1:50 AM

Mocha is far from ideal for many moving shots because Mocha relies on an area of the image defined by splines and if that splined area leaves frame, that's where difficulties begin. Not helping is that there is not much that is defined in the tree canopies that Mocha can lock on to when tracking - but you may have found that that wasn't a problem.

In theory, the basic and profressional options in Vegas Pro's stabilisation should work ... but I don't think that it is stabilisation per se that is the problem; rather, it is a 'jello effect' problem where different areas of the image are wobbling around independent of each other. In saying this, I am assuming that the first video in your upload is the original camera footage.

I've had jello effect problems in the past with a few smart phone cameras and was never able to fully get a stable result no matter what stabiliser I used. It's really a case of getting the best result of the various stabilisation runs and going with that.

You might want to get the trial version of ProDad''s Mercalli 6 Standalone (SAL) stabiliser and see how that goes but making sure that rolling shutter compensation is enabled as that may help with the jello effect. Thus far, there isn't a Mercalli 6 plugin for Vegas Pro - only for some of MAGIX's NLEs but not Vegas Pro.

Also, try stabilisation in DaVinci Resolve's free version. When it comes to stabilisation, the more stabilisers available the better because no stabiliser is the be-all-and-end-all for all stabilisation tasks, each having their advantages as well as disadvantages.

I hope that you can get a satisfactory result.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

fabianfelder wrote on 11/15/2024, 2:23 AM

Thanks alot! I will upload the source media later after work, and I have to admit that I made a mistake with uploading the youtube video.

Instead of uploading the rendered result, I wanted to choose the screenrecording as where you can see what options in Vegas I already tried and - according to that - which results I got by putting the here shown video at the end.

@Dexcon understandable, I'll give it a try - thank you very much for your help and new input, when it comes to this topic.

fabianfelder wrote on 11/15/2024, 10:36 AM

Alright, here comes the originally meant source material and the video material I wanted to upload at first.

https://www.dropbox.com/scl/fo/w2gj63ie4n9xgmn3ru1cj/ADvb6lWCoCApD-H0X5KdVG4?rlkey=64cd7kvh8mki26hbc60p75dhh&st=empa3qvm&dl=0

Thank you once again.

 

Reyfox wrote on 11/16/2024, 10:21 AM

@fabianfelder at what point in time in the clip do you want stabilization?

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

3POINT wrote on 11/16/2024, 2:17 PM

@fabianfelder at what point in time in the clip do you want stabilization?

My impression is that this footage only needs CMOS wobble correction. I got a perfect result with Mercalli 6 SAL with just CMOS wobble correction. (Unfortunately directly uploading a video sample here, to show the result, is not possible at the moment.)

https://www.dropbox.com/scl/fi/ptf6tb3j63gx2lx48o80q/DJI_20241110135918_0024_D-mercalli-SE.mp4?rlkey=9rmwcwcubzcloj0kbqve7izvu&st=esecgpfs&dl=0

Last changed by 3POINT on 11/16/2024, 2:29 PM, changed a total of 1 times.

3POINT, Theo Houben, Vegasuser since version 5 and co-founder and moderator of the Dutch Vegasforum https://www.vegas-videoforum.nl/index.php

Recware: DJI Osmo Pocket/Mavic Mini, GoproHero7Black, PanasonicFZ300/HCX909.

Software: Vegaspro365+Vegasaur, PowerDirector365, Davinci Resolve 20

Hardware: i910900k, 32GB, GTX2080super, 2x1920x1200 display

Playware: Samsung Qled QE65Q6FN

Reyfox wrote on 11/16/2024, 2:25 PM

@3POINT I was thinking the same thing, CMOS wobble.

3POINT wrote on 11/16/2024, 2:53 PM

@3POINT I was thinking the same thing, CMOS wobble.


@Reyfox I updated my previous comment with a video sample downloadable from dropbox.

fabianfelder wrote on 11/17/2024, 3:44 AM

@3POINT I was thinking the same thing, CMOS wobble.


@Reyfox I updated my previous comment with a video sample downloadable from dropbox.

Insane, the footage looks perfect! I'm rendering at the moment to take a closer look on a bigger screen, but even on a small desktop screen like mine it looks unbelievable, thank you so much! Now I have to think about getting Mercalli myself. Did I get it right, that there is no plugin but I can use it as the software itself, and then implement the results as already stabilized footage into my vegas project?

Dexcon wrote on 11/17/2024, 4:01 AM

Now I have to think about getting Mercalli myself. Did I get it right, that there is no plugin but I can use it as the software itself, and then implement the results as already stabilized footage into my vegas project?

Earlier, I mentioned 'rolling shutter correction' - that is in fact CMOS correction.

A Mercalli 6 plugin for Vegas Pro has thus far not been released. The last Mercalli plugin for Vegas Pro was Mercalli 5 but does not seem to be available for purchase on ProDad's website.

In any event, I've long preferred the SAL version to the plugin (that's just my choice). With the SAL, it's a case of doing the stabilisation, render it to .MP4 (or .MOV if that format is preferred), and then import the render into Vegas Pro.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

3POINT wrote on 11/17/2024, 4:42 AM

The only disadvantage of the SAL version is that you have to decide prior before importing into Vegas which portion of the video you actually need (trimming) and that you actually work with a second rendergeneration. With a plugin you first trim in Vegas the event on the timeline and than only stabilize that portion. This works faster and more accurate.

@fabianfelder You can try yourself with a demo of Mercalli 6SAL, which only gives a small watersign in the output (which could be cropped away)