GMU:Tutorials/Networking/Controlling MAX MSP with IanniX - Revision history

LeifWEi: /* Introduction */

2016-07-27T14:33:12Z

Introduction

← Older revision		Revision as of 14:33, 27 July 2016
Line 1:		Line 1:
	== ''Introduction'' ==		== ''Introduction'' ==

	So you want to ~~work with~~ IANNIX ~~and~~ aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered.		So you want to do a workflow from IANNIX to Max MSP aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered.

	== '''Preparing IANNIX''' ==		== '''Preparing IANNIX''' ==

LeifWEi: /* Working with data in Max */

2016-07-27T14:31:56Z

Working with data in Max

← Older revision		Revision as of 14:31, 27 July 2016
Line 66:		Line 66:

	[[File:leif_bild5.png\|thumb\|200px\|left\|IANNIX OSC-String]]		[[File:leif_bild5.png\|thumb\|200px\|left\|IANNIX OSC-String]]







	So this is what Max is receiving. We've just looked at a trigger, so let's say we want to continue working with data from the triggers exclusively. We can do that with a command in Max:		So this is what Max is receiving. We've just looked at a trigger, so let's say we want to continue working with data from the triggers exclusively. We can do that with a command in Max:
Line 72:		Line 78:
	To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with		To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with
	'''unpack 0 0. 0. 0. 0. 0. 0.'''		'''unpack 0 0. 0. 0. 0. 0. 0.'''
	Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!''' (Tutorial by Leif Weitzel)		Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!'''
			(Tutorial by Leif Weitzel)
	[[File:leif_bild6.png\|thumb\|200px\|left\|Max Patch to print out individual parts of an OSC-string]]		[[File:leif_bild6.png\|thumb\|200px\|left\|Max Patch to print out individual parts of an OSC-string]]
	[[File:leif_bild7.png\|thumb\|200px\|left\|Checking back with the console]]		[[File:leif_bild7.png\|thumb\|200px\|left\|Checking back with the console]]

LeifWEi: /* Working with data in Max */

2016-07-27T14:31:25Z

Working with data in Max

← Older revision		Revision as of 14:31, 27 July 2016
Line 72:		Line 72:
	To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with		To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with
	'''unpack 0 0. 0. 0. 0. 0. 0.'''		'''unpack 0 0. 0. 0. 0. 0. 0.'''
	Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!'''		Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!''' (Tutorial by Leif Weitzel)
	[[File:leif_bild6.png\|thumb\|200px\|left\|Max Patch to print out individual parts of an OSC-string]]		[[File:leif_bild6.png\|thumb\|200px\|left\|Max Patch to print out individual parts of an OSC-string]]
	[[File:leif_bild7.png\|thumb\|200px\|left\|Checking back with the console]]		[[File:leif_bild7.png\|thumb\|200px\|left\|Checking back with the console]]

LeifWEi: /* Working with data in Max */

2016-07-27T14:27:40Z

Working with data in Max

← Older revision		Revision as of 14:27, 27 July 2016
Line 48:		Line 48:

	[[File:leif_bild4.png\|thumb\|200px\|left\|Checking out if stuff works]]		[[File:leif_bild4.png\|thumb\|200px\|left\|Checking out if stuff works]]













	== '''Working with data in Max''' ==		== '''Working with data in Max''' ==

LeifWEi: /* Receiving data in Max */

2016-07-27T14:26:56Z

Receiving data in Max

