AudioUnit plugin - Revision history

Benjustchords: /* Use Cases */

2026-01-19T18:08:09Z

Use Cases

← Older revision		Revision as of 20:08, 19 January 2026
Line 42:		Line 42:
	* Building looping and modular performance templates where JustChords provides chord progression and structure while the DAW handles audio looping, effects and recording.		* Building looping and modular performance templates where JustChords provides chord progression and structure while the DAW handles audio looping, effects and recording.

	~~-->~~ AUv3 users~~, please describe~~ your configurations and ~~use cases—goals~~ you ~~can~~ achieve with the JustChords AUv3 ~~plugin~~.		'''AUv3 users: You can add value to this page by contributing your own configurations, routing setups and goals you achieve with the JustChords AUv3 plug‑in in this section.'''

Benjustchords at 18:06, 19 January 2026

2026-01-19T18:06:23Z

← Older revision		Revision as of 20:06, 19 January 2026
Line 6:		Line 6:
	=== MIDI Output Configuration ===		=== MIDI Output Configuration ===

	JustChords provides '''two configurable MIDI outputs: MIDI 1 and MIDI 2'''.		JustChords provides '''two configurable MIDI outputs''', named '''MIDI 1''' and '''MIDI 2'''.
			Each output can be set to one of the following modes:

	~~Each output supports these modes:~~		* '''Off''' – No MIDI data is transmitted on this port.
	* '''Off''': No MIDI ~~transmission~~.		* '''MIDI Chords''' – Sends standard MIDI note block chords in sync with the DAW transport.
	* '''MIDI Chords''': Sends standard MIDI note block chords on transport ~~beats~~.		* '''TonePacketProtocol Chords''' – Sends chords using the Tone Packet protocol for compatible apps and devices.
	* '''TonePacketProtocol Chords'''~~: Proprietary chord format~~ for compatible apps/devices.

	~~For Chords mode~~:		When using MIDI chords:
	* Set '''anticipation''' (lead-in) to allow downstream apps processing time: 1/4 beat, 1/8 beat, or 1/16 beat.[user-provided]
	* Chords fire in sync with DAW transport

	~~Additionally~~:		* An '''anticipation''' (lead‑in) value can be configured so that downstream apps have processing time (for example 1/4, 1/8 or 1/16 beat before the grid position).
	* '''MIDI on song appear''': Sends a ~~custom~~ MIDI message ~~when~~ a new song is displayed/loaded~~. You can define~~ message in SongEditor.		* Chords are generated and transmitted in time with the DAW’s playhead and tempo.
	* '''MIDI in SongStructure definition''' ~~- IN_PROGRESS~~
	* '''Control ~~Messages~~'''~~: Transmits~~ CC messages on section changes.		Additional options:
	** First section: CC with value 1		* '''MIDI on song appear''' – Sends a user‑defined MIDI message whenever a new song is displayed or loaded; the message is configured per song in the SongEditor.
	** Second section: CC with value 2		* '''MIDI in SongStructure definition''' – Planned feature for embedding MIDI events directly into SongStructure items (work in progress).
	** ~~Etc.~~		* '''Control messages''' – Sends MIDI CC messages on section changes:
	** End of last section: CC with value 0		** First section: CC with value 1
	** ~~Full spec:~~ MIDI CONTROL port transmits CC ~~when entering~~ new ~~sections (1~~, ~~2, etc.);~~ value 0 at song end.		** Second section: CC with value 2
			** And so on for subsequent sections
			** End of the last section: CC with value 0
			** The dedicated MIDI CONTROL port transmits these CC messages whenever a new section is entered, with value 0 signalling song end.

	=== TonePacket Protocol ===		=== TonePacket Protocol ===
	https://forum.loopypro.com/discussion/60971/introducing-tone-packets		The '''Tone Packet protocol''' is an extended MIDI‑style format for transmitting richer chord and harmony information between compatible apps.
			JustChords can output chords as Tone Packets so that hosts and instruments that support the protocol can receive more detailed harmonic data than with plain MIDI notes.

			For more background, see the Loopy Pro forum article:
			:[https://forum.loopypro.com/discussion/60971/introducing-tone-packets Introducing Tone Packets]

	=== Use Cases ===		=== Use Cases ===
			Common AUv3 plug‑in use cases include:

			* Live chord triggering from JustChords into synths or samplers hosted in Loopy Pro or AUM.
			* Driving song section changes and automation by mapping JustChords’ control‑port CC messages to widgets or scripts in the host environment.
			* Building looping and modular performance templates where JustChords provides chord progression and structure while the DAW handles audio looping, effects and recording.

	AUv3 users, please describe your configurations and use cases—goals you can achieve with the JustChords AUv3 plugin.		--> AUv3 users, please describe your configurations and use cases—goals you can achieve with the JustChords AUv3 plugin.

Marekpalka at 15:45, 19 January 2026

2026-01-19T15:45:22Z

← Older revision		Revision as of 17:45, 19 January 2026
Line 26:		Line 26:
	** End of last section: CC with value 0		** End of last section: CC with value 0
	** Full spec: MIDI CONTROL port transmits CC when entering new sections (1, 2, etc.); value 0 at song end.		** Full spec: MIDI CONTROL port transmits CC when entering new sections (1, 2, etc.); value 0 at song end.

			=== TonePacket Protocol ===
			https://forum.loopypro.com/discussion/60971/introducing-tone-packets

	=== Use Cases ===		=== Use Cases ===

	AUv3 users, please describe your configurations and use cases—goals you can achieve with the JustChords AUv3 plugin.		AUv3 users, please describe your configurations and use cases—goals you can achieve with the JustChords AUv3 plugin.

Marekpalka: /* Use Cases */

2026-01-19T15:43:03Z

Use Cases

← Older revision		Revision as of 17:43, 19 January 2026
Line 28:		Line 28:

	=== Use Cases ===		=== Use Cases ===

			AUv3 users, please describe your configurations and use cases—goals you can achieve with the JustChords AUv3 plugin.

Marekpalka: /* Using JustChords as an Audio Unit Plugin */

2026-01-19T15:41:39Z

Using JustChords as an Audio Unit Plugin

← Older revision		Revision as of 17:41, 19 January 2026
Line 19:		Line 19:
	Additionally:		Additionally:
	* '''MIDI on song appear''': Sends a custom MIDI message when a new song is displayed/loaded. You can define message in SongEditor.		* '''MIDI on song appear''': Sends a custom MIDI message when a new song is displayed/loaded. You can define message in SongEditor.
			* '''MIDI in SongStructure definition''' - IN_PROGRESS
	* '''Control Messages''': Transmits CC messages on section changes.		* '''Control Messages''': Transmits CC messages on section changes.
	** First section: CC with value 1		** First section: CC with value 1
Line 25:		Line 26:
	** End of last section: CC with value 0		** End of last section: CC with value 0
	** Full spec: MIDI CONTROL port transmits CC when entering new sections (1, 2, etc.); value 0 at song end.		** Full spec: MIDI CONTROL port transmits CC when entering new sections (1, 2, etc.); value 0 at song end.

			=== Use Cases ===

Marekpalka at 15:40, 19 January 2026

2026-01-19T15:40:35Z

← Older revision		Revision as of 17:40, 19 January 2026
Line 25:		Line 25:
	** End of last section: CC with value 0		** End of last section: CC with value 0
	** Full spec: MIDI CONTROL port transmits CC when entering new sections (1, 2, etc.); value 0 at song end.		** Full spec: MIDI CONTROL port transmits CC when entering new sections (1, 2, etc.); value 0 at song end.

	~~=== Loopy Pro Integration ===~~

	~~# In Loopy Pro mixer, add JustChords as Instrument or MIDI Processor on a channel.~~
	~~# Configure MIDI 1/2 outputs to Loopy bindings, clips, or other AUv3 instruments for chord-triggered loops/sequencing. [youtube](https://www.youtube.com/watch?v=KYtJIbWDOfg)~~
	~~# Use anticipation for tight sync; map Control CC to Loopy actions (e.g., clip arming per section).~~
	~~# Control JustChords playback via Loopy MIDI clips/actions; enable OnSongAppear for song changes.[user-provided] [loopypro](https://loopypro.com/manual/)~~

	~~=== AUM Integration ===~~

	~~# Create a MIDI chain; insert JustChords early, route MIDI 1/2 to instruments/effects downstream.~~
	~~# Attach audio sources (files, Apple Music) for transport sync; use Control CC for section-based automation.[user-provided] [kymatica](https://kymatica.com/aum/help)~~
	~~# Set chord anticipation to match AUM latency; test OnSongAppear for playlist workflows.~~

	~~=== Tips and Best Practices ===~~

	* '''Sync Prep''': Load songs in standalone JustChords first; transpose, capo, or autoscroll as needed. [apps.apple](https://apps.apple.com/us/app/justchords/id1632968272)
	* '''Routing''': MIDI 1 for chords, MIDI 2 for Control/OnSongAppear; split to multiple targets.[user-provided]
	* '''Limitations''': No per-song triggers beyond OnSongAppear; no MIDI clock output (DAW provides). [perplexity](https://www.perplexity.ai/search/79ecfc1a-49b5-46d7-b70e-3b31a798ab7c)
	* '''Community**: Share workflows on JustChords Discord; test in TestFlight betas.

	~~For advanced setups, refer to DAW manuals (Loopy Pro, AUM) and experiment with MIDI monitoring tools. [loopypro](https://loopypro.com/manual/)~~

	~~----~~

	~~''Last edited: January 19, 2026''<br/>~~
	~~''Keywords: AUv3, MIDI plugin, Loopy Pro, AUM, chord triggering''~~

Marekpalka at 15:39, 19 January 2026

2026-01-19T15:39:34Z

← Older revision		Revision as of 17:39, 19 January 2026
Line 15:		Line 15:
	For Chords mode:		For Chords mode:
	* Set '''anticipation''' (lead-in) to allow downstream apps processing time: 1/4 beat, 1/8 beat, or 1/16 beat.[user-provided]		* Set '''anticipation''' (lead-in) to allow downstream apps processing time: 1/4 beat, 1/8 beat, or 1/16 beat.[user-provided]
	* Chords fire in sync with DAW transport~~; no native MIDI clock generation (use host/DAW clock). [perplexity](https://www.perplexity.ai/search/e2ecb3e0-7dbf-4d38-90e3-a9aa97cde95c)~~		* Chords fire in sync with DAW transport

	Additionally:		Additionally:
	* '''~~OnSongAppear~~''': Sends a custom MIDI message when a new song is displayed/loaded.~~[user-provided]~~		* '''MIDI on song appear''': Sends a custom MIDI message when a new song is displayed/loaded. You can define message in SongEditor.
	* '''Control Messages''' ~~(via dedicated Control port)~~: Transmits CC messages on section changes.		* '''Control Messages''': Transmits CC messages on section changes.
	** First section: CC with value 1		** First section: CC with value 1
	** Second section: CC with value 2		** Second section: CC with value 2
	** Etc.		** Etc.
	** End of last section: CC with value 0		** End of last section: CC with value 0
	** Full spec: MIDI CONTROL port transmits CC when entering new sections (1, 2, etc.); value 0 at song end.~~[user-provided]~~		** Full spec: MIDI CONTROL port transmits CC when entering new sections (1, 2, etc.); value 0 at song end.

	=== Loopy Pro Integration ===		=== Loopy Pro Integration ===

Marekpalka at 15:37, 19 January 2026

2026-01-19T15:37:55Z

← Older revision		Revision as of 17:37, 19 January 2026
Line 2:		Line 2:
	== Using JustChords as an Audio Unit Plugin ==		== Using JustChords as an Audio Unit Plugin ==

	'''JustChords''' operates as an AUv3 MIDI plugin in DAWs like Loopy Pro and AUM, sending block chords and control messages synchronized to the transport. It features two independent MIDI outputs (MIDI 1 and MIDI 2) for flexible routing to instruments, samplers, or other plugins.[user-provided] Users commonly integrate it for live chord triggering, section changes, and song progression in looping and modular workflows. ~~[perplexity](https://www.perplexity.ai/search/79ecfc1a-49b5-46d7-b70e-3b31a798ab7c)~~		'''JustChords''' operates as an AUv3 MIDI plugin in DAWs like Loopy Pro and AUM, sending block chords and control messages synchronized to the transport. It features two independent MIDI outputs (MIDI 1 and MIDI 2) for flexible routing to instruments, samplers, or other plugins.[user-provided] Users commonly integrate it for live chord triggering, section changes, and song progression in looping and modular workflows.

	~~=== General Setup in DAWs ===~~

	~~# Load JustChords as a MIDI processor or instrument AUv3 in your DAW's plugin slot, mixer channel, or chain.~~
	~~#* In Loopy Pro: Add via mixer on a color channel (Instrument or MIDI FX). [loopypro](https://loopypro.com/manual/)~~
	~~#* In AUM: Insert early in a MIDI chain before target instruments. [kymatica](https://kymatica.com/aum/help)~~
	~~# Import or create songs with chords, lyrics, and sections inside the plugin interface.~~
	~~# Enable transport/playback to output MIDI data on beats; prepare playlists via standalone JustChords app or iCloud sync. [apps.apple](https://apps.apple.com/us/app/justchords/id1632968272)~~
	~~# Route MIDI 1/MIDI 2 outputs to downstream AUv3s, loops, or hardware for sound generation and control. [justchords](https://www.justchords.app/help-integrations/)~~

	=== MIDI Output Configuration ===		=== MIDI Output Configuration ===

	JustChords provides '''two configurable MIDI outputs: MIDI 1 and MIDI 2'''.~~[user-provided]~~		JustChords provides '''two configurable MIDI outputs: MIDI 1 and MIDI 2'''.

	Each output supports these modes:		Each output supports these modes:
Line 22:		Line 13:
	* '''TonePacketProtocol Chords''': Proprietary chord format for compatible apps/devices.		* '''TonePacketProtocol Chords''': Proprietary chord format for compatible apps/devices.

	For ~~MIDI~~ Chords mode:		For Chords mode:
	* Set '''anticipation''' (lead-in) to allow downstream apps processing time: 1/4 beat, 1/8 beat, or 1/16 beat.[user-provided]		* Set '''anticipation''' (lead-in) to allow downstream apps processing time: 1/4 beat, 1/8 beat, or 1/16 beat.[user-provided]
	* Chords fire in sync with DAW transport; no native MIDI clock generation (use host/DAW clock). [perplexity](https://www.perplexity.ai/search/e2ecb3e0-7dbf-4d38-90e3-a9aa97cde95c)		* Chords fire in sync with DAW transport; no native MIDI clock generation (use host/DAW clock). [perplexity](https://www.perplexity.ai/search/e2ecb3e0-7dbf-4d38-90e3-a9aa97cde95c)

Marekpalka: Created page with "300px| == Using JustChords as an Audio Unit Plugin == '''JustChords''' operates as an AUv3 MIDI plugin in DAWs like Loopy Pro and AUM, sending block chords and control messages synchronized to the transport. It features two independent MIDI outputs (MIDI 1 and MIDI 2) for flexible routing to instruments, samplers, or other plugins.[user-provided] Users commonly integrate it for live chord triggering, section changes, and song progressi..."

2026-01-19T15:36:37Z

Created page with "right|300px| == Using JustChords as an Audio Unit Plugin == '''JustChords''' operates as an AUv3 MIDI plugin in DAWs like Loopy Pro and AUM, sending block chords and control messages synchronized to the transport. It features two independent MIDI outputs (MIDI 1 and MIDI 2) for flexible routing to instruments, samplers, or other plugins.[user-provided] Users commonly integrate it for live chord triggering, section changes, and song progressi..."

New page

[[File:audiounitplugin.png|right|300px|]]
== Using JustChords as an Audio Unit Plugin ==

'''JustChords''' operates as an AUv3 MIDI plugin in DAWs like Loopy Pro and AUM, sending block chords and control messages synchronized to the transport. It features two independent MIDI outputs (MIDI 1 and MIDI 2) for flexible routing to instruments, samplers, or other plugins.[user-provided] Users commonly integrate it for live chord triggering, section changes, and song progression in looping and modular workflows. [perplexity](https://www.perplexity.ai/search/79ecfc1a-49b5-46d7-b70e-3b31a798ab7c)

=== General Setup in DAWs ===

# Load JustChords as a MIDI processor or instrument AUv3 in your DAW's plugin slot, mixer channel, or chain.
#* In Loopy Pro: Add via mixer on a color channel (Instrument or MIDI FX). [loopypro](https://loopypro.com/manual/)
#* In AUM: Insert early in a MIDI chain before target instruments. [kymatica](https://kymatica.com/aum/help)
# Import or create songs with chords, lyrics, and sections inside the plugin interface.
# Enable transport/playback to output MIDI data on beats; prepare playlists via standalone JustChords app or iCloud sync. [apps.apple](https://apps.apple.com/us/app/justchords/id1632968272)
# Route MIDI 1/MIDI 2 outputs to downstream AUv3s, loops, or hardware for sound generation and control. [justchords](https://www.justchords.app/help-integrations/)

=== MIDI Output Configuration ===

JustChords provides '''two configurable MIDI outputs: MIDI 1 and MIDI 2'''.[user-provided]

Each output supports these modes:
* '''Off''': No MIDI transmission.
* '''MIDI Chords''': Sends standard MIDI note block chords on transport beats.
* '''TonePacketProtocol Chords''': Proprietary chord format for compatible apps/devices.

For MIDI Chords mode:
* Set '''anticipation''' (lead-in) to allow downstream apps processing time: 1/4 beat, 1/8 beat, or 1/16 beat.[user-provided]
* Chords fire in sync with DAW transport; no native MIDI clock generation (use host/DAW clock). [perplexity](https://www.perplexity.ai/search/e2ecb3e0-7dbf-4d38-90e3-a9aa97cde95c)

Additionally:
* '''OnSongAppear''': Sends a custom MIDI message when a new song is displayed/loaded.[user-provided]
* '''Control Messages''' (via dedicated Control port): Transmits CC messages on section changes.
** First section: CC with value 1
** Second section: CC with value 2
** Etc.
** End of last section: CC with value 0
** Full spec: MIDI CONTROL port transmits CC when entering new sections (1, 2, etc.); value 0 at song end.[user-provided]

=== Loopy Pro Integration ===

# In Loopy Pro mixer, add JustChords as Instrument or MIDI Processor on a channel.
# Configure MIDI 1/2 outputs to Loopy bindings, clips, or other AUv3 instruments for chord-triggered loops/sequencing. [youtube](https://www.youtube.com/watch?v=KYtJIbWDOfg)
# Use anticipation for tight sync; map Control CC to Loopy actions (e.g., clip arming per section).
# Control JustChords playback via Loopy MIDI clips/actions; enable OnSongAppear for song changes.[user-provided] [loopypro](https://loopypro.com/manual/)

=== AUM Integration ===

# Create a MIDI chain; insert JustChords early, route MIDI 1/2 to instruments/effects downstream.
# Attach audio sources (files, Apple Music) for transport sync; use Control CC for section-based automation.[user-provided] [kymatica](https://kymatica.com/aum/help)
# Set chord anticipation to match AUM latency; test OnSongAppear for playlist workflows.

=== Tips and Best Practices ===

* '''Sync Prep''': Load songs in standalone JustChords first; transpose, capo, or autoscroll as needed. [apps.apple](https://apps.apple.com/us/app/justchords/id1632968272)
* '''Routing''': MIDI 1 for chords, MIDI 2 for Control/OnSongAppear; split to multiple targets.[user-provided]
* '''Limitations''': No per-song triggers beyond OnSongAppear; no MIDI clock output (DAW provides). [perplexity](https://www.perplexity.ai/search/79ecfc1a-49b5-46d7-b70e-3b31a798ab7c)
* '''Community**: Share workflows on JustChords Discord; test in TestFlight betas.

For advanced setups, refer to DAW manuals (Loopy Pro, AUM) and experiment with MIDI monitoring tools. [loopypro](https://loopypro.com/manual/)

----

''Last edited: January 19, 2026''<br/>
''Keywords: AUv3, MIDI plugin, Loopy Pro, AUM, chord triggering''