Vegas 17 wouldn't open until I uninstalled Boris BCC 11 from my PC. Now Vegas 17 opens and works fine. Does this mean BCC 11 does not work with Vegas 17?
Yes. BCC 2019-5 (aka v12) is the only officially compatible version, according to Boris FX. There have been several other threads about this here already, have a search and you'll see them.
BCC 2019 5.1 does work with V17. The only problem I have found is that the Match Move Spline tracking ( which does track the object ) there is no facility to add an overlay Clip to ( replace a face wit another face )
I have had much communication with BORIS and they also either don't understand to Don't know.
BCC 2019 5.1 does work with V17. The only problem I have found is that the Match Move Spline tracking ( which does track the object ) there is no facility to add an overlay Clip to ( replace a face wit another face )
I have had much communication with BORIS and they also either don't understand to Don't know.
Are you applying match/move as a track composite and then putting your overlay on a track below it? I might add this is a situation where creating a nested project for the effect really facilitates the process.
Hi, Yes I am applying it as a Track Composite and also adding the overlay on the track below..I have tried lots of things ( parent and child, etc )… The BCC Basic Match Move in 2019 Continuum Tracking ( with the Square and the Absolute cross work perfect when I use the Composite to add Match Move with the insert on the track below. Sadly, Boris have not produced any Tutorials for That Version with Magix Vegas.
I have not yet found any tutorial with Magix Vegas and the Spline Tracking where you are doing the tracking and you Exit and save out of Mocha, the tracking is applied to the overlay..
Any clues would be most useful
BCC 2019 12.5.2 became available today - the main tweaks relate to Particle Illusion and Title Studio.
FYI.
Boris Help advisers indicate that not ALL features on BCC 2019 12.?.? will work with MAGIX VEGAS. The only issue is they wont or can't say what ones are affected.. So not worth moving on from the trial version if only some of the features work..
The conversation seems to be that MAGIX VEGAS is such a Small minor Brand that it is not worth investigating any issues or fixing any issue so that you can get all of what you have signed up for..
The MAGIX VEGAS info sheet on their WEB is still not available.. says " In Progress " and just refers to older versions which is of course no use with V17 and it totally different from the 2019 version.
The VEGAS Pro 17 Update 1 (build 321) release notes state:
"No longer crash upon attempting to load older, unsupported Boris Continuum plug-ins"
So at least the crashing issue should now be fixed.
I have noticed that the Boris Continuum BCC 11 Film Style Unit (that came with VEGAS Movie Studio 15 Suite) no longer shows up in the Video FX in VP17 build 321. I just see empty folders, whereas in VP16 it works with a watermark. So I guess the crashing has been solved by just disabling BCC 11 plugins completely.
Here (thread now locked), pioneer109 reported that the BCC Key and Blend group plugins have been lost in this update. @pioneer109, which version of the plugins were those, and how did you purchase them?
Hi Nick. Version 11.03.2463-2018-5-24(85ad6469) is what the version number tells me in Pro16. I purchased these as part of the Pro16 suite last year. Cheers John
Hi Nick. Version 11.03.2463-2018-5-24(85ad6469) is what the version number tells me in Pro16. I purchased these as part of the Pro16 suite last year. Cheers John
@pioneer109 Thanks. So it seems to be expected behaviour that those BCC 11 plugins no longer show up in VP17.
Before this update, did you install the first release of VP17 and have it running while those BCC 11 plugins were installed? That's what I inferred from your previous comment, but it would be surprising if you did. And if so, did the plugins work?
Yes Nick, I had been using the BCC Chroma key in Pro17
Yes Nick, I had been using the BCC Chroma key in Pro17
That's definitely a backwards step then. Perhaps an inevitable side-effect of having to disable other BCC 11 plugins to stop VP17 from crashing.
Good afternoon Nick Hope, any suggestion where I should go from here? Its no big deal, just a bit inconvenient.
Good afternoon Nick Hope, any suggestion where I should go from here? Its no big deal, just a bit inconvenient.
@pioneer109 Firstly I would report it to the VEGAS team, telling them the exact plugins and versions, how you obtained them, and that they were working in the first release of VP17, as well as in VP16. I doubt BCC 11 plugins will ever get enabled again in VP17, but you never know.
Then you could either just continue to use it in VP16, as you are doing, or perhaps investigate upgrading it, either directly with Boris FX, or by upgrading to VP17 Pro Suite, which includes version v2019.5 of that unit. But you should be aware that there is no guarantee it will work in VP18, the same as any bundled plugins might not work in higher versions of Vegas. The VP17 Suite upgrade may still be running at $349. If you go that route, leave it in your basket for a while and keep checking your email. You might get a little "encouragement" ;)