OSC - what is it (in max)?
hi
just to understand it better:
I (most of the time !) know how to use OSC in Max - or with computers (?)
_meaning I either do a network between 2 or more (max-running)
computers or communicate between, say, max & reaktor on the same
machine
for doing so I use (or used) objects such as udp, OSCroute, udpsend,
net.maxhole....
but are those all OSC??
_with udpsend for exemple I can communicate with Reaktor (which
understands OSC) so I assume it is OSC
_a network between 2 max patches on 2 computers, using maxhole - is it OSC??
i understand I can pass any (??) message (text etc) by OSC.... but
is any max-max connection OSC??
if not what would be the difference (in max) between an OSC
communication and a non-OSC one?
many thanks
kasper
--
Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com
On Fri, Feb 29, 2008 at 11:33 AM, Kasper T Toeplitz
wrote:
> hi
>
> just to understand it better:
>
> I (most of the time !) know how to use OSC in Max - or with computers (?)
>
> _meaning I either do a network between 2 or more (max-running)
> computers or communicate between, say, max & reaktor on the same
> machine
> for doing so I use (or used) objects such as udp, OSCroute, udpsend,
> net.maxhole....
>
> but are those all OSC??
>
Hi Kasper,
You're mixing things up. OSC is a communication protocol. UDP, TCP/IP, USB
etc are transport protocols. They are not linked or restricted to one
another.
Thijs
>
>You're mixing things up.
this I knew ! :-)
>OSC is a communication protocol. UDP, TCP/IP, USB etc are transport
>protocols. They are not linked or restricted to one another.
>
>http://en.wikipedia.org/wiki/OpenSound_Control
yeah I had a look at wikipedia, and I understand that udp etc are protocols...
my question was maybe more specific to max:
_before net.maxhole existed I was using OSC (at least I think I was -
I was using the cnmat tools and the "osc primer" help patch) to send
data between 2 or more computers
now I am using net.maxhole, in the same situation (sometimes the same
patches) to acheive the same task (and send similar data) - is it
still OSC??
if not what would be the difference between the 2? or what (in max
world) would make me use OSC vs messages send by maxhole???
hope I am clearer...
thanks
kasper
--
Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com
On Fri, Feb 29, 2008 at 12:11 PM, Kasper T Toeplitz
wrote:
>
> yeah I had a look at wikipedia, and I understand that udp etc are
> protocols...
>
> my question was maybe more specific to max:
>
your question has less to do with max than you think.
>
> _before net.maxhole existed I was using OSC (at least I think I was - I
> was using the cnmat tools and the "osc primer" help patch) to send data
> between 2 or more computers
>
> now I am using net.maxhole, in the same situation (sometimes the same
> patches) to acheive the same task (and send similar data) - is it still
> OSC??
>
>
> if not what would be the difference between the 2? or what (in max world)
> would make me use OSC vs messages send by maxhole???
>
net.maxhole is just an easy way to send data to multiple computers over (I
think) TCP/IP. It takes a max message, formats it into a data packet thing
and sends it over the network. This messages could be an OSC "formatted" max
list message. A max message formatted according to OSC layout with the
"/name/space/thing value" If you were using udpsend/udpreceive instead of
maxhole you would still be doing the same thing. Sending an osc formatted
message, but using a different transport protocol.
Whether you're doing something with OSC has nothing to do with the way you
transport the data from one computer to the other. OSC doesn't dictate how
something is send / transported, it specifies how messages should be
formatted / communicated. Thats why OSC is a communication protocol, and
net.maxhole is using a transport protocol.
If you were using only CNMAT objects before, they were probably using UDP in
one of the objects to transfer the OSC messages from one computer to the
other.
If I remember correctly, not all OSC features are supported by current max
OSC objects. Timestamping for example. This is probably because timestamping
would involve something more complicated than max list parsing/formatting,
with the /foo/sub/name/space thing.
I hope I'm being clear now;-)
Thijs
We can communicate in English by speaking to each other, sending emails, sending letters, sending sms messages, speaking on the phone, or encode word by word into morse code...
In this example English is the communication protocol. We get the data to each other using a transport protocol.
But maybe English is not convenient: We could choose to communicate in Russian, over the phone. Or in French, writing letters. We could also speak OSC, over UDP. Or OSC over email, or even OSC encoded in morse using smoke signals...
If you'd really want to you could probably write an application or vst that reads OSC messages from a text file on your hard drive stored there using a [coll] in Max. Or print the data from the coll and fax it to me so I could scan it to eventually feed it into my Reaktor patch here.. It would still be OSC. Just OSC using a very high latency transport protocol.
regards,
kjg
maybe it can help (or maybe you already know it):
https://cycling74.com/story/2005/5/2/134847/8926
https://cycling74.com/story/2006/10/23/104657/91
cheers
f./