Vienna Symphonic Library Forum
Forum Statistics

196,954 users have contributed to 43,043 threads and 258,499 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. isn't VE Pro supposed to ask about converting to VI Pro

  • isn't VE Pro supposed to ask about converting to VI Pro

    civilization 3C
    civilization 3C

    That doesn't happen here, hasn't for three projects in a row. When I went to the menu to convert, a save as and reopen maneuver, it crashed VE Pro.

    These are projects in metaframes. Is that excluded from this routine?
  • PaulP
    VSL Team
    PaulP

    Hi Gianna, 

    it helps a lot include at least the system specs of your computer (used versions, OS....), so that we can reproduce this behaviour. Conversion to VI PRO instruments is based on VE PRO projects (*.viframes), which can then be saved in a *.metaframe file, of course.

    Which other plug-ins are included in your setup? 

    Best, 

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • civilization 3C
    civilization 3C

    Build 6844 of VI Pro & VE Pro. OSX.6.4 (slave = MacPro 8 core, 24GB). There is Kontakt 3.5 with VI in one project, Kontakt 4.1 with it in another (64-bit), VI by itself in others, both servers... there are Vienna Suite and IK plugs in the 32-bit instances, Vienna Suite in the x64. One mixes Kore2 with VI, another with VI and Kontakt. Same result as far as a message asking me if I want to convert. Hasn't happened.

    I am not able to reproduce last night's crash this morning, using the project that crashed. I've opened, and converted/reopened ca. 9 projects today. I hoped it would work in the mixed projects where I don't have to reload the Kontakt to do this.
  • civilization 3C
    civilization 3C

    The plot thickens. That viframe project by itself does not crash. In the metaframe, converting it [save as and open same] does. This is the 32-bit server, three instances in the metaframe.

    Now, next try: the same meta (bypassing the save as for this viframe) avoided the crash. However, it would not load the plugin IK Multimedia 'Amplitube Jimi Hendrix' with the conversion/reopen. And will not load that plugin in this instance now.

    Next try (NB: I saved the viframe in this case and the previous try beforehand, not during the conversion): converting that viframe = crash. So save as does not appear to be the cause of the crash.

    Try 5: I have saved a version of the viframe that has the preset in the ATJH plug renamed. I opened the metaframe, which I had not saved with this tiny change in that viframe, and converted/opened the new version, did not crash or fail to load that plug. Pretty weird.

    Sp mostly these things will convert, but it means reloading some kontakt and other things. the kontakts use some samples, so...
  • civilization 3C
    civilization 3C

    New problems. I clicked on one of the other instances in this metaframe, and VE Pro crashes. I reopen with this metaframe and repeat the conversion. VI Pro GUI is frozen. Kore2 and Kontakt GUI are nonexistent (white).

    Try again: save that viframe with a new name. Convert/open that name. NI GUIS, VI GUI, fine. Go to open Amplitube Jimi Hendrix, white GUI and a crash. So, the combo of Kore2, Kontakt 3.5 (KMS), VI Pro and ATJH is not copasetic.

    My guess at this point, is these GUIS all in the same project doesn't want to happen.