Render panel suggestions

relaxvideo wrote on 8/10/2023, 12:11 PM

I use Vegas19, don't know if 20 is better, 'cos i wait for 21 :)

So my tips:

- the current rendering fps text update is so quick, that it's impossible to read. Average fps is fine, but if i like to check the current fps, my eyes going crazy. This should be updated less frequently, say in every 0.5-1 seconds, so users can read it.

- estimated time needed for rendering is only accurate after 4%. It is so since many-many years. What's the explanation for this? If i multiple the number by 4 while rendering just hit 1%, i got the same time, as when i wait until 4%.

- often i need to pause a long render, but there is no such button. Would be nice..

- in many encoding programs if i stop rendering, the partial file will be correct, readable, playable. But not in Vegas, which delete the whole rendered movie. Why?

- as we all know, storage space is never enough. why Vegas need 3x much space for the rendering, than the finished file itself?
That wasn't the case in earlier time, for example with Vegas 11. Seems like video and audio are rendered separately and they will muxed at the end? If this is the case this slows down everything, because read and write at the same time on a same drive can be slow, especially on hdd (poor hdd head). By me a 10GB rendered video needs at least 30GB free space and extra 10 minute at the end because of muxing. Should be done differently.

- if i don't have that 30GB free space, say only 20GB, then it would be nice to see a warning message, that this is not enough. Both estimated size and free space are known and displayed. Now rendering start, and when finished, muxing process fail, mp4 will be corrupt, unplayable. All this after few hours of waiting in some cases..

And two small suggestions:
- the blue render progress bar line should be more thick, so we can see it from further too, not only from sitting in front of the monitor. Often i like to check it from 2-3m, and it's hard to see that thin line.

- when i select render template, folder and enter filename, would be nice to start rendering with the press of ENTER. Now filename will be highlighted (why?), and render won't start, no matter how many times i press enter. I have to press TAB or CLICK on the render button. Not a big deal, but in Vegas 11 it worked so much easier and quicker.

What you think?

Comments

relaxvideo wrote on 8/16/2023, 1:50 AM

Hmmm. No a single comment?

Are these problems not valid?

#1 Ryzen 5-1600, 16GB DDR4, Nvidia 1660 Super, M2-SSD, Acer freesync monitor

#2 i7-2600, 32GB, Nvidia 1660Ti, SSD for system, M2-SSD for work, 2x4TB hdd, LG 3D monitor +3DTV +3D projectors

Win10 x64, Vegas22 latest

RogerS wrote on 8/16/2023, 2:21 AM

You can add feature requests here to keep them in one place: https://www.vegascreativesoftware.info/us/forum/vegas-pro-feature-requests--134374/

Not sure most of these are problems, more good ideas to improve the VEGAS UI.

The biggest problem is the render failure with a lack of hard drive space- VEGAS should be able to calculate and warn about that before the render starts.

(21 seems the same as 20, FWIW.)

relaxvideo wrote on 8/16/2023, 2:25 AM

ok, thanks, i will post there.

Vegas DOES calculate it, it will show the estimated size and the free size, only NOT WARN when its not enough.
So we have to manually check with keep in mind that free space should be 3x the estimated size..

Last changed by relaxvideo on 8/16/2023, 2:26 AM, changed a total of 1 times.

#1 Ryzen 5-1600, 16GB DDR4, Nvidia 1660 Super, M2-SSD, Acer freesync monitor

#2 i7-2600, 32GB, Nvidia 1660Ti, SSD for system, M2-SSD for work, 2x4TB hdd, LG 3D monitor +3DTV +3D projectors

Win10 x64, Vegas22 latest

RogerS wrote on 8/16/2023, 2:52 AM

Yes, you're right and that's a good point- we need the warning.

I thought it was more like 2x the final render size but haven't tried to check it myself (these days I keep my c: drive from totally filling up). VEGAS devs know what the actual number is so I hope they can integrate this and help avoid failed renders and resulting complaints online.

Edmund-Papp wrote on 9/7/2023, 2:53 AM

I have a general question for the community or moderator about rendering in Vegas Pro 21. I use both Premiere Pro and Vegas Pro but VP is my first choice. Here is what I did. I rendered a 5 minute, 26 gig, Pro Res file from my iPhone 14 Pro Max in both Premiere Pro and Vegas Pro... the exact same MOV. file. Here what I learned. Premiere Pro rendered the file to a 4k Mp4 file in 4 minutes... the finished size was 2.5 gigs. I repeated this on Vegas Pro 21. It took 6 minutes and reduced the file size from 26 gigs to 870mgs. My conclusions... the fidelity of the Premiere pro render was visibly superior, not by much, but visible to the naked eye. I attribute this to the finished size of both renders... 2.5 gigs compared to 870megs. Is Vegas crunching the file too much?!

