Folks, we're on a roll debating all things related to Pd documentation here and there and I'm now focusing on the Pd FLOSS Manuals issue.

Pd has this very famous and long lasting FLOSS Manual. It's old and it tells you how to instal Pd Extended 0.39! So, it's from the extended era and still references to 'extended objects'. For what I see, it was a Manual that came to be in the Extended era as a Manual to it. Back in the day we basically all used just Extended anyway and were mostly oblivious to Pd Vanilla and its manual.

And by Pd's manual, I mean http://msp.ucsd.edu/Pd_documentation/index.htm - I know that's called 'Pd Documentation', and that it is confusing, cause it actually is an 'html Manual' and it refers to itself as "this html manual". Anyway, this is also something I brought up on github and is not the issue here..  
The point is that there's a conflict and I guess this made sense then, but it's a problem nowadays. A documentation noise problem. Lots of people seem to get to it and consider it "the manual for Pd". We're still struggling with a post Pd Extended issue and what was consolidated in its era but now sits as ruins. Actually, Pd Vanilla's manual also refers to FLOSS Manuals. But these days we have something weird, which is simply the fact that Pure Data has these two manuals. One is the official one, included as part of Pd Vanilla and its documentation, and this other one, which is terribly outdated and actually refers to this unsupported and abandoned fork of Pd.

But the point is, one software cannot have two concurring Manuals, even if both are up to date - that'd be silly. The point of FLOSS is to provide the one and only official and single Manual for a piece of software. See the problem? Csound uses FLOSS Manuals as a place to provide its official manual. It's clearly linked in csound.com. Csound also has the 'Canonical Csound reference manual', which is actually something else and not to be confused with "The" manual they provide in FLOSS.

So, my point is we have to get rid of one of them and have a single official one.

Should we then remove the included and official manual from Pd and 'move it' to FLOSS and completely overhaul that online version?

Or just get rid of the FLOSS version? Well, that is there, and people know it. Burn it down, purge and disappear with it would be bad.

Well, I don't know, so I'm asking...

Another scenario is that FLOSS can still be around, of course, but as a museum piece, for those interested in web archeology, as extended is now an archeological piece of software. No one touches it, it stays there, but we try to make it clear how that is an old, outdated, unofficial and that Pd has its own 'real manual. This would help a lot. Or... also, treat it for what it is, a manual reference for Pd Extended, not Vanilla, and make it clear how Pd Extended is abandoned and so is this manual.

Other than these, the only option I see is we maintain and update these two manuals somehow. And I already said how I think that's pointless. I also don't know who'd do that... but maybe there'd be a way to manage them as two clearly distinct guides. One would be the 'Canonical Vanilla Manual' and the other could be 'The Pure Data Manual' (or some other name)? The question would be, why to do that? What is the advantage in keeping another FLOSS version around?

The thing I can think people like about the FLOSS version is:

• A: A friendlier look for beginners;
• B: A nice beginner level tutorial;
• C: Support for many externals, external libraries, how to use Arduino and stuff (more as a tutorial than a 'manual');

These can all be compensated. With 'A)', we can try and make the Pd manual look nicer maybe? As for the rest, what really seems to be the substance of this is the fact that it serves as a tutorial.

Well, a tutorial is not necessarily a "Manual".

We can add tutorials to Vanilla too... actually, even though it's based on Extended, many of the examples there are 'vanilla', so they can be easily ported and shipped as part of Vanilla!

As for tutorials that use externals. Well, they would really benefit from an update. But a tutorial is a tutorial, this could live somewhere else.

By the way, tutorials can easily be uploaded to deken and be available from there. You'd have a tutorial that relies on externals, but that's ok too (my live electronics tutorial comes as part of the ELSE download)... just give instructions in the tutorial on how to install the needed libraries from deken as well...

But if the case is made that we should really keep FLOSS and update it. Well, maybe we could manage and do that, taking care on how to not overlap even know I don't know who'd do it, but it'd mean completely rewrite from scratch and get rid of some of the stuff. That's bad too, as the old version would be lost (so have it sit as an 'old extended manual'?).

So, in short, possible scenarios include:

1. Forget about floss, tell it's outdated (rename it to pd extended manual maybe), focus on Vanilla's manual. Bring stuff we miss and like from FLOSS to current Pd in some new form.
2. 'Move' Pd's manual to a new FLOSS incarnation
3. Keep and manage two versions

My thoughts on these are here, and I think the best scenario is number "1)"

Any other thoughts?

Cheers

Hey Seb!

I appreciate the feedback

The routing I am not so concerned about, I already made a nice table based preset system, following pretty strict rules for send/recives for parameter values. So in theory I "just" need to get the data into a table. That side of it I am not so concerned about, I am sure I will find a way.

For me it's more the decoding of the sysex string that I need to research and think a lot about. It's a bit more complicated than the sysex I used for Blofeld.

The 32 voice dump confuses me a bit. I mean most single part(not multitimbral) synths has the same parameter settings for all voices, so I think I can probably do with just decoding 1 voice and send that data to all 16 voices of the synth? The only reason I see one would need to send different data to each voice is if the synth is multitimbral and you can use for example voice 1-8 for part 1, 9-16 for part 2, 17-24 for part 3, 24-32 for part 4. As an example....... Then you would need to set different values for the different voices. I have no plan to make it multitimbral, as it's already pretty heavy on the cpu. Or am I misunderstanding what they mean with voices here?

Blofeld:
What I did for Blofeld was to make an editor, so I can control the synth from Pure Data. Blofeld only has 4 knobs, and 100's of parameters for each part.... And there are 16 parts... So thousand + parameters and only 4 knobs....... You get the idea

It's bit of a nightmare of menu diving, so just wanted to make something a bit more easy editable .

