DP and Mavericks

[nk_e]

FWIW. I updated and ran into a weird problem.

When I launch DP it runs through it's start up sequence and presents that "landing page" or whatever you call it (the thing listing projects, links to tutorials, etc.). At this point, one of three things happen:

1 - If I hesitate and do nothing, the beach ball appears on its own about 10 or 15 seconds in, and never goes away.
2 - If I move to click anything in that pane, the beach ball appears and never goes away.
3 - If i quickly move to the menu bar and try to open a new project or previous one, it sometimes works and everything is fine. (The project loads and I can proceed on my merry way.) I have to be very quick though.

In either scenario 1 or 2 the only way out is to ctrl-alt-esc and force quit.

Last night based on something I read in this thread, I made DP a "trusted application" in the security settings. I was then able to launch things normally. I have tried this only once as, now that I have it running, I decided to keep it running. (I'm trying to finish up a short personal project this weekend and I don't want to lose anymore time.) Don't know if this solved anything or was a fluke...

Incidentally, I did fix permissions, rebooted, and at one point reinstalled the 8.05 update while trying to sort this out. (To no effect.)

Other than that, no other issues that I have run across.

[MIDI Life Crisis]

Sounds like that worked but never underestimate the need to reinstall the OS itself.

[bayswater]

1 - If I hesitate and do nothing, the beach ball appears on its own about 10 or 15 seconds in, and never goes away.
2 - If I move to click anything in that pane, the beach ball appears and never goes away.
3 - If i quickly move to the menu bar and try to open a new project or previous one, it sometimes works and everything is fine. (The project loads and I can proceed on my merry way.) I have to be very quick though.

In either scenario 1 or 2 the only way out is to ctrl-alt-esc and force quit.

Maybe it was looking for a file or volume that isn't there, or checking for updates, and unable to establish an internet connection.

[James Steele]

FWIW. I updated and ran into a weird problem.

When I launch DP it runs through it's start up sequence and presents that "landing page" or whatever you call it (the thing listing projects, links to tutorials, etc.). At this point, one of three things happen:

FWIW, you can disable that starting page thing now on the Mac version.

[nk_e]

FWIW. I updated and ran into a weird problem.

When I launch DP it runs through it's start up sequence and presents that "landing page" or whatever you call it (the thing listing projects, links to tutorials, etc.). At this point, one of three things happen:

FWIW, you can disable that starting page thing now on the Mac version.

Ah! I didn't realize. Cool. Thx.

[James Steele]

No prob. They added it as an option in the DP startup prefs.

[Phil O]

Did you just install Mavericks? I got lots of beach balls while Spotlight was indexing and it took quite a while to index (over an hour). After that it was smooth sailing.

Phil

[mhschmieder]

I was almost in a panic as every project I opened spun forever and required a "Force Quit", but it turned out that this is due to having turned off my RME Fireface UFX before quitting DP the other night. So I started a New Project using the Empty template, and set the audio back to RME from internal, and everything is fine.

I only mention this because it is new behavior, and other might be unpleasantly surprised and scratching their heads (Repair Permissions did not help, nor did quarantining new plug-in updates). There must be some problem with resolving default audio assignments when the original audio device is not connected or set in the project setup, so a New Project is required in order to unravel this problem before restarting with a project you want to work on.

[amadeus_d]

FYI - 7 runs fine with Mavericks

[kurtl]

I had a sudden and weird rash of Kernel panic attacks. Thursday I installed Mavericks and got my UAD2 plugins working correctly. It took a while to get things working right. Then yesterday I had a 4 hour recording session, all went smooth. Later doing what seemed like nothing, Bam! Kernel panics galore! My Mac restarted and went into a panic loop, constantly restarting and going into a weird black screen which I was finally able to take picture of and read it. It helped diagnose what was going on. After I started up in Safe Boot, hold shift while starting, I went to the Apple forum and found a lot of these type of panics, all which looked the same. Long story short, Zapping the NVRAM or PRAM got me out of the loop and restarted the Mac normally, so far. Hold, "command, option, P, and R" on restart is how you zap it. Hold it for a couple of chimes then let go after and it should restart ok.
Turning on MOTU PCIE hardware after start up never was a problem for me. On or Off didn't make any difference.

