I noticed that breeding MIDI CC# parameter values under 10 is very difficult as minimal values tend to blend back into the population, but minimal values are important for envelope parameters like attack and decay. I'll have to patch an option to weigh the randomization of parameter values for each CC# so they tend to generate smaller numbers.
And a much bigger population of at least 12 sounds would be helpful. Will take a while...

Exactly, but you don't have to create a loop, if you rout a keyboard into your synth. You just have to make sure, that the synth only gets note events from your keyboard - not the CCs, as those are coming from Ewolverine.
You can also control Ewolverine with your keyboard. Just scroll to the right to read the MIDI implementation chart.

Here's a video. Not the best quality, but you'll get the essence.
Ewolverine works like a Biomorphs-program with sounds. It generates random presets and interpolates between selected individual ones in a dominant-recessive or intermidiate way.

Hi, you're right. I'll record something for you, soon.

EWOLVERINE 7.2 by Henry Dalcke.pd

...again some adjustments

@alexandros
it could very well be that these objects work. Being a pd-rookie, all my patches are dependent on external help. Thank you very much.

Hi everyone,
I'm trying to patch waveguide wind instruments in Pd and need some building blocks:

1. a nonlinearity (waveshaper with transfer function x-x³)
2. a phase inverter
3. a way to create a zero/low-latency, time-variable feedback delay line

Any ideas?

Kind regards

Hello again,

I need to compare audio against a target sample. I heard that MFCC error calculation does a good job in this field. Is there any object in pd that does that for multiple seconds long audio recordings?

regards

Hello everyone,

as most of you know, I'm continuously developing my Ewolverine patch with which you can genetically breed sounds out of your MIDI-gear.
In order to automatically approximate synthesizer parameters, Ewolverine must compare different synth-sounds to a target sample. The problem is that sounds match differently to the target sample depending on the comparison-criterion.

Examples:

Case 1:
If the selection criterion is the length of synthesized sounds in comparison to the target, the selection mechanism may choose for synth parameters that generate sounds as long as the target sample, but may pay no attention to its timbre.

Case 2:
If the selection criterion is the onset, the generated sounds may all have equal onsets, but differ in length and timbre.

What I need is a way of multi-objective optimization which takes all criteria into account and tells Ewolverine's selection mechanism which synthesized sound is generally nearest to the target sample.

Is there anything in pd that I could use or do you have any idea what I could do or do you know anyone who could help me?

EWOLVERINE v.7.1 beta by Henry Dalcke 6.pd

...changed some default settings of the Target Drive and corrected the Help-subpatch a little...