Important question about BTD and track settings
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
Important question about BTD and track settings
Hi, I am stumped! I just figured out (after a year of using DP) that if I play a project through to the end, and then say "OK, that's what I want" and bounce to disk, the BTD does not reset the automation settings for different tracks to the beginning of the project. I discovered this because I had a guitar track fade to null, and then it was mysteriously absent from the bounce, at which point I figured out that the automation settings do not initialize to the beginning of the project when you bounce. My question is, therefore, how do you get DP to initiatilze everything in the project for a bounce, without closing and reopening the project? Thank you.
- buzzsmith
- Posts: 3097
- Joined: Mon Dec 27, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Houston
- Contact:
PG:
I'm assuming that...
1. All of the tracks that you want to BTD are set to the same output (Analog 1-2) and this corresponds with the setting in the bounce window...
2. Your start and end times are set correctly to inform DP of the regions that you want to bounce (Start: 1|1|000---End 87|3|425, for instance...)
3. All the tracks are highlighted (selected) in the tracks window that you want to bounce.
4. Automation is enabled for the tracks that need it including the Master
This is the way I do it anyway, and I never start a project right on 1|1|000, either.
Hope this helps!
Buzz
I'm assuming that...
1. All of the tracks that you want to BTD are set to the same output (Analog 1-2) and this corresponds with the setting in the bounce window...
2. Your start and end times are set correctly to inform DP of the regions that you want to bounce (Start: 1|1|000---End 87|3|425, for instance...)
3. All the tracks are highlighted (selected) in the tracks window that you want to bounce.
4. Automation is enabled for the tracks that need it including the Master
This is the way I do it anyway, and I never start a project right on 1|1|000, either.
Hope this helps!
Buzz
Early 2009 Mac Pro 4,1>5,1 3.33 GHz Hex Core Intel Xeon OS X 10.8.5 SSD (32 gigs RAM)
DP 9.51 PCI-424e / original 2408, 2408mkII, 24I/O, MTP-AV
Yamaha C7 Conservatory Grand
Hammond B-3 / Leslie 145
Focal Twin6 Be(s)
DP 9.51 PCI-424e / original 2408, 2408mkII, 24I/O, MTP-AV
Yamaha C7 Conservatory Grand
Hammond B-3 / Leslie 145
Focal Twin6 Be(s)
- Tritonemusic
- Posts: 2745
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
haha! THANK YOU buzzsmith!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
All of my Bounce settings were correct, just as you described they should be.
I have tried a variety of different experiments, and I've learned some stuff about Bouncing in DP that may be of interest. Having reviewed many posts on this board about bouncing problems (specifically, missing tracks), I think I've figured out the problem that various people are having, and I have the solution, too.
Bottom line: the DP Bounce to Disk does not reset automation parameters to the beginning of the region (or project). It takes whatever automation levels are extant at the moment the sequence was stopped, and uses them for the Bounce, until an automation change occurs.
Example: A guitar track that starts at 0db at measure 1, is increased to 2 db for the chorus at measure 17, and at the end of the project fades to null. You listen to the whole project, and at the end, after the fadeout, you say "That's perfect" and you bounce to disk. The guitar track will not be heard, until measure 17 when it will kick in at +2db.
However, if you rewind and just play a measure or two at the start of whatever region is being bounced (as someone already mentioned on this thread), all of the automation parameters will be set correctly.
I believe this is the simple explanation for the many complaints of tracks mysteriously being absent in DP bounces. I don't think there's a bug or error, as many have speculated. I think it's just a question of initializing the automation parameters before the bounce (i.e. "rewind")
All of my Bounce settings were correct, just as you described they should be.
I have tried a variety of different experiments, and I've learned some stuff about Bouncing in DP that may be of interest. Having reviewed many posts on this board about bouncing problems (specifically, missing tracks), I think I've figured out the problem that various people are having, and I have the solution, too.
Bottom line: the DP Bounce to Disk does not reset automation parameters to the beginning of the region (or project). It takes whatever automation levels are extant at the moment the sequence was stopped, and uses them for the Bounce, until an automation change occurs.
Example: A guitar track that starts at 0db at measure 1, is increased to 2 db for the chorus at measure 17, and at the end of the project fades to null. You listen to the whole project, and at the end, after the fadeout, you say "That's perfect" and you bounce to disk. The guitar track will not be heard, until measure 17 when it will kick in at +2db.
However, if you rewind and just play a measure or two at the start of whatever region is being bounced (as someone already mentioned on this thread), all of the automation parameters will be set correctly.
I believe this is the simple explanation for the many complaints of tracks mysteriously being absent in DP bounces. I don't think there's a bug or error, as many have speculated. I think it's just a question of initializing the automation parameters before the bounce (i.e. "rewind")
- tommymandel
- Posts: 1056
- Joined: Tue Nov 30, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: New York
- Contact:
is this true because DP has to "chase" the (automation) controllers?
DP 11.32 12core(5,1): 64GB/10.14.6, two 24i/o's, two 2408mk3's, 4pre, MicroLite-- MBP 2015 16GB/ 2TB 'Blade SSD 10.14.4, Mainstage, Numa C2x, ReMOTE SL -- 32 Lives, Pro-53, SampleTron,Keyscape,MTronPro,RolCloud,Icarus,Dune,OB-E; Clearmountain Domain,Soundtoys,AdrenaLinnSync, LinnSequencers,Tempest, Montage, JU80, Sledge, Prophet-X, T8, OB-6 V-Synth, s70xs, D-50, TS-10, JD800, Karma, Pa-1x B3, Wurly, Mason Hamlin.
Hardware rig: http://www.tommymandel.com/famous.html/tmrig.html"
Hardware rig: http://www.tommymandel.com/famous.html/tmrig.html"
- buzzsmith
- Posts: 3097
- Joined: Mon Dec 27, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Houston
- Contact:
PG:
I don't "think" I've ever had this problem but now I'm curious!
Later today, I'll experiment a bit.
Reflecting, it occures to me that when I BTD, I set my end point in the Sequence Editor with the I tool and click on END in the Tracks window to set the end point, then "rewind" to the beginning, see where the audio begins and set my start point.
So, perhaps, that's why I don't seem to be having any problems, since my normal procedure does involve a "rewind" of sorts.
Buzz
I don't "think" I've ever had this problem but now I'm curious!
Later today, I'll experiment a bit.
Reflecting, it occures to me that when I BTD, I set my end point in the Sequence Editor with the I tool and click on END in the Tracks window to set the end point, then "rewind" to the beginning, see where the audio begins and set my start point.
So, perhaps, that's why I don't seem to be having any problems, since my normal procedure does involve a "rewind" of sorts.
Buzz
Early 2009 Mac Pro 4,1>5,1 3.33 GHz Hex Core Intel Xeon OS X 10.8.5 SSD (32 gigs RAM)
DP 9.51 PCI-424e / original 2408, 2408mkII, 24I/O, MTP-AV
Yamaha C7 Conservatory Grand
Hammond B-3 / Leslie 145
Focal Twin6 Be(s)
DP 9.51 PCI-424e / original 2408, 2408mkII, 24I/O, MTP-AV
Yamaha C7 Conservatory Grand
Hammond B-3 / Leslie 145
Focal Twin6 Be(s)