All DAW programs have a ‘bounce’ feature available to create a stereo or multi-channel mix of your current multi-track project.
In Digital Performer, this ‘bounce’ process occurs offline, and usually happens faster than real time.
What this means is that if you have a 2 minute sequence, and you bounce to disk, it takes less than 2 minutes [usually] to create that bounce audio file.
But many times the resulting ‘bounce’ file contains errors.
It simply does not sound like the mix you’ve been working on for the past week!
Automation nodes get cut off, or CC data curves controlling VI parameters get inaccurately rendered. Maybe it’s a midi data bottleneck somewhere, who knows.
These errors do not happen all of the time, or even the majority of the time. But it happens enough that Bounce to Disk is not 100% reliable.
And this is not unique to Digital Performer.
Over the years I’ve experienced the same problems with Logic as well.
So how can you get a bounce that truly sounds like your mix during playback?
Simply do a ‘Real-Time Bounce to Disk’.
This is nothing more than routing all of your audio/VI/aux tracks to a single bus output and then recording that bus output
onto a new audio track.
Here’s how it’s done.
In this example, you can see my Tracks Overview window.
The midi tracks on top and the VIs on the bottom.
There are no audio tracks in this project, but the procedure is the same for audio or VI tracks or aux tracks.
Notice the Track Folders [Project-->Track Folders] for easy viewing:
Step 1: change the output destination of the Virtual Instruments to a single stereo bus.
You can do this one by one, or first select all the VI tracks in the TO window, and then use the Audio Assignments window [Studio-->Audio Assignments] to change them all simultaneously:
After doing this, here’s how things look:
Step 2: Create a stereo audio track.
Name it something useful, like ‘final mixdown’.
Step 3: Set the input for that audio track to the same bus you chose for the VI output. Bus 1-2 in this example
Step 4: set the output of your mixdown track to your main audio output [connected to your speakers for monitoring] so you can hear what is happening during mixdown.
Record enable and input enable the mixdown track.
Step 5: rewind to the start of the sequence. Tap record. Now all of your tracks are being mixed down to a single audio track.
Here’s the finished result:
You can have any number of audio tracks/midi VI sound sources/Aux tracks filled with effects plugins/stems/submixes
and the process for real-time mixdown is exactly the same.
Just route all of them to a single bus, then record the bus onto a dedicated audio track.
I have yet to get a single mixdown ‘error’ when using this method instead of bounce to disk.
Happy mixing!







#1 by bb on February 9, 2010 - 10:27 pm
Quote
Nice site, I just stumbled across it.
#2 by charles on February 10, 2010 - 10:09 am
Quote
Thanks! Good to hear that viewers are liking the site…
#3 by Archie Peay on June 11, 2010 - 12:36 pm
Quote
I believed what you have desribed here is the same as what have done for years via a realtime bounce on my Yamaha 02r via an alternate stereo input (can’t think of the name at this moment). But I have never had a problem with a bounce-to-disk in DP. I running DP6 currently.
However, I just stumbled across the site, and it sounds like you may be able to help me in another matter.
I have a library of old reel-to-reel tapes, which I dumped over to ADATs a few years ago, when ADATs were popular. Way back then, before the ADATs, I would sync DP up with my 8-track reel-to-reel using a Datasync2 device recorded on one of the 8-tracks. When I dumped them over to ADATs, I did a direct track-to-track transfer, which included the sync tone.
Now, I am trying to transfer the tracks from the ADAT (two in some projects), which I am able to do, but I can’t for the life of me, get DP to respond the the track with the sync tone. I consulted MOTU about this, with no successful response.
Here’s my current gear. DP 6.x; 2-ADATxt’s sync’d via the 9-pin cable to my MOTU 424 (upgraded from the 324); Midi Timepiece2; Yamaha 02r with 2 ADAT cards; MTU’s Clockworks (latest version I think)… I have othr gear, but not significant to this.
I can dump the ADAT data via the optical connect, but I cannot get DP to actually sync to the audio sync tone. I have connect the analog output of the ADAT track containing the sync tone to the audio input of the MTP2. I’ve tried all the “Sync to” and “Transmit Syn” options in DP, as well as MMC (midi machine control) settings, etc., but DP’s location counter never moves, and the play indicator of the Master ADAT just flashes.
The object here is to get DP to sync up with the sync tone to follow the ADAT tape bar for bar and tempo as the original sequence.
I guess my main issue here is how to set all of the Clockworks settings. I never really understood Clockworks. There’s icons of all my gear in two columns (left & right). I never understood the difference between the left and right columns.
I hope all of this makes sense to you. I’ve been with MOTU since 1988, but they are practically unreachable now by phone. The online contact is even worst.
Thanks
#4 by paul davies on May 15, 2011 - 2:25 pm
Quote
hi charles
great site, really sorry i’m coming at this post so late but i’ve only just stumbled across this great place!
apparently i’m one of the 7 (or is it 8 now?) users of DP in the UK, but like you, i’m using it day-in-day out and have been for about 10+ yrs now, and still with every update i find things i never knew i could do – some of that changes with the type of job i’m doing as well, be it editing, composing, foley etc etc
back to the topic though…. just a little tip to share: i started using the ‘long bounce’ (ie real-time mix) method around v5 when things started becoming really unreliable at bounce-down for me, and used it right up to a few months ago when i upgraded my studio machine to something that could cope with v7 and gave bounce a go again, and i’m pleased to say it’s dramatically improved, though i do still check everything meticulously in real-time before burning etc
when i first started doing real-time mixes i was dogged by the problem that i often couldn’t hear what was going down to the mix track. the info was appearing ok, but i just couldnt hear anything till afterwards, which made mixing a nadge tricky.
it took me ages to figure out that i needed to make sure that the Input Monitoring Mode was set to Monitor Thru Internal Effects NOT Direct Hardware Playthru, once changed – presto! i could hear everything again.
I know that sounds really simple, but it threw me for quite a while and it’s one of thos things I would have loved to have read within 5 mins of having the problem because some other spoon had done it.
Hence why i thought I’d share….
Keep up the fantastic work.
Paul D
the frozen north
UK
I’m Paul, and I’m a British DP user, and I can be a spanner at times. Don’t hit me with your Logic Pro manual just cos i’m human.
#5 by se on May 30, 2011 - 12:07 pm
Quote
Thanks for the wonderful site…
and…@ Paul D.
THANXXX:-)
I’ve been trying to figure it out for a loooong while!! I couldn’t hear a sound! NOW I CAN.
Thanks for sharing
S
#6 by charles on May 30, 2011 - 4:39 pm
Quote
@se….your welcome, thanks for writing!