[Release] VEGAS POST: One workflow. One suite.

VEGAS_CommunityManager wrote on 8/12/2019, 8:17 AM

Dear community,

For the first time, we integrate video editing, VFX, compositing tools and image processing into a powerful video post production suite: VEGAS POST.

VEGAS POST offers industry-renowned editing tools coupled with FXhome’s expertise in compositing and visual effects. This jointly-developed software solution includes the brand new VEGAS Pro 17 for fast, professional video editing, VEGAS Effects for high-end compositing and effects, and VEGAS Image for creative image processing. With a perpetual license and flexible subscription plans available, VEGAS POST provides an attractive new alternative to conventional solutions in the market.

VEGAS POST: What’s Included

VEGAS Pro 17

Last week we released our fastest NLE: VEGAS Pro 17. Here you can find the official release thread.

VEGAS Effects

For highly efficient post production, the new VEGAS POST integrates creative effects tools directly into the video editing workflow, including:

Over 800 effects and filters
Particle generators for super-realistic effects
3D model rendering
Green Screen removal
Muzzle Flash generator
Video scopes for accurate color analysis

VEGAS Image

VEGAS Image is a powerful photo-editing tool that keeps image data RAW and all layers self-contained. Flexible layers can be accessed and adjusted in real time and as many times as needed, without disturbing anything else in the image. Key features include:

Built-in keying tools like Chroma Key
Professional compositing tools
Easy color adjustment
Dozens of powerful image filters and effects
LUT support
Flexible layer access and adjustment

Learn more at https://www.vegascreativesoftware.com/us/vegas-post/

Disclaimer: Once you downloaded and installed all the components of VEGAS POST, you need to activate each of the software applications. Have a look at our tutorial how to activate VEGAS Pro 17, VEGAS Effects and VEGAS Image:

Best Regards,
The VEGAS Pro team

Back to post

Comments

zdogg wrote on 9/10/2019, 9:35 PM

Choose "Deactivate Vegas pro 17" (from help menu) - restart, and in activation window make sure that you don't just click "OK" (you probably have the Vegas pro 17 serial code), delete that code and insert the Vegas Post code. Then the other programs will be activated as well.

AVsupport wrote on 9/13/2019, 1:19 AM

for the record: I have always been a fan of 'Vegas native' modules that won't suffer the death of software proliferation in an upversioning cycle. Better if Magix aquires bulk licenses and manages those for it's users so we don't have to deal with the petty shipfight each year. Tight integration with transcoding 'file managers' aka production assistant, and tools like HOS alike would make a lot of sense. Tease with a free trial period, and offer a meaningful upgrade path to existing users. Suck in new users with a beesticky free 'lite' / beta as the opposition does. So, rather than one suite, a flexible, 'add-on' options based model would suit me better.

TOG62 wrote on 9/13/2019, 10:23 AM

bitman wrote on 9/28/2019, 6:37 AM

@bitman, run VEGAS in administrator mode and the registration should succeed. This is a known issue that we're working on a fix for.

@gary-rebholz Thanks for the suggestion, I was out on vacation the last 3 weeks and filming a lot to edit in Vegas and could not try it out! In the mean time I see you have an update 321, I installed it, but ...

The Vegas Post “demo” issue seems solved (not sure it was fixed by 321, or if it was fixed once and for all by starting as administrator as you suggested…)
However, the "demo" issue was also further complicated (and masked by an OFX interop issue): vegas post app crash on launch and is still NOT fixed by 321.

In order to have Vegas post start up (in my case at least) without a Vegas Post crash I had to:

Rename C:\Program Files\BorisFX\ContinuumOFX\12\lib\Continuum_OFX_8Bit.dll to something else
Rename C:\Program Files\Common Files\OFX\Plugins\NewBlueFX\TitlerPro2.ofx.bundle\Contents\Win64\TitlerPro2.ofx to something else
Vegas POST will startup after the renaming actions, but when using certain Boris FX in Vegas POST, it will crash in C:\Program Files\BorisFX\ContinuumOFX\12\lib\Continuum_OFX_Float.dll or will not work because of renaming Continuum_OFX_8Bit.dll

