Latest Versions of both, MacOS Ventura and Logic Pro.

All worked fine, but now I cannot seem to load my server projects.

I get an alert saying "The Project you are trying to load is invalid."

 And when I try to dig in an individual one, it won't let me, it says its invalid and I see an e-Licenser error message about Synopsis.

UPDATE:

I uninstalled the e-Licenser software and that fixed it.

I log-in and when I click on that box to type it in, nothing happens.

I really want to transition from the e-Liscenser already.

I am not looking to be critical, but both e-licenser and iLok have been around a very long time, so I  am surprised that transitioning from using one copy protection scheme to the other is such a big deal. But admittedly, I have no real knowledge as to what is involved.

Originally Posted by: Paul

Hi,

We will make the transition as soon as possible, and we will announce it on all our channels, and of course we will inform all our users via newsletter as well.

Best,
Paul

This transition is taking longer than the Franco-Prussian War.

Deadman, for me, too many steps for too little reward, but as you say, because I am a classically trained guy, the score page approach is just more relatable for me.

Interesting, Dewdman , I didn’t remember that!

I think you are correct though in your guess that their are so few developers who have bothered to create AU 3 versions that Logic’s utility with them, or shortcomings  hasn’t gotten any attention. As we’ve discussed, it isn’t something I care a lot about, although it would be nice to use if I it worked reasonably effortlessly, but when I see the lengths you go to to make it work, I am not willing to go there.

Macker , what a nice fellow you are, thanks. 

Logic is my DAW, period. I have thousands of hours working with it and I can make it serve any musical composition or production task I do quickly and well. VE Pro has been a good partner for it  the only way I would even think about using another is if a client said to me, “Jay, I have $50,000 worth of work for you but you need to use (fill in any DAW) to do it.”

I didn’t say Apple. calls it a beta, VSL does. The plug-in is named AU Beta when you access it in Logic Pro, as you acknowledged.

My memory could be letting me down but I don’t remember Apple ever saying that AU 3 was fully implemented and  supported. 

As for DP, funny, but in recent years a number of people hired me to help them migrate to Logic because they were unhappy with DP, but I don’t do DAW wars. They all have their pros and cons. But most users who have used multiple ones concede that while they may prefer Cubase or DP, Logic is more efficient in running software instruments and fx  but of course VE Pro helps all of them with that. And Cubase, on the Mac at least, is less stable than Logic, according to the Cubase Mac people I talk to. They use Cubase in spite of that, not because of that.

Again, though, I don’t care which DAW people prefer. 

Originally Posted by: Macker

Au contraire, Ashermusic. As VSL informed us, VEPro7 (AU3 Beta) was the world's first plugin in which Apple's new AU3 support for multiple MIDI-Out ports was implemented; even though it's still Beta and now in a badly broken state, unlike in LPX 10.4.8.

If you have reliable information about the status of AU3 in Apple, please do share it with us, citing your source(s).

My class action remark was just a quip - as signified by a customary quip-signifier:- "Lolol".

I've no idea why you mentioned DP. It's nothing to do with me and I've nothing to do with it; nor have I ever had even the slightest intention of becoming involved with it.

Beta is beta is beta. I have been doing this since 1990 and I am always surprised when anything beta works:)

I have no insider info from Apple about this and frankly couldn't care less about it. My view has always been that if I could not accomplish what I needed too with 16 MIDI channels, I would not see myself as very skillful.

Sorry, it was someone else who mentioned moving to DP. 

Originally Posted by: pianoomann88

This is great news! Can't wait for this. Just got the new MacBook Pro so one less dongle is a good thing :)

Agreed, I will not sorry to say goodbye to my Steinberg keys.

1. Logic has never supported multiple MIDI ports.

2. Apple doesn't fully or officially support AU 3.

3. VE Pro AU 3 is beta software.

So no, I will not be joining a class action against Apple.

Good luck with Digital Performer, Macker. I predict you will find that you are out of the frying pan and into the fire, but maybe not.

Originally Posted by: Paul

Hi everybody, 

So we have to confirm that the plug-in GUIs of all our software are broken under Monterey. We're working on a fix and will let you know asap when the new versions are available. 

Best, 
Paul

