Hi,
I was investigating a bit the behaviour of Play with memory (looking for something like the Kontakt memory server which addresses memory outside the host application) and I've found this post in the KonledgeBase of Soundsonline:
"If you are using PLAY as a plugin inside a sequencer host on Mac, then you are already accessing RAM outside the host.
While using any plugin in a 32 bit host on Mac, we are still limited to the host's addressable space of 3-4 Gb. However with PLAY we use a 64 bit daemon that loads samples outside of the host's address space. This daemon loads the prime buffer (the portion of the sample that's loaded into ram, not the portions that are streamed directly from the hard drive) of each instrument loaded. However, there are still parts of the instrument that are being loaded in the host's 32 bit address space, such as effect settings, articulations being used, and so on. This 64 bit daemon process is always running in the background when you instantiate PLAY, so there is no need for the user to do anything other than load instruments as normal."
https://www.soundsonline.com/support/in ... ticleid=75I've not seen any deamon or any memory used outside Notion.....
According to another thread in soundsonline forum (
http://www.soundsonline-forums.com/show ... hp?t=23950 ) It seems the the external memory is used only when the addressable memory limit is reached by the host application: this doesn't seem to be a good strategy because when the host application reaches this limit it usually crashes (Notion, Logic).
Using something like Plogue Bidule could maybe solve the problem ? And if are using another hosting 64bit apps are we goingo to loose preset/rules for EWQLSO ?
Thanks
GF