Rendering takes so long 5,3k 60fps 10bit Nvenc

vasya-pauk wrote on 7/15/2024, 8:44 PM

Hi. I'm recordingimy Hero12 videos on 5,3k 60fps and 10bit. Just want to be sure whether is this okay. My videos length is one hour. Right now is 1,20 hours elapsed and there is still zero percentage. Average speed in performance: 0,30fps. Current speed is varying from 0 to 10fps. I use nvidia encoding type and the final size of my video is 87GB. I know maybe it is too much but I want to get the highest quality possible out of it. I have Lenovo ideapad gaming 3 Arch05. 1650ti 4GB, 16GB RAM and Amd ryzen 4000 series. Can you help me? I've closed all other apps. My video also includes scenes from google earth studio. Just want to know whether this is a normal speed for that file size.

Comments

vasya-pauk wrote on 7/15/2024, 8:53 PM

https://imgur.com/U4as4po. Cpu usage is jumping. 99 percent or 40 percent or 70 percent. Its varying promptly. Ram takes 8gb

Adis-a wrote on 7/15/2024, 10:09 PM

Hm, doubt that you can render much faster using a laptop.

RogerS wrote on 7/15/2024, 11:03 PM

Feel free to try the benchmarks in my signature to see if it's something specific to your media and project.

Note, you can also upload images to this forum- see the arrow next to the smiley face.

vasya-pauk wrote on 7/16/2024, 9:55 AM

I'm still didn't yet defined what to do about it and the current render speed of my video in fps is 0,12fps. I've tried all different settings for render and don't know what to do. I've tried to export the projects to davinci and premiere pro also but it didn't working. They simply refusing to open my project...

vasya-pauk wrote on 7/16/2024, 9:59 AM

vasya-pauk wrote on 7/16/2024, 10:01 AM

Don't pay attention to 32 floating point idk why it shows it but i've already changed it for 8 bit full range

RogerS wrote on 7/16/2024, 10:56 PM

I didn't see any new benchmarking results submitted. Happy to take a look if you do one using the exact settings written there. The older benchmark works with VP 16 or newer.

vasya-pauk wrote on 7/17/2024, 6:54 AM

Sorry i just don't really know how to use it. I'm quite new to all of this. Now i will try

vasya-pauk wrote on 7/17/2024, 7:04 AM

Yeah, rendering goes well. so maybe footage too hard for this? I'm recording on gopro12 using these specs

RogerS wrote on 7/17/2024, 7:33 AM

If you fill out the form I can give better advice. If dynamic ram preview is at 0MB put it back on the default.

Otherwise it may just be that this GoPro footage is hard to decode so try to choose different settings in your camera that are easier to edit or be patient with your renders.

Dexcon wrote on 7/17/2024, 8:07 AM

... it may just be that this GoPro footage is hard to decode so try to choose different settings in your camera that are easier to edit or be patient with your renders.

Agreed. The GoPro settings are at its maximums:

5,3k 60fps and 10bit

... but your computer is somewhat below recommended specifications for 4K Vegas Pro.

If you have an unavoidable need for 5.3K at 10 bits, then you'll need to expect long render times with your current computer.

Maybe do a GoPro comparison test between 5.3k / 10 bit and 4k / 8 bit and see if there is an appreciable difference between the two settings for your editing/rendering experience as well as your end display destination.

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

mark-y wrote on 7/17/2024, 8:45 AM

... it may just be that this GoPro footage is hard to decode so try to choose different settings in your camera that are easier to edit or be patient with your renders.

Agreed. The GoPro settings are at its maximums:

5,3k 60fps and 10bit

... but your computer is somewhat below recommended specifications for 4K Vegas Pro.

If you have an unavoidable need for 5.3K at 10 bits, then you'll need to expect long render times with your current computer.

Maybe do a GoPro comparison test between 5.3k / 10 bit and 4k / 8 bit and see if there is an appreciable difference between the two settings for your editing/rendering experience as well as your end display destination.


@Dexcon Thank you for your sentient reply. GoPro footage is easily one of the most difficult acquisition formats for Vegas to swallow. That is unlikely to change.

