VEGAS Pro 19 Update 5 (Build 643)

Comments

Bruggeling wrote on 6/6/2022, 12:02 PM
 

Do you have a test-video sample so others could crash-test it too?

It is a project with a lot of resources, 7 camera's running for more than an hour makes for a lot of Gbytes (wouldn't know how to make a test-sample). They were all synchronised with the seprate soundtrack and then put on a multicamera track. The 2 UHD tracks were cropped to HD to let the HD image follow the dancers with the Vegas event-pan, works very well.

All video proved to contain too much red and too little blue, this was corrected with colorgrading the whole track. Many events (every multicamera change creates a separate event) were corrected for brightness. After the colourgrading the real problems began, although I had already crashed many times, before the grading it was always possible to render without a hitch.

The dance-performance is rendered number by number, so not the whole hour in one piece, each number takes about 3 or 4 minutes and is a seperate mp4 file. For no obvious reason sometimes a number renders, but if you repeat that sometimes it will crash. The final 2 numbers simply do not render with colourgrading on.

I have been using Vegas from version 8, even writing an extension for it, so I guess I'm quite able to produce a video. Build 636 is just an update that needs an urgent update.

Last changed by Bruggeling on 6/6/2022, 12:51 PM, changed a total of 1 times.

Main cameras Panasonic S5, still using some FZ1000

Windows 11
Processor AMD Ryzen 7 3700X 8-Core Processor 4.20 GHz
GPU NVidia Geforce RTX 2070 super
RAM 32,0 GB

Main disk M2 2 Terabyte, other disks SSD on SATA, some on USB.

Howard-Vigorita wrote on 6/6/2022, 2:48 PM

@Bruggeling Curious what your system consists of. Working on a 636 multicam project right now, albeit with only 2 uhd plus 3 hd cameras and not experiencing the problems you mention. UHD shot with hevc 4:2:0 mp4 and HD with 1 Canon 4:2:2 mxf and 2 JVC 4:2:0 avc. I generally put one camera on each track and pre-glue the uhd clips as well as Canon hd clip together for one big clip per camera track before edit. And mix in externally recorded on-stage audio using the camera audio only for ambience, applause, and performers who wander away from a mic while talking. Sync video optically with a time display and external audio with clicks in the waveform. Cannot glue my jvc clips because they drop frames between clips so for those I have to sync each clip by eye with the waveform display.

I particularly love 636's track-based color grading which I apply after multicam cuts and expansion which has been working flawlessly for me. My systems mostly have amd gpus and 32- to 128-gigs ram. Might be helpful to diagnose your issues if you put system specs in your profile/signature. See mine for an example.

Bruggeling wrote on 6/7/2022, 3:44 AM

@Howard-Vigorita I followed your hint and put my PC specs in my profile. The specs are not the problem I think, because rendering goes very fast (all output to SSD), the project I work on is at 50 fps and the average rendering speed is about 100 fps. I have upgraded everything that can be upgraded, Windows, display driver, Vegas AI driver. I finished the editing by now, but just can't render. Cameras were 4 x Panasonic S5, 2 x Panasonic FZ1000. As the FZ1000 has no MOV output, I have recorded all to MP4, except 2 S5 that were recording UHD to MOV. Strange thing is that I managed to render 15 out of the 17 dances.

Talking about 'glueing' events. I wonder if there is a possibility to lock an event's location and duration, but still be able to change the crop and pan, brightness, colorgrading... everything that does not change it's synchronisation to the rest of the tracks. Even the events on the multicamera track would be a lot safer it you could lock them into place and still be able to change the look of the generated events.

Main cameras Panasonic S5, still using some FZ1000

Windows 11
Processor AMD Ryzen 7 3700X 8-Core Processor 4.20 GHz
GPU NVidia Geforce RTX 2070 super
RAM 32,0 GB

Main disk M2 2 Terabyte, other disks SSD on SATA, some on USB.

EfGe wrote on 6/7/2022, 4:11 AM

Disappointed.

Not a major thing this time, but it will definitely make me re think about future updates.

Why my preferences were reset? Temp directory, space bar function, etc. Why? Is it a bug or is this normal for Pro?

I don't want to have to re organize everything for patches/updates.

 

RogerS wrote on 6/7/2022, 6:09 AM

Preferences reset was definitely not a bug and isn't often needed for updates so you should be good for a while. I agree it's time consuming to fix everything and a warning in advance would be nice.

lan-mLMC wrote on 6/7/2022, 6:43 AM

All users who want to install this build are advised to back up this registry:

For all users who want to install this build, I personally recommend exporting the registry key 【HKEY_CURRENT_USER\SOFTWARE\Sony Creative Software\Vegas Pro\19.0】 into a .reg file to prevent the loss of preferences, UI placement (not the layout file), project presets, etc reported by many forum users / social media users.

If build 636 deletes your user data, you can roll back to build 550 and double-click .reg file to restore the data.  

Bruggeling wrote on 6/7/2022, 11:20 AM

@Howard-Vigorita in a separate post I have described how I solved the rendering crisis :-) for now.

Main cameras Panasonic S5, still using some FZ1000