RogerS wrote on 9/7/2023, 3:08 AM

You picked different compression settings for VEGAS would be the answer. Try a much higher bitrate (compare both renders by right-clicking on them and going to properties. I assume you matched the resolution and framerate).

Feel free to share a screenshot of the render template for more detailed advice.

Wolfgang S. wrote on 9/7/2023, 3:36 AM

I use Vegas19, don't know if 20 is better, 'cos i wait for 21 :)

So my tips:

- the current rendering fps text update is so quick, that it's impossible to read. Average fps is fine, but if i like to check the current fps, my eyes going crazy. This should be updated less frequently, say in every 0.5-1 seconds, so users can read it.

Fully agree

- estimated time needed for rendering is only accurate after 4%. It is so since many-many years. What's the explanation for this? If i multiple the number by 4 while rendering just hit 1%, i got the same time, as when i wait until 4%.

no idea why they did it in this way

- often i need to pause a long render, but there is no such button. Would be nice..

fully agree

- in many encoding programs if i stop rendering, the partial file will be correct, readable, playable. But not in Vegas, which delete the whole rendered movie. Why?

that would be helpfull. Especially, if the render process crashes.

- as we all know, storage space is never enough. why Vegas need 3x much space for the rendering, than the finished file itself?
That wasn't the case in earlier time, for example with Vegas 11. Seems like video and audio are rendered separately and they will muxed at the end? If this is the case this slows down everything, because read and write at the same time on a same drive can be slow, especially on hdd (poor hdd head). By me a 10GB rendered video needs at least 30GB free space and extra 10 minute at the end because of muxing. Should be done differently.

agree

- if i don't have that 30GB free space, say only 20GB, then it would be nice to see a warning message, that this is not enough. Both estimated size and free space are known and displayed. Now rendering start, and when finished, muxing process fail, mp4 will be corrupt, unplayable. All this after few hours of waiting in some cases..

very biring, indeed

And two small suggestions:
- the blue render progress bar line should be more thick, so we can see it from further too, not only from sitting in front of the monitor. Often i like to check it from 2-3m, and it's hard to see that thin line.

- when i select render template, folder and enter filename, would be nice to start rendering with the press of ENTER. Now filename will be highlighted (why?), and render won't start, no matter how many times i press enter. I have to press TAB or CLICK on the render button. Not a big deal, but in Vegas 11 it worked so much easier and quicker.

What you think?

 

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

john_dennis wrote on 9/7/2023, 11:08 AM

@relaxvideo said: "Average fps is fine, but if i like to check the current fps, my eyes going crazy. This should be updated less frequently, say in every 0.5-1 seconds, so users can read it."

Displaying these data to two decimal places is completely useless. It pretends to have a level of precision that doesn't exist and no one needs. If renders went faster no one would ever look at the panel.

Anecdotal Folderol

My granddaughter's car has an analog speedometer and also displays a digital number in the center of the gauge. Two integer digits are perfectly fine for displaying the needed information. It probably displays three digits, but I've never seen it do it with a student driver.

relaxvideo wrote on 4/16/2024, 12:26 AM

any planned changes in render panel?

#1 Ryzen 5-1600, 16GB DDR4, Nvidia 1660 Super, M2-SSD, Acer freesync monitor

#2 i7-2600, 32GB, Nvidia 1660Ti, SSD for system, M2-SSD for work, 2x4TB hdd, LG 3D monitor +3DTV +3D projectors

Win10 x64, Vegas22 latest

Steve_Rhoden wrote on 4/16/2024, 7:34 AM

@Edmund-Papp Because the render settings you choose in Vegas are completely different from what you choose in Premier pro. There are a lot of variables that can be missed when doing these comparisons with Vegas..... Plus your query is different from what this thread is about, its always advisable you start a new post when the subject matter differs.

VEGASDerek wrote on 4/16/2024, 7:55 AM

@relaxvideo

Yes, our UX team has been working on a complete redesign of the export/render workflow. We are unsure when we will be able to implement the design they have come up with as we have many other high priority items on our plate, but this is in our roadmap.

Dexcon wrote on 4/16/2024, 8:13 AM

@VEGASDerek  ... I really hope that bulk rendering as has long been available in HitFilm Pro, DaVinci Resolve and even in Mercalli 5/6 SAL is on that roadmap. Needless to say, bulk rendering is way more convenient to individually edit a whole lot of events and add each of them to a render list than, as is the case in VP, to have to edit and then render each and every event individually. This is one of the reasons that I use DaVinci Resolve for some multi-event editing processes because I can work on a heap of video events and then render them as a bulk action.

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