MOTUnation.com

mikehalloran wrote:

Just a guess, but VST3's show up in a different folder in the Plug Ins folder, they seem to be incompatible with VST2.4

That's not just a guess as any of us who own Antares plugins can verify. Antares AUs are barely compatible with DP 8 (Antares cautions us to test everything first) and decent support is non-existant. The VST 3 versions are incompatible and there is no other VST set.

kelldammit wrote:VST2 & 3 are completely separate animals, at least on PC. You cannot use one in place of the other.
They're not interchangeable in either direction, as the architecture is apparently very different (auto-selection of mono vs stereo channels, explicitly defined sidechain support, and per-note expression in vst3 are a few of the differences that probably wouldn't translate).
AFIAK, you can still use vst2 plugs in cubase, but you have to install the vst2 version.

Shooshie wrote:I agree with every point, and could not have said it better, myself. These are my concerns, too. I can't believe that for the first time I'm actually envying Cubase users a little, and not because MOTU is inattentive to DP, but because Apple has become a wild card. With its attention to mind-blowing designer watches for upscale lifestyles and an Apple car, how many times do you think the words "Audio Units" have crossed Tim Cook's desk in the past 5 years? It's the most profitable damn company on earth, for goodness sake! Who knows what other products are in the pipeline? But one thing seems pretty certain right now: professional multi-media technologies are simply not on the Apple Radar, except for photo-ops with famous people like U2. All of our creative and professional interests — our livelihood — could go away at moment's notice, without so much as a press release.

Mister Zero wrote:I understand most aspects of the VEPro 5.4.1 migration and am reading (and re-reading) the page 49 stuff in the manual, but fail to understand something:

What happens to the Event Inputs from previous versions of VEPro that might be in a project? Is an Event Input option included in the MAS plug-in version?

The reason I ask is because I use the Event Inputs to help organize my work and find them very handy.

Thanks for any help with this.

Shooshie wrote:...but because Apple has become a wild card. With its attention to mind-blowing designer watches for upscale lifestyles and an Apple car, how many times do you think the words "Audio Units" have crossed Tim Cook's desk in the past 5 years? It's the most profitable damn company on earth, for goodness sake! Who knows what other products are in the pipeline? But one thing seems pretty certain right now: professional multi-media technologies are simply not on the Apple Radar, except for photo-ops with famous people like U2. All of our creative and professional interests — our livelihood — could go away at moment's notice, without so much as a press release.

nightwatch wrote:

Mister Zero wrote:I understand most aspects of the VEPro 5.4.1 migration and am reading (and re-reading) the page 49 stuff in the manual, but fail to understand something:

What happens to the Event Inputs from previous versions of VEPro that might be in a project? Is an Event Input option included in the MAS plug-in version?

The reason I ask is because I use the Event Inputs to help organize my work and find them very handy.

Thanks for any help with this.

Good question. I made a Youtube video for you. It's quick and simple but answers your question. Short answer is there is no Event Input for MAS. You need to re-assign your MIDI outputs. But take a look here: http://www.youtube.com/watch?v=-AmSCnZj ... e=youtu.be

Part 2 to my last video will be out in a couple of days.

nightwatch wrote:From Paul at VSL:

"We have decided to pull VE PRO from MyDownloads and roll back to the previous version until we have fixed the AU/MAS confusion (working on it with high pressure, and it is looking good).

If you´d like to roll back, please use the VE PRO Uninstaller, this way the MAS plug-in will be completely removed.
I will let you know as soon as the update is available!"

Some further explanation from Paul... "I thought I´d keep you in the loop, this is the current situation we´re facing: DP forces the use of MAS over AU even in an AU saved project, so it will not be able to load the data.

In other words: MAS automatically overrides AU, resulting in project data incompatibility. A project saved with VE PRO AU should be loaded with the MAS plugin version disabled.

The best way to migrate existing songs is to disable the MAS plugin in DP, load the project, preserve the instances, reload the project with MAS plugin enabled again, then reconnect the VE PRO instances.

Of course if the instances are already preserved (which we assume will be the case with most songs), reconnecting the individual VE PRO plugins will do the trick.

We´re in touch with MOTU and hope that we can find a better solution for migration. "

Source: http://www.vsl.co.at/community/posts/m2 ... post235668

I've had no problems, but it's good to see VSL and MOTU working so hard together. Maybe this is a rebirth for MAS. The timing is perfect. Developers are upset with the AU spec and lack of documentation, and then the VST3 issues. MAS is now cross-platform correct?

Maybe now is a good time to email your favorite developer and plead our case for MAS development. I plan on contacting Steven Slate personally. They've been through it with AAX. But now that that's done, why not MAS?

Keep it positive!

comp15 wrote:

nightwatch wrote:From Paul at VSL:

"We have decided to pull VE PRO from MyDownloads and roll back to the previous version until we have fixed the AU/MAS confusion (working on it with high pressure, and it is looking good).

If you´d like to roll back, please use the VE PRO Uninstaller, this way the MAS plug-in will be completely removed.
I will let you know as soon as the update is available!"

Some further explanation from Paul... "I thought I´d keep you in the loop, this is the current situation we´re facing: DP forces the use of MAS over AU even in an AU saved project, so it will not be able to load the data.

In other words: MAS automatically overrides AU, resulting in project data incompatibility. A project saved with VE PRO AU should be loaded with the MAS plugin version disabled.

The best way to migrate existing songs is to disable the MAS plugin in DP, load the project, preserve the instances, reload the project with MAS plugin enabled again, then reconnect the VE PRO instances.

Of course if the instances are already preserved (which we assume will be the case with most songs), reconnecting the individual VE PRO plugins will do the trick.

We´re in touch with MOTU and hope that we can find a better solution for migration. "

Source: http://www.vsl.co.at/community/posts/m2 ... post235668

I've had no problems, but it's good to see VSL and MOTU working so hard together. Maybe this is a rebirth for MAS. The timing is perfect. Developers are upset with the AU spec and lack of documentation, and then the VST3 issues. MAS is now cross-platform correct?

Maybe now is a good time to email your favorite developer and plead our case for MAS development. I plan on contacting Steven Slate personally. They've been through it with AAX. But now that that's done, why not MAS?

Keep it positive!

So does this mean it's back to 16 MIDI Ports per instance? I just downloaded VEPro last thursday, and it appears that the MAS plug-in is still included, because MAS was included on the list of formats during the installation process...