A very very strange problem. No one could help me. Maybe you

[ady]

Hi,

I'll try to be short and precise.

My setup:
Dual 2GHz PowerPC G5
2 GB SDRAM
OS X 10.4.11
Logic Pro 7
Logic Studio 8

Audio interfaces:
MOTU 828
MOTU 896HD

MIDI interface:
MOTU FastLane USB

Problem:
The communication between my MOTU audio interfaces and the computer's audio
system doesn't work. It used to work for a few years, but since a few weeks ago
it doesn't. In "doesn't work" I mean that when the interface is powered up, and
I try to launch any program, it doesn't let the program open. The little
"rainbow ball" starts to turn and until I turn off the MOTU interface the
program is "stuck". After I turn off the MOTU the program opens normally.

The MOTU hardware and all my cables are definitely NOT the problem. I know this
because when I connect them to my older PowerBook G4 (OS9.1, Logic 4.8.1)
everything works perfectly.

The problem seems to be with the MOTU driver(s). I already tried updating to the
most recent driver, downgrading to an older driver, nothing helps.

I tried MOTU's technical assistance and they have no clue. I tried other
technicians who know their Apple, their Logic and their MOTU and they had no
clue.

My next step is to erase my Hard Disc and re-install everything.

But I hate to do things like this, without knowing what is actually the problem.
I mean, if I don't know the reason for the problem, how do I know that it won't
happen again after I go through all the hassle of erasing and re-installing???

I'm sure that some file or files in my system are probably "clashing" with the
MOTU driver. But only someone who really knows Apple would probably be able to
know which files are they.

Is there a genius here who can help me?

I have so much work waiting for me, so if I don't solve this until tomorrow I'll
have to erase my HD.

Thank you in advance!

Ady

[MIDI Life Crisis]

Have you tried creating a new user account and launching from there? Also, before you wipe your drive, try the devices on another machine if possible.

Another thing you can try right away is delete ALL your Audio/MIDI setups (Apple/s A/M utility, that is) including ALL you MIDI and audio devices. Delete the plist for A/M Utility and create a new profile in the A/M app from scratch. MOTU should have walked you thru that as well as the new user accounts.

[ady]

Dear MIDI Life Crisis,

Your suggestions are very interesting and refreshing, and no, the MOTU guy who answered my TechLink didn't say anything even close to them.

1. I did try my devices on my older PowerBook G4 (I wrote this in my original post) and they work perfectly.

2. I have another user account on my computer already - my 6-year-old son uses it. I just switched to this account, turned on my MOTU 828, and immediately received an error message:
"MOTU Audio
An undefined error has occurred.
File FWCnslApp.cpp, Line 311
Error Code 0".

This was something new already. I clicked OK on the message, didn't turn off the MOTU, and opened an mp3 file with QuickTime.

It worked!!!

I immediately switched to my user account, and... it still works!!!

What's happening here? I hope it will keep on working like it is now, but what about that error message? I'm sure there is something still wrong. If I can solve it without erasing my HD this would be great.

Thank you!

Ady

[jlaudon]

Do you have an extra hard disk you can install OS X on and then install the MOTU drivers to try out (before erasing your present hard disk)? This is to hopefully ensure it's not your hardware (your G5), and/or the firewire ports in your G5

[newrigel]

It used to work for a few years, but since a few weeks ago
it doesn't.
Ady

I know this sounds elementary but you stated "for a few years"...
Was there ANYTHING you installed prior to this problem? I mean ANYTHING! If it was a working configuration (for years) and you didn't update or install anything... the only thing it could be is maybe a corrupt MOTU audio.plist file (or other files too) or a permission problem. If it was a newer session, try opening an older session and see what happens. Is your HD getting pretty full? It could only be something you added recently, or a corrupted file since you stated that this configuration has worked for years.
Hope this helps.

[ady]

Dear jlaudon and HVK,

Have you read my last reply, just above your replies? I think it sheds a lot more light on my problem, doesn't it?

Thanks,

Ady

