VEGAS Pro 14 Update 3 (build 201)

Back to post

Comments

ion-marin wrote on 12/3/2016, 11:08 AM

The trimmer Mouse behavior when dragging a video to timeline is very very bad. if you pull slightly sideways it ruins your in/out points and make another selection. the way it use to be was perfect. Now i had to downgrade. it is unusable this way... ruins the fast workflow vegas was famous for.

Guido3d wrote on 12/3/2016, 12:03 PM

Why "net notify" VEGAS function doesn't work and "notify and link" to me to the new update??? Fix this please... Not even an email...just a Facebook news that I've seen just today....

fhu wrote on 12/3/2016, 12:05 PM

Agreed, ion. it's been noted on this thread. I hope they tweak the trimmer setting so it works more smoothly.

SKALPOVICH wrote on 12/3/2016, 6:04 PM

Always hold grey color :(

paul-priestley wrote on 12/4/2016, 4:01 AM

Installed build 201 and doing my first render since buying Pro 14. My video is 35 minutes long and I've made a lot of use of the Newblue plugins supplied with Pro 14 especially chroma key and saturation EQ. So far it has taken 14 hours and 20 minutes to complete 54% of the render and it is telling me it will complete in 18 hours time. In Pro 13 the render would take approximately twice to three times the length of the video. I am using the same settings as Pro 13 and no GPU acceleration. My kit is I7 4770 cpu, 24 gb ram and gtx 750ti with Windows 10 latest edition. This needs sorting Magix PLEASE i have a life to live and deadlines to meet..

 

ed-sharpe wrote on 12/4/2016, 4:08 AM

so I am ok staying with 13 then for a while maybe?

SKALPOVICH wrote on 12/4/2016, 4:29 AM

Velocity does not work X40 for me, and i also have the problem with titler pro 3, the titler library pro3 actually planted the software, impossible to use this plugin, also i would like to change the old gray color of vegas pro, It's old! Thank you guy's

paul-priestley wrote on 12/4/2016, 7:03 AM

I certainly would until all the issues are resolved.

Jam_One wrote on 12/4/2016, 3:46 PM

1) There are at least 2 sorts of grey color (Two Shades Of Gray) in UI. These can not get old being neutral/achromatic reference. One is "Vegas color scheme", the other one seems to act like "System color". I never bothered to experiment after setting System&everything to "classic win-98 style" neutral grey. Long time ago. For the neutral/achromatic referencing purposes.
👉 If you hate gray that much, try unchecking "Use Vegas color scheme" and then tuning system colors to your taste.

 

2) Many people do dramatically confuse "GPU acceleration" of encoding & "GPU acceleration" of the timeline / FX processing. This is really ought to be written in the first lines of FAQ.
These two kinds of GPU's engagement are being controlled by different "switches". Everybody having doubts is to check one's course of action. The main "switch" for timeline/FX proc is located in "Preferences -> Video".
The user's fiddling with "GPU to the render" is limited nowadays. So.
👉 After checking the GPU is identified & enabled in Vegas you absolutely have to make sure the use of GPU is also supported & successfully enabled in third party plugins of yours.

 

(Needless to say I have same rendering times in V14 and V11. Never used V12, V13; found them both slower than V11.)

Last changed by Jam_One on 12/4/2016, 3:52 PM, changed a total of 3 times.

Win 7 Ultimate | Intel i7-4790K @ 4GHz | nVidia GTX 760 4GB * 2

SSD | 32 GB RAM | No Swap file | No Overclock | GPU-in-CPU OFF

t.A.T.u. F.o.R.e.V.e.R.!

 

Jam_One wrote on 12/4/2016, 4:12 PM

P.S.:
Also, if problems are experienced after updating Vegas or plugins and are believed to be related to the update, the very first step to make is

if exist "C:\Users\*username*\AppData\Local\VEGAS Pro\14.0\" (
del /f /s /q "C:\Users\*username*\AppData\Local\VEGAS Pro\14.0\" )

 

Last changed by Jam_One on 12/4/2016, 4:13 PM, changed a total of 1 times.

Win 7 Ultimate | Intel i7-4790K @ 4GHz | nVidia GTX 760 4GB * 2

