Just curious if it's something with the VP17 engine (or whatever) or something activated by the plugin creators that causes Ignite (free) and Boris Continuum 8 to not work in 17 when they do in 16?
Are you talking about the included plug-ins that are sold with Vegas Pro ?
Or are you talking about 3rd party plug-ins that you bought separately from Vegas Pro ?
The included plug-ins are specific to the version of Vegas Pro that you bought and will NOT work with any other version of Vegas Pro. 3rd party plug-ins that are bought separately from Vegas Pro should work, but you might have to reinstall them to get them to recognize a newer version of Vegas Pro.
No, I'm talking about the purchased one (BC8 suite). The Ignite plugins I'm talking about were the "free" ones they were giving out previously. Ignite doesn't seem to still offer those, but they still appear in VP16.
Re Ignite Express … this was discussed on this forum a few times back in August/September last after VP17's release. Ignite Express does not work in VP17 as does not Ignite Pro unless the latest version - 4.1 - of the latter is installed. The following reply re Ignite Express and VP17 is from FXHome's forum, and it makes the situation very clear:
https://fxhome.com/forum/discussion/50824/ignite-express-2017-support-for-vegas-pro-17#latest
BCC12 and 13 have worked without a problem for me in VP17. Given that BCC8 is now very much a legacy release, it is entirely possible that coding within VP has changed with the result that some legacy plugins no longer work within the latest VP release. Changes to coding in VP17 is apparently the reason that Ignite Express (and for a time Ignite Pro) does not work in VP17.
Thanks for the info, Dex.
Before you buy VEGAS Pro 17, you should ask support team that does old plugins work in vegas pro 17.
Or you will suffer a loss if you own old plugins.
Actually, the develop team disables old or free plugins, wishing you pay for new plugins.
VEGAS Pro team replaces sign"com.sonycreativesoftware.vegas" to "com.vegascreativesoftware.vegas", so many old plugins can't work in VEGAS Pro 17.0 .
The third (fr0sty) post in this thread may help explain https://www.vegascreativesoftware.info/us/forum/hello-my-neat-lil-pardners--117699/#ca734165
OR they should switch to a standard that everyone uses... except that is less profitable
OR they should switch to a standard that everyone uses... except that is less profitable
@wwjd You should really do some research before posting something like that (which you have repeated a few times).
OFX is a standard that is widely used by many manufacturers. The issue here was strictly legal. We, for 3 years, had delayed making this change because we knew of the headaches it would cause. We finally had no choice but to make the host name change. We gave OFX manufacturers, who we knew had host locked some of their plugins, almost a year warning that this was going to happen. We also made no secret that this could potentially be a problem.
So the reason that this was a problem was BECAUSE we are adhering to a standard that everyone uses.
You believe making this change, that was obviously going to upset people, is somehow more profitable to us? The only thing that was benefiting us financially in this situation was the avoidance of legal problems that would be involved.
Ahhh, the lessons MIDI did not teach us...
Jessariah67, I've been burned by this many versions ago. IMHO these Vegas plugins offered by 3rd party vendors is basically baitware. In all cases they don't work with later releases of Vegas and if you depend on them for your production you'll end up having to pay for the software.
I have purchased 3rd party plugins that I consider worth using on my projects and most of them still work with updated versions of Vegas.
NewBlue and Universe keep up - and there's quite a bit of overlap between Universe and Continuum. I WILL miss a couple of the Ignite plugins from time to time, but my use of plugins is not excessive beyond basic touching (color, curves & unsharp m0ask), so it doesn't make sense to keep them all when you basically have to subscribe now and carry annual renewels. If I were doing a lot of edgy, music-video-ish work, then that would be one thing. But most of the work I do lately is corporate, and mostly involves RF video and motion graphics.
It's just a head-scratcher for a layman like me to have to hold on to different versions of o program "just in case" I need to use that one plugin or transition that is no longer compatible - especially when previous versions keep popping up the file association alert, as well as the Upgrade Now window every time you open it up, cuz the "Don't Show This Again" box doesn't work.