← Older revision		Revision as of 14:26, 27 July 2016
Line 41:		Line 41:
	== '''Receiving data in Max''' ==		== '''Receiving data in Max''' ==

	For receiving data Max you'll want to use the '''udpreceive''' function and the host you want to listen to. In our case this comes to[[File:leif_bild3.png]]		For receiving data Max you'll want to use the '''udpreceive''' function and the host you want to listen to. In our case this comes to

			[[File:leif_bild3.png]]

	You may want to check if you got everything communicating by using a print command and checking the console, where lots of words and numbers should appear by now (if IANNIX is still playing of course). If nothing appears, check your Hosts or IP-Adresses. If you work on different computers, the udpreceive also needs the sender's IP-Adress, so you should write something like: '''udpreceive [IP-Adress]:[Host]'''		You may want to check if you got everything communicating by using a print command and checking the console, where lots of words and numbers should appear by now (if IANNIX is still playing of course). If nothing appears, check your Hosts or IP-Adresses. If you work on different computers, the udpreceive also needs the sender's IP-Adress, so you should write something like: '''udpreceive [IP-Adress]:[Host]'''

	[[File:leif_bild4.png\|thumb\|200px\|left\|Checking if stuff works]]		[[File:leif_bild4.png\|thumb\|200px\|left\|Checking out if stuff works]]


















	== '''Working with data in Max''' ==		== '''Working with data in Max''' ==

LeifWEi: /* Preparing IANNIX */

2016-07-27T14:25:43Z

Preparing IANNIX

← Older revision		Revision as of 14:25, 27 July 2016
Line 28:		Line 28:

	[[File:leif_bild2.png\|thumb\|200px\|left\|IANNIX OSC Configuration]]		[[File:leif_bild2.png\|thumb\|200px\|left\|IANNIX OSC Configuration]]

LeifWEi: Created page with "== ''Introduction'' == So you want to work with IANNIX and aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered. == '''Preparing IANNIX'..."

2016-07-27T14:22:20Z

Created page with "== ''Introduction'' == So you want to work with IANNIX and aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered. == '''Preparing IANNIX'..."

New page

== ''Introduction'' ==

So you want to work with IANNIX and aren't sure how to receive, unpack and use the IANNIX OSC data in Max? We've got you covered.

== '''Preparing IANNIX''' ==

IANNIX makes it crazy easy to send nice OSC-Data. For this tutorial I created a simple Rosette (Files Tab -- Examples -- Rosette -- Quantity 5)
You can use something else, I don't care. For the sake of this tutorial just be sure it has cursors and triggers.

[[File:leif_bild1.png|thumb|200px|left|Simplified Rosette in IANNIX]]

IANNIX automatically sends OSC-Data locally through port 57120, but better check back with this (Config Tab -- Network -- Enable OSC)

[[File:leif_bild2.png|thumb|200px|left|IANNIX OSC Configuration]]

Press Play and boom, stuff is being sent. Well done so far!

== '''Receiving data in Max''' ==

For receiving data Max you'll want to use the '''udpreceive''' function and the host you want to listen to. In our case this comes to[[File:leif_bild3.png]]

You may want to check if you got everything communicating by using a print command and checking the console, where lots of words and numbers should appear by now (if IANNIX is still playing of course). If nothing appears, check your Hosts or IP-Adresses. If you work on different computers, the udpreceive also needs the sender's IP-Adress, so you should write something like: '''udpreceive [IP-Adress]:[Host]'''

[[File:leif_bild4.png|thumb|200px|left|Checking if stuff works]]

== '''Working with data in Max''' ==

So let's look at the data received and check out what it means. Back in IANNIX you can hover over any cursor or trigger to see how it's OSC-String is build:

[[File:leif_bild5.png|thumb|200px|left|IANNIX OSC-String]]

So this is what Max is receiving. We've just looked at a trigger, so let's say we want to continue working with data from the triggers exclusively. We can do that with a command in Max:
'''route /trigger'''
This only lets OSC-messages from the triggers through the grid.
To make sense of the string and use only the data we want, we'll use the unpack command, which unpacks (duh) the OSC string, followed by the string's logical structure. In our case this leaves us with
'''unpack 0 0. 0. 0. 0. 0. 0.'''
Now we can do with any of the unpacked information whatever we like (I suggest you do some nice art with it), for this tutorial we'll be fine with just printing them to the console piece by piece, and you're done! '''Nice work!'''
[[File:leif_bild6.png|thumb|200px|left|Max Patch to print out individual parts of an OSC-string]]
[[File:leif_bild7.png|thumb|200px|left|Checking back with the console]]