Vienna Symphonic Library Forum
Forum Statistics

196,675 users have contributed to 43,023 threads and 258,419 posts.

In the past 24 hours, we have 2 new thread(s), 3 new post(s) and 99 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. .mframe32 and .mframe64 opening with same server app

  • .mframe32 and .mframe64 opening with same server app

    S
    S

    I am trying to find the best solution for using both PLAY and Kontakt in VEP since they can't seem to coexist in the same metaframe anymore.

    So the idea is that I use PLAY in the 32-bit server and Kontakt in the 64-bit server.

    However, if I create a 32-bit metaframe, close down VEP and double click the .mframe32 file, it will correctly start up the 32-bit server. However, double clicking the .mframe64 file hosting all the Kontakt stuff will merge it into the same 32-bit server. It will not open up the 64-bit server. I have associated the files correctly in OS X, but it doesn't work. Seems like when VEP server is open, OS X can't tell the 64-bit one from the 32-bit one.

    Same thing happens if I load up the 64-bit metaframe first, then the 32-bit.
  • civilization 3C
    civilization 3C

    I bet this issue is a product of double-clicking the metaframes. Start the servers and use the menu. It_works.
  • S
    S

    Of course I am double clicking (or in my case, choosing the mframes from a stack folder in the dock) - that's the whole point: It is a very quick way to launch two mframes, instead of first launching each server, then browsing to each mframe to load. It should be possible, but for some reason those two file suffixes are seen as the same by OS X.
  • A
    A

    Further to this The "open recent" menu shows both 32 and 64 bit mframes. I've started labelling the 32 bit versions as "32bit" just to remind me. 

    Can you make a better way?

    Thanks

    Amiin