Well, the installer (Apple's own) does have the option of complete uninstallation prior to installing the new files turned on. That caused lots of people (read: not all) to have no driver files at all after 'successful' installation...

We have no third party Installer or Uninstaller and don't expect this to change, sorry.

Sorry....
Spoke too soon.

IT'S BACK.

I just powered my fireface unit while typing and the system froze with a beach ball of hell.

Well... somethings definitely fishy with 10.6. Maybe my first assumption that it will be mended in 10.6.3 was correct after all.

No problem for me. I already guessed that the Uninstaller process might have caused troubles in the past which lead to the manual process.

A third party (Un)Installer that makes really sure that all files are being unlocked and deleted would surely be a nice addition, but I understand that this would mainly be a convinience thing for those who don't know how to do installations manually.

I can check Itunes again, but these were my more sophisticated test results:

http://www.rme-audio.de/forum/viewtopic … 778#p35778

Keep in mind that I'm using a FF400 though.

"Sorry....Spoke too soon. IT'S BACK."

Not surprised!

I'm not an 'expert', but I do consider myself a very experienced Mac user (14 years) who has progressed system by system, Desk top computer by desktop computer to my current set up, using Logic, Aperture, Photoshop etc in a professional capacity. I've tried all manner of investigating, isolating apps, I've had my computer checked twice now to ensure my drives and RAM are okay and I've installed Snow Leopard twice. What I know for sure is that everything worked fine in Leopard, so all the problems, kernel panics freezes and crashes have occurred since Snow Leopard was installed. I also never had anything like these problems with any of the previous operating systems - and I was always a user who bought the new OS early.

While the RME drivers may not be helping the problem - there does clearly appear to be a conflict - I am more and more convinced because of my own experience that the problems are triggered by Snow Leopard. My computer has been problematic the last few days (just had everything checked out by the apple dealer) without any RME drivers installed and with nothing connected except a 30"monitor! It seems to have settled down today and is working okay, but for how long? Who knows. I reinstalled 2.66 a couple of hours ago, remove the p.list file and the RME400 appears to be working okay and no issues - yet.

The problems are to inconsistent to make sense, thats the problem. I have exactly the same apps running on a macbook (white 13") and that's working like a dream, never the slightest hint of a problem. Logic, apperture, photoshop etc etc and ALL the same stuff as is on my Mac Pro.

I doubt that somehow because:

1. The hardware did not change (except for IDs). It's still the same NVidia chipset with the same everything.

2. I can swap the harddrive of my 2009 Macbook Pro (17") with my old Leopard clone and it runs like nothing has changed (except for application activation being necessary because of the changed hardware IDs).

Great! New situation here: For one week, I didn't have the time to make music. Before, I had the problem everyone had, but I worked around it by restarting my Mac after the FF800 had been turned on. It was recognised during the grey startup screen.

Today, this doesn't work any more! I sit here, want (and have to!) make music, but five (!!!) restarts and one shutdown plus restart haven't helped: The red light stays on. Ridiculously enough, the red light turns OFF, when I restart the FF800. But then I have the old problem: Audio apps freeze, and the mixer and settings don't autostart. However, when I restarted the Mac today, the red light stayed on, while mixer and setting DID autostart (the settings displaying a sample frequency of "-1073748 kHz").

Guys, this is getting absolutely RIDICULOUS! Now I WANT to :censored work but the FF800 gives me the kick in the head. Never had this before!

Ah yes, and before anybody asks: No, I did NOT change anything particular. One week ago, it worked just like that, today it doesn't.
The only thing that changed in the system: I disconnected my printer and scanner and connected and installed a new printer-scanner combi device by Canon. Connected or not, turned on or not, the red light stays. And NO, I don't think this should be happening, it's just a :censored printer for :censored sake! rant

I should add that I did just that this morning and it's still (fingers tightly crossed!) working, so hopefully I can finish my work today.

Scott, this was one of the very first things people claimed: It's the RAM or it only happens with 4 or more GB of RAM. Hardly anybody has commented on this ever since, but for me it was always a strong contender... I wasn't able to test it on my MacPro yet, but for my MacBook it's true: FF400 running smoothly on 2 GB, crashing on 4.

Best regards,

Christian

Since we are talking about RAM again, let me quote something from the Windows 7 thread that includes a "memory corruption" message by Windows (Macbook Pro 17 2009):

I am also having this problem on my Mac Pro and I have 12GB of RAM.

/K

After my earlier post, I tried to open Logic this evening - I've been working on artwork for the past three days, although I did process a master CD in wave burner and have been listening to itunes without problem.

Complete computer crash. No warning, no reason, aside from opening Logic. The crash was so bad that it rendered my system drive as "beyond repair" when I eventually managed to get the original OS disc into the computer to repair permissions and verify drives.

I have never ever known crashes cause this much chaos and damage to a hard drive - it's insane!

So, I'm erasing my system drive and starting all over again - joy!

Something quite strange happened today (and I'm disgusted that I didn't think of it before - I just FORGOT I had this thing!!!): I crawled behind my machinery and realised I had a Firewire 400/800 expansion card in my MacPro. The external hard disks are connected to it.

So, just for fun, I disconnected the FF800 from the Mac's own FW port and connected it to a FW800 port of the card. I turned on the Fireface, the red light turned off, and the FF settings and mixer autostarted (which hasn't happened even ONCE since I switched to Snow Leopard!).

Logic, however, froze again, during CoreAudio initialization. :-O

So, why's the FF800 happy enough with another FW controller to autostart mixer and settings but still freezes afterwards? Maybe this helps any of the developers?

Here's the MacPro I use (don't know how to find out details on the FW controller):

Hardware-?bersicht:

  Modellname:    Mac Pro
  Modell-Identifizierung:    MacPro1,1
  Prozessortyp:    Dual-Core Intel Xeon
  Prozessorgeschwindigkeit:    2,66 GHz
  Anzahl der Prozessoren:    2
  Gesamtzahl der Kerne:    4
  L2-Cache (pro Prozessor):    4 MB
  Speicher:    5 GB
  Busgeschwindigkeit:    1,33 GHz
  Boot-ROM-Version:    MP11.005C.B08
  SMC-Version (System):    1.7f10
  Seriennummer (System):    YM6326S7UQ2
  Hardware-UUID:    00000000-0000-1000-8000-0017F20034A0

Here's the data of the PCIe card I use:

pci104c,8025:

  Typ:    IEEE 1394 Open HCI
  Treiber installiert:    Ja
  Bus:    PCI
  Steckplatz:    Slot-4@4,2,0
  Hersteller-ID:    0x104c
  Ger?te-ID:    0x8025
  Subsystem-Hersteller-ID:    0x1409
  Subsystem-ID:    0x3110
  Versions-ID:    0x0001

Best regards,

Christian

Hello,

i bought yesterday the FF 400 and it doen'nt work with my Macbook pro early 2009. I used this test driver, but it was'nt better. If you start any audio app like iTunes, no sound, just the red Host led on the FF.
After mailing the support, he means to connect a HD between Mac and FF. It works, but is it your serious?
Is there no other solution for this issue?

I mean, any macuser that bought a mac can not use any Fireface...

Reading this thread after another "mysterious" hang on loading a project in Logic 9.1 in 32 bit mode. In the console I saw:

PlugIn Fireface MIDI.plugin -- /Library/Audio/MIDI Drivers/ does not contain a supported architecture.

That's what brought me here.

Over the past 6-8 months, I have been having a nightmare with hangs/crashes/freezes mainly when launching Logic projects once Logic app is already active. I've also had the RME FF400 host light problem.

I have been all round the houses trying to pin point where the problem lies, and may have had layered problems that are not related - I really don't know. It's been a right mess. It started with Logic 8.0.2 on Leopard - I moved to SL and Logic 9 in an attempt to solve the problems!

I thought it was Nomad Factory plugins to start with, then BFD2 possibly. Then thought it may be the Mac - checked all cores and RAM - seemed fine. Then I suspected the FF. Tried new drivers - seemed better. Hangs continued though. Got rid of the Blue Tubes (Nomad) plugz. Seemed better - was clear of problems for a few days maybe. BUT - then got another hang on project loadup. Nothing to do with Blue Tubes this time it seems.

Overall I get less problems but it still happens - like this one just now.

Back to suspecting RME drivers??

Running:

Mac Pro 2.8GHz 8-core early 2008
10.6.2
FF400 (wall outlet power)
latest drivers
Logic 9.1 32/64
32 bit kernel

Here is a small update. Thanks to user Logico we have verified that the same problem that we found for a short time on our own computers is still the main culprit. The simple call of a standard FireWire command makes - some - computers go hayward. It's the same command that we notified Apple about some time ago, and they were not able to see the error themselves, nor to find an error in our source code. Meanwhile we also have proof that this problem affects the Fireface 800 as well - if the Mac is one of those that poof when connecting the FF too late then it doesn't matter if it is a FF 400 or 800.

Please believe us that the whole situation is highly unsatisfying not only for your but also for us. We continue working on it and hope to have a fix as soon as possible. Until then just use the known workaround and first switch on the FF - or never switch it off.

For now, should I use driver v2.66 or 2.67?
Post #14 here says that "Mac driver 2.66 for SL will not solve the ongoing sleep issue, but includes two important fixes: noise when starting a recoding and invalid SysEx sending via MIDI."
So if 2.67 only use different LaunchAgent, which one is safest?

I always turn on my Fireface 800 first and always have turned off power savings on my MacBook Pro (on hard drives too), and never go in sleep mode during sessions. So I never really experienced or tried to see if I too got the problem talked about in this tread. Got Logic 9.1 crashing some times, but I believe it is not related to the Fireface.

I think it's the end of the RME road for me! I got my Mac Pro back Thursday; to cut a long story short; new hard drive, new graphics card and a new processor. Snow Leopard loaded, ilife and iworks loaded! Works like a dream, as it should - no problem. Installed logic pro 9 - everything fine. No 3rd part software installed. Installed RME400 Drivers 2.66.......................computer doesn't recognize driver. Tried 5 times installing and uninstalling. The most worrying things was that when I did a repair disc permission and verified system disc,  the new drive came up with loads of "invalid...." blurb in red! It was okay beforehand!! Disc repaired, but, I'm now very, very, very unsure about trying to install rme drivers again! Just what the hell is going on here? I think I'll be contacting Digital Village on Monday and insisting on a refund and will change to another make of driver, because whoever is at fault here is irrelevant to me, because I'm a professional who is unable to work because the RME driver doesn't want to work with an apple computer and no-one it seems has a clue why!

An amendment to my post earlier today, my mac pro had a new graphics card and a new logic board, not a new processor. Also, as a point of interest, I spoke to my local mac dealer technician this morning and he tried to download the drivers to, but they wouldn't install on his mac either!

I downloaded the Zip file, open the zip file and installed the driver (6 times). However, neither of the RME apps will open. The RME400 is on (powered) and connected via firewire (as it always has been). When I uninstalled, (to reinstall) I noticed that there an NO items in the user library! The mac technician did the same and the same thing happened to him. Bizarrely, he then experienced "hanging applications" for the first time ever! I don't know what mac he was using, this was done over the telephone this morning.

Tried both and even looked on the net in desperation to see if I could get 2.65 because that worked for me before..........

oops.......apologies on two counts. Firstly for appearing to have taken over this thread, and secondly for posting the wrong text in my previous post at 16:03 - I intended to copy and paste a shorter, more relevant to the thread text account.

In a nutshell, I'm now convinced that my problem has nothing to do with RME drivers, but the RME400 hardware itself! That's the only thing that makes any sense now after all this time and messing around.

Could it be that there are other RME users with problems that have also fixated so much on RME "drivers" that they're missing the less obvious cause is actually the unit itself?

Hopefully I can get a replacement unit to at least test the theory.............

"That said I did not hear about this update before, nor saw anyone using/mentioning it here:

http://support.apple.com/kb/DL1004

Maybe it helps one or the other..."

Came up as "not supported on this system" when I tried to install it on my mac Pro. Simple truth is that for me, everything is working fine at the moment on my computer. When I had 'windows of calm' before, the computer always felt "flakey" as if something was gonna happen. I'm sure other uses who have had problems will know what I mean. Now though, it's firing on all cylinders and aside from getting the firewire port sorted out, there are no issues at all. But, there are no RME drivers installed or perhaps more pertinently, the RME400 isn't connected. Like I said before, if I can get a new RME400 sent to me from synthax or DV then I will give RME one more, final shot.