V16&17 upgrade: plugins?

wwjd wrote on 7/23/2019, 7:36 AM

current deal: upgrade to 16, get 17 FREE. Cool. 16 comes with a PILE of plugins.... so.... will all those plugins that come with 16 work in 17?

Plugins are not rocket science: make them within a standard and they can load into everything. They have to go out of their way to cripple them from working in the "next" version... .or Vegas coders are doing something VERY wrong.

* Plugins have worked this way for about 2 decades, this is not new tech

Comments

Dexcon wrote on 7/23/2019, 7:59 AM

will all those plugins that come with 16 work in 17?

Unlikely. This has been discussed many times over the years on this forum. Usually, the add-on 3rd party plug-ins that come with a particular version of VP are licensed only to that VP version - but it totally depends on the license arrangement with the 3rd party plug-in provider.

Many on the forum - including myself - have decided its best to go with the VP Edit choice (I think the 16/17 offer has the Edit choice) and buy the 3rd party OFX plug-ins that we want directly from the 3rd party company as they should work across all versions now and later assuming that the OFX protocol doesn't change.

Unfortunately, the only real way to know if the VP 16 plug-ins will work in 17 is to buy the 16/17 offer (presumably the suite offering) and try them on 17 when 17 is released. A bit of a gamble in my opinion, and will probably lead to a level of disappointment.

wwjd wrote on 7/23/2019, 9:42 AM

Yes, I'm aware of the past faults, wondered if going forward they (Vegas) are improving it by sticking to known global standards like everyone else does. thus eliminating the problem. :)

 

JN_ wrote on 7/23/2019, 9:53 AM

@wwjd I believe its mostly a licence limitation issue per VP version number, 16, 17. Not that they won’t work because of VP17 changes necessarily.

 

Desktop and Laptop basic specs ...

Both run Win 10, has latest updates ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

vkmast wrote on 7/23/2019, 10:16 AM

"Going forward" (which we cannot know of) including the full versions of the 3rd party plugins would most likely affect the pricing.

wwjd wrote on 7/23/2019, 1:36 PM

right, I kinda mean, just stick with a standard... I could purchase from 3rd party... that would be money away from MAGIX. alrighty then. doesn't seem like the brightest choice for a company that wants money.

wwjd wrote on 7/23/2019, 1:41 PM

so... just thinking this through logically.... buy 16 with 5 plugins, then buy 17 (or get free upgrade) - have to REBUY those 5 plugins from the manufacturer anyway because new versions may not come WITH 17... see what I am saying? why not just LET the ones that came with 16 WORK in 17 and future by using the standard? like if you bought them externally from 3rd party? I know how it is, it's stupid, and I guess I am done venting. One more nail in coffin of my favorite editing software. :( Unfortunately, other logical options abound these days.

wjauch wrote on 7/23/2019, 5:18 PM

From the Magix website it states "Buy VEGAS Pro 16 Suite today and get a free upgrade to Version 17." I would take this to mean that the upgrade would be to Vegas Pro 17 Suite. Therefore I'd expect to get whatever is bundled in 17Suite included which may be the same or similar to Suite 16. (I also vaguely think a few years what was bundled in the Suite version changed midway during a Vegas version). Am I wrong in this?

 

paul-marshall wrote on 7/24/2019, 5:24 AM

The upgrade silly season is upon us. I've just gone for the 16+17 upgrade (from 15) because I want Motion Tracking and for the first time I've gone for the Edit version. I'm fed up with getting used to using some much lauded included plugin (Mercalli for example) only to find it wont work in a later version. I wouldnt mind so much if that had been made clear from the outset. It's easy to say I could use the old version for the plugin but really that is not a satisfactory work flow. So its less money for Magix and less money for 3rd parties. I've got a bunch of effects that I like and that'll do me. If any of those dont work in 17 I shall be really p'd off.

wwjd wrote on 7/24/2019, 6:56 AM

wjauch, that's what I am asking for: clarity. if you buy BECAUSE you get 17 upgrade free, then it doesnt come with the same plugins, you are screwed.

