For what it's worth, I installed this update as soon as it became available (FYI, I got it via a regular Apple software update). It made no difference with regards to the Fireface@SnowLeopard issue (system freeze on Core Audio initialization when FF not switched on before Mac OS).

@davidwright: I suppose you don't use a 2009 Mac Pro, hence this update is not applicable to your hardware.

Cheers

After further problems, apparently with the RME400 audio interface last weekend, all RME drivers and files were removed and the RME hardware returned to the UK distributor Synthax for testing. Still waiting status confirmation of the unit.

The computer problems were kernel panics, spinning wheel, hanging applications, drivers not being recognized and all firewire ports on my computer ceased to function (red error message in 'an about this mac - firewire'). This was resolved by doing PRAM reset, safe boot and repair permissions. Hard drives also verified as okay.

I installed an "alternate" audio interface so that I could work on music.

My mac Pro has been performing perfectly in all ways on everything non music related, ie photo shop, aperture, mail, internet, pages etc etc.

I use my sound system in two ways: Firewire obviously connected between interface and computer. Digital connected via optical connection to a Quantum DBX with in/audio out to interface. I therefore use the DBX in conjunction with the computer's digital mode and when recording analog I use the firewire interface.

I had the firewire connected for two days without problems in digital mode. All sound worked, Logic Pro 9 in 64 bit, itunes, Toast, Peak.........everything seamless and perfect!

Until............I switched the DBX off and ran the audio interface in firewire mode to do some analog recording. After 5 minutes the drivers ceased to be recognized, system hang, kernel panic and eventually lost all firewire ports again!
I uninstalled and reinstalled drivers several times and the same thing happened.

So I did a couple of PRAM resets/safe boots and repair permissions etc as before and that seemed to solve the driver and firewire problem, all ports working. But something is clearly very wrong for this to keep happening.

So this morning I called in an electrician to test my studio electrics (which is on its own circuit) and test all the gear (which has already recently been PAT tested!). Everything is fine, no problems. So I have ruled out any faulty gear, faulty wiring or bizarre electrical behaviour. I've used several firewire cables, so its not the cables. But in any case, because we couldn't work using the main computer last night, I used my mac laptop, running the same 'alternate' drivers running Snow Leopard, the same firewire cables etc, and we worked happily for 5 hours!

So, as at 23.30 today the alternate audio firewire interface has worked "nearly" okay. I had been playing itunes before my evening break. When I came back to the studio the computer had gone to sleep and when I tried itunes again - nothing! Itunes didn't respond. Now, there were no kernel panics this time, but when I eventually turned off the audio driver and disconnected the firewire, itunes worked again. When I reconnected the firewire and audio interface the system continued to work okay.

This would appear to add weight to the sleep problem issue being more to do with "audio devices" and "mac" than a particular driver.

The other points worth mentioning are as follows: by coincidence there was an AMT8 driver update from apple early this morning and apple advised me to remove my 30" apple computer firewire connection and to disconnect my isight camera when using an audio device, both of which I have done.

Since early this evening everything is running okay and I've put the computer to sleep on a couple of occasions for 10 minutes and there have been no problems.

I'm now eagerly awaiting the return of the RME400 to see if that will now work without problem!:-)

I can reproduce this 'lock up' crash problem 100% everytime I turn on my 003R (Digidesign) and the Firewire bus resets. Effectively the same as turning the FF800 off and on again.  It crashes my system (MacPro 2.8 Octocore, running 10.6.2 and latest RME FF driver) every single time, unless I power everything before I boot the Mac.
In other words, I can reproduce this repeatedly... 100% of the time.  Something is up and it never used to behave like this.

Regards,
Matt

(edited: yes incorrect OS version shown.)

I'm not trying to be lazy, but there is a lot to read and though I've read most all of it there seems to still be a lot of conflicting information. So, can anyone please give me a simple (if possible) yes or no as to if the Fireface 800 is finally stable and working with Snow Leopard?  HeadScratch

I'm still using 10.5.8, despite having bought Snow Leopard last years sometime. Wanting to know if it's safe to make the upgrade.

Well, I've given it a long time for the situation to change and if this is the experience users are still having it's time to sell my RME gear and look for an alternative (like the Ensemble). Unfortunately, if so, that's the end of my RME purchases. I can tolerate issues from time to time, but this seems a bit extreme. Good gear that's been great to me, but this is unacceptable. No offense to anyone, but I bought my Mac Pro partially to use with Snow Leopard's features.

Daniel, you've always been helpful, what's the official status on this, if you will?

I feel as though I've been bounced back and forth between RME and apple like a tennis ball over the driver issue, and I've tried to retain a logical approach to discover the cause of the problem/conflict as it relates to my studio set up. I've also been quick enough on this thread to knock the RME drivers.

