From your first note to an exported recipe.

Verified: Create a Tech House Session, hear it and export real audio

Verified in a real browser · 2026-10-12 · fd033e09

Executed in Chromium on the production build: the Tech House Engine producer template, actual Web Audio playback, local project save/reopen, a 2-bar PCM WAV and complete DAW handoff.

1. Open Session (/loop) and expand “Start from a producer template”.
2. Choose “Tech House Engine” and press “Use template”. Confirm the Session heading displays TECH HOUSE ENGINE.
3. Press Global Play in the main transport. Hear the real output, then press Global Stop. The QA browser measured non-silent audio.
4. Press “Save Session”, refresh the page and confirm the same Session reopens. The tested project contains five tracks, one section and 38 note events.
5. Open “Section settings”, set “Section length bars” to 2 and press Enter.
6. Press “Export current section”. Open TECH_HOUSE_ENGINE.wav: 48 kHz, 24-bit, stereo, approximately 5.57 seconds.
7. Open “Project & export” and click “Export full-track handoff”. The tested ZIP contained the master WAV, five layer WAVs, five MIDI files, the editable project, a manifest and README.
8. Use “Export project” if you need a portable editable .soundcode-session.json copy.

Actual output: QA produced real non-silent PCM audio with a sample peak of −3.00 dBFS and a structurally valid 14-file DAW ZIP.

Evidence limits: Verified for this template and shortened two-bar arrangement. Not a certificate of complete true-peak control, external Stem Lab providers, every mix setting, authenticated cloud persistence or producer listening. Screenshots remain pending.

Loop Studio: hear your project together

Build a synchronized loop with up to twelve instrument or sample tracks.

1. Open Loop Studio. Add an instrument and tap steps to place notes.
2. Use Sounds from your project to browse your signed-in cloud projects and add rendered sounds on separate tracks.
3. Play all starts every track on one clock. Mute, Solo, Volume and Pan affect playback immediately.
4. Expand Edit notes to change pitch, timing, duration and velocity.
5. Save loop keeps the current arrangement in this browser. Export project creates a portable backup; use Import take or loop to restore it.
6. Export mix produces a stereo 48 kHz WAV.

Try this: Add a bass part and a piano part, solo each to refine it, then play both together.

Current limits: Loop saving is device-local. Short cloud renders are limited to eight seconds and play at their original speed; automatic tempo stretching and cloud arrangement persistence are not available.

Your first sound

Create a project, choose an instrument, render, and press Play.

1. Open Studio and choose New project. Name it for a track or session.
2. Select an instrument family, then Create sound. This creates an editable recipe.
3. Choose Render preview. Wait for the job to finish and a waveform to appear, then press the audio player’s Play button.
4. Change one macro, render again, and listen. Each accepted edit creates another version.
5. Compare two rendered versions, select your preferred version, Lock sound, then Export bundle if your plan permits source exports.

Try this: Project: Midnight Groove. Family: bass. Direction: “Darker body and shorter tail.”

Current limits: Studio uses your account and the cloud worker. Play Studio is a separate device-local instrument workspace.

Sign in, profile and privacy

An account keeps cloud projects and versions together.

1. Sign in with your email and password, or choose Sign up. If email confirmation is enabled, open the confirmation email before signing in.
2. If no message arrives, check spam and the email spelling. A missing email is a delivery issue; the app cannot confirm that it reached your inbox.
3. Use Reset password, follow the email link, then Account → Set new password.
4. In Account, set your display name, creative role, DAW and comma-separated genres; choose Save profile.
5. Export account data for a JSON copy. Delete account is permanent and requires confirmation and your password.
6. Report issue saves a support report with the current project/version/job context. It does not send a chat message to a support agent.

Try this: Role: producer. DAW: Ableton Live. Genres: Tech House, Indie Dance.

Current limits: Training consent is optional. Never include passwords, API keys or payment details in support text.

Projects and sound creation

Projects group sounds, reference profiles and musical settings.

1. Use the Project selector to reopen a session or New project to create one.
2. Expand Project settings to edit name, BPM, key, notes and sample rate; choose Save.
3. Choose a family and Create sound. Select a sound in the sidebar to load its version history.
4. Archive / restore changes a project’s status. Delete project permanently removes its sounds and references after confirmation.

Try this: 126 BPM, F minor, 48 kHz; notes: “Rolling bass with a short tail.”

Current limits: Project settings and each sound recipe are separate. Check the recipe’s tempo before rendering an existing sound.

Describe, Build, Upload, Record and Combine

Choose a starting point based on what you have available.

1. Describe: create or select a sound, enter a direction, review the proposed changes and accept only what you want.
2. Build: choose an instrument family, create a sound and use macros or Advanced controls without an AI provider.
3. Upload: use Reference audio in Studio for analysis. For audio you intend to play as a sample, use Your samples in Play Studio.
4. Record: opens Play Studio, where you can record, preview and use your own microphone sample.
5. Combine: opens Loop Studio. Add instruments, saved takes, or verified rendered sounds from a cloud project, then play the tracks together.

