@Seventh Sam said:

For your purposes, absolutely. Synchron is designed to get you up and running much more quickly than VI. The great thing for you is that if, for whatever reason, you want to return to the under-the-hood flexibility of VI, you have that available too 😊

Thanks Sam

Anyone else got any ithought re whether this is worth doing? 

Do I have to load a seperate player for each instrument?

Today is last chance to do this so any help much appreciated

Thanks

Jill

@bbelius said:

I can fully recommend this upgrade.
You can use one instance and load different articulations in it, but most of the time you will use one instance per instrument.

Thanks Ben for the quick reply.

For a full orchestra thats a lot of instances though. I've just got used to the ease of being able to load all my instrument section into one interface hence my hesitation

VSL's tools are highly optimized. For example you can load 10 instances of Flute1, but it will load the samples only once and share the samples in memory. The additional instances will only need a little more RAM for displaying processing the different settings. The high instance count will not be an issue; in fact you can use much more instances compared to Kontakt.

It look like that In Logic when you use VIs the load is better spread accross the processors.

Can somebody confirm this ?

A question for Martin : If you use the same instrument with VIs, is Logic/VSL is sharing memory ?

Best

Cyril

@jjmus said:

I've still time to purchase all my special editions as crossgrade to the new format at a good price. Could I ask Is this worth doing ? I like something that is intuitive and easy to set up and doesn't get in the way of the composing flow. The end focus is always on a live orchestra playing the works, I just use vsl for composing and mocking up the piece for the performares.

Thanks

Jill

It has been well worth the upgrade, but I do recommend turning off two of the three reverbs (I think each loads with two of the three reverbs as on by default). What makes Synchron nice is how quickly you are up and running. Since all of the instruments are pre-eqd (meaning, they dont sound flat and empty like the VI instruments do) and the panning is correctly done for you out of the box, you can have a good start right away. Of course, you loose the flexibility with Synchron for tweaking, you get to keep your VI library so if you still wanted to do this, you can. Of course, also, the eq'ing is negated if you have MirX / MIR Pro, so there is that to consider. If you have one of the variants of MIR, the real thing you have to consider is whether you like the Synchron stage sound (bigger, more film score oriented) and whether the UI suits you. Personally, Im not a fan of the UI, but Ive been learning to get around it, I think the UI looks cheesy, but that might just be me. The other major thing you loose with Synchron is the divisi feature, so if you rely on that in Instruments Pro, you wont find it in Synchron.

For me personally, it was well worth the upgrade, and depending on the work that Im doing, I use both libraries. I only wish they would upgrade Instruments Pro to be compatible with the Synchron libraries as I have all my presets and shortcuts already setup there, and I like the UI more in Instruments Pro (now if we can get Vienna to upgrade the UI to allow resizing).

There is one other note worth considering, you wont be using any variatns of MIRx with Synchron and if you plan to use MIR Pro, you will need to do some tweaking for the Synchron libraries (disabling all the builtin reverb settings in Synchron and some eq'ing, depending on the venue you choose to use).

I lied, one more thing to consider, if you plan on getting the bigger libraries, keep in mind that Synchron has no woodwinds outside of epic orchestra and the special edition libraries, so you will need to purchase MIR Pro with the Synchron stage impulse response addon in order to utilize woodwinds from Instruments Pro, to have the same impulse responses / timbre as the libraries offered in the Synchron libraries.

Hi Cyril, 

@Cyril Blanc said:

A question for Martin : If you use the same instrument with VIs, is Logic/VSL is sharing memory ?

We are always using shared memory, with all 3 players. 

Best,
Paul

Hi Paul

Thanks for your answer.

IF you work on big templates, considerig the problem of Logic to spread  the VE process across different processor  the solution seem to be not to use VE but VI

Can you confirm ?

Is this problem occurs with Cubase on Mac too ? other DAW on Mac too ?

Does this problem occurs on a Windows PC using Cubase ? other DAW on Windows ?

Best

Cyril

Hi Cyril, 

I don't know which problem you are referring to.

In my experience, there is no better multithreading available than in VE / VE Pro. but of course you're free to experiment. 

Best, 
Paul

Hi Paul

@Paul said:

I don't know which problem you are referring to.

You dont remember all the post complaining that Logic was using only one processors with VSL  !

It has improve a little bit but the problem is still there. Speak with Martin 

Best 

Cyril

HI Cyril, 

We don't have too much influence on how Logic manages plug-ins. But it is definitely one reason to work with Vienna Ensemble / Pro. 

Speak to Logic 😉. 

Best, 
Paul

Hi Paul

Working with WE oblige to use the one process, that could be the problem with Logic !

With VI the work load is spread across all the process.

Speak with Martin to check this

Best

Cyril

Hi Cyril, 

I am speaking to Martin all the time. 

So in your probably extensive tests and research, what did YOU find out?

Best, 
Paul

Hi Paul

It looks like if I use VI instead of VE the load on my MacPro 12 core is more spread across the processors

Can you confirm ?

Best

Cyril

Hi Cyril, 

Can't confirm, but that's great. So you can use our products anyway you like!

Best, 
Paul