First I simply recorded every single sysex parameter of Blofeld(100's) into Pure data, replaced the parameter value in the parameter value and the channel in the sysex string message with a variable($1+$2), so I can send the data back to Blofeld. I got all parameters working via sysex, but one issue is, that when I change sound/preset in the Pure Data, it sends ALL parameters individually to Blofeld.... Again 100's of parameters sends at once and it does sometimes make Blofeld crash. Still needs a bit of work to be solid and I think learning how to do this decoding/coding of a sysex string can help me get the Blofeld editor working properly too.

I tried several editors for Blofeld, even paid ones and none of them actually works fully they all have different bugs in the parameter assignments or some of them only let's you edit Blofeld in single mode not in multitimbral mode. But good thingis that I actually got ALL parameters working, which is a good start. I just need to find out how to manage the data properly and send it to Blofeld in a manner that does not crash Blofeld, maybe using some smarter approach to sysex.

But anyway, here are some snapshots for the Blofeld editor:
Image of the editor as it is now. Blofeld has is 16 part multitimbral, you chose which part to edit with the top selector:

Here is how I send a single sysex parameter to Blofeld:

If I want to request a sysex dump of the current selected sound of Blofeld(sound dump) I can do this:

I can then send the sound dump to Blofeld at any times to recall the stored preset. For the sound dump, there are the rules I follow:

For the parameters it was pretty easy, I could just record one into PD and then replace the parameter and channel values with $1 & $2.

For sound dumps I had to learn a bit more, cause I couldn't just record the dump and replace values, I actually had to understand what I was doing. When you do a sysex sound dump from the Blofeld, it does not actually send back the sysex string to request the sound dump, it only sends the actual sound dump.

I am not really a programmer, so it took a while understanding it. Not saying i fully understand everything but parameters are working, hehe

So making something in Lua would be a big task, as I don't know Lua at all. I know some C++, from coding Axoloti objects and VCV rack modules, but yeah. It's a hobby/fun thing I think i would prefer to keep it all in Pure Data, as I know Pure Data decently.

So I do see this as a long term project, I need to do it in small steps at a time, learn things step by step.

I do appreciate the feedback a lot and it made me think a bit about some things I can try out. So thanks

there we go:

tried ./pd_helios.d_ppc and failed
tried ./pd_helios.pd_darwin and failed
tried ./pd_helios/pd_helios.d_ppc and failed
tried ./pd_helios/pd_helios.pd_darwin and failed
tried ./pd_helios/pd_helios-meta.pd and failed
tried ./pd_helios.pd_lua and failed
tried ./pd_helios.pd and failed
tried ./pd_helios.pat and failed
tried ./pd_helios/pd_helios.pd and failed
tried /Library/Pd-l2ork/pd_helios.d_ppc and failed
tried /Library/Pd-l2ork/pd_helios.pd_darwin and failed
tried /Library/Pd-l2ork/pd_helios/pd_helios.d_ppc and failed
tried /Library/Pd-l2ork/pd_helios/pd_helios.pd_darwin and failed
tried /Library/Pd-l2ork/pd_helios/pd_helios-meta.pd and failed
tried /Library/Pd-l2ork/pd_helios.pd_lua and failed
tried /Library/Pd-l2ork/pd_helios.pd and failed
tried /Library/Pd-l2ork/pd_helios.pat and failed
tried /Library/Pd-l2ork/pd_helios/pd_helios.pd and failed
tried /System/Library/Fonts/pd_helios.d_ppc and failed
tried /System/Library/Fonts/pd_helios.pd_darwin and failed
tried /System/Library/Fonts/pd_helios/pd_helios.d_ppc and failed
tried /System/Library/Fonts/pd_helios/pd_helios.pd_darwin and failed
tried /System/Library/Fonts/pd_helios/pd_helios-meta.pd and failed
tried /System/Library/Fonts/pd_helios.pd_lua and failed
tried /System/Library/Fonts/pd_helios.pd and failed
tried /System/Library/Fonts/pd_helios.pat and failed
tried /System/Library/Fonts/pd_helios/pd_helios.pd and failed
tried /Library/Fonts/pd_helios.d_ppc and failed
tried /Library/Fonts/pd_helios.pd_darwin and failed
tried /Library/Fonts/pd_helios/pd_helios.d_ppc and failed
tried /Library/Fonts/pd_helios/pd_helios.pd_darwin and failed
tried /Library/Fonts/pd_helios/pd_helios-meta.pd and failed
tried /Library/Fonts/pd_helios.pd_lua and failed
tried /Library/Fonts/pd_helios.pd and failed
tried /Library/Fonts/pd_helios.pat and failed
tried /Library/Fonts/pd_helios/pd_helios.pd and failed
tried /Users/didipiman/Library/Fonts/pd_helios.d_ppc and failed
tried /Users/didipiman/Library/Fonts/pd_helios.pd_darwin and failed
tried /Users/didipiman/Library/Fonts/pd_helios/pd_helios.d_ppc and failed
tried /Users/didipiman/Library/Fonts/pd_helios/pd_helios.pd_darwin and failed
tried /Users/didipiman/Library/Fonts/pd_helios/pd_helios-meta.pd and failed
tried /Users/didipiman/Library/Fonts/pd_helios.pd_lua and failed
tried /Users/didipiman/Library/Fonts/pd_helios.pd and failed
tried /Users/didipiman/Library/Fonts/pd_helios.pat and failed
tried /Users/didipiman/Library/Fonts/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cyclone/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cyclone/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cyclone/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cyclone/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cyclone/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cyclone/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cyclone/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cyclone/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cyclone/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/zexy/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/zexy/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/zexy/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/zexy/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/zexy/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/zexy/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/zexy/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/zexy/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/zexy/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/creb/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/creb/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/creb/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/creb/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/creb/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/creb/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/creb/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/creb/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/creb/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cxc/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cxc/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cxc/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cxc/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cxc/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cxc/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cxc/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cxc/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/cxc/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/iemlib/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/iemlib/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/iemlib/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/iemlib/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/iemlib/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/iemlib/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/iemlib/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/iemlib/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/iemlib/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/list-abs/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/list-abs/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/list-abs/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/list-abs/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/list-abs/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/list-abs/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/list-abs/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/list-abs/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/list-abs/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mapping/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mapping/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mapping/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mapping/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mapping/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mapping/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mapping/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mapping/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mapping/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/markex/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/markex/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/markex/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/markex/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/markex/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/markex/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/markex/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/markex/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/markex/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/maxlib/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/maxlib/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/maxlib/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/maxlib/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/maxlib/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/maxlib/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/maxlib/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/maxlib/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/maxlib/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/memento/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/memento/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/memento/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/memento/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/memento/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/memento/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/memento/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/memento/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/memento/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mjlib/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mjlib/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mjlib/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mjlib/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mjlib/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mjlib/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mjlib/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mjlib/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/mjlib/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/motex/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/motex/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/motex/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/motex/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/motex/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/motex/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/motex/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/motex/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/motex/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/oscx/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/oscx/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/oscx/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/oscx/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/oscx/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/oscx/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/oscx/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/oscx/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/oscx/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pddp/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pddp/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pddp/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pddp/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pddp/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pddp/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pddp/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pddp/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pddp/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pdogg/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pdogg/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pdogg/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pdogg/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pdogg/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pdogg/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pdogg/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pdogg/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pdogg/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pixeltango/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pixeltango/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pixeltango/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pixeltango/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pixeltango/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pixeltango/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pixeltango/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pixeltango/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pixeltango/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/rradical/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/rradical/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/rradical/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/rradical/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/rradical/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/rradical/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/rradical/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/rradical/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/rradical/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/sigpack/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/sigpack/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/sigpack/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/sigpack/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/sigpack/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/sigpack/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/sigpack/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/sigpack/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/sigpack/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/smlib/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/smlib/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/smlib/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/smlib/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/smlib/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/smlib/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/smlib/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/smlib/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/smlib/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/unauthorized/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/unauthorized/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/unauthorized/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/unauthorized/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/unauthorized/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/unauthorized/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/unauthorized/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/unauthorized/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/unauthorized/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pan/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pan/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pan/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pan/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pan/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pan/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pan/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pan/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pan/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/hcs/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/hcs/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/hcs/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/hcs/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/hcs/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/hcs/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/hcs/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/hcs/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/hcs/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/jmmmp/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/jmmmp/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/jmmmp/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/jmmmp/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/jmmmp/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/jmmmp/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/jmmmp/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/jmmmp/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/jmmmp/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ext13/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ext13/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ext13/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ext13/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ext13/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ext13/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ext13/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ext13/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ext13/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ggee/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ggee/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ggee/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ggee/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ggee/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ggee/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ggee/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ggee/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ggee/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ekext/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ekext/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ekext/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ekext/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ekext/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ekext/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ekext/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ekext/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/ekext/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/disis/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/disis/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/disis/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/disis/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/disis/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/disis/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/disis/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/disis/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/disis/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/lyonpotpourri/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/lyonpotpourri/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/lyonpotpourri/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/lyonpotpourri/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/lyonpotpourri/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/lyonpotpourri/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/lyonpotpourri/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/lyonpotpourri/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/lyonpotpourri/pd_helios/pd_helios.pd and failed
tried /Users/didipiman/Library/Pd-l2ork/pd_helios.d_ppc and failed
tried /Users/didipiman/Library/Pd-l2ork/pd_helios.pd_darwin and failed
tried /Users/didipiman/Library/Pd-l2ork/pd_helios/pd_helios.d_ppc and failed
tried /Users/didipiman/Library/Pd-l2ork/pd_helios/pd_helios.pd_darwin and failed
tried /Users/didipiman/Library/Pd-l2ork/pd_helios/pd_helios-meta.pd and failed
tried /Users/didipiman/Library/Pd-l2ork/pd_helios.pd_lua and failed
tried /Users/didipiman/Library/Pd-l2ork/pd_helios.pd and failed
tried /Users/didipiman/Library/Pd-l2ork/pd_helios.pat and failed
tried /Users/didipiman/Library/Pd-l2ork/pd_helios/pd_helios.pd and failed
tried /Library/Pd-l2ork/pd_helios.d_ppc and failed
tried /Library/Pd-l2ork/pd_helios.pd_darwin and failed
tried /Library/Pd-l2ork/pd_helios/pd_helios.d_ppc and failed
tried /Library/Pd-l2ork/pd_helios/pd_helios.pd_darwin and failed
tried /Library/Pd-l2ork/pd_helios/pd_helios-meta.pd and failed
tried /Library/Pd-l2ork/pd_helios.pd_lua and failed
tried /Library/Pd-l2ork/pd_helios.pd and failed
tried /Library/Pd-l2ork/pd_helios.pat and failed
tried /Library/Pd-l2ork/pd_helios/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios.d_ppc and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios.pd_darwin and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios-meta.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios.pd_lua and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios.pd and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios.pat and failed
tried /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/pd_helios.pd and failed
pd_helios: can't load library```

NoxSiren is a modular synthesizer system where the punishment of failure is the beginning of a new invention.

--DOWNLOAD-- NoxSiren for :

• Pure Data :
  NoxSiren v15.rar
  NoxSiren v14.rar

• Purr Data :
  NoxSiren v15.rar
  NoxSiren v14.rar

--DOWNLOAD-- ORCA for :

• x64, OSX, Linux :
  https://hundredrabbits.itch.io/orca

In order to connect NoxSiren system to ORCA system you also need a virtual loopback MIDI-ports:

--DOWNLOAD-- loopMIDI for :

• Windows 7 up to Windows 10, 32 and 64 bit :
  https://www.tobias-erichsen.de/software/loopmidi.html

#-= Cyber Notes [v15] =-#

• added BORG-IMPLANT module.
• introduction to special modules.
• more system testing.

#-= Special Modules [v15] =-#

• BORG-IMPLANT (connects ORCA MIDI system to NoxSiren system)

#-= Current Modules [v15] =-#

• VCO (voltage-controlled-oscillator)
• VCO2 (advance voltage-controlled-oscillator)
• WAVEBANK (additive synthesis oscillator)
• ADSR (Attack-Decay-Sustain-Release envelope)
• C-ADSR (Curved Attack-Decay-Sustain-Release envelope)
• CICADAS (128 steps-Euclidean rhythm generator)
• CICADAS-2 (advance 128-steps polymorphic-Euclidean rhythm generator)
• COMPRESSOR (lookahead mono compressor unit)
• DUAL-COMPRESSOR (2-channel lookahead mono compressor unit)
• STEREO-COMPRESSOR (lookahead stereo compressor unit)
• MONO-KEYS (virtual 1-voice monophonic MIDI keyboard)
• POLY-KEYS-2 (virtual 2-voice polyphonic MIDI keyboard)
• POLY-KEYS-3 (virtual 3-voice polyphonic MIDI keyboard)
• POLY-KEYS-4 (virtual 4-voice polyphonic MIDI keyboard)
• POLY-KEYS-5 (virtual 5-voice polyphonic MIDI keyboard)
• POLY-KEYS-6 (virtual 6-voice polyphonic MIDI keyboard)
• BATTERY (simple manual triggered machine for drumming.)
• REVERB (reverb unit with lowpass control)
• STEREO-REVERB (stereo reverb unit with lowpass control)
• RESIN (advanced rain effect/texture generator)
• NOISE (generates black,brown,red and orange noise)
• NOISE2 (generates yellow,blue,pink and white noise)
• COBALT (6-stage polyrhythm generator)
• SHAPER (basic shaper unit)
• FOLDER (basic wave folding unit)
• STEREO-FOLDER (stereo wave folding unit)
• DUAL-FOLDER (advance wave folding unit)
• POLARIZER (transform a signal into bi-polar, uni-polar, inverted or inverted uni-polar form)
• CLOCK (generates a BPM clock signal for sequencing other modules)
• CLOCKDIVIDER (a clock divider with even division of clock signal)
• CLOCKDIVIDER2 (a clock divider with odd division of clock signal)
• DELAY-UNIT (delay unit)
• STEREO-DELAY (stereo delay unit)
• CHORUS (chorus unit)
• STEREO-CHORUS (stereo chorus unit)
• SEQ (advance 16-step/trigger sequencer)
• KICK (synthesize kick unit)
• KICK2 (synthesize flavor of KICK module)
• KICK3 (synthesize flavor of KICK module)
• SNARE (synthesize snare unit)
• CLAP (synthesize clap unit)
• CYMBAL (synthesize cymbal unit)
• RAND (RNG generator for other modules parameters)
• FMOD (feedback modulation unit)
• AM (amplitude modulation unit)
• RM (ring modulation unit)
• LFO (low-frequency-oscillator)
• LFO2 (advance low-frequency-oscillator)
• COMBINATOR (combine two waves)
• COMBINATOR2 (combine three waves)
• COMBINATOR3 (combine four waves)
• STRING (Karplus-Strong string synthesis unit)
• STRING2 (advance Karplus-Strong string synthesis unit)
• DETUNER (parametric 4-channel detuner unit)
• CRUSHER (basic audio resolution unit)
• STEREO-CRUSHER (basic stereo audio resolution unit)
• DUAL-CRUSHER (advance audio resolution unit)
• FILTER (basic filter)
• VCF (voltage-controlled-filter)
• MAR (Moog-analog-resonant filter)
• VCA (voltage-controlled-amplifier)
• DUAL-VCA (advance voltage-controlled-amplifier)
• FMUX (multiplexer with fast A/D internal envelope)
• MMUX (multiplexer with medium A/D internal envelope)
• SMUX (multiplexer with slow A/D internal envelope)
• FDMX (demultiplexer with fast A/D internal envelope)
• MDMX (demultiplexer with medium A/D internal envelope)
• SDMX (demultiplexer with slow A/D internal envelope)
• MIXER (mix 1-4 possible waves)
• SCOPE (oscilloscope analyzer)
• MASTER (fancy DAC~)
• BOX (useless decorative module)

NoxSiren integrated modules menu system.

JASS, Just Another Synth...Sort-of, codename: Gemini (UPDATED TO V-1.0.1)

jass-v1.0.1( esp with midi fixes).zip

1.0.1-CHANGES:

• Fixed issues with midi routing, re the mode selector (mentioned below)
• Upgraded the midi mode "fetch" abstraction to be less granular
• Fix (for midi) so changing cc["14","15","16"] to "rnd" outputs a random wave (It has always done this for non-midi.)
• Added a midi-mode-tester.pd (connect PD's midi out to PD's midi in to use it)
• Upgrade: cc-56 and cc-58 can now change pbend-cc and mod-cc in all modes
• Update: the (this) readme

INFO: Values setting to 0 on initial cc changes is (given midi) to be expected.

JASS is a clone-based, three wavetable, 16 voice polyphonic, Dual-channel synth.

With...

• The initial, two wavetables combined in 1 of 5 possible ways per channel and then adding those two channels. Example: additive+frequency modulation, phase+pulse-modulation, pulse-modulation+amplitude modulation, fm+fm, etc
• The third wavetable is a ring modulator, embedded inside each mod type
• 8 wave types, including a random with a settable number of partials and a square with a settable dutycycle
• A vcf~ filter embedded inside each modulation type
• The attack-decay-release, cutoff, and resonance ranges settable so they immediately and globally recalculate all relevant values
• Four parameters /mod type: p1,p2, cutoff, and resonance
• State-saving, at both the global level (wavetables, env, etc.), as well as, multiple "substates" of for-each-mod-type settings.
• Distortion, reverb
• Midiin, paying special attention to the use of 8-knob, usb, midi controllers (see below for details)
• zexy-limiters, for each channel, after the distortion, and just before dac~

Instructions

Requires: zexy

for-entire-state

• O: Open preset. "default.txt" is loaded by...default
• S: Save preset (all values incl. the multiple substates) (Note: I have Not included any presets, besides the default with 5 substates.)
• SA: Save as
• TEST: A sample player
• symbol: The filename of the currently loaded preset
• CL: Clear, sets all but a few values to 0
• U: Undo CL
• distortion,reverb,MASTER: operate on the total out, just before the limiter.
• MIDI (Each selection corresponds to a pgmin, 123,124,125,126,127, respectively, see below for more information)
  • X: Default midi config, cc[1,7,8-64] available
  • M: Modulators;cc[10-17] routed to ch1&ch2: p1,p2,cutoff,q controls
  • E: Envelopes; cc[10-17] routed to filter- and amp-env controls
  • R: Ranges; cc[10-17] routed to adr-min/max,cut-off min/max, resonance min/max, distortion, and reverb
  • O: Other; cc[10-17] routed to rngmod controls, 3 wavetypes, and crossfade
  • symbol: you may enter 8 cc#'s here to replace the default [10-17] from above to suit your midi-controller's knob configuration; these settings are saved to file upon entry
• vu: for total out to dac~

for-all-mod-types

• /wavetable
  • graph: of the chosen wavetype
  • part: partials, # of partials to use for the "rn" wavetype; the resulting, random sinesum is saved with the preset
  • duty: dutycycle for the "du" wavetype
  • type: sin | square | triangle | saw | random | duty | pink (pink-noise: a random sinesum with 128 partials, it is not saved with the preset) | noise (a random sinesum with 2051 partials, also not saved)
• filter-env: (self-explanatory)
• amp-env: (self-explanatory)
• rngmod: self-explanatory, except "sign" is to the modulated signal just before going into the vcf~
• adr-range: min,max[0-10000]; changing these values immediately recalculates all values for the filter- and amp-env's scaled to the new range
• R: randomizes all for-all-mod-types values, but excludes wavetype "noise"; rem: you must S or SA the preset to save the results
• U: Undoes R

for-each-mod-type

• mod-type-1: (In all cases, wavetable1 is the carrier and wavetable2 is the modulator); additive | frequency | phase | pulse | amplitude modulation
• mod-type-2: Same as above; mod-type-2 May be the same type as mod-type-1
• crossfade: Between ch1 and ch2
• detune: Applied to the midi pitch going into ch2
• for-each-clone-type controls:
  • p1,p2: (self-explanatory)
  • cutoff, resonance: (self-explanatory)
• navigation: Cycles through the saved substates of for-each-mod-type settings (note: they are lines on the end of a [text])
• CP: Copy the current settings, ie. add a line to the end of the [text] identical to the current substate
• -: Delete the current substate
• R: Randomize all (but only a few) substate settings
• U: Undo R
• cut-rng: min,max[0-20000] As adr-range above, this immediately recalculates all cutoff values
• res-rng: min,max[0-100], same as previously but for q
• pbend: cc,rng: the pitchwheel may be assigned to a control by setting this to a value >7 (see midi table below for possibilities); rng is in midi pitches (+/- the value you enter)
• mod-cc: the mod-wheel may be assigned to a control [7..64] by setting this value

midi-implementation

name	---	Description
sysex		not supported
pgmin		123,124,125,126,127; They set midi mode
notein		0-127
bendin		pbend-cc=7>pitchbend; otherwise to the cc# from below
touch		not supported
polytouch		not supported

cc - basic (for all midi-configs)

#	name	---	desciption
1	mod-wheel		(assignable)
7	volume		Master

cc - "X" mode/pgmin=123

cc	---	parameter
8		wavetype1
9		partials 1
10		duty 1
11		wavetype2
12		partials 2
13		duty 2
14		wavetype3
15		partials 3
16		duty 3
17		filter-att
18		filter-dec
19		filter-sus
20		filter-rel
21		amp-att
22		amp-dec
23		amp-sus
24		amp-rel
25		rngmod-freq
26		rngmod-sig
27		rngmod-filt
28		rngmod-amp
29		distortion
30		reverb
31		master
32		mod-type 1
33		mod-type 2
34		crossfade
35		detune
36		p1-1
37		p2-1
38		cutoff-1
39		q-1
40		p1-2
41		p2-2
42		cutoff-2
43		q-2
44		p1-3
45		p2-3
46		cutoff-3
47		q-3
48		p1-4
49		p2-4
50		cutoff-4
51		q-4
52		p1-5
53		p2-5
54		cutoff-5
55		q-5
56		pbend-cc
57		pbend-rng
58		mod-cc
59		adr-rng-min
60		adr-rng-max
61		cut-rng-min
62		cut-rng-max
63		res-rng-min
64		res-rng-max

cc - Modes M, E, R, O

Jass is designed so that single knobs may be used for multiple purposes without reentering the previous value when you turn the knob, esp. as it pertains to, 8-knob controllers.

Thus, for instance, when in Mode M(pgm=124) your cc send the signals as listed below. When you switch modes, that knob will then change the values for That mode.

In order to do this, you must turn the knob until it hits the previously stored value for that mode-knob.

After hitting that previous value, it will begin to change the current value.

cc - Modes M, E, R, O assignments

Where [10..17] may be the midi cc #'s you enter in the MIDI symbol field (as mentioned above) aligned to your particular midi controller.

cc#	---	M/pgm=124	---	E/pgm=125	---	R/pgm=126	---	O/pgm=127
10		ch1:p1		filter-env:att		adr-rng-min		rngmod:freq
11		ch1:p2		filter-env:dec		adr-rng-max		rngmod:sig
12		ch1:cutoff		filter-env:sus		cut-rng-min		rngmod:filter
13		ch1:q		filter-env:re		cut-rng-max		rngmod:amp
14		ch2:p1		amp-env:att		res-rng-min		wavetype1
15		ch2:p2		amp-env:dec		res-rng-max		wavetype2
16		ch2:cutoff		amp-env:sus		distortion		wavetype3
17		ch2:q		amp-env:rel		reverb		crossfade

In closing

If you have anywhere close to as much fun (using, experimenting with, trying out, etc.) this patch, as I had making it, I will consider it a success.

For while an arduous learning curve (the first synth I ever built), it has been an Enormous pleasure to listen to as I worked on it. Getting better and better sounding at each pass.

Rather, than say to much, I will say this:

Enjoy. May it bring a smile to your face.

Peace through love of creating and sharing.

Sincerely,
Scott

oh, great - thanks for all the replies!
@ingox

Is it possible that you are using @Balwyn's xy-patch

no, not this patch, but yeah, i was inspired by another patch i found here somewhere in the forum... don't remembr exactly which one, but this got me started - i'm still trying to get into data structures, which is quite hard sometimes, so it's really good to have some patches to get started with...

It is that data structures get an invisible dragging area of 10 or 12 pixels squared. This is not documented and i don't remember the exact circumstances how the area is created. But the dragging area is unfortunately independent from the displayed form in size, so a bigger form can not be dragged at any point. Hope that helps a little bit.

yeah, i was afraid, this could be the answer!

@Balwyn said:

@toxonic just multiplying the outputs by 0.01 gives the same result

yes, correct - it's not a big deal to convert the output into any range, but i just hoped to keep things simple....

@Balwyn said:

@toxonic You may get some insight into using the hotspot without a pointer with this offering I uploaded a few years ago,
https://forum.pdpatchrepo.info/uploads/files/1498974324729-xydrag.zip
The template is a little confronting but shows that by using just one xy pair (px and py) multiple nodes can be created using scaling and constraining (eg px(-100:100)(20:20) py(-100:100)(-20:-20)).
the x and y output from the grid is interpreted as greater or smaller than the previous which activates a plus or minus counter for the output values

oh, sweet jesus, this is a huge template within the [pd template] patch.... i have to go to work now, but i'll try to figure it out, when i'm at home again!

thank you all for your answers, great forum!

mda Delay.vst.zip

[vstplugin~] v0.2.0
WARNING: on macOS, the VST GUI must run on the audio thread - use with care!
searching in '/Users/boonier/Library/Audio/Plug-Ins/VST' ...
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/BreakBeatCutter.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/Camomile.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/Euklid.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/FmClang.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/Micropolyphony.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/PhaserLFO.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/pvsBuffer.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/smGrain3.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/smHostInfo.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/smMetroTests.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/smModulatingDelays.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/smTemposcalFilePlayer.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/smTrigSeq.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/SoundwarpFilePlayer.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/SpectralDelay.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/SyncgrainFilePlayer.vst'... failed!
probing '/Users/boonier/Library/Audio/Plug-Ins/VST/Vocoder.vst'... failed!
found 0 plugins
searching in '/Library/Audio/Plug-Ins/VST' ...
probing '/Library/Audio/Plug-Ins/VST/++bubbler.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/++delay.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/++flipper.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/++pitchdelay.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/ABL2x.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/BassStation.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/BassStationStereo.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Camomile.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Crystal.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Ctrlr.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Dexed.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Driftmaker.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/GTune.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Independence FX.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Independence.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/JACK-insert.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Lua Protoplug Fx.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Lua Protoplug Gen.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Ambience.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Bandisto.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda BeatBox.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Combo.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda De-ess.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Degrade.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Delay.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Detune.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Dither.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda DubDelay.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda DX10.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Dynamics.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda ePiano.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Image.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Leslie.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Limiter.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Looplex.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Loudness.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda MultiBand.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Overdrive.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Piano.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda RePsycho!.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda RezFilter.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda RingMod.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda RoundPan.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Shepard.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Splitter.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Stereo.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda SubBass.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda TestTone.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda ThruZero.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Tracker.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Transient.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda VocInput.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mda Vocoder.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mdaJX10.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/mdaTalkBox.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/ME80v2_3_Demo.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Metaplugin.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/MetapluginSynth.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Molot.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Nektarine.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Nektarine_32OUT.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Nithonat.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Obxd.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Ozone 8 Elements.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/PlogueBiduleVST.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/PlogueBiduleVST_16.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/PlogueBiduleVST_32.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/PlogueBiduleVST_64.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/PlogueBiduleVSTi.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/PlogueBiduleVSTi_16.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/PlogueBiduleVSTi_32.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/PlogueBiduleVSTi_64.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/sforzando.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Sonic Charge/Cyclone FX.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Sonic Charge/Cyclone.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Soundtoys/Devil-Loc.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Soundtoys/LittlePlate.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Soundtoys/LittleRadiator.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Soundtoys/SieQ.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/SPAN.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Spitter2.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Surge.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/Synth1.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/TAL-Chorus-LX.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/TAL-Reverb-2.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/TAL-Reverb-3.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/TAL-Reverb-4.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/TAL-Sampler.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/TX16Wx.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/u-he/Diva.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/u-he/Protoverb.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/u-he/Repro-1.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/u-he/Repro-5.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/u-he/Satin.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/u-he/TyrellN6.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/u-he/Zebra2.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/u-he/Zebralette.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/u-he/Zebrify.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/u-he/ZRev.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/UltraChannel.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/ValhallaFreqEcho.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/ValhallaRoom_x64.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/VCV-Bridge-fx.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/VCV-Bridge.vst'... failed!
probing '/Library/Audio/Plug-Ins/VST/WaveShell1-VST 10.0.vst'... failed!
found 0 plugins
searching in '/Users/boonier/Library/Audio/Plug-Ins/VST3' ...
found 0 plugins
searching in '/Library/Audio/Plug-Ins/VST3' ...
probing '/Library/Audio/Plug-Ins/VST3/TX16Wx.vst3'... error
couldn't init module

probing '/Library/Audio/Plug-Ins/VST3/WaveShell1-VST3 10.0.vst3'... error
factory doesn't have any plugin(s)

probing '/Library/Audio/Plug-Ins/VST3/Nektarine.vst3'... failed!
probing '/Library/Audio/Plug-Ins/VST3/Nektarine_32OUT.vst3'... failed!
probing '/Library/Audio/Plug-Ins/VST3/OP-X PRO-II.vst3'... failed!
probing '/Library/Audio/Plug-Ins/VST3/SPAN.vst3'... failed!
probing '/Library/Audio/Plug-Ins/VST3/Surge.vst3'... failed!
probing '/Library/Audio/Plug-Ins/VST3/Zebra2.vst3'...
[1/4] 'Zebrify' ... failed!
[2/4] 'ZRev' ... failed!
[3/4] 'Zebra2' ... failed!
[4/4] 'Zebralette' ... failed!
found 0 plugins
search done
print: search_done

Hello,

this is going to be a long one.
After years of using PD, I am still confused about its' timing and schedueling.

I have collected many snippets from here and there about this topic,
-wich all together are really confusing to me.

*I think it is very important to understand how timing works in detail for low-level programming … *

(For example the number of heavy jittering sequencers in hard and software make me wonder what sequencers are made actually for ? lol )

This is a collection of my findings regarding this topic, a bit messy and with confused questions.

I hope we can shed some light on this.

---

• a)
  The first time, I had issues with the PD-scheduler vs. how I thought my patch should work is described here:
  https://forum.pdpatchrepo.info/topic/11615/bang-bug-when-block-1-1-1-bang-on-every-sample