Try this: Use Build for a bass from synthesis; use Play → Your samples for a recording you want mapped across the keyboard.

Current limits: Reference analysis does not automatically incorporate the reference recording into your sound. Play recipes currently remain separate from cloud SoundSpecs.

Macros and Advanced controls

Macros offer broad changes; Advanced exposes individual recipe settings.

1. Select a version. Move a macro and release it to save an edit; render the new version to hear it.
2. Open Advanced, expand a section, edit a value and leave the field to apply it. Values must stay within the displayed bounds.
3. Attack shapes the beginning; decay and sustain shape the body; release controls the fade.
4. Filter controls change frequency balance. Pitch controls change tuning. Effects change space, repeats or character.
5. Use version history to return to an earlier recipe. Fork creates an independent sound to develop separately.

Try this: Lower a low-pass cutoff to darken a tone. Shorten release to leave more space between hits.

Current limits: Editing a recipe does not automatically render it. Locked versions are protected; fork before developing a locked sound.

Creative direction and proposals

Read the provider status, describe one change, and review it before accepting.

1. Select a sound and version before sending a direction.
2. Write the sound change you want. Preserve dimensions protects selected first-layer filter, envelope, pitch or generator settings.
3. Choose Propose. Review the rationale, audible effects and explicit parameter operations.
4. Accept creates a version and requests a render. Dismiss proposal keeps your current version unchanged; it does not record a server-side rejection event.
5. If the screen says local rules, the response comes from bounded local interpretation rather than an external language model.

Try this: “Make it warmer and shorten the tail.” Try one direction at a time and compare by ear.

Current limits: A configured external provider still requires a successful request to prove its connection. Local rules understand a limited vocabulary.

Render, playback and job status

A recipe needs a completed render before the Studio player has audio.

1. Choose Render preview once and watch the status: queued means waiting; running means processing; succeeded means artifacts are available.
2. After a waveform appears, press Play in the player. Enable Loop to repeat the render.
3. After changing a macro or version, render that version before evaluating its sound.
4. If a job fails, retain the job/error identifier and report the issue. Admin can retry eligible failed jobs.
5. If queued never advances, check worker health through the operator; repeated render clicks do not repair an offline worker.

Try this: A player showing 00:00 with no waveform has no playable render yet.

Current limits: If downloaded audio fails after a long session, reselect the rendered version to obtain fresh private artifact links.

Reference upload and analysis

Analyze a permitted recording without automatically adding it to the synthesis.

1. Open a project. Confirm you have permission to use the reference, then choose an analysis focus.
2. Select a supported WAV, AIFF, MP3 or M4A file within the server’s size/duration limits. The default size limit is 4 MiB.
3. Wait for the analysis job. Expand Descriptors to inspect measured results.
4. Select Use profile when rendering with that reference profile. This does not automatically translate every descriptor into sound edits.
5. The reference panel shows whether raw audio was deleted or when deletion is due. Delete removes the raw reference and descriptors after confirmation.

Try this: Choose bass focus for a bass reference; inspect its descriptors, then make a manual brightness or envelope adjustment.

Current limits: The current UI does not yet offer individual rhythm/pitch/envelope extraction checkboxes or a complete reference-to-new-recipe wizard.

A/B, history, variation and locking

Compare rendered versions and preserve the recipe you prefer.

1. Render both versions you want to compare. Select one as the current version A.
2. Choose the other version in Compare with, then use A and B to switch the audio source. Press Play after switching.
3. Expand Parameter differences to inspect changed values. Version history selects previous snapshots.
4. Variations creates controlled alternatives; select and render each before comparing. Favorite and Label mark versions.
5. Fork creates an independent sound. Lock sound protects the selected version and records provenance.

Try this: Compare a warmer version against a brighter one at similar listening volume.

Current limits: Select your preferred history version before locking or exporting; switching the listening slot to B does not select B as the export target.

Studio export and reproducibility

Export the selected locked version with its recipe and provenance.

1. Select the exact version you want and Lock sound.
2. Choose Export bundle. The server checks your entitlement and queues an export.
3. Wait for completion; the download begins through a temporary authorized URL.
4. Keep the bundle, including audio, SoundSpec, manifest, provenance and standalone Python source. The manifest records the engine, seed and hashes.
5. Use the bundle README when reproducing the sound outside SoundCode.
6. Recipe & version data downloads a V2 compatibility envelope with recorded actions and available provenance. This is data, not an audio export.

Try this: Keep an original ZIP beside the WAV you import into your DAW.

Current limits: Paid export requires a configured billing/entitlement path. Provenance records creation history; it does not guarantee copyright or exclusivity.

Library and organization

Find cloud sounds and reopen them in Studio.

