Vienna Symphonic Library Forum
Forum Statistics

201,360 users have contributed to 43,243 threads and 259,254 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Extremely slow loading times in VEP while I'm moving my old template
  • D
    D

    A little update, if I press play on Reaper everything keeps working again. If I disconnect and re-connect the main plugin everything go to hell again.

    There must be something concerning the communication between Reaper and VEP.

     

    EDIT

    Further testing shows me that if I go to start audio engine everything goes to work again, till the next connection where it loose everything again. So I need to click on the audio engine button everytime.

    Another thing I noticed is that when I put the play cursor perfectly aligned with a note (quantized with the grid) the note doesn't play, I always have to put the play cursor before the note to hear a sound.

    It doesn't happen with an instance of Kontakt loaded directly in Reaper....
  • PaulP
    VSL Team
    PaulP

    Hi Daniele, 

    Sorry for the delay, our development team is already working on a solution with high pressure. 

    Until then it will make sense to roll back to VE Pro 6. 

    Thanks for your patience, it's unfortunate that some bugs will always pop up with a new version of such a complex software. But we will fight through it! 

    Best, 
    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • K
    K
    last edited
    last edited

    @DANIELE-ES said:

    I'm not having such issues with the initial release.

    To clarify, with initial release you mean a previous VE Pro 7 release, or VE Pro 6?

    Thanks.
  • D
    D
    last edited
    last edited

    @Paul said:

    Hi Daniele, 

    Sorry for the delay, our development team is already working on a solution with high pressure. 

    Until then it will make sense to roll back to VE Pro 6. 

    Thanks for your patience, it's unfortunate that some bugs will always pop up with a new version of such a complex software. But we will fight through it! 

    Best, 
    Paul

     

    Hi Paul, thank you for reply. I'm happy to hear that you are working on it. I hope to solve all my problems.
  • D
    D
    last edited
    last edited

    @DANIELE-ES said:

    I'm not having such issues with the initial release.

    To clarify, with initial release you mean a previous VE Pro 7 release, or VE Pro 6?

    Thanks.

    I meant the intial release of VEP7.

    I tried VEP6 a little right before the release of VEP7 and from what I could try it works well. Right now I'll wait for this fix to come hoping that this will not require too much time.
  • D
    D

    Here's a GIF where I show you the unresponsive UI problem: https://drive.google.com/file/d/1pOXYQ4Xu8_EjTq4CgaOmVbb3cU7IQkWu/view?usp=sharing

     

    Maybe it could be useful for the vsl guys. You can notice that when I click on ui buttons to show the mixer or the performance window etc...the ui not respond, you could also notice that if I minimize the window the UI works.

    PS it seems that with the last update (7.0.807) the "not playing first note on play cursor" problem is fixed.
  • D
    D
    I did some more testing and I noticed that when I play and stop the test instrument I obviously hear the release tail, if I go from Reaper to Vienna this suddenly stop to restart again when I came back to Reaper.
     
    The problems I talk about start when I stop playing in Reaper and I focus from VEP to Reaper, as if the connection were unstable or interrupted when switching from one window to another. I also tried all the settings for the plugin inside Reaper but nothing changes.
     
    In order:
     
    1. I hit play in Reaper;
    2. While the track is playing I focus VEP and the instruments UI works fine;
    3. I stop the track while I'm still in VEP focus, the Kontakt GUI keeps working fine;
    4. I came back to Reaper and I keep hearing the release tail of the instrument;
    5. I focus VEP again and the sound and GUI stop working;
    6. If I focus back to Reaper I start hearing again the tail sound;
    7. From here is VEP -> Sound stops - Reaper -> Sound resumes and so on until I press play and start the process again.

    This happens both with VST and VST3 version of the plugin.

    Maybe it is a simple configuration problem in Reaper or VEP or both...
  • D
    D

    I think I finally found the reason for this behavior.

    Here's how to reproduce it:

    1. Create 1 track in Reaper for the main plugin (VST or VST3 is the same);
    2. Create 1 track for the Event Input plugin;
    3. Link everything to a VEP instance with some kontakt libraries loaded in.

    Here we are, if every "Record ARM" button is disabled then you will have this problem, if one of two tracks has this button enabled the everything will works fine.

    So in my template I obviously put off all of my arm buttons, this is why I had this problem.

    Uff...well, now is your turn VSL, I don't know if it is a bug or it is intentional but I think I shouldn't be forced to have all of my VEP main plugin tracks armed.

    Also I'd like to remember you that VST3 plugin is still unusable because of the slowness of loadin and viewing time. This is not only a problem of mine and I know (and hope) you still working on it.

    I'll keep you updated if I find something else. I hope now you could work faster to solve this issue.
  • PaulP
    VSL Team
    PaulP

    Hi Daniele, 

    Thanks for your efforts. Just so that other forum readers know: We also get these reports via mail, and our developers are on it!

    Best, 
    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • D
    D
    last edited
    last edited

    @Paul said:

    Hi Daniele, 

    Thanks for your efforts. Just so that other forum readers know: We also get these reports via mail, and our developers are on it!

    Best, 
    Paul

    Yes yes, since a developer contacted me about the case I thinked it was right to keep him updated to help him find faster the cause, so I tried to keep updated both this thread for other people that are reading this and the email for developers only. I know maybe it is a little redundant but it is also useful.

    Thank you.