I'm a newbie with Pd, who's enjoying the vast horizon of potential more than really accomplishing anything significant.

The problem I'm facing is with manifesting signals from an external FaderFox controller:

Fader inputs are fine via 'ctlin'

BUT I'm not managing to get buttons functioning via 'notein'

And, since I'm here, I'd like to invite you all to think of jumping board something I do here in India, called The Carnival of e-Creativity & Change-agents Conclave (CeC & CaC), of which the second iteration is due up in February 2007. See: http://www.theaea.org/cec_cac/

... and keep well all ~ Shankar

The horizon of possibilty will dazzle you for a while, until you spot somewhere you want to go, then you will accomplish a great deal of very significant work all at once. It's the way with such a powerful tool as Puredata

Are you sure your buttons send note events? Use [midiin] and [sysexin] to dump raw midi data to a [print] statement and see what you have.

The Cec&CaC looks like fun, but too late for new ideas I think. Is it every year?

I used the "Test Audio & Midi Settings" patch in the main menus to check signals and get their values, so we know that the hardware is fine.

Regarding your kind suggestion:- I'm still disassembled right now from a bit of fun last weekend, with controllers still in a box somewhere, but Pd alone seems to think that [midiin] and [sysexin] work only under Linux, while I'm (sadly) on Win-XP.

Anyway, that's how I got the *faders* going via [ctlin X] to their respective controllers in a patch, modified in some cases by [/ 127] or

• or [+ Z] or whatever (the XYZ being number values of course, as appropriate).

But this doesn't work to even set off simple Bangs with the *switches* via [notein X].

I know I'm probably missing something very simple here but can't for the life of me figure it out... as yet.

**Yes CeC & CaC is fun, and will hopefully happen every year. 2006 was the first, and 2007 is looking firm.

Keep well ~ Shankar

[Notein] alone is working fine, but that means every button sets off every bang that such an object is connected to. So the issue is of differentiating the buttons on the basis of the values I get for each from "Test Audio & Midi Settings". Aaaarrrgghhhhh!

Yes, the FaderFoxes are lovely. What I have are the LV1 & LX1 ~ both gifts from a most wonderful electroacoustic legend, in appreciation and support of my self-flagellation with CeC & CaC.

Keyboards have been packed away while I figure out this stuff.

~:o)

[Notein] alone is working fine, but that means every button sets off every bang that such an object is connected to. So the issue is of differentiating the buttons on the basis of the values I get for each from "Test Audio & Midi Settings". Aaaarrrgghhhhh!

Yes, the FaderFoxes are lovely. What I have are the LV1 & LX1 ~ both gifts from a most wonderful electroacoustic legend, in appreciation and support of my self-flagellation with CeC & CaC.

Keyboards have been packed away while I figure out this stuff.

You should be able to differentiate between different buttons by using [pack] and [route], if I understand that the buttons send note events.

Something like

[notein] <-- if i remember correctly, notein outputs (from right to left) channel, velocity, note
| |
[pack f f]
|
[route 60 61 62] <-- note 60 is Middle C i think, use test-audio-and-midi to see what the buttons send

Thank you ClaudiusMaximus.

That is perfect. All systems are go (so far ~:o).

However, the [pack] object in the middle seems to be unnecessary,.. and I can't understand what you intended for the two floats in it.

Maybe someday I will!

Keep well ~ Shankar

That is very useful.

Keep well ~ Shankar