Works great here

The headphone output in your screenshot is Main. The purpose of the DAW mode is to do all the routing in the DAW, so you will only hear something on Main if you play back a signal on channels phones 3/4. I don't know how there can be a difference in DAW mode with driver 2.18, only if you had changed the basic CoreAudio routing via Sound - Speakers in Mac OS to feed the phones.

You can not 'select' the phones out with the button on the BF Pro to make it an 'active' output (only in stand-alone mode). This function is limited to adjust the phones output level/volume with the wheel.

That kind of improvement is indeed expected.

I tried the new driver today. The Fireface USB Settings application now requires high performance graphics which forces MBPs to switch to the discrete graphics chip which consumes more battery and generates more heat. The other driver does not do this.

Can you please try this modified Settings dialog (just close the current one, then copy the app into the Applications folder, overwriting the old one):

https://archiv.rme-audio.de/download/Fi … 9_Test.zip

The issue is now resolved with the new settings dialog thanks.

Further to this....

I can get Totalmix partially working if my Fireface UCX is not switched on (still no interface but at least a few drop down windows). However when I switch on my Fireface, Totalmix (or at least the parts that appear to function) crashes.

Thanks for the link.

I searched for the audio plugins you mentioned there but don't  have them in the locations you suggested. I tried the 2.17 driver but that also made no difference. I'm running a late 2013 mac, 3.5 ghz processor, core i7, NVDIA Ge force graphics card. I was using Yosemite and the Fireface (and Totalmix) worked perfectly. I'm using Logic Pro X as my DAW. After the Sierra download I also did the latest Logic update. I have not downloaded any other plugins apart from those that come with Logic.....The only drivers in the audio plugins folder are AirPlay, Apple AVB Audio, Apple Time since audio clock, bluetooth audio plugin and isight audio driver.  Any other ideas please?

OK I have a .hang file report but it's very long. How can I send it to you?

Have you tried making a new user account?

If TM works on this new account, your first account is probably somehow corrupted. In that case, it seems wise to reinstall OSX (and Logic and other apps) from scratch and set back your data from backup.

Alternatively, you can use the new account, reinstall Logic on it and transfer your data through the "public" folder, or via an external disk.

1. We will check that.

2. Aggregate Devices is there to combine several devices. Using it with just one doesn't seem to be what it is intended for, so a weired behaviour might be normal.

RME devices require sync by external clock. This is a known limitation when using the Aggregate Devices function. With two Fireface 800 (example) you would connect them via word clock and set master/slave correctly. This is also mentioned in most manuals. The software clocking via Core Audio is not supported.

Just to add this is only really appropriate for synths and sound modules since "drift correction" obviously means Apple is messing with the incoming USB digital audio. But it works surprisingly well. I have compared playing a keyboard via Apple's "drift correction" SRC and analogue capture and the former is perfectly clean (no noise floor) and to my ear a slightly more detailed sound.

