I just installed build 384 for Vegas pro 15. The program is now unusable  The program has crashed three times in a row trying to render a Mpeg2 file. On the fourth try the program ran 8 1/2 hours and froze at 10 percent done.. It produced a 3 1/2 minute clip at a very low quality. When I tried to use Vegas 14, I get unable to use files created in Vegas 15. What gives? Also, when adding chapter markers, the program was constantly freezing. It looks like I will have to start my project all over again using Vegas Pro 13. A whole day down the drain. And yes, I did restart my computer several times during this ordeal.

 

Hi Dominick
The problem you are experiencing with rendering to MPEG-2, is not a Vegas Pro 15 problem only.
I have experienced this problem myself, with many different versions of Vegas.
The solution that has always worked for me, is to turn off GPU Acceleration.
Go to Options/Preferences/Video - GPU Acceleration = OFF.
This problem only effects rendering to MPEG-2.
Also remember that if rendering for DVD, the MPEG-2 output for DVD is only Standard Definition video, not HD.

If you still experience problems after turning off GPU Acceleration, I would also recommend you reset Vegas Pro 15. After a reset, you will have to turn off GPU Acceleration again!
Instructions for how to reset here, if you don't know how to do that:
https://www.moviestudiozen.com/doctor-zen-faq/573-how-to-reset-sony-software-to-default-settings#a1

And finally, I always re-boot my computer before rendering to MPEG-2.

Regards
Derek

After my error 59 on startup I uninstalled VP15 and then reinstalled it, but now every time I start it up I have to activate it again, it did not seem to register the serial number. I have a back up of my drive and have now restored my drive to yesterday and it seems to ok now, just trying a render of a file I know is ok.

Where do you find build 387 ???

Where do you find build 387 ???

See if you'd get it using the DL options in section 3 or 4 here. You probably noted this though. Buid 384 still here ATM.

This is the direct link my download manager logged http://dl04.magix.net/2017/VEGASPro15/update/VEGAS_Pro_15.0.0.387_DE-EN-FR-ES_x64.exe

I did not install it, as Magix is almost hiding it from users. I assume there's no noticeable positives, it's release is just for people buying the superseded vegas15, when vegas16 is released.

Thanks for the link

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?

No. Not gonna worry more, I do have better framerate in preview with that 1050ti. Thanks for commenting and asking!

I have a Dell XPS 15 i7 Core Skylake with a Geforce 960M/Intel GPU, today I tried every driver version from the Gforce website to see if one would work with adjusting the FX and see the results in the preview, non of them worked, has anybody with the same spec laptop got any driver version to work on this error.

@michael-cookson the FAQ on this but you have obviously gone through all the suggestions there.

Hi Michael, XPS 15 GeForce 1050 here. Sadly, no. All that works for me is switching to Intel integrated graphics when I am about to color correct or do subtitles.

I have a Dell XPS 15 i7 Core Skylake with a Geforce 960M/Intel GPU, today I tried every driver version from the Gforce website to see if one would work with adjusting the FX and see the results in the preview, non of them worked, has anybody with the same spec laptop got any driver version to work on this error.

Is this with an external monitor connected or just the laptop display?

No its just the laptop, I do what RodgerS does when I need to color correct or FX, its no biggy but just annoying, I hope these things are fixed in the Version 16 , as they should have been in version 15.

No its just the laptop, I do what RodgerS does when I need to color correct or FX, its no biggy but just annoying, I hope these things are fixed in the Version 16 , as they should have been in version 15.

On some laptops, the discrete GPU is only active when an external display is connected. That keeps power consumption low, extending the laptop’s time it can operate on battery only.

On the XPS it stays active as far as I can tell. I only use it with an external display while plugged in, and the problem is with the discrete GPU only.

I have Vegas 15 Suite and Divinchi Resolve .

Does Vegas 16 have the same color capabilty As Divinchi Studio and Resolve?

Divinchi v15 hasDNxHR and more.

Vegas 16 isn't available yet. What do you mean by color capability?

VEGAS Pro 15 Update 6 (build 384) has been released. Please give us your feedback in this thread. We want to keep you informed about as much as we can and have your feedback, even

 

Customer complained that cello was still producing sound with operator standing up and bowing to the audience,investigated, customer is right. Vegas yet again messed the file pointer to the separate audio file up and selected a random incorrect start offset.

I have been hoping this bug would be fixed in the next update since I started using the comsumer version around version 12. Please be so kind as to fix that bug, it is a bug, it is not a feature to preserve, it is a pestinuisance; thank you!

Yes, I know, this bug is why everybody says restart at least Vegas and preferably the computer before you render. Yes, I omitted doing it. Yes, I only stop checked the file and on a spot check in the middle thinks look reasonable. The giveaway is that the cello does not go silent when it should and applause does not start as it should.
 

VEGAS Pro 15 Update 6 (build 384) has been released. Please give us your feedback in this thread. We want to keep you informed about as much as we can and have your feedback, even though this is not a big update.

If you already have build 384 or earlier installed, there is no need to uninstall it. The build 384 will overwrite your installation and retain your settings. Your computer will need to be online for activation after the update.

If you are installing VEGAS Pro 15 for the first time, it is generally better to install using a VEGAS Pro download manager. See here for details & links.

Official announcement with Patch Notes

VEGAS Pro 15 (build 384) installer

Previous general discussion thread

 

You asked for our feedback, well here is mine. Your update (384) was worthless. Never addressed or resolved the render issues I've been reporting that your failed customer support failed to address or properly respond to. You refused to grant my refund and as a legacy Vegas owner I have lost all faith in Vegas Pro and Magix. I spent the cash to purchase the Suite version of VP15 and it cost me a job and a nick on my business rep because of VP15's render flaws. Your lack of a fix, your lack of customer support, and the painful waste of cash testing you "Beta" VP15 has me very sore with Magix. LOL, and now you skip on past us and try throwing in VP16 which is probably just as broken as VP15. Have lost my faith in you. Thanks for nothing.

i think we need vp16 thread

vp 16 is out, should i use it or wait for next build

Just curious, do we have a chance to see another VP15 bug fix update?

Or they're done with VP15?

Unfortunately if you look at their build convention & history for vp15, the 2nd last bug fix build 384 is alarmingly close to 387 which had no bug fixes or features added. This is typical of an end of life build where they may update legal information & user agreements & updating to latest version abilities.