Getting really wound up by this now. Even when Mulab is sitting with empty tracks when it has just opened, my RAM usage for it is over 1,000,000k
I have recently got a Midi Controller, but even with that unplugged and the drivers etc all reinstalled, I'm still getting it so it can't be that. I have also reinstalled Mulab (opted for 32 bit this time instead of the 64) and it's still doing it.
Specs:
Windows 7: Service Pack 1
Processor: Intel(R) Core(TM) i5-4440 CPU @ 3.10GHz 3.10GHz
RAM: 8.00 GB
System Type: 64 Bit Operating System
Okay, had another wee test while writing this and it seems to be down to a much more reasonable 85,000k but it will no doubt happen again as it already has so I'd prefer to have an actual fix for it.
Need any more info, giez a shout!
Mulab 6 using extremely high amounts of RAM
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Questions:
1) Which MuLab version?
2) Are you sure the RAM usage is not caused by inserting a RAM intensive plug-in?
3) When launching MuLab and choosing "New" from the startup menu, then do nothing at all in MuLab, then how much RAM does it take?
1) Which MuLab version?
2) Are you sure the RAM usage is not caused by inserting a RAM intensive plug-in?
3) When launching MuLab and choosing "New" from the startup menu, then do nothing at all in MuLab, then how much RAM does it take?
-
- KVRer
- Topic Starter
- 8 posts since 5 Jan, 2015
Mulab 6 UL
It shouldn't be now, I never reinstalled my plugins after the install of the 32 bit version
Having done new, it's now showing 95,000k. When I opened it yesterday, even after the reinstall I was getting the obscenely high 1,000,000k reading.
It seems to be running at about 500,000k today when I'm recording, although the program is slow and unresponsive when trying to even access the menus to save. After I hit the record button to finish a recording, it's taking up to 7 minutes to actually place the recording on the track.
It shouldn't be now, I never reinstalled my plugins after the install of the 32 bit version
Having done new, it's now showing 95,000k. When I opened it yesterday, even after the reinstall I was getting the obscenely high 1,000,000k reading.
It seems to be running at about 500,000k today when I'm recording, although the program is slow and unresponsive when trying to even access the menus to save. After I hit the record button to finish a recording, it's taking up to 7 minutes to actually place the recording on the track.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Which exact version? See MULAB menu -> Info -> About MuLab.jurdu wrote:Mulab 6 UL
Immediately after MuLab launch and choosing New, i see MuLab 32 bit takes around 52 MB, MuLab 64 bitHaving done new, it's now showing 95,000k.
takes around 120 MB. Other figures from other users on other systems are welcome.
When using audio parts, plugins, MUX presets etc RAM will increase of course.
How many plugins did you insert? How many audio parts do you have in your composition?
When does this situation occurs? Immediately after starting from a new session? Please describe step by step with technical relevant details.It seems to be running at about 500,000k today when I'm recording, although the program is slow and unresponsive when trying to even access the menus to save. After I hit the record button to finish a recording, it's taking up to 7 minutes to actually place the recording on the track.
-
- KVRer
- Topic Starter
- 8 posts since 5 Jan, 2015
Sorry, 6.1.32.
I've not installed any plugins, I'm just using the built in Funeral Pipes synth with the midi controller at the minute. Just that 1 track of audio for a bit of experimentation to see how the RAM behaves.
Whether I've recorded 2 tracks already or just starting a first track doesn't matter, it is a lot slower than it used to run.
Literally all I will do is start a new session, choose a track (whether that be sample or synth), hit record and stop record when I'm done. It usually only takes 2 minutes, but yesterday it was taking up to 7 minutes to stop the recording. I'm not left with minutes of silence at the end of my recording, I just mean it takes minutes for the recorded sequence to actually appear on the track. As soon as I go into the menus they take about 30-45 seconds to actually open up, then when I select an action it takes at least 1 minute to start said action.
I've not installed any plugins, I'm just using the built in Funeral Pipes synth with the midi controller at the minute. Just that 1 track of audio for a bit of experimentation to see how the RAM behaves.
Whether I've recorded 2 tracks already or just starting a first track doesn't matter, it is a lot slower than it used to run.
Literally all I will do is start a new session, choose a track (whether that be sample or synth), hit record and stop record when I'm done. It usually only takes 2 minutes, but yesterday it was taking up to 7 minutes to stop the recording. I'm not left with minutes of silence at the end of my recording, I just mean it takes minutes for the recorded sequence to actually appear on the track. As soon as I go into the menus they take about 30-45 seconds to actually open up, then when I select an action it takes at least 1 minute to start said action.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
To add some more comparison figures:mutools wrote:Immediately after MuLab launch and choosing New, i see MuLab 32 bit takes around 52 MB, MuLab 64 bit takes around 120 MB.
When launching MuLab and before choosing a initial session thus while the startup menu is up it takes around 20 MB on a 32 bit system.
As the default "New" session is not really empty i also created a really empty session and then M6.1.32 takes around 40 MB on a 32 bit system.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Are you recording audio or events?jurdu wrote:I've not installed any plugins, I'm just using the built in Funeral Pipes synth with the midi controller at the minute. Just that 1 track of audio for a bit of experimentation to see how the RAM behaves.
Whether I've recorded 2 tracks already or just starting a first track doesn't matter, it is a lot slower than it used to run. Literally all I will do is start a new session, choose a track (whether that be sample or synth), hit record and stop record when I'm done. It usually only takes 2 minutes, but yesterday it was taking up to 7 minutes to stop the recording. I'm not left with minutes of silence at the end of my recording, I just mean it takes minutes for the recorded sequence to actually appear on the track. As soon as I go into the menus they take about 30-45 seconds to actually open up, then when I select an action it takes at least 1 minute to start said action.
In other words: does the recorded part show note events or does it show an audio waveform?
-
- KVRAF
- 5383 posts since 25 Jan, 2014 from The End of The World as We Knowit
On a macbook 2.66Ghz i7 8GB 10.8.5; MuLab 6.1.32 splash screen 36.3MB New Session (BasicSynth) 82.8MBmutools wrote: Other figures from other users on other systems are welcome.
F E E D
Y O U R
F L O W
Y O U R
F L O W
-
- KVRAF
- 1925 posts since 29 Mar, 2013
Sounds like there is something happening in the background unrelated to Mulab, your pc is not trying to defrag or virus scan is it ? look into Task Manager.
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
-
- KVRAF
- 4536 posts since 17 Jun, 2013 from very close to Paris, France
- Acer Aspire V3 (i5, 8 Gb RAM)
- Windows 7 Family Edition SP1 64-bit
- Mulab 6.1.29 32-bit (I never use 64-bit)
- Splash screen: 39 228 K
- New session: 84 440 K
Build your life everyday as if you would live for a thousand years. Marvel at the Life everyday as if you would die tomorrow.
I'm now severely diseased since September 2018.
I'm now severely diseased since September 2018.
-
- KVRAF
- 4536 posts since 17 Jun, 2013 from very close to Paris, France
A question:
When a DAW is loaded, I assume that there are other things which are loaded at the same time but which are external. The ASIO drivers and the MIDI drivers for example, and other things...
Could the differences from a machine to another one be due to such external things? (which are required at the launch of a DAW)
When a DAW is loaded, I assume that there are other things which are loaded at the same time but which are external. The ASIO drivers and the MIDI drivers for example, and other things...
Could the differences from a machine to another one be due to such external things? (which are required at the launch of a DAW)
Build your life everyday as if you would live for a thousand years. Marvel at the Life everyday as if you would die tomorrow.
I'm now severely diseased since September 2018.
I'm now severely diseased since September 2018.
-
- KVRer
- Topic Starter
- 8 posts since 5 Jan, 2015
Nah nah definitely not, I always manually choose when to scan to avoid issues such as this. I always have my processes sorted by RAM being used rather than alphabet so I can see any issues quickly. At the times of the reading being 1,000,000 the only thing close in terms of RAM use was Firefox at a measly 200,000. Next closest was away down at 20,000.bibz1st wrote:Sounds like there is something happening in the background unrelated to Mulab, your pc is not trying to defrag or virus scan is it ? look into Task Manager.