I kind of like the Japanese approach.  Fix the problem, not the blame.  I'm sure this has been a thorn in RME's side and they were anxious to fix it.  Bad word of mouth makes if much harder to sell products.  Maybe we can focus on any remaining issue rather than scolding RME?

One thing, as users have reported that 'changing the sample rate' fixes the problem of 'no sound' after disconnecting and re-connecting - would it be possible for RME to fix this one last thing?  Very minor thing to me, I don't ever turn it off until after I shut down my Mac.

Or - as a temporary 'fix' add a button that would essentially 'change the frame rate' and get sound back again?

Also, is the problem totally fixed so that the FF400 can be turned on (for the first time) after the Mac Pro has booted?

Thanks!

hey, RME)
thnx for new driver, but i have two kernel panics in last one day.
one was when itunes was working and im tried to start ableton in same time... Kernel panic.
another one was when my mac wake up after sleep, and no freezes and also no sound. i started itunes with built in output - it plays, then changed output to ff400 - no sound. When im tried to change sample rate - kernel panic...
then appear logs that i was sent to apple. if you need them, where to send it?

macbook pro(early 2008), 4gb ram, 10.6.3, ff400

I fail to see how this is a bug nor why someone should do something as crazy as desribed (pull the cable during playback, plug in again and expect everything just to continue).

Whatever, if you want to do that use driver 2.72:

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

No no, as a German I can assure you that I neither am used to nor like be adressed like that.

Is there any benefit updating to this latest version if I'm still on 10.5.8?
I'm using 2.62a as that's what seems to be recommended on the driver download page for 10.5 systems.
Thanks

Great stuff Matthias, working great here!!

Please do MC... I probably owe you a beer, anyway! :-)

This is a very weird use of an expensive piece of kit

Thats's Plug and Play :-) The plug was more reachable than the power switch of the FF.

Being serious: After loosing the content of a firewire hard disk, and lot of time and done work by freezes at very inconvenient time, I consider it as quite natural to to some stress test under controlled circumstances (i.e. while no real work is endangered) with the new driver before "trusting" it again and dare to keep the FF connected to the working machine.

P.S. according the Tech Specs of Firewire according to Wikipedia:

http://www.rme-audio.de/forum/viewtopic.php?id=3385

Regards
Daniel Fuchs
RME

Better that is....

i pull the firewire cables all the time , never got issues via firewire 400 and 800    ... maybe it is a MAC thing ....the burnt out photo seems to be a via..  ...i dont know ...for everything is a first time

Didn't have an issue with the old driver, but I'm loving the new look of Total Mix and so far 2.72 is working just as well. Glad to see that the problem is understood and fixed at any rate.

Did you uninstall before updating to 2.72?

Regards
Daniel Fuchs
RME

You know what? I don't know the answer... :-O
I'm sitting here recording a live concert in my free time (no, I don't have a 24/7 contract...), and I don't happen to have access to an Intel Mac with a Fireface where I am. So I choose to ask whether the driver was uninstalled first. If not, this might just help, and if it doesn't, then maybe it's only a cosmetic issue. We'll look into it on Monday.

Guess I should stop trying to help outside office hours... rant :roll

Regards,
Daniel Fuchs
RME

Minor cosmetic issue, I'd say. I'll forward it.

Regards
Daniel Fuchs
RME

scottkrk,

i think its not right what you are doing here.
first of all it is not true that the problem was reproducible.
i have seen it on an imac and a macpro but many other 10.6x users
never experienced any trouble throughout this 9 month.
yes, rme was not behaving as we where used to, maybe this was the first time
that they have been unsure about what is going on with their product (thats daily business at motu for example).
but we have seen them working constantly on fixing the problem.
your advice to buyers of an audio device is resultung from pure anger it seems to me.
i have seen metric halo cases where users where not able to work with their device for almost a year.
and metric halo was just saying : we are waiting for spare parts from usa.
want a apogee example ? well i guess every user who bought an early ensemble could start the same thread in their forums.
if your posting at GS was caused by emotional reasons, please think about editing the spikes.

Now we are double posting on two forums...

If you go by number of posts then I'm even more of an Ableton Live enthusiast. But given the fact that I was banned from the Ableton Forum the post-count might be quite misleading here. gooof Besides that most of my posts are trying to support other users.

Maybe you can call me an enthusiast, but I am also a demanding or say challenging customer/user. And I use to provide lots of detailed informations and not only understand how audio hardware/software works but very much understand how computers work. Because of that I became beta-tester for RME products, which obviously keeps me around their forum alot. I also beta-test lots of other audio- and non-audio related stuff.

But yes, I generally like my own RME interfaces and I want them to work properly just as much as you do. Having to wait several months for a driver to fix a problem is not an experience I like to make, but I have been waiting *alot* longer for other companies to look into their stuff with *alot* easier to fix issues. DeadHorse

Concerning Firewire hot-plugging. With my FF400 I do it all the time (often several times a day) without any problems. And that doesn't mean "if it works for me it works for anyone", it just means "the risk doesn't seem that high and I am willing to take it".

Scott,

final comments from me here...

This was a regular cable, but the exact details are irrelevant. It just shows that untoward things can happen with bus powered FW involved, even when doing something as harmless as connecting a cable to a FW card. Most of the time, nothing will happen, but it's possible. Hence our warning that comes with the FF.

I don't design hardware. If at all, MC might comment.

Quote obviously, there is no way I could answer this question to your satisfaction, mostly because your biased question and definition of "this level of support", which is clearly not something we (or a lot of other customers who never even noticed this issue) would agree upon. Therefore I somehow don't even assume you actually expect an answer to this question...

I don't quite agree with these views (asexplained earlier), and will therefore refrain from commenting. Also, none of this is related to the hot-plugging issue you've brought up in the middle of this...

Regards
Daniel Fuchs
RME

Okay, here's my 0.01$:

- Uninstalled everything RME with the FF800 turned off.
- Installed the new driver 2.72.
- Restarted the Mac.
- Turned on the FF800 AFTER the Mac had booted.

-> Red host light has turned off.
-> Mixer and Settings do NOT autostart! As always for months and months! They ONLY autostart when the Mac is turned on AFTER the FF
-> I had to launch Mixer and Settings manually - again.
-> Driver version reads 2.72, Kernel reads 2.71
-> Logic did NOT crash or freeze this time!

Well, I came that road before: Directly after installation and reboot, it sometimes worked. But the next day, when I cold-started everything, the problem usually was back.
Since I don't have the time for excessive tests tonight (still correcting some strange class test by 13-year-olds ;-), I'll post again tomorrow where I will try to start the Mac and THEN the FF800 once again.

But even if it works - my first wish will be for the autostart to work whenever I want it to...

Best regards,

Christian

Hi Mathias,

thanks for getting back to me... I just tried it again after a cold start: Autostart of the apps doesn't work, but the freezes aren't happening (second attempt today, will see more in the next few days). So for now, the worst of all problems seems to be gone. Autostart would be great though.

I'll contact Martin about this.

Best regards,

Christian

New driver (2.72) is definitely a no go here on 10.6.4, the interface appears to lose sync and glitches out randomly. Rolled back to 2.65 and the problem goes away completely. Anyone else seeing this?

Do you have the latest firmware update applied to the FF800?

http://www.rme-audio.de/en_downloads.ph … r_fireface

hope this helps