Best way to send my bass track to others for them to mix/master/engineer?

Hello all,

My current process is I am recording my bass into my DAW to send off to others for their projects.

My question is what is the best way to send my bass track to others for them to mix/master/engineer?

I am using StudioOne as my DAW, should i export a mixdown to send to my collaborators or stems? and what formats etc. should i be using?

TIA!
 
I do a lot of my studio work this way lately (and especially so this past year!) and generally clients/producers want a single 24-bit WAV file at either 44.1 or 48kHz (occasionally 96kHz, surprisingly never at 192kHz). No plug-ins, no stems, and no "it has to start on beat 3 of measure 27" crap. Just send them a single track that starts at timestamp 0:00:00:000 and runs until the end of the song, with all your sound baked in. On very rare occasions -- emphasis on "very" -- they'll ask for a separate DI and mic'd amp tracks, but usually they want me to choose the blend.

And they all want it sent via DropBox.
 
Last edited:
Good advice from @Bob_Ross. As an engineer I would differ and say that if there are separate DI and mic tracks to send me both, not a mixdown of the two but every engineer is different. Your best bet is to speak to your engineer in advance and see what they want.

Additionally, don’t send a stereo file if the source is mono, even if it’s a stereo file where both left and right are identical. We engineers want mono files for mono sources and bass is almost always mono.

Lastly, understand proper gain staging. If you’re recording with leaks hotter than -6dbfs you’re probably recording too hot. You’re not technically too hot if there’s no clipping, but if you keep the loudest peaks to -6dbfs you’ll almost certainly have a happy engineer on the receiving end.
 
ONE PRODUCERS GUIDE TO DELIVERING MULTITRACK FILES FOR MIXING:

1) Print your tracks DRY without any reverb, delay, etc. Insert effects (other than reverb/delay) that are a part of the sound should be printed, such as amp simulators, chorus, distortion, filters, etc. If compression and EQ are extreme and part of the sound, then print it – if it’s just to get the sound to fit in your rough mix, please do not print it. Remember to turn off reverb and delay effects on VST instruments BEFORE printing them.

2) Do all of your editing including vocal comps, copying choruses, auto-tuning, trimming up space before and after takes, etc.

3) CONSOLIDTAE all your tracks. Please consult your DAW manual and there are plenty of youtube videos on this topic. There are also instructions for most DAWs at the end of this document. All tracks should be bounced from the exact same starting point. Please attempt to keep stereo tracks stereo and mono tracks mono if your software allows it.

4) Properly label your tracks! Don’t send me ‘track1.wav’, ‘track2.wav’. Label tracks appropriately like, ‘piano’, ‘snare’, ‘chorus vox hi’, ‘V. bkgnd vox’, ‘intro talk’, etc. so I don’t waste your time trying to figure out what is what.

5) Preferred format is WAV or Broadcast WAV, 24bits, 44.1kHz. If you tracked your song at only 16 bits, then keep it at 16 bits – do not convert. If you tracked your song at 48kHz, then keep it at 48kHz. I do not recommend 88.2 or 96kHz without discussing it with me first. Do not send AIFF files unless you have to. Do not send outdated and problematic formats like SD2.

6) Please include the following when delivering your tracks: A) the consolidated files. B) rough mix if you have one. C) A *.txt file with notes including the file format for the tracks, tempo, name and contact info for the engineer and/or producer, and anything else such as what was used to record, problem areas, ideas, influences, etc. The more info the better!! D) lyric sheet (with words to be censored for clean versions highlighted).

7) ZIP all your files and upload them using www.wetransfer.com (or a similar service) t

If ANY of this is confusing at all, PLEASE CALL ME AND ASK! Do not take chances with little mistakes that could cause massive delay; play it safe and ask. There is no such thing as a stupid question; there are only stupid people who refuse to ask questions!

I like to spend all of my time making your mix as good as possible. Following the above guidelines ensures that. The more you deviate from these guidelines, or make mistakes because you didn’t ask for clarification, means I have to spend your mix time fixing stuff or making it compatible instead of actually mixing. So it’s in your best interests to follow the above guidelines.


