Vienna Symphonic Library Forum
Forum Statistics

182,219 users have contributed to 42,213 threads and 254,714 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEPRO 32bit & 64bit Servers side by side on MAC OS X ( ? )

  • VEPRO 32bit & 64bit Servers side by side on MAC OS X ( ? )

    G
    G

    Dear folks at VSL , Dear community,

    I need some help / insight concerning the following :

    when I open VEPRO 32bit and VEPRO 64bit side by side on my MainDAW ( ... the  MacPro listed below in my signature ... ),

    then launch Logic(32bit) and try to connect with the particular instances via the VEPRO AU inside Logic 9.1.3 (32bit) I notice the following behavior :

    Whenever the sum of RealMemory used by the VEPRO 32bit Server and the 64bit Server themselves is around 3,7 GB / 3,8GB

    Logic (32bit) will crash when I try to connect with an VEPRO instance .

    I thought that VEPRO 32bit Server  and VEPRO 64bit Server  can  be considered as two separate applications  ( ?)  .

    But obviously Logic 9.1.3 (32bit) recognizes the two Servers as one big single 32bit application and cannot open

    the connection when the 32bit RAM Limit of this big "single"  app is reached .

    Look at the screenshot below :

    the VEPRO 32 Server itself consumes 2,18GB of RAM , the VEPRO 64bit Server 1.60 GB .  At this point I still can connect to the VEPRO instances from within Logic 32bit .

    Actually my aim was to leave the VEPRO 32bit Server as it is now  , but load at least " a little bit" more into the VEPRO 64bit Server .

    However , loading a further patch in ( ... either the 32bit Server or ... )  the 64bit Server will raise the number of  RAM used by the particular VEPROServer  ( ... -> so the sum of used RAM for both Servers is rising above 3,8 GB  ... )  and results in Logic 32bit crashing .

    (  Just for the record : In this particular setup the VEPRO 32bit Server  contains  6 instances with EastWest's PLAY only, the VEPRO 64bit Server contains four instances  with K4.1 only . Both PLAY and K4.1 load samples into their own Memory Servers outside VEPRO .  My VSL stuff is on the Mac G5 Slave computer .  )

    Please , can someone clarify  things for me ?

    Am I missing something here ?

    ( By the way , I don't want to use Logic 64bit . Logic 32bit is stable on my setup , while Logic 64bit and its 32bit Bridge is not . )

    Thanks in advance  for any help and info/insight on this  ,

    Best 

    Gerd

    _ _ _ _ _ _ _ _ _ _ _ _ _  _  _  _ _ _ _ _ _ _ _ _ _ _ _
  • G
    G

    HI Gerd,

    I know you and I have discussed the VE Pro 32 and 64 bit servers at length. 

    Attached is a screen shot of my activity monitor with my typical orchestral template loaded. Note that currently, I am only using 6 instances of VSL stuff in my 64 bit VE PRO instances. No Kontakt or other. 

    You can see that the total ram usage of the 32 + 64 bit servers is over 6GB. So at least on my machine, that doesn't appear to be a limitation. I can connect easily to the various instances of VE PRO, decoupled or not. No problems. 

    I wonder if the problems you are having are somehow related to the size of the VE PRO 32bit ram load (which I know on your machine consist of EW PLAY, same as mine). After our discussions, I found that any more than 2.0 GB loaded into VE Pro 32 bit server caused funny things to happen, and generally precipitated a crash. When I got up to 2.5 GB I couldn't even connect VE PRO instances in Logic without a crash.

    I am using Logic 9.1.2 in 32 bit mode. I resisted upgrading to 9.1.3 in the last week.
  • G
    G

    Andy , thank you for sharing your information !!!

    Very interesting . Obviously I have to  do some more testing on my system.

    There's something I still don't understand ... .

    It would be great if VSL could chime in here .

    Best wishes

    Gerd

    P.S.:

    Andy , you do not necessarily need to upgrade to 9.1.3 . This is more an update for Nehalem Macs with virtual cores .

    Actually it now takes several attempts to open the GUI of PLAY or Kontakt within Logic9.1.3 , a behavior that

    I didn't recognized in Logic 9.1.2 on my DAW .
  • marnixM
    VSL Team
    marnixM

    Hi Gerd,

     

    VE Pro Server 32-bit and 64-bit are indeed two separate applications!

    And the RAM limitation of any 32-bit application would be around max. 3 GB, so the crash would occur much earlier...

     

    I actually suspect the Memory Servers to be the culprits - please try and disable the Kontakt Memory Server first, does that already make a difference?

     

    Best, Marnix
  • G
    G
    last edited
    last edited

    @marnix said:

    I actually suspect the Memory Servers to be the culprits - please try and disable the Kontakt Memory Server first, does that already make a difference?

    Best, Marnix

    Ahaaa .... !!!

    That's the solution of this little riddle ! Marnix , you saved my day !!! Thank you , thank you , thank you  !

    As you've suggested I switched off KMS in the Konatkt4 Instances within the VEPRO 64bit Server , quit the VEPRO 64bit Server , then reloaded it , and added some more Kontakt Sounds .

    Actually Logic32bit does not crash anymore when I now try to connect to the VEPRO Servers , although I have now much more loaded into the VEPRO64bit Server .

    @Andy : thanks again for your infos and your help .

    @ Marnix : thank you  so  much indeed,  ... from now on I will call you  Sir Marnix ...

    Best wishes

    Gerd
  • G
    G

    Thanks Marnix - great info. I will keep this in mind when adding kontakt instances to my VE PRO 64 bit setup. 

    you are welcome Gerd!

    best,

    andy