The answers where:

„
[...] it's just that messages actually only process every 64 samples at the least. You can get a bang every sample with [metro 1 1 samp] but it should be noted that most pd message objects only interact with each other at 64-sample boundaries, there are some that use the elapsed logical time to get times in between though (like vsnapshot~)
also this seems like a very inefficient way to do per-sample processing..
https://github.com/sebshader/shadylib http://www.openprocessing.org/user/29118
seb-harmonik.ar posted about a year ago , last edited by seb-harmonik.ar about a year ago 
• 1 
 whale-av 
@lacuna An excellent simple explanation from @seb-harmonik.ar.
Chapter 2.5 onwards for more info....... http://puredata.info/docs/manuals/pd/x2.htm
David.
“

There is written: http://puredata.info/docs/manuals/pd/x2.htm

„2.5. scheduling 
Pd uses 64-bit floating point numbers to represent time, providing sample accuracy and essentially never overflowing. Time appears to the user in milliseconds. 
2.5.1. audio and messages 
Audio and message processing are interleaved in Pd. Audio processing is scheduled every 64 samples at Pd's sample rate; at 44100 Hz. this gives a period of 1.45 milliseconds. You may turn DSP computation on and off by sending the "pd" object the messages "dsp 1" and "dsp 0." 
In the intervals between, delays might time out or external conditions might arise (incoming MIDI, mouse clicks, or whatnot). These may cause a cascade of depth-first message passing; each such message cascade is completely run out before the next message or DSP tick is computed. Messages are never passed to objects during a DSP tick; the ticks are atomic and parameter changes sent to different objects in any given message cascade take effect simultaneously. 
In the middle of a message cascade you may schedule another one at a delay of zero. This delayed cascade happens after the present cascade has finished, but at the same logical time. 
2.5.2. computation load 
The Pd scheduler maintains a (user-specified) lead on its computations; that is, it tries to keep ahead of real time by a small amount in order to be able to absorb unpredictable, momentary increases in computation time. This is specified using the "audiobuffer" or "frags" command line flags (see getting Pd to run ). 
If Pd gets late with respect to real time, gaps (either occasional or frequent) will appear in both the input and output audio streams. On the other hand, disk strewaming objects will work correctly, so that you may use Pd as a batch program with soundfile input and/or output. The "-nogui" and "-send" startup flags are provided to aid in doing this. 
Pd's "realtime" computations compete for CPU time with its own GUI, which runs as a separate process. A flow control mechanism will be provided someday to prevent this from causing trouble, but it is in any case wise to avoid having too much drawing going on while Pd is trying to make sound. If a subwindow is closed, Pd suspends sending the GUI update messages for it; but not so for miniaturized windows as of version 0.32. You should really close them when you aren't using them. 
2.5.3. determinism 
All message cascades that are scheduled (via "delay" and its relatives) to happen before a given audio tick will happen as scheduled regardless of whether Pd as a whole is running on time; in other words, calculation is never reordered for any real-time considerations. This is done in order to make Pd's operation deterministic. 
If a message cascade is started by an external event, a time tag is given it. These time tags are guaranteed to be consistent with the times at which timeouts are scheduled and DSP ticks are computed; i.e., time never decreases. (However, either Pd or a hardware driver may lie about the physical time an input arrives; this depends on the operating system.) "Timer" objects which meaure time intervals measure them in terms of the logical time stamps of the message cascades, so that timing a "delay" object always gives exactly the theoretical value. (There is, however, a "realtime" object that measures real time, with nondeterministic results.) 
If two message cascades are scheduled for the same logical time, they are carried out in the order they were scheduled. 
“ 

