We are not sure if this is a bug,  or is a "works as designed" or rather a "technical support request". That's why we choose to post it here before going into a support ticket scenario.

Running a Vienna Ensemble Pro 7 Server 64bit on a quite powerful studio machine which handles big score Pro Tools sessions on a daily basis (VEP newly installed) freezes temporary (getting greyed/whited out) after clicking "save server project". And the time it keeps freezing extends as more tracks are involved. Having a template of a full string section ready in only one instance (with MIR pro), saving takes over 5 minutes which feels too slow for me, since everything here runs on SSD and NVMe SSD inside the box and saving a 600k veps64 file can't take such a long time.. In this time there is nothing you can touch on it and it has this (not responding) in the title of the app window. No other programs are open and the Server isn't connected to any DAW yet and holds only one instance.

This smells fishy to me. Especially the greying out and that CPU load raises to 12%? By saving a preset file? I know from many projects that we have run lots of not user friendly loading times in different scenarios in our facilities, so my worries are not caused by not knowing that big thinks take long to load in the professional area. Our render farms take hours for film rendering. But in this case it seems not in the right proportion (ratio of loaded tracks and save time). I am not able to create and finish an orchestra template since days because of that.

Is this an individual use case or is this a known issue or do I miss something here? All ideas and help would be much appreciated since we still are not able to start the set ups we need here in this new facility.

Thanks in advance and all the best.

Well ... no difference, Apart from that I found out that happens also by such global tasks like "disable all samples" ... it freezes for many minutes ...