MOTUnation.com

James Steele wrote:It's another one of those new weird bugs that doesn't affect almost anybody else.

A nasty roach! Sorry about the sarcasm...
If it's appearing on a fresh instal and nothing else is installed you'd equate it to a bug but if no one else is having this issue it may just be a user issue. I'd try it without the interface and see want happens.

It's big time a user issue. This is the most bizarre thing I've ever heard of and I have never encountered it or know anybody else who has encountered it. I really have to wonder. There's something seriously wrong with the user's system or someone is pulling our leg. Maybe it's a Logic user funning with us!

It's weird that it's doing it on a fresh install of SL and DP7... that's why I came to that conclusion... but like I said before, I'd try it w/o installing the 828 drivers then you'll nail down the real issue.
I NEVER use that function in DP because it's a waste of time.
And from my post obviously you can tell he he!
I'm still in 5.13 and very happy thank you!

No it's not a problem of user, I tried to make the same installation on my Macbook with very new Snowleopard and boom the same problem!!
I don't understand what is this &?/à&& issue, please help !!

legodo wrote:No it's not a problem of user, I tried to make the same installation on my Macbook with very new Snowleopard and boom the same problem!!
I don't understand what is this &?/à&& issue, please help !!

Neither do I because I've never seen it before and you and the other person who posted are the only people I ever seen mention this problem before.

Well... I just installed on my other drive a new build of SL and DP 7 and no problems here so...
You know, I don't see anyone ever use that new project command unless they are just beginning to learn DP. I have probably used it once or twice then after I figured out the template thing, I haven't even used it. If the user is having problems then just open up one of his old projects if it don't open look in the manual.. it's very easy to find it in the PDF version too!

Thank you all for the replies, and I realize that I've been flooding the forum with updates about the situation constantly, and that could tend to get annoying- sorry about that. Right now, Dp 5 and 6 are working fine on my system, so that's all that I really need by now, and I'll be trying to figure out what is wrong with 7 sometime in the future- need a break from this constant error-searching!
I've been working with DP for 5 years and never thought that the "new file" option is a waste of time, if you put your templates in the template folder and then click on "new-> template you want to use", isn't it just as good as opening a project file?

So again, thank you so much for your help/moral support/suggestions etc And if anyone besides legodo and me experiences this strange thing, let me know.

Why don't you contact Motu and tell them about the problem and see if they can help you????

James Steele wrote:Neither do I because I've never seen it before and you and the other person who posted are the only people I ever seen mention this problem before.

Actually, I did have this experience a couple of times when I first installed DP7... but I managed to very quickly resolve it. If I recall correctly, it was a problem that occurred after DP7 crashed and had not yet properly saved its preferences after the install (i.e. the command bindings hadn't stuck and I had to okay those dialog boxes again). I think just opening up a new project, saving it and then restarting DP made the problem to disappear... but I'm pretty fuzzy on the details... sorry.

It may have also been an incompatible plugin...

Ugh I'm having the same issue. HOW DO YOU FIX THIS?!

It seems to be happening to us Mac Pro users... with the 8-core machines. ?

Sigh.. I need this fixed pronto..

OK fixed it. Here's how:

http://www.motu.com/techsupport/technot ... ix-Leopard

Well, I stand corrected. That really is an odd problem, but glad there's a solution. I'm going to edit the header to say it's resolved.

James Steele wrote:Well, I stand corrected. That really is an odd problem, but glad there's a solution. I'm going to edit the header to say it's resolved.

This is the same user account problems that were happening before James.
Using the terminal:
From MOTU Site:

How to reauthorize DP, AudioDesk, or Unisyn under Tiger (OS 10.4)
At this time, reauthorizing under OS 10.4 must be done through the Terminal.

Quit all running applications. Make sure youare logged in as an administrator user, then proceed.
Go to Applications/Utilities and open Terminal.
Copy and paste this command, then pressReturn:
cd /

Then copy and paste this command, then press Return:
rm Auth-DigitalPerformer\ 4.5

If you are reauthorizing AudioDesk2 or Unisyn 2.1 instead, use the appropriate one of these two commands.

rm Auth-AudioDesk\ 2.0

Peace!
You can use Cocktail too in the finder preference to see hidden files but a fresh install shouldn't exhibit a permissions problem like this... this is due to creating multiple user accounts.

Indeed resolved! Thanks, this forum is great!

I Have the same problem running osx 10.4.11 on a 2.66 mac pro. I tried reauthorizing using Terminal, but I still get the error saying the file was created on an older version of DP. I reauthorized dp 6 first, and then realized that I need to reauthorize dp7.