I know at the 1/16th it's a lot of patterns, even so so at 1/8ths(256).
What I have found, without a mixing board to play it by ear, it really begs to be used with [text sequence] where fine grain selections can be sent in (via drafting them by formula in a spreadsheet app). (Did notice one nice thing with the mixer, is the patterns are contiguous as you sweep across them, ie only single beat changes to the pattern at each click. Which sounds cool.)
The test case above, was to see if I could make it sound good...and have fun doing it.
Thanks, for the comment. Would love to see what you find out.
Using the metro_pat abs posted here:
But eight of them all sending their bangs to an eight-track sampler I am working using it and and Akai Midimix, 8 track controller.
Takes all the available patterns, given a beat_length, ex 1/4=4 beats in a measure, so 2^4 patterns.;
Allows the user to select the pattern, via scaled hslider.;
Converts that value to binary.;
Then, on the metro, if the value at that idx (via list-idx) (as tabulated by a running counter for the total number of beats) ==1, sends the bang.;
note: rnd_pat changes the value only, i.e. not the hslider.
5:rnd_pat(any input triggers it)
p.s. used this last night on a drum-Meta-pattern generator/sample-player last night, and it made some really cool sounds.
I just tried the above, by downloading from Launchpad and using the (5) Kinetic builds, and got:
/usr/bin/puredata: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /usr/bin/puredata) /usr/bin/puredata: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /usr/bin/puredata) /usr/bin/puredata: /lib/x86_64-linux-gnu/libmvec.so.1: version `GLIBC_2.35' not found (required by /usr/bin/puredata)```
So am pretty sure. to do that upgrade (from Xenial), would require upgrading my OS (puppy linux). As I mentioned 'Having had problems in the past, when I upgrade'.
Thank you, @oid, for suggesting it. But prob going to need to just hold out until I switch computers. Will see what I can find out, about getting those paths, prob via bash.
Looks like I need to take the plunge to 0.52.
Do you know if I can just install that build on top of/or over the previous 0.50? And/or is it safe (to all my files and installs) to uninstall 0.50 and then install 0.52? (64-bit).
p.s. I figure, at the very least. I must back up my .pdsettings file and probably my */pd_externals folder.
This (which.pd) is great. Thank you, for the vanilla-ish versions. I really appreciate the extra effort. (Esp. as I am using the Xenial 0.50.2 version of pd. Having had problems in the past, when I upgrade, am a bit leary of making the jump to the 0.52 ).
Am wondering does the 3tree.pd handle [declare -path]'s and/or clones? I use them pretty consistently now in almost every project I do. But know they throw a wrench in even a 3d concept of the relationship between pd's "objects".
Thanks. again, for your help better understanding your work.
PtM and LtS.
p.s. re: meta-synth was thinking of different tonalities based on file organization of a patch's files. So closer, virtually, to the difference between the physical difference of ex. a viola and a cello
...[file which] is showing up "not found" on my system. Can you tell me how to fix it?
Your 3tree.pd looks Awesome! So many different way we could use this, ex. audio generation based on a meta-level.
p.s. was thinking one way to represent the 3d aspect would be to use GEM.
PtS and LtM.
Will definitely take a look at this when i get a chance.
Had not realized I didn't include the 3dtreeview (xml, xsl) code above.
You might check it out (the zip below). You are more than welcome to use it for your 3dtree if you wish.
Peace thru Music.
Love thru Sharing.
p.s. the only attribute which triggers either "right" or "down" is inside the xml.
Am looking into building a "project browser", like html developer tools (and later a "watchwindow"), and know that pd is Not 2-d hierarchical, but rather 3d with both subpatches and abstractions both operating as container nodes.
Which is ok. Because years ago, I built a 3d-treeview.
However, I have trouble (unless I require a naming convention for subpatch and abstraction ex., .sub and .abs suffixes, which would be really clunky) of "walking the tree".
Am certain, or at least confident, it's embedded inside the pd parser, somewhere. And would really like to see it.
Thanks, for any code or pointers, you may offer.
Would love to see this come to fruition....esp as often my patches are difficult to see at the highest level, ie in only their most abstract sense. And only seeing the primary ideas would improve my workflow substantially.
This is what the 3d-treeview looks like. But in our case, it would be subpatches "down" and abstractions "across".
-"Pd patches not only make art. Making pd patches Is art."