Windows 11
Processor AMD Ryzen 7 3700X 8-Core Processor 4.20 GHz
GPU NVidia Geforce RTX 2070 super
RAM 32,0 GB

Main disk M2 2 Terabyte, other disks SSD on SATA, some on USB.

Sam-Fisher wrote on 6/8/2022, 4:20 AM

I would like to thank the developers for a lot of bugfixes. However, there are still some bugs to fix. Here is my list:

1) I'm still waiting for Optical flow resample mode working properly. (I have written about the problem HERE )

2) Window layout problems. I make all windows fx / media generator / crop / project media / etc... open in tabs fitting the whole space of the left panel without splitting it, but after some time it splits vertically into 2 (the standard set - project media/explorer/etc occurs as a separate part). I'm tired of restoring the layout every time.

3) Vegas crashes while loading if at least 1 network adapter is enabled (physical or virtual), but there is no internet connection and the root certificate was not obtained from the internet yet. For this reason vegas crashes on some PCs that are a part of a local network only (without the internet). The solution is to add the certificate manually. I am writing about it because Vegas 18 and earlier didn't have this issue.

4) Exr format is not in "all formats" by default when importing media. I have to choose "all files" to import exr sequence. It is strange because it was there in earlier versions of vegas.

5) Not a bug, but... Please, unblock the limit of playback rate or add it to internal settings!!! 0.050-4.0 is not enough. I don't see a real reason to set max limit except it might cause a bug we don't know about :)

The rest is fine. Thank you once again!

Bruggeling wrote on 6/8/2022, 4:35 AM

Nice to have colorgrading on different levels !  On event-level, it would be handy to affect all selected events, instead of just one.  When working with a multicamera track, often the same adjustments are needed for every take from a specific camera. I noticed that when you select more than 1 event the colorgrading panel is disabled.

Last changed by Bruggeling on 6/8/2022, 4:39 AM, changed a total of 1 times.

Main cameras Panasonic S5, still using some FZ1000

Windows 11
Processor AMD Ryzen 7 3700X 8-Core Processor 4.20 GHz
GPU NVidia Geforce RTX 2070 super
RAM 32,0 GB

Main disk M2 2 Terabyte, other disks SSD on SATA, some on USB.

Sam-Fisher wrote on 6/8/2022, 5:23 AM

Here is my protest against the latest UI abusing. The icons keep getting worse with each version of vegas.

Dexcon wrote on 6/8/2022, 5:45 AM

Re Auto-Ripple, I've moved the Auto-Ripple icon to the end of the Timeline Toolbar by selecting Options/Customize Timeline Toolbar and, in the RH 'Current toolbar buttons' field, highlighted the Auto-Ripple entry and used the Move Down Button to move it to the end of the entries. Then highlighting the Separator entry in the LH field, added the Separator to the RH field about 6 times just in front of the Auto-Ripple entry. This way, the Auto-Ripple button is well separated away from the other buttons/icons.

Then under Options/Preferences/Display (tab), the 'Button Highlight Color' field allows for the color of highlighted buttons/icons to be changed to a color of your choice - I've chosen red (255/0/0).

Nonetheless, I'd really like it if there was something larger and more eye-catching to alert that Auto-Ripple is activated (this has been raised a number of times over the years). I still regularly fall foul of forgetting/over-looking that it's 'on' - at least Undo in VP19 is usually quite quick compared to previous versions.

Last changed by Dexcon on 6/8/2022, 6:06 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

Robert123 wrote on 6/8/2022, 7:12 AM

Changing the pixel properties in the 'Project video properties window' makes Vegas crash. It never crashed on me before. 😕

VEGASDerek wrote on 6/8/2022, 9:20 AM

I don't see a real reason to set max limit except it might cause a bug we don't know about :)

Well, you kinda hit upon the problem right there.

Cielspacing wrote on 6/8/2022, 11:44 AM

I don't see a real reason to set max limit except it might cause a bug we don't know about :)

Well, you kinda hit upon the problem right there.

It's good to see attentiveness to detail from developers as we users in this channel voice our issues, usage particularities or even ideas with released patches and updates.
Here it could easily be appreciated how this communication could steer VEGAS into being a nuanced and satisfying tool for a broad user base. (As it has been increasingly so since MAGIX's uptake of VEGAS devs, imho).

Some released updates may need a fast modification/correction patch, even if it is just a requirement from a small group of users. Such resilient responsiveness is very much appreciated for sure.
With it, one could understand that given VEGAS complexity and its varied platforms and possible workflows, it would be wise not hurry too much said secondary patch. Maybe extra days or a few weeks, enough for a relevant group of us to thoroughly utilize and confirm most relevant (albeit minor) things are included as well.
We all could benefit after all.

BJIag wrote on 6/8/2022, 1:44 PM

Greetings, colleagues. Does anyone have a working script to disable resample on all video clips located on the timeline at once? My script doesn't work on the 19th version, but everything worked on the older ones. Thanks.

pierre-k wrote on 6/8/2022, 2:05 PM

I don't see a real reason to set max limit except it might cause a bug we don't know about :)

