Vienna Symphonic Library Forum
Forum Statistics

184,538 users have contributed to 42,365 threads and 255,344 posts.

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

  • Issue with Mir Gui

    Not sure what is happening with gui in VEP/Mir. I just updated Mir to Vienna Konzerthaus RoomPack 2.0.259 ; Mystic Spaces RoomPack 2.0.119  and VEP5 to Vienna Ensemble PRO 5 / MIR PRO (Windows) build 10370
    I am using Win7 64bit- Cubase 6.5, i7 950 12gb ram
    Attached is screenshot of what I am now seeing, can you let me know if I can correct this to see stage view of Mir again? Or any clues as to what I have done wrong?

    http://www.flickr.com/photos/55372850@N08/7061112395/


  • Also here is video of MIR on desktop

    http://www.flickr.com/photos/55372850@N08/7061223233/in/photostream


  • Sorry to see that you're facing problems. Of course thats not the intended MIR Pro GUI.

    Just to restrict the set of possible influences: What happens when you start VE Pro / MIR Pro as a stand-alone application on this system? Same situation?

    Kind regards,


    /Dietz - Vienna Symphonic Library
  • Hi,

    "Just to restrict the set of possible influences: What happens when you start VE Pro / MIR Pro as a stand-alone application on this system? Same situation?"

    I did not have the issue in standalone just now...I hate to complicate things but :) it doesn't happen all the time. It happened the first time when opening a older project. This time MIR was working great but when I merged current project (had flute-piano-vibes etc) with a trumpet/sax patch I got the problem you are seeing. I am sorry to admit  that issue is intermitant lol

    Do you need any info from system which may help you?


  • I think the specs you provide in your signature should be sufficient (it's the Windows-machine, I assume?) - the only info missing at the moment are the detailed specifications of the graphics card. It might be that you're facing an OpenGL-related issue.

    ... a wild guess: Does the graphics card use shared memory? What was the RAM usage when you were seeing the problem?

    Kind regards,


    /Dietz - Vienna Symphonic Library

  •  Windows machine yes (64bit win 7)///Video card is NVIDIA GeForce 9800GT. Per specs openGL 2.1 supportpretty sure the 9800gt doesnt support shared graphics memory but I can check bios if needed.  Computer ram usage at time of problem is 7.8gb used, ram amount  is 12gb. Virtual Ram is set  for 12gb. I am going to update driver to eliminate that as issue.

    Thanks


  • Thanks, Kenny - I will ask VSL's software engineers to take a look at the issue.


    /Dietz - Vienna Symphonic Library
  • Thanks Dietz, look forward to hearing back. I looked through posts and ao far didn't see anyone else with this issue, if anyone else runs accross this let me know as we maybe able to trade info for solutions also.


  • Like I mentioned in another thread, this exact thing happened to me.  Ended up being a problem with Waves plugins being loaded in MIR Pro.  Waves uses OpenGL I believe.  When I removed the offending Waves plugin, graphics went back to normal.  Problem only cropped up because I wanted to see how the new VE Pro handled Waveshell support.  Apparently not too well.


  • Sorry to hear about your problems, and thanks for reporting. VSL's software engineers are aware of the issue already.

    Kind regards,


    /Dietz - Vienna Symphonic Library
  • last edited
    last edited

    @Animus said:

    Like I mentioned in another thread, this exact thing happened to me.  Ended up being a problem with Waves plugins being loaded in MIR Pro.  Waves uses OpenGL I believe.  When I removed the offending Waves plugin, graphics went back to normal.  Problem only cropped up because I wanted to see how the new VE Pro handled Waveshell support.  Apparently not too well.

    Which Waves plugins exactly cause the issue? This is not an issue with WaveShell hosting, but rather with Waves plugins not properly using their OpenGL context probably. Hopefully I can work around it.


  • It was C6 specifically.  I didn't try any others so it might be just that one I guess.


  • I've just fixed these issues for the next update of VE Pro 5. Thanks for the detailed report.


  • Now that's what I call service!  Good work Karel.