nssykes@hotmail.com

I am trying to use the p5 virtual reality glove to controll sounds useing max/msp. I am haveing problems connecting the p5 glove up to my pc useing the hi and spray objects. It seems to work fine when useing macs, but im haveing problems useing my pc. I know it can be done. Has anyone got any views on how to do this alternitively or by still useing the hi and spray objects. It might just be a problem with drivers, am not sure...

Hi
I am trying to use the p5 virtual reality glove to controll sounds useing max/msp. I am haveing problems connecting the p5 glove up to my pc useing the hi and spray objects. It seems to work fine when useing macs, but im haveing problems useing my pc. I know it can be done. Has anyone got any views on how to do this alternitively or by still useing the hi and spray objects. It might just be a problem with drivers, am not sure...
Kind Regards
Nick


useing-p5-glove-with-maxmsp

Quote: nssykes@hotmail.com wrote on Wed, 21 March 2007 08:22

----------------------------------------------------

> I am trying to use the p5 virtual reality glove to controll sounds useing max/msp. I am haveing problems connecting the p5 glove up to my pc useing the hi and spray objects. It seems to work fine when useing macs, but im haveing problems useing my pc. I know it can be done. Has anyone got any views on how to do this alternitively or by still useing the hi and spray objects. It might just be a problem with drivers, am not sure...

I've been using it with a Mac. But, I think the info you want is here:

http://tech.groups.yahoo.com/group/p5glove/

Quote: nssykes@hotmail.com wrote on Wed, 21 March 2007 08:22
----------------------------------------------------
> Hi
> I am trying to use the p5 virtual reality glove to controll sounds useing max/msp. I am haveing problems connecting the p5 glove up to my pc useing the hi and spray objects. It seems to work fine when useing macs, but im haveing problems useing my pc. I know it can be done. Has anyone got any views on how to do this alternitively or by still useing the hi and spray objects. It might just be a problem with drivers, am not sure...
> Kind Regards
> Nick
----------------------------------------------------

I've been using it with a Mac.  But, I think the info you want is here:

have you managed to get the glove working with an intel mac? i cant get the new drivers to work, the glove is still controlling OS stuff, also the commandline isnt porting osc correctly so max isnt able to recieve the data.

Quote: Wilber wrote on Wed, 21 March 2007 17:41

> have you managed to get the glove working with an intel mac? i cant get the new drivers to work, the glove is still controlling OS stuff, also the commandline isnt porting osc correctly so max isnt able to recieve the data.

It seems to work fine for me on the command line (as far as "p5osc -d", but the packets it sends to Max are 1) on port 7000 and 2) not good OSC.

You should email Tim Kreger... I'll get on it as soon as I finish a couple of big performances....

It is a little fussy about starting the driver; try replugging the glove if it doesn't work.

Quote: Wilber wrote on Wed, 21 March 2007 17:41
----------------------------------------------------
> mz:
>
> have you managed to get the glove working with an intel mac? i cant get the new drivers to work, the glove is still controlling OS stuff, also the commandline isnt porting osc correctly so max isnt able to recieve the data.
>
> Will
----------------------------------------------------

you need to make sure you've got the latest version from the simulus page -

and that you've removed any old p5 drivers. That should stop the P5 being

interpreted as a mouse by the OS. However, I'm sitll having problems with

OSC in Max/MSP. Have chatted with Tim about this but neither of us have had

much time to dig further in to it. The main problem seems to arise from

switching to the intel version of the CNMAT OSC external. If you have the

energy to investigate using an alternative OSC capable host (supercollider?)

then that would help narrow down where the issue is.

> have you managed to get the glove working with an intel mac? i cant get

> the new drivers to work, the glove is still controlling OS stuff, also the

> commandline isnt porting osc correctly so max isnt able to recieve the data.

you need to make sure you've got the latest version from the simulus page -
and that you've removed any old p5 drivers. That should stop the P5 being
interpreted as a mouse by the OS. However, I'm sitll having problems with
OSC in Max/MSP. Have chatted with Tim about this but neither of us have had
much time to dig further in to it. The main problem seems to arise from
switching to the intel version of the CNMAT OSC external. If you have the
energy to investigate using an alternative OSC capable host (supercollider?)
then that would help narrow down where the issue is.

