Vienna Symphonic Library Forum
Forum Statistics

180,742 users have contributed to 42,140 threads and 254,362 posts.

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

  • VE Pro takes forever to load

    Hello, I have had this problem since upgrading to VE Pro 5. I have 5 VE Pro servers running on 5 different PC. Every morning I switch on the 5 PCs, load the metaframe files, and then switch on the DAW. They usually start up nicely, but 3/10 times they would all get stuck at loading the Metaframe files, I had to eventually force quit them all, re-launch all VE Pro, reload all Metaframe files, and they all would load again. any advice please?

  • Personally I would decouple all your slaves and run them as standalone VEP's. The convenience of having all the metadata saved with the sequence was eventually outweighed for me by the speed advantage of leaving them all separate. It also speeds up the save file proceedure in your DAW which emans you are more likely to do it more often! (I am Mac Pro + 4 VEP slaves)


  • To the OP ......... I hope this is not a hijack of your thread. If so please let me know and I will take it out. I just wanted to get flashman's opinion because I have the same issue of slow loading...only in the slave.....and I am new to this.

    Flashman can you, or anyone, explain this better for me a beginner?

    I have problems with Pro Tools running out of CPU with 1-3 VI's. So I thought to use my MacBook Pro as a server for VI's using VEPro.

    So I guess I then open an Instrument track in Pro Tools and select VEPro....in the Master computer with the DAW. Then I open VEPro Server 32 or 64 in the MacBook Pro and connect via ethernet. Is this correct? I would open the application and put what VI's I want in those channels? 

    Is there a better way to do it?

    Also, I guess this means I also have to have all the sample libraries I want to use in the slave also or by FW drive. I have a backup of my samples libraries on a FW drive already. Do I have to have the actual applications of each software in the slave also.

    So if I use Symphobia.......... my library of samples is in the master, internal drive.....and in FW drive. But the Project Sam/NI/Kontakt 5/Symphobia application itself is only in the MacPro master.

    Will that work?


  • We're having the same issue, but with VE Pro Standalone. We have 3 slave PC's with Windows 7 Pro 64bit and 1 slave Mac Pro with OS X 10.8.2, all running VEP 5.1.12010, though the issue started before the latest VEP update. We use ipMidi to send midi, and each computer has an RME HDSPe Raydat card for audio output. Each template is set to load automatically on boot-up, with various VI pro, Kontakt, and EW Play instruments loaded.

    Most of the time, the metaframes load with no issue, but every once in a while, all of them will hang before loading anything. It seems to happen mostly after they've been off for a while, such as Monday morning after a weekend. We'll reboot or shut down and restart, and they will load with no issue. It's happening on both the Mac and the PC's, so there's no single program or setting that would be interfering with the loading process. Since it only happens once and then loads normally for days, there's no easy way to troubleshoot the issue.

    Attention to this issue from Vienna would be very much appreciated. Thanks!


  • Same issue here since 2-3 builds ago. I raised the issue in multiple threads but no answer from the VSL people...

    Like you, it happens seemingly randomly that VEP simply freezes on beginning to load the metaframe. It usually happens on all the machines on my network or none. One Mac Pro, two PC's in my case. It is annoying because I need to have an eye on my slaves and log onto them via VNC and force quit the app and reload it again to get moving. It is managable but still annoying and obviously they must have changed something 2-3 builds ago that causes this.


  • Bump. Is this issue being looked in to?


  • OK now I see exactly what you mean. Just building a new template and wondered where half the instruments had gone. Then looked at activity monitor and watching the memory useage very very very slowly creeping up. Most of my stuff is kontakt 5 so it maybe a K5 problem as well?

    *bump*


  • last edited
    last edited

    @HighwayChile said:

    the application itself is only in the MacPro master.

    Will that work?

    No, the application needs to be connected to the machine with the VE Pro server in order to be seen.


  • last edited
    last edited

    @flashman said:

    OK now I see exactly what you mean. Just building a new template and wondered where half the instruments had gone. Then looked at activity monitor and watching the memory useage very very very slowly creeping up. Most of my stuff is kontakt 5 so it maybe a K5 problem as well?

    I'm pretty sure it's a VEP issue. While many of our instruments are also K5, one of the machines is only running EW Play instruments, and it hangs as well. I'm not sure that your issue is identical, though, since on our end, nothing is loaded, it just hangs when it starts loading the first instance. If you hit cancel (in K5) it will start loading the next instance, though we usually just restart the computer to get it to load everything properly.

    I can also confirm after further observation that it indeed consistantly occurs after not running the machines for at least 24 hours, though it's not limited to Mondays.


  • ISSUE SOLVED! In a recent update to VE Pro, Vienna added an option to automatically check for updates. Apparently, this process was causing the template to hang when loading automatically on start-up. Oddly enough, on two of our three PC's, the version we were running (I neglected to note of which version it was) didn't even have the option of disabling the auto-update. I updated all instances, Mac and PC, to the latest version, VEP 5.1.12010, disabled Enable Automatic Update Check, and we haven't had any hangups on loading since! (That would also explain the regular timing of the hangups, as well as the fact that it was occurring on all computers, both Mac and PC, at the same time.)

    Hopefully, someone at VSL will take note of this issue, and either fix it or address it in the release notes.


  • last edited
    last edited

    Hi kkmusic_6722,

    I don´t know what needs to be fixed, and we mentioned the possibility to disable the automatic update check in the Changelog (VE PRO 5.4.12010 in February 2013).

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • Hi Paul,

    It seems that having auto-update enabled, as it was by default, was causing all of our slave machines, which load VEP templates automatically on boot up, to hang before loading any of the template. The only solution was to force quit VEP and launch it again, or restart the computers. As I wrote above, this was happening on both Mac and PC, and it was occurring on all the computers at the same time, periodically. Clearly, something about the auto-update process causes this. If I had to guess, I'd say the computers, having just started up, had not yet established an internet connection, and were waiting to get a response from the VSL server, without the query ever having been sent anywhere. But that's just a hypothesis on my part.

    In any case, since disabling auto-update solved the issue, we're more than happy to continue updating manually, and stick with a stable release until we decide to make the jump.