HOW TO CONSOLIDATE AUDIO FILES IN MOST DAW PROGRAMS:

Please consult your DAW instruction manual for information on how to consolidate your audio files. There are also plenty of youtube videos that demonstrate the process for your particular DAW software.

The following are instructions for how to consolidate files in DAWs. These instructions were generated by people who have used these programs. I do not have first-hand experience with most of these programs, but I have yet to encounter someone complaining that these instructions did not work. However, best practice is always to consult your software instruction manual.

Please select Broadcast Wav or Wav if your software gives you a choice of file formats. Do not send “acidized” files. After consolidating the files, please put them in a ZIP folder and either upload them to me or burn them to a CD or DVD (if using a Mac, make sure it can be opened on a PC!!!!).


Consolidating regions in Pro Tools HD, LE, and M-Powered:
On the Mac -
1. Ensure that the audio tracks are all clearly named.
2. Highlight all the audio in the Edit Window, making sure you've successfully selected before the beginning of the early-most region and after the end of the last-most region.
3. Press and hold Option and Shift, and while pressing them, press "3" (the one above the QWERTY keyboard, not the numeric keypad).
Alternatively, you could select "Consolidate Selection" from the Edit pull-down menu.
4. To export these new files, highlight them all to select them, and press Command + Shift + "K".
Alternatively, you could select "Export Selected as Files" from the Audio Regions List pull-down menu.
Remember to export them as 24-bit wav or broadcast wav files, using the "(Multiple) Mono" format.

On the PC -
1. Ensure that the audio tracks are all clearly named.
2. Highlight all the audio in the Edit Window, making sure you've successfully selected before the beginning of the early-most region and after the end of the last-most region.
3. Press and hold Alt and Shift, and while pressing them, press "3" (the one above the QWERTY keyboard, not the numeric keypad).
Alternatively, you could select "Consolidate Selection" from the Edit pull-down menu.
4. To export these new files, highlight them all to select them, and press CNTRL + Shift + "K".
Alternatively, you could select "Export Selected as Files" from the Audio Regions List pull-down menu.
Remember to export them as 24-bit wav or broadcast wav files, using the "(Multiple) Mono" format.


Consolidating regions in Logic:
From the Arrange page choose File > Export > All Tracks As Audio Files
Remember to export them as 24-bit wav or broadcast wav.


Consolidating regions in Cubase/Nuendo:
1. Select the Range Tool, and highlight all tracks from 0:00:00.000 through to the very end of the very last region.
2. From the Audio menu, select Bounce and Replace Events.
3. From the File menu, select "Save Project to New Folder" or "Backup Project", and all the new consolidated files will be available in that new project's Audio Files folder. Just be sure to check the box labelled "Remove Unused Media" to ensure only the consolidated files appear in the Audio Files folder.


Consolidating regions in Sonar:
1. Highlight all clips in the first track, right click, and select "Bounce to Clip".
2. Highlight all clips in the second track, right click, and select "Bounce to Clip".
3. Repeat these steps for the remaining tracks.
4. Once all clips have been consolidated, click File > Export > Audio
5. Set audio to export as 24-bit RAW Broadcast Wave Files. Be sure not to use "Fast Bounce".


Consolidating regions in Garage Band:
1. Disable all automation, plugins, etc.
2. Solo the first track, and select "Export Song to Disk" from the Share pull-down menu.
3. In the subsequent dialog box, make sure that the Compress box is left unchecked, click Export, and name the file according to the solo'd track's contents.
4. Solo the second track, and select "Export Song to Disk" from the Share pull-down menu.
5. In the subsequent dialog box, make sure that the Compress box is left unchecked, click Export, and name the file according to the solo'd track's contents.
6. Repeat the steps for the remaining tracks.


