You are not logged in. Please login or register.
RME User Forum → TotalMix FX → (Mac) Screen Recordings are Mono (Loopback enabled)
Can someone please explain to me why all my screen recordings have mono audio when choosing "Fireface UCX II" as an input device in the MacOS screen recorder? Is that an OS thing or is there something I need to configure inside TotalMix?
Thanks in advance!
just tried, the screenrecording is fine, audio is stereo.
Sure your original source is stereo ?
In Totalmix the software playback channel showing a stereo material ? Different levels left to right ?
I am trying to film a session in Cubase 13.
Under "Software Playback", the System channel plays back all the audio coming from Cubase. It is set to "Stereo"
But the recording is clearly mono, compared to how it sounds directly in my DAW
Another interesting fact: when I separate Analog 1/2 into two channels and change the L-R values during recording, it still stays mono.
If you listen music MP3 or Youtube or something from the computer and listen it via the UCXll is the music playing correct stereo ?
If you listen music MP3 or Youtube or something from the computer and listen it via the UCXll is the music playing correct stereo ?
Yes, everything else just plays fine.
I used the app "Loopback" by Rogue Amoeba until now. It lets me create a new virtual audio device which just takes the software output and routes it into that. If I then select this virtual device for the screen recording, it is Stereo.
I was wondering if other RME users have similar issues with that as I have.
Another interesting fact: when I separate Analog 1/2 into two channels and change the L-R values during recording, it still stays mono.
Where exactly do you change L-R values ? In Cubase in the recording track or in Totalmix ?
dreikelvin wrote:Another interesting fact: when I separate Analog 1/2 into two channels and change the L-R values during recording, it still stays mono.
Where exactly do you change L-R values ? In Cubase in the recording track or in Totalmix ?
I've been operating the L and R dials in TotalMix.
With no change in the audio.
There was a more recent driver update (DriverKit) which I just installed - without change.
I am out of options. if anyone has a clue as to what is happening here, I'd be happy to hear your thoughts
The panning in Totalmix is for monitoring not for recording.
The recording channels in a DAW receive the signals from the audio-interface input channels as is.
Inside the software playback channel in Totalmix there is a knob for width, this should be 1.00 for full stereo.
If the knob is set to 0.00 that is mono, -1.00 is stereo L-R swapped.
But this has no influence when using the Loopback Rogue Amobea software instead of the UCX.
Totalmix Loopback sending the stereo signal untouched to the DAW inputs.
You have somewhere on the road a bottleneck what makes the signal mono, I guess its Cubase.
Sure the master output in Cubase is not by mistake switched ON mono ?
The panning in Totalmix is for monitoring not for recording.
The recording channels in a DAW receive the signals from the audio-interface input channels as is.
Inside the software playback channel in Totalmix there is a knob for width, this should be 1.00 for full stereo.
If the knob is set to 0.00 that is mono, -1.00 is stereo L-R swapped.
But this has no influence when using the Loopback Rogue Amobea software instead of the UCX.
Totalmix Loopback sending the stereo signal untouched to the DAW inputs.
You have somewhere on the road a bottleneck what makes the signal mono, I guess its Cubase.
Sure the master output in Cubase is not by mistake switched ON mono ?
that all makes sense, yes.
also I mentioned that I was using "Loopback" by Rogue Amoeba as alternative audio device with Cubase mixer and output settings unchanged and it did come out in stereo on the screen recording.
so there seems to be a thing that the screen recording tool or the audio driver does that converts the audio into a mono signal.
there are no controls or settings accessible or that I know of to fix this
I did a test with the Digiface USB.
You did nothing wrong.
Me Apple-Fanboy- have to admit : it seems the MacOS screenrecording tool is not able to record stereo from a multichannel audio device. The recording is flatten into mono. What a shame for MacOS !
The solution :
You have to use Rogue Amobea Loopback for screenrecorder. This Loopback tool is a plain 1 stereo channel device, the screenrecorder can handle it and your recording is fine.
As soon as I meet Tim Cook I will tell him what he has to do.
I did a test with the Digiface USB.
You did nothing wrong.Me Apple-Fanboy- have to admit : it seems the MacOS screenrecording tool is not able to record stereo from a multichannel audio device. The recording is flatten into mono. What a shame for MacOS !
The solution :
You have to use Rogue Amobea Loopback for screenrecorder. This Loopback tool is a plain 1 stereo channel device, the screenrecorder can handle it and your recording is fine.As soon as I meet Tim Cook I will tell him what he has to do.
LMAO yes, please thanks!
So there is no alternative to using Loopback...figures. What a shame!
I will file yet another pointless complaint about it at https://www.apple.com/feedback/
Me Apple-Fanboy- have to admit : it seems the MacOS screenrecording tool is not able to record stereo from a multichannel audio device. The recording is flatten into mono. What a shame for MacOS !
Maybe they sum all input channels available, if there is multichannel... And render it mono, if it is of unknown format/count. Because, what else to do with it? Beside asking user, what to do, which would be the best.....If user knows.....
Beside Rogue Amobea Loopback, there are many other similar tools like Hijack or Blackhole
or those three helper tools on my system :
waedi wrote:Me Apple-Fanboy- have to admit : it seems the MacOS screenrecording tool is not able to record stereo from a multichannel audio device. The recording is flatten into mono. What a shame for MacOS !
Maybe they sum all input channels available, if there is multichannel... And render it mono, if it is of unknown format/count. Because, what else to do with it? Beside asking user, what to do, which would be the best.....If user knows.....
Yes, Kubrak, but it does not sum up when only two channels are available, only multichannel is not accepted.
Apple support says it is not a bug it is standard at moment. We shall file feedback.
Just encountered this issue today with Cubase 14 and macOS Sequoia. My interface is UFX III. Seems the problem still persists 
I don’t have Loopback but I do have Audio Hijack, which waedi mentioned. It is one of my all time favorite utilities, and I use it all the time. Although I’m not sure I understand how that particular app might allow for stereo screen recordings.
Another snaggle... I am trying to use OBS instead of the macOS screen capture, and now I hit a different issue. Super low audio levels. When 'built-in' audio is used for the audio source in OBS, levels are normal. However, when I switch to UFX III, output levels drop 30-40db, even though 'software playback' levels are normal in Totalmix. Very confused about what's going on here..
In the UFX lll the Loopback is post-fader, make sure the fader of the hardware output channel (where the Loopback is ON) is up.
I was using “macOS Audio Capture” as the source in OBS, so I would assume that this would be drawing from software playback channels 1/2 in Totalmix rather than the RME Loopback input channel.
Speaking of which: do you suppose there is any way to use Audio Hijack to supply audio to the macOS screen recorder? I tried Rogue Amoeba’s Loopback app and that definitely works. I love RA but not sure I see much use for this app beyond this and would like to save myself $100 if I can.
You are the owner of the UFXlll the flagship giant audio interface.
Use Totalmix Loopback and forget all these quirky-quarky workaround tools.
Why spent 2400 and not learn how to use it's great features ? But then be concerned about spending 100 bugs ?
OBS receives audio on input channels 1/2.
In Totalmix route all sound for OBS to the hardware output 1/2 and enable Loopback.
The Loopback button is inside the channel, to open with the wrenchtool button.
Hit the Loopback button and the complete sound from this output is instantly available in OBS.
Don't forget to lift the output fader of this Totalmix hardware output channel 1/2.
Why spent 2400 and not learn how to use it's great features ?
I am here precisely because I want to learn more from the real experts such as yourself, waedi!
I understand your suggestion to use Totalmix Loopback. The big problem there is that I need to use all rear analog inputs on the UFX (including 1/2). Engaging Totalmix Loopback will disable that input. I use AES I/O (ch 13/14) as my dedicated Loopback channels.
I have observed inconsistent and confusing behavior with regard to macOS system audio + RME and I'm trying to make sense of it:
- macOS native screen recorder, with "Fireface UFX" selected as "Microphone": given the label, I would expect this to pull audio from an input device. However, the resulting recording includes input sources as well as Software Playback 1/2, all summed to mono (as you observed earlier in this discussion)
- OBS screen recording with "macOS Screen Capture" or "macOS Audio Capture" selected as "source": here I would expect an output device as the source. And indeed, the recording captures only Software Playback channel 1/2 (no input sources) Great! But for some reason the recording is approx 35dB quieter than original playback. This is the biggest mystery to me.
- macOS native screen recorder OR OBS screen recording with Rogue Amoeba Loopback (RME ch 13/14) as source: everything works as expected.
Anyway, simplicity is my goal with regard to screen recording. Ideally, I would like to just use the native macOS screen recorder to quickly capture what's on the screen and what's coming through the default macOS output (Totalmix Software Playback channel 1/2). Seems like Rogue Amoeba Loopback is probably the best way to achieve that for now.
I'm a composer/producer/teacher who works with screen sharing 2-5x a day with different clients, students, or VideoRecordings. I've had my BabyFace Pro for 10+ years, and persisted with only TotalMix Loopback for five years or so, but had give in and purchase LoopBack by RA.
What horseofcourse is saying is true in my experience as well, but saying "Use TotalMix" does not solve every problem. Some notable problems TotalMix does not solve:
-MacOS QuickTime ScreenRecorder flattens the audio to Mono (taking it from Input 1). There seems to be no workaround outside of LoopBack-RogueAmoeba/BlackHole/SoundFlower
-Some clients insist on using Discord (video game devs) which rarely if ever recognizes my RME device input, and does not facilitate screensharing.
-Google Meet will not recognize TotalMix-Loopback playback (this is a Safari Issue, I believe. Chrome/Firefox will work)
-Zoom will recognize TotalMix-Loopback, but when "original sound for musicians" is engaged you it throws your mic channel hard left Analoge input 1, unless "COPY A->B settings" is engaged in Mic Settings for Channel 1. This can be quite limiting as is obvious, but it immediately negates the usefulness of Zoom Recordings, Mics/Inst running on the 2nd channel, among many other instances.
-I often do not want global sound being sent into my Totalmix-Loopback recordings. Recorded mixing sessions, collaborations, interviews, screen-sharing meetings, YT recordings -- they all can range from 15 minutes to 2+ hours. It is extremely unlikely that I will not receive a notification of any kind during this recording. One cannot always account for Do-not-disturb modes to catch all incoming notification sounds.
This is to say nothing of other applications that are regularly in-demand: Whatsapp, Messenger, Slack, Riverside, or any of the other which demand audio sharing permissions and are inconsistently buggy. Some are stand-alone, some are chromium based, some are browser based. I wish it were as simple as use Loopback-TotalMix, which I adore. I do not think the issue is with RME, but rather with the proliferation of options that clients tend to use. If you're working at home, or in a studio where you don't have to screenshare, record iterations, produce video content, mix options, or teach -- I think LoopBack-Totalmix is the perfect tool. It's a miracle, truly.
However, in my experience prospective clients do not remember if everything works perfectly, but they do remember that "this audio professional couldn't get his audio working during the interview". I even had a guy once suggest that I "click the little gear icon and change my microphone settings" to get the audio sharing to work.
LoopBack-RogueAmoeba solves all of these issues. Set it as the default microphone input globally for MacOS. Every platform works immediately, no hesitation, no configuring. Every application that isn't the DAW just see's a "LoopBack-RogueAmoeba" Microphone. Output varies depending on work type.
My DAW see's RME device for Input/Output (not System Setting or Loopback). Done, set forever and there are no issues on any platform.
USAGE TIP: Inside of the "Source" selection for LoopBack-RogueAmoeba remember to UNCHECK the "mute when capturing", and then you can set up a single loopback instance and leave it closed presumably forever.
It is possible that someone could setup exactly the same workflow using OBS' virtual microphone extension, route all of the source selections/window selections from OBS, program the recording and capture details to work reliably. I don't think that is news to anyone. Your mileage may vary, but over 10+ years using RME devices I've had enough issues with OBS in the past. Sometimes on MacOS RME devices won't even register, or they won't be gain controllable, or the routing will be hidden. It's open source software and while it can be very reliable, among the problems listed I have forgotten to turn it on once or twice while recording and that was enough for me to look for another option.
As anyone else who has posted or looked for information on this forum will tell you, RME devices are the best, TotalMix-RME is the absolute best. But as a software routing solution, it does not meet the demands of many modern professionals, who are at the whims of 3rd party audio-sharing solutions. How it is that TotalMix can solve 99% of all problems, and yet somehow cannot manage system stereo audio screen-recording, or other platform issues is beyond me, but the 100$ price tag for something I never have to think about or update, that provides total peace of mind for all applications is a no-brainer. Wish I didn't have to, but it's far and away the best and most reliable option.
Google does not find 'Loopback RA'.
Rogue Amobea Loopback ?
It is a good working tool for advanced homerecording people.
Totalmix Loopback is easier to handle.
It's spelled 'Amoeba', and that one everybody knows. I just never heard / read 'loopback RA'. Just wanted to make sure useful post #22 doesn't fail because of a missing reference.
Excuse me, I thought the Loopback RA would distinguish it from the TotalMix Loopback — difficult names to distinguish. I will edit the post for extra clarification.
Again I wish that Totalmix Loopback could accomplish the needs of a modern professional, but the reality is that too many different applications misconfigure the audio routing internally, as my post#22 shows in detail.
you may consider checking out Jamulus for musician audio conference.
It was recommended from many international musicians during Covid lockdown as a very useful tool to play together live over distance.
The software you mentioned is video-conference freeware not made for multichannel audio interfaces.
But recently was a topic about Google-meet, it turned out in the new version of meet you can select different audio input channels.
Try new version...?
And I find your naming Loopback RA a good idea.
you may consider checking out Jamulus for musician audio conference.
It was recommended from many international musicians during Covid lockdown as a very useful tool to play together live over distance.The software you mentioned is video-conference freeware not made for multichannel audio interfaces.
But recently was a topic about Google-meet, it turned out in the new version of meet you can select different audio input channels.
Try new version...?And I find your naming Loopback RA a good idea.
As I mentioned in my post, 99% of the time I'm not in charge of which software platform I'm being dropped in. If I'm conferencing with 6 game devs in different countries I will be expected to use Discord with them, as that is where all of their other business takes place. This is not news, and while audio routing with TotalMix-RME is wonderful, incredible, exhaustingly great, it cannot solve the problem.
The exact same as using Slack, the most common. I haven't even mentioned Microsoft Teams, or Skype, or FaceTime (absolutely the worst for audio sharing, a non-starter). I might not want to use it, but it's often a conference and I need to be able to demo any number of video or audio projects at a moments notice, sometimes without notice.
The problem is not the platform. The platform can never be the issue, because it is the only variable a modern audio professional cannot account for. It has to work, every time. Loopback-RME does not work every time, so it cannot be relied on.
Google-meet is also such a fickle one. It's options change based on which browser you're using, permissions, and I've ever lost certain options that others swear are available because I am in EU.
Totalmix Loopback is part of the RME audio driver wich is standard in professional audio.
It works reliable every time.
The different conference softwares are not ready.
Until they bring up a better version you have to use the workaround with Loopback RA.
Hi there, new user here, I use a Fireface UCX II and play electronic drums with toontrack software, I recorded the screen while playing my edrums and the resulting video's audio was in mono so I goggled this and found this topic, I will give RA Loopback a try.
The obs low level problem...
In obs for the audio device, deselect "allow down mix". When you have it on, which is the default, you can only loopback from output 1/2, where the monitors probably are, and the fader is low, which is why you have a low input to obs.
So,
1. set some unused output to mirror the main mix, say Madi 1/2. Set the Madi 1/2 fader to full level, make sure sure loopback is engaged on that output.
2. in the obs audio device, deselect the down mix option, then you can select any "input". Select Madi 1/2.
As a bonus, you can engage the compressor or whatever on that madi 1/2 output and it will reflect in obs. Hope that helps!
The obs low level problem...
In obs for the audio device, deselect "allow down mix". When you have it on, which is the default, you can only loopback from output 1/2, where the monitors probably are, and the fader is low, which is why you have a low input to obs.
Depends on the interface model. Some have loopback prefader, others have it post-fader.
The user manual has a block diagram that shows the point of Loopback intersection.
Quicker and more comfortably, you can look this information up in my Excel if you want to compare different USB/FW/TB interfaces (sorry, no PCI/PCIe included):
https://forum.rme-audio.de/viewtopic.php?id=35156
All newer USB interfaces have Loopback implemented post-fader, except UCX II which is implemented pre-fader.
Initially, even the UFX was implemented pre-fader, later it changed in UFX+/UFX II/UFX III.
Quicker and more comfortably, you can look this information up in my Excel if you want to compare different USB/FW/TB interfaces (sorry, no PCI/PCIe included):
https://forum.rme-audio.de/viewtopic.php?id=35156
All newer USB interfaces have Loopback implemented post-fader, except UCX II which is implemented pre-fader.
Initially, even the UFX was implemented pre-fader, later it changed in UFX+/UFX II/UFX III.
Thanks, and good to know.
RME User Forum → TotalMix FX → (Mac) Screen Recordings are Mono (Loopback enabled)
Powered by PunBB, supported by Informer Technologies, Inc.