VEGAS Pro 14.0 (Build 161) Released

Comments

Quitter wrote on 9/27/2016, 12:25 AM

something else?
reboot your PC an try again

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 10 Home 1903, i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
           Vegas Pro 14.0 Build 270

megabit wrote on 9/27/2016, 12:34 AM

Just did that, and this time a bunch of errors about not being able to extract registry keys....

Last changed by megabit on 9/27/2016, 12:35 AM, changed a total of 1 times.

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

Quitter wrote on 9/27/2016, 12:42 AM

Antivirussoftware or similar running?

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 10 Home 1903, i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
           Vegas Pro 14.0 Build 270

R0cky wrote on 9/27/2016, 10:24 AM

Where are the download files stored?  All you get from magix is a downloader/installer.  I haven't been able to find where it puts the install files.

Thanks jkerry, but that isn't correct.   A bunch of log files from the install, but not the install files.

Quitter wrote on 9/27/2016, 10:55 AM

Again, the install files are stored in Documents\ Magix Downloads

James Moore wrote on 9/27/2016, 2:04 PM

Ok, I went a bit the bullet and upgraded.  So far things have gone pretty well as I've gotten VP14 to load the Sony Izotope VST's which was important to me.

The one item I haven't been able to get working is PluralEyes which works as an extension.  Does anyone have a suggestion to how I might get it working in VP14? 

I tried to load a Pro Res 4444 clip but no joy.

 

 

Grazie wrote on 9/27/2016, 2:12 PM

Plural? Nothing yet. 

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

MemoriesFX wrote on 9/27/2016, 2:46 PM

Ok, I went a bit the bullet and upgraded.  So far things have gone pretty well as I've gotten VP14 to load the Sony Izotope VST's which was important to me.

The one item I haven't been able to get working is PluralEyes which works as an extension.  Does anyone have a suggestion to how I might get it working in VP14? 

I tried to load a Pro Res 4444 clip but no joy.

 

 

I have PluralEyes, Singular and the VASST series and none show up as extensions. This really anoys me as I use Plurel Eyes and the VASST tools often. So I still need to use Vegas 13 if I want to use these tools, which I do of course. I emailed support last Friday and no answer yet. If I cannot get support on this I will request a refund

jkerry wrote on 9/27/2016, 3:11 PM

I was advised by VASST that they are working updates so the programs will work with Vegas Pro 14.  Just that it will take a little time to get them all working.

James Moore wrote on 9/27/2016, 3:23 PM

I've contacted Red Giant asking about how to get PluralEyes to work with VP14.  We shall see what they say.

Is there a place to post bugs?  I'll try starting a new thread but I think I've got a bug going on with a Pro Res file. 

MemoriesFX wrote on 9/27/2016, 4:01 PM

I was advised by VASST that they are working updates so the programs will work with Vegas Pro 14.  Just that it will take a little time to get them all working.

How come VASST can answer right away but Magix does not respond to new support tickets? Not good Magix

ushere wrote on 9/27/2016, 7:02 PM

one of the problems with 'organisations' is the bigger they get the less well they can respond to their customers' concerns. this is especially evident with software, where small startups actively seek immediate feedback but as they grow the ability to implement changes rapidly becomes bogged down in inter-dept communications and marketing driven forces for more sales and rapid releases.

magix is a large organisation selling multiple overlapping products and needs to generate sales to continue expanding - vegas is simply another product that probably has to prove it's value before they invest too much in it.

george-sealy wrote on 9/28/2016, 10:35 PM

I am having severe problems with rendering.  VP14 is shutting down after about 4 minutes.  The program is unusable in its current form.  VP13 does not shut down.  

James Moore wrote on 9/29/2016, 5:36 AM

Is it all renders or a particular project?

george-sealy wrote on 9/29/2016, 12:03 PM

I have not tried other projects.  Reading the above posts I see there are issues with ProRes files.  This project has several of them on the timeline.  VP14 does not crash during editing.  But it sure does on the render.  So, are they fixing the problems with ProRes?  

george-sealy wrote on 9/29/2016, 12:07 PM

Also, I don't like how the fonts render in the application and the icons are goofy.  I am using an Nvidia 980Ti card which is outputing to a 4K display.  The font rendering in Sony VP13 is perfect.  I don't understand why there are all these issues when VP13 worked fine.  Didn't Sony sell them the source code?  Why did some developer go in and screw with things?  

