MSP Polyphony Tutorial 1: Turning Signals On and Off - Revision history

Gtaylor@rtqe.net at 23:02, 5 July 2012

2012-07-05T23:02:03Z

Gtaylor@rtqe.net at 21:51, 5 July 2012

2012-07-05T21:51:06Z

Gtaylor@rtqe.net: /* Turning off part of a signal network: poly~ */

2012-07-05T21:45:03Z

‎Turning off part of a signal network: poly~

Gtaylor@rtqe.net at 21:43, 5 July 2012

2012-07-05T21:43:35Z

Gtaylor@rtqe.net: /* Summary */

2012-07-05T21:01:48Z

‎Summary

Gtaylor@rtqe.net: /* Turning off part of a signal network: pcontrol */

2012-07-05T20:55:03Z

‎Turning off part of a signal network: pcontrol

Gtaylor@rtqe.net: /* Turning audio on and off selectively */

2012-07-05T20:52:36Z

‎Turning audio on and off selectively

Gtaylor@rtqe.net: /* Using the Mixer Engine to control audio */

2012-07-05T20:51:40Z

‎Using the Mixer Engine to control audio

Gtaylor@rtqe.net at 19:52, 5 July 2012

2012-07-05T19:52:27Z

Gtaylor@rtqe.net at 19:51, 5 July 2012

2012-07-05T19:51:25Z

Show changes

← Older revision		Revision as of 23:02, 5 July 2012
Line 1:		Line 1:
−	Click here to open the tutorial ~~patch~~: [[Media:01hTurningSignalsOnAndOff.zip]]	+	Click here to open the tutorial patches: [[Media:01hTurningSignalsOnAndOff.zip]]

	===Turning audio on and off selectively===		===Turning audio on and off selectively===

← Older revision		Revision as of 21:51, 5 July 2012
Line 1:		Line 1:
−	~~<openpatchlink>Open~~ the tutorial~~</openpatchlink>~~.	+	Click here to open the tutorial patch: [[Media:01hTurningSignalsOnAndOff.zip]]

	===Turning audio on and off selectively===		===Turning audio on and off selectively===

@@ Line 69: / Line 69: @@
 The {{maxword|name=poly~}} object allows us to do just that.
-The {{maxword|name=poly~}} object is very powerful - to describe it simply, it lets us create and manage multiple copies of the same MSP subpatch within one object, and is very useful for creating polyphonic synths. We'll describe its use for that purpose in greater detail in a <link type="tutorial" module="msp" name="mspchapter21">later tutorial</link>. For now, we'll show you how to use it to conserve CPU usage.
+The {{maxword|name=poly~}} object is very powerful - to describe it simply, it lets us create and manage multiple copies of the same MSP subpatch within one object, and is very useful for creating polyphonic synths. We'll describe its use for that purpose in greater detail in MSP Polyphony Tutorial 2. For now, we'll show you how to use it to conserve CPU usage.
 The tutorial patch contains an example of the {{maxword|name=poly~}} object used to enable and disable signal processing in a patch.

← Older revision		Revision as of 21:43, 5 July 2012
Line 116:		Line 116:
	{{maxword\|name=poly~}} - Manage polyphony/DSP for patchers		{{maxword\|name=poly~}} - Manage polyphony/DSP for patchers

−	{{maxword\|name=selector~}} - Assign one of several inputs to an outlet	+	{{maxword\|name=selector~}} - Assign one of several inputs to an outlet
		+
		+	[[Category:Teaching Material]]

@@ Line 103: / Line 103: @@
 ===Summary===
-The <code>startwindow</code> message to {{maxword|name=dac~}} (or {{maxword|name=adc~}}) starts audio processing in the Patcher window that contains the {{maxword|name=dac~}}, and in any of that window's subpatches, but turns audio off in all other patches. The {{maxword|name=mute~}} object, connected to an inlet of a subpatch, can be used to disable all MSP objects in that subpatch. An <code>enable 0</code> message to a {{maxword|name=pcontrol}} object connected to an inlet of a subpatch can also be used to disable all MSP objects in that subpatch. (This disables all MIDI objects in the subpatch, too.) The {{maxword|name=pass~}} object silences the output of a subpatcher when it is muted.
+The <code>startwindow</code> message to {{maxword|name=ezdac~}} (or {{maxword|name=ezadc~}}) starts audio processing in the Patcher window that contains the {{maxword|name=dac~}}, and in any of that window's subpatches, but turns audio off in all other patches. An <code>enable 0</code> message to a {{maxword|name=pcontrol}} object connected to an inlet of a subpatch can be used to disable all MSP objects in that subpatch. (This disables all MIDI objects in the subpatch, too.)
-You can use a {{maxword|name=selector~}} object to choose one of several signals to be passed on out the outlet, or to close off the flow of all the signals it receives. All MSP objects that are connected in a signal flow between the outlet of a {{maxword|name=begin~}} object and an inlet of a {{maxword|name=selector~}} object (or a {{maxword|name=gate~}} object) get completely disconnected from the signal network when that inlet is closed.
+You can use {{maxword|name=selector~}} object to choose one of several signals to be passed on out the outlet, or to close off the flow of all the signals it receives.
-Any of these methods is an effective way to play selectively a subset of all the MSP objects in a
+You can use the {{maxword|name=poly~}} object in conjunction sending the <code>mute 0 0/1</code> message to a {{maxword|name=thispatcher}} object in the
-given signal network (or to select one of several different networks). You can have many signal
+MSP patcher hosted by the {{maxword|name=poly~}} object as a way of enabling or disabling all MSP objects in that subpatch. (This disables all MIDI objects in the subpatch, too.)
-networks loaded, but only enable one at a time; in this way, you can switch quickly from one
-sound to another, but the computer only does processing that affects the sound you hear.
-You can use the {{maxword|name=poly~}} object to disable the processing for the parts of the signal network that are not needed at a given time.
+Any of these methods is an effective way to play selectively a subset of all the MSP objects in a given signal network (or to select one of several different networks). You can have many signal networks loaded, but only enable one at a time; in this way, you can switch quickly from one sound to another, but the computer only does processing that affects the sound you hear.
 ===See Also===