On 3/22/07, WillChadwick  wrote:
>
>
> mz:
>
> have you managed to get the glove working with an intel mac? i cant get
> the new drivers to work, the glove is still controlling OS stuff, also the
> commandline isnt porting osc correctly so max isnt able to recieve the data.
>
> Will
>

I just ran CNMAT's dumpOSC command line utility. I get similar errors to the Max UDP object. Specifically:

*** ERROR: Bad size count 1275068416 in bundle (only 76 bytes left in entire bundle)

So, I'm thinking that the OSC data is not properly formatted on the way out of p5 OSC.

Quote: mj.pedersen wrote on Thu, 22 March 2007 05:43

> you need to make sure you've got the latest version from the simulus page -

> and that you've removed any old p5 drivers. That should stop the P5 being

> interpreted as a mouse by the OS. However, I'm sitll having problems with

> OSC in Max/MSP. Have chatted with Tim about this but neither of us have had

> much time to dig further in to it. The main problem seems to arise from

> switching to the intel version of the CNMAT OSC external. If you have the

> energy to investigate using an alternative OSC capable host (supercollider?)

> then that would help narrow down where the issue is.

> > have you managed to get the glove working with an intel mac? i cant get

> > the new drivers to work, the glove is still controlling OS stuff, also the

> > commandline isnt porting osc correctly so max isnt able to recieve the data.

I just ran CNMAT's dumpOSC command line utility.  I get similar errors to the Max UDP object.  Specifically:

