Pleeeeeeease help! - I'm happily using an ProTools LE002 (rack) with a Panther G5, and have Logic Pro(6) installed on the drive.
When I try to open Logic, error boxes open up:
1 - DAE No Audio hardware found (-9025)
2 - Error code 25974 returned by Core Audio driver

If I 'continue' despite the above I also get:
Error trying to sync Audio and Midi

also I've had:
Error code by DAE -1133
and
Error code -2 returned by Core Audio

I did have Logic working after a fashion (but previously to installing and uninstalling a Waves demo package and repairing permissions)
Thanks
Bloot

I forgot to mention the results of the above error codes - were that I had no sound output through the 002 rack, but on the internal speaker the sounds were like like a gravelly telephone going at half speed.

Since my last post I've gathered some references which I thought I should post, having posed the question.....


1 - error code 25974 ...rambling thoughts & fixes
Interesting note. I launch logic and it intializes core audio thereby launching the digi core audio driver app (without any core audio errors) and everything appears to be fine. If I then change core audio driver to none - hit the relaunch button - it of course returns the "no driver selected" alert. Then I switch back to the digi 002 and hit the "ok" button,
click the done button,
quit logic (without saving the autoload song)
relaunch logic,
The "initializing core audio" comes up on the splash screen and core audio launches in the menu bar (like usual).....BUT core audio cannot see the digi002.....the connection is lost and the 25974 alert pops up when logic launches.
So I assume its a connection error. When I take a look at the launched digigdesign core audio manager it says the digi002 is disconnected and hitting the connect button does not connect it even when hit repeatedly. Quitting that and launching the digidesign core audio setup app brings the alert that the device (digi002) cannot be found.
Power cycling the digi002 solves this.
I've repeated this same "glitch" several times with logic. So that may be one way that the connection to the digi is lost and the 25974 core audio error shows up.
The only thing that seems to correct it so far is to make sure you save the autoload song after you change the hardware driver under core audio in the hardware setup preferences.
Hope that helps someone. --E

2 - error code 25974 ...rambling thoughts & fixes
Running into this error now with logic 6 and my digi 002. A full search across the entire sonik forums for error code 25974 turned up only one post that had no replies.
I wasn't getting this earlier today, and changed nothing as far as the core audio driver was concerned. It just vanished from Logic, and from the system preferences under audio.
I went into core audio manager in the digidesign folder and opened it and "reconnnected" the digi002 (the digi002 was showing as disconnected). After that the digi002 was showing as an option in the audio on system preferences...but not selected because I read here that the core audio driver can only have one application at a time accessing it. it was also showing non-italicized in logic I guess meaning logic was seeing it as well.
Reselecting it in preferences and rebooting logic turned up the error 25974 after launch even after it being "reconnected", but upon powering the digi002 and powering it back up.....it goes away and things are back till normal----(until the digi002 (or whatever application involved) finds a way to "disconnect" once again in the future. Hope that helps somebody

3 - error code 25974 ...rambling thoughts & fixes
firewire 410 crashes
solo-act:
.but not selected because I read here that the core audio driver can only have one application at a time accessing it.
That's not exactly the case.
True, you shouldn't have the default audio. or the system audio. assigned to the same device as Logic, or your other pro audio apps.
Mainly because all sorts of apps, and even the finder, can access those clients, which can bring about conflict [mainly from changing samplerates] when you use the output in Logic.
If you have multiple Pro audio apps accessing the same driver, it is usually OK, since you have the ability to manage samplerate settings, etc yourself.
The current Digi coreaudio driver is multiclient. So it is possible to assign it in several places.
It's also a bit quirky, and, in my experience likes to just die every so often.
In most cases, I have found, quitting Logic, then quitting and/or restarting the DigiCoreAudio Manager before restarting Logic, will often bring it back to life. Sometimes it is necessary to restart the computer though. [and, in my case, power-cycle the 882/20]
On the other hand, getting the digi coreaudio working as default output has been a total crap-shoot. A third of the time it works, but it seems by pure chance.


DAE error -9025 when launching an application.
This error means that an internal data structure had not been assigned to a "deck"object. This could be triggered by a problem in the DAE application (like a third party sequencer), a problem in DAE itself, or unsupported hardware.
Verify that all needed software and drivers are present in the DAE Folder, and that the versions of DAE and the DAE application are compatible with the installed hardware. (For example, launching Logic Audio with DAE 1.09 on Sound Tools II hardware will post a -9025 error. Installing DAE 1.3 resolves this.)


1 - 1133 error on launch of Pro Tools 6.1.x
In one case, after following other Answerbase recommendations for this error code, uninstalling the software (using the custom install option), then deleting the entire digidesign folder from the applications folder, and then reinstalling Pro Tools LE solved the problem.
Also, check that date and time system preference is set to the correct time, date, and year.

2 - "Error -1133, hardware in use" when launching Media Station|PT or "Flamethrower in use" when launching Pro Tools 6.9
These errors will occur if one of the applications is already open and using the Avid DNA hardware (Mojo or V10). You must quit Pro Tools before launching Media Station|PT, or quit Media Station before launching Pro Tools.


......there seems to be some vague pointers here, but I'd appreciate any more positive help or ideas.
TIA
Bloot

Since I haven't had any help from this group, but I have from elsewhere - to help any other complete Mac noobies like me, I'm posting the reply I received (which by the way completely cured the errors on my system!) -


"Here are a few things to try which I think should nail the problem.



1:- Firstly, verify OS and application compatibility. This is obviously important for Logic but also for Digidesign software as this is what Logic is running through.

If you are running Panther as your post suggests, you should be running one the following combinations-

Mac OSX 10.3.2 and ProTools 6.2.3

Mac OSX 10.3.4/5 and ProTools 6.4

Or Mac OSX 10.3.8 and ProTools 6.9

For more info on this visit www.digidesign.com/compato

Also ensure the version of Logic is fully updated and compatible with your current OS.





2:- Have you tried trashing all preferences? Follow this path, Macintosh HD>fredlloyd>Library>Preferences

In this folder there should be loads of preference files. Locate any of these files that are anything to do with Logic or Digidesign and drag them to your trash. Do not empty your trash of these files just yet as we may need to revert back to them. All this process has done is deleted the preferences for each application, forcing each application to write new, and more importantly, current preference files upon next boot. After this, reboot the machine. Then boot logic again. The Logic assistant should hopefully pop up and ask you to set your preferences. Ensure your 002 is powered up and connected to your mac at this point. Set the preferences as appropriate.



3:- Open your Digidesign Core Audio Manager and ensure that Logic is in the list of supported applications, dependant on which version of the manager you are running.



4:- Open Audio MIDI Setup from your utilities folder and make sure that Mac OS is seeing the 002 as both an audio and a MIDI device. Make any necessary MIDI connections as required.



5:- Make sure that the only audio preference in Logic is set to CoreAudio. The DAE errors you are getting should not be there as you are not running a ProTools TDM system. With this in mind locate your plugins folder for both ProTools and Logic and erase any evidence of anything along the lines of ESBsystembridge or TDMEnabler. Essentially anything in the ProTools plugin folder that is really from Logic and vice versa.



6:- If you are not using any digital I/O, make sure the clock sync is set to internal. If you are using digital I/O select whichever you are using as your clock source. ie if you have any ADAT optical signals going into your 002 for recording, use the ADAT as your clock source.



7:- Repair your disk permissions from your Disk Utility."