Collaborative project!

[d.healey]

@lalalandsynth I'm not surprised about the CPU :)

[lalalandsynth]

It does not take much Cpu on my computer ?
2% but maybe that is a lot , hehe :)

[d.healey]

@lalalandsynth It uses 2.5% - 3.5% for me. By comparison if I load a sampled organ it uses 0.10%. So I'd say CollaB3 is a CPU hog, and it must be a lot worse on older hardware and laptops.

[lalalandsynth]

Yep, I guess we cant do much about that , but we should maybe think about fixing the noise ?

Or not, maybe that is just the way it is :)

[Christoph Hart]

I assume the CPU hog is the leslie (because it doesn‘t change with the voices).

Have you tried compiling the leslie into a C++ node?

[ustk]

@Christoph-Hart Does it change something once compiled?
I'll try that once I can get the Last commit to open my projects...

[lalalandsynth]

@ustk In case we do an update.

Fixes.

1. Cpu hogging - probably Leslie.

2. Lower noise - possibly accessible to user in settings ?

3. Drawbars are inverted when midi learned.

4. Examine speed difference between top and low horn - Leslie.

Possible additions.

1 . Distortion - Growl

2. Leslie Cab Impulse

3 Pro version - Another page with stomp boxes or fx / Delay , eq , phaser etc

[hisefilo]

Hi guys!!! Nice finding! The video guy is really happy with Collab3.
Im not shure if they say noise regarding Leakage or some other noises like key click (or DC offset caused by the oscillators with zero or 1 for attack (easy to change but I personally like it)

[lalalandsynth]

@hisefilo I saw someone say they stopped using after trying Waves denoise.
Seen a few of these comments so maybe have something in settings to change it ?

I could do a test , compress it and see where the noise is coming from.

[hisefilo]

@lalalandsynth noise sources un collab are dc offsets from oscillators with zero attack, noise generator for keyclicks and leackage container. do a gentle 20 ms attack and kill leakage and noise gen if you want a clean sound

[lalalandsynth]

Question:

Why is the Leslie such a cpu hog , its not a very involved fx in itself ?
Should I expect CPU problems when building fx with scriptnode ?

[lalalandsynth]

Time for MkII ? :)

And maybe remove the whole Covid Reference ;)

[hisefilo]

@lalalandsynth why not!!!!
And a super fat creamy rotor speaker with IR?

[lalalandsynth]

@hisefilo Yep , I still have access to a real one :)

[Christoph Hart]

Or just take a faust effect LOL:

LeslieSim/faust/leslie.dsp at master · miccio-dk/LeslieSim

Leslie speaker simulator, made in FAUST + JUCE. Contribute to miccio-dk/LeslieSim development by creating an account on GitHub.

GitHub (github.com)

Works out of the box and sounds awesome, you can even connect the leslie positions to a cable...

[hisefilo]

@Christoph-Hart No way!!!! this is awesome!

[hisefilo]

@lalalandsynth well I need to see if it compiles on HISE 3.0
Will pull the repo

[hisefilo]

@Christoph-Hart @lalalandsynth this is promising!

treble_speed = hslider("[00]Treble speed (RPM)", 35, 5, 500, 0.01) : si.smoo;
treble_radius = hslider("[1]Treble radius (cm)", 19, 5, 30, 0.01) : si.smoo;
treble_mics = hslider("[2]Mics distance (deg)", 90, 0, 180, 0.01) : si.smoo;
treble_am_depth = hslider("[3]Treble AM depth", 1, 0, 10, 0.01) : si.smoo;
treble_lpf_freq = hslider("[4]Treble LPF center freq (Hz)", 1500, 500, 3000, 0.01) : si.smoo;
treble_lpf_depth = hslider("[5]Treble LPF depth (oct.)", 1, 0, 4, 0.01) : si.smoo;
treble_horn_freq = hslider("[6]Horn resonance freq (Hz)", 2000, 1000, 3000, 0.01) : si.smoo;

[lalalandsynth]

@hisefilo Oh ! Nice !

[Christoph Hart]

Just be aware that there is no license specified for the code repo I posted.

As long as it's for a GPL project, you're fine, but it's not clear to use in a commercial project.