Vienna Symphonic Library Forum
Forum Statistics

182,955 users have contributed to 42,268 threads and 254,960 posts.

In the past 24 hours, we have 7 new thread(s), 14 new post(s) and 49 new user(s).

  • last edited
    last edited

    Hi noiseboyuk, 

    Too bad.

    Day #1 ðŸ˜Š

    Feel free to send those crash reports to support@vsl.co.at, best with a short description on how to reproduce, we´ll take a look. 

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Day #1 indeed :-)

    Does VE Pro auto generate crash reports, and if so where do we find them to send?  I'm pretty sure I wasn't connected to any host, and no obvious thing set it off, it was all very standard stuff.


  • Working with Reaper and Studio One.

    I have an issue with Ableton Live - the VePRO Plugin does not find the server and the window stays empty. Not sure if I am doing something wrong here since I am new to Live.

    Rewire support for the Server - i.e. connecting Reason on a slave machine would have been great. Or even better a VEP rack extension for Reason to be able to use VEP directly in Reason.

    One usability thing that I would like is that the midi port numbering is related to inserting a plugin. What I mean is that most users use multitimbral plugins - e.g. Kontakt - with VEP which need one port and several midi channels of this port. When I insert several Kontakt instances the Midi Port of VEP stay alway at the same number (number 1) and I have to manually change this portnumber to a different port after I inserted for example Kontakt. It would be nice to have some option setting so that VEP raises the port number with each inserted instance automatically.

    Although VEP is not intended as a DAW I would like to have an option to record the audio of the main out or even several outs to disc - maybe even with a metronome/click precount in the first bar. I use the standalone version of VEP with Reason and trigger VSTIs in VEP via midi. It would be great to be able to record the audio performance within VEP to be able to transfer the files later to Reason for mixing.


  • Hi noiseboyuk, 

    This is the crash dump location on Windows (also mentioned after every crash in the message that everybody clicks away):

    C:\Users\YOURUSERNAME\AppData\Roaming\VSL\Vienna Ensemble Pro\crashdumps\app

    => this folder is a hidden system folder, make sure that you see it: Organize => Folder and Search Options => "View" Tab

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • When I use my VST3 presets in Cubase to connect to my VEP instances Cubase freezes. 

    I can connect and discconect manually but the presets and the A/B function make Cubase freeze.

    please fix.

    Thanks for making it great!

     

    Windows 10 on all my comps. 


  • Thanks Paul, done!


  • I have another little bug and suggestion:

    BUG:

    Shifting through instances with keyboard (CMD+arrow keys on Mac), doens't work reliably. It works fine when shifting through instances with Kontakt in open state, but once you get to e.g. an open channel of Omnisphere, I can no longer switch to next/previous instance with the keyboard. Seems like Omnisphere takes control.

    SUGGESTION:

    Also, would be great to have a better progress bar during loading. Before I could see how far it was and could load up a Logic project when it was almost done and I know I would be ready to go soon. Now I really don't have a clue how many instances it has loaded since the GUI is not updated before everything is loaded.


  • Hi Paul.

    Problem for me is I saved almost everything as metaframes.  Saving projects will mean I have to rebuild metaframes from projects?  Do I need to go back to VEP5 and save all the projects from the metaframes?  I produce pop music pretty much (Universal Music USA and Canada) so many metaframes were similar with tweaks per song!  I'll wander around the software for a bit to see, but don't have tons of time to explore. 

    Thanks


  • Figured out that I could do it the old way by starting VEP with no instances and could recall the metaframes by calling up different projects from Pro Tools HD.  But new VEP6 doesn't see the slave machine.  Tried IP address and still no connect.  Guess it's time to look it up in the manual!


  • May have figured out the metaframe weirdness. Give me time, I'll probably figure out the connection problem