194,425 users have contributed to 42,920 threads and 257,967 posts.
In the past 24 hours, we have 4 new thread(s), 11 new post(s) and 69 new user(s).
For sure - SMART BUSINESS move VSL. You are going to now get NEW adopters into your program just because of this. Which will help us long time users (the stronger you are - the more we benefit in new and well done libraries now and in the future.) It's all good.
Rob
Indeed a smart move. BTW, will it be possible to purchase VEP without owning a VSL instrument?
I have a technical question regarding VE:
When running several instances of VE on a mac pro (with the audio outs rewired to Logic 8), does OS X allocate each separate instance of VE to a different core?
Thanks in advance for your answer!
Thanks for your answer! Does the OS typically schedule the threads evenly, or does it leave much to be desired?@MS said:
This depends on how the operating system decides to schedule the VE threads. One instance of VE will run one thread for gui, one thread for audio processing and several threads for sampler disk streaming.
The reason for my question is that I have some very CPU-intensive kontakt instruments. I am considering running each instrument in a separate VE instance to try and "force" the OS to schedule each to a different CPU core.
Thanks for your answer! Does the OS typically schedule the threads evenly, or does it leave much to be desired?
The reason for my question is that I have some very CPU-intensive kontakt instruments. I am considering running each instrument in a separate VE instance to try and "force" the OS to schedule each to a different CPU core.
Most of the time, the OS is really very good at scheduling threads. As long as you (as a developer) try to keep a sane threading model in your application - you can usually trust the OS to do the proper scheduling, as long as you have thread priorities set correctly. There are of course times when thread context switching can cause performance losses, but to my experience - the OS scheduler is remarkably good and quick. I suppose you are using Kontakt in a sequencer host today, I would recommend to have the sequencer handling any threading or affinity.
When it comes to threading in audio applications, and mixers in aprticular - there are several things to consider. At one or several points the threads need to be syncronized, for submixing, bussing, sends etc, and this can create some issues if it is not done properly. I know some people, running multiple audio input objects in Logic, are having quite some issues with most of processing plugins ending up on the same mixer thread, overloading even an 8-core machine with only a few plugins.
Thanks for your answer! Does the OS typically schedule the threads evenly, or does it leave much to be desired?
The reason for my question is that I have some very CPU-intensive kontakt instruments. I am considering running each instrument in a separate VE instance to try and "force" the OS to schedule each to a different CPU core.
Most of the time, the OS is really very good at scheduling threads. As long as you (as a developer) try to keep a sane threading model in your application - you can usually trust the OS to do the proper scheduling, as long as you have thread priorities set correctly. There are of course times when thread context switching can cause performance losses, but to my experience - the OS scheduler is remarkably good and quick. I suppose you are using Kontakt in a sequencer host today, I would recommend to have the sequencer handling any threading or affinity.
When it comes to threading in audio applications, and mixers in aprticular - there are several things to consider. At one or several points the threads need to be syncronized, for submixing, bussing, sends etc, and this can create some issues if it is not done properly. I know some people, running multiple audio input objects in Logic, are having quite some issues with most of processing plugins ending up on the same mixer thread, overloading even an 8-core machine with only a few plugins.
Thanks again for your answer!
As you have imagined, I'm running kontakt in Logic Pro 8. To my amazement, Logic frequently runs many Kontakt instances all on one CPU core, while other cores idle. So, I am stuck using PC servers for the moment.
It is my hope that VE Pro will be a way to force each Kontakt instance onto a different core, but still be able to mix inside logic -- so I can get rid of my servers and run everything on my mac pro.
Do you think my hopes are reasonable?
AFAIK there is no requirements to run a VI in VEPRO to make it work, and it has been hinted that you don't even need to own a VI to purchase VEPRO when it becomes available so in short the answer should be yes!
The current model for VE3 network is that each purchase gives you three licences, so you can have three slave machines connected to 1 DAW (or two if you are going to run VE3 locally). You need a dongle for each slave computer.
Best
Tim
Hi everybody,
we are focussing on VE PRO for the next month, and I believe that it cannot be released before mid/end of may, realistically.
We need to make sure that VE PRO is rock stable - for all of you [:)], and that includes some serious testing and fine-tuning.
Thanks for your patience and enthusiasm!
Best,
Paul
