Why don't I get faster renders with a 1050ti in this Dell 490 dual 3 Ghz twin core Xeon box? - 1920 x 1080, 25 fps progressive scan, a bit of sony sharpness and a dash of SEMW automatic colour correction  

You didn't say what render codec you are using. Also, 3GHz CPU may not be fast enough to feed the GPU. Have you checked what the load is on you CPU and GPU?

CPU is at 74 to 80 percent evenly on all four cores, I can not find any information on gpu-load in win7. Codec is Magix AVC/AAC.

 

 

You can use a small software like GPU-Z to check the load. Did render it with NVENC?

It would be good if in future updates Vegas Pro can use more than 32gb of RAM and 2 NVIDIA Video Cards in SLI 1080ti or higher

I use GPU hardware too, I have never had Vegas crash the operating system (that smacks of a hardware problem in my opinion), and I am using an older underpowered (by todays standards) PC.

So what is the explanation?

 

Vegas might not be very well written software when it comes to accessing discreet GPU. For the longest time Vegas would not use my GPU, but it was trying, which is why this setup gave the slowest possible render & timeline update speed. Using integrated gpu fastest & not using any GPU 2nd fastest.

When Vegas refuses to use discreet GPU, I found the CPU use would be quite low, probably waiting for the GPU, then using CPU instead. I believe this to be the cause of the bulk of problems & gives the symptoms of only a few fps render & unusable timeline playback preview. Vegas should detect this problem & flash up an error screen advising user to try integrated gpu/no gpu option for maximum performance.

Vegas running so slow without showing an error screen is just bad press for this software.

Hi.

After seeing the "upgrade to v15 now, get v16 free" offer, I upgraded to v15, after not using Vegas for a while (I'm trying to love it again. Getting tired of Adobe's subscription model). Searched on both Google and this forum for a "Feature Request" thread but didn't find anything, so if there is one and somebody could tell me where it is, that would be cool. Till then, here it goes:

Multiple mask lanes (especially with the upcoming motion tracking feature)
Ability to trim multiple selected clips at the same time
Ability to unlink X and Y scale in Picture in Picture (now that we finally have an instinctive way of resizing and positioning stuff)
Zoomable preview window
Clip edge zone to drop transition is way too narrow (when dropping a transition on a single clip edge)
Nesting (It does have it already but way too clunky and crashes most of the time)
Normal dragging over timeline should lasso select multiple clips and not select loop region
Searching for a plugin still freezes everything for a while (not as much as before, but still)
Video preview still very sluggish (compared to PPro)
Ability do deliver pizza, find my TV remote control, and fix flat tires (Not urgent. Maybe in v18).

These are just a few that come to mind after testing it for a couple of days. Two of the most awaited features for me are on the way (stabilization and native motion tracking). Let's hope they're actually good.

Have a good day everybody.
 

Still a big problem using Wavs VST plugins. Seems worse on my main computer than others. Wave Arts VST work great. The audio just drops out completly

That really shouldn't be on the users

@RogerS

I don't disagree. Ideally users should not be able to "cause" a crash. But as we do not live in an ideal world, I wanted to ask the question...Why is it that some users have such terrible problems and some don't?

I use GPU hardware too, I have never had Vegas crash the operating system (that smacks of a hardware problem in my opinion), and I am using an older underpowered (by todays standards) PC.

So what is the explanation?

Vegas may have been designed more for older and underpowered hardware. My previous computer was a 2011-era HP Envy 14 and its dated Radeon card couldn't playback 4K, let alone edit it, but worked okay for HD and didn't crash Vegas often. I did have to used hacked drivers (thanks Leshcat!) to get Vegas to recognize my graphics card, and if I did that it wouldn't appear in Lightroom.

Switching to a new Windows 10 Dell XPS 15 with a NVIDIA 1050 card gave me a far faster system, but quite a few stability problems with Vegas. I don't think the hardware is flawed as I have no issues using other accelerated programs like Lightroom. The only OS crashes I have had are with Vegas 15. So I think Windows 10 and NVIDIA cards aren't a good match for Vegas and especially not NVENC rendering.

I don't think the hardware is flawed as I have no issues using other accelerated programs like Lightroom. The only OS crashes I have had are with Vegas 15. So I think Windows 10 and NVIDIA cards aren't a good match for Vegas and especially not NVENC rendering.

