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.

I have to say, , I don't care for it opening by default either. It's just a small annoyance for me,  but an  annoyance just the same.

Originally Posted by: J.E.S

thanks Jay.

So, unless there is another way, I need to manually replace most of my template changing K5 into K6?

there are much worst things in life, but that is not very effecient.

Yep, you have to do it. Again, N.I. treats it as not an update like going from EW Play 5 to Play 6, which overwrites the old Play 5, but as a different plug-in, which is whaty yoiu see you still have both K5 and K6 after installing K6.

Native Instruments treats them  as two different plugins, no  different than if it was Kontatkt and EW Play.

Personally,  as Logic Pro X user I don't give a large rodent's hiney about AU 3. ArtZ ID has renedered it totally unnecessary for my uses.

Originally Posted by: Paul

Hi guys, 

Just sent you a PM with the next RC that will fix this. Please reply, we're doing quick checks here and will upload this build asap. 

Sorry for the inconvenience, and THANKS for your help!

Paul

Glad I saw this before I installed the Mac update :)

Originally Posted by: jesus_calderon_679

Same behaviour over here.

15 seconds to save any project. Please, fix it!

I think it is really sad when we have reached the point where 12-15 seconds to save is now considered "broken" by some.

I can only tell you guys that here on my iMac with Logic Pro X (High Sierra)  & VE Pro 6 , it crashes maybe once every three months.

Paul showed me Synchron Strings with the new Synchron player at NAMM on Friday. I am impressed.

Originally Posted by: RLD

Originally Posted by: Ashermusic

The extra CPU usage is not that much.

Less CPU you are using, less change you will get pops, crackels ;)

I have set up lots of VE Pro templates for Logic users and lots just in Logic. The CPU trade-off using VE Pro is definitely a major plus in terms of pop and crackle free performance.

Originally Posted by: Cyril Blanc

Do not forget that you can run your AU plug-ins inside Logic and send the audio to VEP and MIR

Normally this solution allow to spread better the load across your processors in Logic.

It is cheaper, CPU wise, to run an AU inside Logic than Inside VEP, because VEP adds another layer

The extra CPU usage is not that much. I have helped set up a lot of LA composers with building VE Pro orchestral templates connected to Logic and they are pretty much all happy now.

Originally Posted by: Paul

 

Personally, I'd stick with multiple VE PRO instances and wait for AU v3, which is high on the to-do list after Synchron Player. 

Best, 
Paul

Yes, avoid it like the plague :)

I don't understand what you are asking. High Sierra is an operating system and Logic Pro is an application. You don't "find" an OS inside an application like Logic.

I think trying to judge it without the full articulations and Synchron player is a bit like trying to judge an elephant while blindfolded by feeling its trunk, so I will wait.

I think I had 46 on my slave PC and about 30 on my iMac.

The only thing I was doing similar was running the entire EW Hollywood Orchestra in VE Pro from SSDs on a slave PC with Kontakt stuff in VE Pro on my iMac from SSDs and the restdirectly  in Logic and it worked just great.

Wel I don't know what is happening but you are using an older version of the OS and an older version of VE Pro.

The only way I know to troubleshoot it is to start smaller and test, then add things and test again, and see where you hit the tipping point.

I mostly agree with Steve's post. However, unless things have drastically changed with newer versions of DP, while it is a great DAW ( I would LOVE to have the Chunks feature in Logic) it is or was less efficient with CPU than Logic.

If you use Peter Schwartz's ArtZ ID (or SkiSwitcher if 16 MIDI channels ins enough, as it is for me) then the lack of MIDI ports in Logic is a non-issue.

All the DAWS have pros and cons but I have the definitive answer as to which one is best to use with VE Pro......wait for it.... it's cvming.., almost there....THE ONE YOU KNOW BEST!

Originally Posted by: McArnes

Until now there are no realistic string libraries on the market, they all sound like a synth.

 Nonsense, there are already a bunch of them that do not sound synthy if you know how to write for them and program them. This will no doubt be one more.

Originally Posted by: Casiquire

Wow, all the overreaction in this thread.  If you're that upset by it, return it.  Get a refund.  Move on.  And maybe this will be a good moment of learning about what early birds and early releases really mean in the world of tech.  They're a risky gamble.  Now you know, and you can be better informed in the future.

Exactly. It is a sample library, not a cure for cancer. Knowing VSL, it will be a very good one but when it comes out, it will not change your life in any meaningful way, and if you think it does, you need to re-examine your priorities.

And if it never came out, you still should be able to make quality music with the many you probably already have.

Worry more about getting better with using what you have and less about timetables and details about upcoming libraries is my advice, which of course, everyone is free to disregard :)

When you open VE Prfo first, you HAVE a  blank server project. When you open your DAW project if it has VE Pro instances that are decoupled and not connected, they don't connect to anything until you connect it.

I am sorry I am just not clear what you are trying to accomplish that does not happen pretty much by default.