Can someone with PLAY and Logic check something here - Larry, you still there?

[RiffWraith]

Glad to be doing this again - good job with the deletion! http://images.zaazu.com/img/clap-animated-animation-clap-000340-design.gif



There is a memory issue with PLAY, happens in Cubase and Sonar, and wanted to see if Logic experiences the same thing. Can someone with Logic and PLAY kindly try this?

Boot DAW
Launch Cubase/new blank cpr
RAM usage at 212 MB
Load an instance of PLAY
Load a bunch of instruments
RAM usage at 1.02 GB
Save and close

Boot DAW
Launch C4/open previous project
RAM usage at 1.67 GB (should be about 1.02)
Unload PLAY from the VST rack
RAM usage at 886 MB (should drop down to about 212)
Save and close
R-open
RAM usage at 212 MB

-------

Of course your RAM numbers will be a bit different, but if you do in fact have the same problem, the basic idea will be the same.

I would like to send another report to EW soon, so please check this if you can.

Thank you!

[D]

When you delete the play instance, the same amount of RAM is released: 0.8 GB. How are you measuring your RAM usage?

[Animus]

[takes a bow]

[RiffWraith]

When you delete the play instance, the same amount of RAM is released: 0.8 GB.

Right - the same amount of RAM is released, but the problem is too much RAM is being used when the project is loaded the 2nd time. So, when the same amount of RAM is released, that means there is still too much loaded.


How are you measuring your RAM usage?

CAD

[D]

Right - the same amount of RAM is released, but the problem is too much RAM is being used when the project is loaded the 2nd time. So, when the same amount of RAM is released, that means there is still too much loaded.

Indeed it does. But what process is using that extra RAM? IOW, does the same thing happen when using the Kontakt engine? It might not be the VSTi software that is causing the problem is what I am getting at here. ;)


CAD

I have been known to be a cad from time to time, but in this case I am sure that I have absolutely no idea what you're talking about. :D

[RiffWraith]

Indeed it does. But what process is using that extra RAM? IOW, does the same thing happen when using the Kontakt engine? It might not be the VSTi software that is causing the problem is what I am getting at here. ;)


Does not happen with Kontakt 2/3, Ivory, Atmosphere, RMX, Zebra, or Hypersonic. PLAY only. As for what process is using that extra RAM - PLAY is.

CAD = Ctrl Alt Delete

[Bman]

Hi. I read your post with interest and thought I'd try it myself in cubase, however I don't notice any significant difference in RAM usage after re-launching. However I am running PLAY on a slave computer running XP64 via FX-Teleport so perhaps having PLAY 64-bit in a 64-bit OS (although FXT is 32-bit I think) might be making the difference. My Master computer is running Cubase under XP32.

Of course, I'm still stuck with inordinately long save times so PLAY isn't an entire winner for me yet...

Brett


Glad to be doing this again - good job with the deletion! http://images.zaazu.com/img/clap-animated-animation-clap-000340-design.gif



There is a memory issue with PLAY, happens in Cubase and Sonar, and wanted to see if Logic experiences the same thing. Can someone with Logic and PLAY kindly try this?

Boot DAW
Launch Cubase/new blank cpr
RAM usage at 212 MB
Load an instance of PLAY
Load a bunch of instruments
RAM usage at 1.02 GB
Save and close

Boot DAW
Launch C4/open previous project
RAM usage at 1.67 GB (should be about 1.02)
Unload PLAY from the VST rack
RAM usage at 886 MB (should drop down to about 212)
Save and close
R-open
RAM usage at 212 MB

-------

Of course your RAM numbers will be a bit different, but if you do in fact have the same problem, the basic idea will be the same.

I would like to send another report to EW soon, so please check this if you can.

Thank you!

[D]

Does not happen with Kontakt 2/3, Ivory, Atmosphere, RMX, Zebra, or Hypersonic. PLAY only. As for what process is using that extra RAM - PLAY is.

CAD = Ctrl Alt Delete

CAD = Task Manager, that is the name of the program. That still is not telling me what process is using that memory, and simply stating it's PLAY is not entirely convincing, although it would not surprise me if you were correct, either. I don't have PLAY, so I can't be of much additional help without going what might turn out to be spending a lot of time spinning wheels.

Good luck.