← Older revision		Revision as of 20:55, 5 July 2012
Line 54:		Line 54:

	If you want to enable or disable signal processing in a {{maxword\|name=patcher}} or abstraction, you can use the {{maxword\|name=pcontrol}} object. The <code>enable</code> message to {{maxword\|name=pcontrol}} turns off ''all'' activity within a subpatcher - both MSP signals and Max scheduling.		If you want to enable or disable signal processing in a {{maxword\|name=patcher}} or abstraction, you can use the {{maxword\|name=pcontrol}} object. The <code>enable</code> message to {{maxword\|name=pcontrol}} turns off ''all'' activity within a subpatcher - both MSP signals and Max scheduling.
		+
		+	[[Image:Enable-pcontrol.png\|border]]

	----		----

@@ Line 5: / Line 5: @@
 There are two elementary ways of turning audio processing on and off in an MSP patcher:
-# Send a <code>start</code> or <code>stop</code> message to a {{maxword|name=ezdac~}}, {{maxword|name=ezadc~}}, {{maxword|name=dac~}}, or {{maxword|name=adc~}} object.
+* Send a <code>start</code> or <code>stop</code> message to a {{maxword|name=ezdac~}}, {{maxword|name=ezadc~}}, {{maxword|name=dac~}}, or {{maxword|name=adc~}} object.
-# Click on a {{maxword|name=ezdac~}} or {{maxword|name=ezadc~}} object.
+* Click on a {{maxword|name=ezdac~}} or {{maxword|name=ezadc~}} object.
 For the first tutorial that introduces the {{maxword|name=poly~}} object and the idea of polyphony in general, we are going to take a step back and think more broadly about allocating resources in a signal processing patch - when you think about it, that is what polyphony is ''about,'' in a general way.
@@ Line 13: / Line 13: @@
 There are two other ways of turning audio processing on and off in an MSP patcher we have not yet mentioned:
-# Send an <code>int</code> to a {{maxword|name=dac~}}, {{maxword|name=adc~}}, {{maxword|name=ezdac~}}, or {{maxword|name=ezadc~}} object. <code>0</code> is the same as <code>stop</code>, and a non-zero number is the same as <code>start</code>.
+* Send an <code>int</code> to a {{maxword|name=dac~}}, {{maxword|name=adc~}}, {{maxword|name=ezdac~}}, or {{maxword|name=ezadc~}} object. <code>0</code> is the same as <code>stop</code>, and a non-zero number is the same as <code>start</code>.
-# Double-click on a {{maxword|name=dac~}} or {{maxword|name=adc~}} object to open the Audio Status window, then use its Audio on/ off pop-up menu. You can also choose <b>Audio Status...</b> from the Options menu to open the Audio Status window.
+* Double-click on a {{maxword|name=dac~}} or {{maxword|name=adc~}} object to open the Audio Status window, then use its Audio on/ off pop-up menu. You can also choose <b>Audio Status...</b> from the Options menu to open the Audio Status window.
 Any of those methods of starting MSP will turn the audio on in all open Patcher windows and their subpatches. There are also a several ways to turn audio processing on and off in a single Patcher.

@@ Line 31: / Line 31: @@
 To display the Mixer engine control panel for your patcher, click on the Mixer button in the patcher toolbar.
-[[Image:Mixerpanel.png|border]]
+[[Image:Mixer-engine.png|border]]
 You can click and drag on the volume knob to set the output volume for the patcher window, and mute or solo the audio output using the M (Mute) or S (Solo) buttons.

← Older revision		Revision as of 19:52, 5 July 2012
Line 117:		Line 117:

	{{maxword\|name=selector~}} - Assign one of several inputs to an outlet		{{maxword\|name=selector~}} - Assign one of several inputs to an outlet
−	~~</seealsolist>~~
−
−	~~</chapter>~~