Mocha jitter

Comments

Roger Bansemer wrote on 11/6/2023, 10:49 AM

> pip moving across the video which has no glitter effect.

Becasue it remains a fixed size ...

Good suggestion so I just used 3D motion tracking on the image that moves across the video slanting it as it goes and it does not "glitter".

Robert Johnston wrote on 11/6/2023, 11:29 AM

@Roger Bansemer As I said earlier, you need to reduce the image size so it's approximately the size it will take up on screen. I reduced the size to 4% of original size in Photoshop, and that got rid of the jitter.

Intel Core i7 10700K CPU @ 3.80GHz (to 4.65GHz), NVIDIA GeForce RTX 2060 SUPER 8GBytes. Memory 32 GBytes DDR4. Also Intel UHD Graphics 630. Mainboard: Dell Inc. PCI-Express 3.0 (8.0 GT/s) Comet Lake. Bench CPU Multi Thread: 5500.5 per CPU-Z.

Vegas Pro 21.0 (Build 108) with Mocha Vegas

Windows 11 not pro

Roger Bansemer wrote on 11/6/2023, 12:14 PM

@Roger Bansemer As I said earlier, you need to reduce the image size so it's approximately the size it will take up on screen. I reduced the size to 4% of original size in Photoshop, and that got rid of the jitter.

I gave it a try and reduced that photo to 525 x 700 and it still glitters.

Former user wrote on 11/6/2023, 1:56 PM

@Robert Johnston I don't know why but Voukoder won't render that MPEG-TS + your pic applied with Mocha Pro (no cropping or resizing the pic), the blue line at the top of the render window just skips across producing no render. & Vegas Magix AVC doesn't recognise the frame rate correctly, = signs next 60fps

 

It does render if I choose the 29.97 Magix AVC, still no glitter. I don't think i can help with this 🤷‍♂️

This is the render.

----

PS, This is the project size that MPEG-TS boat pic creates when dragged on my Vegas, Voukoder doesn't like this & won't render

Changed to a preset that is very basic, (no changes apart from what is seen in this pic, not Best or any other settings changed from Default.) This renders no prob with Voukoder.

You haven't shared your project settings so this may or may not be relevant .

 

RogerS wrote on 11/6/2023, 8:02 PM

Could you add the .veg project file to the Google drive?

RogerS wrote on 11/6/2023, 10:54 PM

I played with this a bit. As Gid wrote it needs to be progressive (not interlaced) so change that in project settings. I resized the image with pan/crop and it's smooth that way, no sparkles.

I don't really know how to use Mocha though to keep the image aligned with the moving ship (it pans and tilts as the ship moves).

Former user wrote on 11/7/2023, 12:09 AM

@RogerS

I don't really know how to use Mocha though to keep the image aligned with the moving ship (it pans and tilts as the ship moves).

Hi, it's not easy to explain but because the boat moves & is turning all options need to be ticked under the Track tab. Turning up the 'Min Pixels used' helps (not always)

At first for the vid above I tracked just outside the grey parallelogram area, but I had to drag the layer spline out at the top & quite a bit to the left at the bottom to stop it from slipping, this is Mocha Pro tho, the tracking spline & the blue insert Surface layer prob work a bit differently in Vegas Mocha , I know the spline holds the tracking data & the blue Surface layer is a child of the spline but I don't know if the data transferred from Vegas Mocha represents the spline or the surface layer.

Roger Bansemer wrote on 11/8/2023, 7:47 AM

Sorry I haven't responded in the past couple days. Had a slight case of the flu due to a flu shot.
Here's my property settings and the veg file on google drive.

https://drive.google.com/file/d/1V20RW2ehs6nCs-sfTBjCdF5_VGzyOmGd/view?usp=sharing

I haven't tried the suggestions yet as I'm still not feeling very well but will try later in the day. Thanks everyone.
 

Roger Bansemer wrote on 11/8/2023, 12:49 PM

Upon opening Vegas this morning I got a version update notice so I went ahead and did the update. It uninstalled v21 and installed v21.something... I don't know if the rest of you just got this update but it's the first it appeared on my system.
Anyway, I tried the "Glitter" problem, rendered it and it looks fine. No glitter. Can you believe it! After hours of me messing with this and all of you as well, this update seems to (at least for now) fixed the issue. I just don't know what to say except thanks for everyone for diving in to this and taking your time to do so.
I sometimes feel like using Vegas is like purchasing a new car and every few miles it breaks down and instead things working like I would expect, I have to rely on the forum and myself in order to get the car running again as it should.
I'll let you know if for some reason this happens again with the glitter thing.
Sincerely, Roger
 

MikeS wrote on 11/8/2023, 2:00 PM

Now this is odd - using your files from Google Drive that I downloaded just now (and using the provided .veg file) ... I get NO 'glitter' using latest version of Vegas Pro - v21 build 187. Even with a fullsize image ... I wonder if they've made changes to PiP? There's certainly nothing in the patch notes. And maybe it's just me ...

<fx edit> Ah, just seen your post above. So we've both seen the change. Not just me ...

Last changed by MikeS on 11/8/2023, 2:01 PM, changed a total of 1 times.

Vegas Post 22.0 Build 239
Boris FX Continuum for OFX 2025 Build 18.0.1.303 - 74
Boris FX Mocha Pro Plug-in 2024.5 v11.5.1 Build 60
Windows 10 Pro - 64-Bit
ASUS PRIME Z390-P motherboard
Intel Core i7-97000K @ 3.6GHz
RAM 32GB (2x 16GB) 2666MHz DDR4
GeForce RTX 2070 SUPER

Roger Bansemer wrote on 11/10/2023, 9:34 AM

Now this is odd - using your files from Google Drive that I downloaded just now (and using the provided .veg file) ... I get NO 'glitter' using latest version of Vegas Pro - v21 build 187. Even with a fullsize image ... I wonder if they've made changes to PiP? There's certainly nothing in the patch notes. And maybe it's just me ...

<fx edit> Ah, just seen your post above. So we've both seen the change. Not just me ...

I tried it again this morning and it works fine. We all sure spent a lot of time on this. Wonder if someone who does coding for Vegas saw the posts and fixed the bug.