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

Ben: /* Grabbing the Bone Vector Coordinates */

2016-10-22T18:50:01Z

Grabbing the Bone Vector Coordinates

← Older revision		Revision as of 18:50, 22 October 2016
Line 44:		Line 44:
	With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.		With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.

	[[File:~~img05~~.png\|400px]]		[[File:img08.png\|400px]]

	== Using the Data Stream from The Captury ==		== Using the Data Stream from The Captury ==

2016-10-22T18:47:06Z

UDP

← Older revision		Revision as of 18:47, 22 October 2016
Line 11:		Line 11:
	UDP (User Datagram Protocol) is an internet protocol which provides communication which no handshaking. It also let you define which port on the destination IP you want to address. In our case it is used to transmit messages in OSC format.		UDP (User Datagram Protocol) is an internet protocol which provides communication which no handshaking. It also let you define which port on the destination IP you want to address. In our case it is used to transmit messages in OSC format.

	In Max/Msp you set up an udpsend object. It need two parameters: IP address and port number (e.g.: "141.54.0.1." or "kosmos.uni-weimar.de" and "~~13000~~").		In Max/Msp you set up an udpsend object. It need two parameters: IP address and port number (e.g.: "141.54.0.1." or "kosmos.uni-weimar.de" and "1065").

	[[File:img01.png\|400px]]		[[File:img01.png\|400px]]

2016-10-22T18:44:32Z

Overview

← Older revision		Revision as of 18:44, 22 October 2016
Line 3:		Line 3:
	== Overview ==		== Overview ==

	The following tutorial covers the process of connecting Max/Msp (short: Max) with "the Captury" tracking software and use the ~~outcoming~~ information.		The following tutorial covers the process of connecting Max/Msp (short: Max) with "the Captury" tracking software and explains how use the out coming information.

	[[File:overview.png\|400px]]		[[File:overview.png\|400px]]

2016-10-22T18:44:12Z

Overview

← Older revision		Revision as of 18:44, 22 October 2016
Line 2:		Line 2:

	== Overview ==		== Overview ==

			The following tutorial covers the process of connecting Max/Msp (short: Max) with "the Captury" tracking software and use the outcoming information.

	[[File:overview.png\|400px]]		[[File:overview.png\|400px]]

2016-10-22T18:36:39Z

Using the Data Stream from The Captury

← Older revision		Revision as of 18:36, 22 October 2016
Line 45:		Line 45:

	== Using the Data Stream from The Captury ==		== Using the Data Stream from The Captury ==

			In the Max domain - instead of patching cords - we can send and receive data as well. To do this we simply write [send] or [receive] and a unique name, which serves as a kind of address: in our case it is [s x-coord] (s as the short form for send is also possible).

			Now we can receive the values that have been sent and use them for very own purposes. In my example I display the data first - to have a kind of overview - to see which direction the information is heading to or where it is coming from.

			[[File:img06.png\|400px]]

			Happy patching!

			For questions please contact me: benjamin[.] vossler[at] uni-weimar[.] de

2016-10-22T18:28:25Z

Controlling Max-Msp with The Captury

← Older revision		Revision as of 18:28, 22 October 2016
Line 42:		Line 42:
	With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.		With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.

	[[img05.png\|400px]]		[[File:img05.png\|400px]]

	== Using the Data Stream from The Captury ==		== Using the Data Stream from The Captury ==

2016-10-22T18:27:59Z

Grabbing the Bone Vector Coordinates

← Older revision		Revision as of 18:27, 22 October 2016
Line 41:		Line 41:
	After [udpreceive] we can route the out coming array of information by using the OSC-Syntax again.		After [udpreceive] we can route the out coming array of information by using the OSC-Syntax again.
	With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.		With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.

			[[img05.png\|400px]]

	== Using the Data Stream from The Captury ==		== Using the Data Stream from The Captury ==

2016-10-22T18:27:30Z

Grabbing the Bone Vector Coordinates

← Older revision		Revision as of 18:27, 22 October 2016
Line 37:		Line 37:

	== Grabbing the Bone Vector Coordinates ==		== Grabbing the Bone Vector Coordinates ==

			The [udpreceive] object work the other way around. It can receive messages coming from a specific IP and port.
			After [udpreceive] we can route the out coming array of information by using the OSC-Syntax again.
			With the [route] object we can exactly determine what branch of the string we want to access, in this case we write "/route/John-Doe/blender/Root/vector" to get exactly what we asked for. Afterwards we unpack the containing floats, which represent the x, y and z value of our subscripted bone.

	== Using the Data Stream from The Captury ==		== Using the Data Stream from The Captury ==

2016-10-22T18:18:08Z

Subscribe to any Skeleton

← Older revision		Revision as of 18:18, 22 October 2016
Line 33:		Line 33:

	Since subscriptions will expire after a while, we call this message every 10 seconds. Therefore we use the Max own metronome object called [metro] which will repeat to put out bangs and so trigger the message. The toggle [X] will turn ON the metro.		Since subscriptions will expire after a while, we call this message every 10 seconds. Therefore we use the Max own metronome object called [metro] which will repeat to put out bangs and so trigger the message. The toggle [X] will turn ON the metro.

			[[File:img03.png\|400px]]

	== Grabbing the Bone Vector Coordinates ==		== Grabbing the Bone Vector Coordinates ==

	== Using the Data Stream from The Captury ==		== Using the Data Stream from The Captury ==

2016-10-22T18:17:18Z

Controlling Max-Msp with The Captury

← Older revision		Revision as of 18:17, 22 October 2016
Line 1:		Line 1:
	= Controlling Max-Msp with The Captury =		= Controlling Max-Msp with The Captury =

			== Overview ==

			[[File:overview.png\|400px]]

	== UDP ==		== UDP ==