Vienna Symphonic Library Forum
Forum Statistics

183,200 users have contributed to 42,282 threads and 255,007 posts.

In the past 24 hours, we have 5 new thread(s), 21 new post(s) and 66 new user(s).

  • Hi
    I have set VEPro7 to auto run, so it start up at boot. 
    But the moment I click on the + icon, to launch a new instance VEPro7 crashes. When I relaunch I get the message above.
    So I have reinstalled, and now I get this:

    Image

    Image


  • Hi,

    This message tells that your Realtek ASIO driver has crashed. Also it indicated that you have started the standalone instead of the server version.

    In order to start the server version, make sure the hyperlink in the autostart has following value in target-field
    "C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe" -server

    This should start the server version on next boot.

    Best, Ben


    Ben@VSL | IT & Product Specialist
  • Hi Ben

    Thanks for your reply.
    It turns out that both Teamviewer AND Anydesk is a subscription service, costing a lot of money every month. That's to bad. I will try VNC.


  • last edited
    last edited

    Hi

    Excuse me for beeing stubborn. But now I have accomplished this:

    PCSlave boots-loads Server app 64 - load a set-up. Connection established from Logic on Mac Pro. It works!

    The moment I tries to create another instance in the VEPro server from my Mac using MRD , VEPro crashes, and I'm informed that a crash dump file is created and I'm asked to send it to you!
    VEPro seems to be the only app NOT working via a MRD connection.
    Hope you can find a solution, because MRD is very easy to use, it's free and the connection can be automated!

    Regards Stig Christensen MUSICMIND

    20200106-104800078-922.zip-1696338934851-x7arx.zip

  • Hi Stig,

    I've looked into the crash-dump and as I mentioned earlier it is related to a graphics crash. This is a known issue and something that we can't influence at the moment. Using another remote control software, and not RDP, will solve this crash. There are free versions of VNC available, so you could check these out.

    Best, Ben


    Ben@VSL | IT & Product Specialist
  • I'm here with the same issue.  The free versions of VNC still require a subscription and it is not a local LAN service.  VEP6 worked without issue with MRD, and now I just upgraded to VEP7 and my PC and templates are unusable.  I would think this would be an incredibly urgent issue that would affect a very large percentage of your users.  When can we expect this to be fixed?

    Alternatively, can I get my money back and reinstall VEP6?  Thanks.  


  • I'm using VepPro7 right now over MS Remote Desktop with 3 simple instances, not a big project, but working fine no crashses so far.  Admittedly I haven't been using a slave really much so maybe if I use it enough it will crash, but anyway if there are some graphics bugs somewhere, I am more inclined to think thats related to a specific plugin.  Can you provide any more details about EXACTLY what you're doing and what you ahve setup when you get the crashes?  what version of OSX, windows and remote desktop?

    Also please tell us your remote desktop settings and your screen resolution settings on both computers.

    Regarding VNC.  There are free ways to do it.  I don't use VNC because Remote Desktop is so much better then VNC in terms of responsivness.

    For VNC you need to run two things.  One thing has to run on your Windows box to host the VNC server side.  Then you run a VNC client on Mac in order to connect to it for viewing.  There are lots of free and commerical VNC clients, google around.  Some are better then others an claim to be more repsonsive.  Any of them will work with the VNC protocol.  I think its even built into Safari believe it or not.

    But for the windows machine you need a VNC server, which is not included by default as it is on the mac.  There are a few of those.  Here is a free one:  https://www.tightvnc.com/licensing-tvnserver.php

    Note, that setting all of this up and getting it running is probably not for the faint of heart.  I've never actually tried it on windows.  But anyway, there are free alternatives, its just a PITA to setup...and....no matter what you do it will never feel as responsive as MS Remote Desktop.  VNC passes your full graphics back and forth across the network, which if you're using a large resolution will feel laggy and is using network bandwidth also.  Remote Desktop is much more lightweight and sends more like internal windows commands back and forth (and some graphics), so that a lot of the window rendering and such doesn't have to pass so much stuff over the wire.  But that is probably why it runs into compatability issues occasionally.  I have had problems with a few plugins like PlogueBidule and a couple others that would crash VePro, or not display graphics properly when used inside RemoteDesktop.  But a lot of other stuff seems to work fine.

    Right now for testing I'm using Harmor and kontakt, no problem, no crash.


  • It's not a plugin issue.  VSL support has confirmed: "Sorry, this is just how it is and we can't fix it - because it is "not a bug we need to fix", it's an OpenGL problem."

    They recommended to use AnyDesk which costs $11 a month for one slave or $20 a month if you have more than one slave-unless you want to lie to the company and claim that it's for "personal use".  

    I have not yet found a VNC option that is free for commercial use.  This is really disapointing that VSL seems to be the only program that crashes MRD and yet, they say it's not their issue. Really bummed about this.


  • ok, but its not crashing here FWIW.  That could be a specific plugin perhaps using openGL?  Or what mode in VePro is using openGL that I can get it to crash here?

    I didn't check all the various VNC products, but VNC is basically an open source technology and I find it hard to believe there is not a free VNC server somewhere.  I'm not too motivated to look for it right now though because RemoteDesktop seems to be working fine for me.  If I start having problems with it I might revisit that later and have more info about it at that time.

    Solutions like AnyDesk would be orders of magnitude easier to adminstrate as they have basically bundled up the server and the client of free VNC technology into an easy to use product and of course they want money for that.  For real "commerical use" is $20 a month unreasonable?  Maybe not, though it probably gets under your skin and I don't blame you, but if you don't want to subscribe, then look around for a freely available VNC server that runs on windows, I saw half a dozen when I did a google search a few hours ago.  Surely one of them must not be tangled up in some kind of commerical use clause, but never know.


  • first server I found, tightVNC is free for personal and commercial use:https://www.tightvnc.com


  • By the way, openGL is being deprecated by Apple.


  • Tightvnc doesn’t work on a Mac. Again-it’s not plug-in related. Trying to open VEP7 through MRD gets an error message that you need to close and reopen the remote server. If you do that and then click + to create an instance VEP immediately crashes. VEP7 works fine loading the full project on startup (without MRD) but as soon as you go in and try and add an instance or disable/enable instance through MRD the program crashes. Do you have a Mac master and a PC slave? If so please try and start VEP7 (a new project) through MRD and let me know if it crashes when you try and add an instance.

  • So far I’ve looked at tightvnc, realvnc, anydesk, and teamviewer. They all either cost money or don’t work on Mac. Imagine if VSL switched to a subscription model out of the blue and now you needed to pay $20 a month to use the product. I don’t think it’s unreasonable for me to not be happy about this situation-especially since I didn’t know there was this issue.

  • last edited
    last edited

    @Another User said:


    Do you have a Mac master and a PC slave? If so please try and start VEP7 (a new project) through MRD and let me know if it crashes when you try and add an instance.

    Yes, mac master and PC slave.  Does not crash.  I jsut created three instances, loaded up an instrument on each one and made sound over on LogicPro.  Working fine.


  • I understand your frustration though.  If it wasn't working for me on Remote Desktop I would probaly be making a lot of noise about it also as I find VNC appalling to use and I most definitely do not want to have to pay a subscription to use one of the easier commerical alternatives such as AnyDesk for this purpose.

    Which version of WIndows and OSX are you using?

    I vaguely recall a while back there was some broken stuff in Remote Desktop with certain version of windows, but I don't remember the details now.


  • Here's another useful article that includes how to make use of VNC client on mac

     

    https://www.tweaking4all.com/os-tips-and-tricks/macosx-tips-and-tricks/best-vnc-client-macos-x/


  • when you try and start VEP through MRD do you get the error message pop up saying that the Remote Desktop needs to close and you need to log back in? Interesting to hear that you can mix and match clients/servers. In case you missed it-my setup has been working fine for a long time with VEP6. My MRD settings haven’t changed-it’s just a simple direct LAN connectionusing a direct Ethernet cable between the two computers on a 10.0.0.0 subnet. Getting on to the slave, opening other programs, etc, all works just fine through MRD. Again- I’m surprised and intrigued to hear that it’s working for you because VSL has basically told me that it’s a known issue and they won’t do anything about it. Sorry for any typos-I’m on my phone in the green room at a gig :-/

  • last edited
    last edited

    @Another User said:


    In case you missed it-my setup has been working fine for a long time with VEP6. My MRD settings haven’t changed-it’s just a simple direct LAN connectionusing a direct Ethernet cable between the two computers on a 10.0.0.0 subnet. Getting on to the slave, opening other programs, etc, all works just fine through MRD. Again- I’m surprised and intrigued to hear that it’s working for you because VSL has basically told me that it’s a known issue and they won’t do anything about it.

    What you are quoting from VSL I don't know the context to really comment about it, but I  know VePro is using a third party graphics library, a very popular and well established one, but still, in some ways its out of their hands if there is actually some kind of OpenGL problem, but personally I don't find that to be a reasonable explanation, maybe someone made a guess at that being the cause and they don't know what to do, but if VePro is dependent on OpenGL and if that is a problem, then it shouldn't work for me either.  But it does work for me, I haven't really had any kind of problem with it, but I haven't been pushing it to the limit either.  I only setup my older windows box to host a few odd windows plugins that aren't on the mac (Harmor, etc)..and might host some kontakt instruments that don't require a seperate dongle.

    A lot changed in VePro7, including they upgraded that third party library.  Ok.  But again, working ok for me.  So in order to figure out why its not working for you, we would need to pretty much look at every single setting we can think of between OS versions, remote desktop version and settings, etc.  and try to see what might be different.  Could be network settings too.

    I am willing to bet that if you get an OpenGL test app and run it on your windows machine it will not crash MRD.  Could be wrong.  But again, if VePro is using OpenGL...and i'm not sure it would be, its not impacting my setup.

    Another factor is that I have a GPU with metal, on Mojave.  If you're using an older mac with older OSX and no metal GPU, maybe its possible that caxuses things to use OpenGL instead of Metal or something, which might explain why it works for me but not for you. (shrug).  I'm guessing wildly now.