VEGAS Pro 15 Update 5 (build 361) - General Discussion

Comments

ColdHardDrewth wrote on 6/7/2018, 3:54 AM

THANK YOU! This is so great, beautiful, and incredible! I'm so glad I upgraded from Studio to Pro. The only bug I seem to have is definitely an annoying one... When you go to "file, add media," the search function doesn't work. I'm not sure if this is a Windows 10 issue or a Vegas 15 but I'm certain it wasn't happening in the past. Often when I go to add a file I want to search for it or start typing the first letter but that does nothing now :(

Still working for me in VP15 build 361 with my out-of-date Windows 10 version 1511.

Sadly in the new build of Windows today it's still happening (but only in vegas search). I will contact Windows 10, I guess it's their bad but hopefully they'll fix it.

Processor    Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz   3.70 GHz
Installed RAM    32.0 GB (31.8 GB usable)
System type    64-bit operating system, x64-based processor
Edition    Windows 11 Home Insider Preview
Version    22H2
Installed on    ‎7/‎14/‎2022
OS build    25158.1000

AxExel wrote on 6/7/2018, 3:25 PM

No, HEVC hardware encoding was not brought in until the 1000 series cards. I don't even think it decodes HEVC, or it's not very good at it if it does, as I have a 970 and my PC chokes trying to decode HEVC above 50mbps.

I've just downloaded the trial of this build and used the Hevc present

In fact it does work (GTX 980 has not full Hevc encoding support mainly chroma subsample, but vegas only uses supported one 4:2:0 [looked it up with media.info program])

Encoding support is full in GM204 chips

So I can confirm that GM204 gpu's (in my case GTX 980) does work

Can anyone else confirm what AxExel reports here that say a 9 series Nvidia card does support hevc Nvenc hardware encoding/rendering in VP15 361?

You can always download the trial version and check it for yourself with dualboot to not overwrite your current vegas version

Anyway the Hevec is locked to main 4.1 profile from what I've noticed

Former user wrote on 6/7/2018, 10:27 PM

In fact it does work (GTX 980 has not full Hevc encoding support mainly chroma subsample, but vegas only uses supported one 4:2:0 [looked it up with media.info program])

Encoding support is full in GM204 chips

So I can confirm that GM204 gpu's (in my case GTX 980) does work

Can anyone else confirm what AxExel reports here that say a 9 series Nvidia card does support hevc Nvenc hardware encoding/rendering in VP15 361?

I don't have such a card but going by nvidia specs 9 series cards should work fine with HEVC

 

Former user wrote on 6/8/2018, 3:15 AM

Maybe @VEGASDerek could clarify ... “As for HEVC encoding for NVidia, a 10xx series card is required. Older cards did not have the HEVC encoder.”

Maybe he was thinking of 10 bit hevc?

Zaffindo wrote on 6/10/2018, 12:37 PM

Good Work. Speed up things for me. User since Vegas 11.

Thanks.

fr0sty wrote on 6/10/2018, 3:22 PM

No, HEVC hardware encoding was not brought in until the 1000 series cards. I don't even think it decodes HEVC, or it's not very good at it if it does, as I have a 970 and my PC chokes trying to decode HEVC above 50mbps.

I've just downloaded the trial of this build and used the Hevc present

In fact it does work (GTX 980 has not full Hevc encoding support mainly chroma subsample, but vegas only uses supported one 4:2:0 [looked it up with media.info program])

Encoding support is full in GM204 chips

So I can confirm that GM204 gpu's (in my case GTX 980) does work

Can anyone else confirm what AxExel reports here that say a 9 series Nvidia card does support hevc Nvenc hardware encoding/rendering in VP15 361?

I get no hardware support for HEVC on my GTX970 in Vegas.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

hessam wrote on 6/11/2018, 2:47 AM

@OldSmoke

Any preliminary observations about preview performance improvements with VCE in Vegas 15?


VCE like NVENC does not improve preview performance, it is primarily for rendering.

NVENC is still a mess - at least for me. I had to revert to the older Mainconcept encoder as using NVENC causes random white flashing of some of my footage. I've attached a sample without audio that shows what I'm referring to.

