Vienna Symphonic Library Forum
Forum Statistics

196,146 users have contributed to 43,014 threads and 258,392 posts.

In the past 24 hours, we have 0 new thread(s), 6 new post(s) and 169 new user(s).

  • In a multi-Mac environment, is a G5 not a good component?

    I'm using a Mac Pro Quad 2.66 as master and a Mac G5 Dual 2.0 Ghz as a slave. G5 has 32 bit version of VE Pro, Mac Pro is running 64 bit VE Pro and 32 bit VE Pro

    I'm using Logic 9.1.1 in 64 bit mode.  I get the message "the 32 bit server has unexpectedly quit" which is Logic's internal server to be able to run 32 bit plugins while in 64 bit mode.  A guy on the Logic forum told me I should not use the G5 since it has to operate in 32 bit mode...

    Thanks for any opinion!


  • last edited
    last edited

    Hi ,

    please read this recent forum entry .

    I assume there are two things that are causing the trouble on your system :

    1. Logic 64bit . The 64bit version and especially its 32bit-bridge is currently (9.1.1) not where it should be . Period .

    2. When working with both 32bit and 64bit version of VEPro on your MacPro , you currently should also follow these simple rules :

    a) In the 32bit VEPro version only load PLAY Libraries . Nothing else .

    b) Load all other Libaries into the 64bit VEPro .

    c) Most important :

    Launch the 32bit VEPro metaframe with its PLAY Libraries first !!!

    Then launch the 64bit VEPro metaframe with its K4.1 libraries and VSL libraries !!!

    My setup - as described in the above mentioned thread - works flawless with these kind of rules.

    Best

    Gerd


  • Despite the fact that Gerd said "period" I am going to partially disagree. I am running Logic 9.1.1 64 bit with both the 64 bit and 32 bit servers of VE Pro and having very little problem. Also, the 32 bit bridge is a temporary workaround until all the plugins are 64 bit so I doubt Apple will be putting a lot of energy into improving it. What he is correct about however is that you want to load your Play stuff before you load the Kontakt stuff as K4 kind of reserves all your unused memory.

  • last edited
    last edited

    @gerdkaeding_31947 said:

    1. Logic 64bit  . The 64bit version and especially its 32bit-bridge is currently (9.1.1) not where it should be . Period .

    I have to disagree with that.  With 64 bit plugins, Logic has been working extremely well for me, a huge improvement over running in 32 bit.

    There are sometimes problems with running plugins in the 32 bit bridge, but that is to be expected to some degree since it is a hack to combine two different kinds of code.  I get occasional crashes with the 32 bit bridge but far less than trying to run big sessions in Logic 32.  The fix probably isn't improvements in the 32 bit bridge but 64 bit versions of all plugins - the bridge is just a hack to tide people over until third parties catch up.

    I'm not surprised that there are some issues with things like VEP, and it does make sense to try various workarounds in those situations.

    Mike


  • last edited
    last edited

    @Ashermusic said:

    ...you want to load your Play stuff before you load the Kontakt stuff as K4 kind of reserves all your unused memory.

    ...but just to clarify, that's only when you have Kontakt's KMS (memory server) enabled, correct?  I've found that in an all-64-bit scenario (i.e. Kontakt 4.1 running inside a 64-bit VE Pro server OR Logic in 64-bit mode), you can disable KMS as it's not needed, and the overall memory situation comes out in the wash.  I believe it's only with KMS enabled that Kontakt reserves any unused memory?  Someone please correct me if I'm wrong about that!


  • Well, Jim, I would argue that KMS is still needed as otherwise the reloading of samples time is way too long.

  • last edited
    last edited

    @Ashermusic said:

    Well, Jim, I would argue that KMS is still needed as otherwise the reloading of samples time is way too long.

    Ah yes, hadn't considered that as it's not a normal part of my personal work flow (I load my template/metaframe in the morning and that's it).

    Thanks Jay...