SSD | 32 GB RAM | No Swap file | No Overclock | GPU-in-CPU OFF

t.A.T.u. F.o.R.e.V.e.R.!

 

gary-rebholz wrote on 12/5/2016, 8:41 AM

Velocity does not work X40 for me...

 

SKALPOVICH, the new velocity limit is 1,000% (10x). To get to 40x you also need to set the timeline event's Playback Rate to 4.0. Are you saying you've done this and you still don't get 40x speed?

MrGrunthunter wrote on 12/5/2016, 5:24 PM

When I upgraded to VEGAS PRO 14 from 13 last Sept I didn't have proDAD Mercalli or NewBlueFX installed. After I downloaded build 201 I can now see proDAD and NewBlueFX installed but they are asking me for activation codes! I submitted a Customer Service request over a week ago but can't seem to get a reply back from them. Anyone else having this issue?

VEGAS_EricD wrote on 12/6/2016, 9:04 AM

@MrGrunthunter - we just responded to your ticket with your order information.  This includes your serials for all products on the order. 

DeTomasi wrote on 12/7/2016, 5:18 AM

How do I update my Steam Version build? Just have 189 :(

MrGrunthunter wrote on 12/7/2016, 6:07 AM

@MrGrunthunter - we just responded to your ticket with your order information.  This includes your serials for all products on the order. 

Greatly Appreciated Eric. Thank You.

 

Andreas wrote on 12/8/2016, 6:32 AM

Can you fix video FX for Threshold, TV simulator. It not show correct menu.

vkmast wrote on 12/8/2016, 6:49 AM

Read this thread and the link(s) there to see if the suggestions would help

https://www.vegascreativesoftware.info/us/forum/video-media-generator-window-problem--104386/

Andreas wrote on 12/9/2016, 6:26 AM

No suggestions help. If I disable in "vegas140.exe" display scaling. Than it is ok, but everything else go wrong, To small icon and font.

marcinzm wrote on 12/9/2016, 4:31 PM

I have GTX 980 TI graphics card with GPU NVENC support. Unfortunately your enhancements for GPU in build 201 didn`t satisfy me. Please write to me when you add support for this video card or maybe you added it and I need to set up something but I have been using Vegas Pro softoware since Sony Vegas Pro 9 version, so I am know your software well.

Please reply me.

 

If you are bored, drink water, you will want to pee. -> Albert Einstein - my idol!

I am 42. I have been creating videos since 2009 (the date when my first daughter was born in). My first video software was Pinnacle, next one was Sony Vegas 8 (I am not sure if remember it correctly). I am also a developer and wedding movie operator and editor. For example: I have created an Android app which let me control Vegas Pro rendering progress level on Android smartphone. I created it for fun, because I also love programming. I also created my own plugin for Audio To Text feature specified usage from Vegas Pro 19. I created proxy creation plugin which uses multiple GPU threads (maximum 3) to create proxy files for Vegas Pro. I also written many others plugin/softwares which enhance my video editing, also wedding editing.

Camera/video camera: Sony FX3, Sony A7 III, Sony FDR AX 100, Canon 5D Mark III, GoPro Hero Black 7,8,9,10

Lenses for Sony: Tamron 28-75mm F/2.8 Di III , Sony 24mm gm 1.4 FE, Sony 20 mm G FE 1.8

Lenses for Canon: Canon EF 24-70 mm F/2.8 L USM, Canon 70-200 f/2.8 L

Drone: DJI Mavic 3 & DJI Phantom 4 Pro v2.0

 

Editing: Vegas Pro 20 (365) with a lot of third party plugins, also my own plugins written in C#

 

PC:

CPU: Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz   3.31 GHz

RAM: 128 GB

GPU: Nvidia RTX 2080 TI

storage: 4 SSD drives (including two M.2 flash drives) and two HDD drives

Windows system: 10 Home edition

marcinzm wrote on 12/9/2016, 4:41 PM

Another nice feature would be changing the active clicked icon background 50% opacity color. I have to be patient a lot to figure out if my buttons are clicked or not, because background color is so soft that it is hard to figure out. In the previous version of Vegas there were no such problem. Easy to fix, easy to develop.

If you are bored, drink water, you will want to pee. -> Albert Einstein - my idol!

I am 42. I have been creating videos since 2009 (the date when my first daughter was born in). My first video software was Pinnacle, next one was Sony Vegas 8 (I am not sure if remember it correctly). I am also a developer and wedding movie operator and editor. For example: I have created an Android app which let me control Vegas Pro rendering progress level on Android smartphone. I created it for fun, because I also love programming. I also created my own plugin for Audio To Text feature specified usage from Vegas Pro 19. I created proxy creation plugin which uses multiple GPU threads (maximum 3) to create proxy files for Vegas Pro. I also written many others plugin/softwares which enhance my video editing, also wedding editing.

Camera/video camera: Sony FX3, Sony A7 III, Sony FDR AX 100, Canon 5D Mark III, GoPro Hero Black 7,8,9,10

Lenses for Sony: Tamron 28-75mm F/2.8 Di III , Sony 24mm gm 1.4 FE, Sony 20 mm G FE 1.8

Lenses for Canon: Canon EF 24-70 mm F/2.8 L USM, Canon 70-200 f/2.8 L

Drone: DJI Mavic 3 & DJI Phantom 4 Pro v2.0

 

Editing: Vegas Pro 20 (365) with a lot of third party plugins, also my own plugins written in C#

 

PC:

CPU: Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz   3.31 GHz

RAM: 128 GB

GPU: Nvidia RTX 2080 TI

storage: 4 SSD drives (including two M.2 flash drives) and two HDD drives

Windows system: 10 Home edition

Fiola wrote on 12/15/2016, 3:40 AM

It seems that I have bigger problem than you guys here in .201. I am working on several projects. At one time, I spent 3 days now on editing footage from one event.

The problem is. The Veg file is no longer be able be opened. Why on earth is this a problem.

This is the steps I did before:

  1. Working on the project
  2. Save project using "save icon"
  3. Exit the Vegas
  4. Get myself back to the computer
  5. Open the Vegas
  6. Open the project
  7. Vegas crashes everytime at 50%

Of course, I CAN'T that project get open in my Vegas 13. I understand why, but never did this to me.

In the project were just MP4 and MOV source files (no HEVC, no ProRes). No plugins needed. No special effects. No third party elements than just pure -SONY- (Edit: MAGIX) tools.

I just can't get it, how it is possible, that somehow Vegas 14 is corrupting save projects itself.

And if it's just my computer. Excuse me, please, but how exactly am I supposed to know, if log file generated from vegas didn't contain anything, my codecs are up-to-date, Windows 10 is up-to-date, GPU drivers are up-to-date. I have 32GB RAM available on the system, GTX 1070, SSD ...

Going back to Vegas 13 for now. :(

Fiola wrote on 12/15/2016, 4:03 AM

This is the steps I did before:

  1. Working on the project
  2. Save project using "save icon"
  3. Exit the Vegas
  4. Get myself back to the computer
  5. Open the Vegas
  6. Open the project
  7. Vegas crashes everytime at 50%

Funny thing! I just did an experiement. I renamed the folder, where the project was in. From "20 - PS EXPERIENCE" to "20 - PS EXPERIENCE222" .. it just opened!

So, that's new! Amazing! I have to keep renaming the folders now...

set wrote on 12/15/2016, 4:16 AM

Extremely weird... try saving multiple vegas projects... do save and save-as.

(I never had this issues, but have heard very-very few people had this)

Fiola wrote on 12/15/2016, 4:53 AM

Extremely weird... try saving multiple vegas projects... do save and save-as.

(I never had this issues, but have heard very-very few people had this)


It's happening regulerly. 3 of my projects are now corrupted this way. Is there any chance I can help you in order to find issue? I tried to create like 100% "reproduction" of the problem but I can't find the action which is causing it. It seems to be unrelated to anything I tried.

I am not sure, but based on the fact that when I rename the folder - it automatically links every media - maybe the "search for media" function could make this weird problem?

You will probably know more what is happening inside the Vegas 14 on 50%.

In Vegas 13 - when I changed the name of the folder where the project was saved, later when I opened the project it still needed to manually direct media files into renamed folder. But Vegas 14 links them automatically,... Probably more intelligent opening makes this problem? :)

Sorry, just blind guessing here. I am just now happy, that this rename workaround works.