Re: The official Babyface Pro Thread
Makes no sense somehow...
Daniel Fuchs
RME
You are not logged in. Please login or register.
RME User Forum → FireWire & USB series → The official Babyface Pro Thread
Makes no sense somehow...
yes makes no sense but the issue described seems to come thru the power adapter, nothing else possible.
The Arturia has its own power supply, and he's referring to a powered USB hub. I still don't quite see how the presence of an ADAT signal would have any influence or which cable may have caused this, or somehow changed the amount of power supplied by the hub...
defect hub
@Ambrosepottie
Please would you do a test ?
Disconnect the Adat cables and let everything else be.
Switching ON/OFF the Arturia has still an effect on the interface ?
Hi, folks!
I literally ready to kill myself because of the problem:
I can't route signal from Babyface Pro FS's instr. 3/4 inputs into DAW to record the signal that going to the inputs.
So... My device is going into instr. 3/4 inputs. I can hear the signal thru my headphones that connected to Babyface Pro.
Also I can hear the signal from DAW when some VSTs are playing.
What I'm doing wrong? I think that I googled everything that I can find ![]()
Live settings:

Total Mix:
Have you been playing around in Totalmix ?
Did you activate Loopback on several outputs and forgot to switch them off ?
Have you been playing around in Totalmix ?
Did you activate Loopback on several outputs and forgot to switch them off ?
I checked Loopback function 10 times, mate... Tried to move things here and there in the TM software too ![]()
Ok then do Total Reset
Is Ableton listed in the Microphone Access in MacOS systrem preferences / Security and Privacy / Microphone ?
Ok then do Total Reset
I did it 3 times or so... What I noticed is that in DAW Bitwig, for example, there is no input 3/4 from Babyface at all.

Interesting, Bitwig seems to have special channel names prepared for popular interfaces.
It is instrument 1/2 assigned to input channels 3/4, I guess.
In Ableton inputs in your screenshot, these yellow fields are not buttons to switch ON that input channel ?
What I noticed is that in DAW Bitwig, for example, there is no input 3/4 from Babyface at all.
Instr. 1/2 = "input 3/4"
technoiswatchingyou wrote:What I noticed is that in DAW Bitwig, for example, there is no input 3/4 from Babyface at all.
Instr. 1/2 = "input 3/4"
I tried to select this channels too and still no signal are going into Bitwig
Interesting, Bitwig seems to have special channel names prepared for popular interfaces.
It is instrument 1/2 assigned to input channels 3/4, I guess.
In Ableton inputs in your screenshot, these yellow fields are not buttons to switch ON that input channel ?
Yellow fields are exactly buttons that are turned ON for all channels.
Enable input monitoring in bitwig
Check this please :
Is Ableton ( and Bitwig) listed and enabled in the Microphone Access in MacOS systrem preferences / Security and Privacy / Microphone ?
Check this please :
Is Ableton ( and Bitwig) listed and enabled in the Microphone Access in MacOS systrem preferences / Security and Privacy / Microphone ?
Turned ON ![]()
Enable input monitoring in bitwig
I tried — nothing is happened
I mean, I know that monitoring must be turned ON.
Then the signal should arrive.
The input signal has a good volume in Totalmix, this is the signal available in the DAW.
There is nothing to route from the interface to the DAW. Only select the input channel in the DAW.
Then the signal should arrive.
The input signal has a good volume in Totalmix, this is the signal available in the DAW.
There is nothing to route from the interface to the DAW. Only select the input channel in the DAW.
I re-checked settings in Privacy & Security again and access was turned OFF! That's it!
All my love to the advice, pal! Thanks a lot!
Wonderful !
Happy recordings
@Ambrosepottie
Please would you do a test ?
Disconnect the Adat cables and let everything else be.
Switching ON/OFF the Arturia has still an effect on the interface ?
The issue is resolved, I think it was the usb cable that goes from the powered hub to the computer. The Babyface usb was plugged into the hub, so ultimately not a direct connection to the computer. It manifested as the Babyface not outputting audio. When straight usb to computer connection was made everything works. With or without the ADAT connected or turned on, that was a red herring I guess.
Question number 2. My ADAT expander, an Arturia Audiofuse 8IN does not have any way to designate it as a Clock Slave, other than using Wordclock. I'm using it via toslink to my Babyface Pro fs. If I designate the clock as internal on the Babyface I get a lock signal with sync blinking on occasionally. If I set clock to optical it syncs.
I've seen a number of people with the same issue on this forum and basically what I gather is that it's not synced properly. In this case it may be that the Arturia has to be the clock master, I can't get a straight answer on that from them. But here's an observation: After doing tests with clock in internal and optical mode, everything sounds identical, at least to me. And no noise, pops crackles etc.... So which setting is preferred, the not quite syncing internal clock or the syncing optical (Arturia) clock?
Second, sync to external optical
it was just luck to have audio good sound.
In the Babyface Fireface USB Settings make clock source external optical , then it is correct.
RME User Forum → FireWire & USB series → The official Babyface Pro Thread
Powered by PunBB, supported by Informer Technologies, Inc.