1. Open Library. Search by text, filter by asset category or family, or choose Favorites or Locked.
2. Open & preview loads the sound in its project. Render first if the selected version has no audio.
3. Choose Play rendered sound to open the selected render in Play Studio; choose Load rendered sound, then set its root note. This plays the whole phrase as a sample, limited to eight seconds.
4. In Studio, edit comma-separated Tags and Sound notes; these save when you leave the field.
5. Copy to project currently asks for a destination project ID and forks a version into that project.

Try this: Tags: rolling, dark, club. Notes: “Use in the second drop.”

Current limits: Current filters are separate requests rather than a combined filter builder. Play’s device-local takes are stored separately.

Play Studio: piano, organ and transport

Make sound immediately with a keyboard, without a cloud render.

1. Open Play Studio and tap Enable sound & test piano. If muted, tap Unmute and raise your device volume.
2. Choose electric piano, organ, bass, pad, lead, pluck, brass, strings, marimba or flute. Load your own sample to play it across the keyboard.
3. Hold keys for notes, use multiple touches for chords and slide between keys. On desktop use the printed computer-key shortcuts.
4. Use Octave to change register, Brightness to darken or brighten, and Release for the fade after lifting a key.
5. For organ, raise drawbars to mix harmonics. All drawbars at zero produces silence.
6. If silent, check both app and device volume, the chosen output/Bluetooth device, and tap Enable sound again. Reopen after a browser interruption if needed.

Try this: Choose ORGAN; start with the 8′ drawbar and add 4′ for brightness.

Current limits: Piano and organ use browser audio. Studio can send a verified render to Play as a pitched mono sample. Live recreation of the original synth patch is not implemented. Browser activation checks do not certify every phone’s speaker output.

Loops, recording, saved takes and Play exports

Place or record notes, then keep both audio and an editable recipe.

1. Set BPM and a 1-, 2- or 4-bar loop. Tap grid cells to place notes; tap existing notes to edit pitch, beat, duration and velocity or delete them.
2. Use Play loop to listen and Stop to edit. The grid scrolls horizontally on small screens.
3. Record one loop captures keyboard input and keeps existing notes as an overdub. Quantize aligns recording to sixteenth notes.
4. Save take stores it in this browser. A matching name replaces the saved take; use a new name to preserve an alternative. The list retains up to 12 takes.
5. Export WAV produces 48 kHz stereo 24-bit audio. Export MIDI preserves notes/timing; assign an instrument in your DAW.
6. Export Sound Code keeps the instrument settings, notes and included sample data. Reopen it with the file importer or paste its JSON.

Try this: At 126 BPM, add C4 on beat 1, G4 on beat 2.5 and E♭4 on beat 4; play, save as FIRST_GROOVE and export.

Current limits: Browser storage can be cleared or fill up. Export Sound Code as a backup. M4A/MP3 take exports and AI melody generation are not available yet.

Microphone and authorized samples

Preview your audio before using it as an instrument.

1. In Play → Your samples, press Record microphone and allow permission. Recording stops after 7 seconds, or use Stop microphone.
2. Preview the recording, rename it, then Use my recording as source or Discard recording.
3. For an uploaded file, select a rights declaration before choosing audio; use a file up to 8 seconds and 20 MB.
4. Set the sample root note to its original pitch, then play other keyboard notes.
5. Set start/end seconds under Trim loaded sample. Normalize raises its loudest peak and background noise. Apply trim replaces the currently loaded sample.

Try this: Record a short “ah”, preview it, use it as source and set its root note before playing a melody.

Current limits: Pitch mapping changes playback speed and duration. Automatic loop-point detection and extracted rhythm/melody transfer are not yet connected. Audio here stays on the device unless you share an export.

Plans, credits and subscriptions

Credits represent permitted compute usage; the ledger explains changes.

1. Open Billing to inspect your plan, remaining credits and plan entitlements.
2. Choose a paid plan to enter Checkout when Stripe is configured. Do not assume an entitlement changed until the verified payment is reflected in the app.
3. Manage subscription / cancel opens the payment-provider portal when an existing customer is available.
4. Read Usage ledger for reservations, grants and refunds; balance after shows the balance at each entry.

Try this: If a render is blocked for insufficient credits, check the ledger or ask your administrator for demo credits.

Current limits: The deployed payment journey still requires real test-mode acceptance. This guide does not certify that purchases are available.

Admin operations

Authorized admins can inspect operations and perform audited support actions.

1. Open Admin using an authorized admin account. Search users, workspaces, projects or jobs.
2. Inspect metrics and job status/error codes. Retry eligible job queues replacement work and may reserve credits again.
3. Suspend or reactivate an account only after confirming the intended user.
4. Grant credits to the correct workspace and supply an audit reason.
5. Plan limits edits monthly credits and queue priority. These are operational values, not a Stripe price editor.
6. Expand Support, audit and billing records to inspect the current records.

Try this: Audit reason: “Compensating credits for failed render, job …”.

Current limits: The current Operations screen is not the full planned Command CMS: draft/preview/publish/rollback, content management and complete cost analytics remain unfinished.