DP 5.01-- User reports

[Shooshie]

1) When the Meter Bridge is open with "tracks" selected, when I go to an audio track's send dropdown and select "New Aux Track via New Mono/Stereo Bundle", I get a "Digital Performer has encountered an error" message, followed by an inevitable crash.

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.

Shooshie

[David Polich]

I still can't think of any reason to really use the Meter Bridge - especially on a 19-inch monitor, it takes up too much screen space. People seemd to get along fine without it in 4.61.

Was it a BIG feature request from users? I've had lots of things I wanted in DP, but a meter bridge was never one of them. I dunno - it just seems like a gimmick more than an essential tool. I could be wrong...

At any rate, if it's buggy, I'd suggest staying away from it until MOTU fixes it in DP 5.1.

[Timeline]

I remember asking for a more precise fader vu like nuendos but not this.

I asked also for an additional red vu for record levels on the fader with an additional fader when in record for level set similar to PT. They definitely have selective hearing. I think this could have been additional to the fader methodology for space and workflow.

I'm just going on the blurb from their site though.

[rainmaker]

Any news on the situation with some having problems with dropouts and volume changes with Bounce To Dick? Has 5.01 fixed that? I am waiting to upgrade until at least that problem is fixed. I think someone earlier in this thread said they were no longer having dropouts or volume jumps on playback but nobody has mentioned anything about the Bounce To Disk issue... anyone?

Thanks,
Rainmaker

[David Polich]

I may stand to be corrected. but as far as I can tell the BTD issue seems to be either pilot error or specific to some users specific set-ups and not a general problem with DP5. I've been running DP5 on my Powerbook G4 1.5 Ghz with no BTD issues, or any other issues, whatsoever.

[blue]

Any news on the situation••¦with Bounce To Dick?

Nothing ever happens when I give that command either.

[edledbury]

I may stand to be corrected. but as far as I can tell the BTD issue seems to be either pilot error or specific to some users specific set-ups and not a general problem with DP5. I've been running DP5 on my Powerbook G4 1.5 Ghz with no BTD issues, or any other issues, whatsoever.

David - I'm glad to hear you're not experiencing some of the problems others on this forum have been plagued with. You might want to refrain, however,from accusing them (or should I say us? ) of operator error. I've been using this program since its MIDI only incarnation, and I think that in that time I've pretty much figured out how it works. Bounce to disk disk issues are a reality for many people using 5.0, where they definitely weren't in 4.61. Hopefully, 5.1 will have solved these problems.

[edledbury]

The audio sync issue does seem to be resolved, but a new problem seems to have replaced it. I output video from an Igniter card (and this behaviour maybe specific to this card....) and now the screen goes black or freezes if I use the locate function on the numeric keypad. I get good playback ( and properly sync'd audio - hooray!) if I rewind and press start, but nothing if I try to start within the body of the cue I'm writing. Definitely a step backwards.

[tommymandel]

Could your difficulties be related to the Pause-on-Locate section earlier in this thread? It seems to be a newly implemented behavio*u*r on locating or rewinding while in play, if the countoff button is highlit in the transport window. Just a thought.

[edledbury]

Hi Tommy - Thanks for the thought. Unfortunately, this doesn't seem to be related. I almost never use the countoff button. This behavio*u*r (sorry for using the Anglo spelling....) seems to be part of DP's new shakiness with QT. I'm sure it'll be resolved soon, but in the meantime it's back to 4.61 for me....

[toodamnhip]

System seems sluggish to start playing..any dared bring the orime seconds setting to 0? Seems less responsive when hitting play.

System irradic when entering in bar numer while playing sometimes it pauses, sometimes it does not.


System crashes when adjusting in/output/aux etc on meter bridge

[Shooshie]

Just a note about various problems in DP and "operator error:"

One thing I learned from collecting data from all you guys on your system setups is that you are using a wide variety of drivers. Some of you are mixing old MIDI drivers with new audio drivers, or vice-versa. Many think you have the latest drivers, but you don't. So, there is actually a wide variety of setups out there, and it stands to reason that many people can have problems that others just don't experience. For example, I know 100% positively for a fact that the majority of stuck notes are caused by MIDI driver version 1.3.2. Those using 1.3.1 (such as myself) rarely report any such problems. Some of us can choose which audio drivers we use, while others cannot. New Macs require the latest drivers for the PCI express cards.

Moral of story: don't be too quick to point the finger. The causes of many problems are more subtle than you think, and the skill of the operator has nothing to do with it. It's more like the luck of where you stopped installing new drivers. I stopped when I had a stable system. That's generally good sense if you can do it. (Obviously, new quad and dual-core Mac owners can't do that)

