240 FPS video management on sony vegas Pro 17

pascal-TOURNACHE wrote on 2/11/2020, 3:15 AM

Hello, do you confirm that if we want to reduce the speed from a 240 fps video down to 30 fps video, as we can't exceed a 4X slow down, we have to do it in 2 steps. First move from 240 to 60 (4x) then render to 60 fps then finally perfom a 2X from this 60 fps video down to 30 fps. Thanks for clarification.

Comments

LongIslanderrr wrote on 2/11/2020, 3:33 AM

Right click the clip and insert a velocity envelope. that will allow you to slow it in 1 step.

3POINT wrote on 2/11/2020, 3:49 AM

Just set your project to 30 fps, rightclick your 240 fps in the Project Media map and choose "Add at Project Frame Rate".

j-v wrote on 2/11/2020, 3:58 AM

+1 for @3POINT
choose this setting

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Dexcon wrote on 2/11/2020, 3:59 AM

Another yet not dissimilar method is to right click the event, click on Properties and then click on the Conform to Project Frame Rate button in the Properties window. The field to the left of the button should then update to show the % frame rate compared to the event's original frame rate.

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 2/11/2020, 4:20 AM

Another yet not dissimilar method is to right click the event, click on Properties and then click on the Conform to Project Frame Rate button in the Properties window. The field to the left of the button should then update to show the % frame rate compared to the event's original frame rate.

This method, I cannot support, because you have to re-adjust then the event length afterwards and audio is not stretched.

Last changed by 3POINT on 2/11/2020, 4:21 AM, 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

Dexcon wrote on 2/11/2020, 4:43 AM

Each to his/her own … what works for one doesn't work for another. I used the Properties approach today because the project is at a very rough-cut stage, so every shot is eventually going to be trimmed for in/out points anyway. And the audio issue is not an issue for this project.

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 2/11/2020, 4:55 AM

Necessary re-adjusting event length is not the same as trimming and in my opinion an extra step, also you have to do this for every event separately, with the "add at project framerate method" you can import all necessary events at once, but as you said "each to his/her own..."

Last changed by 3POINT on 2/11/2020, 4:59 AM, 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

3POINT wrote on 2/11/2020, 5:14 AM

A good example for the use of the "add at project frame rate" option is following issue I had two years ago. In that time I had an actioncam with internal stabilization that only worked fine when recording at 47,952 fps. Unfortunately my TV doesn't support 47,952 fps. So I set my projectsettings to 50 fps, which is perfectly supported by my TV, and imported all 47,952 fps clips at 50 fps. While the audio is also speeded a little up, which isn't heard, I was able to easy edit and watch my holiday memories.

Dexcon wrote on 2/11/2020, 5:55 AM

@3POINT ... Please note that the OP has marked LongIslanderr's suggestion as the solution, yet that solution does not stretch the audio either, and adjusting the length of the event (whether its called trimming or otherwise) is also needed as adding the velocity envelope +/- 100% does not alter the length of the original event on the TL. I therefore assume that you do not support LongIslanderr's approach either.

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 2/11/2020, 6:09 AM

OP had already marked LongIslanderrs suggestion as "the solution" before I posted the "add at project frame rate" solution. Personally I find LongIslanders suggestion even worse than your's, but again "each to his/her own..." I really don't care...