Another thing I found is this.

From Apple Forums:
A person called "Jonathan" on the Apple Support chat found the solution.

First, he made me remove all files in the Library/LaunchAgents, Library/LaunchDaemons and Library/StartupItems folders.

Then, in the Users and Groups menu, he made me remove all startup applications for my account.

And now my MBP starts as before.


https://discussions.apple.com/thread/5478243?tstart=0

I did all this but it didn't seem to do anything to end the Kernel Panics. Zapping the PRAM did.

Oh I Love Upgrades!!!

[MIDI Life Crisis]

Yeah. PRAM and repair permissions. People underestimate their value. When zapping PRAM it's a good idea to let the Mac chime 3 times. That is, start to boot 3x. It is supposed to clear the VRAM as well. Might be old news but it won't hurt.

[teek]

Yup, same here with all the Kernel Panics but after the Zap and Repair Permissions the OS was booting and behaving fine but DP has been exhibiting some strange behavior such as it crashed on me twice while trying to sync to an external source (I haven't had any problems with that on ML) and then for some unknown reason it would not let me access some of the menu commands such as File / Quit and a few other key commands but when I did get it to exit the standard splash screen just went completely blank (white) and then I had to Force Quit anyway.

I should point out here that the first time was as an upgrade to ML on a cloned boot disk to see how Mavericks handled installing that way - Not so favorably as I continued to have major problems so deleted the whole thing and tried a 'clean' install and Mav's seemed much happier going on that way and then used the Migration Assistant to move everything over from ML (DP still isn't terribly happy).

I think I'm sticking to Mountain Lion for awhile until Apple AND Developers get it together on Mavericks. I'll try again later after the first OS update is released along with DP 8.06 or better. Don't really have time to be a BETA tester right now.

[mikeka]

Zapping the NVRAM or PRAM got me out of the loop and restarted the Mac normally, so far. Hold, "command, option, P, and R" on restart is how you zap it. Hold it for a couple of chimes then let go after and it should restart ok.

Another thing I found is this.

From Apple Forums:
A person called "Jonathan" on the Apple Support chat found the solution.

First, he made me remove all files in the Library/LaunchAgents, Library/LaunchDaemons and Library/StartupItems folders.

Then, in the Users and Groups menu, he made me remove all startup applications for my account.

YMMV as they say. Zapping the PRAM (4X chime) on my machine had absolutely no effect. And an Apple tech had me remove all of the same startup items mentioned above. That procedure rendered my machine totally inoperable requiring wiping the boot drive completely and re-installing an older system. Hours and hours wasted. In my 30 years of using Apple OS I've never seen a new release cause so much damage.

[MIDI Life Crisis]

Perhaps, but you might want to try this:

• GO to System Preferences>Security & Privacy

• Select the Privacy tab at the top

• Select Accessibility from the list at the left and see if any of the apps in question are in the box to the right.

• If they are, unlock the dialogue box with your system password and check that app.

Little Snitch, Quickeys, Snapper, and Steer Mouse all needed to be "approved" by me before they worked. If you are using an external sync, I suspect you might find the app attempting to access "control" of you machine in that box.

I don't know that there is a way to add a specific app to the list unless they request access. I believe the default is to deny access.

None of this may be of any help to you at all, but it's worth knowing about, regardless.

[mikehalloran]

I think I'm sticking to Mountain Lion for awhile until Apple AND Developers get it together on Mavericks.

I am one of many for whom Mavericks fixed some issues I had with DP 8.05.

Reading through your problems, I have a feeling that they aren't going to go away until you get good at reading crash reports,

With me, it was Lion. I had a piece of shareware called Bresink and I had Spin Doctor from Roxio included w/ Toast 11. With ML, it was my ATI 5770 video card conflicting with MOTU Audio Setup.app (turn off the app when done id the fix). You are going to find that your extensive kernel panics are not being caused by DP 8.05 / Mavericks - or else a whole bunch of us would have them too.