Flow troubleshooting

This page is a flat list of failure modes and what to do about them. Work top to bottom; the first few cover 90% of cases.

Status bar says "Disconnected"

The web app can't talk to the bridge script. In order:

1. Is the virtual MIDI port up?

   • Windows: open loopMIDI; confirm DawForge Bridge is listed.
   • macOS: open Audio MIDI Setup → MIDI Studio; confirm the IAC Driver's DawForge Bridge port exists and Device is online is ticked.

2. Does the browser tab have Web MIDI permission? Click the address-bar permission icon, allow MIDI, refresh.

3. Is the bridge bound in Cubase? Studio → Studio Setup → MIDI Remote → MIDI Remote Manager. DawForge Bridge should show green status with both MIDI input and output set to the DawForge Bridge virtual port. If Unassigned, click each cell and pick the port.

4. Is the script the right version? Re-download from the app and replace ArtificialHarmonics_DawForgeBridge.js in:

   • Windows: Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local\ArtificialHarmonics\DawForgeBridge\
   • macOS: ~/Documents/Steinberg/Cubase/MIDI Remote/Driver Scripts/Local/ArtificialHarmonics/DawForgeBridge/

5. Are you on a supported Cubase? See Tools you need for the minimum version and edition (Pro is required — Artist and Elements don't have everything DawForge needs).

"Connected" but track selection does nothing

Cubase is linked; the presets aren't installed.

1. On the Flow page, with the template selected, open Connect Cubase → Install presets again.
2. In Chrome or Edge it installs straight into Cubase's preset folder. On Safari or Firefox use Download zip instead — unzip it so the DawForge folder lands inside Documents/Steinberg/Cubase/User Presets/Project Logical Editor/.
3. Cubase 15 picks the presets up live — no restart. Older Cubase versions may need a restart.

"Bridge out of date" banner in Flow

DawForge shipped a newer bridge than the one installed in your Cubase, so Flow shows a passive amber banner.

1. Click Reconnect in the banner — it opens Connect Cubase at Step 1 — Bridge & presets.
2. Click Install (Chrome/Edge) or Download zip instead (Safari/Firefox) to write the latest script. In Chrome/Edge you'll pick your Steinberg/Cubase folder once (or not at all, if you granted it on a previous install).
3. Restart Cubase (or re-add the surface in MIDI Remote Manager) so it loads the new bridge.

A bridge too old to report its version at all is treated the same way — just reinstall to get current.

Tracks selected on the wrong track / nothing happens for one specific track

The presets are tied to track names at install time. If the Cubase project has been renamed since you installed them — or you opened a different project than the one the template came from — the names won't line up.

1. Confirm the Cubase project's track names match the template's track names exactly (case-sensitive).
2. If the template's been re-imported since you last installed the presets, open Connect Cubase → Install presets again.

Articulation grid is empty for a track

That track isn't linked to a patch yet. Open the template page, find the row, and link a library patch (see Annotating tracks).

Articulation switch fires, library doesn't respond

The MIDI is leaving DawForge correctly; the library isn't listening for it.

• Check the output type and value in the map editor against the library's documentation. Spitfire wants UACC on CC 32; Vienna wants keyswitches at the patch's configured base note; Orchestral Tools varies per series.
• If the library expects a specific MIDI channel and the output's channel doesn't match, fix it on the row.
• Some libraries gate keyswitches by velocity. Set the keyswitch output's velocity to something non-zero (the editor exposes this in the output detail).

Selection works but is sluggish

• Cubase is under heavy CPU load. Close inactive instrument racks; increase the audio buffer.
• Very large project. Flow itself handles thousands of tracks, but Cubase slows down dragging selection through huge projects.
• MIDI buffer set too low. Studio Setup → MIDI ports → increase the buffer.

Solo / show / hide misses tracks

Similar names are handled in the common case (soloing "Violins I" without leaving "Violins II" visible), but a couple of edge cases slip through:

• Tracks inside folders that are themselves hidden — Cubase can't act on a track while its parent folder is hidden. Make the parent folder visible first, then try again.
• Tracks whose name contains unusual characters — most punctuation is fine; some special characters may not survive the trip through Cubase. Rename if you can.

How to check your bridge version

The version number is written at the very top of the bridge file. To check it:

1. Open ArtificialHarmonics_DawForgeBridge.js in any text editor (the folder is listed above under "Is the script the right version?").
2. The first few lines show a version number — note it.
3. In DawForge, go to Settings → Cubase bridge (or the download link on the Flow setup page). The current version is shown there.

If your file's version is lower than the one the app shows, re-download and replace it. Cubase picks up the new file the next time it scans for MIDI Remote scripts — no restart on Cubase 13 and newer; older versions need a restart.

Phone link won't pair

See Mobile companion for the phone-specific failure modes.

Still stuck

Email support via the contact form on dawforge.com. Include:

• The template's ID (in the URL of the inspector).
• The Cubase version.
• What the status bar shows and what the browser console shows.

Next

• Mobile companion
• Plans and credits