Actions Tips - Revision history

Edwards: /* Example Library */

2025-09-09T21:17:37Z

Example Library

← Older revision		Revision as of 07:17, 10 September 2025
Line 86:		Line 86:
	== Example Library ==		== Example Library ==

	* '''Repeating Actions with a Button and Dial''' - [[Media:EXAMPLE Repeating Widget.zip\|~~this~~ project]] demonstrates one way to set up repeating sequences of actions using a button and a stepped dial. In this example, a button widget triggers a series of actions to play clips in a particular order. There is also a dial that determines whether the button is retriggered when the actions have been completed.		* '''Repeating Actions with a Button and Dial.''' [[Media:EXAMPLE Repeating Widget.zip\|This project]] demonstrates one way to set up repeating sequences of actions using a button and a stepped dial. In this example, a button widget triggers a series of actions to play clips in a particular order. There is also a dial that determines whether the button is retriggered when the actions have been completed.
	* '''Dial Sequencer'''. [[:File:EXAMPLE Dial Sequencer iPad 1.1.lpproj.zip\|~~this~~ project]] demonstrates two methods of sequencing clips via actions and a stepped dial. One method uses a trigger to advance the clip sequence and the other auto-advances the sequence.		* '''Dial Sequencer'''. [[:File:EXAMPLE Dial Sequencer iPad 1.1.lpproj.zip\|This project]] demonstrates two methods of sequencing clips via actions and a stepped dial. One method uses a trigger to advance the clip sequence and the other auto-advances the sequence.

	= Related Pages =		= Related Pages =
	[[Action List]]		[[Action List]]
	[https://loopypro.com/manual/#actions Loopy Pro Manual - Actions Chapter]		[https://loopypro.com/manual/#actions Loopy Pro Manual - Actions Chapter]

Edwards: /* Example Library */

2025-09-09T21:17:04Z

Example Library

← Older revision		Revision as of 07:17, 10 September 2025
Line 86:		Line 86:
	== Example Library ==		== Example Library ==

	* '''Repeating Actions with a Button and Dial''' - [[Media:EXAMPLE Repeating Widget.zip\|this project]] demonstrates one way to set up repeating sequences of actions using a button and a stepped dial.		* '''Repeating Actions with a Button and Dial''' - [[Media:EXAMPLE Repeating Widget.zip\|this project]] demonstrates one way to set up repeating sequences of actions using a button and a stepped dial. In this example, a button widget triggers a series of actions to play clips in a particular order. There is also a dial that determines whether the button is retriggered when the actions have been completed.
			* '''Dial Sequencer'''. [[:File:EXAMPLE Dial Sequencer iPad 1.1.lpproj.zip\|this project]] demonstrates two methods of sequencing clips via actions and a stepped dial. One method uses a trigger to advance the clip sequence and the other auto-advances the sequence.

	= Related Pages =		= Related Pages =
	[[Action List]]		[[Action List]]
	[https://loopypro.com/manual/#actions Loopy Pro Manual - Actions Chapter]		[https://loopypro.com/manual/#actions Loopy Pro Manual - Actions Chapter]

Edwards at 23:31, 28 July 2025

2025-07-28T23:31:06Z

← Older revision		Revision as of 09:31, 29 July 2025
Line 4:		Line 4:

	== MIDI Learn ==		== MIDI Learn ==
	When you MIDI Learn in Loopy Pro, you are creating a MIDI Binding to an action ~~which you~~ can ~~also customize~~ or add to~~. The bindings and their actions are accessed~~ by the ~~Control Settings panel~~.		When you MIDI Learn in Loopy Pro, you are creating a MIDI Binding to an action. You can edit that binding via the Control Settings panel. You can modify that options for the action or add additional actions to be performed by the binding.

	== Action Sequences ==		== Action Sequences ==
Line 65:		Line 65:

	'''Delay length'''. Use a delay of 1/8th note or more. (Loopy has a little grace period when triggering loops so that if you are a little late triggering a loop it doesn't wait for another cycle to complete -- so the delay has to be long enough that Loopy doesn't think you meant to trigger now). When setting the action timing, make sure that it is set to a delay of 1/8th note and not quantized to 1/8th note.		'''Delay length'''. Use a delay of 1/8th note or more. (Loopy has a little grace period when triggering loops so that if you are a little late triggering a loop it doesn't wait for another cycle to complete -- so the delay has to be long enough that Loopy doesn't think you meant to trigger now). When setting the action timing, make sure that it is set to a delay of 1/8th note and not quantized to 1/8th note.

			==== Performing actions after another loop has finished a cycle ====
			If you want to an action or actions to be performed after some loop has finished its cycle, you can use the play stop action with stop quantization set to loop followed by the actions you want to perform. If you have play the loop as part of the series of actions, it will play uninterrupted since it will start again as soon as it stopped.

			Let's say, you have a loops ''drum loop'' and ''lead loop'' and you want the ''replace'' action to be performed on the ''lead loop'' after the next cycle of ''drum loop''. Use this action sequence:

			* Stop ''drum loop'' (stop quantization loop)
			* [after last] Play ''drum loop'' (probably with quantization set to 1 bar to make sure that it is quantized to the clock)
			* [with last] Replace ''lead'' loop

			The after last/with last timings are set by tapping on the dot to the left of the action in the action editor.

	== Helpful Hints ==		== Helpful Hints ==

Edwards: improve action timing explanations and reorganize page slightly

2025-04-12T18:07:50Z

improve action timing explanations and reorganize page slightly

← Older revision		Revision as of 04:07, 13 April 2025
Line 11:		Line 11:
	== Action Timing ==		== Action Timing ==
	To the left of each action is a white circle. Tapping on the circle pops up a panel to set options for when the action is performed.		To the left of each action is a white circle. Tapping on the circle pops up a panel to set options for when the action is performed.
			[[File:loopy_pro_action_circle.jpeg\|600px]]


	~~[[File:loopy_pro_action_circle.jpeg\|600px]]~~


Line 27:		Line 26:

	If the timing is set to Quantization, the action is performed at the next time that the clocks aligns with that quantization setting. If the timing is set to Delay, the action happens after Delay of the specified time and is independent of the clock's position. If the clock is not moving, all quantizations fire immediately!		If the timing is set to Quantization, the action is performed at the next time that the clocks aligns with that quantization setting. If the timing is set to Delay, the action happens after Delay of the specified time and is independent of the clock's position. If the clock is not moving, all quantizations fire immediately!

			=== Timing Icons ===
			[[File:loopy_pro_action_icons.jpeg\|600px]]

			The circle that appears next to actions indicates the timing/trigger settings.
			* An empty circle indicates "With Last"
			* A circle with a clock in it indicates "With Last" with delay or quantization
			* A circle with a number indicates a "Next Trigger" sequence with the number indicating the trigger number.
			* A circle with an arrow indicates "After Last"

	=== Action Timing and Tempo ===		=== Action Timing and Tempo ===
	Timing ~~(as of 1.~~1.~~17)~~ is always related to musical time/tempo. When the tempo hasn't yet been defined, events with delays or quantization execute immediately.		Timing in Loopy Pro 1.x is always related to musical time/tempo. When the tempo hasn't yet been defined, events with delays or quantization execute immediately. Starting with Loopy Pro 2.0, timing can be set in absolute time (seconds.milliseconds)

	=== After Last/With Last/Next Trigger ===		=== After Last/With Last/Next Trigger ===
Line 38:		Line 46:
	In addition to the choice of Quantization and Delay, the following options appear: After Last, With Last, Next Trigger. The specified quantization or delay is applied. Most actions take next to no time to execute. Stop clip actions are somewhat different as discussed below.		In addition to the choice of Quantization and Delay, the following options appear: After Last, With Last, Next Trigger. The specified quantization or delay is applied. Most actions take next to no time to execute. Stop clip actions are somewhat different as discussed below.

	'''After Last'''. The action is performed after the previous action is performed (with the specified quantization or delay).		'''After Last'''. The action is performed after the previous action is performed (with the specified quantization or delay). Many actions take next to no time to execute (fractions of a millisecond. Some actions, such as play, stop, solo or actions with a specified ramp time, are not considered to have executed until they are "done". What done is depends on the action. See <u>When is After</u> below.

	'''With Last'''. The action is performed simultaneous with the previous action (with the specified quantization or delay). Use this when you need actions to fire truly simultaneously or for the timing to be precisely based on the previous actions execution time. In some contexts After Last and With Last will seem to be the same, but in some cases it can make a difference. Especially if any action changes something that a subsequent action relies on.		'''With Last'''. The action is performed simultaneous with the previous action (with the specified quantization or delay). Use this when you need actions to fire truly simultaneously or for the timing to be precisely based on the previous actions execution time. In some contexts After Last and With Last will seem to be the same, but in some cases it can make a difference. Especially if any action changes something that a subsequent action relies on.
Line 44:		Line 52:
	'''Next Trigger'''. This action is fired the next time that the action sequence is triggered. For example, you might have a button that the first time it is pressed mutes the bass instrument and records clip 1 and on the second press unmutes the guitar, mutes the bass and records clip 2.		'''Next Trigger'''. This action is fired the next time that the action sequence is triggered. For example, you might have a button that the first time it is pressed mutes the bass instrument and records clip 1 and on the second press unmutes the guitar, mutes the bass and records clip 2.

	=== ~~Stop Clip Timing~~ ===		==== When is After? ====
	~~Most~~ actions execute ~~immediately~~, stop ~~clip is different in~~ a ~~very useful way. The Stop Clip and Stop Recording actions~~ are not considered ~~complete~~ until the ~~stopped clip is stopped~~. ~~This is very useful if you want~~ to ~~sequence clip playback. Let~~'~~s say that you want to have a button or MIDI binding that plays or solos clip 1 for one cycle and then plays or solos clip 2 after clip 1~~ is ~~finished playing~~. ~~The easiest way to accomplish it~~ is ~~to have this action sequence:~~		Many actions take next to no time to execute (fractions of a millisecond. Some actions, such as play, stop, solo or actions with a specified ramp time, are not considered to have executed until they are "done". What done is depends on the action. Loopy Pro tries to be smart about what ''done'' is depending on the context. Here is a list of common actions that may not be ''done'' immediately:
	* Play Clip 1
	* Stop Clip 1 set to trigger after last with a slight delay - with stop quantization set to loop
	* Play Clip 2 - with play quantization set to 1 bar (if the clips are a ~~precise number~~ of ~~bars long) or none.~~

	~~The slight delay~~ is ~~needed for~~ the ~~stop~~ action or clip ~~1 would stop~~ immediately ~~because it~~ is ~~already at~~ the ~~loop boundary~~.		* ''Stop'' - the action is done when the clip or clips have stopped.
			* ''Play/Solo'' - the action is done when the targeted clip or clips starts playing. If there is a count-in before the clip starts playing, ''done'' is when the clip actually starts playing. If a clip is already clipping, play is ''done'' immediately '''UNLESS''' the play action has ''Retrigger'' turned on. If ''Retrigger'' is on, the play action is done when the retriggered count-in finishes.
			* ''Adjust actions with a ramp'' - if you have an ''Adjust'' action, such as Adjust Parameter, with ramp time, the action is ''done'' when the ramp finishes.

	~~There are other ways to~~ play/solo ~~clips in order but they require you to set the timing based on the clip length. This method will work without needing~~ to ~~know the clip lengths~~.		==== Using Delays Between Actions ====
			For actions such as play, stop, or solo actions that are quantized, it is sometimes necessary to use ''After Next'' with a delay.

	~~=== Action Timing Icons ===~~		For example, let's say your clips use ''Loop'' play quantization. If you set up an action sequence of Solo Clip 1 then (after last) Solo Clip 2, Loopy Pro would seem to go directly to soloing clip 2 without first playing clip 1. This is because as soon as clip 1 starts soloing, Loopy Pro queues clip 2 to solo. Clip 2's own quantization criterion is met, so clip 2 starts soloing. In order to prevent this behavior, the action sequence you want is Solo Clip 1 then (after last WITH DELAY) Solo Clip 2.
	~~[[File:loopy_pro_action_icons~~.~~jpeg\|600px]]~~

	~~The circle that appears next to actions indicates the timing/trigger settings~~.		'''Delay length'''. Use a delay of 1/8th note or more. (Loopy has a little grace period when triggering loops so that if you are a little late triggering a loop it doesn't wait for another cycle to complete -- so the delay has to be long enough that Loopy doesn't think you meant to trigger now). When setting the action timing, make sure that it is set to a delay of 1/8th note and not quantized to 1/8th note.
	* An empty circle indicates "With Last"
	* A circle with a ~~clock in it indicates "With Last" with~~ delay or ~~quantization~~
	* A circle with a ~~number indicates~~ a ~~"Next Trigger" sequence with~~ the ~~number indicating~~ the ~~trigger number~~.
	* A circle with an arrow indicates "After Last"

	== Helpful Hints ==		== Helpful Hints ==
Line 72:		Line 75:
	== Example Library ==		== Example Library ==

	* '''Repeating Actions with a Button and Dial''' - [[~~MEDIA~~:~~EXAMPLE_Repeating_Widget~~.zip\|this project]] demonstrates one way to set up repeating sequences of actions using a button and a stepped dial.		* '''Repeating Actions with a Button and Dial''' - [[Media:EXAMPLE Repeating Widget.zip\|this project]] demonstrates one way to set up repeating sequences of actions using a button and a stepped dial.

	= Related Pages =		= Related Pages =
	[[Action List]]		[[Action List]]
	[https://loopypro.com/manual/#actions Loopy Pro Manual - Actions Chapter]		[https://loopypro.com/manual/#actions Loopy Pro Manual - Actions Chapter]

Edwards: /* Example Library */

2025-01-05T18:06:33Z

Example Library

← Older revision		Revision as of 04:06, 6 January 2025
Line 72:		Line 72:
	== Example Library ==		== Example Library ==

	* '''Repeating Actions with a Button and Dial''' - [~~https~~:~~//wiki.loopypro.com/images/5/56/~~EXAMPLE_Repeating_Widget.zip this project] demonstrates one way to set up repeating sequences of actions using a button and a stepped dial.		* '''Repeating Actions with a Button and Dial''' - [[MEDIA:EXAMPLE_Repeating_Widget.zip\|this project]] demonstrates one way to set up repeating sequences of actions using a button and a stepped dial.

	= Related Pages =		= Related Pages =
	[[Action List]]		[[Action List]]
	[https://loopypro.com/manual/#actions Loopy Pro Manual - Actions Chapter]		[https://loopypro.com/manual/#actions Loopy Pro Manual - Actions Chapter]

Edwards at 23:23, 4 January 2025

2025-01-04T23:23:18Z

← Older revision		Revision as of 09:23, 5 January 2025
Line 3:		Line 3:
	Loopy Pro's actions can provide control over almost every aspect of Loopy Pro and can be used to create custom behavior. Actions are used by the MIDI Learn/MIDI Binding system, widgets (buttons, sliders, dials, etc), gestures and follow action system to control Loopy Pro.		Loopy Pro's actions can provide control over almost every aspect of Loopy Pro and can be used to create custom behavior. Actions are used by the MIDI Learn/MIDI Binding system, widgets (buttons, sliders, dials, etc), gestures and follow action system to control Loopy Pro.

	= MIDI Learn =		== MIDI Learn ==
	When you MIDI Learn in Loopy Pro, you are creating a MIDI Binding to an action which you can also customize or add to. The bindings and their actions are accessed by the Control Settings panel.		When you MIDI Learn in Loopy Pro, you are creating a MIDI Binding to an action which you can also customize or add to. The bindings and their actions are accessed by the Control Settings panel.

	= Action Sequences =		== Action Sequences ==

	Anywhere in Loopy Pro where an action can be used, a series of actions can be used. There will be a "+" icon you can tap to add more actions. For example, if you MIDI Learn Play/Stop for a clip, you can go into Control Settings and find the MIDI binding you created and add more actions to the sequence so that your MIDI binding does more than just toggle play for that clip.		Anywhere in Loopy Pro where an action can be used, a series of actions can be used. There will be a "+" icon you can tap to add more actions. For example, if you MIDI Learn Play/Stop for a clip, you can go into Control Settings and find the MIDI binding you created and add more actions to the sequence so that your MIDI binding does more than just toggle play for that clip.

	= Action Timing =		== Action Timing ==

	To the left of each action is a white circle. Tapping on the circle pops up a panel to set options for when the action is performed.		To the left of each action is a white circle. Tapping on the circle pops up a panel to set options for when the action is performed.

Line 30:		Line 28:
	If the timing is set to Quantization, the action is performed at the next time that the clocks aligns with that quantization setting. If the timing is set to Delay, the action happens after Delay of the specified time and is independent of the clock's position. If the clock is not moving, all quantizations fire immediately!		If the timing is set to Quantization, the action is performed at the next time that the clocks aligns with that quantization setting. If the timing is set to Delay, the action happens after Delay of the specified time and is independent of the clock's position. If the clock is not moving, all quantizations fire immediately!

	= Action Timing and Tempo =		=== Action Timing and Tempo ===
	Timing (as of 1.1.17) is always related to musical time/tempo. When the tempo hasn't yet been defined, events with delays or quantization execute immediately.		Timing (as of 1.1.17) is always related to musical time/tempo. When the tempo hasn't yet been defined, events with delays or quantization execute immediately.

	= After Last/With Last/Next Trigger =		=== After Last/With Last/Next Trigger ===
	The timing options for all but the first action are slightly different from the first action's.		The timing options for all but the first action are slightly different from the first action's.

Line 44:		Line 42:
	'''With Last'''. The action is performed simultaneous with the previous action (with the specified quantization or delay). Use this when you need actions to fire truly simultaneously or for the timing to be precisely based on the previous actions execution time. In some contexts After Last and With Last will seem to be the same, but in some cases it can make a difference. Especially if any action changes something that a subsequent action relies on.		'''With Last'''. The action is performed simultaneous with the previous action (with the specified quantization or delay). Use this when you need actions to fire truly simultaneously or for the timing to be precisely based on the previous actions execution time. In some contexts After Last and With Last will seem to be the same, but in some cases it can make a difference. Especially if any action changes something that a subsequent action relies on.

	'''Next Trigger'''. This action is fired the next time that the action sequence is triggered. For example, you might have a button that the first time it is pressed mutes the bass instrument and records clip 1 and on the second press unmutes the guitar, mutes the bass and records clip 2		'''Next Trigger'''. This action is fired the next time that the action sequence is triggered. For example, you might have a button that the first time it is pressed mutes the bass instrument and records clip 1 and on the second press unmutes the guitar, mutes the bass and records clip 2.

			=== Stop Clip Timing ===
	= Stop Clip Timing =
	Most actions execute immediately, stop clip is different in a very useful way. The Stop Clip and Stop Recording actions are not considered complete until the stopped clip is stopped. This is very useful if you want to sequence clip playback. Let's say that you want to have a button or MIDI binding that plays or solos clip 1 for one cycle and then plays or solos clip 2 after clip 1 is finished playing. The easiest way to accomplish it is to have this action sequence:		Most actions execute immediately, stop clip is different in a very useful way. The Stop Clip and Stop Recording actions are not considered complete until the stopped clip is stopped. This is very useful if you want to sequence clip playback. Let's say that you want to have a button or MIDI binding that plays or solos clip 1 for one cycle and then plays or solos clip 2 after clip 1 is finished playing. The easiest way to accomplish it is to have this action sequence:
	* Play Clip 1		* Play Clip 1
Line 57:		Line 54:
	There are other ways to play/solo clips in order but they require you to set the timing based on the clip length. This method will work without needing to know the clip lengths.		There are other ways to play/solo clips in order but they require you to set the timing based on the clip length. This method will work without needing to know the clip lengths.

	= Action Timing Icons =		=== Action Timing Icons ===

	[[File:loopy_pro_action_icons.jpeg\|600px]]		[[File:loopy_pro_action_icons.jpeg\|600px]]

Line 67:		Line 63:
	* A circle with an arrow indicates "After Last"		* A circle with an arrow indicates "After Last"

	= Helpful Hints =		== Helpful Hints ==

	Use quantization when timing needs to be precise and even a millisecond or two would make a difference.		Use quantization when timing needs to be precise and even a millisecond or two would make a difference.

Line 74:		Line 69:

	'''Dummy Actions'''. If you need to quantize an action after a delay, you may need to create a dummy action that does nothing but delay. If the action itself is a play or stop or record action which has its own quantization settings, set the quantization within that action. If you need to use a "dummy" action to delay, you can add a the Adjust Parameter Clip Action without specifying a target clip or Trigger Widget action without specifying a widget or any action that would do nothing.		'''Dummy Actions'''. If you need to quantize an action after a delay, you may need to create a dummy action that does nothing but delay. If the action itself is a play or stop or record action which has its own quantization settings, set the quantization within that action. If you need to use a "dummy" action to delay, you can add a the Adjust Parameter Clip Action without specifying a target clip or Trigger Widget action without specifying a widget or any action that would do nothing.

			== Example Library ==

			* '''Repeating Actions with a Button and Dial''' - [https://wiki.loopypro.com/images/5/56/EXAMPLE_Repeating_Widget.zip this project] demonstrates one way to set up repeating sequences of actions using a button and a stepped dial.

	= Related Pages =		= Related Pages =
	[[Action List]]		[[Action List]]
	[https://loopypro.com/manual/#actions Loopy Pro Manual - Actions Chapter]		[https://loopypro.com/manual/#actions Loopy Pro Manual - Actions Chapter]

Edwards: /* Helpful Hints */

2024-06-15T16:37:28Z

Helpful Hints

← Older revision		Revision as of 02:37, 16 June 2024
Line 71:		Line 71:
	Use quantization when timing needs to be precise and even a millisecond or two would make a difference.		Use quantization when timing needs to be precise and even a millisecond or two would make a difference.

	'''Delay Plus Quantization'''. You will sometimes need to have a delay before a quantized event to make sure that it fires on the NEXT quantization interval rather than right now as in the ''Stop Clip Timing'' example elsewhere on this page. If the clock is at 0, every quantization amount would trigger.		'''Delay Plus Quantization'''. You will sometimes need to have a delay before a quantized event to make sure that it fires on the NEXT quantization interval rather than right now as in the ''Stop Clip Timing'' example elsewhere on this page. If the clock is at 0, every quantization amount would trigger. For example, if there is a record or play clip action quantized to the master clock (or 1 bar) and it is immediately followed by a stop clip or stop recording action with the same quantization, the stop will happen immediately because the clock will still be at the specified boundary. Using a small delay for the stop action (say an eighth note) ensures that the clock is no longer at the specified boundary and will execute the event at the next appropriate interval..

	'''Dummy Actions'''. If you need to quantize an action after a delay, you may need to create a dummy action that does nothing but delay. If the action itself is a play or stop or record action which has its own quantization settings, set the quantization within that action. If you need to use a "dummy" action to delay, you can add a the Adjust Parameter Clip Action without specifying a target clip or Trigger Widget action without specifying a widget or any action that would do nothing.		'''Dummy Actions'''. If you need to quantize an action after a delay, you may need to create a dummy action that does nothing but delay. If the action itself is a play or stop or record action which has its own quantization settings, set the quantization within that action. If you need to use a "dummy" action to delay, you can add a the Adjust Parameter Clip Action without specifying a target clip or Trigger Widget action without specifying a widget or any action that would do nothing.

Edwards: /* Stop Clip Timing */

2024-06-15T16:27:52Z

Stop Clip Timing

← Older revision		Revision as of 02:27, 16 June 2024
Line 50:		Line 50:
	Most actions execute immediately, stop clip is different in a very useful way. The Stop Clip and Stop Recording actions are not considered complete until the stopped clip is stopped. This is very useful if you want to sequence clip playback. Let's say that you want to have a button or MIDI binding that plays or solos clip 1 for one cycle and then plays or solos clip 2 after clip 1 is finished playing. The easiest way to accomplish it is to have this action sequence:		Most actions execute immediately, stop clip is different in a very useful way. The Stop Clip and Stop Recording actions are not considered complete until the stopped clip is stopped. This is very useful if you want to sequence clip playback. Let's say that you want to have a button or MIDI binding that plays or solos clip 1 for one cycle and then plays or solos clip 2 after clip 1 is finished playing. The easiest way to accomplish it is to have this action sequence:
	* Play Clip 1		* Play Clip 1
	* Stop Clip 1 set to trigger after last a slight delay - with stop quantization set to loop		* Stop Clip 1 set to trigger after last with a slight delay - with stop quantization set to loop
	* Play Clip 2 - with play quantization set to 1 bar (if the clips are a precise number of bars long) or none.		* Play Clip 2 - with play quantization set to 1 bar (if the clips are a precise number of bars long) or none.

	The slight delay is needed for the stop action or clip 1 would stop immediately because it is already at the loop boundary.		The slight delay is needed for the stop action or clip 1 would stop immediately because it is already at the loop boundary.

	There are other ways to play/solo clips in order but they require you to set the timing. This method will work without needing to know the clip lengths.		There are other ways to play/solo clips in order but they require you to set the timing based on the clip length. This method will work without needing to know the clip lengths.

	= Action Timing Icons =		= Action Timing Icons =

Edwards: /* Stop Clip Timing */

2024-06-15T16:26:14Z

Stop Clip Timing

← Older revision		Revision as of 02:26, 16 June 2024
Line 48:		Line 48:

	= Stop Clip Timing =		= Stop Clip Timing =
	Most actions execute immediately, stop clip is different in a very useful way. The Stop Clip ~~action is~~ considered ~~done~~ until the stopped clip is stopped. This is very useful if you want to sequence clip playback. Let's say that you want to have a button or MIDI binding that plays or solos clip 1 for one cycle and then plays or solos clip 2 after clip 1 is finished playing. The easiest way to accomplish it is to have this action sequence:		Most actions execute immediately, stop clip is different in a very useful way. The Stop Clip and Stop Recording actions are not considered complete until the stopped clip is stopped. This is very useful if you want to sequence clip playback. Let's say that you want to have a button or MIDI binding that plays or solos clip 1 for one cycle and then plays or solos clip 2 after clip 1 is finished playing. The easiest way to accomplish it is to have this action sequence:
	* Play Clip 1		* Play Clip 1
	* Stop Clip 1 set to trigger after last a slight delay - with stop quantization set to loop		* Stop Clip 1 set to trigger after last a slight delay - with stop quantization set to loop

Edwards: /* Action Timing and Tempo */

2024-06-15T16:24:29Z

Action Timing and Tempo

← Older revision		Revision as of 02:24, 16 June 2024
Line 31:		Line 31:

	= Action Timing and Tempo =		= Action Timing and Tempo =
	Timing (as of 1.1.17) is always related to musical time/tempo. When the tempo hasn't yet been defined, events ~~fire~~ immediately.		Timing (as of 1.1.17) is always related to musical time/tempo. When the tempo hasn't yet been defined, events with delays or quantization execute immediately.

	= After Last/With Last/Next Trigger =		= After Last/With Last/Next Trigger =