However, for me the problem is now 99% confirmed to be a hardware issue on my Mac Pro! I'm having exactly the same issues with an alternate firewire audio interface, and also discovered why the problems were not reproduced by the apple technicians trying to find the faults on my computer. I discovered yesterday after exhaustive tests that my Mac Pro only functions properly; ie (bizarrely) only allows audio firewire to function without issue, with the system hard drive installed in bay 1 and the other bays empty. And the same problems were reproduced with the system drive in any of the other bays. I won't go into all the details, but suffice to say all obvious things were checked and double checked. When my mac was away for testing I removed all but the o/s drive in bay 1, thus the problem was never reproduced by the apple technicians.

I strongly suspect than when my RME returns from Synthax and my mac pro is finally repaired (or replaced) the RME will be okay. I'll post again as and when...........

...Or it also crashes if you turn on another connected Firewire device (forcing a reset of the bus) ie, in my case turning on a Digi 003R (different FW port, but as we all know, the various MacPro FW ports share a bus, or something to that effect)

Lets be clear on one fact; forums are populated for the most part by people who are having problems with software and/or hardware, or viewed by people trying to find answers to their hardware/software issues. There are a heck of a lot of users not having problems using apple computers running snow leopard and/or RME drivers. Regrettably, they don't appear to visit forums very much. Why would they? While obviously the issues are immensely frustrating to us users that are affected, I honestly believe that if there was a fundamental problem effecting ALL RME drivers on all apple mac computers worldwide, then it would be fixed pretty dammed quick by both parties. Speaking from experience, I understand just how frustrating it can be and how opaque this issue is, and just how difficult it can be to get to the root cause.

Also no offense, that's my 2p worth!

Should have made clear that I was agreeing with your post Logico. None of us can be certain what is causing our own particular "RME" problem - my experience is a case in point - I'm having the same (and some new ones!) firewire issues using another audio firewire unit after being sure it was the mac, then sure it was snow leopard, then sure it was the RME, only to find myself back at first base with what is almost certainly faulty apple hardware. My mac pro is being collected on Monday morning by apple! Not surprised at what you say about the apple firewire debug!

I'm constantly having issues with the volume knob on my FF400 not being recognized.  I have to reboot multiple times before it works again.  I should note that if I don't connect the computer and use it standalone it works fine every single time.  10.6.2, latest RME drivers, happens 80% of the time at least.  3 times today ina  mixdown session I went to adjust the volume of my monitors and the knob isn't working.  I about threw this incredible sounding interface through the window.

As annoying as it may be you should wage the pros and cons here. How about Midi mapping some spare knob of one of your controllers to volume instead until the issue is resolved.

me too. unit is working, with some limitations though, but i belive it will be fixed soon.

Ditto.

SL 10.6.3 is out, maybe the guys with problems should give it a try.

Greets Urknall

Going to try the update. Hope it works.

Tarekith, is the Fireface Mixer running in the dock already when you try to use the knob?

I just try test my hardware knob ....it works great ....

I also try to unplug and replug FF400 several times... try logic 9.1.1 and ableton 8.1 ....no problems so far....

FF400 now works like it used to .....

I'll keep trying and update .......

At last...
Anyone with the FF800 that can confirm.?

I have a quick question. I went ahead and installed SL last night just updated it to 10.6.3. I'm about to try the Fireface for the first time with SL. However, I only see the 2.6.6 driver, but I see references to a 2.6.7 driver. Where can I find the latter? I don't see it on the main driver page, or was the 2.6.7 just a modified test driver?

I see that in a previous post, MC says that there is no difference between the 2 drivers. Then why have 2?

Doesn't matter anyway... My system just froze again (installed 10.6.3, restarted Mac, turned on FF800 - Mixer and Settings didn't autostart, Logic froze on CoreAudio Init).

Back to square one... :-O

Best regards,

Christian

I had 2.66 installed under 10.6.2 and installed 10.6.3 but the problem with the system freeze is still there.

I will try to uninstall 2.66 and reinstall 2.66 but I doubt that will make a difference.

I will report back.

/K

hey ...

its not possible to reconect the FF400 to my mac pro 4.1 while the os is running :: result total freeze ....

i made a test ...itunes was playing ..i pulled the firewire cable from FF400 and the system switched to the internal speakers but instead to do the same in the oposite direction (connecting FF400 back again) i have got total freeze ....is it the way it should work ????

apple or rme ????

After updating to 10.6.3 I had no problem yesteday. Today after wake up from sleep core audio freeze... forced hard reboot.
Macbook Pro 13" 4GB

sorry if this has been asked before, i did scan this thread briefly.
when booting to 64-bit kernel mode with the 2.66 drivers, the mixer and settings appear as 32-bit
applications in activity monitor. supposed to be that way?
everything else is working great, no freezes or crashes w/ logic 8 on 8.1 imac and ff400.