I will admit - this update to Vegas 15 seems about as solid as I've EVER experienced. Still laggy on playback when using some intensive FX applied (Neat Video, motion title graphics, etc), but this release is really a breath of fresh air and has me excited about editing again. I was really dreading rebuilding the projects I had done in Vegas over to Premiere Pro CS6 - which I believe I may finally be able to retire.

My deepest gratitude and thanks to all the programmers who worked on this update!


Random white flashes here too. It occurs independently of preview quality settings. "Magic bullet Look" and "Filmconvert" applied to track. all plugins and VGA driver are up to date.

GTX 1080 Ti

pierre-k wrote on 6/11/2018, 3:30 AM

@OldSmoke

Any preliminary observations about preview performance improvements with VCE in Vegas 15?


VCE like NVENC does not improve preview performance, it is primarily for rendering.

NVENC is still a mess - at least for me. I had to revert to the older Mainconcept encoder as using NVENC causes random white flashing of some of my footage. I've attached a sample without audio that shows what I'm referring to.

I will admit - this update to Vegas 15 seems about as solid as I've EVER experienced. Still laggy on playback when using some intensive FX applied (Neat Video, motion title graphics, etc), but this release is really a breath of fresh air and has me excited about editing again. I was really dreading rebuilding the projects I had done in Vegas over to Premiere Pro CS6 - which I believe I may finally be able to retire.

My deepest gratitude and thanks to all the programmers who worked on this update!


Random white flashes here too. It occurs independently of preview quality settings. "Magic bullet Look" and "Filmconvert" applied to track. all plugins and VGA driver are up to date.

GTX 1080 Ti

Did you try to disable Dynamic RAM at 0?

1. Zero dynamic RAM

2. Restart Vegas

3. Render project

 

Reyfox wrote on 6/11/2018, 4:25 AM

@pierre-k with Dynamic RAM set to "zero", how would you preview say, using Shift+B?

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: 22.5.1, testing 24.7.1

Gigabyte X570 Elite Motherboard

pierre-k wrote on 6/11/2018, 4:31 AM

Dynamic RAM set to "zero" just for Render your project. It helps me.

hessam wrote on 6/11/2018, 4:38 AM

@OldSmoke

Any preliminary observations about preview performance improvements with VCE in Vegas 15?


VCE like NVENC does not improve preview performance, it is primarily for rendering.

NVENC is still a mess - at least for me. I had to revert to the older Mainconcept encoder as using NVENC causes random white flashing of some of my footage. I've attached a sample without audio that shows what I'm referring to.

I will admit - this update to Vegas 15 seems about as solid as I've EVER experienced. Still laggy on playback when using some intensive FX applied (Neat Video, motion title graphics, etc), but this release is really a breath of fresh air and has me excited about editing again. I was really dreading rebuilding the projects I had done in Vegas over to Premiere Pro CS6 - which I believe I may finally be able to retire.

My deepest gratitude and thanks to all the programmers who worked on this update!


Random white flashes here too. It occurs independently of preview quality settings. "Magic bullet Look" and "Filmconvert" applied to track. all plugins and VGA driver are up to date.

GTX 1080 Ti

Did you try to disable Dynamic RAM at 0?

1. Zero dynamic RAM

2. Restart Vegas

3. Render project

 


Haven't tested render yet. But preview in editing is the major problem here.

ritsmer wrote on 6/11/2018, 5:05 AM

The "Dynamic Preview Ram" (DPR) has been THE Buzzword around here for many years.

The Vegas help defines it so:

"When your project includes compositing and complex video effects, you may not be able to preview your project at its full frame rate.

If you prefer not to prerender your project, you can dedicate a portion of your RAM to cache video frames that cannot be rendered in real time."

Changing this DPR, however, has been noted to have a substantial influence on other things too:

In older Vegas versions there was a peak setting around 100-150 MB which gave the fastest render speed.

And many posts here propose setting the DPR to 0 or whatever number in order to remedy crashes and other things.

