Vienna Symphonic Library Forum
Forum Statistics

200,579 users have contributed to 43,201 threads and 259,101 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. .mframe64 + .mframe32 opening with same server software

  • .mframe64 + .mframe32 opening with same server software

    S
    S

    Hi.

    Trying to work around a memory limitation I am now dividing my VEP instances between a 32-bit and a 64-bit server. However, if I click on a 32-bit metaframe while the 64-bit server is running, VEP tries to add those instances to the currently open 64-bit server. The same goes the other way around. I am on OS X, and ".mframe32" is set to open with "Vienna Ensemble Pro Server" while ".mframe64" is set to open with "Vienna Ensemble Pro Server (64-bit)" - so it seems like the OS doesn't know the difference between those two, or maybe VEP doesn't:) Will it be possible to fix this so mframes will open the correct server software, so I don't have to manually open both servers and then select the mframes from there?
  • H
    H
    I've also had this issue!
  • K
    K

    OS X has a way to mess up file associations. You can however repair them relatively easily by pasting this in a Terminal window:

    /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user

    This will rebuild your Launch Services database, fixing any other file association issues along the way.
  • S
    S

    Karel, thanks, I tried this but it didn't help. Are you sure that the .mframe32 and .mframe64, when clicked, are loading up the 32-bit and 64-bit servers respectively? They still don't here. If I have a 64-bit server open, clicking an .mframe32 will just add to the 64-bit server running.

    Another curious thing is, each time I switch between starting up a 64-bit and 32-bit server, the OS will come up and ask if it is OK to accept incoming connections - as if running either server is "erasing" the information about the other one already being allowed network access. It seems the OS doesn't quite know the difference between the two.
  • K
    K

    Try rebooting after you issue the Terminal command. I will try to find a workaround for OS X' broken behavior for the next update.
  • S
    S

    Thanks, I tried that, but still no luck.
  • H
    H
    i'm interested to know, how did this issue work out? Resolved?
  • S
    S
    last edited
    last edited

    @haydnwalker said:

    i'm interested to know, how did this issue work out? Resolved?

    No, but I think Karel + VSL team are working on a fix for a future update😊

    In the meantime I'll try writing an AppleScript that can launch two mframe's using the correct server software.