Hi,
thanks for your reply! Regarding memory I did following measurements:
Logic working with 2 VSL Ens. new created each with one 20 MB patch:
Total System free is 1 GB out of 2 GB - Logic takes 135 / 586 MB (phys/virt) - VSL Ens 117 / 577 MB (phys/virt)
When relaunching Logic and reloading project it hangs and memory is:
Total System free is still 1 GB out of 2 GB - Logic takes 127 / 575 MB (phys/virt) - VSL Ens 68 / 526 MB (phys/virt)
VSL Ens Service Monitor shows no active instances, however 2 empty VSL Ens GUI Windows are already shown. In the activity monitor Logic and VSL Ens. are marked red as no reaction ("reagiert nicht"). Overall CPU is far below 100%. From a progamming perspective it looks for me more like a lock state or race condition than processing overload or out of memory behaviour.
What is remarkable is that vsldeamon also is marked as "reagiert nicht" even in first part of test although VSL Ens is working good.
Before doing these tests, I even did a complete re-install of VSL including removal of preferences and *.plist files.
Sorry, for bothering with these problems, however I really like VLS Ens approach, but need more plug in instances since 16 midi channels pro plugin is for orchestral work not enough...
Regards
Rolf
PS: If it helps I have the 2 activity monitor screenshots as tiff.
-
OK, I'm out of my depth here, as I don't understand the inner workings of memory on OSX, particularly with regards to physical vs. virtual memory. I still have a feeling that this is memory related, but I'm afraid that you will have to wait until some other Mac users are around for some better advice. Sorry. [:(]
D
-
It is normal for the VSL Daemon to be marked "not responding" ("reagiert nicht") in the Activity Monitor. It remains with this marking throughout operations, but, nonetheless, works. This is also true of the VI software as well as the VE software. However, I can confirm that opening a file with two instantiations of Vienna Instruments causes Logic 8 to crash. Attempting to implement the fix that Paul describes below also did not work - - I was able to quit VE within Activity Monitor, yet the control panel windows associated with VE remained visible and Logic 8 stayed marked as "not responding."
-
Hi everybody,
this is a known bug - we are already working on it.
Loading songs that contain more than 2 Vienna Ensembles do not open - the only workaround for now is to close the "Vienna Ensemble" process in the Activity Monitor. The song will load and the samples will load as soon as you "reconnect" the interface.
Sorry for the inconvenience, a fix can be expected :-), but I cannot give you a date yet.
Best,
Paul
Paul Kopf Product Manager VSL -
Paul:
I tried the procedure you describe, but it did not work. I was able to quit VE with Activity Monitor, but the control panels associated with VE remained visible and Logic 8 continued to be marked as not responding. The song never loaded. Logic had announced previously that it was having difficulty loading a plugin.
-
Paul:
As I posted above, the procedure you outlined did not work with Logic 8. Ostensibly I could stop the VE processes using Activity Monitor, but the small control panel windows remained visible and Logic continued to be marked as "not responding." Logic had, in fact, crashed and had to be force quit.
In addition to this, the bug which causes VE to launch whenever Finale is launched was made worse by the attempting the procedure you described. Not only did VE launch, but Finale and VE crashed - - and had to be force quit. I was then unable to open any Finale files. (None of these files have VE instantiated because because, of course, VE cannot be instantiated within Finale since Finale is limited to "powered by Native Instruments" plugins. It's just that VE launches - - for no immediately obvious reason and to no purpose - - every time Finale is launched.) Luckily, I was able to correct this aberrant behavior - - to the extent that I can once again successfully open Finale files (even though VE continues to launch itself when Finale is launched) by rebuilding the startup disk's directory, once again, with DiskWarrior.
If my experience is any guide, VSL users should refrain from instantiating more than one instance of VE in Logic 8 until this bug has been fixed.
Stephen
Dual 2.5 GHz G5
7GB RAM
OS 10.4.11
MOTU 2408 mk.3
Logic 8 (& Logic Pro 7)
Finale 2008
DP 4.6.1
-
Hi All, I'm a Logic 8 user, and I posted a similar experience already under another subject heading. I can confirm that Logic 8 will not re-open any file that has two instances of VE. Logic becomes unresponsive, and quitting out of VE makes no difference. Unless we can come up with a solution or workaround, any Logic 8 file with 2 VEs is for the moment, DOA. Cheers, James
