Hi Burny,
I know this is an old thread, but I was curious if you had solved this issue. I have the same behavior with C6.5, (32 and 64 bit) on win 7 and RME HDSP drivers.
Cheers.
Does Cubase 5/6 32bit has a memory problem??? Simple test to find out...
-
- KVRer
- Topic Starter
- 17 posts since 17 Feb, 2012
Yes, this was a while agonspaas wrote:Hi Burny,
I know this is an old thread, but I was curious if you had solved this issue. I have the same behavior with C6.5, (32 and 64 bit) on win 7 and RME HDSP drivers.
Cheers.
As far as I remember it was a problem when you use more than 2 Gig mem in Cubase32.
Gets unstable, even if you have far more memory and could theoretically use it.
What I can say for sure is, that I still use the same versions and all works good.
The RME drivers are the best on the whole market and I doubt they where the cause.
One thing I remember was, that I had really big drum stuff (>2Gig) at that time whith samplers and Melodyne and so on. Never had that again in this excess and nerver had problems again...
Let me know if I can help further.
-
- KVRer
- 4 posts since 15 Oct, 2006
Thanks for chiming on mate.
For me, just opening Cubase with no project open and the leak is evident. Only with rme drivers.
I have 12 gig installed, use vep on this and another machine and while I am able to work, the impending time bomb is a PITA. Annoyingly, it does t seem to be a common problem, which hampers troubleshooting somewhat.
Any insight into solutions is most appreciated.
Thanks again.
For me, just opening Cubase with no project open and the leak is evident. Only with rme drivers.
I have 12 gig installed, use vep on this and another machine and while I am able to work, the impending time bomb is a PITA. Annoyingly, it does t seem to be a common problem, which hampers troubleshooting somewhat.
Any insight into solutions is most appreciated.
Thanks again.
-
- KVRAF
- 6159 posts since 4 Dec, 2004
I'm not that much of a computer tech kinda guy but what you describe doesn't necessarily sound like a "leak" to me, it sounds more like Cubase maybe doing some background idle time caching to RAM.
I mean - to me anyway, mmv as usual on my relative ignorance of the subject matter - a leak to me is more when an app uses RAM and does't give it all back when it should, not so much it maybe just using additional RAM in some ways that may not be immediately clear. I mean, if you run a Cubase project that settles into (eventually) X amount of RAM on launch when empty, and that's a consistent figure, then you load a song and doodle for a bit, then close the song, and the process is still showing using way more than the X ram, that's what I'd kinda call a leak.
I have seen that in S1 in past versions, where it (apparently, dunno) wasn't releasing all the RAM, and eventually, if you cycled through multiple projects, it would creep up and you'd have to restart it to clear all the RAM.
But again, I'm not "that guy", and KVR has some knowledgeable techie types lurking, so my general perceptions of all that may not be accurate... as in "completely off base".
I mean - to me anyway, mmv as usual on my relative ignorance of the subject matter - a leak to me is more when an app uses RAM and does't give it all back when it should, not so much it maybe just using additional RAM in some ways that may not be immediately clear. I mean, if you run a Cubase project that settles into (eventually) X amount of RAM on launch when empty, and that's a consistent figure, then you load a song and doodle for a bit, then close the song, and the process is still showing using way more than the X ram, that's what I'd kinda call a leak.
I have seen that in S1 in past versions, where it (apparently, dunno) wasn't releasing all the RAM, and eventually, if you cycled through multiple projects, it would creep up and you'd have to restart it to clear all the RAM.
But again, I'm not "that guy", and KVR has some knowledgeable techie types lurking, so my general perceptions of all that may not be accurate... as in "completely off base".
-
- KVRer
- Topic Starter
- 17 posts since 17 Feb, 2012
AHHHH, just remembered something: I had a problem with the power supply!
One capacitor was faulty and the whole unit behaved more and more strangely.
Like blinking at power up and making strange noises, getting worse over time.
If the unit is out of warranty and you have basic knowledge of electronics you should have a look inside and check if you have any capacitors that have a bulging top. See: http://en.wikipedia.org/wiki/Capacitor_plague
Please be careful, if in doubt, unplug the unit in the evening and open it in the morning so there is no more voltage if you touch the wrong thing.
Changing the power supply was no big deal, I contacted RME and they directed me to a distributor.
Just make sure whether you have a power supply with a plugable connector or if it is soldered/screwed in the back, towards the plug of the power cord.
I had the old solution and got the plugable version. Since I had no suitable plug I had to hack something together. No big deal, but ask them to give you a suitable plug, saves some work in that case.
If you have the plugged version, the change is really simple, just 4 screws and 2 plugs -> done.
Hope that helps. Just checked my installation, no leak at all.
If it is not the power supply, we can get in the details. Please post detailed versions of your software then.
One capacitor was faulty and the whole unit behaved more and more strangely.
Like blinking at power up and making strange noises, getting worse over time.
If the unit is out of warranty and you have basic knowledge of electronics you should have a look inside and check if you have any capacitors that have a bulging top. See: http://en.wikipedia.org/wiki/Capacitor_plague
Please be careful, if in doubt, unplug the unit in the evening and open it in the morning so there is no more voltage if you touch the wrong thing.
Changing the power supply was no big deal, I contacted RME and they directed me to a distributor.
Just make sure whether you have a power supply with a plugable connector or if it is soldered/screwed in the back, towards the plug of the power cord.
I had the old solution and got the plugable version. Since I had no suitable plug I had to hack something together. No big deal, but ask them to give you a suitable plug, saves some work in that case.
If you have the plugged version, the change is really simple, just 4 screws and 2 plugs -> done.
Hope that helps. Just checked my installation, no leak at all.
If it is not the power supply, we can get in the details. Please post detailed versions of your software then.
-
- KVRer
- Topic Starter
- 17 posts since 17 Feb, 2012
One more thing: in the beginning of that problem, I had strange errors while installing new drivers. Had to reinstall the firmware a few times despite having the newest version already. Helped at first.
One or two flashes of the LEDs are normal, but it took longer over time to stop flashing and then made noises too.
But that started about mid 2013 and got heavy early 2014. Got the replacement April 2014.
Just had a look at my old power supply, had bulging tops without any liquid or brown stuff on two capacitors in right lower corner.
The white stuff between capacitors is normal!
The replacement part was about 70 Euros.
One or two flashes of the LEDs are normal, but it took longer over time to stop flashing and then made noises too.
But that started about mid 2013 and got heavy early 2014. Got the replacement April 2014.
Just had a look at my old power supply, had bulging tops without any liquid or brown stuff on two capacitors in right lower corner.
The white stuff between capacitors is normal!
The replacement part was about 70 Euros.
-
- KVRAF
- 26033 posts since 20 Oct, 2007 from gonesville
My mileage is different than when this was a new thread. There is no change in the amount of memory C5.5.3 is using with this project open at all today.
-
- KVRer
- 4 posts since 15 Oct, 2006
Thanks folks.
I don't believe it is a psu issue. The machine is a tank and is extremely reliable running heavy 24/7.
I have discovered that the issue exists for both RME HDSP and MOTU firewire drivers, but for all else is fine.
I don't believe it is a psu issue. The machine is a tank and is extremely reliable running heavy 24/7.
I have discovered that the issue exists for both RME HDSP and MOTU firewire drivers, but for all else is fine.
-
- KVRer
- Topic Starter
- 17 posts since 17 Feb, 2012
It don't have to be related, but that was the last problem I had here…nspaas wrote: I don't believe it is a psu issue. The machine is a tank and is extremely reliable running heavy 24/7.
I have discovered that the issue exists for both RME HDSP and MOTU firewire drivers, but for all else is fine.
Since there was a hiccup with the firmware and the driver, there was a chance that there could be a connection. Bad PSU -> firmware not stored safely or something.
The RME stuff is amazingly build and works very solid. Never had an issue before or after.
You will certainly have another audio software (like a wave editor or something). If this has no problem with the same driver, you could rule out the driver as primary source of the issue.
One of my favorite problem cause: dongles. Perhaps the copy protection has a problem.
Again, you could try to isolate that with different software.
If it is a OS problem, you should have the issue with all software…
As far as I reread the topic, I had no leak without an audio driver, but also a leak with other drivers.
That in mind, I doubt that it is the RME driver.
Also: I only had the problem only with the 32bit version, not with 64bit Cubase.
So it might be a different problem altogether.
You write MOTU, so you are on Mac???
The memory management of OSX is … well… strange at least. No one could explain to me the concept of Wired, Active, Inactive, Real, Private, Shared and Virtual memory so far. I just know, that whenever free memory runs out, my MBP freezes or does other silly stuff.
-
- Pick Me Pick me!
- 10237 posts since 12 Mar, 2002 from a state of confusion
Wow. You are one of the last holdouts.ZenPunkHippy wrote:Did the test. Win 7 64 bit Home, M-Audio 2496, 4 GB RAM, Cubase 5.5.2, 32-bit. .
In hindsight, that was a really good buy.. that card.. I, instead, opted for the slightly cheaper M-Audio Revolution 7.1 card when looking for a new soundcard around a decade ago. It is flaky now.. well.. it works well once you get it going but the install is hit or miss with the Windows XP BETA drivers. haha
Looks like you made the better choice
-
- KVRist
- 471 posts since 5 Dec, 2007 from Location! Location!
Motu products are not mac only.Burny wrote: You write MOTU, so you are on Mac???
Free memory is unused memory.Burny wrote: The memory management of OSX is … well… strange at least. No one could explain to me the concept of Wired, Active, Inactive, Real, Private, Shared and Virtual memory so far. I just know, that whenever free memory runs out, my MBP freezes or does other silly stuff.
Used memory is the total of all memory space that is filled with purposeful data. Wired + Active + Inactive.
Wired memory is used by the OS primarily. It can not become virtualized at any point.
Active memory is memory used by applications. This is where the stack/heap are. Active memory can be moved to virtual memory if necessary.
Inactive memory is memory that WAS used by an application. This allows applications to restart very quicky if needed, but inactive memory will be used 'normally' if you are out of free memory.
Virtual memory is used when free memory has run out. It's essentially utilizing the hard drive as ram. Similar to swap (linux) or the page file (windows).
The memory management of OS X is also not strange. The topology is similar in windows and linux, but with different naming schemes.
-
- KVRAF
- 26033 posts since 20 Oct, 2007 from gonesville
The first part is true, but the second part here is not necessarily true. Too many people's experience has been otherwise. I use 'purge' in terminal frequently as inactive grows and grows, unused by anything.HobbyCore wrote: This allows applications to restart very quicky if needed, but inactive memory will be used 'normally' if you are out of free memory.
https://discussions.apple.com/thread/36 ... 0&tstart=0
-
- KVRist
- 471 posts since 5 Dec, 2007 from Location! Location!
I'm aware of the issue in 10.6-7, but it works as it should in 10.8+. This is due to the removal of automatic garbage collection and move to ARC.jancivil wrote:The first part is true, but the second part here is not necessarily true. Too many people's experience has been otherwise. I use 'purge' in terminal frequently as inactive grows and grows, unused by anything.HobbyCore wrote: This allows applications to restart very quicky if needed, but inactive memory will be used 'normally' if you are out of free memory.
https://discussions.apple.com/thread/36 ... 0&tstart=0
It's entirely possible for someone to screw up memory management and cause problems, but inactive memory works properly until you (the developer) do something to screw up ARC.