[PD] midi learn
jbturgid at hotmail.com
Thu Aug 5 00:51:39 CEST 2010
I actually prefer your solution to mine, the [==] boxes are exactly what I was looking for and would have saved quite a lot of logic. Also I didn't think of [t a a a] which would have saved quite a lot of time. Will have to keep an eye on these for future work.
I've got you in one place, tho. you can use [*] for conditional logic (with a [bang]) to activate when the right inlet changes. instead of multiple spigots. The logic goes, if all of them are 1, the result is 1. If any are 0, the result is zero. Useful stuff. Although more useful when you're working in audio, usually with [expr~] and the inlets of [*~] are summing.
I've gone on a bit of a tangent here. Always interested in approaches to logic in pd, tho.
> Date: Wed, 4 Aug 2010 13:20:51 -0400
> Subject: Re: [PD] midi learn
> From: pboivin at gmail.com
> To: jbturgid at hotmail.com
> CC: pd-list at iem.at
> Hi Andrew,
> I made something similar a couple of weeks ago, as I needed a quick
> way to map midi controllers. It's only for CC though...
> On Tue, Aug 3, 2010 at 1:09 PM, Andrew Faraday <jbturgid at hotmail.com> wrote:
> > Hey All,
> > I don't know if anyone's done this but I've attached a midi learn
> > abstraction I've been working on. The logic's a bit messy but I got it
> > working in the end.
> > Basically from banging the learn patch it listens to the next signal, either
> > a note or a control signal, and then filters out only the velocity or
> > control value from that. (I've started taking an interest in controlling
> > patches with the velocity, as opposed to the note number).
> > Let me know what you think, and if you know of anything similar being done.
> > Cheers
> > Andrew
> > _______________________________________________
> > Pd-list at iem.at mailing list
> > UNSUBSCRIBE and account-management ->
> > http://lists.puredata.info/listinfo/pd-list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list