Well, you kinda hit upon the problem right there.

I have been asking for an increase in the upper limit for 15 years. I am glad that the time has come to finally resolve this.

Peter-Riding wrote on 6/8/2022, 4:45 PM

Re Auto-Ripple, I've moved the Auto-Ripple icon to the end of the Timeline Toolbar by selecting Options/Customize Timeline Toolbar and, in the RH 'Current toolbar buttons' field, highlighted the Auto-Ripple entry and used the Move Down Button to move it to the end of the entries. Then highlighting the Separator entry in the LH field, added the Separator to the RH field about 6 times just in front of the Auto-Ripple entry. This way, the Auto-Ripple button is well separated away from the other buttons/icons.

Then under Options/Preferences/Display (tab), the 'Button Highlight Color' field allows for the color of highlighted buttons/icons to be changed to a color of your choice - I've chosen red (255/0/0).

Nonetheless, I'd really like it if there was something larger and more eye-catching to alert that Auto-Ripple is activated (this has been raised a number of times over the years). I still regularly fall foul of forgetting/over-looking that it's 'on' - at least Undo in VP19 is usually quite quick compared to previous versions.

I keep Auto-ripple in the middle but as with you I use separators to make it easier to locate. Great idea to change it to Red. Just done that thanks :- )

In Davinci Resolve the default keyboard strokes are Del for ripple and Backspace for not-ripple. Maybe a good idea to do similar in Vegas by saving custom keystrokes rather than risking forgetting whether ripple was meant to be on or off.

Ustik wrote on 6/10/2022, 5:44 PM

Here is my protest against the latest UI abusing. The icons keep getting worse with each version of vegas.

I already mentioned this a few times since Vegas 19 was out.

 

Developers and a product owner don't listen, they live in their "Who are you, I know better" mindset bubble.

 

It's sad to mention this again, but the new v19 UI is shitty. Colors schemes and icons are the ugliest I've ever seen in a software.

 

 

Ustik wrote on 6/10/2022, 5:47 PM

Greetings, colleagues. Does anyone have a working script to disable resample on all video clips located on the timeline at once? My script doesn't work on the 19th version, but everything worked on the older ones. Thanks.

It's possible to achieve with Vegasaur.

Grazie wrote on 6/11/2022, 12:59 AM

It's sad to mention this again, but the new v19 UI is shitty. Colors schemes and icons are the ugliest I've ever seen in a software.

@Ustik - Do you have an example of what you want? Examples of other s/w that could be explored. I’m interested to read your thoughts and view a sampling.

Reyfox wrote on 6/11/2022, 5:49 AM

I personally don't mind the color changes and adapt to the icons. Where I do have an issue is with certain colors, you can not see the icons on the events on the timeline. I have to move my moue or work from memory what button I can not see. Yes, you can change the colors, but why should you have to? I would think that any color choice, that all the buttons would be visible.

And also think about new users to Vegas.... how will they react to it? It should be easy to see to access.

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

RogerS wrote on 6/11/2022, 7:42 AM

While I think the old icons looked completely dated and negatively reflected upon the program (just look at Soundforge- still looks like it's in the early 2000s), I find some of the new ones to be too cryptic. I want at least important ones to be immediately recognizable and agree key ones like auto ripple should stand out clearly as to whether it is enabled or not.

Ustik wrote on 6/11/2022, 11:47 PM

It's sad to mention this again, but the new v19 UI is shitty. Colors schemes and icons are the ugliest I've ever seen in a software.

@Ustik - Do you have an example of what you want? Examples of other s/w that could be explored. I’m interested to read your thoughts and view a sampling.

I already mentioned in this thread that Vegas 18 has an amazing, easy-to-read interface.

Similar icons/color schemes are used in a Vegasaur 4.

It's as easy as that.

Developers should leave the option to choose the color scheme, because users get used to it over the years.

But they just removed it in new v19 update. Because they can. Why not...

As an example, Davinci Resolve has a modern "clean" and easy to read interface.

Vegas 19 has track colors which are incompatible by any means. They are not complimentary, breaking all the rules of Johannes Itten and color design, whatever you can call it.

I would say the same about ugly "modern" icons.

95% of software in 2022 has an option for UI customization. I mean custom skins, color variations, user skins and so on.

It's very easy to implement, because it's the front end. Any developer know that.

 

 

 

Ustik wrote on 6/11/2022, 11:52 PM

I personally don't mind the color changes and adapt to the icons. Where I do have an issue is with certain colors, you can not see the icons on the events on the timeline. I have to move my moue or work from memory what button I can not see. Yes, you can change the colors, but why should you have to? I would think that any color choice, that all the buttons would be visible.

And also think about new users to Vegas.... how will they react to it? It should be easy to see to access.

I can tell you why - because the UI was not developed properly.

It was done "on-the-go" for sure.

There was lack of attentions from product owner just to meet another release deadline.

And after the release of Vegas 19 they had other, MORE IMPORTANT stuff on their backlog.

I'm 100% sure it was like that.

I have more to say - I can predict that the Vegas team don't have in office designer and the sketches of "new UI" were done on outsource by some freelancer.

The rest is history.