Hmm. How about OS updates?


Oh..
And .NET updates?

Hi,

I have Cubase Essential 5 32 bit, Win 7 64 bit.
Baseline is 1.57GB in Taskmanager.
Clicked on Cubase without opening any project: 1.70GB.
5 minutes later: 1.70GB.

Try and upgrade the RME driver. RME had a new release none too long ago.
ttt

You found my weak spot, this system is not on any network so this is not even SP1.
Must have actively put that in the last corner of my memory, since this is a PITA.

Will burn a DVD with all that fine stuff from Microsoft...

But thank you for bringing that up. I've totally missed that.

C5.5.3, OSX.6.8. (rme card) opens at 107.1MB... after 5 minutes it has climbed to 107.6.
Last edited by jancivil on Fri Feb 17, 2012 12:57 pm; edited 1 time in total

Thank you for looking into this. 1.7 GB seems a bit much.
Everyone I talked to before was around 150 MB right after start.
Ok, Essentials might be a different animal altogether.



Was the first thing I did after updating the dongle driver.
But in all these years, there was only one minor hick-up with RME drivers...

updated the rme drivers, 'HDSPe series'... restarted. Cubase opened at 106.3MB...seems to add .1MB a minute, about.

Thank you for taking the time to have a look.

Albeit I'm writing this on a MBP right now, I never seen Cubase on a Mac in all these years. Funny in a way.

But 0.1MB / min would mean 6 MB / hour, that would not worry me at all, in case that would not increase during playback of a big project.

I have my current project loaded. the memory usage is not changing. hit playback and the usage went down by ~10MB.
yeah, I don't know to say about that. the usuage according to activity monitor keeps showing less now, after hiting playback.

I got it to jump up half a meg finally when virtual instruments kicked in (they are hosted elswhere).

all differences kind of neglible here.

I think that means Cubase was adding .13 GB to the usage overall.
Last edited by jancivil on Fri Feb 17, 2012 5:58 pm; edited 1 time in total

Its not something to do with Superfetch service? That uses RAM as a cache and frees it as necessery. It often causes confusion as it looks like your RAM is being used for no reason. You can disable it but it can affect performance :

http://mobile.osnews.com/story.php/21471/SuperFetch_How_it_W orks_Myths
Last edited by UltraJv on Fri Feb 17, 2012 3:19 pm; edited 1 time in total

I just tried loading Cubase 5.53 32 bit in Win 7/64 with no project, Echo ASIO and AlphaTrack drivers. Started at about 120 MB, and did not change at all after more then 35 minutes.

Don't have cubase 5 - but on 6 with an RME PCI card I don't get any memory changes with an empty project either

Could it be your midi devices drivers?? - even without a project running cubase has engaged the midi ports?

You are right, that is a mythical part for OS architecture today.
I have big fun with it on Mac OSX 10.6.8 every day, since reclaiming memory
from the cache seems to take some time there...

Nerver had an issue with it on Win7 so far.

But with the problem at hand the Cubase5.exe process goes up in memory and "Cached" stays quite constant.


Thank you all for your answers here!!! Much appreciated!!!

I think, since no one has yet reported a simular behavior, it is unlikely a general defect in Cubase 32bit. It must be something related to ASIO, due to the fact that it stops with the "No driver" setting. Since the effect appears with all ASIO drivers (DirectX and Generic) these are also in the clear.

Leaves side effects from Updates or some ultra strange combination of windows silliness...

Will try to reinstall Cubase soon and report back the result.

Otherwise: Bridging it is...

Haha.. gotcha!
Let's hope the updates bring some help to your situation.

I'd even recommend plugging your machine online once a month just to check if there's updates.

Unfortunately, SP1 did not change a thing. Tried to get offline updates going on a Mac, but it is a major pain...



Hmmm, I am more the school of thought: "never change a running system".
I do subscribe to your view for any system that is connected to the internet and I fully admit, that not being connected to any network is very cumbersome.

I see it that way: A DAW installation is like a race car. It has one purpose and everything should be directed towards supporting that one purpose. Once you start thinking about driving it in normal traffic you have to compromise so much, that you no longer have a race car...

I postponed working on that issue a bit, but one way of solving it will be looking at PreSonus StudioOne in the near future. I work on Cubase since VST came out and that will be a hard decision, but perhaps it's time for a change.