Forums > MaxMSP

OSCulator midiin?

December 14, 2007 | 7:21 am

Sorry to be such a dim brain on this but having ditched aka and moved on to OSCulator to get input from my Wii remote I stuck and cant find any answers t such a basic question.

Once I have OSCulator connected to my wii and want to work with it in MAX i assume I do this with midiin? But not working with midi much dont understand how to separate out the flow of data from OSCulator.

By channels? Ports?

an example would be great.

Thanks

James


December 14, 2007 | 2:16 pm

I had a go at getting wii into max for the first time this week, – was
not able to get it to work with the aka. object, but had little
trouble with OSCulator…

two ways to get the midi CC info (which you use will depend on if you
want the controller number before or after the value with
right-to-left order):

#P window setfont "Fixedwidth Serif" 12.;
#P window linecount 1;
#P newex 254 85 45 1441804 ctlin;
#P comment 271 202 38 1441804 ctl#;
#P number 271 185 35 12 0 0 0 22 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 229 185 35 12 0 0 0 22 0 0 0 221 221 221 222 222 222 0 0 0;
#P comment 229 202 38 1441804 val;
#P comment 161 204 38 1441804 val;
#P number 161 187 35 12 0 0 0 22 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 119 187 35 12 0 0 0 22 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 119 142 52 1441804 unpack;
#P newex 93 114 92 1441804 midiparse;
#P newex 93 85 52 1441804 midiin;
#P comment 119 204 38 1441804 ctl#;
#P connect 11 1 9 0;
#P connect 11 0 8 0;
#P connect 3 1 5 0;
#P connect 3 0 4 0;
#P connect 2 2 3 0;
#P connect 1 0 2 0;
#P window clipboard copycount 12;

On 14/12/2007, James Charlton wrote:
>
> Sorry to be such a dim brain on this but having ditched aka and moved on to OSCulator to get input from my Wii remote I stuck and cant find any answers t such a basic question.
>
> Once I have OSCulator connected to my wii and want to work with it in MAX i assume I do this with midiin? But not working with midi much dont understand how to separate out the flow of data from OSCulator.
>
> By channels? Ports?
>
> an example would be great.
>
> Thanks
>
> James
>


December 14, 2007 | 8:17 pm

open OSCulator 2.2
make sure you also have the Bluetooth Apple System Preference panel open
with the ‘Devices’ Bluetooth control tab showing

go to OSCulator and start the discovery process
this will find the wii
but it will fail
so go back to the Bluetooth panel in the Apple System Prefs and
delete that instance of the bluetooth wii
go to the OSCulator and start the discovery process again
the wii should be recognized and all should be working finally
it takes two times for it to work for some reason

type in a port number
something like 8002 or whatever you want in the box in the upper left
hand corner of OSCulator

all the parameters from the wii should flow into the main window
push all the buttons so they show up as well

pull down on the ‘Type’ pull down menu
and select MIDI CC
then go to the ‘Event’ pull down menu next to it and set the
controller to the number you want to send

for example:
set the xyz to ch1 & controllers to 1 2 3
set the pry and accel to ch2 & the contollers to 5 6 7 8
open the Max patch attached below

this should help get you started:

max v2;
#N vpatcher 102 52 702 452;
#P window setfont "Sans Serif" 12.;
#P comment 243 193 129 196620 pry/accel vals;
#P window setfont "Sans Serif" 18.;
#P comment 41 71 204 196626 wii OSCulator patch;
#P window setfont "Sans Serif" 9.;
#P comment 219 199 14 196617 |;
#P comment 219 185 14 196617 |;
#P comment 219 170 14 196617 |;
#P comment 219 155 14 196617 |;
#P comment 218 141 14 196617 |;
#P window setfont "Sans Serif" 18.;
#P comment 251 106 198 196626 controllers 5-8//ch2;
#P window setfont "Sans Serif" 9.;
#P number 423 168 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 423 139 48 196617 ctlin 8 2;
#P number 295 168 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 295 139 48 196617 ctlin 6 2;
#P number 363 168 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 363 139 48 196617 ctlin 7 2;
#P newex 236 139 48 196617 ctlin 5 2;
#P number 236 168 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P window setfont "Sans Serif" 12.;
#P comment 39 193 65 196620 xyz vals;
#P window setfont "Sans Serif" 9.;
#P number 99 168 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 99 139 48 196617 ctlin 2 1;
#P window setfont "Sans Serif" 18.;
#P comment 39 107 203 196626 controllers 1-3 //ch1;
#P window setfont "Sans Serif" 9.;
#P number 167 168 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 167 139 48 196617 ctlin 3 1;
#P newex 40 139 48 196617 ctlin 1 1;
#P number 40 168 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P user panel 35 52 455 203;
#X brgb 191 191 191;
#X frgb 0 0 0;
#X border 1;
#X rounded 0;
#X shadow 0;
#X done;
#P connect 2 0 1 0;
#P connect 6 0 7 0;
#P connect 3 0 4 0;
#P connect 10 0 9 0;
#P connect 13 0 14 0;
#P connect 11 0 12 0;
#P connect 15 0 16 0;
#P pop;

On Dec 13, 2007, at 11:21 PM, James Charlton wrote:

>
> Sorry to be such a dim brain on this but having ditched aka and
> moved on to OSCulator to get input from my Wii remote I stuck and
> cant find any answers t such a basic question.
>
> Once I have OSCulator connected to my wii and want to work with it
> in MAX i assume I do this with midiin? But not working with midi
> much dont understand how to separate out the flow of data from
> OSCulator.
>
> By channels? Ports?
>
> an example would be great.
>
> Thanks
>
> James


December 15, 2007 | 4:21 am

Fantastic – that was the missing link I needed – I don’t do much with midi so was not familiar with those objects.

Sam – looks like midiparse gives out tons more data but thats not applicable in the case of wwi is it? Also when you talk about the left right order i dont quite see how that would be used if i use an argument to define each ctlin as per Kims patch?

Kim not sure why you say to open Blue tooth and delete. Yes it seems OSculator needs two cracks at it but i had just been hitting start discovery again.

Anyway thanks for the pointers and sorry for the delay in my response had to take the kids to the beach!

James.


December 15, 2007 | 7:06 am

On Dec 14, 2007, at 8:21 PM, James Charlton wrote:

>
> Fantastic – that was the missing link I needed – I don’t do much
> with midi so was not familiar with those objects.
>
> Sam – looks like midiparse gives out tons more data but thats not
> applicable in the case of wwi is it? Also when you talk about the
> left right order i dont quite see how that would be used if i use
> an argument to define each ctlin as per Kims patch?
you should pay attention to how the MIDI CC#’s map to the xyz and
pry&accel data
I noticed my patch had them reversed
so please redo the plumbing in my patch as needed ;)

>
> Kim not sure why you say to open Blue tooth and delete. Yes it
> seems OSculator needs two cracks at it but i had just been hitting
> start discovery again.
this is the secret handshake that needs to occur on my G4 PB for
things to get working — not sure what hardware you are using…
but glad to hear it works just by hitting discovery again
>
> Anyway thanks for the pointers and sorry for the delay in my
> response had to take the kids to the beach!
enjoy! I’ve been using the IR data from the wii for a project and I
think Maxer’s are really going to like the new version of OSCulator
coming out soon!
stay tuned
KIM


Viewing 5 posts - 1 through 5 (of 5 total)