Vienna Symphonic Library Forum
Forum Statistics

181,917 users have contributed to 42,191 threads and 254,630 posts.

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

  • VEPro and Ivory issue?

    I just spent the weekend loading a clean install of my shiny new Win7 64bit and reloading all my VI's onto my slave computer. Everything is working great except for Play (which we know is messed up right now) and surprisingly, Ivory. I hadn't seen any posts on this yet and actually uninstalled and reinstalled Ivory just to make sure.

    I am using the new 1.72 64bit update from the Synthogy site. VEPro sees the plugin and loads the gui, but the drop-down menus for the "program" and "session" buttons don't work. Strangely everything else on the gui seems to be working properly. Unfortunately, without being able to get to the "program" menu, there's no way to load up a piano.

    I tried the standalone with their "Cantible" software host and it worked fine, so I know my installation worked.

    Any one else having issues with Ivory or have any ideas on what I could do?

    Thanks!!


  • Anyone using Ivory with VEPro 64 bit?

    I have tried Synthogy tech support and received this:

    We do not have VE Pro here now am I that familiar with it, but I'm going to predict that there is an incompatibility with how VE Pro tracks the GUI on the slave machine.

    Unfortunately I'm not sure there's much we can do about this on our end. If there's a way for you to run Ivory natively without VE Pro, I would say that's the best suggestion I can give you. Otherwise you could try contacting Vienna to see if they have any suggestions.

    Any insight from VSL? It seems they (Synthogy) are passing the ball.

    Thanks


  • Have you tried this with the public beta that just became available (4.0.4604)?

  • Yes, I was excited to see a new build of VEP and tried it out immediately this morning. Same issue though---nothing happens when you click the Program, Session, or Keyset buttons.

    All the other buttons/knobs/switches work. There's just no way to load a sound.


  • Did you try the plugin (not the standalone) in another host? Perhaps your Ivory installation is somehow invalid. I'm asking this because Ivory is a lone wolf in this regard. No other plugins have such issues.

  • well, other than the Cantible host that they package with the latest update, the only 64bit VST hosts I'm aware of are Cubase and Sonar, neither of which I own.

    Is there some free demo of a 64 bit vst host out there that I could try?


  • Is Ivory a 64 bit application?

    I can't find any information about this on the Synthogy website.

    Does it work with the VE PRO 32 bit version?

    best

    Herb


  • It is 64 bit with the most recent update 1.72.

    I checked it in the VE Pro 32 bit version and it has the same issue. It seems to be some GUI conflict.

    I had forgot I had a license for Brainspawn Forte, so I installed that and loaded Ivory and it works fine. (Forte is 32bit)


  • One piece of info that may be important to know:

    I just realized that Ivory's Program browser opens in a separate window from the main GUI. That is something different from most other plugins I know that keep everything in the same GUI. Could VEP be preventing a second window from opening?


  • Is this program browser a standard windows file dialog or something special?

  • Here's a screenshot of how the browser looks.

    You get it by pressing the menu labeled "Program". (It says *Default currently)


  • So I loaded Ivory on my Mac Pro just to see if the same thing happened cross-platform. However everything works in VEP on OS X (32 bit--no 64 bit OS X Ivory plugin available). The menu, however operates slightly differently. Instead of a seperate pop-up window like on Windows, it opens replacing or on top of (can't tell which but it isn't movable) the normal GUI.

    Hope this helps. Hopefully we can get the windows bug figured out.


  • Does it help to undock the Ivory editor before pressing the button?

  • I should have mentioned that.

    I had the same thought and tried it, but it has no effect. Now that I think about it, it does seem odd that it doesn't work when you undock Ivory because Ivory itself is now in a new floating window. But alas, still nothing.


  • Well, I encouraged the Synthogy guys to check out this thread to see if there was anything they could chime in on. They responded and basically said they had read the thread and since Ivory works with other hosts on my machine, that it would need to be solved on VSL's end.

    I'm surprised no other users have chimed in. Isn't anyone else using VEPro 64 and Ivory 64 on Win7 64?

    I guess I'll try to squeeze Ivory natively into my DAW in the meantime till this gets sorted out. Too bad though, it takes a lot of memory. I'll keep my fingers crossed for a fix.


  • Just an update, build 4657 does not fix the Ivory menu problem. Still cannot load any Ivory patches. Don't know if this is on the buglist, but since Synthogy has washed their hands of the issue, I'm still in hopes that something will be resolved. :)


  • Update:

    -Have tried Ivory 1.72 64bit and 32bit in Win7 64, Vista 64.... Same issue.

    -VEPro Build 4686 still does not fix the GUI issue.

    -Have sent another pleading request to Synthogy to look into it.

    -Am asking for any advice from VSL

    Thanks


  • Good evening from Germany... I have the same problem with ivory. vista 64,VEPro Build 4686, the stand alone ivory and ivory Cantabile are working without problems ivory in VEPro needs a lot of time and then no program or session file can be load all the tips from the homepage of synthogy do not fit... I hope for a soon solution, cause I love the ivory sound... best regards ray

  • Good night from Brasil. Having exactly the same problem with the same configuration. Maybe interesting to mention that all screencontrols are working except the ones to load a program, session or keyset. Maybe an iLok issue? Um grande abraço

  • This issue has been fixed for the next update. Thanks for reporting.