We can at least start a summary of what we know so far in this thread.
Keep in mind that some report improvements while others are still having the same problems.
1. Erratic MIDI Click problem when using count-off was fixed by trashing prefs (partially but not entirely related to solution listed in item #5)
2. Audio dropouts when playing right after recording-- fixed on some systems, not on others
3. CPU spikes in 4.61 constant (Dual 800), occasional in 5.0, hovering around 75% in 5.01
4. 5.0 crashed while edge-editing soundbites. Fixed in 5.01.
5. Pause on Locate and other features tied to DP 4.x preferences work better when a new sequence, new V-Stack, new chunk, or new VI patch setting is created in DP 5.x. Could be related to MIDI driver 1.3.2. According to Shooshie, those using 1.3.1 are having fewer MIDI problems-- sluggish starts, etc.
6. DP 5.x- crashes apparently associated with certain AUX track bussing functions-- no known solution posted. Could be driver related...
7. Meter Bridge clips readouts..? Composites signal and red-lines what looks fine in the mixer's master fader. No solution (?)
8. Meter Bridge causes crash in DP 5.x. When opened with TRACKS selected, (to quote muzishun) choosing
"New Aux Track via New Mono/Stereo Bundle", I get a "Digital Performer has encountered an error" message, followed by an inevitable crash.
9. Another from muzishun:
I have a plug-in on an audio track - say MW Equalizer. When I go to "Automation Setup", under "Enable Automation Types", in the "Add" dropdown, the parameters for the plug-in are not present...until I automate one of them, then that one will show up. In 4.5, this was not the case. All parameters were available immediately.
Shooshie wrote:I've had problems with the Meter Bridge. My intuition is that anything that changes which would involve the Meter Bridge while it is open stands a good chance of causing problems. Example: change audio bundles while the Meter Bridge is open, and you may actually break the Meter Bridge semi-permanently until you put those bundles back as they were, then CLOSE the meter bridge before changing those bundles.
In your case, you added an Aux track, which would actually change the meter bridge. It would have to add a track to its display. That may or may not be enough to crash it. In your case it was. So, it's advisable to close the Meter Bridge before making large changes involving I/O and numbers of tracks.
10. BTD dropouts and volume jumps on playback-- no definitive solution.
11. From user Jim:
CPU meter can be hovering around half when I start a project, but then after working with volume automation only for a while, the CPU meter goes up to around 90%, starts spiking red frequently, and the audio quality degrades (sounds like dropouts).
Closing and re-opening the project fixes this temporarily, as does Quitting and re-launching the application. Then about fifteen minutes later, I have to repeat.
12. Uncertain if the Pitch Bend Range has been corrected in DP5 to -8192 to +8191 instead of the MOTU alleged limit of -8064 to 8064
13. MAS-Native VI's with DP 5.x on some systems not appearing in the Add Tracks Menu even though proper MAS files are present in the the proper Library/Audio/Plugins folders. One solution, again, was to trash old Prefs, reconfig any V-Stacks-- basically start with fresh DP 5.x projects. Some users are reporting problems running older projects from DP 4.61 and earlier in DP 5.x, despite repairing permissions, accounting for all files, reinstalling, etc., etc.
Note: unless someone does a side-by-side test with DP 4.x and DP 5.x, cross checking the long DP 4.x problems thread with the DP 5 Wish List thread, the list of problems and fixes may ever be incomplete. But, perhaps this is a start.
Feel free to add to this list, and make any corrections as they are "lifted into consciousness".