[ 100000000000000
*** ERROR: Bad size count 1275068416 in bundle (only 76 bytes left in entire bundle)

Quote: mj.pedersen wrote on Thu, 22 March 2007 05:43
----------------------------------------------------
> hi Will,
>
> you need to make sure you've got the latest version from the simulus page -
> and that you've removed any old p5 drivers. That should stop the P5 being
> interpreted as a mouse by the OS. However, I'm sitll having problems with
> OSC in Max/MSP. Have chatted with Tim about this but neither of us have had
> much time to dig further in to it. The main problem seems to arise from
> switching to the intel version of the CNMAT OSC external. If you have the
> energy to investigate using an alternative OSC capable host (supercollider?)
> then that would help narrow down where the issue is.
>
> cheers,
>
> Mark
>
> On 3/22/07, WillChadwick  wrote:
> >
> >
> > mz:
> >
> > have you managed to get the glove working with an intel mac? i cant get
> > the new drivers to work, the glove is still controlling OS stuff, also the
> > commandline isnt porting osc correctly so max isnt able to recieve the data.
> >
> > Will
> >
>
>
>
----------------------------------------------------


Just to put in my two pen'orth - those are the same kind of messages 

> I just ran CNMAT's dumpOSC command line utility. I get similar 

> errors to the Max UDP object. Specifically:

> *** ERROR: Bad size count 1275068416 in bundle (only 76 bytes left 

> So, I'm thinking that the OSC data is not properly formatted on the 

Just to put in my two pen'orth - those are the same kind of messages  
I was getting. (MacBook Pro, latest max)

>
> I just ran CNMAT's dumpOSC command line utility.  I get similar  
> errors to the Max UDP object.  Specifically:
>
> [ 100000000000000
> *** ERROR: Bad size count 1275068416 in bundle (only 76 bytes left  
> in entire bundle)
>
> So, I'm thinking that the OSC data is not properly formatted on the  
> way out of p5 OSC.
>
> mz
>
>
>
>


i wrote an external called p5in that... you guessed it, gets input from a p5 glove. the one problem is that it's written for windows, but the code should be pretty much exactly the same.

let me know if anyone wants me to post it, and i will.

you're in luck (sort of)...
i wrote an external called p5in that... you guessed it, gets input from a p5 glove. the one problem is that it's written for windows, but the code should be pretty much exactly the same.
let me know if anyone wants me to post it, and i will.


I would be most greatfull if i could get a copy of that external you wrote. I am a windown user so it would be ideal for me!

Heya
I would be most greatfull if i could get a copy of that external you wrote. I am a windown user so it would be ideal for me!
Cheers
Nick


i get similar messages using both udp and cnmat, i contacted tim in january and had a look a breif look at the source but to no avail. 

if anybody is interested in tackling the p5osc source hre is the link:

https://www.smartelectronix.com:9000/repos/osc/

>i wrote an external called p5in that... you guessed it, gets input >from a p5 glove. the one problem is that it's written for windows, >but the code should be pretty much exactly the same.

>let me know if anyone wants me to post it, and i will.

id like to have a look at the code and try compiling for intel if you dont mind. no garuantees mind! :)

>
> I just ran CNMAT's dumpOSC command line utility. I get similar 
> errors to the Max UDP object. Specifically:
>
> [ 100000000000000
> *** ERROR: Bad size count 1275068416 in bundle (only 76 bytes left 
> in entire bundle)

i get similar messages using both udp and cnmat, i contacted tim in january and had a look a breif look at the source but to no avail. 
if anybody is interested in tackling the p5osc source hre is the link:

>i wrote an external called p5in that... you guessed it, gets input >from a p5 glove. the one problem is that it's written for windows, >but the code should be pretty much exactly the same.
>let me know if anyone wants me to post it, and i will.

Has anyone had any luck with this issue yet? If not I will take a crack at it... Is this problem an issue specifically with p5osc on intel, or is it an aspect of a wider issue?

Has anyone had any luck with this issue yet?  If not I will take a crack at it...  Is this problem an issue specifically with p5osc on intel, or is it an aspect of a wider issue?

as far as I know it is a problem with p5osc on intel only. One potentially

important change between PPC and Intel is that the CNMAT externals for

handling OSC are different. Chatting with Tim, he was surprised at the

errors coming up in Max, as he wasn't aware of any reasony why the OSC

message format being generated on Intel would be different (notice the

Max/MSP error messages seem to indicate an issue with the size of the OSC

packet). I've had a go at trying to read from the OSC output of p5osc using

ChucK, just to see if it's an issue with the CNMAT externals, but I'm

getting segmentation faults from ChucK when trying to read from p5osc and no

further error message, so that's not particularly useful. I haven't tried

with PD yet, but that's another option....

Happy to help if I can - let us know what you find.

> Has anyone had any luck with this issue yet? If not I will take a crack

> at it... Is this problem an issue specifically with p5osc on intel, or is

as far as I know it is a problem with p5osc on intel only.  One potentially
important change between PPC and Intel is that the CNMAT externals for
handling OSC  are different. Chatting with Tim, he was surprised at the
errors coming up in Max, as he wasn't aware of any reasony why the OSC
message format being generated on Intel would be different (notice the
Max/MSP error messages seem to indicate an issue with the size of the OSC
packet). I've had a go at trying to read from the OSC output of p5osc using
ChucK, just to see if it's an issue with the CNMAT externals, but I'm
getting segmentation faults from ChucK when trying to read from p5osc and no
further error message, so that's not particularly useful. I haven't tried
with PD yet, but that's another option....

On 4/25/07, Jeff Ridenour  wrote:
>
>
> Has anyone had any luck with this issue yet?  If not I will take a crack
> at it...  Is this problem an issue specifically with p5osc on intel, or is
> it an aspect of a wider issue?
>
> thanks,
> jeff
>

Easy to choose any general Human Interface Device (HID)

Automatically detects buttons, sliders, etc in use

Automatic scaling to 0.-1. (OSC) or 0-127 (MIDI)

Can output data using either Open Sound Control (OSC) or MIDI

http://www.hf.uio.no/imv/forskning/forskningsprosjekter/

musicalgestures/resources/multicontrol/index.html

I use with Max/msp Reaktor 5 and P5 of course... on a macbook pro 

On 24/04/2007, at 08:11 PM, Mark Pedersen wrote:

> as far as I know it is a problem with p5osc on intel only. One 

> potentially important change between PPC and Intel is that the 

> CNMAT externals for handling OSC are different. Chatting with Tim, 

> he was surprised at the errors coming up in Max, as he wasn't aware 

> of any reasony why the OSC message format being generated on Intel 

> would be different (notice the Max/MSP error messages seem to 

> indicate an issue with the size of the OSC packet). I've had a go 

> at trying to read from the OSC output of p5osc using ChucK, just to 

> see if it's an issue with the CNMAT externals, but I'm getting 

> segmentation faults from ChucK when trying to read from p5osc and 

> no further error message, so that's not particularly useful. I 

> haven't tried with PD yet, but that's another option....

> Happy to help if I can - let us know what you find.

> On 4/25/07, Jeff Ridenour < jridenou@ics.uci.edu> wrote:

> Has anyone had any luck with this issue yet? If not I will take a 

> crack at it... Is this problem an issue specifically with p5osc on 

> intel, or is it an aspect of a wider issue?

Try
Multicontrol by Jensenius
Easy to choose any general Human Interface Device (HID)
Automatically detects buttons, sliders, etc in use
Automatic scaling to 0.-1. (OSC) or 0-127 (MIDI)
Easy to choose desired output scaling
Optional data smoothing
Can output data using either Open Sound Control (OSC) or MIDI
Store presets to xml-files
http://www.hf.uio.no/imv/forskning/forskningsprosjekter/ 
musicalgestures/resources/multicontrol/index.html

I use with Max/msp Reaktor 5 and P5 of course... on a macbook pro  
2.16 ghz

> hi jeff,
>
> as far as I know it is a problem with p5osc on intel only.  One  
> potentially important change between PPC and Intel is that the  
> CNMAT externals for handling OSC  are different. Chatting with Tim,  
> he was surprised at the errors coming up in Max, as he wasn't aware  
> of any reasony why the OSC message format being generated on Intel  
> would be different (notice the Max/MSP error messages seem to  
> indicate an issue with the size of the OSC packet). I've had a go  
> at trying to read from the OSC output of p5osc using ChucK, just to  
> see if it's an issue with the CNMAT externals, but I'm getting  
> segmentation faults from ChucK when trying to read from p5osc and  
> no further error message, so that's not particularly useful. I  
> haven't tried with PD yet, but that's another option....
>
> Happy to help if I can - let us know what you find.
>
> cheers,
>
> Mark
>
> On 4/25/07, Jeff Ridenour < jridenou@ics.uci.edu> wrote:
>
> Has anyone had any luck with this issue yet?  If not I will take a  
> crack at it...  Is this problem an issue specifically with p5osc on  
> intel, or is it an aspect of a wider issue?
>
> thanks,
> jeff
>


looks very interesting. I just tried this but it seems the p5 is not

detected by multicontrol. I suspect this is due to the dummy driver that is

installed as part of Tim's p5osc set up - can you explain a little bit more

about how you've got the p5 configured on your MBP, as far as drivers/HID

> - Easy to choose any general Human Interface Device (HID)

> - Automatically detects buttons, sliders, etc in use

> - Automatic scaling to 0.-1. (OSC) or 0-127 (MIDI)

> - Easy to choose desired output scaling

> - Can output data using either Open Sound Control (OSC) or MIDI

http://www.hf.uio.no/imv/forskning/forskningsprosjekter/musicalgestures/resources/multicontrol/index.html

> I use with Max/msp Reaktor 5 and P5 of course... on a macbook pro 2.16 ghz

> On 24/04/2007, at 08:11 PM, Mark Pedersen wrote:

> as far as I know it is a problem with p5osc on intel only. One

> potentially important change between PPC and Intel is that the CNMAT

> externals for handling OSC are different. Chatting with Tim, he was

> surprised at the errors coming up in Max, as he wasn't aware of any reasony

> why the OSC message format being generated on Intel would be different

> (notice the Max/MSP error messages seem to indicate an issue with the size

> of the OSC packet). I've had a go at trying to read from the OSC output of

> p5osc using ChucK, just to see if it's an issue with the CNMAT externals,

> but I'm getting segmentation faults from ChucK when trying to read from

> p5osc and no further error message, so that's not particularly useful. I

looks very interesting. I just tried this but it seems the p5 is not
detected by multicontrol. I suspect this is due to the dummy driver that is
installed as part of Tim's p5osc set up - can you explain a little bit more
about how you've got the p5 configured on your MBP, as far as drivers/HID
interface etc?

On 4/25/07, Aldo Rodriguez  wrote:
>
> Hi!
>
> Try
> Multicontrol by Jensenius
>
>    - Easy to choose any general Human Interface Device (HID)
>    - Automatically detects buttons, sliders, etc in use
>    - Automatic scaling to 0.-1. (OSC) or 0-127 (MIDI)
>    - Easy to choose desired output scaling
>    - Optional data smoothing
>    - Can output data using either Open Sound Control (OSC) or MIDI
>    - Store presets to xml-files
>
>
> http://www.hf.uio.no/imv/forskning/forskningsprosjekter/musicalgestures/resources/multicontrol/index.html
>
> I use with Max/msp Reaktor 5 and P5 of course... on a macbook pro 2.16 ghz
>
> Bang!
>
> Aldo Rodriguez 
>
>
> On 24/04/2007, at 08:11 PM, Mark Pedersen wrote:
>
> hi jeff,
>
> as far as I know it is a problem with p5osc on intel only.  One
> potentially important change between PPC and Intel is that the CNMAT
> externals for handling OSC  are different. Chatting with Tim, he was
> surprised at the errors coming up in Max, as he wasn't aware of any reasony
> why the OSC message format being generated on Intel would be different
> (notice the Max/MSP error messages seem to indicate an issue with the size
> of the OSC packet). I've had a go at trying to read from the OSC output of
> p5osc using ChucK, just to see if it's an issue with the CNMAT externals,
> but I'm getting segmentation faults from ChucK when trying to read from
> p5osc and no further error message, so that's not particularly useful. I
> haven't tried with PD yet, but that's another option....
>
> Happy to help if I can - let us know what you find.
>
> cheers,
>
> Mark
>
> On 4/25/07, Jeff Ridenour < jridenou@ics.uci.edu> wrote:
> >
> >
> > Has anyone had any luck with this issue yet?  If not I will take a crack
> > at it...  Is this problem an issue specifically with p5osc on intel, or is
> > it an aspect of a wider issue?
> >
> > thanks,
> > jeff
> >
>
>
>
>
>
>

If any of you are looking for an easy way to use the p5 glove in max, here is one way if you dont already know it;

download a midi converter for the glove, they are easy to find!

There is something called Midiyoke which allowes devices and applications to communicate with each other, you need to download midiyoke and install. In the midi converter app for, the p5 glove you will be able to choose midiyoke as a port for the glove. Then in max/msp use the ctl in object and select midiyoke, and you will find variables moveing up and down in accordance to the glove.

Hi People
If any of you are looking for an easy way to use the p5 glove in max, here is one way if you dont already know it;
download a midi converter for the glove, they are easy to find!
There is something called Midiyoke which allowes devices and applications to communicate with each other, you need to download midiyoke and install. In the midi converter app for, the p5 glove you will be able to choose midiyoke as a port for the glove. Then in max/msp use the ctl in object and select midiyoke, and you will find variables moveing up and down in accordance to the glove.

Hope this helps some of you 
Cheers
Nick


P5 midilove is another app... very simple and efective...but, windows 

On 25/04/2007, at 11:30 AM, Nick Sykes wrote:

> If any of you are looking for an easy way to use the p5 glove in 

> max, here is one way if you dont already know it;

> download a midi converter for the glove, they are easy to find!

> There is something called Midiyoke which allowes devices and 

> applications to communicate with each other, you need to download 

> midiyoke and install. In the midi converter app for, the p5 glove 

> you will be able to choose midiyoke as a port for the glove. Then 

> in max/msp use the ctl in object and select midiyoke, and you will 

> find variables moveing up and down in accordance to the glove.

Hi...
it seems ok... but only for windows...
P5 midilove is another app... very simple and efective...but, windows  
only too...

>
> Hi People
> If any of you are looking for an easy way to use the p5 glove in  
> max, here is one way if you dont already know it;
> download a midi converter for the glove, they are easy to find!
> There is something called Midiyoke which allowes devices and  
> applications to communicate with each other, you need to download  
> midiyoke and install. In the midi converter app for, the p5 glove  
> you will be able to choose midiyoke as a port for the glove. Then  
> in max/msp use the ctl in object and select midiyoke, and you will  
> find variables moveing up and down in accordance to the glove.
>
> Hope this helps some of you
> Cheers
> Nick


I'm having no problem with the p5 on an intel. I use an altered 

version of Dan Lehrlich's p5 glove MIDI assigner, replacing otdup 

with udpreceive, and osc-route with [route /p5glove_data]. All works 

great (insofar as the p5 works great at all).

On Apr 25, 2007, at 16:40, Aldo Rodriguez wrote:

> P5 midilove is another app... very simple and efective...but, 

> On 25/04/2007, at 11:30 AM, Nick Sykes wrote:

>> If any of you are looking for an easy way to use the p5 glove in 

>> max, here is one way if you dont already know it;

>> download a midi converter for the glove, they are easy to find!

>> There is something called Midiyoke which allowes devices and 

>> applications to communicate with each other, you need to download 

>> midiyoke and install. In the midi converter app for, the p5 glove 

>> you will be able to choose midiyoke as a port for the glove. Then 

>> in max/msp use the ctl in object and select midiyoke, and you will 

>> find variables moveing up and down in accordance to the glove.

I'm having no problem with the p5 on an intel.  I use an altered  
version of Dan Lehrlich's p5 glove MIDI assigner, replacing otdup  
with udpreceive, and osc-route with [route /p5glove_data].  All works  
great (insofar as the p5 works great at all).

> Hi...
> it seems ok... but only for windows...
> P5 midilove is another app... very simple and efective...but,  
> windows only too...
>
> Bang!
>
> Aldo R
>
>
> On 25/04/2007, at 11:30 AM, Nick Sykes wrote:
>
>>
>> Hi People
>> If any of you are looking for an easy way to use the p5 glove in  
>> max, here is one way if you dont already know it;
>> download a midi converter for the glove, they are easy to find!
>> There is something called Midiyoke which allowes devices and  
>> applications to communicate with each other, you need to download  
>> midiyoke and install. In the midi converter app for, the p5 glove  
>> you will be able to choose midiyoke as a port for the glove. Then  
>> in max/msp use the ctl in object and select midiyoke, and you will  
>> find variables moveing up and down in accordance to the glove.
>>
>> Hope this helps some of you
>> Cheers
>> Nick
>


that's very interesting to hear. which versions of p5osc and udpreceive are

I managed to get multicontrol working with the p5 on my MBP, but I like the

p5 glove MIDI assigner better as far as a cleaner interface to the p5 goes.

> I'm having no problem with the p5 on an intel. I use an altered

> version of Dan Lehrlich's p5 glove MIDI assigner, replacing otdup

> with udpreceive, and osc-route with [route /p5glove_data]. All works

> great (insofar as the p5 works great at all).

> On Apr 25, 2007, at 16:40, Aldo Rodriguez wrote:

> > it seems ok... but only for windows...

> > P5 midilove is another app... very simple and efective...but,

> > On 25/04/2007, at 11:30 AM, Nick Sykes wrote:

> >> If any of you are looking for an easy way to use the p5 glove in

> >> max, here is one way if you dont already know it;

> >> download a midi converter for the glove, they are easy to find!

> >> There is something called Midiyoke which allowes devices and

> >> applications to communicate with each other, you need to download

> >> midiyoke and install. In the midi converter app for, the p5 glove

> >> you will be able to choose midiyoke as a port for the glove. Then

> >> in max/msp use the ctl in object and select midiyoke, and you will

> >> find variables moveing up and down in accordance to the glove.

that's very interesting to hear. which versions of p5osc and  udpreceive are
you running?

I managed to get multicontrol working with the p5 on my MBP, but I like the
p5 glove MIDI assigner better as far as a cleaner interface to the p5 goes.

On 5/4/07, mattyo  wrote:
>
> I'm having no problem with the p5 on an intel.  I use an altered
> version of Dan Lehrlich's p5 glove MIDI assigner, replacing otdup
> with udpreceive, and osc-route with [route /p5glove_data].  All works
> great (insofar as the p5 works great at all).
>
> M
>
>
>
>
> On Apr 25, 2007, at 16:40, Aldo Rodriguez wrote:
>
> > Hi...
> > it seems ok... but only for windows...
> > P5 midilove is another app... very simple and efective...but,
> > windows only too...
> >
> > Bang!
> >
> > Aldo R
> >
> >
> > On 25/04/2007, at 11:30 AM, Nick Sykes wrote:
> >
> >>
> >> Hi People
> >> If any of you are looking for an easy way to use the p5 glove in
> >> max, here is one way if you dont already know it;
> >> download a midi converter for the glove, they are easy to find!
> >> There is something called Midiyoke which allowes devices and
> >> applications to communicate with each other, you need to download
> >> midiyoke and install. In the midi converter app for, the p5 glove
> >> you will be able to choose midiyoke as a port for the glove. Then
> >> in max/msp use the ctl in object and select midiyoke, and you will
> >> find variables moveing up and down in accordance to the glove.
> >>
> >> Hope this helps some of you
> >> Cheers
> >> Nick
> >
>
>

On May 4, 2007, at 10:04, Mark Pedersen wrote:

> that's very interesting to hear. which versions of p5osc and 

USEING P5 GLOVE WITH MAX/MSP