@jamcultur I am wondering if there is a quick way to search through the files using a text based search. I know you can open Pd files as text files and there is a syntax to them. I think you can edit them as well and produce working Pd patches.

So here are the results from a search on the MacOS cli:
mimba-092b % grep "sin" *
mba.pd:#X obj 1201 543 r $1-mmbsintkeybp;
mba.pd:#X obj 319 354 r $1-mnbsinidelall;
mba.pd:#X obj 347 454 r $1-$2-mnbsinidelalldd;
mba.pd:#X obj 348 493 r $1-$2-mnbsinidelallml;
mba.pd:#X obj 1704 4618 r $1-mmbsinidelsensi;
******************* MY ADDED TEXT TO HIGHLIGHT THE LINE*****************************
mba.pd:#X obj 595 437 expr sin(w$0)sinh(ln(2)/2$f1w$0/sin(w$0));
MY ADDED TEXT TO HIGHLIGHT THE LINE**********
mba.pd:#N canvas 0 83 1920 997 sineIm 0;
mba.pd:#X restore 160 538 pd sineIm;
mba.pd:#X obj 323 536 sin;
mba.pd:#X text 505 456 alpha = sin(w0)/(2Q);
mba.pd:, peak gain = Q) b0 = sin(w0)/2 = Qalpha b1 = 0 b2 = -sin(w0)/2 =
mba.pd:#X text 530 678 b0 = sin(w0)/2 = Qalpha;
mba.pd:#X text 530 759 b2 = -sin(w0)/2 = -Qalpha;
mba.pd:#X obj 125 383 sin;
mimba.pd:#X msg 59 488 ; $1-wtable-ramp3 sinesum 515 1 -1 0.5 -0.5 0.33 -0.33
mimba.pd:#X msg 51 296 ; $1-wtable-ramp2 sinesum 515 1 0 -0.111111 0 0.04
mimba.pd:#X msg 52 88 ; $1-wtable-ramp1 sinesum 515 1 0.5 0.33 0.25 0.2 0.16
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X msg 875 315 ; $1-wtable-z1b sinesum 515;
mimba.pd:#X obj 147 791 list prepend sinesum 1024;
mimba.pd:#X text 509 510 rising saw;
mimba.pd:#X text 35 274 soft sine 2;
mimba.pd:#X text 20 201 soft sine 1;
mimba.pd:#X msg 521 916 ; 1-addiwaves write sine-noisy1.txt;
mimba.pd:#X msg 522 853 ; $1-addiwaves read sine-noisy1.txt;
mimba.pd:#X text 165 339 (3) soft sine 3;
mimba.pd:#X text 1334 643 soft sine 1 with octave louder;
mimba.pd:#X obj 171 780 list prepend sinesum 1024;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 147 791 list prepend sinesum 1024;
mimba.pd:#X obj 679 864 list prepend sinesum 1024;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X text 193 158 0 soft sine 4;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 42 374 s $1-mmbsintkeybp;
mimba.pd:en filders te 'clearen' in tien voices tegelijkertijd. Oplossing: tussen
mimba.pd:elke stem bv. 100ms steken , zie oplossing aan de rechterkant van
mimba.pd:#X msg 1041 471 ; 1-addiwaves write sine-noisy1.txt;
mimba.pd:per wavetable)(de langste sinesum messages -zoals 37- hebben nu 36
mimba.pd:#X text 36 318 alle lage tonen maximum 36 harmonieken in sinesum ,
mimba.pd:doen met global previous pitch (en toggle voor aanpassing van vorige
mimba.pd:#X msg 59 488 ; $1-wtable-ramp3 sinesum 515 1 -1 0.5 -0.5 0.33 -0.33
mimba.pd:#X msg 51 296 ; $1-wtable-ramp2 sinesum 515 1 0 -0.111111 0 0.04
mimba.pd:#X msg 52 88 ; $1-wtable-ramp1 sinesum 515 1 0.5 0.33 0.25 0.2 0.16
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 147 791 list prepend sinesum 1024;
mimba.pd:#X text 509 510 rising saw;
mimba.pd:#X text 177 311 soft sine 2;
mimba.pd:#X text 162 238 soft sine 1;
mimba.pd:#X msg 521 916 ; 1-addiwaves write sine-noisy1.txt;
mimba.pd:#X msg 522 853 ; $1-addiwaves read sine-noisy1.txt;
mimba.pd:#X text 227 363 (3) soft sine 3;
mimba.pd:#X obj 171 780 list prepend sinesum 1024;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 147 791 list prepend sinesum 1024;
mimba.pd:#X obj 679 864 list prepend sinesum 1024;
mimba.pd:#X obj 100 1319 r $1-mnbsinidelall;
mimba.pd:#X obj 624 1290 r $1-mmbsinidelsensi;
mimba.pd:#X obj 11 591 hsl 128 15 0 508 0 0 $1-mnbsinidelall $1-mnbrinidelall
mimba.pd:#X obj 829 17 bng 15 250 50 0 $1-mmbsinfopifqin empty i 17 7 0 10
mimba.pd:(read) variations ; 31 = read once with small sine (read) variations
mimba.pd:; 32 = read once with bigger (read) sine variations ; 33 = normal
mimba.pd:#X obj 306 22 r $1-mmbsinfovelom;
mimba.pd:#X obj 555 28 r $1-mmbsinfopifqin;
mimba.pd:#X obj 29 231 r $1-mmbsinfodetails;
mimba.pd:#X obj 416 137 bng 15 250 50 0 $1-mmbsinfovelom empty i 17 7 0 10
mimba.pd:#X obj 907 94 hsl 121 10 -1 1 0 0 $1-mmbsinidelsensi $1-mmbrinidelsensi
mimba.pd:the pitch detuning caused by bypassing/crossfading APF delay., f 66
mimba.pd:#X obj 22 622 r $1-mmbsinfoafterfiltrin;
mimba.pd:#X obj 1016 539 bng 15 250 50 0 $1-mmbsinfodetails empty xtra_details
mimba.pd:#X obj 1650 601 bng 15 250 50 0 $1-mmbsinfoafterfiltrin empty i 17
mimba.pd:; mmbsimplvl ; mmbsxfadeapf ; mmbsxnoilop ; mnbsinidelall ; mmbsxnoistaval
mimba.pd:'drastische oplossing: default naar alle voicespecific send-receives
grep: presets: Is a directory

I am going to refine the search method to include the relationship/equation from the error message to see what happens.

@Glop-Glop said:

I want to coordinate two arrays : tab24 which has 24 steps and tab_var which has 1, 2, 3, 4, 6 or 8 steps.
In a first time, I want to move the value of the 0 stept of tab_var graphically and report it on step 0 of tab24.
Does anyone have a solution without using a bang to let the value get out ?

Basically... no. If there are any messages emitted by arrays when they're changed graphically, the documentation is so well hidden that I guess it doesn't exist.

The only way I can think of is to poll the array repeatedly.

26-0202-array-sync.pd

I wouldn't call this a beautiful solution -- perhaps someone else knows some array messaging magic that I wasn't able to find.

hjh

So, how about we discuss all these options and how they relate to each other? Anyone with me?

Let me talk about FOF here... Basically, it's a hard-synced oscillator! And I always thought hard synced oscillators sounded really nice for forcing harmonics into a fundamental pitch, and that's it... Ok, there's more to that of course, and it also passes through a decay envelope, which can be implemented with [rpole~], here's a minimal Pd patch of this main core.... it uses objects from ELSE of course... specially for making hard sync easier. Below, 150 is 'f0' (fundamental), 390 is center/formant frequency, and 100 is bandwidth, all in Hertz...

But then, the envelope grain might and can overlap. The Csound implementation is pretty much "Csoundy", ridiculously complicated with way too many parameters and options, not to mention a seemingly inexplicable low output that forces you to multiply it by a ridiculously large and arbitrary number. Besides the decay envelope, it also applies another envelope on top of it, which might be pretty useless when the first envelope simply dies before it, but it can be useful to apply an attack phase. What a mess! The FAUST implementation is simpler and makes more sense!

The Formlet UGen from supercollider implements a filter with attack and decay, and it rings, so you don't need the hard synced oscillator. Plus, it can "overlap" grains quite seeminglessly. It's pretty clever and it made its way back into Csound, where it's called fofilter.

What makes no sense for me is the "BandWidth" parameter in FOF (or using Formlet). In Pd's examples we have the paf like patches and the bandwidth makes actual sense because it represents a bandwidth of partials over the center frequency. In FOF we don't have that and the larger the bandwidth, the thinner the sound actually is because the decay is faster.

Now, i also ported the Formant UGen and this is what it is, basically, as a patch, guess what? Yup, another hard synced oscillator, basically, being enveloped, so... I guess it relates to the Fof approach... but not quite... one way or another, there's no reference in the docs or code of where it comes from and maybe I should ask the SC Forum (again) Below, BW ratio means the ratio of bandwidth according to the fundamental, so '3' is '150' hz. This parameter to me feels like controlling the "brightness" anyhow.

And there are also the FM approach, the paf, the VOSIM, not to mention the filterbank approach... Gosh, what a mess... I guess I know why I procrastinated so much to finally deal with this... but it's time and now I'll map them all and see how they relate to each other. And I'll sort it all out in my Live Electronics Tutorial...

I'm still thinking what are the objects that make sense actually including in ELSE...

@jameslo said:

Per tua informazione, sai come applichi il grain envelope all'output di snake~, 1 per canale? Potresti anche applicarlo a snake una sola volta, in modo che abbia effetto su entrambi i canali. È proprio questo lo scopo di snake~: ridurre le duplicazioni inutili.

left one is correct, right? so the grains on the right are basically passing through without being enveloped, right?

Ok, the cat is out of the bag --> https://github.com/porres/pd-else/releases/tag/1.0-rc13 I'm officialy announcing the update and uploaded binaries to deken for mac (intel/arm), Win and Linux. It all looks ok but tell me if you see something funny please. There's also a raspberry pi binary but not working 100%yet and we'll still look into that. Hopefully someone could help me/us with it. I might make another upload just for the pi later on if/when we figure it out. Find release notes and changelog below.

RELEASE NOTES:

Please support me on Patreon https://www.patreon.com/porres I'll now try to add special content for subscribers. You can follow me on instagram as well if you like... I'm always posting Pd development stuff over there https://www.instagram.com/alexandre.torres.porres/

It's been a little bit over 7 months since the last update and I almost broke the record for taking too long to release an update (which had happened in my previous update). So yeah, there's just too much to talk about! I guess the delays in releasing updates is because it's been a little tricky and hard to sync the release cycles of ELSE with PlugData, which includes ELSE in its download.

Plugdata 0.9.2 should come out soon with ELSE RC13 and it's supposedly the last update before 1.0.0, so I've heard. And the plans was to get to that still in 2025! This means ELSE could be at its last "Release Candidate" phase as I'm aiming to sync the final release with PlugData. Until then, I'll still make breaking changes and I can't wait until I can't do that anymore as I really feel bad. On the other hand, it's kind of inevitable when I'm always adding new stuff and redesigning and reconfiguring objects to include more functionalities. And I always got a lot of new stuff! So I'm thinking that I will eventually try some mechanism like Pd's compatibility flag or something. I'll try to come up with something like that in the next update.

This update has 22 new objects for a total of 573 and 26 new examples in my tutorial for a total of 554 examples. Let's dive into the highlights (see full changelog below after the release notes).

• Multichannel Support: Last release had 92 MC aware objects, now it's 139! Over a 50% increase that include old and new objects (all the new ones have been coming with MC support). Virtually all oscillators and envelope generators now have MC support, plus some other random ones. Let me highlight the new [lace~]/[delace~] objects that are 'MC' tools that perform interleave/deinterleave in Multichannel connections. My bare minimum number of objects "to start with" would be at least a bit over half the number of signal objects. That was my target for 1.0! ELSE right now has 319 signal objects, so that'd be at least 160. I will definitely pass this milestone in the next update. I guess a good number of MC objects would be around 75% of the signal objects. I will aim for that as soon as I can. Some objects simply can't be MC at all, so 100% will never be the case, but maybe an ideal 90% eventually? We'll see... I am just proud and happy that ELSE is taking such a big jump on MC awareness in less than a couple years.

• Envelope generators ([adsr~]/[asr~]/[envgen~]/[function~]) now have more curve options. For [adsr~]/[asr~] the default is now a new log curve that you can set the curve parameter (and was 'stolen' from SuperCollider). A new [smooth~] family of objects perform the same kind of curved smoothening for alternating inputs - [envgen~] and [function~] also have that but also '1-pole' filtering, 'sine' and 'hann' curves. You can now trigger [adsr~] and [asr~] with impulses.

• The [play.file~] object now supports even more file formats besides MP3 and stuff. Hey, you can even stream the supported formats from weblinks! The [sfload] object (which loads files into arrays) also gained support for more formats and can download from weblinks as well! It also has a new threaded mode, so loading big files won't choke Pd. It now also outputs the file information, which is a way to tell you when loading finished in threaded mode. The [sample~], [player~], [gran.player~] and [pvoc.player~] objects are now also based on [sfload], so they support all these file formats!!! Now [sample~] and [tabplayer~] are integrated in a way that [tabplayer~] is always aware of the sample rate of the file loaded in [sample~] (so it reads in the "correct speed"). A new [sfinfo] object is able to extract looping regions and instrument metadata information from AIFF files (which is something I wanted for ages) - it should do more stuff in the future.

• [knob] has become the ultimate featured bloated creep GUI I always feared and avoided. MAX is envy! but I'm happy with this structure and I want to replicate in other GUIs in the future (yeah, I got plans to offer alternatives to all iemguis). I wanna highlight a new 'param' symbol I added that allows you to remotely set a particular method in an object, so you don't to connect to a "method $1" message and you can even do this wirelessly with a send symbol. [knob] now also acts like a number box, where you can type in the value, which may also be displayed in different ways or the value can be sent elsewhere via another send symbol so you can temper with it using [makefilename] or [else/format]. I've been using this for the MERDA modules and it's really cool.

• We finally have a [popmenu] GUI object! This was in my to do list forever and was crucial to improve the MERDA modules to set waveforms, instruments and whatnot.

• Let's about MERDA, the "Modular Euroracks Dancing Along" subset of abstractions in ELSE. It was first released in the last update and it's been driving lots of the development in ELSE as you can see. I now added a MIDI Learn feature for all knobs that feels great and quite handy! There are many fixes and improvements in general and some new modules. I wanna highlight the new [sfont.m~] module, which loads "sound font" banks and you can just click on a [popmenu] to choose the instrument you want. The default bank has numerous (hundreds) options and also comes with PlugData. The sequencer module [seq8.m~] was rather worthless but it's now a whole new cool thingie. It allows you to set pitches with symbols and even has quarter tone resolution. I added a right outlet to send impulses to trigger envelopes and stuff (there's still more stuff of course, see full changelog below).

• There are newly designed/renamed/recreated [resonbank~]/[resonbank2~] objects that are well suited for Modal Synthesis.

• What actually drives my development is my Live Electronics tutorial, which got a fair upgrade with a new chapter on Modal Synthesis amongst other things, such as new subtractive synthesis examples and a revision of envelope generators with examples on AHDSR and DAHDSR - by the way, there are new gaterelease~/gatedelay~ objects for handling envelopes (and other processes).

• I have to thank some people. Tim added 'zoom' to the [pic] object, as well as an image offset. Tim also implemented a new and better technique for bandlimited oscillators. Ben Wesh gave me a new [scope3d~] GUI object, pretty cool, that plots an oscilloscope in 3 dimensions, which is coded in LUA - and ELSE has been carrying a modified version of [pdlua] because it now depends on it for a couple of GUIs. Tim and Ben made many improvements to [pdlua] (as well as Albert Graef, of course).

• For more new objects, let me also tell you about the simple and cool [float2imp~], that is based on [vline~] and can convert floats to impulses with sample accuracy (don't know why I didn't think of that earlier). A new [tanh~] object has Multichannel support. A bit earlier I made an update to Cyclone that actually "borrows" and includes this one from ELSE instead of its original one (which does not have Multichannel support). PlugData users will load the one from ELSE. This is another tiny step that sort of integrates ELSE and Cyclone, specially for PlugData users.

happy patching.

CHANGELOG:

LIBRARY:

Breaking changes:

• [adsr~]/[asr~]: now a gate off before reaching the sustain point does not start the release right away (this allows you to trigger it with impulses). There's a new mode just for immediate release. There's a new exponential setting for curve factors, the old 'log' mode is renamed to 'lag' as it's the same as used in the [lag~] object. For [adsr~], a bang now is not "retrigger", but an impulse at control rate, there's a new 'retrigger' message for control rate retriggering (and now it only retriggers if the gate is on). For [asr~] a bang now also works like an impulse.
• [sample~]: no more 'load' message, args to 'open' message changed, size is now only in 'ms'.
• [format]: outputs are now always symbols, before you could get float outputs. Also, we just have a simplified symbol output, no more lists or anythings. Hopefully I'll be able to get the 'list' output back, but it involved some bugs that I couldn't fix so I just removed it. You cannot use bangs and lists in secondary inlets no more (this is cylone/max crappy paradigm we don't want here). Bang method was actually removed as well.
• [pack2]: no more support for anythings, also no more support for lists in secondary inlets and output has a list selector (I wanna make this more Pd like and not a silly clone from MAX's [pak], cause fuck MAX).
• [merge]/[unmerge]/[group]: no more '-trim' flag (again, respecting pd's usual list paradigm), in [merge] now there's no more 'hot' argument and a bang now represents an empty list and inlets initialized with empty lists
• [mono]: 1st argument is now 'glide' in ms.
• [sfont~] now uses 'mma' for bank selection (this alters how CC messages set the bank number).
• [player~]/[play.file~]: 'open' message does not play files right away anymore.
• [tabplayer~]/[player~]: play message without args now play at the default settings (whole file at regular speed).
• [envgen~]: removed the 'maxsustain' parameter, use the new [gaterelease~] or [gaterelease] objects instead. Removed the rightmost inlet just to set envelopes, now a list input only sets the envelope and doesn't trigger it. The 'set' message is then removed.
• [envgen~]/[function~]: simplified and got rid of '-exp' flag and message, also deleted 'expl' and 'expi' messages. A new 'curve' and cimpler message sets exponential factors for all or individual segments, and includes more curve formats.
• [knob]: 'esc' key now deactivates the object. The 'ticks' message is renamed to 'steps' and there is a new 'ticks' message that toggles showing ticks on and off. The 'start' message has been renamed to 'arcstart'. The 'outline' message has been renamed to 'square' for better clarity. Design changed a bit to make it like it is in PlugData (they won), so we now fill the whole background color when in 'square mode' and the knob circle has an 85% proportion in this case inside the full 100% square size (so it grows bigger when not in 'square' mode). Now, by default, the GUI is in a new 'loadbang' mode (I don't think this will influence old patches). I'm afraid some old patches might behave really weird since I added a lot of new stuff. I changed the 'load' message behaviour to not update the object (this can arguably be considered a bug fix).
• [wavetable~], [bl.wavetable~] and [wt2d~]: 'set' message now sets frequencies because of the MC support in [wt~] and [wt2d~], while there's a new 'table' method to set the table name.
• [gbman~]/[cusp~] list method is now for MC, old list method is now renamed back to an old 'coeffs' method.
• [f2s~]/[float2sig~] default value is now 10 ms.
• [op] now behaves like [*~] where the smaller list wraps til reaching the size of the longer one.
• [list.seq] does not loop anymore by default.
• [impseq~] list input removed, use the new [float2imp~] object to convert floats to impulses.
• [resonant~] now has 'q' as the default.
• [resonant2~] has been removed.
• [decay2~] has also been removed ([asr~] much better).
• [vcf2~] has been renamed to [resonator2~].
• [resonbank~]/[resonbank2~] have basically been deleted and replaced by new objects with the same name... [resonator~] is based on a new [resonator~] object which is similar to [resonant~] and [resonbank2~] is now based on [resonator2~] (old [vcf2~] instead of [resonant2~] that got deleted). These are well suited objects for Modal Synthesis.
• [oscbank~] now uses a 'partial' list and not a frequency list. The freq input now defaults to '1' and this makes [oscbank2~] completely obsolete.
• [oscbank2~] has been deleted since it became completely obsolete.
• [sfload] load message changed the behaviour a bit.

Enhancements/fixes/other changes:

• [adsr~]: We have now a new mode for immediate release (see breaking changes above, I'm not repeating it). Fixed ADSR signal inputs (it was simply not really working, specially for linear). Fixed status output for MC signals. There's a new curve parameter that allows you to set the curvature.
• [asr~] I actually just made the new [adsr~] code into a new [asr~] code as a simplified version (as it was before)... so it's got the same impromevents/fixes.
• [play.file~]: added support for more file formats and even weblinks for online streaming!
• [sfload]: added an outlet to output information, added threaded mode, added support for more file formats and even weblinks for downloading.
• [sample~], [player~], [gran.player~] and [pvoc.player~] are now also based on [sfload], so they support more file formats!
• [sample~]: improved extension management with [file splitext].
• [sample~] and [tabplayer~] now are automatically integrated in a way that [tabplayer~] is always aware of the sample rate of the file loaded in [sample~], so it automatically adjusts the reading speed if it is different than the one Pd is running with.
• [numbox~]'s number display is not preceded by "~" anymore (that was just kinda stupid to have).
• [format]: fixed issues where empty symbols and symbols with escaped spaces didn't work. Added support '%a' and '%A' type. Added support for an escaped 'space' flag. Improved and added support for length modifiers. Improved syntax check which prevents a crash. Improved documentation.
• [knob]: added new 'param', 'var', 'savestate', 'read only', 'loadbang', "active", "reset" and 'ticks' methods. Added the possibility to type in number values and also modes on how to display these number values, plus new send symbols for 'activity', 'typing', 'tab' and 'enter'. New design more like plugdata. Changed some shortcuts to make it simpler. If you have the yet unreleased Pd 0.56-0 you can also use 'double clicking' in the same way that works in PlugData. Properties were also significantly improved (I'm finally starting to learn how to deal with this tcl/tk thingie). Yup, a lot of shit here...
• [autofade2~]/[autofade2.mc~]: fixed immediate jump up for 0 ramp up.
• [synth~]: fixed polyphony bug.
• [metronome~]: fixed bug with 'set' message.
• [midi2note]: fixed range (octaves 0-8).
• [pulsecount~]: fixed reset count to not output immediately, added bang to reset counter at control rate
• [click]: fixed regression bug where it stopped working.
• [else]: new 'dir' method to output ELSE's binary directory in a new rightmost outlet. The print information also includes the directory.
• [pic]: added zoom capability finally (thanks to tim schoen) and added offset message (also thanks to tim).
• [store]: added 'sort' functionality.
• [scales]: fixed octave number argument. Added functionality to allow octave number as part of the note symbol.
• [mono]: added 'glide' parameter, as in [mono~].
• [pluck~]: fixed list input.
• [rescale]/[rescale~]: added a "reverse log" mode.
• [limit]: added a new second ignore mode.
• [graph~]: added an external source input for plotting the graph and a 'clear' message.
• [canvas.setname]: added a new argument for "abstraction mode" and methods to set name, depth (and mode).
• [midi.learn]: added a new argument for "abstraction mode", fixed 'dirty' message sent to parent.
• [brickwall~]: fixed initialization.
• [list.seq]: added a loop mode and a 2nd outlet to send a bang when the sequence is done.
• [delete]: fixed index for positive numbers.
• [dust~]: added 'list', 'set' and '-mc' flag for managing the already existing Multichannel capabilities.
• Thanks to Tim we have many fixes and a whole new technique for band limited oscillators. Now [bl.saw~], [bl.saw2~], [bl.vsaw~], [bl.square~], [bl.tri~], [bl.imp~] and [bl.imp2~] have been redesigned to implement elliptic blep, which should provide better anti-aliasing.
• [parabolic~] now uses and internal wavetable for more efficiency.
• [resonant~]: added 'bw' resonance mode.
• [lowpass~]/[highpass~]: added 't60' resonance mode.
• [quantizer~]/[quantizer]: added a new mode, which combines floor (for negative) and ceil (for positive) values.
• [crusher~]: now uses the new [quantizer~] mode from above (arguably a breaking change).
• [envgen~]: fixed a bug (actually a misconception) where ramps started one sample earlier. Fixed 0-length lines. Added a possibility to set time in samples instead of ms. Maximum number of lines is now 1024. Added loop mode. Added many curve options (sin/hann/log curve/lag).
• [function~]: Added many curve options (sin/hann/log curve/lag).
• [The out~] family of abstractions now use [bitnormal~] so you won't blow your speakers beyond repair in edge cases.
• [trig.delay~]/[trig.delay2~]: fixed bug where impulse values different than '1' didn't work.
• Added MC support to: [trig.delay~], [trig.delay2~], [gatehold~], [vca.m~], [gain2~], [decay~], [asr~], [envgen~], [function~], [bl.osc~], [bl.saw~], [bl.saw2~], [bl.vsaw~], [bl.square~], [bl.tri~], [bl.imp~], [bl.imp2~], [imp2~], [tri~], [saw~], [saw2~], [vsaw~], [square~], [pulse~], [parabolic~], [gaussian~], [wavetable~], [wt2d~], [randpulse~], [randpulse2~], [stepnoise~], [rampnoise~] [pink~], [gbamn~], [cusp~], [gray~] and [white~].
• Also added MIDI input and soft sync to [imp2~], [tri~], [saw~], [saw2~], [vsaw~], [square~], [pulse~], [gaussian~] and [parabolic~].
• [wavetable~] and [wt2d~] gained args to set xfading.
• Updated pdlua to 0.12.23.
• M.E.R.D.A: Added MIDI-LEARN for all modules (this is only for the knobs). Replaced some number boxes that were attached to knobs by an internal number display mechanism (new feature from knob). Improved interface of [gendyn.m~]. Preset/symbol name fixes to [flanger.m~]. Now we have automatic MIDI mode detection for [plaits.m~] and [pluck.m~] when no signals are connected (still trying to get plaits right, huh? Yup! And bow MIDI input with monophony and trigger mode has been fixed in [plaits.m~]). Added MC support to [vca.m~]. Increased range of [drive.m~] down to 0.1. Changed some objects to include the new [popmenu] GUI. [vco.m~] now uses the new MC functionalities of oscillators and doesn't need to load abstractions into [clone], I hope it makes this more efficient and clean. The [seq8.m~] module was worthless and got a decent upgrade, it's practically a new module. Added new modules (see below). Note that MERDA is still at alpha development phase, much experimental. Expect changes as it evolves.
• 22 new objects: [float2imp~], [lace], [delace], [lace~], [delace~], [gatehold], [gatedelay],[gatedelay~], [gaterelease~], [gaterelease], [popmenu], [scope3d~], [tanh~], [resonator~], [sfinfo], [smooth], [smooth2], [smooth~], [smooth2~], [dbgain~], [level~] plus [crusher.m~], [sfont.m~] and [level.m~] MERDA Modules.

Objects count: total of 573 (319 signal objects [139 of which are MC aware] and 254 control objects)!

• 323 coded objects (210 signal objects / 113 control objects)
• 227 abstractions objects (87 signal objects / 140 control objects)
• 23 MERDA modular abstractions (22 audio / 1 control)

TUTORIAL:

• New examples and revisions to add the new objects, features and breaking changes in ELSE.
• Added the MERDA modules into the examples for reference.
• Revised section on envelopes.
• New subtractive synthesis examples.
• New chapter on Modal Synthesis.
• Total number of examples is now 554! (26 new ones)

SingingBowl.pdf singingBowl1.pd

Hi everyone.
I have been thinking about creating a pd patch that is a physical model of a singing bowl or a crystal sound bath type bowl for awhile.
I found a paper on the internet about the physical modeling of a singing bowl.

I uploaded a patch trying to use some of the info in the paper. To use the patch you need the else library to use the compress~ and resonator2~ objects.

The paper says the bowl resonated at 186, 551 1007 1627 and 2337 Hz. I tried to scale the amplitude from the paper to something that would work. I looked at Figure 2 in the paper for info on how the different frequencies decayed.

I added a frequency close to each frequency to get some beating. The paper says that due to the imperfections of a singing bowl each frequency has some ringing to achieve that.

The patch I created kind of sounds like a singing bowl.
Does anyone have ideas to improve on to this? I was also thinking to have each frequency go into a bandpass filter so I can control it's bandwidth, but that seems like a lot of extra work and objects.

Thank you for any input.

Nick

@whale-av Thanks.

It seems the MIDI clock patch does not reset properly. Or, there should be a delay of some sorts when syncing to MIDI clock.

My apologies, this went a bit too far out of scope.

I can nudge the MIDI clock input to 0, and sync it properly.

Just need to figure out how to nudge it automatically.

Thanks a lot,
Raymond

EDIT:

I am resetting the PPQN counter to 0 on FA (MIDI clock PLAY).
But this does not sync properly.
Clock SOURCE according to MIDI spec should give some delay for the target to sync (1ms). Figuring out how to implement that....
24 is a weird number

Hey all, I recently switched from Windows to macOS and really enjoy patching there a lot. There's one thing that's quite annoying though and after lots of useless googling and support chats, I felt like people here might have answers:

I built quite a few abstractions for my own use and some of them follow names like perlin.3d~. To keep files and folders a little organized, I place abstractions in folders with the same name. So in this case, the actual abstraction is placed in path_to_externals/perlin.3d~/perlin.3d~.pd.

This worked pretty well for my Windows setup. And it also basically works on macOS. But I'm using Dropbox to sync my Pd stuff and in this case, syncing doesn't work - the folder doesn't sync back to Dropbox and Finder alerts inside the folder that Dropbox encountered an unexpected error. items may be out of date. Dropbox support says it's an Apple problem and Apple until now says this is "somehow" connected to temporary file conventions and they can't do anything about it.

So here are my questions:

• Are these names bad practice for Pd abstractions?
• Is there a better way to organize them other than through folders like this?
• Am I the only one experiencing this? (Please no!)

Been working on this for awhile, only this week had a chance to record the material.

[abl_link~] (in Deken) has existed for awhile for Ableton Link sync. PlugData is more recent for Pd to run in a DAW, with timeline sync.

With both approaches, however, you'll crash into a handful of problems whose solutions are not at all obvious. This project is all about: What does it really take to have Ableton Link, or DAW timeline, sync working properly. 49 minutes a bit longer than I expected.

(This is exposing some rough edges in Pd's interfaces. Unfortunately rough edges can end up being a feedback loop -- something is hard, so people avoid it, and as a result, it remains hard and people continue to avoid it. I hope this will break the feedback loop in some crucial places and make these types of sync more approachable.)

hjh

PS Note one correction in the video's description.

HI All,

Thanks to all'y'all that responded so quickly with very good guidance. And especially thanks to 'whale-av' for that little bit of brilliant code: [once]. I was able to integrate it and it now works.

The pitch-harmonic content is specific to a dramatic song cycle I am composing, entitled NEUROTICA. In this song that I am composing currently, there is a guitar part that plays a melody on which the guitarist (me) is invited to improvise at times throughout the piece. The pitch content of the melody is: F, G, Ab, A, Bb, B, C, Db, Eb, and E.

This content surely has different pitch centers, under which the chords that I have constructed more/less 'land' when improvising - so cool! If you look inside the subpatches, you will find that there are randomized choices for chords to harmonize the same pitch. For input, I am using a basic University Guitar to MIDI converter, the G2M, made by SONUUS (monophonic, yet chromatic input), but you could plug in any controller and play monophonically. For output, I am routing the midi to an FM8 synth that comes with Kontakt.

NEUROTICA SONG SOLO HARMONIZER.pd

Once last question, Whale-av: In which PD folder do I put your object? You will notice that made a subpatch after copy-pasting the content of your object to make it work. (Please forgive me, as I do not use PD all that often except for very specific creative projects, and I forget the directories/paths.)

Thanks again for all the help! And for those curious, enjoy!

All best, and happy holidays,
D