Here's the demo – comparison between a 512 symmetric table and tabosc4~, a 512 cosinesum table and tabosc4~, and osc~ (512 linear interpolation).
I'm wondering, if this is a problem, is it a bug or just an alternative? Might affect how one thinks about compatibility. On Wed, Aug 4, 2021 at 3:15 PM Miller Puckette <[email protected]> wrote: > Unfortunately they can't be fixed by default (compatibility...) I'm still > struggling to figure out how to best allow alternative tables (especially > larger table sizes when needed) without badly complicating everything. > > cheers > M > > On Wed, Aug 04, 2021 at 03:09:26PM -0400, Matt Barber wrote: > > Hi Andy, > > Thanks for the reply. sinesum is better but not perfect – the issue is > that > > the cos() function is not the same on all four parts of the waveform, and > > those imperfections can cause fm to drift. You can build a symmetric > table > > easily enough but since osc~ and cos~ are so important, they should be > > fixed. I'll submit a demo patch when I get home. > > > > Matt > > > > On Wed, Aug 4, 2021, 2:50 PM Andy Farnell <[email protected]> > > wrote: > > > > > > > > I always found that [tabosc4~] along with ability to fill arrays using > > > like csound gen message functions [sinesum( gives me all the accuracy > > > I needed for FM. Am I missing something in pull/106 about shorcomings > > > of [osc~] > > > > > > andy > > > > > > On Wed, Aug 04, 2021 at 10:55:02AM -0400, Matt Barber wrote: > > > > I'd love to get a symmetric cos table for stable FM: > > > > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_pure-2Ddata_pure-2Ddata_pull_106&d=DwIFaQ&c=-35OiAkTchMrZOngvJPOeA&r=XprZV3Fxus2L1LCw80hE4Q&m=ivUR0FnAHdNwIEVfI256EXxk4y8UQELfZv-zc4r1eVI&s=_kjOA5CF2UpoVobqDdhS46dvekWZSN3tJcfqWSYEImI&e= > > > > > > > > But I remember you were thinking about going another direction > entirely > > > > with osc~? > > > > > > > > Thanks, > > > > > > > > Matt > > > > > > > > On Tue, Jul 13, 2021 at 1:23 PM Miller Puckette via Pd-dev < > > > > [email protected]> wrote: > > > > > > > > > (re-send - I had sent to [email protected] but that now seems to be > > > > > defunct...) > > > > > > > > > > To Pd dev - > > > > > I'm going to try to get the next Pd release (0.52) out over the > next > > > month > > > > > or two. My personal priorities for this release would be putting > in a > > > > > message > > > > > backtrace mechanism (by overriding canvas_connect and pd_bind to go > > > through > > > > > small proxy objects; this will have to be done at load time I > think) > > > and > > > > > to go back and try to figure out how to do tooltips without adding > > > cruft to > > > > > the inlet structure. (There's an ancient source-patch to provide > > > tooltips > > > > > by Chris McCormichadn Guenter Geiger that I plan to start with - > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_pure-2Ddata_patches_264_&d=DwIFaQ&c=-35OiAkTchMrZOngvJPOeA&r=XprZV3Fxus2L1LCw80hE4Q&m=ivUR0FnAHdNwIEVfI256EXxk4y8UQELfZv-zc4r1eVI&s=kv8MTDBG_E2ZbR5-jXxHxJD9BdHKZbHGVHvsxhnfjb8&e= > ). > > > > > > > > > > Before doing that I want to do some reorganizing - in porting Pd to > > > > > FreeRTOS > > > > > (so I can run it on an Espressif LyraT board, which I think takes > only > > > > > about > > > > > 10 or 20% of the current that a Pi needs) I found out that I had to > > > move > > > > > a few functions from one file to another. > > > > > > > > > > This might break some PRs, so... first of all would be to identify > > > whatever > > > > > PRs are ready to merge so I can do that before I make incompatible > > > changes. > > > > > Of course "stable development branch" first... then Dan's soundfile > > > > > updates... > > > > > then what? > > > > > > > > > > PS more ideas of mine (among many): > > > > > hot-reloading externs via a message to Pd > > > > > use a "unix binding" socket between Pd and pd-gui instead of > localhost > > > > > generalize number/symbol box to allow displaying entire messages or > > > lists > > > > > > > > > > cheers > > > > > Miller > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Pd-dev mailing list > > > > > [email protected] > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.puredata.info_listinfo_pd-2Ddev&d=DwIFaQ&c=-35OiAkTchMrZOngvJPOeA&r=XprZV3Fxus2L1LCw80hE4Q&m=ivUR0FnAHdNwIEVfI256EXxk4y8UQELfZv-zc4r1eVI&s=AmL3TzRPWWisuWbBuxgOfFqNejtPrisXYC6GSzprlGI&e= > > > > > > > > > > > > _______________________________________________ > > > > Pd-dev mailing list > > > > [email protected] > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.puredata.info_listinfo_pd-2Ddev&d=DwIFaQ&c=-35OiAkTchMrZOngvJPOeA&r=XprZV3Fxus2L1LCw80hE4Q&m=ivUR0FnAHdNwIEVfI256EXxk4y8UQELfZv-zc4r1eVI&s=AmL3TzRPWWisuWbBuxgOfFqNejtPrisXYC6GSzprlGI&e= > > > > > > > > -- >
FM-instability.pd
Description: Binary data
_______________________________________________ Pd-dev mailing list [email protected] https://lists.puredata.info/listinfo/pd-dev
