My FF 800 works great for me under SL.  Maybe because I did a fresh SL install and not a upgrade from Tiger or Leopard...

Hi there, thanks for all the work, the new driver works for me. No more panics.

Logic 8 Waveburner.
FF800
Latest Snow Leopard

Model Name:    MacBook Pro
  Model Identifier:    MacBookPro3,1
  Processor Name:    Intel Core 2 Duo
  Processor Speed:    2.2 GHz
  Number Of Processors:    1
  Total Number Of Cores:    2
  L2 Cache:    4 MB
  Memory:    4 GB
  Bus Speed:    800 MHz
  Boot ROM Version:    MBP31.0070.B07
  SMC Version (system):    1.16f11
  Serial Number (system):    3R7226WUX91
  Hardware UUID:    00000000-0000-1000-8000-001B63918A23
  Sudden Motion Sensor:
  State:    Enabled

I have to take this back. Today it hang my system again and I am able to reproduce.

/K

I"m starting to loose faith...3 months now that I bought my new mac and I have to reboot each time I want to use the fireface...

as a professional guitar player / musician, I do endorse many compagnies like PRS, T-rex, Fryette amps...I have a few contacts and I phoned apogee's distributor yesterday. we may have an arrangement.

it's now 3 months that I bought my new mac and the fireface freezes my logic until I reboot the mac...and we don't have no info or help.

it's just UNACCEPTABLE.

Just to chime in...

I am running an RME FF800 (driver v2.64a, firmware v2.70) with OS 10.6.2, 17" MacBook Pro 2,1 with no problems whatsoever...

I am not defending RME but my FF has been running flawlessly

OK, I've had a crash! On inserting the FW cable while Mac is running. But it is still better than before...

One thing I've noticed, is that on removing FW cable, the output has to be manually set to Safari etc. This has been the case since 10.6 (I think) but may be an artefact of the FF800 driver.

Keep up the good work, Apple is being naughty about Firewire I think. Amongst other things.

FF800 working great for me.... However, Digidesign 003R will take out Core audio everytime I use it on 10.6.2

I should elaborate......

If I am running along all well and good with LogicPro9 and my Fireface800 and decide to turn on my 003R, it will reset the Firewire buss and take out Logic and the Fireface..  Full freeze, no kernel panic or anything fancy, I have to hold the power button on the MacPro and hard reset it.
(MacPro 2.8 8 Core / 6gigRAM / FF800 running 2.65 / OSX.6.2)

This is the first issue I've ever contacted RME about after 10 years of using their interfaces (up to now they were rock solid). Since October, my ticket was chronically neglected and support (when I called after a week of painfully unproductive email correspondence) was extremely misinformed (they said no one was having the problems we are all having here), was extremely condescending and otherwise completely unhelpful. I gave up hope in the support department, so I went to the forum and the first inclination of the admin (MC) was to insult me (see thread). He simply ignored subsequent inquiries.

Great gear (when it works). Disgusting PR.

I agree !!!!