Consolidating regions in Digital Performer:
1. Put a piece of audio at 0:00:00.000 on every track.
2. Select all the audio in all the tracks, and be sure.
3. Select Merge Soundbites from the Audio pull-down menu.
Note that this will create new files, which can be retrieved from the Audio Files folder. Just sort the files by Date Created so that they are grouped together.
Alternatively, after merging the soundbites, you could go into the Soundbites Palette and select the merged tracks to be exported, then choose "Export Soundbites" from the palette's mini-menu. This will bring up a dialog from which you can select the desired format, resolution, and destination. Remember to export them as 24-bit wav or broadcast wav files.


Consolidating regions in Reason:
Simple Method (yields lower quality audio):
1. Set start marker to Bar 1.
2. Set end marker to the end of the song.
3. Turn off all effects on the mixer, as well as any effects modules you may be using (reverbs, delays, etc) and set all levels to unity gain. Just make sure none of the channels are clipping. If they are, turn the fader down on that channel, or turn down the output of the module feeding that channel.
4. Solo the first track, preferably using the sequencer, not the mixer.
5. From the File menu, select "Export Loop As Audio File".
6. Choose the export format. Remember, use 24-bit wav or broadcast wav.
7. Click "Save".
8. Repeat these steps for each track.

Advanced Method (yields higher quality audio):
If you have a compatible host DAW, it's best to use the ReWire protocol to pipe the Reason tracks into the host DAW. This will bypass the Reason 14:2 mixer, yielding higher quality audio. Be sure to bypass any effects, and record the audio into DAW. Then just Export the new audio files from the DAW.


Consolidating regions in Reaper:
1. Highlight from 0:00:00.000 to just past the end of the song.
2. Solo the first track.
3. From the File Menu, select "Render".
4. Un-solo the first track, and solo the second track.
5. From the File Menu, select "Render".
6. Repeat this with every track until all tracks have been rendered.
Once you've rendered all tracks, you can select them from the Audio Files folder; I recommend copying them to a new folder for ease of transfer.


Consolidating regions in Fruity Loops:
1. Split all the instruments or sounds onto their own mixer channels.
2. Name each channel according to the sound it's playing back and bypass effects inserts on each channel and the master channel.
3. Put the file in SONG MODE.
4. Clear any region set in the playlist.
5. From the File menu, select "Export"
6. Ensure "Split Mixer Tracks" selected and "save Acidized" is NOT selected, then export as wav or aif files.
WARNING: DO NOT SEND "ACIDIZED" FILES! Make sure "save Acidized" is NOT checked.
Naming the base file "[the name of your song]" will help to organize the exported files by grouping them by your song's title. For example, the Drums track would be called "[the name of your song] Drums", the Bass would be called "[the name of your song] Bass, etc.


Consolidating regions in Audacity:
1. Name all your tracks.
2. Select "Export Multiple" from the File pull-down menu.
3. Set Export Format to WAV, Split files based on Tracks, and Name files Using Label/Track Name.
 
Last edited:
A couple of clarifications on items that could go poorly on your session if not discussed with the engineer beforehand.

2) Do all of your editing including vocal comps, copying choruses, auto-tuning, trimming up space before and after takes, etc.
Don't do this without speaking to your engineer first. This is potentially very dangerous advice as comping done by an inexperienced person playing engineer can result in all sorts of problems. At the very least, if you're going to comp and edit yourself, create a copy and send both the comped version and a properly indexed version of the unedited files as well. Nothing screws up a performance faster than a poorly cut part that results in an audible pop because the person doing the editing before sending it to the engineer didn't know how to properly implement a crossfade.

5) Preferred format is WAV or Broadcast WAV, 24bits, 44.1kHz. If you tracked your song at only 16 bits, then keep it at 16 bits – do not convert. If you tracked your song at 48kHz, then keep it at 48kHz. I do not recommend 88.2 or 96kHz without discussing it with me first. Do not send AIFF files unless you have to. Do not send outdated and problematic formats like SD2.
Generally good advice, but discuss it with the engineer first. A good example of this is when people are recording music that relies heavily on synthesis or VST instruments. I will often encourage people in those settings to record at 88.1 or 96 to avoid aliasing from foldback as lots of these virtual instruments and ITB synthesis have a tendency to try and generate content above Nyquist. Additionally, if there are other people recording separately be sure that everyone is using the same sample rate and file format.
 
