Is it normal for the MuDrum to use 12-13% CPU? I started MuLab and have 4 Racks in a new session with a Mux Preset on two of the Racks and MuDrum on third. CPU% was hovering around 14-15% so I tried deleting the MuDrum and it went down to 2-3%. I only had 1 drum sample and 1 Mux Preset loaded in MuDrum.
Win7 x64
Core i5 2467M 1.6GHz
MuLab x32
4GB RAM
EDIT: Is the CPU monitor just what MuLab uses or an overall usage monitor? Would other apps affect MuLab's monitoring?
MuLab 5.0.39 (pre-release)
-
- KVRAF
- 2692 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- 2973 posts since 10 Sep, 2003 from Karlskoga, Stockholm, Sweden
Sort of depends on what was in the mux, doesn't it? Was it empty?
-
- KVRAF
- 2692 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Indeed it does, I checked and removing that preset reduced CPU% by 1-2%, not a major amount.
-
- KVRAF
- 2973 posts since 10 Sep, 2003 from Karlskoga, Stockholm, Sweden
On my system a samples-only preset draws 6% cpu. From 1.2% idle to 7.7%. Turning off the individual pads drops it around 0.5% each. Makes sense since there's 12 pads.
Is it much or not, i don't know. Not sure how much something like this is supposed to draw.
Is it much or not, i don't know. Not sure how much something like this is supposed to draw.
-
- KVRAF
- 2692 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Percentage should be relative to the individual CPU though?
eg. 10% of 100 = 10, 10% of 200 = 20. Your processor is far better than mine judging by it's speed.
How many samples? Mine was idle too nothing being used.
eg. 10% of 100 = 10, 10% of 200 = 20. Your processor is far better than mine judging by it's speed.
How many samples? Mine was idle too nothing being used.
-
- KVRAF
- Topic Starter
- 12737 posts since 24 Jun, 2008 from Europe
The MuDrum indeed is a serious beast full of (sub-)mixing options and that may take a bit of cpu. On slower systems this may be more striking. MuLab's cpu meter measures MuLab's audio processing.
-
- KVRAF
- Topic Starter
- 12737 posts since 24 Jun, 2008 from Europe
There is a new MuLab 5.0.34 package available in http://www.mutools.com/mulab/everest
This is what's changed since M5.0.33:
Cheers!
This is what's changed since M5.0.33:
- Sequence Player module now is syncable to the sequencer.
- Fixed/tuned a couple of practical issues with the Sequence Player module.
- Session browser is also focusable by clicking its background.
- Fixed a little display bug wrt the session name in the session window title bar.
- More accurate undo/redo descriptions for the audio DSP functions.
- Fixed a practical problem where undoing/redoing an audio file edit could not be performed because the audio file is opened in another app at the same time.
- Fixed a problem wrt loading presets in the MuDrum and MuPad.
- Reverted the default for DrawGuiFocusBox to 100 (%).
- Tuned the looks of the MuSynth.
- Finetuned some other graphics.
- Extended & tuned the factory library.
Cheers!
-
- KVRAF
- Topic Starter
- 12737 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 2692 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
A couple things I noticed... when I hit the space bar to start play in the arrange window it starts playback in the browser. Is that unavoidable and or focus has to be established by clicking on the arrange window? Also is there a way to have the preview (browser) off by setting? Seems like it keeps turning back on whether I turn it off.
Checking out new version!
Checking out new version!
-
- KVRian
- 1441 posts since 4 Oct, 2012 from Utah
1. The new Musynth look has settled my ocd. One issue though is that its colors do not match the other pre-made devices
2. When picking colors In the MUX and for track/rack purposes instead of saying "no color" have the button say "default color" because no color would mean no visibility
2. When picking colors In the MUX and for track/rack purposes instead of saying "no color" have the button say "default color" because no color would mean no visibility
-
- KVRAF
- 2692 posts since 28 Mar, 2008 from a Galaxy S7 far far away
In MuSynth, there's option to Choose Colour, but the colour doesn't actually change! This either in the Menu or by R-clicking a 'module' name on the Front Panel of the Synth.
Also, the Browser's 'What, Where, Which' text is still different from the Menu text colour.
Also, the Browser's 'What, Where, Which' text is still different from the Menu text colour.
-
- KVRAF
- 9077 posts since 28 May, 2005 from Netherneverlands
Sorry to say, but the new default MuSynth colors are not easy to look at 
I'm not sure if this is the best choice of color scheme as default..
And indeed. Change color does not seem to work.
I'm not sure if this is the best choice of color scheme as default..
And indeed. Change color does not seem to work.
No band limits, aliasing is the noise of freedom!
-
- KVRAF
- 23101 posts since 7 Jan, 2009 from Croatia
Change color indeed doesn't work on any of Mu... synths.
By default it should follow the color of Top Panel Display Color, I'd suggest...
By default it should follow the color of Top Panel Display Color, I'd suggest...
-
- KVRAF
- 2692 posts since 28 Mar, 2008 from a Galaxy S7 far far away
+1 but would personally prefer to have a seperate option.
