200,858 users have contributed to 43,214 threads and 259,138 posts.
In the past 24 hours, we have 2 new thread(s), 6 new post(s) and 61 new user(s).
When, on Mac, it starts to go slow, either you have bad memory stick, either you starts to use VM because you have a lack of physical memory !
I don't know about Windows, this could be something to check
Is the Bosendorfer patch much bigger than the C7 patch ?
Can you look at memory occupation ?
is 5.7 Gb without the piano loaded ?
How much memory left with the bosendorfer loaded ?
With W7, can you monitor memory during the load ?
If you are having PT load it, or with any host coupled with VE Pro, that can happen. Have you never found other loading to be significantly slower than loading it in VE Pro first and then connecting; or have you never done decoupled sessions?@gen0use said:
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.
I can confirm this behavior. I tried several of the EW Pianos and they all behave this way. The Kontakt stuff loads lightning fast, then it gets to Play and it chugs like a snail.
I'd say it'd take a half hour or more if I waited, but what I've been doing is abort the load, let everything else finish, then once the Cubase project is open simply add the piano to the Play VSTi that is already present in VE Pro. Then it loads at normal speed.
So something is happening with Play 3.0.15 that causes it to load slowly while the project is loading, but can be added afterwards with no problem.
So something is happening with Play 3.0.15 that causes it to load slowly while the project is loading, but can be added afterwards with no problem.
Yes, a workaround is to load whatever Play sounds are in your project first BEFORE you load your DAW project. Then, the DAW (say, Cubase) project loads lightning fast, even though it loading a separate, new instance. For some reason, separately loaded Play sounds load perfectly fast, and then the in-project instance must be optimized to use the same samples that are already in memory. That's my theory.
Yes, after upgrading to 8861 and to PLAY3 to re-test this, I simply can't load any project with preserved and coupled instances containing PLAY. It takes forever!
It the instance is decoupled then the VEP metaframe can be loaded prior to loading the cubase project and everything seems to work fine.
I don't know what the hell is with EW and PLAY. Nothing but problems here....(sigh)
@gen0use said:
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.
Thanks for the report.
