I'd like to use MIDI data to controll the mouse pointer and mouse clicks. Is there some output object to controll the mouse pointer?

hmm interesting question.
do you know any music software that can do that?
are you saying you want to use your gear as a mouse?
a keyboard with an x/y joystick would be hot for that!

i don't know if there's a one-stop solution,

but you could do something close:

just use the normal [midiin] [ctlin] [msgin] objects to get your midi data,

and then use the [dyn~] external to move stuff round. not sure about the mouse clicks though.

also, look into HID ... maybe it can help??

just found this
[url=http://www.analogx.com/contents/download/audio/mousemod.htm ]http://www.analogx.com/contents/download/audio/mousemod.htm

maybe that will help? just have pd intercept the midi?

also there must be something to intercept mouse actions in the graphics packages for PD?

@Laserbeak said:

also there must be something to intercept mouse actions in the graphics packages for PD?

Gridflow's [#out window] outputs mouse and keyboard information when the window has focus.

I don't know of any Pd package that can control the system mouse/keyboard to let you control software other than Pd itself. I think [dyn~] is the best way to get Pd to control itself, but it has limitations.

CPNmouse (http://cpnmouse.sourceforge.net/) is a driver for Windows that has support for multiple mice. Maybe PD could pipe mouse data (emulate a mouse) in a way that CPNmouse recognizes as a second mouse?

@tacitdynamite said:

CPNmouse (http://cpnmouse.sourceforge.net/) is a driver for Windows that has support for multiple mice. Maybe PD could pipe mouse data (emulate a mouse) in a way that CPNmouse recognizes as a second mouse?

this seems to be a good area to investigate. i remember last year my group set up a system where we mapped movement as seen by a camera to a pointing device. we did the motion tracking with eyecon, but i can't remember how we got that data to the cursor object. i think we had another piece of software to do that part, which most likely communicated with eyecon via OSC (which means it would be quite easy to go from midi to pd to OSC etc).

zac hilbert