@Cyril said:

Did you check QLSC compatibility page :

http://www.soundsonline.com/Symphonic-Choirs

Why dont you post your problem on Cubase forum ?

If you read Cubase compatibility list there are some restrictions because of problem with versions of Cubase

I am not going to fight with you :

I this guy has problem hosting Play QLSC in VEP and other "Play" instruments are working ok, it could be because with add on of the word builder Play behave deferently.

Did you read well, I am speaking of using or not using MIR, that does make a big differences of what you can or cannot do and where you put the load !!!!! and to justify the use of  VEP

Is is a non sense to host "Play" in VEP if you are not using MIR, because you add a level.

This end the subject

Sorry for the delay, guys, been working hard to get this stuff all working. I originally had 2 slave boxes, one housing EW products, and the other VSL (with aux items like Superior Drummer and Trillian scattered around) and a master box for Cubase.

The EW box, well, it crashed all the time, and after a long while of trying to fix it, I finally abandoned it just last week or so.

So now, I have my VSL slave, and my master box running Cubase - and that box is now housing EW as well.

Over the course of the last few weeks, I've removed the crashing computer, replaced a faulty router, and downgraded Play to version 3 since I'm using Cubase 6.5.

Both boxes have static IPs.

With the exception of EWSC, EVERYTHING is finally working. It's been a long haul! 

Right now, I'm using VEP5 on both boxes. And that includes Play in VEP5 on the master. It works fine, no glitches/pops.  The VSL box is all Samsung EVOs, so it blazes. The master box is all HDDs, so I've turned disk streaming off in Play and set it to 2048 samples, which seems to work great.

As I say, the only issue I have now is that EWSC will load (WB multis), but in time, it simply drops the samples, and goes blank. Reloading works to solve the problem.

I'm very happy that everything is working.

Obviously, I can't be building huge templates now as I only have a 24gb (RAM) slave and a 16gb master that's doing double duty to house Play, but as funds allow in the new year I will get a second slave and things should be just peachy. In July, I'll be upgrading the master to Samsung EVOs as well, which will allow me to load more instruments, obviously.

The biggest problem I face now that everything is working, is that Windows 8 doesn't support my GI-20 (midi guitar controller) so I think I will have to install Cubase on the slave (Win 7 Pro) and when using the guitar, write on that box. Unless of course someone knows if I can keep the guitar on the slave and somehow have Cubase read it on the master?

Thanks a lot for all the help I've received on this forum over the years. I'm finally able to write again:)

edit: ps, no MIR, just mirX for VSL and Altiverb 6 for everything else...though to be honest I've not figured out how to get Altiverb into VEP5...

Shawn

@Cyril said:

Is is a non sense to host "Play" in VEP if you are not using MIR, because you add a level.

This end the subject.

I hope you have stopped 'helping'.  You're just adding noise now.

I used to isolate Play in any of the versions 3. That was because its memory server and Kontakt's memory server - which on OSX one had to use with Kontakt 3.5 for the memory access - would not share the same sandbox.

That isn't true for me today because I don't use Kontakt memory server; I don't know if the two still won't co-exist. But in that scenario VE Pro would only ever crash.

Civilisation 3 ; before criticising my post you should think a little

1 ) Play in Daw

Logic or other DAW  -->> Play --> Logic --> amplifier

2) Play in VEP

Logic or other DAW  -->> VEP -->> Play--> VEP/MIR --> Logic --> amplifier

How can you say there not a level !

I can return "You just say rubbish !"

So I will repeat :

It is a non sense to host "Play" in VEP if you are not using MIR, because you add a level.

-->> = Midi

--> = audio

I should think. Why do you use VSL instruments in VE Pro? What is different?
I didn't say 'you don't add a level', I said that you add a level with VSL, Kontakt, Spectrasonics, etc. Obviating your point completely.

You should read!

This last bit does nothing but reiterate your silly "point". You should see if you can get a working definition of *sense*.

Isn't Cyril saying that if you have Play working separately, and VE Pro working, then unless you are trying to use Play with MIR it is not necessary to use Play as a plugin because that would be redundant? 

That makes sense to me, though I just use Play separately on another slave since it is somewhat difficult to deal with.

I don't have an opinion on this, however PLAY is a cumbersome engine, and the Symphonic Choirs may be unique (therefore irreplaceable), but both system hungry and very hard for the user to perfect their enunciation, so it is best not to include them in a large project, but rather to dedicate a separate project to the choirs and effect/filter/mix them there (except for reverb), and then import the results as audio files. What happens then (VE PRO or straight to sequencer output) is not within my purview to say, although I very happily throw them as audio regions in Logic and its output. If working with MIR some other way may be preferable.

