RESOLVED: still no luck getting DP 7 working

[cchord59]

Well, that's the fix. If in FACT you NEVER saved the session in 7.1 then you have some other issues. Try reformatting your HD and reinstalling OS X and then DP... if it don't work then, you have a corrupt session document there. I'd try the LOAD command and just get the session @ least to ground zero and start from there.

It's a general problem that occurs with any session I open from 6.03. Even new sessions won't open. But I don't get the error message that time.

[cchord59]

Just reauthorized dp 7.01 again, and still no luck. I removed 7.02 as well.

[newrigel]

Man I'll tell ya... I have NEVER encountered any of these problems. I don't know but I'd start from scratch if I ever had this since it's my audio workstation. have you tried to just uninstall everything DP and then trashing all the .plist, and the auth file like I said, THEN, repair permissions by booting off the OSX install DVD, running disk utility and repairing permissions? Then after that, try a complete reinstall of DP and NOTHING else. No plugs nothing, then try to launch a new project. If this doesn't work I'd call MOTU and get a new install disk and or wipe the drive and redo everything from scratch. It's a permission problem and you should be the only user on that machine if you want a STABLE DAW!
Only have ONE user account on your Mac... YOU if you want stability.

[dado]

You must find the invisible Auth DP in the finder an put in the trash. Then put some other doc you don't need in the trash and empty it. Then repair permissions and reinstall DP7. Good Luck!

[cchord59]

Finally worked. I have no idea how, but I have been doing the same thing every time. Maybe deleting prefs is the key.

Thanks for the help.

[newrigel]

You must find the invisible Auth DP in the finder an put in the trash. Then put some other doc you don't need in the trash and empty it. Then repair permissions and reinstall DP7. Good Luck!

I did forget to say that... but since I do it with cocktail everything is visible so you don't need to but within the finder yes... sorry about that HUGE important detail.

[cuttime]

Glad you got it resolved. I'm watching from the sidelines, as I don't use Snow Leopard, but I've seen various threads about authorization problems lately, and it seems that they might be related to SN. I'm thinking that it may be related to the fact that Apple has dropped support for creator codes in OSX 10.6. This article is a good introduction to the scenario:

http://www.macworld.com/article/142937/ ... files.html" onclick="window.open(this.href);return false;

This seems to ring a few bells, perhaps those who are more conversant in OSX programming can offer some clarification.

[zed]

I'm thinking that it may be related to the fact that Apple has dropped support for creator codes in OSX 10.6. This article is a good introduction to the scenario:

http://www.macworld.com/article/142937/ ... files.html" onclick="window.open(this.href);return false;

Thanks for posting that. Interesting stuff.

Once DP7 is launched, it will automatically launch double-clicked applications with the version that is active and running (if it is the same version). But as I mentioned above, on my system I am unable to force all DP documents to automatically open with DP7.1 using the "change all" command (as the article suggested as a workaround). I probably have an invisible file to delete or a parametre in the OS to adjust somewhere. But fortunately the point is moot as long as I begin each day by launching DP7.1 from the dock.

[newrigel]

Glad you got it resolved. I'm watching from the sidelines, as I don't use Snow Leopard, but I've seen various threads about authorization problems lately, and it seems that they might be related to SN. I'm thinking that it may be related to the fact that Apple has dropped support for creator codes in OSX 10.6. This article is a good introduction to the scenario:

http://www.macworld.com/article/142937/ ... files.html" onclick="window.open(this.href);return false;

This seems to ring a few bells, perhaps those who are more conversant in OSX programming can offer some clarification.

Yeah, I don't use SL... I don't NEED to! Unless anything I rely upon calls for it, I don't update. Leo has been VERY stable and as solid as Tiger was for me. It took Apple a few updates but now, Leo's very stable and solid!

[zed]

Leo has been VERY stable and as solid as Tiger was for me. It took Apple a few updates but now, Leo's very stable and solid!

I think Snow Leopard is pretty stable too... no less so than Leopard, for me anyway. It just has a few differences with the way things are handled.

