MOTUnation.com

Virtually every time I launch DP (5.13, 6.03, or 7.24) I have to go through this rather involved process:
-Launch DP…goes fine until….
-“The Audio Hardware did not respond…..”
-I’m given a choice of hardware set-up or studio set-up
-I choose either one and “ok” it.
-DP continues to load and asks me which session to open.
-I choose a session and click “open”
-DP reads session, opens and proceeds to open VI’s
-VI’s vanish
-“The audio hardware’s state changed while MAS was running….”
-I choose “continue”
-“The MOTU Audio System has been turned off, you may be able to turn it back on….”
-Through the set-up menu, I turn on the MOTU audio system
-VI’s re-load and everything’s good…I’m ready to roll!!
I’ve gotten used to this routine…it’s really a minor annoyance. But, I can’t help feeling that it’s not supposed to be this involved!
Is there anything you can offer me in the way of advice to correct this situation??
It would be SO SWEET to simply start the program and roll!
I use a 24” iMac, digi 002, OSX 10.5.8, 4 gig ram.
I run pro tools regularly as well (LE 8.01)
Thanks for any help you can offer!!

J. Murphy

I've heard that the core audio drivers for the 002s are really bad. That might be the reason...

Wow! 43 views...is this the definitive answer???
Once I go through the "ritual" DP works great, absolutely rock solid..
Isn't there anyone out there that uses digi hardware and has found a solution for this???

J. Murphy

I can't speak to the Digi002 drivers. But if my system had become that looney tunes, I would simply reinstall everything: DP and the Digi drivers, just to see if it was a bad install (you'd be amazed how often). If that didn't work, I'd start with MOTU support.

murphymusic wrote:Wow! 43 views...is this the definitive answer???

Careful. Those if us here to help don't always know the right answer, but we're not tech support and we're not paid and, believe it or not, we also have lives and careers.

If you don't get an answer right away (or at all) maybe no one else has the problem or can figure out your problem. I've read it a few times and don't know what to tell you, except this:

Chill!

Oh, BTW, thank you, Future Legends for responding. I'm sorry you didn't get a more 'appreciative' response for your very kindly taking the time to give the o/p a clue.

Gimme, gimme, gimme...

What a Tool!
Didn't mean to ruffle any feathers here...just looking for some advice.
My issue is a "minor annoyance" you seem to be more annoyed w/me than I am w/my start-up routine.
I am certainly not expecting, or begging, or demanding anything of any of you. I am simply hoping that someone here can help. I am in no hurry (chilled). "gimme,gimme +shaking head"...you are a mean one (childish, hurtful) Mr. MIDILIFECRISIS

Thanks to all that have responded thus far...hopefully I will get even more info (before I'm banned)

Wow! Two responses and that's all you got? Yes, I am a tool but not the kind you think. I actually fix crap like what you're experiencing and much worse. You need to work on your people skills.

Oh BTW, with all you've experienced have you contacted MOTU even once?

I didn't think so.

>...just looking for some advice<

And you got some good advice, too.

My first thought is a problem I've not run into since OS 8 or 9. Remember the problems you could get by extensions not loading in the right order?

Anyway, the 002 drivers do have a reputation for not being great.

I'd be looking at whatever else starts up with your computer. See what processes load automatically. Sometimes, preferences can load old garbage and mess things up.

You have three versions of DP loaded - how many other old versions that no longer run? There are instructions on MOTU support for purging these old, hidden files. I'd start there.

And to add to Mike's comments (sorry, but this tool keeps workin' for the good of the community... LOL) given the various versions of DP running, one would suspect the MAS AudioUnit Support.bundle as a very likely culprit. How does one check and fix that?

Clearly, one needs to access just the right tool...

Sweet!

13 posts in 4+ years
& he demands service!!!
I think the annoying startup ritual is based on his posting frequency & etiquette!
Where's my tool box?
lol
Vrmmmmm Vrmmmmm Vrmmmmm

kgdrum wrote:13 posts in 4+ years & he demands service!!! Where's my tool box?
lol

I got ya toolbox right heeeree! But don't begrudge him for not posting. It's working for him, obviously, and he has his procedure down to a science:

• Launch DP…goes fine until….
• “The Audio Hardware did not respond…..”
• Given a choice of hardware set-up or studio set-up
• Choose either one and “ok” it.
• DP continues to load and asks which session to open.
• Choose a session and click “open”
• DP reads session, opens and proceeds to open VI’s
• VI’s vanish
• “The audio hardware’s state changed while MAS was running….”
• Choose “continue”
• “The MOTU Audio System has been turned off, you may be able to turn it back on….”
• Through the set-up menu, turn on the MOTU audio system
• VI’s re-load and everything’s good…ready to roll!!

We should make that a sticky... of what NOT to do to solve your long term "DP" problems.

Of course, a simple call to MOTU could solve that problem in under 5 minutes. Just give them your name and serial number and you're in business. And if one has been with DP since version 5.13, one would presume a user would have had some contact with the manufacturer regarding a problem covering several years. The elephant in the room remaining (once again) why hasn't such a member (in the truest sense of that word) called MOTU on the problem?

Someone pass the 3 in 1 oil. I could use a hit about now...

When do you think the drivers for the 002 were made? and what OS?

Some of you folks are being unnecessarily mean to the OP. I don't think he meant his initial comment anywhere near as insensitively as it has been taken.

Try not to let this get to you murphymusic. I hope you manage to resolve this issue, since there should normally be no rituals like you've been facing when running DP.

When I get the MOTU Audio System shutting down, it is usually something acting up in my MOTU 2408 mkII hardware unit (and presumably the fact that it is getting it's clock information from an external ADC). Usually restarting the computer and all devices, plus making sure that the cables are all firmly in place makes the problem go away. Your situation sounds a little more complex than that though.

MLC. Bad tool,very bad tool.....

Maybe so. perhaps I need to retool...