James Moore wrote on 9/29/2016, 12:37 PM

I've done beta testing in the past for another companies editing software.  I've rarely had a beta build that has given me as much trouble as VP14.  I thought I would try doing a small job on it.  Basically I've got to clean up some audio on a 3 min short film.

First I had troubles with the Pro Res file they supplied me.  I've reported the info to Magix tech support.  So far no reply.  I rendered the Pro Res file to an MPG2 file in VP13 and used that as my reference video.  I am having great difficulty simply opening projects.  It often seizes up at 4% or 5% loading.  When I go to close the program it tells me a background process is running.  Sometimes I can stop it and get the program closed.  Other times I have to use task manager to close it.  Still it takes a few trys there as well.

Some projects open ok it seems (VP13 projects) I can then load the small project I am working on.  I decided to test a render.  I tried to render to MPG2 and it rendered but in play back the picture freezes at about the half way.  Then it renders black.  It's a mess.  I tried to open the project again to try a different render and VP14 hung again.

Not good.

By the way, I heard back from Red Giant about getting PluralEyes running and they wrote:

"Unfortunately we haven't got any version of PluralEyes that's yet compatible with Vegas Pro 14. It's something our project team would love to tackle but I couldn't give a definitive timeframe as to when it'll get implemented. I'll append this ticket into the tally system to hopefully give it some weight in development, until then there's nothing that can be done to get those two programs to work together. Sorry this wasn't a more fruitful query, but let me know if there's any other way I can help."

 

Quitter wrote on 9/29/2016, 1:09 PM

I think the major problem is the renaming.
Why else named some folders with items of VP14 still Sony?
They renamed it from Sony Vegas to Vegas, it would be better they had done this to Magix Vegas in the whole software. So it would be easier for all to adapt everything.
Also for Magix.

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 10 Home 1903, i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
           Vegas Pro 14.0 Build 270

vkmast wrote on 9/29/2016, 1:12 PM

The current renaming may help if there are further changes in ownership.

James Moore wrote on 9/29/2016, 1:14 PM

I did notice that the render pre-sets I created in VP13 appear in the VP14 list

Quitter wrote on 9/29/2016, 1:22 PM

The current renaming may help if there are further changes in ownership.

Yes, maybe, but I think it has not been fully carried out.

Last changed by Quitter on 9/29/2016, 1:23 PM, changed a total of 1 times.

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 10 Home 1903, i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
           Vegas Pro 14.0 Build 270

James Moore wrote on 9/29/2016, 3:02 PM

In my case the loading projects problem was because one file was on a network drive and there was a network problem so it just hung.

The render problem came from using a preset that I created in VP13 but which (I think mistakenly) is loaded in VP14 (because it is accessing the wrong directory for the presets?).

I shall continue working on this little project with VP14 for now.

set wrote on 9/29/2016, 6:48 PM

I think the major problem is the renaming.
Why else named some folders with items of VP14 still Sony?
They renamed it from Sony Vegas to Vegas, it would be better they had done this to Magix Vegas in the whole software. So it would be easier for all to adapt everything.
Also for Magix.

I had crashes on OFXs when trying Magix VP14 first time. In the middle of experiment, the crash window came out with report of each 3rd party OFX (in my case, I have NewBlueFX TotalFX3 and Red Giant Universe installed):

(Sorry, didn't copy-paste the details of report). Then closes down. Next time restart Magix VP14, I had no further issue.

BUT, if I'm running Sony VP13 again, in the middle of editing, I had similar crash like shown above, like happening in Magix VP14. Restart Sony VP13 - and no further issue. So, I guess I agree if renaming is totally confusing anyone.

(I have temporarily do system restore to previous condition before installing VP14 - so I currently have no VP14 for experiment - but probably return later)

MemoriesFX wrote on 9/29/2016, 10:11 PM

I keep getting an error message saying that  autosave failed to save project.. Don't know how to turn this off. Also I chose to have files in media bin open in trimmer when double clicked but it does not stick, so then I get files getting applied on the timeline over my edits. So maybe they fixed old bugs but seem to have new ones. The best thing is that rendering times seem better.