Riffwork Bridge

Tag bars in Riffwork with RigWork presets. When playback crosses a tagged bar, Riffwork fires your preset automatically - MIDI goes out to your whole rig without touching RigWork.

What It Does

RigWork lives at rigwork.gpdoom.com and Riffwork at riffwork.gpdoom.com. Because they're on the same domain, they share access to browser localStorage. The bridge uses this to let the two apps talk:

Riffwork reads your RigWork presets from localStorage
You tag bars in Riffwork with those presets
During Riffwork playback, when the playhead crosses a tagged bar, Riffwork fires the preset over MIDI

This is how you sync your tab-learning practice session to your live rig - no Ableton, no timeline, no extra software. Open the tab, hit play, your rig follows along bar by bar.

Requirements

Both apps open in the same browser on the same device
Both at tools.gpdoom.com (the bridge uses localStorage, which is origin-scoped)
MIDI connected in RigWork (or in Riffwork - both share the same MIDI outputs via Web MIDI)
At least one preset in RigWork

Tagging Bars in Riffwork

Open your tab in Riffwork
Click the RigWork button in the toolbar (score-tools area)
The RigWork panel opens. If your presets are loaded, you'll see them in the dropdown. If the panel says "no presets found", make sure RigWork is open in the same browser and has at least one preset.
Click any bar in the score to park the cursor there
Pick a preset from the dropdown in the RigWork panel
Click Tag this bar

The bar is now tagged. A list of all tagged bars appears in the RigWork panel. Repeat for each section change in the song.

Playing Back

Once bars are tagged, hit play in Riffwork. As the playhead crosses each tagged bar, Riffwork fires the assigned preset - sending MIDI CC values and PCs to all connected outputs, exactly as if you'd tapped the preset in RigWork directly.

A toast notification in Riffwork shows which preset fired: "RigWork: Verse Clean", etc.

Managing Tags

The RigWork panel in Riffwork shows all bar→preset assignments for the current song. Each entry has a ✕ button to remove the tag. Tags are stored per-song in your browser - they persist across sessions as long as you're using the same browser on the same device.

Tags are stored in browser localStorage tied to Riffwork's song ID, not inside the .gp file. If you reload the same song from a different location, the tag IDs may not match. Export the .rig.json from RigWork to back up preset data, and re-tag bars if you switch machines.

Typical Practice Workflow

Learning a set with tab + live rig

1. Build presets in RigWork (one per song section).

2. Open the song's Guitar Pro tab in Riffwork.

3. Tag bars in Riffwork at each section change.

4. Hit play in Riffwork. Your board changes automatically at each section, exactly as it would on stage.

5. Play along - no tab-switching, no preset-hunting, no hands off the guitar.

MIDI Routing in the Bridge

When Riffwork fires a preset through the bridge, it sends:

CC messages for each device in the preset (on that device's channel)
PC messages for each device in the preset (on that device's channel)

This is identical to firing the preset directly in RigWork. The MIDI goes to all outputs that were connected when Riffwork's MIDI was last initialized. Connect MIDI in Riffwork the same way you do in RigWork - click the MIDI button in the Riffwork toolbar.

← Back to Manual