anyone got the p5 dataglove to work on mac intel ?

download the new p5osc and new opensoundcontrol object 

he told me to reinstall or ask the maxlist cause some maxers got it working according to him.

http://www.cnmat.berkeley.edu/OpenSoundControl/dumpOSC.html)

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

works great on G4 but again not on intel....

anyone got the p5 dataglove to work on mac intel ?
download the new p5osc and new opensoundcontrol object 
but still no luck

even mailed Tim Kreger
he told me to reinstall or ask the maxlist cause some maxers got it working according to him.

i download dumpOSC to test it (http://www.cnmat.berkeley.edu/OpenSoundControl/dumpOSC.html)
works fine on g4 but on intel it says

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

i use this patch to test it in max
works great on G4 but again not on intel....

p5-dataglove-on-mac-intel

I'm having no trouble at all. For whatever it's worth, I don't use 

the CNMAT second argument in my udpreceive object.

Do you see data in the terminal if you use the -d option with p5osc?

> anyone got the p5 dataglove to work on intel ?

> download the new p5osc and new opensoundcontrol object

> he told me to reinstall or ask the maxlist cause some maxers got it 

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

> works great on G4 but again not on intel....

> #P newex 90 250 103 196617 route /p5glove_data;

> #P newex 61 197 90 196617 OpenSoundControl;

> #P newex 39 54 128 196617 udpreceive 47110 CNMAT;

I'm having no trouble at all.  For whatever it's worth, I don't use  
the CNMAT second argument in my udpreceive object.

>
> hi list
>
> anyone got the p5 dataglove to work on intel ?
> download the new p5osc and new opensoundcontrol object
> but still no luck
>
> even mailed Tim Kreger
> he told me to reinstall or ask the maxlist cause some maxers got it  
> working according to him.
>
> i download dumpOSC to test it (http://www.cnmat.berkeley.edu/ 
> OpenSoundControl/dumpOSC.html)
> works fine on g4 but on intel it says
>
> [ 100000000000000
> *** ERROR: Bad size count 1275068416 in bundle (only 76 bytes left in
> entire bundle)
>
> i use this patch to test it in max
> works great on G4 but again not on intel....
>
> #P user gswitch2 179 314 39 32 1 0;
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P newex 211 356 50 196617 print hop;
> #P newex 90 250 103 196617 route /p5glove_data;
> #P newex 61 197 90 196617 OpenSoundControl;
> #P user gswitch2 77 95 39 32 0 0;
> #P newex 109 137 50 196617 print poh;
> #P newex 39 54 128 196617 udpreceive 47110 CNMAT;
> #P connect 2 1 1 0;
> #P fasten 0 0 2 1 44 80 82 80 111 80;
> #P connect 6 1 5 0;
> #P connect 4 0 6 1;
> #P connect 3 1 4 0;
> #P connect 2 0 3 0;
> #P window clipboard copycount 7;
>
>
> anyone?...
>
>
> -MJ
>
>


Quote: news wrote on Wed, 17 October 2007 06:17

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

> I'm having no trouble at all. For whatever it's worth, I don't use 

> the CNMAT second argument in my udpreceive object.

What is your computer; I think this is an intel-specific problem.

Quote: news wrote on Wed, 17 October 2007 06:17
----------------------------------------------------
> I'm having no trouble at all.  For whatever it's worth, I don't use  
> the CNMAT second argument in my udpreceive object.
>
>

it's an intel -- but I'm not having any problems......

> Quote: news wrote on Wed, 17 October 2007 06:17

> ----------------------------------------------------

>> I'm having no trouble at all. For whatever it's worth, I don't use

>> the CNMAT second argument in my udpreceive object.

> What is your computer; I think this is an intel-specific problem.

> || michael f. zbyszynski -- molecular gastronimist

>
> Quote: news wrote on Wed, 17 October 2007 06:17
> ----------------------------------------------------
>> I'm having no trouble at all.  For whatever it's worth, I don't use
>> the CNMAT second argument in my udpreceive object.
>>
>>
>
> What is your computer; I think this is an intel-specific problem.
>
> mz
>
>
>
> --
> || michael f. zbyszynski -- molecular gastronimist
> || http://www.cnmat.berkeley.edu/
> || http://www.mikezed.com/
>
>
>


Quote: news wrote on Thu, 18 October 2007 11:23

> it's an intel -- but I'm not having any problems......

Strange. On both my intel Macs I'm getting bad size count errors.

p5osc -d dumps well in the terminal, but the actual OSC packets have a bad size. I've verified this in Max and with dumpOSC.

I've got an Intel iMac and a Macbook Pro, both running OS 10.4.10.

Quote: news wrote on Thu, 18 October 2007 11:23
----------------------------------------------------
> it's an intel -- but I'm not having any problems......
>

p5osc -d dumps well in the terminal, but the actual OSC packets have a bad size.  I've verified this in Max and with dumpOSC.

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

Quote: Roby Steinmetzer wrote on Thu, 18 October 2007 13:38

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

I found a problem where the endianness isn't set correctly. I've successfully built a version that works for me on my Macbook Pro.

I'll check with Tim to see if we can get this fixed.

Quote: Roby Steinmetzer wrote on Thu, 18 October 2007 13:38
----------------------------------------------------
>
> On 17 oct. 07, at 04:49, MJ wrote:
>
> > [ 100000000000000
> > *** ERROR: Bad size count 1275068416 in bundle (only 76 bytes left in
> > entire bundle)
>
> Same problems here on Macbook Pro...
>
> Roby
>
----------------------------------------------------

I found a problem where the endianness isn't set correctly.  I've successfully built a version that works for me on my Macbook Pro.

> I found a problem where the endianness isn't set correctly. I've 

> successfully built a version that works for me on my Macbook Pro.

> I'll check with Tim to see if we can get this fixed.

On 18 oct. 07, at 23:35, mzed wrote:
> I found a problem where the endianness isn't set correctly.  I've  
> successfully built a version that works for me on my Macbook Pro.
>
> I'll check with Tim to see if we can get this fixed.

Please let us know here if you do get it fixed - I've had no luck 

On 18 Oct 2007, at 23:24, Roby Steinmetzer wrote:

>> I found a problem where the endianness isn't set correctly. I've 

>> successfully built a version that works for me on my Macbook Pro.

>> I'll check with Tim to see if we can get this fixed.

Please let us know here if you do get it fixed - I've had no luck  
with my p5 (on my macbook pro) either.

>
> On 18 oct. 07, at 23:35, mzed wrote:
>> I found a problem where the endianness isn't set correctly.  I've  
>> successfully built a version that works for me on my Macbook Pro.
>>
>> I'll check with Tim to see if we can get this fixed.
>
> Thanks,
> Roby


Quote: david stevens wrote on Thu, 18 October 2007 15:49

> Please let us know here if you do get it fixed - I've had no luck 

Quote: david stevens wrote on Thu, 18 October 2007 15:49
----------------------------------------------------
> Please let us know here if you do get it fixed - I've had no luck  
> with my p5 (on my macbook pro) either.
>

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/macosx_usb_hid.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/main.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/IpEndpointName.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/NetworkingUtils.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/UdpSocket.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscOutboundPacketStream.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscPrintReceivedElements.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscReceivedElements.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscTypes.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscReceiveTest.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscSendTests.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscUnitTests.ob

/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/p5glove.ob

>Quote: david stevens wrote on Thu, 18 October 2007 15:49

>----------------------------------------------------

>> Please let us know here if you do get it fixed - I've had no luck 

>> with my p5 (on my macbook pro) either.

>|| michael f. zbyszynski -- molecular gastronimist

ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/macosx_usb_hid.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/main.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/IpEndpointName.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/NetworkingUtils.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/UdpSocket.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscOutboundPacketStream.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscPrintReceivedElements.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscReceivedElements.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscTypes.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscReceiveTest.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscSendTests.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/OscUnitTests.ob
ZeroLink: could not load .o file: 
/Users/mzed/CNMAT/Code/trunk/devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects-normal/i386/p5glove.ob

>Quote: david stevens wrote on Thu, 18 October 2007 15:49
>----------------------------------------------------
>>  Please let us know here if you do get it fixed - I've had no luck 
>>  with my p5 (on my macbook pro) either.
>>
>
>No guarantees:
>
>http://www.mikezed.com/p5osc.zip
>
>Put this in /usr/local/bin/
>
>
>mz
>
>--
>|| michael f. zbyszynski -- molecular gastronimist
>|| http://www.cnmat.berkeley.edu/
>|| http://www.mikezed.com/
>
>
>

Quote: MJ wrote on Thu, 18 October 2007 17:06

> >|| michael f. zbyszynski -- molecular gastronimist

Quote: MJ wrote on Thu, 18 October 2007 17:06
----------------------------------------------------
>
> it says :
>
> ZeroLink: could not load .o file: 

> >
> >No guarantees:
> >
> >http://www.mikezed.com/p5osc.zip
> >
> >Put this in /usr/local/bin/
> >
> >
> >mz
> >
> >--
> >|| michael f. zbyszynski -- molecular gastronimist
> >|| http://www.cnmat.berkeley.edu/
> >|| http://www.mikezed.com/
> >
> >
> >
>
>
>
----------------------------------------------------


Change from "development" to "deployment" in XCode build settings. 

> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 

> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 

> normal/i386/OscPrintReceivedElements.ob

>> Quote: david stevens wrote on Thu, 18 October 2007 15:49

>> ----------------------------------------------------

>> > Please let us know here if you do get it fixed - I've had no luck

>> > with my p5 (on my macbook pro) either.

San Francisco, CA    Work: 857-544-3967

Change from "development" to "deployment" in XCode build settings.   
Zerolink = BAD.

>
> it says :
>
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/macosx_usb_hid.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/main.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/IpEndpointName.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/NetworkingUtils.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/UdpSocket.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/OscOutboundPacketStream.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/OscPrintReceivedElements.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/OscReceivedElements.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/OscTypes.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/OscReceiveTest.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/OscSendTests.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/OscUnitTests.ob
> ZeroLink: could not load .o file: /Users/mzed/CNMAT/Code/trunk/ 
> devices/p5osc/build/p5osc.build/Development/p5osc.build/Objects- 
> normal/i386/p5glove.ob
>
> -mj
>
>> Quote: david stevens wrote on Thu, 18 October 2007 15:49
>> ----------------------------------------------------
>> > Please let us know here if you do get it fixed - I've had no luck
>> > with my p5 (on my macbook pro) either.
>> >
>>
>> No guarantees:
>>
>> http://www.mikezed.com/p5osc.zip
>>
>> Put this in /usr/local/bin/
>>
>>
>> mz
>>
>> --
>> || michael f. zbyszynski -- molecular gastronimist
>> || http://www.cnmat.berkeley.edu/
>> || http://www.mikezed.com/
>>
>>
>>
>

San Francisco, CA	Work: 857-544-3967
Email: bthrew@gmail.com
IM: captogreadmore (AIM)
http:/www.barrythrew.com

Quote: barry threw wrote on Fri, 19 October 2007 17:17

> Change from "development" to "deployment" in XCode build settings. 

Sorry; I was working too quickly. As I said in my last post,

Quote: barry threw wrote on Fri, 19 October 2007 17:17
----------------------------------------------------
> Change from "development" to "deployment" in XCode build settings.   
> Zerolink = BAD.
>

Sorry; I was working too quickly.  As I said in my last post, 

>Quote: barry threw wrote on Fri, 19 October 2007 17:17

>> Change from "development" to "deployment" in XCode build settings. 

>Sorry; I was working too quickly. As I said in my last post,

>Quote: barry threw wrote on Fri, 19 October 2007 17:17
>----------------------------------------------------
>>  Change from "development" to "deployment" in XCode build settings.  
>>  Zerolink = BAD.
>>
>
>Sorry; I was working too quickly.  As I said in my last post,
>
>http://www.mikezed.com/p5osc.zip
>
>should work for everybody now.
>--
>|| michael f. zbyszynski -- molecular gastronimist
>|| http://www.cnmat.berkeley.edu/
>|| http://www.mikezed.com/
>
>
>


I'm also try to use the object P5 by CNMAT, but I don't know the correct use: I must use Terminal before Max (as some older P5 in Max systems). Becouse the object can't "connect to the glove".

I use a Mac Intel Core duo 2 on MacOS 10.6.7

Dear,
I'm also try to use the object P5 by CNMAT, but I don't know the correct use: I must use Terminal before Max (as some older P5 in Max systems). Becouse the object can't "connect to the glove".

I use a Mac Intel Core duo 2 on MacOS 10.6.7


p5 dataglove on mac intel.....