Frame logic

Comments

Dexcon wrote on 7/18/2023, 7:15 AM

Maybe, just maybe, regardless of what fps is set in Vegas Pro's project settings, Mocha Pro still sees the video as 60fps whereas the max fps in Mocha Pro (inexplicably) is 59.94 fps and therefore needs to correct with a 1 frame adjustment - in this case this being the last frame.

To test this, try transcoding and rendering the 60 fps video to 30 fps (via Vegas Pro, Handbrake, ShutterEncoder, etc) and see if the same missing first frame occurs in Mocha Pro with its project settings also set to 30 fps.

Otherwise, just reducing the video event by one frame (as you've said works) may well be the best overall solution.

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

Former user wrote on 7/18/2023, 8:04 AM

I suspect that the intent was to for you to make sure that the project settings in both Vegas Pro and Mocha Pro are the same. In Mocha Pro, check File/Preferences/Clip (tab) for the fps rate:

@beaverbrook @Adis-a @Dexcon

That picture that is being shared is Preferences not Project Settings,

Here i loaded a 120p clip, Vegas reads it as 119.880p

Mocha Project settings reads it as the same 119.880p

------------

PS, why the Mocha Project settings say Length (frames) 1666 but both timeline counters say 1665 must be because the counter incs frame 0 in the total count, Boris would have to answer that.

 

Dexcon wrote on 7/18/2023, 8:10 AM

@Former user  ... the reference to project settings was meant as a general reference to settings - it was in the next clause of that sentence that it was pointed out that the specific item in Mocha Pro was Preferences:

In Mocha Pro, check File/Preferences/Clip (tab)

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

Former user wrote on 7/18/2023, 8:23 AM

 

@Former user  ... the reference to project settings was meant as a general reference to settings - it was in the next clause of that sentence that it was pointed out that the specific item in Mocha Pro was Preferences:

In Mocha Pro, check File/Preferences/Clip (tab)

@Dexcon Sorry I don't understand that, ?

@beaverbrook wrote -

Mocha Pro's frame rate was indeed different at like 24. But I switched it to 59.94 (the max) and it still didn't change the issue where I still have to place the top layer ending one frame extended to the right.

On this 120p project mine reads 24, I'd need to read up on it or ask Boris as I'm not sure how the Preferences 'Clip' setting relates to the Project settings,

Dexcon wrote on 7/18/2023, 8:27 AM

@Former user  .. please read my comment again:

I suspect that the intent was to for you to make sure that the project settings in both Vegas Pro and Mocha Pro are the same. In Mocha Pro, check File/Preferences/Clip (tab) for the fps rate:

Sorry - it wasn't in the second clause, it was in the next sentence.

Last changed by Dexcon on 7/18/2023, 8:38 AM, changed a total of 1 times.

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

Former user wrote on 7/18/2023, 8:39 AM

@Dexcon Yes I can read, read your comment again, you say "make sure that the project settings in both Vegas Pro and Mocha Pro are the same" but the Preferences (Clip) & Project setting in Mocha are different things, Look at my pictures again.

I just searched Boris, it wasn't helpful

Clip -

If you are working on a number of shots that share the same clip attributes (the same video standard, frame rate and color space), it can be useful to set a default clip setting. Then you will not have to re-enter the same clip information each time you load a clip.

Dexcon wrote on 7/18/2023, 8:42 AM

Oh dear! Sigh!

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

Former user wrote on 7/18/2023, 8:51 AM

@Dexcon No need for that!

Former user wrote on 7/18/2023, 9:10 AM

I suspect that the intent was to for you to make sure that the project settings in both Vegas Pro and Mocha Pro are the same. In Mocha Pro, check File/Preferences/Clip (tab) for the fps rate:

@Dexcon You inc Project settings & Preferences in the same comment, they may well be in separate sentences but you followed one with the other in the same paragraph implying they were related. Even @beaverbrook read it like that with his reply comment - "Mocha Pro's frame rate was indeed different at like 24..... "

So explain how Preferences - Clip relates to all this instead of just repeating yourself & exasperating?

beaverbrook wrote on 7/18/2023, 7:35 PM

Adis-a wrote earlier:

Media frame rate and Project frame rate, do they match?

I suspect that the intent was to for you to make sure that the project settings in both Vegas Pro and Mocha Pro are the same. In Mocha Pro, check File/Preferences/Clip (tab) for the fps rate:

 

Yes.

If they don't match you'll have either overlapping or a gap, like here:

 

 

 

One clip is 23,97 fps inside a 23,97 fps Project, the other, showing a gap in the timeline, is 25. If everything matches Project fps that should reflect in Mocha as well. I think, that is. :)

Mocha Pro's frame rate was indeed different at like 24. But I switched it to 59.94 (the max) and it still didn't change the issue where I still have to place the top layer ending one frame extended to the right.

AFAIK, your clip frame rate is 60 fps, so set Project frame rate to 60 (you can just type 60 in the box, like here:

...should do the trick, I think. :)

Adis-a wrote earlier:

Media frame rate and Project frame rate, do they match?