A couple of clarifications on items that could go poorly on your session if not discussed with the engineer beforehand.
@silky smoove . You are right. Always discuss with your team.

The list I posted was from my cousin's website. He mixes and produces a lot of stuff and those are his particular parameters. I thought it was interesting and give people and idea of what they might expect.
 
  • Like
Reactions: One Way
@silky smoove . You are right. Always discuss with your team.

The list I posted was from my cousin's website. He mixes and produces a lot of stuff and those are his particular parameters. I thought it was interesting and give people and idea of what they might expect.
Right, and the key distinction here is that every engineer is particular. If I were hired as the engineer I would regard the items from your cousin’s list to be subjectively bad advice in many situations. If that’s how he chooses to work and it works well for him, then good for him. If I were given files with bad edits/comps that I couldn’t fix and didn’t have the unedited files to go back to I’d have to tell the client to try again on the edits or send me an unedited file both of which would eat into their session budget. If I got files with a ton of aliasing from VSTs and plugins that were printed at 44.1 while they tried to create content above Nyquist it would make for a more challenging mix. In the case of heavily aliased VSTs there might be nothing possible to resolve the inharmonicity of the foldback short of massively low passing to cut it out which results in a dull and lifeless top end.

Moral of the story: If you’re working with an engineer, ask them what they want and how they want it delivered. However that particular engineer answers is the correct method for that particular project but not necessarily for any other project including subsequent ones with the same engineer.
 
  • Like
Reactions: One Way
Right, and the key distinction here is that every engineer is particular. If I were hired as the engineer I would regard the items from your cousin’s list to be subjectively bad advice in many situations. If that’s how he chooses to work and it works well for him, then good for him. If I were given files with bad edits/comps that I couldn’t fix and didn’t have the unedited files to go back to I’d have to tell the client to try again on the edits or send me an unedited file both of which would eat into their session budget. If I got files with a ton of aliasing from VSTs and plugins that were printed at 44.1 while they tried to create content above Nyquist it would make for a more challenging mix. In the case of heavily aliased VSTs there might be nothing possible to resolve the inharmonicity of the foldback short of massively low passing to cut it out which results in a dull and lifeless top end.

Moral of the story: If you’re working with an engineer, ask them what they want and how they want it delivered. However that particular engineer answers is the correct method for that particular project but not necessarily for any other project including subsequent ones with the same engineer.
Like you say, each person has their own work flow. What works well for person A may not work for person B. All I know is he is pretty busy, in demand and does ok. He isn't a hack.

I offered his list as an example of what a producer/editor might want. YMMV.
 
  • Like
Reactions: One Way
Definitely a tangent ahead! And one, forgive me OP, that drags this train off the rails a lil bit.

Funny @Bob_Ross mentions the sample rate... it really does seem like we've hit a practical plateau for nearly all pop & commercial music formats: 24-bit, 96kHz.

Big-budget classical orchestral recordings may use massively multitracked 32-bit floating-point resolution and 196kHz sample rate, because they're done in high-tech environments similar to where blockbuster film scores are recorded (or identical to them). Insanely low noise floors, crystal-clear response and clarity from the first violins, high percussion, piccolos, etc, and headroom for million-dollar studio effects processing.

That sounds exactly like what we need for bass double-tracked thru DI and a mic'd cab, right? :smug: As far as a lot of bass goes, we could theoretically get away with recording at 22.05kHz, which would functionally only capture frequencies up to ~11kHz. Marcus Miller might need 48kHz for his fresh zingy string pops, but most of us don't need it.


This is all academic, though. Personally, I record 24/96 because I recently built a system loaded with CPU headroom and HDD space, and don't feel like switching the settings per instrument. 24/48 would be absolutely fine for professional bass tracks, though.

As for editing...if it's a serious gig, I'll make a duplicate session file where I edit down to taste (I'm good at it and very comfortable & confident in my work), but make it known the unedited multitrack stems are available if wanted/needed.


The actually useful info about communicating with the client or engineer, that's all covered above.
 
  • Like
Reactions: One Way