@thenightwatch said:

In other words, everything just worked without me having to select the MAS version of the VEPro Ensemble Pro, or de-select the AU version in DP. All I had to do was re-connect the instances.
Are these MAS instances, or do I need to merge projects from an AU instance to a MAS instance and then aim my midi tracks to the new instance? Or has this already been taken care of by VEPro?
Thanks!

Right. I saw this post too. However I have a slightly different situation. I wanted to ask you though. Using PreGen mode works fine? Any issues, or is it a go?

Thanks!

@thenightwatch said:

I did this without loading the MAS version of the plugin in DP. Did VEPro somehow already open/convert the instances as MAS instances? In other words, everything just worked without me having to select the MAS version of the VEPro Ensemble Pro, or de-select the AU version in DP. All I had to do was re-connect the instances.

Hi willimmyers! Thanks for the reply. I like to see how things are going to work as I install them (a sort of preemptive troubleshooting mode kicks in). Actually, I did the opposite thing as I wanted to see what would happen if I updated everything. I also generally keep all my main plugins in as many formats as I can, ready for other software.

It still did the same thing that happened to both of us. The only thing I can think of is that DP reverts to a MAS version if a MAS and an AU plugin is installed. So even though my previous version was using AU, when I opened the template this morning, DP and VEPRO just replaced the AU version for the MAS version. Also keep in mind after installation, the VEPro instrument instances were disconnected from their VE instances. When I connected one, it was working with 32 ports and 16 midi channels (the image above was taken as that happened). Whichever the case, AU can not use midi ports and my system is working as discussed so I must be using the MAS version. Only way to find out is to disable the AU plugin in the prefs and see if the instance still works. That will confirm it. I might be able to dig into the xml file somewhere and check that way, but it seems obvious all is well.

Anyway, enjoy or new gift!

Hi there,

I'm on the second day of a 30 days demo, trying to see if it's really worth substituting my Bidule orchestral setup with VEP5. Despite my silver hair, being the second day with VEP I'm a complete newbie.

At the moment I'm using DP8.07 with server 64 and 32 bit in the same computer, and apart the loooong time to reassign all the input midi tracks of a large templete, everything "seems" to work as expected, which is a good news. But everything isn't completely jolly, there are some quirks.

For example on lauching both VEP server 32 and 64 bit, I had several crashes while validating AU plugin. I'm attaching those logs here.

Another problem I had it happened with MachFive.: while trying to load a MachFive MULTI, MachFive GUI propt to look for a PLACE or DEVICE where the multi should be located. In that moment I had to scroll the MachFive GUI but VEP froze and I had to force quit. This happened to me three times in a row. Workaround I've found is to pop out MachFive from the VEP and everything worked again.

Only one question … VEP seems to totally ignore VST plugin and instrument. I've searched in the pref but there's nothing about it. Am I missing something?

Thank you

ciao

MacPro3.3 - 12Cores/24gig RAM/MacOSX.8.5/512SSD + 256 SSD + 2TB
DP8.07/MOTU 2408mk3/1296/24I-O/MTPAV/UAD2

Working ok for me so far, with one major exception:   tempo changes are causing drop outs and clicks.  I have a dense orchestral cue that plays back perfectly, right up until a ritard near the end.  It goes from 74bpm to 50 bpm in a slow ritard.  As soon as it hits this point in the conductor track, I get all sorts of pops, crackles, dropped notes.  I verified that it plays back fine using the AU plugin.  It seems to have only started on the MAS version (which is awesome btw!).

Anyone else encounter this?

Hey Tripi,

This has actually been a problem for me with the AU plug. too. I get quick stutters and dropouts with tempo changes. BUT, when I print to audio, everything sounds fine. It's just playback that suffers. Definitely annoying, but  not as bad as it would be if things recorded that way!

I haven't switched over to the MAS update yet. Waiting for things to slow down a bit before I take the plunge. Other than the tempo issues, have you noticed any significant performance enhancements? I'm hoping that my stuck and missed note issues go away.

@Tripi said:

