Logic articulation sets
Import and export Logic Pro articulation sets (.plist) from DawForge — what translates, what doesn't, and the differences vs. Cubase.
DawForge supports Logic Pro Articulation Sets at both ends of the workflow. You can import an existing .plist and edit it in the same editor you'd use for Cubase, and you can export any map (whatever its source) as a .plist.
Import
Use /map-editor/import. The page accepts .plist files directly, or a .zip containing several. DawForge reads Logic's standard Articulation Set format and turns each articulation into one row in the editor.
What translates on import:
- Articulation name.
- Switch type — Logic's "Note On" → DawForge keyswitch; "Controller" → DawForge CC; "Program Change" → DawForge program change.
- MIDI channel.
- Output value(s).
- Articulation ID — Logic's unique-per-set number is kept as the row's remote-key trigger (nudged slightly to avoid clashes if you later mix Logic imports and Cubase keyswitches in the same map).
What's lost or approximated:
- Symbols and symbol mappings. Logic associates each articulation with a notation symbol displayed in the Score editor; DawForge doesn't carry score-engraving metadata. The articulation is preserved; the symbol isn't.
- Articulation groups. Logic has its own groups concept distinct from Cubase's 0–3 lanes. DawForge folds them into the canonical Cubase-style groups, picking the closest match.
Export
In any saved map, Download → Logic (.plist) writes an Articulation Set. The export:
- Generates the Articulation Set with one entry per non-disabled row.
- Assigns articulation IDs starting at 1, derived from row order.
- Picks "Note On", "Controller", or "Program Change" per output type.
- Sets the switch range / value as appropriate.
What's dropped:
- DawForge tags and the hidden per-row identifier (Logic has no place for them).
- Pre-delay / separation timings (Logic doesn't expose equivalent fields in the Articulation Set; use track inserts).
- Multi-output rows are flattened — Logic Articulation Sets are one switch per articulation. If a row has both a CC and a keyswitch, the export uses the first output and warns.
Versions
DawForge writes Articulation Sets for the Logic Pro version listed in Tools you need. Earlier Logic Pro versions read them with mild quirks (some advanced switch types may be ignored); confirm in your DAW before relying on edge cases.
Where Logic and Cubase diverge
| Feature | Cubase | Logic |
|---|---|---|
| Score-engraving symbols | Implicit (color/lane) | Explicit per-articulation symbol |
| Multi-output per articulation | Yes (multiple outputs per slot) | One switch per articulation |
| Pre-delay / separation per articulation | Yes | No (use track inserts) |
| Live remote key triggering | Yes (Remote Keys section) | Yes (different mechanism via Smart Controls) |
| Round-trip stability | Row identity preserved | Re-numbered on each export |
For ongoing work the same map is fine on both. If you live in Logic only, you can ignore the Cubase-specific fields entirely.