Vienna Symphonic Library Forum
Forum Statistics

199,404 users have contributed to 43,164 threads and 258,953 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VePro - build 4881 (Ok to use)
  • R
    R

    I don't think so.

    Two things.

    1.  All master and slaves had EXACT version/build of vepro installed (with 4881 on ALL machines - midi did not work.)

    2.  midi did not work WHEN only running VEPRO on  Master.

    Unistall update - rolled back to 4686 (again - ALL machines) - all midi communication work as designed.
  • civilization 3C
    civilization 3C

    I had the update installed on master and slave as well. I have only ever seen that in that build. Rolled back to official version, midi is fine.
  • R
    R

    Ok - I was starting to think it was just me. :(
  • K
    K

    Same Issue here. Also some interesting overload impact on the CPU's after a couple hours of operation. Old version works fine.
  • R
    R

    Hey info when you say 'old' are you referring to 4686?  That's the one that works here.  Thanks.
  • K
    K

    Yes, back to Build 4686. Works great again!
  • R
    R

    OK - same here - 4686 works as design.
  • J
    J
    In my 1 day experience 4881 is the best version yet... very good latencies also
  • R
    R

    Ah rats - I was AFRAID you would say that.   So wish the 'midi ghost bug' (at least on mine and a couple of posters here) gets solved so I can try it.  The latencies improvement is of course KEY.

    jvdieks - were you running Play before and can you still?   I am maybe one of the few who is successfull running Play on a farm unit in vepro - just want to be sure on 4881 hasn't changed that (I know the official position of VSL is that Play is NOT supported but....:)
  • J
    J
    no... i primarily use kontakt with it and a couple of other vstis... but i send my midi to the plugin version on the master.. I hardly ever use the normal midi inputs.. I noticed a big improvement when setting latency to 0... that's the main thing i like about this update.
  • O
    O

    Hi Rob,

    please allow me to chime in:

    You have PLAY running in VEPRO?

    How did you do that?

    Did I miss anything in a thread?

    That´s sensational!

    Thanx for response.

    Cheers

    Oliver
  • R
    R

    One Caveat - still crashes from 'time to time' - but for now (until Play Pro) - I can live with it.  Do a search on this board - there is a suggestion (forgotten how but I think it was login as 'administrator' (on PC).  Good luck (you mileage may vary.)
  • D
    D
    last edited
    last edited

    @Rob Elliott said:

    One Caveat - still crashes from 'time to time' - but for now (until Play Pro) - I can live with it.  Do a search on this board - there is a suggestion (forgotten how but I think it was login as 'administrator' (on PC).  Good luck (you mileage may vary.)

     

    Hmmmmmm. I haven't been able to get a usable GUI for PLAY for quite a few versions now. I'm convinced the problem is because of the way VE Pro embeds the GUI. The same problem occurs with PLAY and J-Bridge, which also embeds the GUI. I sense a pattern. [8-|]

    DG
  • B
    B

    I have big problems with 4881. Please see my post:

    http://community.vsl.co.at/forums/t/24476.aspx

    Thanks.
  • T
    T

    I have PLAY working in VE Pro on one of my PC slaves, but I've only use one instance of it for the piano. It's been stable without issue, unless I try to load more than one piano into it. I wouldn't even attempt to run more than one instance or even just one fully loaded instance. The more you have to access the Play GUI, the great the chances of a crash. 
  • F
    F

    What versions of Play and VE are you using?  I'd love to try it out.  Its hard to do a search for "play" in an audio forum so I figured I'd ask here.

    hah...found the helpful thread.   http://community.vsl.co.at/forums/p/22983/157469.aspx#157469

    f
  • B
    B
    In former versions of VEPro Play runned perfect. But since 4881 I can't use any button on the Play GUI. Like the ongoing K4 crashes this is very bad!!!
  • R
    R

    I was one of those folks (on 4686) that got Play to work in vepro - with 'occassional crashes'.   Well those crashes got to me more occassional so I have move my Play libraries to the Master (from farm) and life is a LOT smoother.
  • R
    R

    Still on 4686 here - all is working as it should.   Has anyone who posted on this thread that was having no midi communication on 4881 built now up and running?

     Just curious.
  • civilization 3C
    civilization 3C
    last edited
    last edited

    @Rob Elliott said:

    Still on 4686 here - all is working as it should.   Has anyone who posted on this thread that was having no midi communication on 4881 built now up and running?

     Just curious.

    I only ever saw that when - I think - there were some preferences from a much earlier version on the master machine conflicting with 4881 on the slave. One time only. That is no issue now, I've finished a number of projects with 4881.

    I do have an issue where I will add instruments which at some point will send no audio back to Cubase, which I don't understand. But eventually I get something to stick just thru sheer stubbornness.