DP5 Bug Report

For seeking technical help with Digital Performer and/or plug-ins on MacOS.

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.
User avatar
hammerman
Posts: 536
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Lynn, MA
Contact:

DP5 Bug Report

Post by hammerman »

OK. Here goes:

1. PROBLEM WITH FADES- If I fade two tracks or more at the same place and they are the same length, I get volume changes when we get to the faded portion of the files. On their own they're fine. Together, volume glitches occur and they are not the same on repeated playback. BTD doesn't solve it BUT MERGE SOUNDBITES DOES. OR, deleting the Fades folder and having DP recalculate the fades does as well, until you create NEW fades and the problem comes back. Try it with the same file. Duplicate it and create a 3 or 4 second fade in or fade out. Sometimes the problem isn't there though. Hmmm. No problem at all with DP 4.61 with the same project. All prefs have been trashed.

2. Every time I open a project, I get the default time ruler with bars with the Edit Grid on. If I chose Real Time with the Edit Grid off and save the project, the next time I open it, it will be bars and beats with Edit Grid on. This preference used to be saved with every project.

3. When using Continuous Scroll, the wiper now seems to want to stay all the way at the left of the screen and I can't move it. The icon changes when holding down the option key to move the wiper but it will not move.

4. COUNTER- What happened to the little icons to the right of the numbers so you know what's real time, measures, or frames? They're gone in DP5.

OK, except for fades, these are small small bugs. Overall, I'm really happy with DP5. It's solid, stable, and lean. Waves, Altiverb, Virtual Guitarist 2, Stylus RMX, and GPO are all working great. Also, these may have to do with my system so it would be nice to know if others are having these problems. I will post this to MOTU as well.
User avatar
hammerman
Posts: 536
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Lynn, MA
Contact:

Post by hammerman »

I forgot this big problem (at least on my system) Many times when I try to bounce a mono file with a mono output into any format, the first second or so is cut off. The file starts but the audio is muted for the first second or so. Doesn't happen everytime but it does happen at least 70% of the time. I go back to DP4.61 and no problemo at all. I have trashed prefs, etc.. I think it has to do with the new MAS. I have tried changing buffer settings, using no plugs, changing prefs, but no luck.
User avatar
hammerman
Posts: 536
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Lynn, MA
Contact:

Post by hammerman »

I guess this is a solo thread! I am having trouble loading old projects into a new DP5 file. Quits every time. Anyone else?
User avatar
kwiz
Posts: 1345
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: NYC
Contact:

Post by kwiz »

Had a vocal session yesterday and everytime I punched in on a track and then punched out I got a buffer error message. I'm on a dual 1.8 wih 2 gigs of ram and my buffer is set at 512/work priority is at medium, recording to a 10k rpm Raptor drive.
If I didn't punch out and just hit stop, everything was fine.

Anyone else experience this?
Great family and friends!

Mac Studio M2 Max, MacPro 8 core (trashcan), MacBook Pro 16 in 2023, OSX Ventura, DP 11, Pro Tools, Logic Pro X, Motu 112D, 24Ao, 8M, 896 MKIII, UA Apollo 16, Waves Horizon, Slate Everything Bundle, Plugin Alliance Bundle, UAD-2 Satellite DSP Accelerator, UAD Apollo Twin.
Native Instruments Komplete 14 Ultimate, Console 1 MKIII w/C1 Fader

"Without struggle, there is no progress"

F. Douglas
bhagert
Posts: 62
Joined: Thu Nov 25, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Stockholm

Post by bhagert »

I had some odd error messages when I first installed DP5. After trashing the pref file it works great. Just a thought!
Dual 2.0 G5/3.5GB, 10.4.6, DP 5.0, 828mkii
User avatar
Kazrog
Posts: 42
Joined: Fri Nov 19, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Santa Barbara, CA
Contact:

Re: DP5 Bug Report

Post by Kazrog »

hammerman wrote:OK. Here goes:
4. COUNTER- What happened to the little icons to the right of the numbers so you know what's real time, measures, or frames? They're gone in DP5.
These still exist for me. I haven't experienced any of your other problems, but I haven't tested them.

What's your configuration?
Shane McFee
Recabinet | Kazrog LLC
User avatar
MIDI Life Crisis
Posts: 26286
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Post by MIDI Life Crisis »

hammerman wrote:I guess this is a solo thread! I am having trouble loading old projects into a new DP5 file. Quits every time. Anyone else?
Been about 2 weeks since your first post. What does tech support have to sya about this?
2013 Mac Pro 2TB/32GB RAM

OSX 10.14.6; Track 16; DP 12; Finale 28

LinkTree (events & peformances)
Instagram
Facebook

MIDI LIFE CRISIS
User avatar
kwiz
Posts: 1345
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: NYC
Contact:

Post by kwiz »

bhagert wrote:I had some odd error messages when I first installed DP5. After trashing the pref file it works great. Just a thought!
Thanks, I'll give that a try.
Great family and friends!

