Help

How .bforge projects preserve edits and recover source audio

A Backbeat Forge project is a working document, not a preference file. The versioned .bforge format keeps the editable score, analysis choices, mixer, source identity, and workspace state together for later review.

Save the full working state

Choose Save project after transcription or MIDI import. The project records score events and their kit piece, timing, velocity, articulation, and confidence; detection sensitivity and written grid; source metadata and fingerprint; mixer volume, mute, solo, and master gain; and the current workspace state. Recent score and mixer edits are flushed before serialization so a delayed UI update is not silently lost.

Use Save project to update the current file, or the save shortcut described by the app when you need a new location. Keep the .bforge extension so Backbeat Forge can validate the product and schema version when reopening it.

Reopen a project

Choose Open project and select the .bforge file. Backbeat Forge restores the score first, then tries to reconnect the original audio evidence. A valid source lets playback and the stem mixer return with the saved controls. The project does not need to rerun drum detection simply to display the saved score.

When the source moved

The project stores source identity information rather than trusting a path blindly. If the audio is missing, the saved score still opens and the app reports a source warning. If a file exists at the old or relative path but its fingerprint no longer matches, Backbeat Forge does not attach the changed audio as if it were the original recording.

Move a project and its source together when possible. If you intentionally replace the recording, open the new source and verify the score relationship before saving a fresh project state.

Bundled stem evidence

When the project contains separated stem assets, reopening can rebuild the playback mixer from the saved material. If bundled model resources are unavailable or a saved stem cannot be rebuilt, the score and mixer controls remain recoverable and the warning explains what playback evidence is missing.

Test recovery before depending on the project

After the first meaningful edit, save the project, close it, and reopen it while the source is still available. Confirm one ordinary groove, one manual correction, the current playhead, and a mixer setting. This small recovery test finds path or permission problems before hours of review depend on a file that has never been reopened.

Recovery state	Safe interpretation	Next action
Source fingerprint matches	Score and playback refer to the reviewed recording	Continue and save normally
Source path changed but identity matches	Recording moved without changing	Reconnect and verify a known passage
File exists but fingerprint differs	A different recording occupies the path	Do not attach it automatically
Source is unavailable	Saved score remains viewable	Restore evidence before audio-based claims

When moving work between machines, copy the .bforge project and its original source together. Keep filenames stable, but rely on the identity check rather than the name alone. Do not overwrite the only project while testing a replacement recording; save a new project after the relationship has been reviewed.

Use a simple revision convention for important sessions and keep at least one earlier state before large timing or mapping changes. A project that opens successfully can still contain the wrong musical revision, so spot-check a known manual edit and the ending rather than relying only on the title or modification date.

Does a missing source erase score edits?

No. The score can reopen independently so the work is not discarded. Playback and stem evidence may remain limited because the app refuses to invent a connection to unrelated audio.

What should be archived for a reproducible handoff?

Archive the project, the matching source recording, and the exported delivery files. Record the application version when a long-lived case matters. A PDF documents the written result, but only the project retains editable events, analysis settings, source identity, and mixer state for later review.

For normal creation steps, see Quick start. For warning recovery, see Troubleshooting. Install the current build from Download.

Direct answer and acceptance boundary

For “How .bforge projects preserve edits and recover source audio”, the short answer is: A Backbeat Forge project is a working document, not a preference file. The versioned .bforge format keeps the editable score, analysis choices, mixer, source identity, and workspace state together for later review. Treat that statement as a result to verify, not as a promise that every input, device, project, or environment behaves identically. A complete result records the starting state, the exact action, the visible output, and the condition that proves the task is finished in Backbeat Forge.

Evidence-first operating procedure

Work from a small, repeatable case before changing a full project. Record the application version, operating system, input or device identity, relevant settings, and the expected result. Perform one deliberate action, preserve the first unexpected transition, and compare it with a known-good run whenever one is available. Changing several controls at once may hide which condition fixed or created the problem.

Checkpoint 1: How .bforge projects preserve edits and recover source audio

Treat “How .bforge projects preserve edits and recover source audio” as a separate acceptance gate for “How .bforge projects preserve edits and recover source audio”. Record its initial state before acting, then capture the first visible change and the final state. If the result differs from the page’s stated outcome, return to the last confirmed checkpoint instead of continuing with assumptions.

Checkpoint 2: A Backbeat Forge project is a working document, not a preference file. The versioned .bfor

