FWIW, I don't have any audio dropout issues in any apps. I am on 10.4.3, DP 4.61 (I deleted DP5), PTHD 6.9.3. I have two systems, more or less identical: G5 dual 2.7, both with Motu Travelers, and Digidesign HD192s (two each). I run PT through it's own interfaces, everything else (DP, iTunes, Quicktime, Jam, etc.) through the Travelers. I never, ever hear any audio dropouts in any program. So as far as reports of audio dropouts in other software, I ain't seeing it. I also have a powerbook 1.67, and between all these machines, that is pretty much all my waking hours (I don't get out much). "What audio dropout problems?" would be my response.
BTW, I don't use BTD. So that one may very well exist, but system-wide stuff, nope!
Bounce TD broken 5.1 yea yea old news but....
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.
-
BobK
- Posts: 1533
- Joined: Mon Oct 18, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Oakland, CA
- Contact:
I know this is old news, but I want to add my testimony. I've been doing some tracking in DP 5.1, and haven't had much occasion to do any bounces till tonight.
I just tried to do a bounce for a project with around 40 tracks (though a bunch of those didn't have audio data till the last minute of the track). At least a dozen tracks didn't appear at all in the bounces. Tried bouncing to MP3 and SDII - same result.
I saved the project in DP 4.61 format, quit DP 5.1, launched DP 4.61, bounced, and it worked just fine. I didn't make any changes to the file in 4.16 before doing the bounce.
After reading Chris' post, it reminded me: Earlier this week I loaded this same project onto a MacBook Pro I'd just gotten. I'm pretty sure the same tracks which are absent from my bounces are the same tracks which wouldn't play back on my notebook.
I tried various things to resolve the problem on the Mac Book Pro, and what eventually worked was this: based on a suggestion from magicd, I created new input bundles. The only bundles that initially showed up were those from the interface connected to the G5, on which I'd originally created this Project. When I first opened the project on the MBP, I only created new output bundles (for the built-in audio); I wasn't planning to record to the MBP, so I had ingnored input bundles.
In one Project, simply assigning the problem tracks to one of these new inputs resulted in the problem tracks now playing back. In another project, I may have had to toggle the input monitor buttons on the problem tracks before they'd play back (I don't recall).
Just now, I opened tonight's problem project in DP 5.1 on my G5. I deleted all the input and output bundles and rebuilt them (I use a MOTU 1224/PCI 424). I didn't rebuild the internal bus bundles.
I reassigned all appropriate tracks to the new output bundles and tried the bounce again (no audio tracks were assigned to input bundles at this point). No dice - tracks are still missing from the bounce.
Next, I assigned the input for all the audio tracks to Analog 1. Then, in the Tracks window, I toggled the Input Monitor ('Mon') switch on and then off.
This time, the bounce worked - the missing tracks were now present.
When I had the problem with my MacBook Pro, I thought it had something to do with moving the files from a PPC to an Intel Mac. Maybe it did at some level, but it appears that there are problems with DP's internal bussing. I'm sending this to MOTU.
I just tried to do a bounce for a project with around 40 tracks (though a bunch of those didn't have audio data till the last minute of the track). At least a dozen tracks didn't appear at all in the bounces. Tried bouncing to MP3 and SDII - same result.
I saved the project in DP 4.61 format, quit DP 5.1, launched DP 4.61, bounced, and it worked just fine. I didn't make any changes to the file in 4.16 before doing the bounce.
After reading Chris' post, it reminded me: Earlier this week I loaded this same project onto a MacBook Pro I'd just gotten. I'm pretty sure the same tracks which are absent from my bounces are the same tracks which wouldn't play back on my notebook.
I tried various things to resolve the problem on the Mac Book Pro, and what eventually worked was this: based on a suggestion from magicd, I created new input bundles. The only bundles that initially showed up were those from the interface connected to the G5, on which I'd originally created this Project. When I first opened the project on the MBP, I only created new output bundles (for the built-in audio); I wasn't planning to record to the MBP, so I had ingnored input bundles.
In one Project, simply assigning the problem tracks to one of these new inputs resulted in the problem tracks now playing back. In another project, I may have had to toggle the input monitor buttons on the problem tracks before they'd play back (I don't recall).
Just now, I opened tonight's problem project in DP 5.1 on my G5. I deleted all the input and output bundles and rebuilt them (I use a MOTU 1224/PCI 424). I didn't rebuild the internal bus bundles.
I reassigned all appropriate tracks to the new output bundles and tried the bounce again (no audio tracks were assigned to input bundles at this point). No dice - tracks are still missing from the bounce.
Next, I assigned the input for all the audio tracks to Analog 1. Then, in the Tracks window, I toggled the Input Monitor ('Mon') switch on and then off.
This time, the bounce worked - the missing tracks were now present.
When I had the problem with my MacBook Pro, I thought it had something to do with moving the files from a PPC to an Intel Mac. Maybe it did at some level, but it appears that there are problems with DP's internal bussing. I'm sending this to MOTU.
Bob
M1 Max Mac Studio - 64 GB RAM - macOS 15.4
MacBook Pro (15-inch, Mid 2012) - 2.6 GHz Intel Core i7 - 16 GB RAM - macOS 14.4 via Open Core Legacy Patcher
DP 11.23
Metric Halo ULN-8 mk4
M1 Max Mac Studio - 64 GB RAM - macOS 15.4
MacBook Pro (15-inch, Mid 2012) - 2.6 GHz Intel Core i7 - 16 GB RAM - macOS 14.4 via Open Core Legacy Patcher
DP 11.23
Metric Halo ULN-8 mk4
-
Timeline
- Posts: 4910
- Joined: Tue Nov 09, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Fort Atkinson Hebron, Wisconsin...
- Contact:
It makes sense that the internal voice/track bussing was broken in 5.1 as it was re-written as an automatic app.
Previously in 4.6 we could select number of voices and tracks that were required for our projects forcing them open all the time.
Remember when you didn't have enough voices selected and the SAME thing would happen when DP would switch from dead space on an audio track to one with sound? It would leave one for another and you would loose sound until empty space returned then switch again.
This is what was broken in 5.1 imo.
Previously in 4.6 we could select number of voices and tracks that were required for our projects forcing them open all the time.
Remember when you didn't have enough voices selected and the SAME thing would happen when DP would switch from dead space on an audio track to one with sound? It would leave one for another and you would loose sound until empty space returned then switch again.
This is what was broken in 5.1 imo.
2009 Intel 12 core 3.46, 64GB, OSX.10.14.6, Mojave, DP11, MTPAV, Key-station 49,(2) RME FF800,
DA-3000 DSF-5.6mhz, Mackie Control. Hofa DDP Pro, FB@ http://www.facebook.com/garybrandt2
DA-3000 DSF-5.6mhz, Mackie Control. Hofa DDP Pro, FB@ http://www.facebook.com/garybrandt2
My work is a continuos BTD... I encontered this bug in this summer, upgrading to dp5 and I tried all possible solutions (rebuild audio bundles, uncheck flags in preferences and hardware/studio settings, etc. etc.). In some cases this works, in others the bug still remain...
I can't risk on btd, and I want not to lose a lot of time for a control of hundreds of files...
At this moment the only one solution is to make the BTD in DP 4.6.1: I have the absolute certainty the bounce is ok. I have not replies from Motu, I hope They solve asap this bug, the worst I seen in DP Hystory (even DP3.0 if memory not deceive, has a BTD bug, but peremptorily solved by MOTU with 3.0.1 and 3.0.2...)
Best
I can't risk on btd, and I want not to lose a lot of time for a control of hundreds of files...
At this moment the only one solution is to make the BTD in DP 4.6.1: I have the absolute certainty the bounce is ok. I have not replies from Motu, I hope They solve asap this bug, the worst I seen in DP Hystory (even DP3.0 if memory not deceive, has a BTD bug, but peremptorily solved by MOTU with 3.0.1 and 3.0.2...)
Best