VEGAS Pro 14 Update 3 (build 201)

Comments

Cosmin_Gurau wrote on 11/22/2016, 6:46 AM

See, I don't like having to do that. My usual workflow was converting them to Cineform Filmscan 2. But there was some noticeable loss of quality. If the Windows version of Premiere can do it, then VEGAS needs to be able to do it too, in order to compete. Vegas needs to "just work". And it will. I have full confidence in this team, and this community.

LabTwenty wrote on 11/23/2016, 12:39 PM

Support for ProRes 4444 XQ too? let me know, thanks.

richardbushell wrote on 11/23/2016, 2:18 PM

Great work. To re-iterate several other posts, we really *need* native DNxHD / DNxHR support please!

Xerxeth wrote on 11/23/2016, 4:56 PM

When will build 201 be pushed to the Steam version of Vegas Pro 14? I tried updating manually, but that obviously didn't work out too well applying the retail update to the Steam version.

Edit: Nevermind, I actually just pulled it off. I was able to install build 201 over the Steam version by applying the update to: C:\Program Files (x86)\Steam\steamapps\common\Vegas Pro 14.0\Vegas Pro 14.0

I originally tried installing it to just C:\Program Files (x86)\Steam\steamapps\common\Vegas Pro 14.0

Hitfilm Pro 2017 Integration seems to work just fine now!

kim-s wrote on 11/24/2016, 1:13 AM

um....not import MOV(codec:animation)  .........

redpaw wrote on 11/28/2016, 7:10 AM

unfortunately no change with XAVC footage... the memory use still skyrockets when putting the clips on the timeline 😞

Pashi wrote on 11/28/2016, 10:25 AM

Just updated Vegas to this 201 build and got an issue with Sony A7SII XAVC-S codec - footage crashing in blocks like strong JPEG compression. Have to downgrade to 161.

ebetindo.com wrote on 11/29/2016, 1:08 AM

nice post bruh :D
can't wait for that

Radomir wrote on 11/29/2016, 5:23 AM

Okay, now, why drag&drop selected fragment from trimmer to timeline don't work as usual? Did you added switch for default behavior?

Nick Hope wrote on 11/29/2016, 6:19 AM

Okay, now, why drag&drop selected fragment from trimmer to timeline don't work as usual? Did you added switch for default behavior?

Drag vertically down drags it to timeline. Drag horizontally creates new selection. You need to be precise with vertical dragging.

Radomir wrote on 11/29/2016, 6:42 AM

Wooo, thank you :) But this is new behaviour right? 

gary-rebholz wrote on 11/29/2016, 7:24 AM

And until you get used to it, you might accidentally destroy your chosen in/out points by dragging too horizontally. If that happens, remember that the Backspace key scrolls you through your last five selections (just as it does on the timeline). So, if you've dragged too horizonatlly and create a new in/out selection, type Backspace to go back to what you had, and try again.

Paul-Fierlinger wrote on 11/29/2016, 8:22 AM

And keep on making safety backups... this is why I wish we had a way to make backups automatically compile themselves instead of having to type in a new name each time...

AVsupport wrote on 11/29/2016, 9:37 PM

Was editing a 3.5' clip for the last couple of days, XAVC-S 4K/25p and 1080/50p  on a 1080/25 timeline. A Crashathon. Couldn't hit that Save button quick enough. Didn't even bother with Crash Reporting Tool, which was crashed just as much. Add to that a dud Titler PRO (you need to be a PRO to fix that) that was so Express you couldn't hardly even change anything without crashing. That's on a Win10/64/1607. build 14393.82 Home machine, 12GB RAM, Core i7. I hope the future is heading towards us speedily, because living in the now sucks.  

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Nick Hope wrote on 11/29/2016, 10:45 PM

Wooo, thank you :) But this is new behaviour right? 

Yes, it's part of the new trimmer scrubbing in VP14. You can't do that in VP13. Personally I think the mouse angle and sensitivity should be adjusted a little so that it's easier to drag the selection instead of creating a new selection.

fhu wrote on 11/29/2016, 11:25 PM

Wooo, thank you :) But this is new behaviour right? 

Yes, it's part of the new trimmer scrubbing in VP14. You can't do that in VP13. Personally I think the mouse angle and sensitivity should be adjusted a little so that it's easier to drag the selection instead of creating a new selection.

Agreed 100%... It's too sensitve.

Former users wrote on 12/2/2016, 9:24 AM

Can I downgrade to build 189 just by installing the 14.0.0.189_update-Retail over build 201? There is the problem with HEVC with this newer build but older maybe works with 30p UHD.

Nick Hope wrote on 12/2/2016, 9:30 AM

Can I downgrade to build 189 just by installing the 14.0.0.189_update-Retail over build 201? There is the problem with HEVC with this newer build but older maybe works with 30p UHD.

I think you can but I am not 100% sure.

Cornico wrote on 12/2/2016, 9:37 AM

Can I downgrade to build 189 just by installing the 14.0.0.189_update-Retail over build 201?

No, you cannot.
Only a higher build
Now you have to deïnstall build 201 and than install a lower build.

 

 

Former users wrote on 12/2/2016, 9:43 AM

Can I downgrade to build 189 just by installing the 14.0.0.189_update-Retail over build 201?

No, you cannot.
Only a higher build
Now you have to deïnstall build 201 and than install a lower build.

 

Ok, I quess I'll try that. Thanks.

Former users wrote on 12/2/2016, 10:22 AM

Downgrading was succesful! And HEVC 30p UHD works again ;) 

Aiki wrote on 12/2/2016, 11:18 AM

Vegas Pro 14 does not work with Blackmagic DeckLink Studio 2. This card works well with V Pr 12 and 13

Vegas Pro 14 ne fonctionne pas avec Blackmagic DeckLink Studio 2. Cette carte fonctionne pourtant bien avec V Pr 12 et 13