Working ok for me so far, with one major exception:   tempo changes are causing drop outs and clicks.  I have a dense orchestral cue that plays back perfectly, right up until a ritard near the end.  It goes from 74bpm to 50 bpm in a slow ritard.  As soon as it hits this point in the conductor track, I get all sorts of pops, crackles, dropped notes.  I verified that it plays back fine using the AU plugin.  It seems to have only started on the MAS version (which is awesome btw!).

Anyone else encounter this?

Hi, 

Installed the MAS version and changed the plug in preferences as discussed. However, when I open my template or any previous sequences only the shell is loaded, none of the instruments. I can then load my saved metaframe - fine for the template, but for previous sequences, any changes that I made to the metaframe were only saved with the sequence so are to all intense and purpose, lost, unless I revert back to the non-MAS plug in.

Is anyone else having the same problem or could put me right? 

Cheers

Thank you Paul! THank you VSL team ! I so appreciate you providing this MAS version.

Hi everybody, 

Thanks for your feedback, it is much appreciated!

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. 

Best,
Paul

Hello again, 

Another update: 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!

If you´d like to accelerate beta-testing, please let me know at support@vsl.co.at, I´ll provide you with the next release candidate as soon as it is ready.

Thanks for your understanding and patience, 

Paul

@Paul said:

Hello again, 

Another update: 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!

If you´d like to accelerate beta-testing, please let me know at support@vsl.co.at, I´ll provide you with the next release candidate as soon as it is ready.

Thanks for your understanding and patience, 

Paul

Paul - We DP users support your decision to pull it to get things right! Although I've had no problems, we look forward to the next releaase. In the meantime, I'll sign up for the beta test.

Thanks!

I have been having an issue with my instances connecting/disconnecting, as I open projects, causing long connect times. I am guessing it has someyhing to do with the issue mentioned it this thread.

I am going to deal with the current beta and the connect issues until there is a new release as I already reset my template to work with this outstanding, amazing, game changing, version of Mas enabled VEP!

@Paul said:

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

Hi, 

That´s the only reason. We have now added a message to the upcoming build that informs all DP users how to migrate from VST/AU to MAS with existing projects, and I´m writing an additional chapter for the VE PRO manual, with screenshots, so that the scary moment of opening a DP project with empty VE PRO instances is not such a shock. 

You should definitely stay with the existing update if it works for you, and the next update will improve some behaviour as well (I´ll add that information to the changelog when the version is released, probably tomorrow). 

Thanks for your patience and understanding, everybody!

Best,
Paul

Excellent news. I have been seeing long connect times when I'm connecting to my brand new VisionDaw slave(windows7 pro) as compaired to an instance on my desktop. Is this expected behaivor?

@reddognoyz said:

Excellent news. I have been seeing long connect times when I'm connecting to my brand new VisionDaw slave(windows7 pro) as compaired to an instance on my desktop. Is this expected behaivor?

My desktop being osx 10.10.2

Hi, 

Please define "long connect times"... how much longer does it take than with the previous version?
Did you change any preference settings (e.g., Ports and Audio Channels in the VE PRO Preferences?

You can always contact me at support@vsl.co.at with more details, screenshots, DP songs in specific cases (this should be the "announcement thread").

Thanks, 
Paul

Hello everybody,

We have decided to add an info-screen when you first open VE PRO with the new MAS version in Digital Performer, which points you to the updated Vienna Ensemble PRO 5 manual with detailed instructions on a successful migration from AU/VST to MAS.

This version is now online in MyDownloads, with a few further improvements (check the VE PRO Changelog).

All the best from a busy Vienna,
Paul

Hi, 

Wow, you read the manual!
We think it´s nice to have more than just 16 instruments in one VE PRO instance, for better overview, less screen clutter, and of course to use with MIR PRO (all instruments in one room).
In any case, that´s now possible. I always use the channel collapse function to get more channels on the screen. 

Best, 
Paul

Hi Paul,

I'm looking for clarification on this as the manual isn't that clear to me.  With the MAS version, can we now use Pre-gen mode or do we still have to set DP to run plug-ins in real-time?  The only place Pre-gen is mentioned is under "Working with Audio Input/Event Input plug-ins."

Thanks,

Chris