Sync Tricks With Loopy AUv3 - Revision history

Wim-number37: /* Send Clock independent of Host Transport */ Added Drambo example

2024-08-06T05:22:18Z

Send Clock independent of Host Transport: Added Drambo example

← Older revision		Revision as of 15:22, 6 August 2024
Line 6:		Line 6:
	MIDI clock out isn't sent when many hosts, including Loopy's, transport is stopped. Sometimes it's desirable to keep clock flowing at all times to external hardware, such as delays that accept external clock. This example targets Loopy Pro as the host, but it can be adapted to other hosts such as Drambo.		MIDI clock out isn't sent when many hosts, including Loopy's, transport is stopped. Sometimes it's desirable to keep clock flowing at all times to external hardware, such as delays that accept external clock. This example targets Loopy Pro as the host, but it can be adapted to other hosts such as Drambo.

			=== Example: Loopy Pro ===
	* Add a Loopy Pro AU midi processor as a midi input. The instance can be empty.		* Add a Loopy Pro AU midi processor as a midi input. The instance can be empty.
	** Enable Ableton Link, but not Link Start/Stop in the AU.		** Enable Ableton Link, but not Link Start/Stop in the AU.
Line 17:		Line 18:

	The AU will stay in sync with the Loopy Host tempo won't be affected by the host transport. It will send clock out reliably to the destination until you stop the plugin instance's transport.		The AU will stay in sync with the Loopy Host tempo won't be affected by the host transport. It will send clock out reliably to the destination until you stop the plugin instance's transport.

			=== Example: Drambo ===
			* Add a Loopy Pro Audio Unit MIDI Processor module in Drambo. The instance can be empty.
			** Enable Ableton Link, but not Start/Stop in Loopy.
			** Disable host sync in Loopy.
			** Set the clock out destination in Loopy.
			** Make sure there are no MIDI Clock Sources in Loopy.
			* Disconnect the Drambo track's midi output from the Loopy module to avoid possibly doubling the clock.
			* Enable Link in Drambo. (Start / stop can be what you like. Loopy will ignore it.)
			* Disable the Clock destination Drambo. (Clock will come direct from Loopy.)
			* Press play in the AU and keep it running.

	== Sync Hosts That Don't Follow Clock ==		== Sync Hosts That Don't Follow Clock ==

Wim-number37: Trying to get the category tag right...

2024-08-05T05:48:13Z

Trying to get the category tag right...

← Older revision		Revision as of 15:48, 5 August 2024
Line 1:		Line 1:
	[[Category:Tips and Tricks]]		[[Category:Tips and Tricks]]

	Loopy Pro can enable some powerful workaround to host clock and sync shortcomings. Use cases can be listed here		Loopy Pro can enable some powerful workaround to host clock and sync shortcomings. Use cases can be listed here

Wim-number37: Created

2024-08-05T05:46:22Z

Created

New page

[[Category:Tips and Tricks]]
Loopy Pro can enable some powerful workaround to host clock and sync shortcomings. Use cases can be listed here

== Send Clock independent of Host Transport ==
MIDI clock out isn't sent when many hosts, including Loopy's, transport is stopped. Sometimes it's desirable to keep clock flowing at all times to external hardware, such as delays that accept external clock. This example targets Loopy Pro as the host, but it can be adapted to other hosts such as Drambo.

* Add a Loopy Pro AU midi processor as a midi input. The instance can be empty.
** Enable Ableton Link, but not Link Start/Stop in the AU.
** Disable host sync in the AU.
** Set the clock out destination in the Loopy AU.
** Make sure there are no MIDI Clock Sources in the Loopy AU.
* Enable Link in the host.
** Link Start / Stop can be what you like)
** Disable the Clock destination in the host.
** Press play in the AU and keep it running.

The AU will stay in sync with the Loopy Host tempo won't be affected by the host transport. It will send clock out reliably to the destination until you stop the plugin instance's transport.

== Sync Hosts That Don't Follow Clock ==
(If they follow Ableton Link)

AUM is a notable example of a mainstream app that can send, but not follow MIDI Clock at this time. Loopy AUv3 running as a plugin in AUM can be used to overcome this without using an external app as a bridge.

* Add a Loopy Pro Midi Processor AU in an AUM Midi Channel. The instance can be completely empty.
** Enable Ableton Link and Link Start/Stop
** Set the Clock Source to the midi clock source. Remove all other sources.
* Enable Ableton Link and Link Start/Stop in AUM.
** No MIDI routings to Loopy are needed.
** Be sure AUM isn't set to send clock out to Loopy.

Loopy should receive tempo and transport from the clock source and will update Link tempo and start/stop, which AUM will respond to.