I suspect that the intent was to for you to make sure that the project settings in both Vegas Pro and Mocha Pro are the same. In Mocha Pro, check File/Preferences/Clip (tab) for the fps rate:

 

Yes.

If they don't match you'll have either overlapping or a gap, like here:

 

 

 

One clip is 23,97 fps inside a 23,97 fps Project, the other, showing a gap in the timeline, is 25. If everything matches Project fps that should reflect in Mocha as well. I think, that is. :)

Mocha Pro's frame rate was indeed different at like 24. But I switched it to 59.94 (the max) and it still didn't change the issue where I still have to place the top layer ending one frame extended to the right.

AFAIK, your clip frame rate is 60 fps, so set Project frame rate to 60 (you can just type 60 in the box, like here:

...should do the trick, I think. :)

I can't set it to 60 because that makes the Render Preview feature not work. I have to keep it at 59.94 (Or something like that).

13900K - RTX 4090 - 64 GB memory - 2 TB disk
PRO Z690-A WIFI (MS-7D25) 2.0
Windows 11 Pro
Vegas Pro, v 22.0, build 239
I own the entire BorisFX Suite, but here are my commonly used applications and their versions as listed in BorisFX Hub:
BorisFX Continuum, v 2025.0.3
Mocha Pro, v 2025.0.2
Particle Illusion, v 2025.0.2

Adis-a wrote on 7/18/2023, 9:40 PM

Adis-a wrote earlier:

Media frame rate and Project frame rate, do they match?

I suspect that the intent was to for you to make sure that the project settings in both Vegas Pro and Mocha Pro are the same. In Mocha Pro, check File/Preferences/Clip (tab) for the fps rate:

 

Yes.

If they don't match you'll have either overlapping or a gap, like here:

 

 

 

One clip is 23,97 fps inside a 23,97 fps Project, the other, showing a gap in the timeline, is 25. If everything matches Project fps that should reflect in Mocha as well. I think, that is. :)

Mocha Pro's frame rate was indeed different at like 24. But I switched it to 59.94 (the max) and it still didn't change the issue where I still have to place the top layer ending one frame extended to the right.

AFAIK, your clip frame rate is 60 fps, so set Project frame rate to 60 (you can just type 60 in the box, like here:

...should do the trick, I think. :)

Adis-a wrote earlier:

Media frame rate and Project frame rate, do they match?

I suspect that the intent was to for you to make sure that the project settings in both Vegas Pro and Mocha Pro are the same. In Mocha Pro, check File/Preferences/Clip (tab) for the fps rate:

 

Yes.

If they don't match you'll have either overlapping or a gap, like here:

 

 

 

One clip is 23,97 fps inside a 23,97 fps Project, the other, showing a gap in the timeline, is 25. If everything matches Project fps that should reflect in Mocha as well. I think, that is. :)

Mocha Pro's frame rate was indeed different at like 24. But I switched it to 59.94 (the max) and it still didn't change the issue where I still have to place the top layer ending one frame extended to the right.

AFAIK, your clip frame rate is 60 fps, so set Project frame rate to 60 (you can just type 60 in the box, like here:

...should do the trick, I think. :)

I can't set it to 60 because that makes the Render Preview feature not work. I have to keep it at 59.94 (Or something like that).

Selectively Prerender Video, that it? Shift+M?

Hm, works on my end:

 

 

beaverbrook wrote on 7/18/2023, 9:45 PM

Selectively Prerender Video, that it? Shift+M?

Hm, works on my end:

 

 

Well, I just resolved that ploblem. It was the problem I had just before this thread. And setting to 59.4 from 60 is exactly what fixed it.

Since I already hacked the workaround for this thread, this is less important compared to the risk of breaking my prerenders again.

13900K - RTX 4090 - 64 GB memory - 2 TB disk
PRO Z690-A WIFI (MS-7D25) 2.0
Windows 11 Pro
Vegas Pro, v 22.0, build 239
I own the entire BorisFX Suite, but here are my commonly used applications and their versions as listed in BorisFX Hub:
BorisFX Continuum, v 2025.0.3
Mocha Pro, v 2025.0.2
Particle Illusion, v 2025.0.2

beaverbrook wrote on 7/19/2023, 6:42 AM

I am getting the same problem with a single-layered clip.
The cutout does not appear in the last frame.
Also, if I include the Mocha Pro effect in the first frame of the scene, it appears in the last frame of the last scene.

The solution is to shift the split one frame to the right at the beginning and end.
This discards the first frame of the scene and includes the first frame of the next scene.

Very confusing, but it seems to work.

*It won't let me add any pictures* *sigh...*

Last changed by beaverbrook on 7/19/2023, 6:51 AM, changed a total of 4 times.

13900K - RTX 4090 - 64 GB memory - 2 TB disk
PRO Z690-A WIFI (MS-7D25) 2.0
Windows 11 Pro
Vegas Pro, v 22.0, build 239
I own the entire BorisFX Suite, but here are my commonly used applications and their versions as listed in BorisFX Hub:
BorisFX Continuum, v 2025.0.3
Mocha Pro, v 2025.0.2
Particle Illusion, v 2025.0.2