Another BTD solution?
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.
Another BTD solution?
Today, I was still having inconsistent BTD results. I decided to remove all audio inputs, (except my busses off course) and it has worked 3 times in a row. I think it's worth a try for everyone else.
DP 5.13 dual G5 2.7 synced to dual 1.42 via SMPTE, Muse Receptor (filled with Stylus RMX, Trilogy, Atmosphere, Elektrik piano, Disco DSP), OSX.410, Ableton LIVE, Apogee Big Ben, Apogee mini DAC, MachV, Symphonic, Ethno, M-Tron, Mx-4,Latigo, Jupiter Vi, iDrum, Microtonic, Kontakt3, Bassline, Bassline Pro, Ultra Focus, Novation Basstation, Novation Drum Station, Nord Lead2, JD-990, EMU Proteus, Orbit 2, MicroKorg, UAD, Poco, Altiverb, VW2, Waves, Ozone, to name a few 

This is kind of what I was talking about some time ago when I first received 5.01. Once I cleared out old busses and built new ones, 5.01 has worked flawlessly for me. I'd recommend to everyone to rebuild templates from scratch including all aux busses and audio bundles set-up. Only takes a minute or two.
- Shooshie
- Posts: 19820
- Joined: Sat Oct 16, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Dallas
- Contact:
Chris, funny thing is that I HAD to rebuild my bundles. I opened my old projects in 5.0 and 5.01 to empty bundles. Er... at least that was the case in two projects. Come to think of it, some others were intact. Were your bundles intact when you opened projects in 5.x for the first time?
Shooshie
Shooshie
|l| OS X 10.12.6 |l| DP 10.0 |l| 2.4 GHz 12-Core MacPro Mid-2012 |l| 40GB RAM |l| Mach5.3 |l| Waves 9.x |l| Altiverb |l| Ivory 2 New York Steinway |l| Wallander WIVI 2.30 Winds, Brass, Saxes |l| Garritan Aria |l| VSL 5.3.1 and VSL Pro 2.3.1 |l| Yamaha WX-5 MIDI Wind Controller |l| Roland FC-300 |l|
I don't remember exactly. I do remember trying to bounce some tracks and experiencing odd problems -- mostly hangs, then quits -- so I cleared all routing out and rebuilt. Since then, I've rebuilt all my templates, starting from 5.01 scratch, and all's been well.Shooshie wrote:Chris, funny thing is that I HAD to rebuild my bundles. I opened my old projects in 5.0 and 5.01 to empty bundles. Er... at least that was the case in two projects. Come to think of it, some others were intact. Were your bundles intact when you opened projects in 5.x for the first time?
Shooshie
Didn't change my bundles. Just removed all inputs from the tracks view window except for necessary busses. Bounced several times again this weekend using this method and had no dropouts.
DP 5.13 dual G5 2.7 synced to dual 1.42 via SMPTE, Muse Receptor (filled with Stylus RMX, Trilogy, Atmosphere, Elektrik piano, Disco DSP), OSX.410, Ableton LIVE, Apogee Big Ben, Apogee mini DAC, MachV, Symphonic, Ethno, M-Tron, Mx-4,Latigo, Jupiter Vi, iDrum, Microtonic, Kontakt3, Bassline, Bassline Pro, Ultra Focus, Novation Basstation, Novation Drum Station, Nord Lead2, JD-990, EMU Proteus, Orbit 2, MicroKorg, UAD, Poco, Altiverb, VW2, Waves, Ozone, to name a few 

- mhschmieder
- Posts: 11408
- Joined: Wed Jul 06, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: Annandale VA
I just finished a four-day marathon remixing/remastering session that used projects from when I first started on DP 3 (OS 9!) to recent ones that were started on DP5. This became an opportunity for me to consolidate all that I have learned along with new productivity gains and workflow flexibility in DP5, recreate templates and reassign all inputs/outputs/busses (even on committed tracks/submixes). It really doesn't take that long, relatively speaking.
I like to retain a history of where tracks came from, in case I have to go back and correct something later, so I am overjoyed by the "disable" feature in DP5, as I no longer have to deassign inputs/outputs. But I did REASSIGN all inputs/outputs after cleaning out unused assignments from since-sold equipment (MOTU 896, Yamaha 01x, Yamaha mLAN expansion for Motif ES, etc.). When multiple devices have inputs/outputs that show up with the same name, it doesn't pay to be lazy in leaving clutter around!
The only problem I have encountered in DP5 thus far is some odd behaviour when it starts to run out of memory. And this couldn't happen in earlier versions because I could never get away with leaving the same session of DP running for sixteen hours or more
. Anyway, sometimes my iZotope Ozone mastering plug-in disengages (as though it's bypassed), or some of the stem submixes in the final mix start cycling out of the mix while auditioning the final master before performing the BTD.
This doesn't really concern me, as it's obvious why it's happening and easy enough to fix (by restarting DP after a precautionary save). I'm actually very impressed thus far with what a huge step forward DP5 is in terms of reliability, productivity, and even audio quality.
I like to retain a history of where tracks came from, in case I have to go back and correct something later, so I am overjoyed by the "disable" feature in DP5, as I no longer have to deassign inputs/outputs. But I did REASSIGN all inputs/outputs after cleaning out unused assignments from since-sold equipment (MOTU 896, Yamaha 01x, Yamaha mLAN expansion for Motif ES, etc.). When multiple devices have inputs/outputs that show up with the same name, it doesn't pay to be lazy in leaving clutter around!
The only problem I have encountered in DP5 thus far is some odd behaviour when it starts to run out of memory. And this couldn't happen in earlier versions because I could never get away with leaving the same session of DP running for sixteen hours or more

This doesn't really concern me, as it's obvious why it's happening and easy enough to fix (by restarting DP after a precautionary save). I'm actually very impressed thus far with what a huge step forward DP5 is in terms of reliability, productivity, and even audio quality.
- Shooshie
- Posts: 19820
- Joined: Sat Oct 16, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Dallas
- Contact:
Jim, do you find that ADC pulls down the CPU meter?Jim wrote:Thanks, I did this as well as turn off the Pre-Fill and Compensation, and for now, I can bounce again.
Shoosh
|l| OS X 10.12.6 |l| DP 10.0 |l| 2.4 GHz 12-Core MacPro Mid-2012 |l| 40GB RAM |l| Mach5.3 |l| Waves 9.x |l| Altiverb |l| Ivory 2 New York Steinway |l| Wallander WIVI 2.30 Winds, Brass, Saxes |l| Garritan Aria |l| VSL 5.3.1 and VSL Pro 2.3.1 |l| Yamaha WX-5 MIDI Wind Controller |l| Roland FC-300 |l|
Hey Shoosh, I've been working mostly with 461 for the past week. I generally only pay attention the CPU meter when it's clip light is on. But, I'll pay more attention to it on my next mix session and report back.Shooshie wrote: Jim, do you find that ADC pulls down the CPU meter?
Shoosh
recording: Mac Mini 2018 - 32GB RAM - 3.2 GHz 6-Core Intel Core i7 - two Focusrite Scarlett 18i20 - OS 14.7.2 - DP 11.34
mixing: Mac Mini M4 Pro - 64 GB RAM - Focusrite Scarlett Solo - OS 15.3.2 - DP 11.34
VIs and Plug-ins: hundreds (amassed since 1990)
mixing: Mac Mini M4 Pro - 64 GB RAM - Focusrite Scarlett Solo - OS 15.3.2 - DP 11.34
VIs and Plug-ins: hundreds (amassed since 1990)