Some of the Snow Leopard improvements are WAY MORE important to me than the few things that are more awkward. The most obvious one is that screen captures (which I do all the time) are now dated and timed in the filename so you never run into the former situation of having numerous files with the same name and not being able to put them in the same folder. And Exposé is cleaner and more organized (which is also something that gets used dozens of times every day). And a bunch of other little things make for a more pleasing Finder experience. I definitely wouldn't want to go back to Leopard.

[zed]

But having said that...

One thing that is driving me crazy in Snow Leopard is the fact that aliases do not work well anymore. Whenever I do a Finder search for just about anything on my hard drives, the Finder finds a list of things and I see what I am looking for. I double-click on the file and get the message:

The alias "blah blah blah" can't be opened because the original item can't be found.

Not only is that ridiculous because it JUST FOUND IT. But it also isn't an alias at all. I suspect that Finder searches see all files as aliases. The work around is simple--you just single-click on the file and the hard drive to file heirarchy is displayed at the bottom of the window. If you double-click on the file or folder in the heirarchy, then it will open.

Pretty frustrating that this is broken, though.

And other aliases don't work also. I just created some aliases this morning, and they completely don't work when I try to navigate to them via Finder windows (i.e. like when I am trying to load or save a preset from within a VI). I suppose this is maybe connected to all the permissions problems in Snow Leopard. Whatever it is, it really needs to be rectified sooner than later since it totally undermines the efficiency of my workflow.

EDIT >>> I just discovered that the aliases from within the Finder windows do actually work, after all. They are just greyed out as if they are locked or unavailable. When they looked this way in previous versions of Mac OS they were actually not available options. So I am not sure if this is an error in OS functionality or another one of Apple's changes to things just to mess with us.

[bongo_x]

But having said that...

One thing that is driving me crazy in Snow Leopard is the fact that aliases do not work well anymore. Whenever I do a Finder search for just about anything on my hard drives, the Finder finds a list of things and I see what I am looking for. I double-click on the file and get the message:

The alias "blah blah blah" can't be opened because the original item can't be found.

Not only is that ridiculous because it JUST FOUND IT. But it also isn't an alias at all. I suspect that Finder searches see all files as aliases. The work around is simple--you just single-click on the file and the hard drive to file heirarchy is displayed at the bottom of the window. If you double-click on the file or folder in the heirarchy, then it will open.

Pretty frustrating that this is broken, though.

And other aliases don't work also. I just created some aliases this morning, and they completely don't work when I try to navigate to them via Finder windows (i.e. like when I am trying to load or save a preset from within a VI). I suppose this is maybe connected to all the permissions problems in Snow Leopard. Whatever it is, it really needs to be rectified sooner than later since it totally undermines the efficiency of my workflow.

EDIT >>> I just discovered that the aliases from within the Finder windows do actually work, after all. They are just greyed out as if they are locked or unavailable. When they looked this way in previous versions of Mac OS they were actually not available options. So I am not sure if this is an error in OS functionality or another one of Apple's changes to things just to mess with us.

I'm not having this problem at all. Aliases are working fine here in all windows.

bb

[zed]

I'm not having this problem at all. Aliases are working fine here in all windows.

Are they greyed out as I described in the paragraph I added above?

[bongo_x]

I'm not having this problem at all. Aliases are working fine here in all windows.

Are they greyed out as I described in the paragraph I added above?

No. They don't seem any different than before.

I did a couple tests after you wrote this. I only found one problem. I made an alias of a folder and then renamed the alias. Now it doesn't show up in a spotlight search of the drive, but it did show up in a search of the containing folder. I find spotlight searches pretty hit and miss though.

bb

[zed]

I find spotlight searches pretty hit and miss though.

I hear you. Gone are the days when the OS could actually find everything on your hard drives. I often find myself looking for files which I know are there, and the Finder cannot find them. I look for them manually, and find them right where they should be.

It is a little disheartening that Apple keeps stripping away aspects of basic functionality. Searches, and aliases, window states, and keeping track of parent applications are among the most essential computer functions and yet they are all working a little unreliably right now.