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

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.

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.

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

+1

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 ...

  1. 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…)
  2. 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:

  1. Rename C:\Program Files\BorisFX\ContinuumOFX\12\lib\Continuum_OFX_8Bit.dll to something else
  2. Rename C:\Program Files\Common Files\OFX\Plugins\NewBlueFX\TitlerPro2.ofx.bundle\Contents\Win64\TitlerPro2.ofx to something else
  3. 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.

Last changed by bitman on 9/28/2019, 6:38 AM, changed a total of 1 times.

Current system: VP 17 (build 421), VP16 (suite) build 424, (uninstalled VP 13,14,15), Vegasaur, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2020, Davinci Resolve Studio 16,...

  • OS: Windows 10 Pro 64, version 1909
  • CPU: i9900K stepping R0 (since October 2019), previously, der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive (games & APPS): Samsung NVMe SSD 2TB 960 pro

  • Current Video source work drive: Samsung NVMe SSD 2T 970 EVO plus

  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB

  • MOBO: Gigabyte Z370 Aorus Gaming 7, BIOS F14
  • PS: Corsair HX1200i, Case: Silverstone fortress 2,
  • Misc: Logitech G910, Evoluent Vertical Mouse, shuttlePROv2

 

NickHope 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...

Current system: VP 17 (build 421), VP16 (suite) build 424, (uninstalled VP 13,14,15), Vegasaur, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2020, Davinci Resolve Studio 16,...

  • OS: Windows 10 Pro 64, version 1909
  • CPU: i9900K stepping R0 (since October 2019), previously, der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive (games & APPS): Samsung NVMe SSD 2TB 960 pro

  • Current Video source work drive: Samsung NVMe SSD 2T 970 EVO plus

  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB

  • MOBO: Gigabyte Z370 Aorus Gaming 7, BIOS F14
  • PS: Corsair HX1200i, Case: Silverstone fortress 2,
  • Misc: Logitech G910, Evoluent Vertical Mouse, shuttlePROv2

 

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.

Current system: VP 17 (build 421), VP16 (suite) build 424, (uninstalled VP 13,14,15), Vegasaur, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2020, Davinci Resolve Studio 16,...

  • OS: Windows 10 Pro 64, version 1909
  • CPU: i9900K stepping R0 (since October 2019), previously, der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive (games & APPS): Samsung NVMe SSD 2TB 960 pro

  • Current Video source work drive: Samsung NVMe SSD 2T 970 EVO plus

  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB

  • MOBO: Gigabyte Z370 Aorus Gaming 7, BIOS F14
  • PS: Corsair HX1200i, Case: Silverstone fortress 2,
  • Misc: Logitech G910, Evoluent Vertical Mouse, shuttlePROv2

 

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.

 

Last changed by bitman on 10/30/2019, 2:42 AM, changed a total of 1 times.

Current system: VP 17 (build 421), VP16 (suite) build 424, (uninstalled VP 13,14,15), Vegasaur, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2020, Davinci Resolve Studio 16,...

  • OS: Windows 10 Pro 64, version 1909
  • CPU: i9900K stepping R0 (since October 2019), previously, der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive (games & APPS): Samsung NVMe SSD 2TB 960 pro

  • Current Video source work drive: Samsung NVMe SSD 2T 970 EVO plus

  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB

  • MOBO: Gigabyte Z370 Aorus Gaming 7, BIOS F14
  • PS: Corsair HX1200i, Case: Silverstone fortress 2,
  • Misc: Logitech G910, Evoluent Vertical Mouse, shuttlePROv2

 

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.

VidGuy069 wrote on 11/29/2019, 10:29 PM

I aggree with SDI, should have added. It's (mocha) is mentioned in the manual for VEGAS Effects. Can't find it anywhere. Next build? HINT HINT Or if Mocha is in effects, how do I access it?

Thank you.

vjsouza wrote on 12/19/2019, 1:17 PM

IMPOSSIBLE TO BUY LICENSE IN BRAZIL

Since Magix sell to Brazil, the following text is in Brazilian Portuguese.

Eu duvido de que alguém da Magix vá ler este texto. E se ler, duvido que vão entrar em contato comigo. O suporte ao cliente da Magix só atende por telefone, e em alemão e inglês somente. Não tem como enviar e-mail para a Magix!

Eu faço compras com cartão VISA Internacional sem nenhum problema. Estou tentando comprar a licença anual do Vegas Post, mas a Magix não disponibiliza outro meio de pagamento senão Visa ou Mastercard Internacional. No site da Magix ela diz aceitar PayPal, mas isso é mentira! Minhas tentativas de compras são bloqueadas sem nenhum aviso. Será que meu nome está numa espécie de "lista negra" na Magix?

 

gary-rebholz wrote on 12/20/2019, 11:34 AM

@vjsouza, you've been trying to contact the wrong support. You need to contact VEGAS Creative Software support. I'm not sure if they can help you, but at least it is the right support portal. All of their support is by email. Please contact them to open a support ticket: https://support2.magix.com/customer/en/vegas/form. Sorry; they don't speak Portuguese, but Google Translate does. (I've pasted a Google Translation below this message.)

