I am currently downloading/installing Vegas pro 14!!! :)))

[David Shirey]

Wow, I downloaded the trial on my home computer and it’s crashing like crazy and running way worse than Vegas 11. It renders fine but if this isn’t going to just run perfectly out of the box I don’t think it’s worth $200 and a day or two of troubleshooting. Glad most people don’t seem to be having these problems though.

[Don Cobble]

MVP14 is crashing now in multicam
I do not know what this means? but its looking like it will be a while to become stable – disappointed
Extra Information
File: C:\Users\DCM Editor Win 10\AppData\Local\VEGAS Pro\14.0\dx_video_grovel_x64.log
File: C:\Users\DCM Editor Win 10\AppData\Local\VEGAS Pro\14.0\svfx_video_grovel_x64.log
File: C:\Users\DCM Editor Win 10\AppData\Local\VEGAS Pro\14.0\ocio_x64.log
File: C:\Users\DCM Editor Win 10\AppData\Local\VEGAS Pro\14.0\dx_grovel_x64.log
File: C:\Users\DCM Editor Win 10\AppData\Local\VEGAS Pro\14.0\gpu_video_x64.log

Problem Description
Application Name: VEGAS Pro
Application Version: Version 14.0 (Build 161) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module:
Fault Address: 0x00000000723D8400
Fault Offset: 0x00000000723D8400

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 14.0\vegas140.exe
Process Version: Version 14.0 (Build 161) 64-bit
Process Description: VEGAS Pro
Process Image Date: 2016-09-13 (Tue Sep 13) 21:47:24

[László Kovács]

Today I’ll try multicam 🙂
For me there was no crash so far.
(i5 3570, 8GB, win7 home premium 64bit, radeon hd6970)

Best regards

László Kovács

[László Kovács]

So I took a previous project which was a 2 cam shot. It opened the same as it did in Vegas 10.
I switched to multicam mode, with “show the full frame on external monitor” option.
This project was done originally in Vegas 10 – 1920*1080 25p -the footages are 1920*1080 25p from a Canon XA10,
and 1920*1080 50p from a JVC HM600.
In vegas 13 the multicam preview (half) was about 7-9 fps, in V14 9..12 fps on the same spot.
I made some random edits in V14, scrubbing, etc, did not crash.
Then took an older 4 cam shot, also done in Vegas10. The footages are from Canon XF100 and Sony V1, all 1440*1080 (HDV). The project itself is 1280*720 25p.
V14 was unable to open this project, it just hung (or didn’t wait enough…)
V13 opened the same project in a reasonable time. Then saved it as a V13 project.
V14 could open this, but took forever.
A quick, not too accurate comparison:
Originally Vegas 10 opens this project in 5 seconds approximately. Vegas 13 needs 14 seconds to get to the timeline.
Vegas 14 needed 54 seconds! And what’s worse: if I save this project in V14 format, it takes 2 and a half minute to get to the timeline.
(Looks like for some reason it reads through the whole .m2t and .mxf files)
There’s some room for improvement 😉
Once on the timeline, things go smooth and well.

Best regards

László Kovács

[Colin Moxey]

You will definitely need version 3.00 of Vegasaur to work in MVP 14.
I received an email from Vegasaur yesterday pointing this out and offering upgrades to this new version.
Anything less than version 3 will not work.

Depending on what version of Vegasaur you currently have, you might find that the upgrade price is very reasonable.

Good luck and thank you for your information on MVP 14

[Ron Whitaker]

Oh. Oh.

It appears that it may be best to wait for a few weeks before upgrading. Sounds like there’s some crashes out there going on.

[László Kovács]

Yes, I know. I got that mail too later that day.
First I want an activated fully functional V14 :))

Best regards

László Kovács

[Angelo Mike]

Downloading the pro suite upgrade (my first time using Boris plugins!) because of the $350 deal, along with other upgrades which seem pretty ground. But I’ve yet to try it. Even if it’s buggy, I at least want to buy it at the lower price and keep it while using Vegas 13 until bugs are fixed, but I’m going to try it out this afternoon.

[Angelo Mike]

So far, mostly good-I already used Boris FX with success. NewBlue FX, as usual, just makes Vegas crash when I click on the plugin.