With no guidance we Vegas users can only guess - and we use (read: waste) a lot of time experimenting - hoping that THE Buzzword might bring some improvement of - ah - something..

Now to Magix and the Vegas developers: Please once and for all give us a thorough description of what DPR is (besides for caching preview video frames) and what else we can use it for ?

If this significant info has been somewhere already please supply a link and disregard this post.

Reyfox wrote on 6/11/2018, 11:57 AM

@ritsmer, a clear explanation would be great. I've increased DPR to 2GB just to preview an 8 second basic title with shadow and text only. It was from Titles & Text>Slide Right. Anything less would not play back the entire 8 second title. It was slow to render to RAM (RAM speed DDR4 3200), and considering how "simple" it is, I would think that my overclocked AMD 1700X would be able to play it back. Vegas 15 can't, even with Preview set to Draft Auto.

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: 22.5.1, testing 24.7.1

Gigabyte X570 Elite Motherboard

supergafudo wrote on 6/11/2018, 12:53 PM

thank your for this amazing release. the best is that now I can use AMD hardware enconde for superfast render. just one thing, when you try to create a personalize frame size and rate in a AMD hardware encode option the software (obviously) get you an error because the block of the GPU does not support this frame size.

the problem is that error is so generic that sometimes if you do not understand how hardware encode works you think that the feature is broken. please change this error msg or just do not give the option for custom frame rates and size when you rendrr via gpu.

AxExel wrote on 6/11/2018, 6:37 PM

There is a crash happening when you alt tab from Vegas to any other window and then back to Vegas and the quickly pressing play preview Vegas will hang

NickHope wrote on 6/12/2018, 1:27 AM

There is a crash happening when you alt tab from Vegas to any other window and then back to Vegas and the quickly pressing play preview Vegas will hang

@AxExel Please submit a support request at https://support2.magix.com/customer/en/vegas/form , including as much detailed information about the problem as you can. That's the best way to draw the developers' attention to bugs and get them into their backlog.

JoeAustin wrote on 6/12/2018, 6:10 PM

I've used the proxy creation feature many, many times, and this is a new one. It may or may not have to do with the 361 update, but I can't think of any other variable that has changed on my system since. When selecting media, and choosing create proxy, I get the following:

An error occurred while creating a proxy file for a stream.

The reason for this error could not be determined.

This used to work without a hitch. Still does in 13. Hopefully the fault is known?

 

JoeAustin wrote on 6/13/2018, 7:57 AM

I've used the proxy creation feature many, many times, and this is a new one. It may or may not have to do with the 361 update, but I can't think of any other variable that has changed on my system since. When selecting media, and choosing create proxy, I get the following:

An error occurred while creating a proxy file for a stream.

The reason for this error could not be determined.

This used to work without a hitch. Still does in 13. Hopefully the fault is known?

 

It turns out that unselecting "Enable QSV where available" in general preferences allowed proxies to be built without the error. It occured to me that it was probably related to this, as I get the same error when I try to render MP4 files using QSV. I'm not quite clear if this is some problem specific to my system, or if in fact QSV rendering is just broken. Can other render successfully using Intel QSV?

NickHope wrote on 6/13/2018, 8:46 AM

@JoeAustin What CPU and GPU are you using?

JoeAustin wrote on 6/13/2018, 9:48 AM

Hi Nick,

I have the i7 4790K and it is not overclocked. The video card is a Radeon R380. Also in default mode. If there's any hope to get QSV working, that would be awesome.

michael-cookson wrote on 6/13/2018, 12:14 PM

I have read a lot of posts on this thread so I thought I would try something on my system, I have a Dell Xps 15 i7 with a Intel and Nvidia card in it, the Nvidia card is a Gtx 960M and Intel is a HD 530.

I have a 4k video from my Mavic Pro its 8 mins long and has curves Fx, Neat video profile and a D-log lut on the time line.

I have tried a lot of different render options and everyone I have tried does not use either card to render the video, the CPU is at 99 to 100% and both cards never get higher than 15% use. Whats the point of having a good graphics card if the Vegas is not going to use it.?