você está tentando entrar em contato com o suporte errado. Você precisa entrar em contato com o suporte do VEGAS Creative Software. Não tenho certeza se eles podem ajudá-lo, mas pelo menos é o portal de suporte certo. Todo o apoio deles é por email. Entre em contato com eles para abrir um tíquete de suporte: https://support2.magix.com/customer/en/vegas/form.
 

alifftudm95 wrote on 12/23/2019, 10:33 AM

Will VEGAS Effects have dynamic link between VEGAS Pro? Its hard to edit without seeing the adjustment you've done inside VEGAS Pro inside VEGAS Effects

VidGuy069 wrote on 1/9/2020, 12:11 PM

Yes alextudm95 it does have dynamic link between VEGAS Pro. You need to 'Export' the clip after your VEGAS Effects work is complete. It SFOULD drop a copy of the updated on your timeline where the old cip was.

Marco. wrote on 1/9/2020, 3:29 PM

You don't need to export the clip from VEGAS Effect. You only need to save the Effect project, this then automatically updates the Take in the VEGAS Pro timeline.

VidGuy069 wrote on 1/9/2020, 5:39 PM

I sit corrected. It also adds a copy of the 'Effected' clip to the media bin.

Marco. wrote on 1/9/2020, 5:42 PM

It looks like and actually it is to be used like an "effected" clip, though what's added into the media bin (and as a Timeline Take) is the Effect project file which can be natively read by Vegas Pro.

Dave-arena wrote on 1/26/2020, 7:43 PM

I got, and installed today, Vegas Post. Out of the 4 components, all work but Vegas Effects. It crashes every single attempt to launch, either from within Post or as stand alone. Quite annoying.

 

SDI wrote on 2/6/2020, 5:56 PM

@Dave-arena, you have 4 components? Vegas effects crashes on my system also. it seems if you have any new blue plugins (that came bundled with previous versions of Vegas Pro) Vegas effects wont run. delete these and it works. 😞

bitman wrote on 2/26/2020, 6:27 AM

Update on Vegas Post (build 387 and prior builds):

when Boris continuum OFX is installed it is still incompatible with Vegas Post (Vegas effects).

I will not be able to test the new Vegas build (421), I need to buy a new licence for Vegas 17 (without post) as Magix has recently cancelled and gracefully refunded me Vegas Post on my request as the 3 companies involved (Vegas, Boris, Hitfilm) cannot seem to solve the Boris continuum OFX installed incompatibility with Vegas Effects in a reasonable time frame (more than half a year has passed without a fix after I reported the issue).

P.s. Just bought a new license for Vegas edit 17, I hope the companies work together and fix the Boris OFX and Vegas Post (Vegas effects) some day in the future.

Last changed by bitman on 2/27/2020, 2:27 AM, changed a total of 2 times.

Current system: VP 17 (build 421), VP16 (suite) build 424, (uninstalled VP 13,14,15), Vegasaur, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2020, Davinci Resolve Studio 16,...

  • OS: Windows 10 Pro 64, version 1909
  • CPU: i9900K stepping R0 (since October 2019), previously, der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive (games & APPS): Samsung NVMe SSD 2TB 960 pro

  • Current Video source work drive: Samsung NVMe SSD 2T 970 EVO plus

  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB

  • MOBO: Gigabyte Z370 Aorus Gaming 7, BIOS F14
  • PS: Corsair HX1200i, Case: Silverstone fortress 2,
  • Misc: Logitech G910, Evoluent Vertical Mouse, shuttlePROv2

 

lan-mLMC wrote on 2/29/2020, 2:57 AM

Update on Vegas Post (build 387 and prior builds):

when Boris continuum OFX is installed it is still incompatible with Vegas Post (Vegas effects).

I will not be able to test the new Vegas build (421), I need to buy a new licence for Vegas 17 (without post) as Magix has recently cancelled and gracefully refunded me Vegas Post on my request as the 3 companies involved (Vegas, Boris, Hitfilm) cannot seem to solve the Boris continuum OFX installed incompatibility with Vegas Effects in a reasonable time frame (more than half a year has passed without a fix after I reported the issue).

P.s. Just bought a new license for Vegas edit 17, I hope the companies work together and fix the Boris OFX and Vegas Post (Vegas effects) some day in the future.

You can move "NewBlueFX","BCC_OFX_3DObjects.ofx.bundle","BCC13_OFX.ofx.bundle"

from "C:\Program Files\Common Files\OFX\Plugins"

to "C:\Program Files\VEGAS\VEGAS Pro 17.0\OFX Video Plug-Ins"

lan-mLMC wrote on 2/29/2020, 3:01 AM

@gary-rebholz  Hello, when will next build of VEGAS Effects be released?

And what's the difference between the two Direct Download Links:

VEGAS Pro 17 (DE/EN/FR/ES):  https://rdir.magix.net/?page=8FY0YLZSTWIE

VEGAS POST (DE/EN/FR/ES): https://rdir.magix.net/?page=LZWVHQOQ2233

Which is in this post.