ScoreBraid
ScoreBraid / Product overview
Editing, sound design and interactive playback in one score. Browse the tools, see the actual editors, and check what stays controllable when the project reaches Unreal.
Search feature descriptions and common terms, including controller, keyboard, buses, sends and recording. Category filters still apply.
Try a feature name or a shorter search. No result does not establish whether the software supports it.
Ask about a feature ↗Define a musical state with its own region, track selection, levels, pan and switch timing.
Scene isolation is a separate editing view. Scene playback and isolated editing are not the same operation.
Set repeat rules for regions inside a scene, independently of the scene mix.
The supplied inspector shows the available condition controls. Its example has no game parameter assigned.
Organise additional parts into named layers and choose how they become active.
The panel identifies activation in the app and Unreal. These are musical variation layers, not the recorded takes used when comparing performances.
Write a separate one-shot composition to connect two scenes rather than relying only on a crossfade.
A transition point is the handoff to the destination scene. A stinger’s impact point instead aligns an accent over the running score.
Trigger a short musical event over the score, with an authored impact point and variation settings.
Relearn a ducking profile after changing the sound. The curve is prepared ahead of time, not inferred afresh from gameplay on every trigger.
Arrange WAV and MIDI parts on a musical timeline, then edit notes and velocity in the docked piano roll.
Recording quantisation and piano-roll editing settings are separate. Quantisation is an explicit musical edit, not an automatic change to every imported performance.
Edit a selected waveform inside the project instead of moving to a separate audio-editing application.
The docked editor writes new WAV versions while preserving the original media. Drawn clip-gain curves are committed to the audio; they are distinct from parameter-automation lanes.
Connect a MIDI controller or keyboard and play instruments directly inside ScoreBraid. You can audition a sound without recording a take.
The device must be available to ScoreBraid on Windows. Live MIDI input, recording arm and hardware control mapping are separate settings. Sonic MIDI Learn is described separately; controller input does not imply universal control-surface support.
Record a MIDI keyboard or controller performance directly into armed tracks, then edit the notes and velocity in the piano roll.
MIDI overdub, replace, record quantisation and swing affect MIDI, not recorded audio. Monitoring and recording arm are independent. A recorded performance is separate from the Part Layers activation rules.
Record audio directly into ScoreBraid from a supported recording input. Capture a microphone or other audio source as WAV clips in the arrangement.
Audio takes are additive. MIDI overdub/replace settings do not replace an audio take. The documented capture path uses Windows WASAPI recording endpoints; ASIO output support does not imply direct ASIO input capture. Available inputs depend on the device, driver and app build.
Hear a live audio input through the track mixer and effects, and check its input level before or during recording.
Input gain affects the live monitored signal and newly recorded samples, not existing clips. Monitoring latency depends on the device, buffer and processing. Enabling monitoring and recording at the same time is optional, not required.
Focus the editor on one scene’s parts and mix, then return to the full arrangement.
This is a focused authoring view, not an additional scene-launching mode. The supplied capture shows an isolated scene in the demo project.
Find project and shared material, preview it, and bring it into the score.
Library audition is a desktop authoring workflow. It is separate from the musical states and parameters the Unreal project receives.
Continue a composition from your DAW, or bring in MIDI files and WAV stems. Keep using the import route supported by your source project and beta build.
Project import does not guarantee a complete session clone. Instrument formats, presets, routing, effects and automation may need review. MIDI files do not include the original instrument sound. Check compatibility for the release you use.
Create a synth patch in ScoreBraid and retain supported sound controls in Unreal.
Saved Sonic presets carry macro values, names and mappings. A game binding and a hardware MIDI mapping serve different purposes; do not assume every sampler control has MIDI Learn.
Build drum kits and playable instruments from samples, then use their supported controls in Unreal.
The documented sampler loads sample data into memory. Its Tape speed control changes pitch and duration together. It is not the pitch-preserving WAV time-stretch path.
Add effects to audio and instrument tracks. Use an insert to process the track signal in sequence, with a wet/dry blend for each effect.
Built-in reverbs and their supported game bindings can remain live in Unreal. VST3 processing follows the render/freeze export path. Track inserts and auxiliary sends are distinct routes; not every master-rack option matches a regular track.
Use buses to group processing and share an effects return between tracks. A bus has its own level, pan, mute, solo, meters and effect chain.
The documented auxiliary-send path takes a post-fader copy while the source keeps its dry path to the master. Bus-to-bus sends are disabled. Built-in bus effects can remain live in Unreal; a bus using VST3 effects is rendered as a separate return WAV.
Use send effects for parallel processing rather than placing every effect in the main signal path. Track-local sends and shared auxiliary buses serve different purposes.
A local effect send stays on its source track. An auxiliary send feeds a separate bus and is post-fader in the documented routing. For a VST3 reverb or delay used as a send, its own mix should be fully wet. VST3 effects are rendered for Unreal, not hosted as runtime plug-ins.
Use supported VST3 audio effects while authoring. ScoreBraid prepares their processed audio when you export the score for Unreal.
The editable authoring project is retained. Frozen tracks have restrictions on live bindings and per-part scene states. Third-party VST3 effects do not run inside Unreal; external sidechains and VST2 effects are not supported by the documented effect path. Long or infinite effect tails still need listening checks.
Compose with supported VST3 instruments, then let ScoreBraid prepare their audio for Unreal.
Reuse requires matching MIDI and sound-affecting state, not simply the same notes. Third-party VST3 instruments and effects do not run as plug-ins inside Unreal.
Author tempo changes across the arrangement and control musical tempo from a game value.
Pitch-preserving WAV behaviour requires a supporting plugin and playback mode. Large stretch ratios need listening checks. The screenshot shows multiple BPM points with rising and falling tempo segments.
Draw control changes over musical time or record supported parameter movements.
Built-in synth, sampler and reverb automation can remain live in Unreal. VST3 and general track/send/filter automation follow the documented render path. Automation is not a universal registry for all controls, and its export restrictions still apply.
Map named game values to the musical controls they should affect.
Preview availability depends on the target. The binding notes identify tempo and custom MetaSound controls as requiring Unreal for auditioning. Live response-curve edits need a supporting plugin version.
Map a physical controller knob to a Sonic synth control or macro. Use hardware controls while you audition and shape the sound.
The documented Sonic mapping system accepts absolute 7-bit MIDI CC messages and saves assignments for the Windows user. Relative encoders and paired 14-bit CC messages are not included in that mapping path. Sampler MIDI Learn is not documented as available; its gameplay bindings are a separate feature.
Pair ScoreBraid with a running Unreal game to audition supported performance edits in context.
This does not cover arbitrary structural changes. Sample replacement, VST changes and structural edits require export and reimport. The link is for supported performance edits, not a substitute for saving updated game assets.
Export a .scorebraidbundle and import the score and media through the Unreal plugin.
The plugin and music assets still need to be packaged. Runtime cost depends on voices, processing, media and hardware. Test the score in the game; desktop screenshots are not runtime performance measurements.
16 editor views
Closed beta / Limited places
Apply with your project and workflow details. Selected testers receive access to the app and plugin.