[block~ smaller then 64] doesn't change the interval of message-control-domain-calculation?,
Only the size of the audio-samples calculated at once is decreased?
Is this the reason [block~] should always be … 128 64 32 16 8 4 2 1, nothing inbetween, because else it would mess with the calculation every 64 samples?
How do I know which messages are handeled inbetween smaller blocksizes the 64 and which are not?

How does [vline~] execute?
Does it calculate between sample 64 and 65 a ramp of samples with a delay beforehand, calculated in samples, too - running like a "stupid array" in audio-rate?

While sample 1-64 are running, PD does audio only?

[metro 1 1 samp]  

How could I have known that? The helpfile doesn't mention this. EDIT: yes, it does.
(Offtopic: actually the whole forum is full of pd-vocabular-questions)
How is this calculation being done?
But you can „use“ the metro counts every 64 samples only, don't you?

Is the timing of [metro] exact? Will the milliseconds dialed in be on point or jittering with the 64 samples interval?
Even if it is exact the upcoming calculation will happen in that 64 sample frame!?

---

• b )
  
  There are [phasor~], [vphasor~] and [vphasor2~] … and [vsamphold~]
  https://forum.pdpatchrepo.info/topic/10192/vphasor-and-vphasor2-subsample-accurate-phasors

“Ive been getting back into Pd lately and have been messing around with some granular stuff. A few years ago I posted a [vphasor.mmb~] abstraction that made the phase reset of [phasor~] sample-accurate using vanilla objects. Unfortunately, I'm finding that with pitch-synchronous granular synthesis, sample accuracy isn't accurate enough. There's still a little jitter that causes a little bit of noise. So I went ahead and made an external to fix this issue, and I know a lot of people have wanted this so I thought I'd share. 
[vphasor~] acts just like [phasor~], except the phase resets with subsample accuracy at the moment the message is sent. I think it's about as accurate as Pd will allow, though I don't pretend to be an expert C programmer or know Pd's api that well. But it seems to be about as accurate as [vline~]. (Actually, I've found that [vline~] starts its ramp a sample early, which is some unexpected behavior.)
[…]
“

---

• c)
  
  Later I discovered that PD has jittery Midi because it doesn't handle Midi at a higher priority then everything else (GUI, OSC, message-domain ect.)

EDIT:
Tryed roundtrip-midi-messages with -nogui flag:
still some jitter.
Didn't try -nosleep flag yet (see below)

---

• d)
  
  So I looked into the sources of PD:

scheduler with m_mainloop()
https://github.com/pure-data/pure-data/blob/master/src/m_sched.c

And found this paper

Scheduler explained (in German): 

https://iaem.at/kurse/ss19/iaa/pdscheduler.pdf/view

wich explains the interleaving of control and audio domain as in the text of @seb-harmonik.ar with some drawings
plus the distinction between the two (control vs audio / realtime vs logical time / xruns vs burst batch processing).
And the "timestamping objects" listed below.

And the mainloop:

Loop
- messages (var.duration)
- dsp (rel.const.duration)
- sleep

With
[block~ 1 1 1]
calculations in the control-domain are done between every sample? But there is still a 64 sample interval somehow?
Why is [block~ 1 1 1] more expensive? The amount of data is the same!? Is this the overhead which makes the difference? Calling up operations ect.?

---

Timing-relevant objects
from iemlib:

[...]
iem_blocksize~   blocksize of a window in samples
iem_samplerate~  samplerate of a window in Hertz 


------------------ t3~ - time-tagged-trigger --------------------
-- inputmessages allow a sample-accurate access to signalshape --
t3_sig~          time tagged trigger sig~
t3_line~         time tagged trigger line~


--------------- t3 - time-tagged-trigger  ---------------------
----------- a time-tag is prepended to each message -----------
----- so these objects allow a sample-accurate access to ------
---------- the signal-objects t3_sig~ and t3_line~ ------------
t3_bpe           time tagged trigger break point envelope
t3_delay         time tagged trigger delay
t3_metro         time tagged trigger metronom
t3_timer         time tagged trigger timer

[...]

What are different use-cases of [line~] [vline~] and [t3_line~]?
And of [phasor~] [vphasor~] and [vphasor2~]?

When should I use [block~ 1 1 1] and when shouldn't I?

[line~] starts at block boundaries defined with [block~] and ends in exact timing?
[vline~] starts the line within the block?
and [t3_line~]???? Are they some kind of interrupt? Shortcutting within sheduling???

---

• c) again)
  

https://forum.pdpatchrepo.info/topic/1114/smooth-midi-clock-jitter/2

I read this in the html help for Pd: 
„
MIDI and sleepgrain
In Linux, if you ask for "pd -midioutdev 1" for instance, you get /dev/midi0 or /dev/midi00 (or even /dev/midi). "-midioutdev 45" would be /dev/midi44. In NT, device number 0 is the "MIDI mapper", which is the default MIDI device you selected from the control panel; counting from one, the device numbers are card numbers as listed by "pd -listdev."
The "sleepgrain" controls how long (in milliseconds) Pd sleeps between periods of computation. This is normally the audio buffer divided by 4, but no less than 0.1 and no more than 5. On most OSes, ingoing and outgoing MIDI is quantized to this value, so if you care about MIDI timing, reduce this to 1 or less.
„

