M4L devices max out CPU meter!!!

[adh82]

Has anyone else noticed this???
If I run around 6-10 M4L devices my CPU meter shoots up to 60%-80% and I start to get crackles in my audio!!!
I'm running:
live 9 32bit MacBook Pro i7 16gb

I should have heaps of processing power!

What going on???

Cheers,
Adrien.

[Lumix]

i know i loaded a convolution reverb pro and it was using 60-80% of my old phenom II X4(i know its an old one - will update soon to an intel cpu)
hmm i guess i wont use max4live that much in the meantime. (hope this will be improved in the future)

[adh82]

14 views and only one response, is no one else having this issue?
it seems to happen when using the device randomizer utility.
have at least 5 instances of it and let me know what happens.

Cheers.
Adrien.

[eric_c]

I've noticed this a little bit as well. I haven't spent a lot of time comparing everything to Live 8 yet, but I can tell you that the Buffer Shuffler 2.0 in 9 uses about twice as much CPU as it did in 8. This is really frustrating considering its one of my most oft used devices.

[tone61]

M4L devices tend to use more CPU than native devices or VSTs.
Device Randomizers quite a bit more.
So you have to think how many M4L devices you can use at the same time.

[adh82]

Really? I would have thought m4l would have been better with CPU usage seeing that its such a big deal in 9.
So how many devices do people usually use?
Will this get fixed in an undate?

[pencilrocket]

Why did you think so? How can visual programmed plugin more efficiently than one written from the ground?

[timothyallan]

Pretty sure that cycling didn't re-write max because Live 9 was coming out

[adh82]

Thanks for testing that out,
I did use CPU hungry devices one I noticed they were eating into my meter.
I prob wouldn't use as many as I had set up, but it's still a concern if they are that heavy on the system!
I really hope they look into it further.
Is there a place to report this behavior?

[skiMo]

I also have this problem, for me it's pretty specific to the Device Randomizer. If I do the following steps:

1) New empty project
2) Instrument rack (empty)
3) Device Randomizer mapped to Instrument Rack
4) Device Randomizer mapped to the previous Device Randomizer



I end up with around 50% cpu usage on a MBP Retina, 2.6ghz, 16gb RAM.

I can't understand why something that only really provides random numbers can be so heavy on the CPU.

[33tetragammon]

I have cpu spikes with these devices:

-Expression control : assign a few parameters to (for example) aftertouch, play one note. cpu goes from 6% to 23% as long as the device is turned on over here.

-Mono Sequencer: just turning the 'pattern' knob skyrockets my cpu (sometimes above 100%, especially when i turn the knob quickly ). Plus it also causes glitches in the audio when i turn that very same knob.

-Device Randomizer : just turning it on increases my cpu 10%. Turn 'auto' on, cpu goes up to 25%. Plus it doesn't randomize everything even when everything is set to 'on' in the device's 'edit' tab. Tested it with Live's instruments and VST's. No difference.

I'll investigate the new MFL devices some more and will post the problems here.


I'm on a brand new 15" Macbook Pro Retina, 2.3 ghz quadcore i7, 8gb ram, 256 gb flash hd, mac osx 10.8.2.
Focusrite Forte as my audio interface.

[Valiumdupeuple]

1) New empty project
2) Instrument rack (empty)
3) Device Randomizer mapped to Instrument Rack
4) Device Randomizer mapped to the previous Device Randomizer

This was acknowledged during the beta, but you know, they've released the final version while the beta was still full of problems...

[andrewbrewer]

From the beginning I have viewed M4L plugins as experimental and thus all bets are off regarding resource management. I still use them heavily but I find I stay a bit more sane when I bounce ideas to audio and remove M4L devices.

[pepezabala]

-Mono Sequencer: just turning the 'pattern' knob skyrockets my cpu (sometimes above 100%, especially when i turn the knob quickly ). Plus it also causes glitches in the audio when i turn that very same knob.

yes, what a pity, same here. unusable for me when assigning my nanokontrol to the pattern-knob. audio glitches on every twist on macbookpro 2,2ghz quad, 8 gb ram.

I just had started to love this device.