That logic is a bit speculative, but intuitively I would agree that things like NVENC, etc. are likely culprits. I use windows 10 with AMD r9 290 and intel i7 980x with no problems (using 4k media). I still feel that if you get an OS crash it is a hardware problem or incompatibility (not necessarily a physical flaw) and it should be caught at the OS level. I have seen this happen with devices like Blackmagic intensity, and it certainly was not restricted to Vegas.

Vegas has recently undergone a serious "engine refit" so it does make sense that those newer features give the most problems.

CPU is at 74 to 80 percent evenly on all four cores, I can not find any information on gpu-load in win7. Codec is Magix AVC/AAC.

 

 

You can use a small software like GPU-Z to check the load. Did render it with NVENC?

I don't know. I tend to assume that it did not, I do not seem to get additional choices in the render-menu. I'll see what GPU-Z can tell me. Thank you!

CPU is at 74 to 80 percent evenly on all four cores, I can not find any information on gpu-load in win7. Codec is Magix AVC/AAC.

 

 

You can use a small software like GPU-Z to check the load. Did render it with NVENC?

I don't know. I tend to assume that it did not, I do not seem to get additional choices in the render-menu. I'll see what GPU-Z can tell me. Thank you!

 

This is how it looks during a render:

CPU is at 74 to 80 percent evenly on all four cores, I can not find any information on gpu-load in win7. Codec is Magix AVC/AAC.

 

 

You can use a small software like GPU-Z to check the load. Did render it with NVENC?

I don't know. I tend to assume that it did not, I do not seem to get additional choices in the render-menu. I'll see what GPU-Z can tell me. Thank you!

 

This is how it looks during a render:

There seems to be some load on your GPU but hard to tell if it's just OpenCL's FX processing or NVENC encoding.

Just wanted to chime in and say that the current version of VEGAS PRO is better than it's been for a few years now. I make 48 Hour Film Projects each year, and it was such a blessing this year to have ZERO issues with the software during editing and rendering!
Things can always be improved, and better use of modern hardware is something I hope MAGIX gets in this software, but for now, I just want to offer kudos for improved stability.

CPU is at 74 to 80 percent evenly on all four cores, I can not find any information on gpu-load in win7. Codec is Magix AVC/AAC.

 

 

You can use a small software like GPU-Z to check the load. Did render it with NVENC?

I don't know. I tend to assume that it did not, I do not seem to get additional choices in the render-menu. I'll see what GPU-Z can tell me. Thank you!

 

This is how it looks during a render:

There seems to be some load on your GPU but hard to tell if it's just OpenCL's FX processing or NVENC encoding.

The software could be more helpful if unhappy with the hardware, but there is a solid hint in the lower CPU usage - about 75 percent - to the effect that the delay is caused by the motherboard, the lower than 80 percent cpu usage in rendering with the 1050 suggests that the CPU waits for data back from the GPU as I recall Microsofts bottleneck finding guidelines. Time for but not yet money for something newer to put that 1050ti in, it is quite obviously a lost cause to try to get more speed from this old box.

CPU is at 74 to 80 percent evenly on all four cores, I can not find any information on gpu-load in win7. Codec is Magix AVC/AAC.

 

 

You can use a small software like GPU-Z to check the load. Did render it with NVENC?

I don't know. I tend to assume that it did not, I do not seem to get additional choices in the render-menu. I'll see what GPU-Z can tell me. Thank you!

 

This is how it looks during a render:

There seems to be some load on your GPU but hard to tell if it's just OpenCL's FX processing or NVENC encoding.

The software could be more helpful if unhappy with the hardware, but there is a solid hint in the lower CPU usage - about 75 percent - to the effect that the delay is caused by the motherboard, the lower than 80 percent cpu usage in rendering with the 1050 suggests that the CPU waits for data back from the GPU as I recall Microsofts bottleneck finding guidelines. Time for but not yet money for something newer to put that 1050ti in, it is quite obviously a lost cause to try to get more speed from this old box.

 

You are one of the few users that can see it and is willing to admit it, hardware is the root of many issues. Anyways, did you check if you are rendering with NVENC? If not, you may get a little more out of the box.

