Mudrum cpu
-
- KVRAF
- 5383 posts since 25 Jan, 2014 from The End of The World as We Knowit
Many factors: several MuDrum tracks? many tracks Muted but Racks on? Perhaps post a screenshot, with system info.
F E E D
Y O U R
F L O W
Y O U R
F L O W
-
- Banned
- Topic Starter
- 1256 posts since 22 Feb, 2014
Could some please test this drum kit on there pc Thank's It's useing 19% cpu
Last edited by runaudio on Thu Sep 22, 2016 11:41 am, edited 2 times in total.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
It's missing the samples. Easiest way is to resave the project with all used samples embedded:
Project Browser -> What = Samples, Where = This Project.
Then Options -> Delete Unused + Options -> Embed All.
Resave + resend.
Alternative way = Project menu -> Export Consolidated Project -> Select some new folder.
Then zip that resulting folder + resend.
Project Browser -> What = Samples, Where = This Project.
Then Options -> Delete Unused + Options -> Embed All.
Resave + resend.
Alternative way = Project menu -> Export Consolidated Project -> Select some new folder.
Then zip that resulting folder + resend.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Ok, had a quick look, all seems normal. The MuDrum indeed uses some cpu cause it's a fully modular thing and everything is active all the time. You can make it more easy on the cpu by switching off processing for the pads that you don't use. Switching on/off a drum pad can be done via the big on/off button at the top of the pad pane (a bit above the little on/off of Sampler 1).
Also note that in your mudrum project you're using a shaker sample with a long release which builds up some polyphones. Making the release shorter will make it more easy on the cpu.
Also note that in your mudrum project you're using a shaker sample with a long release which builds up some polyphones. Making the release shorter will make it more easy on the cpu.