[stephentayler]

This may be stating the obvious, but I don't see it mentioned here at all.... have you actually repaired permissions yet?

Cheers

Stephen

[ady]

Yeah... Sorry I didn't mention it. That's one of the first things I did when the problem began. I think I did everything possible...

Thanks anyway.

[MIDI Life Crisis]

The fact that it works in Quicktime but not in DP leads me to believe that perhaps your DP program file may be corrupted. The next thing I would do is delete the DP app and ALL associated files and reinstall the app. I would start with the original DP install disk and then go to the latest update you're qualified for. I'd go ahead and delete the drivers and all plist files for DP and the drivers (MIDI and audio).

If this is your only real issue with the machine, there is no good reason to erase your HD. Clearly, the problem is in DP or a MOTU component and the only files that need to be replaced are the ones MOTU installers placed on the disk.

Have you reinstalled the DP prior to this?

And the fact that the MOTU guy didn't suggest a new user account is amazing. It's a basic procedure and they usually suggest it. You must have gotten the guy who I sometimes get. No names - but he's useless. Other techs there are great and probably would have had this fixed in 10 minutes.

[MIDI Life Crisis]

I should also add that I have the same G5 as you but with an M-Audio Firewire 410 for audio. EVERYTIME I open the control panel for that device I get 4 or 5 "exception caught" errors. Then the panel and the device works fine. Tha, as well as my video interface (AVDC 100 or something like that) will also loose connectivity with Firewire.

Even though your cables may work fine elsewhere, you might want to use a different firewire cable. Even a slight data drop can cause problems - as can any loose connection. I'm not a fan of Monster Cable but a decent FW cable might run you $15 at an office or electronics store.

[ady]

Maybe I didn't make myself clear...

Not only Qt works now. Everything works fine now! Even Logic (I don't work with DP at all, only Logic).

I hope it keeps on working. If not, I'll come back to this forum...

Thanks,

Ady

[ady]

So...

Doesn't anyone here know what the following error message -

"MOTU Audio
An undefined error has occurred.
File FWCnslApp.cpp, Line 311
Error Code 0"

means?

Ady

[ady]

My joy from yesterday was too early...

My problem was not solved actually.

What happened after I tried your suggestions was that I returned to the stage where all the problems began, about 6 weeks ago: when I open the MOTU interface, I can launch QT or Logic (and please guys, this is not a matter of Logic 7 or 8, it's a principal problem with the audio of my computer) - then sound comes out but just for 1-2 seconds. Then there's no sound for another 3-4 seconds and again sound comes out for another 1-2 seconds. And so on. In Logic, whenever the sound goes out, I get an error message which says: "Error while trying to synchronize audio and MIDI".

What do you think? This is really strange, as I said in the beginning...

Ady

[SixStringGeek]

So...

Doesn't anyone here know what the following error message -

"MOTU Audio
An undefined error has occurred.
File FWCnslApp.cpp, Line 311
Error Code 0"

means?

Ady

Only MOTU can decode that. Its a typical programmer error message for an error he doesn't think will ever really happen. The file/line number will tell the programmer where in the program the error occurred so he can analyze it. Without the source code to the program, the error message means nothing. Support should be able to figure something out from that. If first line can't (and they probably can't) then insist on escalation.

[MIDI Life Crisis]

... sound comes out but just for 1-2 seconds. Then there's no sound for another 3-4 seconds and again sound comes out for another 1-2 seconds. And so on. In Logic, whenever the sound goes out, I get an error message which says: "Error while trying to synchronize audio and MIDI".

What do you think? This is really strange, as I said in the beginning...

Ady

It sounds like a bad cable. Really. Or a fried FW port? Whatever the cause, it is apparently a connectivity issue. Have you tried a new, quality cable? They don't go bad often, but the can go bad. Might not be that at all, but that'd be a place to start.

You might also try an earlier version of the device driver and also see if a different device yields the same results. It would be worth the restocking fee and who knows, you may simply need a new interface. It happens!!!