Ops... guess I was missing something :-)

Thanks for the heads up, quattroquarti!

see ya

Hi Daniel,

first impressions:

- Matthias said about this driver (2.66), it would NOT cure the problem. You say it MIGHT. Is yours another subrelease with the same number?
- I just installed the file YOU linked and restarted my Mac Pro with the FF800 turned OFF.
- After boot-up, I turned the FF800 ON.
- Autostart of FF Settings and Mixer does NOT work (as always since the problems occured - autostart only works for me when the FF800 is started BEFORE the Mac).
- Testing Freeze problem NOW...

... pleasepleaseplease...

- Logic did NOT freeze on start-up. It's running in the background now.

So I'll watch this for a few days and cold starts. Maybe this is the driver to go? However, Autostart still doesn't work for me. I have to start Settings and Mixer manually.

Best regards,

Christian

Sad to hear that. It sort of resembles my situation... As described above, when I follow this procedure Logic hangs at "Initializing Core Audio" (didn't try iTunes or else as I use the optical SPDIF for regular audio) and subsequently my whole system freezes - no clean shutdown possible (only reboot via ssh). Your experience sounds familiar...

Eagerly awaiting own tests of the fresh 2.66 driver!

I have installed this driver - 2.66 "NEW":

Hello,

sorry for the confusion about the version number. This was just a test...

Just uploaded a new file with a new version number. Official download to follow.

Regards
Daniel Fuchs
RME

A correctly renumbered version is now available here:

https://archiv.rme-audio.de/download/fi … 86_267.zip

This one uses a different launch agent to see if the problem is caused by that application.

Thanks for trying it.

Hello,

Small report:

1. I have installed driver called 2.67 by MC (however there is folder called 2.66 inside zip, and I can read I have 2.66 in FF Settings).
2. Woke up my MBP twice from sleep (wake up-->switch FF800 on-->open audio app-->OK-->switch FF800 off-->Sleep-->wake up...)

Looks like it works. But the same I said yesterday... Unfortunately too fast.

Call you later :-)

RobR

Hi!

Since i had updated to v2.65 i was not having any troubles with the driver, but i never turn my fireface off, only using sleep mode.
But i am always using the latest drivers and testing. Anyways the latest zip from MC v2.67 is also 2.66 for me (but i guess this is ok because it was already stated that its only a test).

But the 64 bit driver transition is still in full progress i guess, the midi plugin is still 32 bit, resulting the midi server to be restarted on my system. The developer team is hopefully now on the right way to fix the problems, its taking some time now (maybe too long for some of us...).

Lets hope the problems get fixed and the driver will soon be completely written for 64 bit snow leopard without any problems.

Stability is first (so first lets get rid of the problems), but the fixing takes already a few months now, and i am slowly worried on the progress on other fronts, like new driver features or the missing digicheck features on mac compared to the windows world.

Greets Urknall

Spent all evening trying to get my computer to work - major hangs, freezes and reboots. Trying to do music is a waste of time. I therefore removed all traces of the RME400 from my system and my computer now works like a dream. Whatever the conflict is between Snow Leopard and RME drivers, it's pretty dammed major and I've come to the end of the road with messing around. I've rigged up my Quantum DBX to the Mac Pro and my genelecs - so at least I can work! I'll just wait until RME and or apple sort this mess out..........

I agree that the situation seemed even worse with the new driver, which is why I removed all trace of RME from my system until the matter is resolved.

But today, maybe the cavalry has arrived............I too received an email from apple and have just sent them copy of recent crash reports and system profile report. Lets hope that with their input RME can resolve the problem.

I think that freezes and crashes are one and the same thing - kernel panics!! What tended to happen to me was that applications would firstly hang and take ages to open - I'm talking 3 or 4 minutes - then eventually everything would freeze, requiring the Mac to be powered off. If I could get into to apple>restart or apple>shutdown I would get a major computer crash - dark screen with the text in the centre of screen, so I stopped doing that. It was also impossible to get into system utilities or activity monitor for clues. I always did the pram reset and run disc utility afterwards. The biggest difficulty is that with so many freezes/crashes, we don't know what damage is being done to the system drive. I think we end up with additional problems caused by the crashes, unrelated to the initial cause; ie the RME drive conflict. It's why I eventually sent my computer to a Mac dealer to check that memory and drives were okay (and to rule out as the cause of the problems), and to repair any damage to the system drive. It'll be interesting to see what apple come up with.

Anyway, you need to go to apple>about this mac>more info and then just select file>save as - That will save the file as MacPro spx file, mine was about 2.5 mb, and that's what you send to apple.

i'm tried to use 2.67 ver driver - nothing changed.
RME - pleeeease! find way to solve the problem. A lot of crashes, freezes and bug reports was sent to apple, i cant believe that nobody was read and analyzed their. Pleeeeeease!

Deafening silence... Everybody left their dead fireface home and went on holidays.

Knock! Knock!
Is anybody home? Any new drivers?

RobR