Some of the render options I have tried do nothing, it goes through the render process but takes hours, but nothing happens when I watch the performance tab, its like the laptop is sitting at idle?.

Just rendering a avc file at the moment using the Intel card, the gpu is 4% my i7 CPU is at 100%, it looks like its going to take 75 mins to render.

If I try and use the so called fast Nvidia GTX960M card the same projects takes 3.5 hours to render, am I missing something with my setup?.

 

supergafudo wrote on 6/13/2018, 1:19 PM

I have read a lot of posts on this thread so I thought I would try something on my system, I have a Dell Xps 15 i7 with a Intel and Nvidia card in it, the Nvidia card is a Gtx 960M and Intel is a HD 530.

I have a 4k video from my Mavic Pro its 8 mins long and has curves Fx, Neat video profile and a D-log lut on the time line.

I have tried a lot of different render options and everyone I have tried does not use either card to render the video, the CPU is at 99 to 100% and both cards never get higher than 15% use. Whats the point of having a good graphics card if the Vegas is not going to use it.?

Some of the render options I have tried do nothing, it goes through the render process but takes hours, but nothing happens when I watch the performance tab, its like the laptop is sitting at idle?.

Just rendering a avc file at the moment using the Intel card, the gpu is 4% my i7 CPU is at 100%, it looks like its going to take 75 mins to render.

If I try and use the so called fast Nvidia GTX960M card the same projects takes 3.5 hours to render, am I missing something with my setup?.

 

well you need to understand how a GPU encode. the GPU pass the video in a specific block in your card, thats why you are only seeing the GPU at 4% because you are not using all your GPU, just this special block. and usually the encoding block is the same in a $1000 card than in a $100 card so you are not going to see much faster render speed in a expensive card than in a cheap one, the diference is in the openGL, 3d games, memory etc.. etc...

fr0sty wrote on 6/13/2018, 2:54 PM

I have read a lot of posts on this thread so I thought I would try something on my system, I have a Dell Xps 15 i7 with a Intel and Nvidia card in it, the Nvidia card is a Gtx 960M and Intel is a HD 530.

I have a 4k video from my Mavic Pro its 8 mins long and has curves Fx, Neat video profile and a D-log lut on the time line.

I have tried a lot of different render options and everyone I have tried does not use either card to render the video, the CPU is at 99 to 100% and both cards never get higher than 15% use. Whats the point of having a good graphics card if the Vegas is not going to use it.?

Some of the render options I have tried do nothing, it goes through the render process but takes hours, but nothing happens when I watch the performance tab, its like the laptop is sitting at idle?.

Just rendering a avc file at the moment using the Intel card, the gpu is 4% my i7 CPU is at 100%, it looks like its going to take 75 mins to render.

If I try and use the so called fast Nvidia GTX960M card the same projects takes 3.5 hours to render, am I missing something with my setup?.

 

Neat Video will bring any system to a crawl. You need to go into Neat Video's settings, it has options for you to specify the number of CPU cores plus GPU acceleration. Set it to use about half of your available VRAM on your graphics card, leaving some for Vegas as well. This will improve the speed of your renders, and you will notice much more of your GPU being utilized.

Another reason you aren't seeing high utilization, with Neat Video running, it is maxing out your system, and the GPU isn't getting the frame for a while... it only takes it a small amount of time to encode the frame, then it's back to waiting on Neat Video for the next frame. If you have Neat Video's GPU and CPU utilization tuned well in its settings (it has a wizard that will run tests to suggest the best settings), then that process of the GPU waiting for Neat Video won't take as long.

Last changed by fr0sty on 6/13/2018, 5:34 PM, changed a total of 1 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

michael-cookson wrote on 6/13/2018, 5:09 PM

Wow fr0sty, I have been playing with the settings in Neat Video and Vegas, I set DRP to 150, it was at 200, I then did as you suggested and used the optimization option in NV to see what that came up with, I could get 1.5 using this method.

I then went through the options manually and tweaked it till I got the best settings, this turned out to be 1.89.

The same project now that took just over three hours to render with my Nvidia card is now telling me it should be done 49 mins 😎