Flow
Flow — Logic (beta)
Current Logic Pro support in DawForge. Maps work end-to-end; the Flow bridge is Cubase-only for now.
Logic bridge is not yet shipping. The expression-map workflow (build, import, export
.plist) is fully supported on Logic Pro today.What works on Logic right now
| Feature | Status |
|---|---|
| Knowledge base browse and acquire | ✓ |
| Map editor (build from scratch, import, export) | ✓ |
.plist Articulation Set import | ✓ |
.plist Articulation Set export | ✓ |
| Round-trip via DawForge | ✓ (with the Logic-specific caveats) |
| Templates (Cubase Track Archive import) | ✗ (Logic projects export differently) |
| Flow live track selection | ✗ |
| Flow articulation switching | ✗ |
| Flow solo / show / hide | ✗ |
Why no Flow on Logic yet
Flow leans on two things Cubase has and Logic doesn't (yet):
- Two-way remote control. Cubase can take live commands from DawForge and tell DawForge what's selected, so the two stay in sync. Logic has its own scripting, but nothing that talks back in the same way.
- Select a track purely by its name. In Cubase, DawForge can say "select the track called X" and Cubase finds it at any distance, even when it's hidden. Logic has no equivalent — it can't reliably jump to a track just from its name.
The upshot is that Flow's core promise — "click a row and the right track gets selected, every time, no matter the folder or visibility" — is something we can deliver on Cubase but not (yet) on Logic.
What's plausible
Two paths we're tracking:
- A stripped-down Logic version of Flow that switches articulations on whichever track you've got focused, but doesn't move the selection for you. It would use a small Logic script that listens for switch commands. Less powerful than the Cubase version, but handy for solo practice.
- Selection through Logic's key commands. Less direct and more fragile. We've prototyped it; it works on a clean project but falls apart quickly once there are a lot of tracks.
Neither has a ship date.
Signal your interest
If you'd use a Logic bridge, let us know via the contact form on dawforge.com. Interest signal directly affects how the roadmap is sequenced.
Workflow recommendations for Logic users today
- Build maps in DawForge, use them in Logic. Export to
.plistand load in Logic's Articulation Set editor. - Use the Mobile companion for articulation switching from a phone — it works with any DAW that can receive MIDI from the DawForge Bridge port. See Mobile companion.
- Cross-DAW projects: if you work on a piece in Logic and finish in Cubase, the same map travels (export Cubase from DawForge for the final).