Editing and rendering it on a laptop only makes matters worse. Pushing the format to its limits, which are absurd by today's normal delivery standards, makes it a darned near impossible task.

Your suggestion of shooting and producing at something closer to a minimally deliverable format is best described as basic training.

Good job.

@vasya-pauk You are admirable as a new user, since you are honest about your level of experience, and you have not laid claim to knowledge you do not have, nor do you lash out at the software and your peers. Welcome to the discussions; I know you will become a trusted contributor.

One thing you may try, after shooting your GoPro at sane settings, is to first transcode your camera footage to ProRes 422, a Digital Intermediate format, which is a lot easier on the Vegas decoding and processing engine, and "may" render faster for you, contingent on the other filters, effects, and timeline transformations in your Vegas project.

Now I will relax my jaw, and hopefully the bite marks on my tongue will heal quickly.

john_dennis wrote on 7/17/2024, 9:30 AM

@vasya-pauk said: "I'm quite new to all of this." 

vasya-pauk wrote on 7/18/2024, 8:25 AM

... it may just be that this GoPro footage is hard to decode so try to choose different settings in your camera that are easier to edit or be patient with your renders.

Agreed. The GoPro settings are at its maximums:

5,3k 60fps and 10bit

... but your computer is somewhat below recommended specifications for 4K Vegas Pro.

If you have an unavoidable need for 5.3K at 10 bits, then you'll need to expect long render times with your current computer.

Maybe do a GoPro comparison test between 5.3k / 10 bit and 4k / 8 bit and see if there is an appreciable difference between the two settings for your editing/rendering experience as well as your end display destination.


@Dexcon Thank you for your sentient reply. GoPro footage is easily one of the most difficult acquisition formats for Vegas to swallow. That is unlikely to change.

Editing and rendering it on a laptop only makes matters worse. Pushing the format to its limits, which are absurd by today's normal delivery standards, makes it a darned near impossible task.

Your suggestion of shooting and producing at something closer to a minimally deliverable format is best described as basic training.

Good job.

@vasya-pauk You are admirable as a new user, since you are honest about your level of experience, and you have not laid claim to knowledge you do not have, nor do you lash out at the software and your peers. Welcome to the discussions; I know you will become a trusted contributor.

One thing you may try, after shooting your GoPro at sane settings, is to first transcode your camera footage to ProRes 422, a Digital Intermediate format, which is a lot easier on the Vegas decoding and processing engine, and "may" render faster for you, contingent on the other filters, effects, and timeline transformations in your Vegas project.

Now I will relax my jaw, and hopefully the bite marks on my tongue will heal quickly.

Thanks I thought about this. Now I will try to convert it to prores.

Yes, i've got accustomed to Vegas from childhood when I was editing some videos from games. Now it seems to me that It didn't changed much and it is still convenient to work in.

Dexcon wrote on 7/18/2024, 8:34 AM

@vasya-pauk  ...

Now I will try to convert it to prores.

Please do a small test transcode to ProRes first. The reason, ProRes transcodes are massively huge compared to the original media size. Try comparing a ProRes render to a MAGIX AVC/AAC render.

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

vasya-pauk wrote on 7/18/2024, 8:38 AM

@vasya-pauk  ...

Now I will try to convert it to prores.

Please do a small test transcode to ProRes first. The reason, ProRes transcodes are massively huge compared to the original media size. Try comparing a ProRes render to a MAGIX AVC/AAC render.

Is it the same huge as transcode to DNxHR(mov)? Because I thought to transcode it to this format and tried but has been forced to buy two terabytes external hdd to export transcoded files straight to it. But Vegas is more convenient for me to work in than Davinci. So I suppose Prores is going to be better if there is not much of a difference in sizes

Dexcon wrote on 7/18/2024, 8:45 AM

ProRes is great, but let your own transcode tests help you make the decision for yourself.

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

vasya-pauk wrote on 7/18/2024, 8:46 AM

Thanks a lot, I will try

mark-y wrote on 7/18/2024, 12:01 PM

DNxHR is 32 bit architecture. I think you will not be so happy editing it.