Wow, so many fixes, you guys are amazing!

Thank you!

VEP 5 v5.0.9687 on Win7 x64, when I double-click any viframe64 file it opens a blank instance of VE, the only way to properly load a viframe64 is run an instance of VEP5 (not server) and Open Project from there. It's a slight annoyance but got me scared until I figured out the workaround.

I searched through the forums so I hope I'm not double posting.

Wanna see the changelog for this verion, current one is for September release.

PLAY v3.0.25 just appeared on EastWest website. A bunch of WordBuilder fixes and some other tweaks but not a word about loading probs. I'll be testing it out tonight and will report back.

UPDATE: Gave this version a try but there's no change in loading, still the same behavior.

+1 for a powerful server, the faster the CPU on the server the lower you can set your latency without any audio artifacts occurring.

I'm aware of decoupling & proper loading techniques and whatnot. What I'm reporting here is that there is a problem with Play v3.0.15 that wasn't there with Play v2.1.2; recent changes that were made to VEP seem to work only partially.

Around 6 GB without Play, ~5.7 with Play. RAM was never an issue here.

As suggested, tried complete reinstall of VEP on all machines and still get the same issue.

Bosi is definitely larger, around x2 the size but Yamaha loads in ~ 5 seconds when Bosi can go for 5 min. When loading Bosi directly from Play interface it'll take around 10 sec but when loading previously saved ProTools session it'll either be super slow or get stuck. As I mentioned, some patches are OK and some aren't.

I've noticed that some Play patches load lightning fast but some load either extremely slow or will halt to a stop. For example I'll make a ProTools session with 64-bit VEP server on another Win7 x64 machine and load any Bosendorfer grand patch. When reopening the session it'll load for ages and occasionally stop altogether. If, however, I try reopening a session with Yamaha C7 patch in it, it loads VERY fast.

After some more testing I'm still having the same issues as before with my setup (details in my sig). I'm unsure if its specific instrument presets that cause it. I did a clean Play install just to be sure. Created brand new template - same thing. Anyone else with ProTools on Win7 having these issues?

It's faster than before but still much slower than Play v2.1.2

Loading time is still terrible with PLAY v3.0.21 and the loading message window steals window focus every time a new sample is loaded. I hate PLAY with all my heart now.

I can confirm there are issues with Play 3, in fact I just tried the updated v3.0.21 (VEP version is 4.1.8008) and still the patches load for ages or will stop loading altogether. Don't know if its a VEP issue as I don't use Play with anything else.

I would still suspect a defective ram stick. I've had numerous times when all ram tests wouldn't report issues but it still turned out to be bad ram. Try leaving only 8 GB of ram and changing ram sticks one by one until, hopefully you spot the one causing the crash.

Is this a serious question? If yes, Wi-Fi is VERY limited, no way you can efficiently do what VEP needs to do.

I support this idea!

Problem with 32-bit environment is that the allocated RAM space has to be shared among all 32-bit apps. As you mentioned, there might be a way to create a separate, virtual ram space but it may involve licensing VM code or developing new code from scratch. By the time it works the VI's may already be available in x64. I hope I'm wrong though and that it's fairly easy to implement cause this is a great idea.

So what's new in 7644? Changelog is old and I'd really like to know what's under the hood before installing.

Hi Karel, I bring sad news, the behavior described in OP is still there (with or without OC) just doesn't happen often but eventually any opened ProTools session with VEP in it will die. Other people are having this issue as well. Please, let me know if I could be of any help in finding the root of this issue.

I finally have good news to report on this as I found the root of the problem. The slave machine I was streaming audio from was overclocked and was not so stable as recent stress testing showed. I fine tuned the settings to have a very stable clock and cool temps and so far I've had zero issues. VE Pro is exactly what I needed and now that this is sorted out I'll go get myself a copy. Thanks for your input Karel!

The new VE PRO 4.0.6150 update still produces the same issue. My demo is running out in less than 10 days and don't have a stable setup. Please, let me know if it's a know or a new bug and is being worked on, or is it an isolated case?

I ran a bunch of tests and the only solution to prevent ProTools from throwing the RAM errors (and crashing shortly afterwards) is engaging the "Decouple" feature from the plug-in interface. Nothing else works. Note that saving the session doesn't take long at all so it's not necessary to use the feature in this case.
It has to be a bug of some sort cause no other plug-in in ProTools ever caused this sort of behavior in my experience (unless ProTools has exceeded the 32-bit memory limit which is not the case in my situation). Please, let me know if you need help reproducing the crash or need more info on this issue.
Here are the snapshots of the errors that ProTools shows:

Yes, the network is fully gigabit equipped and all connections are Cat7 cables. All computers have gigabit cards and work as expected. I went through the tweaks described in this post http://community.vsl.co.at/forums/t/25673.aspx but don't notice any changes. I'll try some tests using Reaper as the host to test the network. If there are any tips at this point, please, let me know.

I'm currently trying out VE PRO on ProTools HD 8.0.4, Win7 x64. I really like the concept but here are the issues I'm having:
When streaming audio via LAN ProTools at some point which is pretty random throws all kinds of errors like it's running out of memory. When streaming audio from localhost (same machine Protools is on) everything is normal. I tried the build 5436 and the BETA build 5814 and still get the same thing. Looked through the forums and did not find anything helpful.
Please, if anyone has any tips for me or if it is a known issue, please, let me know.