Wow, glad I saw this I was just about to update to Monterey because all my other important stuff is reportedly fine, but if it messes up VE Pro 7, then I must wait until I get the all clear from you guys.

Originally Posted by: Paul

Hi Ashermusic, 

You can adjust the auto-saving times in the VE Pro Preferences.  

Best, 
Paul

Odd, somehow it got changed to 1 minute:)

Is there a way to control what it saves? I never, for instance, automate in VE Pro, only in Logic Pro.

Is there a way to control how often it does so?

Personally, I feel no need for multi-port. I use one VE pro project per instrument and if I cannot get the work done with 16 articulations, it does not reflect well on my skills IMHO.

I am a single instance per instrument guy. Just like a score page.

I just tried it here with 9 VE Pro 7 instances, each with 1 instance of EastWest Play Hollywood Strings Diamond, which is very resource demanding, connected to 9 VE Pro 7 software instruments  in Logic X 10.4.8.

Chose Bounce- And Replace All Tracks. The resulting bounces are flawless.

Originally Posted by: Dewdman42

Asher I still don’t understand your workflow case about one staff per track. I don’t know logic’s score editor at all and I know you have literally written books about it, but don’t midi tracks all get their own score staff? Why do you need an isolated vepro instance for each score staff?

First of all, I have not used MIDI instruments in years and have no desire to revisit using them. But this way, each VE Pro software instrument, e.g. Violin 1, connects to a VE Pro instance with 1 instrument and all its articulations, again  e.g Violin 1.

Just like a score page. 

Originally Posted by: Dewdman42

Originally Posted by: Ashermusic

Logic Pro X does better with more instances with less in them. Also, that way, it is more like a score page.,

I tested it both ways in logic and it actually performed better in terms of cpu usage with a single instance playing 90 instrument tracks vs 90 instances, one per track. But only 1% better, which basically means it performs about the same either way. It comes down to a workflow decision for which there are pros and cons both ways. One big reason for using seperate instances is because Logic Pro can only run one midifx script per instance, which can be kind of complicated if you have 90 instruments that all need their own articulation script.

CPU usage is not rthe only way to measure how Logic does with more/fewer. Back when I tested both methoids exrtensively, as did Peter Schwartz and George Leger, we all concluded that Logic was more stable and spread the load throughout the cores better with more.

That said, that was three years ago and it is possible that things under the hood in VE Pro and/or Logic Pro have changed that.

Logic Pro X does better with more instances with less in them. Also, that  way, it is more like a score page.,

Originally Posted by: feeserface

Hey all.  I'm writing about the weirdest conflict and I've tried everything but am pulling my hair out now.

I had a Vienna Server project saved with 9 projects in it, divided by section of orchestra.  The first project was a set of Piano samples with some instruments being Kontakt Based and 2 being EW Play based.   I had a crash and needed to rebuild the system (Windows 10).  All the drive letters are the same.  I reloaded all the apps and all seemed good.  Kontakt was working, Play was working.  Cubase was working and Vienna Ensemble seemed to see all the VSTs and load sounds as did play.  Each part was working the way it ought to have. However, when I went to put it all together again Vienna Ensemble hung while Play was trying to load its samples (would love the ability to 'skip' offending vsti's in a project/server project load btw)

I proceded to remove Play (I tried both version 5 and 6) from all my vst folders and reloaded the project into Vienna.  All the Kontakt's loaded without a hitch.  The instrument that should have had Play, was skipped but the placeholder was there, so what I then did was put the play VST back into its original place, rescanned plugins from within Vienna, loaded it where it should have gone and was able to load my samples....

"Great" I thought.  It must have been a corrupt Play file.  So I resaved the project with the new Play File loaded and quit Vienna (after saving the Server Project).  I figured on the next load should now be smooth.  But the exact same thing happened.   Vienna Hung on the Play load.

What's weird is when I run play alone, I can load the file.  When I load Play into Vienna empty and try to load the samples, they load.  But...when I try to load a Play sample into Play as part of a Project/Server Project load.  It hangs.

The only solution for me right now is to save the project with Play empty and manually load Play on each reload.  Obviously this is not ideal.  Any help would really be appreciated.

 

Thanks

Play 6.1.2?

Also, VE Pro dows a better job spreading the load throughout the cores than any DAW.