AudioUnit plugin: Difference between revisions
From JustChords Wiki
More actions
Marekpalka (talk | contribs) No edit summary |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
=== MIDI Output Configuration === | === MIDI Output Configuration === | ||
JustChords provides '''two configurable MIDI outputs | JustChords provides '''two configurable MIDI outputs''', named '''MIDI 1''' and '''MIDI 2'''. | ||
Each output can be set to one of the following modes: | |||
* '''Off''' – No MIDI data is transmitted on this port. | |||
* '''Off''' | * '''MIDI Chords''' – Sends standard MIDI note block chords in sync with the DAW transport. | ||
* '''MIDI Chords''' | * '''TonePacketProtocol Chords''' – Sends chords using the Tone Packet protocol for compatible apps and devices. | ||
* '''TonePacketProtocol Chords''' | |||
When using MIDI chords: | |||
* 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). | |||
* ''' | * Chords are generated and transmitted in time with the DAW’s playhead and tempo. | ||
* | |||
Additional options: | |||
* '''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. | |||
* '''MIDI in SongStructure definition''' – Planned feature for embedding MIDI events directly into SongStructure items (work in progress). | |||
* '''Control messages''' – Sends MIDI CC messages on section changes: | |||
** First section: CC with value 1 | |||
** 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 === | |||
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 === | |||
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: 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.''' | |||
Latest revision as of 20:08, 19 January 2026
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.
MIDI Output Configuration
JustChords provides two configurable MIDI outputs, named MIDI 1 and MIDI 2. Each output can be set to one of the following modes:
- Off – No MIDI data is transmitted on this port.
- MIDI Chords – Sends standard MIDI note block chords in sync with the DAW transport.
- TonePacketProtocol Chords – Sends chords using the Tone Packet protocol for compatible apps and devices.
When using MIDI chords:
- 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).
- Chords are generated and transmitted in time with the DAW’s playhead and tempo.
Additional options:
- 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.
- MIDI in SongStructure definition – Planned feature for embedding MIDI events directly into SongStructure items (work in progress).
- Control messages – Sends MIDI CC messages on section changes:
- First section: CC with value 1
- 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
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:
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: 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.