Home / Docs / For mixing and mastering engineers

For mixing and mastering engineers

This guide shows how mixing and mastering engineers can use Rebounce to organize client work, handle revisions, and keep feedback clear across multiple projects.

Why use Rebounce for client work

Mixing and mastering engineers deal with:

  • Multiple clients with different projects running at once
  • Revision cycles that span weeks or months
  • Timestamped feedback that needs to stay organized per version
  • File handoff that must be clean and traceable
  • Version control ("finalv3_MASTERED.wav" vs. "finalv4_actuallyfinal.wav")

Rebounce solves this by:

  • Organizing all client projects in one workspace
  • Keeping every version in its own timeline
  • Attaching feedback directly to specific timestamps
  • Making it clear which version is final (master designation)
  • Providing download links with proper ID3 tags

Workspace setup for engineers

One workspace for your studio

Create a single workspace for your mixing/mastering business. This workspace will contain all your client projects.

Benefits:

  • All storage and billing happens in one place
  • You control who sees what using private artists
  • Clients don't need to manage their own workspace or pay for storage

Use private artists for each client

When a new client books a session:

  1. Create a private artist with the client's name or project name
  2. Add the client as a collaborator to that private artist only
  3. They'll see only their own tracks — nothing from other clients

This keeps client work isolated. Other workspace members won't see private artists unless you explicitly add them.

Invite clients as workspace members (not track collaborators)

If you work with a client regularly:

  1. Go to workspace settings and invite them as a member
  2. Add them as a collaborator to the specific private artist
  3. They can now see all tracks under that artist, but no one else's work

This is better than per-track invites because:

  • They see all their tracks in one place
  • You don't need to re-invite them for every new track
  • They can upload reference files or stems themselves

Workflow for handling revisions

1. Initial mix or master upload

When you finish the first pass:

  1. Go to the client's artist page
  2. Create a track (or find the existing one)
  3. Upload the audio file as a new version
  4. The client receives a notification

2. Client leaves timestamped feedback

The client plays the track and:

  • Clicks on the waveform to leave a marker comment at a specific timestamp
  • Drags across a region to leave a region comment spanning multiple timestamps
  • Can attach text, emoji reactions, or just flag something for attention

All feedback stays attached to that specific version.

3. You upload the next revision

After addressing notes:

  1. Upload a new version to the same track
  2. Old feedback remains visible on the previous version
  3. New feedback can be added to the new version
  4. You can see which issues were addressed and which carried over

4. Mark the final version as master

Once the client approves:

  1. Click the "Mark as master" button on the final version
  2. This visually indicates the file is release-ready
  3. Clients and collaborators know this is the definitive version

Only workspace owners and admins can mark a version as master.

Managing multiple clients

Naming conventions

Suggested structure:

  • Artist name: Client name or project name (e.g., "Jane Doe", "Sunset Records - Album X")
  • Track name: Song title or deliverable type (e.g., "Track 01 - Intro", "Full Mix", "Mastered Stereo")

This keeps everything scannable when you're juggling multiple projects.

Use workspace members page to see all clients

Go to workspace settings to see a list of all members. This shows:

  • Who's invited
  • What role they have
  • Which private artists they can access (if you've set that up)

Archive completed projects

Rebounce doesn't have an "archive" feature yet, but you can:

  • Delete old versions you no longer need to free up storage
  • Keep the final master version for reference
  • Leave the artist visible so you have a record of past work

Common scenarios

Scenario: You're mixing a single for an independent artist

Setup:

  1. Create a private artist called "Artist Name - Single"
  2. Invite the artist as a workspace member
  3. Add them as a collaborator to the private artist
  4. Create a track called "Song Title - Mix"

Workflow:

  1. Upload your first mix
  2. Artist leaves timestamped feedback
  3. Upload Mix v2 addressing notes
  4. Repeat until approved
  5. Mark the final version as master
  6. Artist downloads the file with ID3 tags already embedded

Scenario: You're mastering an EP with 5 tracks

Setup:

  1. Create a private artist called "Artist Name - EP"
  2. Create 5 tracks, one per song
  3. Invite the artist to the private artist

Workflow:

  1. Upload first pass of all 5 masters
  2. Artist reviews and leaves notes on each track
  3. You address feedback and upload revised masters
  4. Once all tracks are approved, mark each final version as master
  5. Artist downloads all masters in one go from the artist page

Scenario: You work with a producer who sends you multiple artists

Setup:

  1. Invite the producer as a workspace member (role: member)
  2. For each artist they send you, create a private artist
  3. Add the producer as a collaborator to each relevant private artist

Benefit:

  • The producer sees only the artists you've shared with them
  • They don't see your other client work
  • You manage storage and billing centrally

Scenario: A client wants to share work-in-progress with their label

Your client is a workspace member with access to their private artist. They want to share a specific track with their label A&R.

What they can do:

  1. Go to the track page
  2. Click "Share"
  3. Enter the A&R's email
  4. Choose role: viewer, commenter, or editor

Result:

  • The A&R receives a track invite (not a workspace invite)
  • They can see only that one track
  • Feedback from the A&R appears alongside your notes

Collaboration and feedback

Viewing feedback summaries

After a bounce is uploaded, Rebounce generates an AI summary of all comments left on the previous version. This helps you quickly see what changed without reading every note.

Seeing who listened to each version

Rebounce tracks who played each version. You can see if your client has actually listened to the latest revision yet.

Downloading files

When clients download a version, the file includes:

  • Properly formatted ID3 tags
  • Original audio quality
  • Filename based on track and artist metadata

This ensures the file is ready for distribution or archival.

Billing and storage

You pay for storage, not your clients

Your workspace subscription covers all storage. Clients don't need to pay unless they create their own separate workspace.

Plans:

  • Free: 3 active tracks, 1 GB storage, 2 artists (good for trying it out)
  • Creator: $10/month, 100 GB storage, unlimited tracks and artists (covers most engineers)

Storage is shared across all artists and tracks in your workspace.

Tracking storage usage

Go to workspace settings → billing to see:

  • Total storage used
  • Storage available on your plan
  • How much space each artist is using

If you're running low, delete old versions or upgrade to a larger plan.

Passing costs through to clients

Rebounce doesn't have built-in client billing. If you want to charge clients for storage or project management, include it in your session fee or invoice them separately.

Tips for staying organized

Keep each project as a separate private artist

Don't lump all clients into one artist. Use a private artist per client or per project. This makes permissions and organization much cleaner.

Upload reference files as versions

If your client sends reference tracks or stems, upload those as versions too. That way everything is in one timeline.

Use comments to track decisions

Leave notes for yourself or the client about why you made certain decisions. Comments are timestamped and searchable.

Check notifications

Rebounce notifies you when:

  • A client uploads a new version
  • A client leaves feedback
  • A client responds to your comment

Turn on email or push notifications so you don't miss anything.

What's next

This guide covers the essentials for mixing and mastering engineers. If you run into issues or want to request features, reach out to the Rebounce team.

Recommended reading:

  • Workspaces — understand roles, permissions, and billing
  • Tracks — learn how to share tracks and manage collaborators
  • Versions — deep dive into version history and master designation