I'm so tired , i can't work anymore. I wanted to start on odroid or raspberry board, but the synth is very heavy in term of cpu usage and i can't start on each one board. So my all project are failed and i'm bored to continue that, so if you want help me to develop this synth and maybe also lighten that, i will really apreciate it.

You can download the project here:

@Qwbit Wow! Very nice synth. Hope someone will contribute.

Download link: https://mega.nz/#!whNCQBZb!bIZLUR0kPG0MwMjgMLdTLTq7UYd4B6SjjbaZfzOBJNY

I wonder if it could run on http://khadas.com/vim/ (need a usb audio card).
Cheers~

@EEight i'm working for this, my first target was start the synth on raspberry board , but the raspberry are too slow. After i tryed on the odroid Xu4 board, the best single board pc with a 8 core... but also on the odroid the synth can't work totally.

So i restart to remake all synth in a few days and this time i try to make that directly on the board, so i can see the consumption in real time and to act accordingly.

If you're going to use an embedded computer like the Odroid or the Pi, I guess you'll build some kind of controller, or are you going to use a computer screen as well?
In case you don't use a screen (which is meaningful when using and embedded computer), get rid of all the GUIs (sliders, number atoms, knobs, bangs, toggles, radios, VUs). Use [float] instead of sliders, number atoms, radios, and toggles, and [bang] or [t b] instead of bangs.
Get rid of all your array graphs and use the [array] object or [table] instead. Get rid of all the GOP (Graph On Parent) and enclose your processes in subpatches or abstractions.
This should save quite a LOT of CPU.

Your synth is really nice, I would follow @alexandros even if you go with a screen, you should probably only keep what is really necessary. On the rpi pd 's gui can be a real cpu hog. It's always good practice to seperate audio and gui code and try to reduce the number of controls

And if you do want a screen why not test the performance on android or ios with droidparty or mobmuplat ? You'd need to keep your patch vanilla compatible though. I see also that you use freeverb, sometimes there is memory leaks with this object maybe you could try another reverb ?

Thanks for your comment, i will restart to develop the entire synth and i will follow your advice

@Qwbit

I found this a while back (and on linux at least) it might help (perl script to fine tune real time audio configuration settings to improve performance):

https://github.com/raboof/realtimeconfigquickscan

"realtimeconfigquickscan:
Linux configuration checker for systems to be used for real-time audio"

Good luck!

-Scott

Hey!

How did you get those dials?