paul, true. If they would simply allow them to work in the next version LIKE ALL STANDARD 3RD PARTY PLUGINS ALREADY DO AND HAVE DONE FOREVER, then there would be no issue. Vegas is NOT rewritten from the ground up with each new release. There is simply no reason to not allow plugs from 16 to 17. cept profit.

Dexcon wrote on 7/24/2019, 7:36 AM

@wwjd ... your desires are understandable and admirable, but unfortunately unrealistic.

You mention that all standard 3rd party plugins already work and have always worked in later NLE versions. True … but only if you have bought the full OFX version of that plug-in.

The add-on plug-ins in offers like VP Suite are not really 'standard' plug-ins - they are specially licensed plug-ins limited in operation to that specific version of VP, the aim evidently being two-fold: 1/ to entice customers to buy the more expensive VP package (which offers the plug-in at a much reduced price than the full retail version - and sometimes those plug-ins are named 'express' or 'LE' or the like); and/or 2/ to entice customers to purchase the full OFX version of the plug-in from the 3rd party company. After all, 3rd party plug-in companies are businesses wanting to get more sales, and offering low-cost teasers via NLEs is an avenue for future sales. I consider the limited licence plug-ins to be 'teasers'.

The only real exception to this was back in Sony VP 11/12/13 days when NewBlueFX did permit their add-on plug-ins to work in future Sony VP versions - there's a lot of forum history about that going back to VP 11/12/13 days.

Also, purchasing the full OFX version also means that the plug-in will likely work in other NLEs such as DaVinci Resolve free and HitFilm free or pro - or any other NLE that you might have that supports OFX.

vkmast wrote on 7/24/2019, 7:49 AM

+1 @Dexcon Get the Edit version (see comparison chart and 3rd party plugins) and buy the full OFX versions if you need them. If you want to be sure.

wwjd wrote on 7/24/2019, 10:14 AM

yup. I do understand all that. I've downloaded many, better, freeware plugins that worked across all versions, also VST audio and the like... it's a shame that moving to the competition seems a more logical move than to continue support this absurd behavior. :( Oh well.

j-v wrote on 7/24/2019, 10:31 AM

support

???? It is your own free will to use them and/or to buy them.
Nobody is asking or forcing you to support something.
And therefore it should be better for you (and us) to stop your nonsense here.

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 7900 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 16 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 15,16,17 and VMS PL 15,16 are installed
Both Nvidia GPU's have driver version 431.86 Studio Drivers
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

Wolfgang S. wrote on 7/25/2019, 1:44 AM

@wwjd ... your desires are understandable and admirable, but unfortunately unrealistic..

Right. Many people do not understand that the have paid a much lower price for the bundled plugins, and fight for the opinion that such a bundled plugin must be the same as a direct purchased plugin. No, it is not the same because otherwise you would have to pay much more.

There is no free lunch in live, but that seems to be hard to understand for some guys who have not been trained in economics maybe.

wwjd wrote on 7/25/2019, 6:59 AM

i dont really care about the COST. I want the plugins I have already purchased with 16 to SIMPLY WORK in the next version I get...... like most of the rest of the plugins on the planet.

Seems like my true point is lost here so I'll stop. If everyone keeps on "SUPPORTING" it, that's the way it will stay.

Wolfgang S. wrote on 7/25/2019, 8:29 AM

i dont really care about the COST. I want the plugins I have already purchased with 16 to SIMPLY WORK in the next version I get...... like most of the rest of the plugins on the planet.

Seems like my true point is lost here so I'll stop. If everyone keeps on "SUPPORTING" it, that's the way it will stay.


If you do no care about costs then purchase the plugins offered by the third Party companies. Sorry, but everything else will not help you.

Maybe there will be possibilities to purchase Upgrades for your plugins from some of the suppliers, that could be cheaper then to purchase a brandnew license. But you have to check that a the suppliers Webpags.

fr0sty wrote on 7/25/2019, 9:05 PM

Magix likely has to limit the plugins to that version in order to be able to bundle them at a discount. If you don't like that limitation of the discounted version, nothing stops you from just buying the full version.