Sorry mlbstrd, but I never got to the point where did a specific edit to a specific object, I was just super-pleased that I could do it at all. I know I practiced at the time and saw results, but whether it was done right and bug free is another thing entirely.

The problem might not actually be your coding, it might be something to do with the patching environment so hopefully someone who knows what they're talking about will step in and advise, but I'm sorry I can't help.

@mlbstrd You can make your own versions of those objects, the rings for example:

Embed the object.

Go to "edit object definition" and "copy to library" to save the object as a real object to a folder you like.

Go to the "rings" folder, in the factory library, then simply copy the header file "rings_fx.h" to the folder that you saved your own version of the object in.

Voila, the object will now load and you have created your own local version that you can edit to taste

(It's because the object need to have a specific path so it MUST be saved(copy to library).... And then next the object expects the headerfile to be in the same folder as the object itself. So you need to copy it over manually, as described above).

SO, an amalgam of a few of these oscillators would do it, but none of them are up to the task on their own.

Here's what I was able to accomplish -- I successfully added a quadrature outputs to sine-sync. (

Now I just need to add the other waveforms and I'm a little overwhelmed. I also tried converting the dual multiwave LFO to s-rate, but I can't get it to work. I changed the inlet/outlet types and parameter types to match what i've seen other s-rate oscillators use. I also cut and paste the code from k-rate to s-rate. Didn't work, lol. Am I even close?

I didn't want to start an extra 101-thread, so:Is it as "easy" (as easy as modulation-inputs) to make stereo out of mono-modules?e.g. "stereorize" a filter/sampler/delay?Or is to dublicate the modules the best way? It would save a lot of sram + time to setting up...Thanks!

Is it as "easy" (as easy as modulation-inputs) to make stereo out of mono-modules?

I think the easiest way is to make a subpatch and throw it all in there.

deef:

Or is to dublicate the modules the best way?

You can write it in code, for example making a for loop X times depending on how many you want.

Or you could just copy the code inside and object and rename the variables for the second version. Like if you have some variables called "int a" and you copy that one, you neeed to rename it, cause you can only have one variable with that specific name.

So basically if you know a little code you can try the above.

deef:

It would save a lot of sram + time to setting up...

Time yes, but S-ram I am not sure, cause you still need 2 of each. I think its going to be very little you save if its just a stereo delay.

For the S-ram, try using the delay that uses SD-ram. There are a lot more SD-ram than S-ram, so you can save the S-ram for other purposes.

How would be the subpatch way go? I mean I'd have to still have the module 2x in the subpatch + make all the parameters/dials available on parent, to assign them to midi quickly.... or is that actually the main SRAM saving tip, to have simply INS & OUTS on parent & rest hidden in the subpatch, but still mapped to midi or analog-pots? Hm...Probably I confuse what RAM is needed for what. All the dials on an object is it in SRAM, right?

Probably I confuse what RAM is needed for what. All the dials on an object is it in SRAM, right?

I dont think you should worry too much about a couple of dials, there are other things that will take up alot more memory than dial, like for example if you use a delay that uses S-ram, instead of the SD-ram version.

I am no expert on the details about how much resources they use, I think someone else who know code a lot better than me can answer that for you... Ut a couple of dials...... Dont worry about that

Anyway, I think you should just start patching and if you eventually get to the point where you hit the limit there are always ways to optimize a little bit here and there. But overall I think you should just build what you like and the realise if you actually have issues or not. Use some of the tips above, like use SD-rams for the delay anf you will go far.

About the stereo thing, the essence of stereo is, that its two channels, so if you want stereo....

I know the community library is huge, but its definately worth the while spending some hours looking through it to see whats there. Its a really good way of finding inspiration for your own pacthes. Not only check the community library objects but also the the patches that you find in >

Basically putting a parantese around the inlet_leng, so ONLY the inlet is affectced and then bit shift 21:(inlet_leng<<21)

If that doest work, then try to switch the <> for all of the changes I have made. I don't have my Axo board fired up ath the moment and I always get those two switched around, so if one doesn't work, try the other.

I added some displays so you can see the scaling on the object. They are all scaled 0-63 now in integer. Can be tuned so it fits bette fo the purpose, like 1-16 instead of 0-63.

Besides that sorry, I have no idea why it wont work. I tried a few things and yeah it just doesnt seem to work properly when using dials. After it has been rescaled, it should work the same. Sorry I am out of suggestions.