Verify “A Backbeat Forge project is a working document, not a preference file. The versioned .bforge format keeps the editable score, analysis choices, mixer,” with the smallest representative input. Keep unrelated settings unchanged, repeat the same action once, and note whether the result is stable after reopening or reconnecting. A screenshot alone is weaker than a record that includes the input, setting, action, output, and time.

Checkpoint 3: Save the full working state

For “Save the full working state”, distinguish a product decision from an operating-system, hardware, source-file, permission, or workflow boundary. Confirm which layer supplied the evidence before assigning a cause. This prevents a nearby symptom from being reported as a proven root cause.

Checkpoint 4: Reopen a project

Use “Reopen a project” to define a pass/fail statement that another operator can repeat. Include what should be present, what must be absent, and what recovery action is safe if the check fails. Keep the original project or capture unchanged until the repaired copy has passed the same check.

Checkpoint 5: When the source moved

When “When the source moved” is ambiguous, compare one known-good case with one failing case under matching conditions. Mark the first meaningful difference rather than listing every later symptom. That first boundary usually produces a clearer support request and a safer next experiment.

Checkpoint 6: Bundled stem evidence

Close “Bundled stem evidence” only after the saved, exported, or reopened result still matches the observed state. Temporary UI feedback is useful, but durable evidence is stronger. Record any limitation that remains so the next reader does not interpret an incomplete path as a successful one.

Checkpoint 7: Test recovery before depending on the project

Treat “Test recovery before depending on the project” as a separate acceptance gate for “How .bforge projects preserve edits and recover source audio”. Record its initial state before acting, then capture the first visible change and the final state. If the result differs from the page’s stated outcome, return to the last confirmed checkpoint instead of continuing with assumptions.

Checkpoint 8: Does a missing source erase score edits?

Verify “Does a missing source erase score edits?” with the smallest representative input. Keep unrelated settings unchanged, repeat the same action once, and note whether the result is stable after reopening or reconnecting. A screenshot alone is weaker than a record that includes the input, setting, action, output, and time.

Checkpoint 9: What should be archived for a reproducible handoff?

For “What should be archived for a reproducible handoff?”, distinguish a product decision from an operating-system, hardware, source-file, permission, or workflow boundary. Confirm which layer supplied the evidence before assigning a cause. This prevents a nearby symptom from being reported as a proven root cause.

Checkpoint 10: A Backbeat Forge project is a working document, not a preference file.

Use “A Backbeat Forge project is a working document, not a preference file.” to define a pass/fail statement that another operator can repeat. Include what should be present, what must be absent, and what recovery action is safe if the check fails. Keep the original project or capture unchanged until the repaired copy has passed the same check.

Acceptance matrix

Checkpoint	Evidence to retain	Pass condition
How .bforge projects preserve edits and recover source audio	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome
A Backbeat Forge project is a working document, not a preference file. The versioned .bforge format keeps the editable s	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome
Save the full working state	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome
Reopen a project	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome
When the source moved	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome
Bundled stem evidence	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome

Failure isolation, recovery, and handoff

If a check fails, stop at the first failed boundary. Preserve the source, project, session, or capture; duplicate it before destructive editing; and change one variable per experiment. Repeating a broad workflow after several simultaneous changes may produce a different result without explaining why.

Separate absence of evidence from evidence of absence. A blank view may mean the wrong input, scope, filter, permission, device, time range, or project state rather than “nothing happened.” Verify the acquisition or import path before interpreting a decoder, editor, report, or export.

Before handoff, reopen the durable artifact and inspect its beginning, the decision point, and its end. Record version, platform, relevant configuration, expected behavior, observed behavior, and the smallest reproduction. Remove or redact sensitive material and confirm the recipient is authorized to receive it.

Questions and answers

What is the fastest reliable way to start?

Use the smallest representative case, write down the expected result, and change one variable. Confirm the basic path before adding filters, effects, edits, automation, or a larger source. This creates a baseline that can be compared after every later decision.

What evidence should be saved?

Keep the input identity, application version, platform, relevant settings, exact action, first unexpected transition, and final output. If the workflow creates a project, session, report, or export, close and reopen it before treating it as durable evidence.

When should the procedure be repeated?

Repeat it after an application, operating-system, driver, firmware, model, source, or workflow change that can alter the result. Preserve the earlier accepted case so the comparison uses the same acceptance boundary rather than memory.

When is the task ready for handoff?

It is ready when another authorized person can identify the input, repeat the action, see the same result, understand any remaining limitation, and open the saved artifact without relying on undocumented local state.

Related guides

Continue with the same-language pages below. They cover adjacent stages without changing the canonical owner of this topic: