wavebypartial.pd: Waveshaping intermediate waves between the four basic waveshapes

wavebypartial.zip

So reading/selecting across are the partials for that waveshape, ex. sine's are all "0", etc.

The bangs just after the waveshape-name select all the partials for that waveshape, ex. clicking sine's bang makes the wavetable a sine curve.

The sliders have been included in case you want to manually shape the wave.

note: best to change to Log Level 1 (errors) as it does throw a lot of the pd-rounding messages.

I had been wondering about this for a while..."How do you get at the between-shapes?".

May it serve of some use to you.

-Peace
S

p.s. really just killing time until I have to get back to my much more complicated current project.

A funner example....
Sliders instead of hradio

wg.pd
wavebypartial-gradient-help.pd

So gradients between the four wave shapes.

Found, through other work, this is a much cooler way to handle making the wave form via partials:
using an xysl where x=the partial [0..9] and y=the value [-1-1]:
see the -help to see it in action

wavebypartial_b(via-xyslider).zip

Peace thru sharing,
s

Hey!

I've been trying to play with this and gensyn -- both seem like really neat synth ideas! However, I have run into a couple of issues.

I'm running the latest purr-data release installed through AUR.

First, the $1 creation arguments on the wavetables are not assigning the $1 float to the table id, instead, the wavetables are named "$1-wavetable" If I rename the wavetable to, for instance, 2-wavetable, then everything writes correctly.

Secondly, with wavebypartial_b(via-xyslider), purr-data is unable to create the objects "adsr" and "mknob".

Thirdly, switching to random partial generation for all gensyn clones in the help patch causes a huge lag, after which everything works. (this one could totally be a system issue, but I thought I'd mention it as long as I was commenting here.)

@Valuska-Yoshimitsu

Thank you, for all the feedback.

I will try and get these issues resolved as soon as possible.

In the mean time, I suggest you take a look at Jass~(the complete synth at https://forum.puredata.info/topic/13070/jass-just-another-synth-sort-of-codename-gemini-updated-esp-with-midi-fixes)

which is where all of these small ideas are born from.

Thanks, again, for your time, insights, and input. I will be getting back with you in a few days.

Peace and love through sharing,
s

@Valuska-Yoshimitsu for replies re: gensyn check my comments on that topic page.

'Secondly, with wavebypartial_b(via-xyslider), purr-data is unable to create the objects "adsr" and "mknob".'

The [adsr] file is included in the .zip and for the -help to work must be in the same folder as the [wavebypartial_b(via-xyslider)].
and
I apologize for the stray moonlib>mknob. I have removed it from the zip (below).

Peace through sharing,
s

wavebypartial_b(via-xyslider).zip

p.s. I, sincerely, hope this doesn't offend you @Valuska-Yoshimitsu but for expediency and clarity sake it's always best to separate comments regarding various threads into comments under their originating topic. Thanks. Much easier to write and share them that way and for the readers to follow along. -Peace. and Happy Pd-ing. Really appreciate your comments and hope the tools work out for you.

Hey, sorry it took me so long to get back to you! I had a BIOS blowout and had to totally rehaul my computer.

I don't take any offense! it makes much more sense to keep things in their own threads. Thanks for your response and I look forward to digging in to this stuff.

Best!

Hey! Valuska-Yoshimitsu is my other account I made because I had temporarily lost access to the email for this one.

I've been playing with this and it sounds beautiful. Thanks for your work.

I made a couple of changes:

-changed the $1 arguments naming the wavetable to $0
-added [line] objects after the xysl router to smooth out transitions]
-added [tabosc4~] and accompanying outlet/inlet
-added an inlet for a xysl as it comes packaged. (i'm not sure why, but i can't get xysl to respond when it's in a subpatch or abstraction. Additionally, not sure how you got it to data scale the way you did, so I added glue in wavebypartial for data scaling)

Here's the updated version-wavebypartial_b_2(viaxyslider).zip

Finally, I absolutely love the way this sounds: I want to run like 10 of them at once. Unfortunately, it's cpu expensive. My guess is that it's all of the sinesums going on.

I've thought for a while now that it could be possible to achieve this waveshaping effect by creating a huge bank of tables instead of running sinesum every time you want to switch. This is probably foolish, but I'm curious if you have any thoughts.

Thanks again!

Gosh, I really wish I had enough reputation to edit posts. Taking the wavetable off the abstraction graph-on-parent cut cpu usage some. I'm still getting little popping noises when I drag the xysl around fast enough, though.

also, @svanya, i forgot to tag you in the last post.

@Matt-Stalcup

wavebypartialx10.zip

Sorry, it's taken me so long to get back with you.

1. re: $1,$0- that is there so you can route "from afar" from those tables (you'll see this in the x10 file I included in the zip. Harder to do if the array is $0.
2. the line makes sense. Thanks.
3. tabosc4~ good idea. The x10 uses an abstraction I built around the same time I did this, gensyn~ (generic synthesizer) which includes those as its double-osc (see https://forum.pdpatchrepo.info/topic/13099/gensyn-generic-multi-modulator-synthesizer-abstraction for more info).
4. the xysl has an object in it at the very top: [iemguts/receivecanvas] where the creation argument defines what level-up of parent you want the mouse to be active, i.e. which level of grandparent. The original xysl abs hardcodes it at 1, meaning only the parent patch will be allow it to move. I have included my modified version which only includes changed integers out and the depth as $6 creation argument. Seems to help with the performance issue. As the x10/gensyn~ runs at about 5-10% on my old-ish desktop.

I am thrilled you like the patch. Always good to know the work is helping out.

I made the x10 version for you to consider. The notion of routing different tables to different clones, doesn't make a lot sense, but it does show this will work even with a high number of (cloned) tabosc~s.

Thanks, again for you input and help in making it better.

Peace through Music.
Love thru Sharing.
-s