Even professional recordings in big studios oftentimes have the choirs sing on top of previously recorded orchestras to simplify the process. And the human choirs are 100 times more flexible than the EWSQ. 

@William said:

Isn't Cyril saying that if you have Play working separately, and VE Pro working, then unless you are trying to use Play with MIR it is not necessary to use Play as a plugin because that would be redundant? 

That makes sense to me, though I just use Play separately on another slave since it is somewhat difficult to deal with.

 Hi William

Thanks for your support

In my setup I have QLSC (Play) in Logic and I send the audio result to VEP/MIR( in 5.1)

I do the same for Omnisphere and K5 😉

@Errikos said:

dedicate a separate project to the choirs and effect/filter/mix them there (except for reverb), and then import the results as audio files.

That is what I've ended up doing out of pure fear of causing a nuclear detonation on my street by trying to use Play and VEPro simultaneously.

@William said:

Isn't Cyril saying that if you have Play working separately, and VE Pro working, then unless you are trying to use Play with MIR it is not necessary to use Play as a plugin because that would be redundant? 

That makes sense to me, though I just use Play separately on another slave since it is somewhat difficult to deal with.

"1 ) Play in Daw

Logic or other DAW  -->> Play --> Logic --> amplifier

2) Play in VEP

Logic or other DAW  -->> VEP -->> Play--> VEP/MIR --> Logic --> amplifier

How can you say there not a level !"

and:
"It is a non sense to host "Play" in VEP if you are not using MIR, because you add a level."

To host Play in VEP, is somehow 'a non sense' but one supposes to host Vienna Instruments in VEP is a sense.

I've seen this stated enough times to believe I understand it. So, it looks like a misunderstanding of the whole raison d'etre of VE Pro. VE hosted only VSL (and on OSX the Apple AU developer FX). VE Pro was developed to_host_third_party_plugins. But these ["Play, Kontakt 5, Omnisphere"] hosted in VE Pro is "a non sense" because 'you add a level'. It's pretty goofy.

I think if I simply had to use EWQL Symphonic Choirs I would not mix that lib. with an otherwise busy project but dedicate a whole level of the project to it. EWQL is enough of a PITA period for me to look for other ways to skin that particular cat. It is definitely something I would commit to audio and send that as audio input to MIR Pro; again here is a layer of a project.

But my [certainly lighter] use of a library in Play is, other than the seriously slower loading, not unlike using Kontakt in VE Pro. Using MIR Pro has naught to do with hosting it in VE Pro making sense per se.

VEP shares the memory of it's VI ; I doubt it will whare the memory  of it's K5, Omnisphere and others

The other advantage of using Play in Logic and to send audion to VE/MIR is that it will use load of the processors not used to send midi to VE

I don't know what this means 'shares the memory of its VI'; but it seems to further show that you have a belief about Vienna Instruments as the proper use of VE Pro while other plugins are 'a non sense'. It is true that you can, through VE Pro learn and optimize the memory of Vienna Instruments but not third-party. To extend this to believing one ought not use third party instruments in it is a non-sequitur. The point of using instruments in VE Pro rather than in the DAW is they perform better, being in a different process. Look it up, ask around, something. 

You can do what you like but you are inflicting this misleading idea on the forum.

I don't see any advantage there per se, as you are almost certainly using more resources to do an audio input than you would to host it in VE Pro. Maybe there is something so botched with Logic's handling of cores? Who knows what's true for you and why, since what you are articulating conveys nothing of it, but this nonsense. Sending MIDI to VE Pro is that much of a load? Vs. sending audio? You're simply wrong. Everything you say seems to be illogical, based strictly in your strange beliefs.

If you dont know whay it means to share memory, I dont need to discuss with you anymore.

You have a lack of knowledge !

For your information it is less cpu intensive to treat an audio flow than a midi  flow

 So you dont die i... : If in a same VE  you have Violon I and Violon II when you load Violon II you do not load the samples in memory, you just load the settings. Violon II will uses the same samples than Violin II, same for all the instruments, when you have 4 x French horns the samples will be loads once !

You see some times it is better to keep your mouth shut when you do not know fully the subjet you are talking about

another rule for VI, it is less CPU intensive to have then in a VE than in Logic because of VE. The Problem in Logic with VE is that all midi flow is treated on one CPU. So if you have other plug-ns they will be treated with another CPU