@Paul said:
Hi,
the focus is on finishing VE PRO in April.... but as always with software, there is no guarantee, only high hopes and the best attitude 😊
Best,
Paul
Paul, are any of these new features going to be available for VE2?
DG
191,468 users have contributed to 42,803 threads and 257,398 posts.
In the past 24 hours, we have 6 new thread(s), 24 new post(s) and 28 new user(s).
This got really quiet from VSL. I can only imagine that they are both recovering from the show and working hard to post VEP.
Rob
Hello everybody,
these new features will only be available with VE Pro, of course.
But there will be a 64 bit version for the "normal" Vienna Ensemble as well, I hope soon.
Most likely there will be multiple outputs.
We are going through some tough testing routines, and this will still take some more time, I hope it´s not much more than a month.
As always, we will release more informations when the tests are finished! Thanks for your patience, it will be worth it!
Best,
Paul
Hi Paul,
I want it as 'fast as possible' - BUT need it to your normal VSL release standards (few bugs as possible). Good luck on this last testing and I am looking forward to it.
Rob
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.