Thx, I did it, but... my trouble yet here: Problem with sync audio and midi has not disappeared. (

v. 2.65, ff400, iMac 6.1, 10.6.2

Well, host is not guilty, but FF400...

P.S. I start Logic 9.1, but it only 32Bit. (
P.P.S. Oops, I stumbled...
1. Quit Logic Pro, if it is running.
2. Navigate to and select the Logic Pro application in the Applications folder.
3. Choose Get Info from the Finder File menu.
4. Enable the "Open in 32-bit mode" checkbox to run Logic Pro in 32-bit mode. Disable the check-box to run Logic Pro in 64-bit-mode.

Damn. I spoke to soon. I thought my testing was exhaustive enough, but it would seem actually leaving the house with my laptop makes all the difference. I plugged my FF400 into the laptop, plugged the power cable into the back of the FF, and viola--instant computer freeze! I don't even need to start Logic or other Core Audio app to cause a panic. While the FF was attached yesterday, I also had a freeze I couldn't explain. My conclusion now is that both freezes are related. I don't have such freezes when the FF is not attached. I believe it is more of a process hang rather than a panic. Multiple errors in the console log refer the following file at the point of the lock-up:

/Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio

I see elsewhere on the forum that other people have noted the same error.
http://www.rme-audio.de/forum/viewtopic … 470#p31470

There is an interesting thread here which is not exclusive to RME users that suggests disabling that plugin toward the end of the thread if DVCPRO is not going to be used in your work flow.
http://discussions.apple.com/thread.jsp … ID=2141503

I think I'll give that a try.

Yep, thinking about going for an Apogee Ensemble and selling the Fireface 800. Seems that Apple and Apogee have it together when it comes to updates:

http://www.gearslutz.com/board/new-prod … 2-1-a.html

"Apogee Electronics is pleased to announce full product line compatibility with Apple's recent Logic 9.1 and MainStage 2.1 update. All Apogee Control Panel functions and features work seamlessly in 64bit and 32bit mode. No Apogee software updates are required.

Products benefitting from the Apple update:
?    ONE
?    GiO
?    Duet
?    Ensemble
?    Symphony, Symphony Mobile"

Same day as Logic 9.1 was released.

Hello,

The problem with this problem, if you will, is the fact that (as MC has pointed out several times, e.g. at the beginning of this thread) the issue can not be reliably reproduced on our systems. Also, as can be observed in this very thread, there are users on whose systems the problem/s disappeared with 2.65. It has also been stated that for the moment, we can only advise against using sleep mode.

In the absence of a reliable way to reproduce the issue, it is rather difficult to determine whether this is (predominantly or exclusively) an RME or Apple issue. This is something that those who utter attacks here might want to consider. Furthermore, without exact reproducibility, it is also difficult for Apple to help us find the cause.

scottkrk's summary in post #66 is quite good, to the best of my understanding of this issue, but I'm not sure what kind of "status report" he'd expect, besides "nothing new yet"... If and when we reach conclusions, we will communicate them immediately.

Is there anyone here from Germany with a machine (preferrably Macbook) where the issue is 100% reproducible in an exact way, i.e. sequence of steps? If yes, would this user be willing to let our developers examine his machine for a while? Maybe this would help track down something. Mind that a conclusion could possibly be that this is after all an Apple issue which we are unable to fix in the driver or firmware (as was the case with the Agere FW chip issue). I'm far from blaming Apple here, of course, but the possibility can't be ruled out entirely, can it?

Kind regards
Daniel Fuchs
RME

PS: The above comment on Apogee and Logic is IMHO quite OT and irrelevant to this issue.

RME Support: Thanks for the informative, constructive post. Out of curiosity, why isn't RME interested in crash and hang data from users? When I first brought up this issue to support in October and asked if I could forward logs, I was flat out refused. I agree that Apple could be at fault here as my last hang indicates a problem with DVCPROHDAudio, and people without RME devices are complaining of similarly described problems on Apple's site, but it seems to me that analyzing our logs would provide some consistent insight. Am I being simplistic?

I doubt it was you I spoke to. You seem much more interested and genuinely helpful than the person I corresponded with. I deleted my old logs and email thread because it wasn't getting me anywhere at the time. I'll keep any new ones I am able to obtain and send them to you directly if I can come up with anything valuable.

Daniel,

I think the problem here is that there is not much faith you folks are *really* working
on this.  You have not stated, for instance, that you have developers dedicated to the
problem.  You state that it happens on your machines, but not all the time - welcome
to the world of code debugging - you instrument and you keep trying.  Have you been
working the problem for the 3-4 months it seems to have existed?

It would appear that this is related to Snow Leopard.  Are you actively working w/ Apple
developers?  How long have you been working with them?  Have there been candidates
for the problem which were confirmed not to be the problem?  What do you suspect is
the problem; or what is the general area in the code/OS you suspect?

These are the sorts of things we'd like to hear.

Given the expertise RME claims to have, I for one find it difficult to believe that you've
really been working on this and it  has eluded you, with or without Apple's help (which
you certainly should be using) for 3 months.

Now you will likely claim that the way you address such problems is internal info only;
and I will reply that you asked, just above, what we'd like to hear.

-Wayne

This gels with my impression as well. I would have expected a set of debugging instructions for advanced users on the forum and an express method of getting logs to the developers by now. I don't get a sense of urgency at all. It feels more like a ghost town in the old west except for those of us who stop by to refuel our horses and stroll into the local saloon for a game of cards, listening to the tall tales of RME legend and myth.

System froze as expected (It's not exactly frozen, but you can't do anything. You can bring up the force quit menu with CMD+OPT+ESC, but you can't do anything after that, so you force quit by holding down your power button for several seconds). There are no further clues in the console log. I'll report back future successes or failure. So far, I have disabled DVCPROHDAudio (in Plugins/HAL) and uninstalled all elements of JacOSX.

yes, I have installed Final Cut Express 4, it's updated.

I have Final Cut Pro 6.0.6 installed. The plugin DVCPROHDAudio may be installed by this, which was causing some freezes on my system. I disabled it, but that doesn't prevent the core audio hang.

Viktor, glad you are having no problems. It helps to see success stories because it points to possible conflicts with other software installations as a possible source of my problems. I'm anxious to see what happens now I have uninstalled JackOSX and DVCPROHDAudio plugin (which I think is part of the FCP install). Out of curiosity, do you have any version of Final Cut installed on your system?

I'd like to know from the people with crashes/issues: What Firewire chipset is build into your Mac (TI or LSI/Agere)?

And what mainboard chipset is build into it (NVidia or Intel)?

Does anyone with PowerPC architecture have the problem (if you managed to make SL work on it)?