Obviously there is something seriously wrong with the compatibility of Vegas Post and some OFX plugins like newblue and Boris.

PS. I have the latest Boris Continuum installed (Continuum_2019_5_OFX_Hosts_12_5_2_Windows.exe), and submitted a ticket [Ticket#2019090517008357] to Magix.

Nick Hope wrote on 10/2/2019, 4:46 AM

I discovered that VEGAS Effects won't run with NewBlueFX Titler Pro Express that came bundled with VEGAS Pro 14. I was able to get VEGAS Effects to run by moving C:\Program Files\Common Files\OFX\PluginsMOVED\NewBlueFX\TitlerPro2.ofx.bundle to another location. I have numerous other plugins installed in that folder, including NewBlue ones. VEGAS Effects would run in demo mode with that plugin, before I activated it, which seems strange.

bitman wrote on 10/4/2019, 10:08 AM

Vegas Post (build 321 and prior build) is currently incompatible with Boris continuum OFX.

When trying to launch Vegas effects, it fails to launch if you have Boris Continuum installed, (even the latest version). Just launching and using Vegas 17 without Vegas effects works with Boris.

I raised a ticket with both the Vegas Team and the Boris team, and they confirmed it is an issue, and I am not alone. The OFX Vegas Post issue probably extends also to newblueFX.

So in short, Vegas 17 Post is a no-no with third party OFX until a fix is found in either the third party OFX or in Vegas Post (or in both), the teams are working on the issue.

As a temporary work-around you can temporary rename (until it is fixed),

the boris OFX plugins (and newblue) from

C:\Program Files\BorisFX\ContinuumOFX\12\lib\Continuum_OFX_8Bit.dll

C:\Program Files\BorisFX\ContinuumOFX\12\lib\Continuum_OFX_Float.dll

C:\Program Files\Common Files\OFX\Plugins\NewBlueFX\TitlerPro2.ofx.bundle\Contents\Win64\TitlerPro2.ofx

Note that you cannot use the Boris effects that depend on these if removed or re-named...

VidGuy069 wrote on 10/5/2019, 12:13 PM

Help guys & gals. I was using Boris FX Continumm before getting VEGAS POST. Found out they don't work well together. Sad but okay. I uninstalled, deactivated, and even removed Boris from registry. Yet, the BCC list continues to appear when I go to add ANY effect. I even deleted the program files (both regular and x86 entries) The BCC effects don't function, but them being listed is annoying beyond words. Anyway to get them off the list?😕

kmaultsby wrote on 10/5/2019, 3:56 PM

Hey Guys I am little confuse here. If you go into Vegas Effects and click on the Help online Help it takes you to X Support page and if you look over to the upper right and click on either Account or Store it takes you to X FXhome which has HitFilm Studio HitFilm Pro13 etc. First off is these included in Vegas Effects? Second if not if you purchase these FX will they work with Vegas Post?

bitman wrote on 10/7/2019, 12:59 AM

@kmaultsby Vegas Effects is a Hitfilm product adapted to smoothly integrate with Vegas. Hitfilm collaborated with Vegas on this.

bitman wrote on 10/29/2019, 3:04 AM

Update on Vegas Post (build 321 and prior build) incompatibility with with Boris continuum OFX version 2019 (build 12.x): the new Boris version just released (commercially named 2020, build 13.0) is still incompatible with Vegas Post.

Note that just using Boris 2019 (12.x) or the new Boris 2020 (13.0) in Vegas (without launching POST) still works OK.

SDI wrote on 11/17/2019, 1:40 AM

I also would like to know the answer to kmaultsby's question. I have noticed vegas affects is almost the same as hitfilm pro. as I was going through the features I was disappointed to find that it was missing mocha. a 45 dollar addon if you have hitfilm express. I think this should have been included but ok. are we out of luck and cannot add this on if we want it? including this in an update would be great.