[sharing] synthcore gen~ library

" I am preparing a demo download to show how it all works. This week I focused on commenting the work I’d done so far, and I appreciate any feedback on making it more understandable."

The lazy boy in me says "comprehensive and detailed comments please", but the auto-didact says "minimal and succinct only please".

'Preciate the hard work Ernest, looking forward to the demo.

Brendan

Damn Ernest, this is awesome.
I've been doing a ton of my recent work within codebox, and this is sure to provide me with some solid techniques.

Thanks for the work!

It just keeps getting better and better! Thanks so much, Ernest!

Also, even as someone who's fairly new to audio, DSP, and coding, I think your use of comments is fairly reasonable. For me, personally, it takes a some effort to fully wrap my head around concepts, but I think your code aids more than hinders in that regard. In fact, a lot of this could make a great companion piece when reading papers on things like filters and bandlimiting- subjects that normally use equations rather than algorithms to demonstrate concepts, which has been a giant wall for me to climb.

Dear Ernest

This is, definitely, a great stuff. Thank you very much.

Thanks Ernest! Great work.

Thanks for the comments. You may notice I some comments that gen~ crashed when returning values from inside conditional statements. It appears to be more frequent when there is more than one variable returned. Today I found something else, which might account for it, while writing the following stereo delay function:

ping(input1, input2, delayL, delayR, mix, cross, inpan, feedback){// stereo delay
    Delay ping1(384000, feedback=1);// allows 2 secs at 192khz
    Delay ping2(384000, feedback=1);
    u, v, x, y, z = 0;
    if(mix > 0){ // this part can be bypassed when not used. 
        x = ping1.read(delayL, interp="spline");
        y = ping2.read(delayR, interp="spline");
        z = 1 - cross;
        u = input1 * (1 - inpan);
        v = input2 * inpan;
        ping1.write((x * z + y * cross) * feedback + u * z + v * cross);
        ping2.write((y * z + x * cross) * feedback + v * z + u * cross);
        return 
            mix(input1, x, mix),
            mix(input2, y, mix);
    } else {
        ping1.write(input1);
        ping2.write(input2);
        return input1, input2;
    }
}
Param dl1 (24000), dr1 (20400), d1m (.75), d1w(.5), d1p(.5), d1z(.75);
left = in1; right = in2;
out1, out2 = ping(left, right, dl1, dr1, d1m, d1w, d1p, d1z);

The above works fine, but if I try calling the function with:

out1 = in1;
out2 = in2;
out1, out2 = ping(out1, out2, dl1, dr1, d1m, d1w, d1p, d1z);

It fails to compile, and sometimes crashes, saying "read-onlys can't be written." Strangely, this works:

out1 = in1;
right = in2;
out1, out2 = ping(out1, right, dl1, dr1, d1m, d1w, d1p, d1z);

So it appears the first argument in a function is read/write, but the others are read only. According to conventional programming, which should it be? Is the first argument meant to be read-only too, or are all the arguments meant to be read only? I never really thought about it before, I don't know the answer.

yesssss!!!

all cool. congrats.

can i just point out that this is crying out the be in max package format. or at least a single '.genexpr' file for using 'require'.

easier for you to maintain and push and users to update.

Well,. it is not easier to maintain *for me*, lol. It might be easier for you. But I have some questions about inexplicable behaviors which rather impact performance in a separate thread to resolve first, before I submit a package.