Kasper

yesterday I was working on an older piece of mine (played last time 

one year ago, and to be replayed tomorrow) which uses 2 macs and a 

back-and-forth communication between them (one is "slaved" to the 

When i first did this piece i was using OpenSoundControl, otudp write 

and read etc etc, made a network with the 2 macs (etherenet - one 

direct cable) gave them manually their IP adresses etc

Now on the 2 same macs - on which the sytems and the max versions 

were most certainly upgraded, both are OSX47, and maxmsp 457 the 

after trying many combinations I came to the conclusion than it was 

the OpenSoundControl object which was not working - the otudp are 

receiving "things" - not very exciting, but things - and 

OpenSoundControl outputs only on its left and right outlets (bang and 

some time confirmation, whatever) but nothing on its middle oulet.

I tried with as many OpenSoundControl objects I could find (from 

different distributions, with different creation dates) - which is 3 

Yes I am sure there was only ONE OpenSoundControl in the serach path 

___so, does it mean OpenSoundControl does not work with OSX47 ? (I 

belive at the time, one year ago, it was the other big cat, was it 

no problem for the patch as I am using net.maxhole (which is just 

great) but I am wondering _ I have soem other patches from that era 

(one year ago) using OSC, it would be so much easier to be able to 

use them just as they are (ok, now it is easy, since i know about 

net.maxhole - yesterday it took me quite some time to get what was 

yesterday I was working on an older piece of mine (played last time 
one year ago, and to be replayed tomorrow) which uses 2 macs and a 
back-and-forth communication between them (one is "slaved" to the 
other..)

When i first did this piece i was using OpenSoundControl, otudp write 
and read etc etc, made a network with the 2 macs (etherenet - one 
direct cable) gave them manually their IP adresses etc

Now on the 2 same macs - on which the sytems and the max versions 
were most certainly upgraded, both are OSX47, and maxmsp 457 the 
communication did not work

after trying many combinations I came to the conclusion than it was 
the OpenSoundControl object which was not working - the otudp are 
receiving "things" - not very exciting, but things - and 
OpenSoundControl outputs only on its left and right outlets (bang and 
some time confirmation, whatever) but nothing on its middle oulet.

I tried with as many OpenSoundControl objects I could find (from 
different distributions, with different creation dates) - which is 3 
different.
Yes I am sure there was only ONE OpenSoundControl in the serach path 
at the time.

___so, does it mean OpenSoundControl does not work with OSX47 ? (I 
belive at the time, one year ago, it was the other big cat, was it 
tiger or panther??)

no problem for the patch as I am using net.maxhole (which is just 
great) but I am wondering _ I have soem other patches from that era 
(one year ago) using OSC, it would be so much easier to be able to 
use them just as they are (ok, now it is easy, since i know about 
net.maxhole - yesterday it took me quite some time to get what was 
not working, and trying to fix it

kasper
-- 
  Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com

osc-mac-osx-4-7

I have a similar situation in that I have taken over an extensive Max 

project that uses OpenSoundControl w/otudp read/write and am moving 

Are you sure that it's OpenSoundControl that's causing the problem? 

My suspicion was that udpsend and udpreceive may not be exact drop- 

and-play replacements for their orphaned cousins from CNMAT.

I haven't worked out the details (UDP communication isn't my top 

priority right now). I was expecting to have to write wrapper objects 

around udpsend/receive to make them behave like the otudp object. But 

if net.maxhole does the trick, that's also good to know.

On 20-Nov-2006, at 10:12, Kasper T Toeplitz wrote:

> yesterday I was working on an older piece of mine (played last time 

> one year ago, and to be replayed tomorrow) which uses 2 macs and a 

> back-and-forth communication between them (one is "slaved" to the 

> When i first did this piece i was using OpenSoundControl, otudp 

> write and read etc etc, made a network with the 2 macs (etherenet - 

> one direct cable) gave them manually their IP adresses etc

> Now on the 2 same macs - on which the sytems and the max versions 

> were most certainly upgraded, both are OSX47, and maxmsp 457 the 

> after trying many combinations I came to the conclusion than it was 

> the OpenSoundControl object which was not working - the otudp are 

> receiving "things" - not very exciting, but things - and 

> OpenSoundControl outputs only on its left and right outlets (bang 

> and some time confirmation, whatever) but nothing on its middle oulet.

> I tried with as many OpenSoundControl objects I could find (from 

> different distributions, with different creation dates) - which is 

> Yes I am sure there was only ONE OpenSoundControl in the serach 

> ___so, does it mean OpenSoundControl does not work with OSX47 ? (I 

> belive at the time, one year ago, it was the other big cat, was it 

> no problem for the patch as I am using net.maxhole (which is just 

> great) but I am wondering _ I have soem other patches from that era 

> (one year ago) using OSC, it would be so much easier to be able to 

> use them just as they are (ok, now it is easy, since i know about 

> net.maxhole - yesterday it took me quite some time to get what was 

Peter Castine +--> Litter Power & Litter Bundle for Jitter

Interface Building for |home | chez nous|

Max/MSP Extremely cool |bei uns | i nostri|

I have a similar situation in that I have taken over an extensive Max  
project that uses OpenSoundControl w/otudp read/write and am moving  
it to Max 4.6.

Are you sure that it's OpenSoundControl that's causing the problem?  
My suspicion was that udpsend and udpreceive may not be exact drop- 
and-play replacements for their orphaned cousins from CNMAT.

I haven't worked out the details (UDP communication isn't my top  
priority right now). I was expecting to have to write wrapper objects  
around udpsend/receive to make them behave like the otudp object. But  
if net.maxhole does the trick, that's also good to know.

> hi
>
> yesterday I was working on an older piece of mine (played last time  
> one year ago, and to be replayed tomorrow) which uses 2 macs and a  
> back-and-forth communication between them (one is "slaved" to the  
> other..)
>
> When i first did this piece i was using OpenSoundControl, otudp  
> write and read etc etc, made a network with the 2 macs (etherenet -  
> one direct cable) gave them manually their IP adresses etc
>
> It all worked
>
> Now on the 2 same macs - on which the sytems and the max versions  
> were most certainly upgraded, both are OSX47, and maxmsp 457 the  
> communication did not work
>
> after trying many combinations I came to the conclusion than it was  
> the OpenSoundControl object which was not working - the otudp are  
> receiving "things" - not very exciting, but things - and  
> OpenSoundControl outputs only on its left and right outlets (bang  
> and some time confirmation, whatever) but nothing on its middle oulet.
>
> I tried with as many OpenSoundControl objects I could find (from  
> different distributions, with different creation dates) - which is  
> 3 different.
> Yes I am sure there was only ONE OpenSoundControl in the serach  
> path at the time.
>
> ___so, does it mean OpenSoundControl does not work with OSX47 ? (I  
> belive at the time, one year ago, it was the other big cat, was it  
> tiger or panther??)
>
> no problem for the patch as I am using net.maxhole (which is just  
> great) but I am wondering _ I have soem other patches from that era  
> (one year ago) using OSC, it would be so much easier to be able to  
> use them just as they are (ok, now it is easy, since i know about  
> net.maxhole - yesterday it took me quite some time to get what was  
> not working, and trying to fix it
>
> thanks
>
> kasper
> -- 
>  Kasper T. Toeplitz
> noise, composition, bass, computer
> http://www.sleazeArt.com
>
>

--------------    http://www.bek.no/~pcastine/Litter/    -------------
Peter Castine             +--> Litter Power & Litter Bundle for Jitter
                                Universal Binaries on the way
iCE:  Sequencing,  Recording &
       Interface  Building  for                   |home    | chez nous|
       Max/MSP   Extremely cool                   |bei uns |  i nostri|
       http://www.dspaudio.com/                   http://www.castine.de

>Are you sure that it's OpenSoundControl that's causing the problem? 

>My suspicion was that udpsend and udpreceive may not be exact 

>drop-and-play replacements for their orphaned cousins from CNMAT.

I actually was using otudp write and read and not udpsend/receive 

(which were not on my HD as it appears than they were not in the 

max457 distribution - ej pointed later that evening that they are on 

but I am sure it's the OpenSoundControl which causes problem:

sending a message (with patches which were working fine before) from 

mac 1 to mac 2, checking with a print, the otudp read receives stuff, 

the OpenSoundControl receives stuff as well (1st and 3rd outlets) but 

maxhole and route did the trick in a few seconds - too bad it took me 

a few hours to "discover" what was going wrong and to read about 

>
>
>Are you sure that it's OpenSoundControl that's causing the problem? 
>My suspicion was that udpsend and udpreceive may not be exact 
>drop-and-play replacements for their orphaned cousins from CNMAT.

"orphaned cousins"??
I actually was using otudp write and read and not udpsend/receive 
(which were not on my HD as it appears than they were not in the 
max457 distribution - ej pointed later that evening that they are on 
the incremental update page)

sending a message (with patches which were working fine before) from 
mac 1 to mac 2, checking with a print, the otudp read receives stuff, 
the OpenSoundControl receives stuff as well (1st and 3rd outlets) but 
nothing comes out of the 2nd outlet.

maxhole and route did the trick in a few seconds - too bad it took me 
a few hours to "discover" what was going wrong and to read about 
maxhole!!!

-- 
  Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com

20/11/06, kl. 10:12 +0100 , skrev Kasper T Toeplitz:

>___so, does it mean OpenSoundControl does not work with OSX47 ? (I 

>belive at the time, one year ago, it was the other big cat, was it 

>no problem for the patch as I am using net.maxhole (which is just 

>great) but I am wondering _ I have soem other patches from that era 

>(one year ago) using OSC, it would be so much easier to be able to 

>use them just as they are (ok, now it is easy, since i know about 

>net.maxhole - yesterday it took me quite some time to get what was 

I thougt I had updated my version of OpenSoundControl, but checking it

now I can see that I am using an old version (creation date 3. juli

2001). I have it working on OSX 10.4.8 MaxMSP 4.5.7. So it might be

worth to try it out on OSX 10.4.7. I can mail you this version off list

>___so, does it mean OpenSoundControl does not work with OSX47 ? (I 
>belive at the time, one year ago, it was the other big cat, was it 
>tiger or panther??)
>
>no problem for the patch as I am using net.maxhole (which is just 
>great) but I am wondering _ I have soem other patches from that era 
>(one year ago) using OSC, it would be so much easier to be able to 
>use them just as they are (ok, now it is easy, since i know about 
>net.maxhole - yesterday it took me quite some time to get what was 
>not working, and trying to fix it

I thougt I had updated my version of OpenSoundControl, but checking it
now I can see that I am using an old version (creation date 3. juli
2001). I have it working on OSX 10.4.8 MaxMSP 4.5.7. So it might be
worth to try it out on OSX 10.4.7. I can mail you this version off list
if you like.

> i believe you are both right. my idea is that some OSC 

> implementation contain mistakes or, perhaps, OSC implementation 

> changed and has not yet beed adapted to maxmsp

I am not aware of any outstanding issues with the OpenSoundControl implementation in Max/MSP. I use it very frequently here at the lab with no problems.

The current version for CFM is 1.9.5. Get that from the CNMAT download site:

http://www.cnmat.berkeley.edu/MAX/downloads/

If that doesn't help, send me a patch that doesn't work. Tell me if you're using PPC or Intel. The lab is generally running OS 10.4.8 -- it's going to be a bit of a drag to set up a special machine to test this bug. Any help you could give us about reproducing it would expedite a fix.

When using udpsend and udpreceive, not that there is an argument on the receive end to switch into "CNMAT" mode.

> i believe you are both right.  my idea is that some OSC  
> implementation contain mistakes or, perhaps, OSC implementation  
> changed and has not yet beed adapted to maxmsp
>

I am not aware of any outstanding issues with the OpenSoundControl implementation in Max/MSP.  I use it very frequently here at the lab with no problems.

The current version for CFM is 1.9.5.  Get that from the CNMAT download site:

If that doesn't help, send me a patch that doesn't work.  Tell me if you're using PPC or Intel.  The lab is generally running OS 10.4.8 -- it's going to be a bit of a drag to set up a special machine to test this bug.  Any help you could give us about reproducing it would expedite a fix.

>The current version for CFM is 1.9.5. Get that from the CNMAT download site:

the current version (named "everything for Mac OSX (CFM)") is a 

folder with only ONE object??? [2threshattck~]

wow, seems like a really striped down "everything"!!!

>
>The current version for CFM is 1.9.5.  Get that from the CNMAT download site:
>
>http://www.cnmat.berkeley.edu/MAX/downloads/
>

the current version (named "everything for Mac OSX (CFM)") is a 
folder with only ONE object??? [2threshattck~]

no kasper, the problem is with stuffit - recent version cant unstuff 

recent posts here were advising to use version 9.

i am having the same problem (only one object), still no time to look 

Am 21.11.2006 um 10:44 schrieb Kasper T Toeplitz:

>> The current version for CFM is 1.9.5. Get that from the CNMAT 

> the current version (named "everything for Mac OSX (CFM)") is a 

> folder with only ONE object??? [2threshattck~]

> wow, seems like a really striped down "everything"!!!

no kasper, the problem is with stuffit - recent version cant unstuff  
it sucessfully.
recent posts here were advising to use version 9.
i am having the same problem (only one object), still no time to look  
for a solution/downgrade

hans w. koch
im krahnenhof 11
d-50668 koeln
+49-221-554902
www.hans-w-koch.net

>>
>> The current version for CFM is 1.9.5.  Get that from the CNMAT  
>> download site:
>>
>> http://www.cnmat.berkeley.edu/MAX/downloads/
>>
>
>
> ????????????
>
> the current version (named "everything for Mac OSX (CFM)") is a  
> folder with only ONE object??? [2threshattck~]
>
> wow, seems like a really striped down "everything"!!!
>
> best
>
> kasper
> -- 
>  Kasper T. Toeplitz
> noise, composition, bass, computer
> http://www.sleazeArt.com
>
>

>no kasper, the problem is with stuffit - recent version cant unstuff 

>recent posts here were advising to use version 9.

>i am having the same problem (only one object), still no time to 

oh, yes sorry (i remember the thread but I am afarid i did not follow 

it!!) - however I tried on 2 macs with 2 versions of stuffit

>no kasper, the problem is with stuffit - recent version cant unstuff 
>it sucessfully.
>recent posts here were advising to use version 9.
>i am having the same problem (only one object), still no time to 
>look for a solution/downgrade
>

oh, yes sorry (i remember the thread but I am afarid i did not follow 
it!!) - however I tried on 2 macs with 2 versions of stuffit

Quote: Kasper T Toeplitz wrote on Tue, 21 November 2006 02:42

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

> >no kasper, the problem is with stuffit - recent version cant unstuff 

> >recent posts here were advising to use version 9.

> >i am having the same problem (only one object), still no time to 

> oh, yes sorry (i remember the thread but I am afarid i did not follow 

> it!!) - however I tried on 2 macs with 2 versions of stuffit

We're looking into solutions to this stuffit disaster. Meanwhile, I hope it works if you download the objects individually. Clicking on the version number in the object's row will do it.

Quote: Kasper T Toeplitz wrote on Tue, 21 November 2006 02:42
----------------------------------------------------
> >no kasper, the problem is with stuffit - recent version cant unstuff 
> >it sucessfully.
> >recent posts here were advising to use version 9.
> >i am having the same problem (only one object), still no time to 
> >look for a solution/downgrade
> >
>
>
> oh, yes sorry (i remember the thread but I am afarid i did not follow 
> it!!) - however I tried on 2 macs with 2 versions of stuffit
>

We're looking into solutions to this stuffit disaster.  Meanwhile, I hope it works if you download the objects individually.  Clicking on the version number in the object's row will do it.

Quote: jmb wrote on Mon, 20 November 2006 20:22

> do you use it to share information between intel, windows or linux 

> machines and ppc g4 or g3 machines, as described in my post?

> > The current version for CFM is 1.9.5. Get that from the CNMAT 

> i'll do this. when i experienced the described behavior last summer, 

> i downloaded the latest version. 10.4.8 didn't exist by july

I've just been sending /giveme some please 44 from my intel machine to my PPC with no problems. I tried Max 4.5.7 and 4.6.2 on the intel side, 4.5.7 on the PPC side. I tried udpsend/udpreceive and otudp in various combinations.

What version of OpenSoundControl are you using? (Send it the message "version" to find out.) There were some substantial bug fixes in 1.9.4.

Quote: jmb wrote on Mon, 20 November 2006 20:22
----------------------------------------------------

> do you use it to share information between intel, windows or linux  
> machines and ppc g4 or g3 machines, as described in my post?
>
>
> >
> > The current version for CFM is 1.9.5.  Get that from the CNMAT  
> > download site:
> >
> > http://www.cnmat.berkeley.edu/MAX/downloads/
>
> i'll do this. when i experienced the described behavior last summer,  
> i downloaded the latest version.  10.4.8 didn't exist by july
>
> >
>

I've just been sending /giveme some please 44 from my intel machine to my PPC with no problems.  I tried Max 4.5.7 and 4.6.2 on the intel side, 4.5.7 on the PPC side.  I tried udpsend/udpreceive and otudp in various combinations.

What version of OpenSoundControl are you using?  (Send it the message "version" to find out.)  There were some substantial bug fixes in 1.9.4.

how about just using .zip? it's built in to OS X and very easy to use.

On Nov 21, 2006, at 10:23 PM, mzed wrote:

> Quote: Kasper T Toeplitz wrote on Tue, 21 November 2006 02:42

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

>>> no kasper, the problem is with stuffit - recent version cant unstuff

>>> recent posts here were advising to use version 9.

>>> i am having the same problem (only one object), still no time to

>> oh, yes sorry (i remember the thread but I am afarid i did not follow

>> it!!) - however I tried on 2 macs with 2 versions of stuffit

> We're looking into solutions to this stuffit disaster. Meanwhile, 

> I hope it works if you download the objects individually. Clicking 

> on the version number in the object's row will do it.

> || michael f. zbyszynski -- molecular gastronimist

> || mzed@cnmat.berkeley.edu -- +1.510.643.9990x314

>
> Quote: Kasper T Toeplitz wrote on Tue, 21 November 2006 02:42
> ----------------------------------------------------
>>> no kasper, the problem is with stuffit - recent version cant unstuff
>>> it sucessfully.
>>> recent posts here were advising to use version 9.
>>> i am having the same problem (only one object), still no time to
>>> look for a solution/downgrade
>>>
>>
>>
>> oh, yes sorry (i remember the thread but I am afarid i did not follow
>> it!!) - however I tried on 2 macs with 2 versions of stuffit
>>
>
>
> We're looking into solutions to this stuffit disaster.  Meanwhile,  
> I hope it works if you download the objects individually.  Clicking  
> on the version number in the object's row will do it.
>
> mz
>
>
> --
> || michael f. zbyszynski -- molecular gastronimist
> || mzed@cnmat.berkeley.edu -- +1.510.643.9990x314
> || http://www.cnmat.berkeley.edu/
> || http://www.piratelemur.com/
>
>
>


On 22-Nov-2006, at 11:08, evan.raskob [lists] wrote:

> how about just using .zip? it's built in to OS X and very easy to use.

The problem with .zip is that it looks cross-platform, sounds cross- 

platform, but if you use Finder's built-in zip it's not really cross- 

platform. (As mentioned earlier in this thread)

There are many good reasons to go the extra mile and use .DMG for 

transferring Mac file hierarchies. But a lot of people won't make the 

The problem with .zip is that it looks cross-platform, sounds cross- 
platform, but if you use Finder's built-in zip it's not really cross- 
platform. (As mentioned earlier in this thread)

There are many good reasons to go the extra mile and use .DMG for  
transferring Mac file hierarchies. But a lot of people won't make the  
effort. In that case, sure, use zip.

On 20-Nov-2006, at 12:05, Kasper T Toeplitz wrote:

otudp is longer supported as Universal Binary and CNMAT recommends 

that we update our patches to use the C74 objects. The new objects 

are bundled with Max 4.6. But this is on the assumption that everyone 

> but I am sure it's the OpenSoundControl which causes problem:

OK, I only looked at this briefly and my gut feeling was that since 

OpenSoundControl.help (inside the .help file) said it was still 

only went until 2005... I guessed nothing had changed with the object 

The object does seem to work in the .help file.

My own problems with OSC have been put on a back burner. I don't know 

On 20-Nov-2006, at 12:05, Kasper T Toeplitz wrote:
> "orphaned cousins"??

otudp is longer supported as Universal Binary and CNMAT recommends  
that we update our patches to use the C74 objects. The new objects  
are bundled with Max 4.6. But this is on the assumption that everyone  
has bought shiny new Intel Macs.

OK, I only looked at this briefly and my gut feeling was that since  
OpenSoundControl.help (inside the .help file) said it was still  
version 0.8 from Aug 2004 and the copyright notice in the Max window  
only went until 2005... I guessed nothing had changed with the object  
and the problem must be elsewhere.

OSC & mac OSX.4.7