For info, turned out my aggregate device issue was related to (a) macOS apparently applying some constraints on aggregate device sample rate which are easy to work around by using the aggregate device for Audio Input only and (b) macOS displaying incorrect values for aggregate device sample rate in Audio Midi Setup. (The real aggregate device sample rate displayed in [System Information / Hardware / Audio] was in harmony with that reported by RME's USB settings.)

So I do not believe there is any issue with the RME driver here, sorry to bother you with this.

An aside for anyone reading with modern synths which present as audio interfaces: you may be interested to note that for me using an aggregate device to process USB audio inputs from multiple synths and then (following SW processing) pushing that audio back through the Babyface Pro works very well. Just set the BFacePro in your application as Audio Output and use an aggregate device of synths (as well as possibly the BFacePro as clock master) as Audio Input and you're away....

[For synth people] Note also I am running the BFacePro at 96 kHz, thus ensuring HW synths are SRC'ed by Core Audio to the BFacePro-clocked 96 kHz for a full 96 kHz/24-bit system including soft-synths as well. My system sounds incredible to be honest, in large part due to the BFacePro's great converters. And I am taking delivery next week of a new completely-maxed out MacBook Pro with touch bar (2 TB SSD etc) and can't wait.... : )

Hello,

Long time RME user here, just sharing my experience with original Babyface and Sierra driver 3.01.

Babyface was working fine w El Capitan. Moved to Sierra in early Jan, clean install.

With Sierra-driver some unexpected noisebursts and audio lockups (session running, master meters showing extreme full scale signal but no audio coming out ) in Logic X. Sudden full scale noises also in Reaper, a big pop to speakers and then silence when session is running.

Usually happening when tweaking a plugin but not limited to a specific plugin. Any synth, eq, compressor or even doing basic region editing (trimming region start etc.) could trigger the burst + silence - kombo. Could not pinpoint any workflow which could reproduce the problem reliably. Audio was coming back after deselecting babyface as audio device and reselecting right after.

Tried that for a few days, installed driver 2.20 and all the problems haven't showed up since. Been working like a dream for a month or so, daily heavy use.

Macbook pro Early 2011 17-inch i7 quad, macOS 10.12.2 and 10.12.3, Logic X 10.2.4 - 10.3, Reaper 5.311 - 5.33

Best

J

Link from above post with better formatting: https://support.apple.com/en-gb/HT202982

Hello forum,

I just wanted to add to JTF's post on 2/17---

I was basically having the same issue when I was using 3.0 driver, and I just saw this thread a few days ago so now I'm using 2.2. So far I haven't encountered the issue.

For me the extreme full-scale pop noise usually came out when I played certain patch in a sample library. There's at least one Kontakt patch that often gives me this issue--- there might be more but I'm only aware one another patch for now. If I switch to another patch (even from same library) the noise will go away. And this doesn't always happen either,  sometimes I load that problematic patch and have no issue at all. It seems like it happens more when I'm more involved in the writing process, having lots of instruments loaded etc. but not 100% sure about this.

Here's the video I recorded when I was having the issue:
https://www.youtube.com/watch?v=TDL81XSY7WE

You can see the pop happens as I play the keyboard, but no sound is coming out of Kontakt (you can't see but Logic's meter isn't moving either). Then I switch to the next patch and plays fine. I don't think this is a problem with the patch, since I was using it before I started using BFace Pro and had no problem.

Hope the driver will get fixed soon, if that's what causing the issue. Thanks.

Thank you Matthias for quick reply.

Yes, I am using 2.2 as I mentioned for a few days now, and have not had an issue yet. I will update if anything happens but hopefully not.

I did have Kontakt update recently so it could be the problem with it. I will look into that more...

I do have the same problem with the Babyface and Macbook Pro 15 (2,9 Ghz i7 and Radeon Pro 460) with touchbar.
I can't work around the problem, only a restart brings the touchbar back alive..
AND, after unplugging it once, the Babyface is not recognised any more by reconnecting it. ??

Hi Matthias,

I have the following information for you regarding the unplug issue and then losing the touchbar:

Macbook: 15" 2.9ghz i7, intel hd530
Sierra 10.12.5
Of the babyface I updated everything, so newest firmware/totalmix etc.

I also have a log, but its pretty big text wise. Should I email that?

Anyone else experiencing a BIG performance improvement with the 3.03 driver using Logic 10.3.1 & OSX 10.12.5?

2014 MBP - 2.8Ghz, 1TB SSD, 16GB Ram & a music only software/hardware config.

I was experiencing a lot of random processing peaks, glitching & sometimes complete halting of playback with the 3.01 & 2.20 drivers - there is a lot of talk on the web about the Logic audio engine having these sorts of issues & many consider it needs a rewrite. The workaround for most it seems is to tolerate the issue until the set-up "settles down"......which it does seem to do after a while. (Talk about ghost in the machine..)

Frustratingly I could play the heavier projects via the audio outputs of my Thunderbolt Display without issue.

Installed the 3.03 driver a couple of days ago & the symptoms have resolved - back to (the usual) very smooth & transparent operation.

Cheers RME team!