Why is there the „sleep-time“ of PD? For energy-saving??????
This seems to slow down the whole process-chain?

Can I control this with a startup flag or from withing PD? Or only in the sources?

There is a startup-flag for loading a different scheduler, wich is not documented how to use.

---

• e)
  
  [pd~] helpfile says:

ATTENTION: DSP must be running in this process for the sub-process to run. This is because its clock is slaved to audio I/O it gets from us!

Doesn't [pd~] work within a Camomile plugin!?

How are things scheduled in Camomile? How is the communication with the DAW handled?

---

• f)
  
  and slightly off-topic:
  There is a batch mode:
  https://forum.pdpatchrepo.info/topic/11776/sigmund-fiddle-or-helmholtz-faster-than-realtime/9

---

EDIT:

• g)
  I didn't look into it, but there is:
  https://grrrr.org/research/software/

clk – Syncable clocking objects for Pure Data and Max
This library implements a number of objects for highly precise and persistently stable timing, e.g. for the control of long-lasting sound installations or other complex time-related processes.

---

Sorry for the mess!
Could you please help me to sort things a bit? Mabye some real-world examples would help, too.

edit: solved

Hello everyone!

I following the installing instructions for Pd extended for Raspberry Pi
and when I run this command:

$ sudo dpkg -i Pd-0.43.3-extended-20121004.deb

