That is a very realistic earthquake simulation!

hahaha

Then make your project properties match the output.

This is a rough cut for my current project. The entire video was shot on Sony a7iii via Ninja V recorder in 4K, ProRes, 4:2:2 10Bit 25FPS.

The Project was set to 1080p 25FPS 32 bit video levels. Some of the edit, I applied Stabilization to get rid gimbal spatial error. It looks good. But when I export using Internet 720p 25fps using Magix AVC template it will make stabilization FX go crazy. Some FX will be offset (if I use Sapphire plugins). Just because the output doesnt match with project properties.

 

in PR, I can export whatever resolution and it wont affect how the FX supposed to work/look.

I would always use the stabilization as MediaFX (using the original resolution). The analysing step to create the paramteres is running with different properties as the rendering step.

Then make your project properties match the output.

I'm hoping VEGAS to do all of the labour work more then I do

This is a rough cut for my current project. The entire video was shot on Sony a7iii via Ninja V recorder in 4K, ProRes, 4:2:2 10Bit 25FPS.

The Project was set to 1080p 25FPS 32 bit video levels. Some of the edit, I applied Stabilization to get rid gimbal spatial error. It looks good. But when I export using Internet 720p 25fps using Magix AVC template it will make stabilization FX go crazy. Some FX will be offset (if I use Sapphire plugins). Just because the output doesnt match with project properties.

 

in PR, I can export whatever resolution and it wont affect how the FX supposed to work/look.

I would always use the stabilization as MediaFX (using the original resolution). The analysing step to create the paramteres is running with different properties as the rendering step.

Yes, that is what I do on this media. I created a subclip so it will gave me a better analysis & results, plus shorten the time span to analyze the video. It does look great.

But whenever the output upon rendering is different from video project properties, it will make the stabilization go crazy.

in PR, I can export whatever resolution and it wont affect how the FX supposed to work/look.

PR is no OFX host.

Stabilize OFX

• Analysing step:
  • input image is used to create for each image a parameter set to transform from the first frame to the second frame.
  • clip with x frames creates (x-1) parameter set
  • 
  • Motion compensation in the stabilisation plugin:
    • translation = translation
    • euclidean = translation + rotation
    • similarity = translation + rotation + scale
    • perspective = warp
• Rendering step
  • smoothing the output by the parameter set
  • if you change the FPS (or shrink/edit a clip) you have to reanalyse... otherwise the parameter set is changed for your new frame at a different position

in PR, I can export whatever resolution and it wont affect how the FX supposed to work/look.

PR is no OFX host.

Stabilize OFX

• Analysing step:
  • input image is used to create for each image a parameter set to transform from the first frame to the second frame.
  • clip with x frames creates (x-1) parameter set
  • 
  • Motion compensation in the stabilisation plugin:
    • translation = translation
    • euclidean = translation + rotation
    • similarity = translation + rotation + scale
    • perspective = warp
• Rendering step
  • smoothing the output by the parameter set
  • if you change the FPS (or shrink/edit a clip) you have to reanalyse... otherwise the parameter set is changed for your new frame at a different position

So meaning I have to keep everything remain the same even the resolution?

How can I export 720p version to client without doing the extra work changing the project properties?

Could Voukoder handle this with the resizing done in a separate step using its output filter?

RogerS, i think it probably would....

@alifftudm95 I'll check. Does it make a difference if rendered with 'Dynamic RAM' set to 0 or limiting the rendering threads to 1?