Shooshie

[toodamnhip]

Just a note about various problems in DP and "operator error:"

One thing I learned from collecting data from all you guys on your system setups is that you are using a wide variety of drivers. Some of you are mixing old MIDI drivers with new audio drivers, or vice-versa. Many think you have the latest drivers, but you don't. So, there is actually a wide variety of setups out there, and it stands to reason that many people can have problems that others just don't experience. For example, I know 100% positively for a fact that the majority of stuck notes are caused by MIDI driver version 1.3.2. Those using 1.3.1 (such as myself) rarely report any such problems. Some of us can choose which audio drivers we use, while others cannot. New Macs require the latest drivers for the PCI express cards.

Moral of story: don't be too quick to point the finger. The causes of many problems are more subtle than you think, and the skill of the operator has nothing to do with it. It's more like the luck of where you stopped installing new drivers. I stopped when I had a stable system. That's generally good sense if you can do it. (Obviously, new quad and dual-core Mac owners can't do that)

Shooshie

[toodamnhip]

Just a note about various problems in DP and "operator error:"

One thing I learned from collecting data from all you guys on your system setups is that you are using a wide variety of drivers. Some of you are mixing old MIDI drivers with new audio drivers, or vice-versa. Many think you have the latest drivers, but you don't. So, there is actually a wide variety of setups out there, and it stands to reason that many people can have problems that others just don't experience. For example, I know 100% positively for a fact that the majority of stuck notes are caused by MIDI driver version 1.3.2. Those using 1.3.1 (such as myself) rarely report any such problems. Some of us can choose which audio drivers we use, while others cannot. New Macs require the latest drivers for the PCI express cards.

Moral of story: don't be too quick to point the finger. The causes of many problems are more subtle than you think, and the skill of the operator has nothing to do with it. It's more like the luck of where you stopped installing new drivers. I stopped when I had a stable system. That's generally good sense if you can do it. (Obviously, new quad and dual-core Mac owners can't do that)

Shooshie

I am not sure I agree that having the latest drivers or, updating DP and DP not being smart enough or thorough enough to upgrade old drivers, or DP's older drivers being better than it's newr ones...I am not sure all of that would be best described as user error....

What bussiness does MOTU have upgrading drivers in a way that makes them worse, or allowing old drivers to stay in compyers when installing new nes, or not giving thorough instructions on how to remove old drivers should MOTU suspect a problem...

I thoroughly DO point my finger at MOTu and have always believed MOTU to be lacking in informing users of system liabilities, best scenarios for set ups and..I feel they are lazy in beta testing at times, making us all guineea pigs from time to time, in addition, I never ceased to be amazed at how DP improves in many ways, and then has certina "once stable" functions become problematic....

3 stpes forward..1 step back...

ANd, depending who you are, and how bad you need that function, you are either screwed or not...

[richardein]

First, I agree with Shooshie that the MW eq is excellent. I don't have the Waves EQ for comparison, but then I haven't felt the need to get it. Yes, the FFT is excellent on the MW.

Regarding drivers, in DP 5.0, I was having a hopeless number of stuck notes with 1.32. I tried to find 1.31, but couldn't (Shooshie posted audio drivers, not MIDI drivers). The closest I could find was 1.3, which is the only thing posted on macmusic.org, btw before1.32.

In any event, 1.3 works fine with 5.0. I'm out of town now, returning today. Will install 5.01 when I get back and if there's anything to report, will let you know.

I'm curious if 1.32 will now work properly in 5.01. I assume there is a good reason the driver was updated so would prefer to use it, if it doesn't break MIDI of course!