Mac Studio M2 Max, MacPro 8 core (trashcan), MacBook Pro 16 in 2023, OSX Ventura, DP 11, Pro Tools, Logic Pro X, Motu 112D, 24Ao, 8M, 896 MKIII, UA Apollo 16, Waves Horizon, Slate Everything Bundle, Plugin Alliance Bundle, UAD-2 Satellite DSP Accelerator, UAD Apollo Twin.
Native Instruments Komplete 14 Ultimate, Console 1 MKIII w/C1 Fader

"Without struggle, there is no progress"

F. Douglas
User avatar
sdfalk
Posts: 2514
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Vancouver BC
Contact:

Re: DP5 Bug Report

Post by sdfalk »

Kazrog wrote:
hammerman wrote:OK. Here goes:
4. COUNTER- What happened to the little icons to the right of the numbers so you know what's real time, measures, or frames? They're gone in DP5.
These still exist for me. I haven't experienced any of your other problems, but I haven't tested them.

What's your configuration?
Appears to be gone for me as well
User avatar
MIDI Life Crisis
Posts: 26286
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: DP5 Bug Report

Post by MIDI Life Crisis »

sdfalk wrote:
Kazrog wrote:
hammerman wrote:OK. Here goes:
4. COUNTER- What happened to the little icons to the right of the numbers so you know what's real time, measures, or frames? They're gone in DP5.
These still exist for me. I haven't experienced any of your other problems, but I haven't tested them.

What's your configuration?
Appears to be gone for me as well
They are on my system. All current Mac OS stuff. What is your OS at?
2013 Mac Pro 2TB/32GB RAM

OSX 10.14.6; Track 16; DP 12; Finale 28

LinkTree (events & peformances)
Instagram
Facebook

MIDI LIFE CRISIS
User avatar
sdfalk
Posts: 2514
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Vancouver BC
Contact:

Post by sdfalk »

The most recent version of the Mac OS

:Edit:
I should mention that the only audio interface I have at the moment
is an M-Box (first gen) with the latest drivers.
User avatar
kwiz
Posts: 1345
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: NYC
Contact:

Post by kwiz »

kwiz wrote:Had a vocal session yesterday and everytime I punched in on a track and then punched out I got a buffer error message. I'm on a dual 1.8 wih 2 gigs of ram and my buffer is set at 512/work priority is at medium, recording to a 10k rpm Raptor drive.
If I didn't punch out and just hit stop, everything was fine.

Anyone else experience this?
Spoke to tech support today and they stated that this is a known problem and it should get addressed in the next release.
I went into preferences and disabled the warning dialog box in order to avoid having this glich mess with my flow, however the red ligh still blinks in the performance meter everytime I punch out.
Great family and friends!

Mac Studio M2 Max, MacPro 8 core (trashcan), MacBook Pro 16 in 2023, OSX Ventura, DP 11, Pro Tools, Logic Pro X, Motu 112D, 24Ao, 8M, 896 MKIII, UA Apollo 16, Waves Horizon, Slate Everything Bundle, Plugin Alliance Bundle, UAD-2 Satellite DSP Accelerator, UAD Apollo Twin.
Native Instruments Komplete 14 Ultimate, Console 1 MKIII w/C1 Fader

"Without struggle, there is no progress"

F. Douglas
User avatar
waterstrum
Posts: 1096
Joined: Tue Oct 19, 2004 10:01 pm
Primary DAW OS: Unspecified

Post by waterstrum »

I've been having the spike/error message on punch out too.
Good idea to disable the warning box.
bone.china
Posts: 67
Joined: Tue Oct 19, 2004 10:01 pm
Primary DAW OS: Unspecified

Post by bone.china »

I haven't read the thread so maybe this has been mentioned already. In DP5 waveforms of the audio files will just disappear for no apparent reason! :shock: It's only happend once to me just a few minutes ago but damn if I know what caused that to happen. I only used the key command of hitting the number 1 on the number pad to return the sequence to the beginning. The waveforms then disappeared but when I pressed the space bar to start the sequence again I could still hear the proper sound being played. Shortly after that DP5 unexpectedly quit and so all changes were lost! :x Of course I didn't want to do a save because I thought that maybe the tracks were corrupted since I could no longer see the waveforms of the audio tracks. Upon opening the project again the audio files displayed correctly but, again, all changes were lost. :?

MOTU has to do some work, man. This feels like DP3. Bummer. :(
Imagination is the source of creativity.
Rush909
Posts: 320
Joined: Mon Nov 29, 2004 10:01 pm
Primary DAW OS: Unspecified

Post by Rush909 »

bone.china wrote: Upon opening the project again the audio files displayed correctly but, again, all changes were lost. :?

MOTU has to do some work, man. This feels like DP3. Bummer. :(
a tip for next time... just save your project file under another name... that way if it is corrupted, then you still have the original project... but if all is good, then atleast you still have all your changes...

r.
Post Reply