same problem here.

Macbook pro (Late 2008) Unibody 2.53 & FF400 & Snow Leopard
Firewire revision 6, I use it with External Seagate HD, which was work in Leopard 10.5 without problems.

It work only when i plug it to computer first time after reboot.

When i try to plug it after sleep, it freeze my computer, and need hot restart, which is bad for computer.
All last drivers have same problem.

Hope that RME find solution soon.

Thanks

It's the same here, with my Mac Pro and my FF800.
:-(

Ciao,
Marco

After having the same problems with total system freezes using the 2.66 (ans older) drivers I installed the unofficial 2.67. Before that I removed the old version as told here in the forum.

Until now (4 days using Logic) I had no problems anymore with instability. Even when turning on my FF after my Mac.

It took a while for RME, but it seems to work for now.

Beeing a graphic designer I encountered loads of incompatibility of Adobe software after Apple system changes. So I do not blame a relatively small company as RME for the problems these changes might trigger. It seems that Apple is not very thorough in keeping hard- and software compatible when they ? once again ? have decided their system needs a new direction.

If Microsoft would be that ignorant the computer- and officeworld would have a lot more serious problems.

RME devices sound terrific and although I hoped for a bit quicker solution I will not stop using their stuff.

Cheers mates.

I used the RME400 on Leopard without problem. So for me, (sorry if I'm stating the obvious) the conflict is clearly between the RME400 driver and Snow Leopard, or something in Snow Leopard. Like some users, I had periods where things appeared to work fine, then not.

After too many crashes and problems, I had my Mac Pro checked by an authorized Mac dealer, and upon its return to me, it was fine for a few days, then started acting up again. I eventually removed all traces of the RME400 driver last week, but then still had problems - no freezes, but applications were hanging and taking longer than they should, then one of my 4 drives inexplicably failed. So my Mac is now back with the mac dealer.

Prior to that I had given apple the information they asked for concerning the RME problem.

My reason for saying this is that the ongoing kernel panics, crashes and freezes are eventually going to cause additional problems to the computer hard drives, so that there are then numerous problems, not just the root cause, thus making whatever is causing the conflict to begin with even harder to identify. I don't know if this is something that all users experiencing problems with the RME drivers have considered? I've spent a lot of my time trying to fathom this problem and I believe that the issues my computer have had were triggered by the RME drivers in the new OS of Snow Leopard, but I don't think it's right to apportion blame on RME.

As a pro user, I find all this frustrating beyond belief. I've lost time and money over it and I want to use RME400, not anyone else's audio interface. From what I know of the complexities of Snow Leopard and from what I've seen on this forum, it appears that RME are trying to resolve what is a very complex and opaque problem brought about by the new Apple OS. However, with apple now involved, hopefully a solution will be forthcoming, sooner rather than later.

I don't know how long are you working with RME stuff... myself over than 10 years! In all this time, there was something really solid on their stuff: the drivers. As we said hundred of times, "Rock Solid". Is the first time in all that time that we're having problems,... it wouldn't be honest if we don't give them an opportunity, or two, or whatever!

Peace!

P.

Sehr geehrter Herr Logico

You wrote a mail to me on 14 Feb, and got an answer from the main developer including debug code on 15 (yes, one day later), cc'ed to me and the support. To quote you: so far no reaction :-)

Maybe you should check your spam folders...

That was only to make sure this one is really correct (sehr dubios, IMHO). The mail had been from Martin Bjoernsen, 484 kB size (not too big).

Mail sent.

I had huge freezing problems with the 2.64 - 2.66 drivers.
The only way to avoid it was to make sure that the Fireface was on before I booted up my mac.
I was almost convinced that this was a Snow Leopard/Firewire issue that maybe would be mended when 10.6.3 arrives.
But I got tired of waiting so I decided to delete the drivers and start from scratch, with 2.67, following this instructions:

[large]Remove the RME Fireface driver and apps on Mac OS X[/large]

Just send all the files listed below to the Trash.

/Applications/Fireface Mixer
/Applications/Fireface Settings
/Library/Audio/MIDI Drivers/Fireface MIDI.plugin
/System/Library/Extensions/FirefaceAudioDriver.kext
/Users/username/Library/Preferences/Fireface folder
/Users/username/Library/Preferences/com.rme.FirefaceMixer.plist
/Users/username/Library/Preferences/com.rme.FirefaceSettings.plist

When using the new Snow Leopard driver also delete:
/Library/LaunchAgents/de.rme-audio.firefaceAgent.plist

After trashing everything I restarted my Mac and installed the new drivers.
and.... IT WORKS NOW!!!

I haven't had a single freeze in 24 hours of work.
And I started the Fireface after computer boot, even after I started Logic.
I put my computer to sleep with the Fireface still on > Woke the computer and it still works!
I put my computer to sleep with the Fireface turned off > Woke the computer turned on the Fireface and it still works!

I'm not sure this will work for everyone but it has certainly worked for me.

+ 500 million!!!