When I put this 1050ti back into the box to get better preview after previously having experienced it a flakey combination Windows 7 went to microsoft and got a hardware certified driver from them instead of getting me a driver from nvidia. It is now a happy box. Not gonna tinker. But from what I have read on NVENC the fact that there is cuda use means that I am rendering via NVENC. Right now I am waiting for a 1280 x 720 render, same codec, it has higher CPU use and lower GPU use, I interprete this to support that it is the CPU wating for processed data back from GPU issue, less data to transmit back means less waiting spent waiting means higher cpu use. Now I just need to make people pay better and not ask for silly introduction prices so that I can get better hardware.

When I put this 1050ti back into the box to get better preview after previously having experienced it a flakey combination Windows 7 went to microsoft and got a hardware certified driver from them instead of getting me a driver from nvidia. It is now a happy box. Not gonna tinker. But from what I have read on NVENC the fact that there is cuda use means that I am rendering via NVENC. Right now I am waiting for a 1280 x 720 render, same codec, it has higher CPU use and lower GPU use, I interprete this to support that it is the CPU wating for processed data back from GPU issue, less data to transmit back means less waiting spent waiting means higher cpu use. Now I just need to make people pay better and not ask for silly introduction prices so that I can get better hardware.

 

Not necessarily are you seeing CUDA/NVENC use. Vegas uses OpenCL for FX processing and nothing else. Nvidia cards do support it and if lately made some improvements in that area, still not as good as AMD. The “load” you see in GPU-Z may well just come from FX processing. You can test that by re-encoding a short clip but without adding any FX or change to the clips video properties, basically making sure OpenCL does no work and only Nvidia’s encoding engine (NVENC) is doing all the work. I am still curious, are you seeing any option to render to MAGIX AVC with NVENC in the render as dialog?

For some reason, I ran Vegas Pro 15 build 384 in System Administrator Mode but turned out Vegas couldn't recognize *.veg files anymore. The *.veg files wouldn't show up in the "Open..." window's file list no matter choosing All files / All project and Media files / Vegas project files option for the file extension.

I don't think the hardware is flawed as I have no issues using other accelerated programs like Lightroom. The only OS crashes I have had are with Vegas 15. So I think Windows 10 and NVIDIA cards aren't a good match for Vegas and especially not NVENC rendering.

That logic is a bit speculative, but intuitively I would agree that things like NVENC, etc. are likely culprits. I use windows 10 with AMD r9 290 and intel i7 980x with no problems (using 4k media). I still feel that if you get an OS crash it is a hardware problem or incompatibility (not necessarily a physical flaw) and it should be caught at the OS level. I have seen this happen with devices like Blackmagic intensity, and it certainly was not restricted to Vegas.

Vegas has recently undergone a serious "engine refit" so it does make sense that those newer features give the most problems.

Hi @Kinvermark, your helpful comment prompted me to research this further. Apparently the 2017 Dell XPS 15 (9560) has known issues with power management that cause sudden OS shutdowns. I think the only program I had to push it hard enough to trigger this was Vegas. I downloaded a benchmark program (Heaven) and it shut down the system a few seconds in.

I did online research which had me roll back the Intel Dynamic Platform and Thermal Framework to AO4 https://www.dell.com/community/XPS/Dell-XPS-15-9560-Shuts-down-randomly/td-p/5712086/page/2 and now I can complete the benchmark just fine. While I don't expect this will fix Vegas render glitches, if it gets rid of shutdowns I'll be very happy. While I was at it I slightly undervolted the system which should help with occasional temperature throttling.

UPDATE: render glitches still in place but the fans are much quieter while rendering now

Since the Build 316 I have to disable So4 dll to make my a7III XAVCS clips playback smoothly, when will it to be fixed again?

My question as well. Otherwise periodic black screens and other issue. If I then want to use the higher quality output from my GH5, I have to re-enable it. This is clearly broken, and it needs fixing in 15.

Does Vegas Pro Handle Adobe Premier Pro and AfterEfects Correctly Yet ? Meaning Projects From them .:)

Hi, What are the patch/update notes for Update7, build 387?

thankyou

Re build 387.

oh thanks. Hmm so probably an end of use final revision that doesn't contain any fixes of note.

Not that i'm having any major problems now, but some people will be upset.