I keep getting this error:

Selecting previously unselected package pd-extended.
(Reading database ... 57768 files and directories currently installed.)
Unpacking pd-extended (from Pd-0.43.3-extended-20121004.deb) ...
dpkg: dependency problems prevent configuration of pd-extended:
pd-extended depends on libfftw3-3; however:
Package libfftw3-3 is not installed.
pd-extended depends on libftgl2 (>= 2.1.3~rc5); however:
Package libftgl2 is not installed.
pd-extended depends on libglu1-mesa | libglu1; however:
Package libglu1-mesa is not installed.
Package libglu1 is not installed.
pd-extended depends on libgsl0ldbl (>= 1.9); however:
Package libgsl0ldbl is not installed.
pd-extended depends on libjack-jackd2-0 (>= 1.9.5~dfsg-14) |
libjack-0.116; however:
Package libjack-jackd2-0 is not installed.
Package libjack-0.116 is not installed.
pd-extended depends on liblua5.1-0; however:
Package liblua5.1-0 is not installed.
pd-extended depends on libmp3lame0; however:
Package libmp3lame0 is not installed.
pd-extended depends on libquicktime2 (>= 2:1.2.2); however:
Package libquicktime2 is not installed.
pd-extended depends on libspeex1 (>= 1.2~beta3-1); however:
Package libspeex1 is not installed.

dpkg: error processing pd-extended (--install):
dependency problems - leaving unconfigured
Processing triggers for man-db ...
Processing triggers for menu ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for desktop-file-utils ...
Processing triggers for shared-mime-info ...
Errors were encountered while processing:

Has anyone else encountered this problem?
If so, any suggestions?

thanks,
J