any1 confirm that audio recording w/ a mic works on linux

If neither ADR or Fairlight track recording work on Linux, those features should be completely disabled. People spend hours trying to make it work as they show up in the UI as they were supported.

The worst practice is to make features "available" for the users, knowing clearly that they don't work. At least it will not give people hope that it will eventually work.

By the way, Decklink inputs show up in both ADR and input-output patch but they also don't work, although it's BDM software talking to BDM hardware, which is even more disappointing. Also, for no particular reason at all, enabling playback and capture with IntensityPro adds a bunch of Decklink and ALSA inputs to the patching list, but none of them work anyway. As Fairlight doesn't show the input level in the list, I had to test 8 pairs separately, just to confirm that none of them work.

Funny enough, everything, just everything, including Decklink and IntensityPro works as expected in OBS, which is developed by enthusiasts and is completely free, unlike the DR Studio I have.

I find it very sad to read that this old issue is not yet fixed. I was planning on using DaVinci for my future projects, and even convincing my superior to buy a couple of licenses.

Well, then I will continue to use an MLT-based software (which all still suffer from audio glitches and missing features). They at least allow me to record audio at all, which is crucial for all my planned projects.

did anybody test this with 17.1?

[Dwaine Maggart]

ADR recording is still not implemented in Linux with Resolve 17.1.

thanks @Dwaine

Just found this topic after few hours of debug

Davinci Resolve 17


Davinci Resolve 17 ADR UI


Gnome sound settings configuration


My XLR Rode Podmic connected to my Evo 4 is working as expected with OBS and Ardour on Pop!_OS 21.04.

So if I understood well, there is currently (Davinci Resolve 16 & 17, Studio version or not) no way to record voice via ADR or Fairlight on Linux?

If it's the case then as mentioned previously, this should be part of the documentation.

[Dwaine Maggart]

That is correct. No ADR on Linux.

That is correct. No ADR on Linux.

Thanks Dwaine for confirming about ADR.

What about Fairlight and voice recording (Patch Input/Output) on Linux.

[Dwaine Maggart]

No. If that worked, then ADR would work.

No. If that worked, then ADR would work.

Thanks Dwaine.
Then I think this should be clearly mentioned into the documentation/limitations.

There I was all ready to drop some audio over a video of my glove puppet to make up for my minimal ventriloquist skills... and it doesn't work. Half-an-hour of fiddling about and Googling and I find this thread.

It seems pretty ridiculous to me, I'm afraid, that this functionality seems, from this thread, to have been broken on Linux for over 2 years. I am slowly coming to the conclusion that BM support for Linux is very much an afterthought. Which is a shame because I found it such a great product using it on my Macbook. I was going to invest in a Resolve Studio licence, but that really doesn't seem worth the money while the Linux version is so comparatively poor. I'm certainly glad I hadn't bought a licence yet!

BlackMagic is probably one of the only real professional video editing software on linux.
Unlike Adobe (Premiere Pro), BlackMagic has already not left linux users in the dark.
So many functionalities already working. Really appreciate that.

I really wonder what stops them from solving this key feature of audio recording on linux though.
I would really hope this support comes real soon. I notice folks complaining about the lack of this feature for at least 2 years now!

Would love to see this fixed

[Dwaine Maggart]

17.3 now has ALSA support. Recording with a mic on Linux should now work.

17.3 now has ALSA support. Recording with a mic on Linux should now work.

Just read about, great news!

I confirm, now it's working

Thanks you !

17.3 now has ALSA support. Recording with a mic on Linux should now work.

OMG! Great news! Thanks!

Can anyone advise how to get this working?

I'm arming the track, patching the inputs and still no audio input. How do I go about debugging this?

[Dwaine Maggart]

On the Fairlight page, select the ADR section. Then select Setup.

In the ADR Setup area, select the Record track. That will activate the Record Source menu. Select ALSA.

The audio track should have the R record indicator turned red, and you should see audio on the track meters.

Thanks for the quick reply, Dwaine

I guess I was manually settings this up by selecting the input for my track, patching the ALSA devices to the track input, then arming the track for recording.

I tried your suggestion and got the same results -- no audio coming in. I can open Audacity (even while Resolve is running) and immediately start recording in Audacity, so I know that the mic is visible to ALSA and working fine.

I hazard a guess that Resolve is not detecting my mic as input. Is there a way I can manually fiddle with the ALSA settings? I've been through every menu, and there's certainly a place to modify output devices, but I can't find the input side...

Thanks again,
S

[Dwaine Maggart]

On a CentOS system, the Settings - Sound would have the ability to select both the input and output devices being used by ALSA.

I happen to have an Ubuntu 21.04 system running at the moment to look at something else, and I notice that it does NOT have the ability to select the input device, just the output device, as you mention. Are you using Ubuntu?

That said, the audio device I'm using, a Behringer UMC404HD, still works as an ADR input source in Resolve 17.3.1 when ALSA is selected as the ADR source.

Just to confirm, you are using Resolve 17.3 or 17.3.1?

17.3 now has ALSA support. Recording with a mic on Linux should now work.

Awesome!
I don't know if this thread helped to implement this feature or if you raised the RFE but thanks for the follow-up!

I happen to have an Ubuntu 21.04 system running at the moment to look at something else, and I notice that it does NOT have the ability to select the input device, just the output device, as you mention. Are you using Ubuntu?

That said, the audio device I'm using, a Behringer UMC404HD, still works as an ADR input source in Resolve 17.3.1 when ALSA is selected as the ADR source.

I can record with several Behringers, including the UMC404HD, on both 20.04 and 21.04, but all intermittently crackle/pop so the result is unusable.

[Dwaine Maggart]

I didn't have that issue in CentOS 7.9, and I don't have that issue in Ubuntu 21.04.

Have you listened to the wav file somewhere else, to verify if the issue is in the recorded file, or if it's a playback issue?

My tests were done with 24 FPS timeline and video clips. Are you using something different?

My tests were also done with no color grades. Just video clips on the timeline. Perhaps if there were heavy grades going on, or issues playing back the video clips, that might cause an issue.

I don't understand what people have against silent movies. They were all the rage before "talkies" came along.

So I installed version 17.3.1 but in "Record Track" under ADR menu I got nothing.
I'm using EVO 4 which is working fine with other applications.

I'm running PopOS 21.10 (based on Ubuntu 21.10) with Gnome, do we need to do anything on the ALSA side?
PulseAudio is my default sound server.

Please find my "alsa-info": http://alsa-project.org/db/?f=95e8388de ... f0825a834b

Have you listened to the wav file somewhere else, to verify if the issue is in the recorded file, or if it's a playback issue?

My tests were done with 24 FPS timeline and video clips. Are you using something different?

My tests were also done with no color grades. Just video clips on the timeline. Perhaps if there were heavy grades going on, or issues playing back the video clips, that might cause an issue.

I used a single video clip with no grades and one audio track on A1. Recorded to A2. A2 audio played back with seemingly random pops/crackles, but otherwise correct. I did not try playing the recorded wave file outside of Resolve.

I did try everything else I could think of on two machines (Xeon 21.04/Threadripper 20.04), and two Behringers (X18, 404HD) before giving up.

Audacity was spot-on with both systems.

I'm out of town for a week but will try with two other Ubuntu systems when i get back and see if the results are any different.

Really happy to see y'all are working on this.

On a CentOS system, the Settings - Sound would have the ability to select both the input and output devices being used by ALSA.

I happen to have an Ubuntu 21.04 system running at the moment to look at something else, and I notice that it does NOT have the ability to select the input device, just the output device, as you mention. Are you using Ubuntu?

That said, the audio device I'm using, a Behringer UMC404HD, still works as an ADR input source in Resolve 17.3.1 when ALSA is selected as the ADR source.

Just to confirm, you are using Resolve 17.3 or 17.3.1?

Hi, Dwaine - I'm using Fedora, which is a little different in appearance than CentOS 7.x, but has otherwise been working very well. The input device that I'm testing with is a Blue Yeti USB microphone.

I update as soon as new releases appear (unless I'm preparing something for a class that's starting in an hour or two...), so I'm on 17.3.1 now.

Do you know how to get Resolve to show what ALSA devices it's finding and perhaps change the mapping?

Thanks...

[Dwaine Maggart]

Resolve has no ability to change the ALSA mapping or display what device ALSA is using. That needs to be done outside of Resolve at the OS level.

Resolve has no ability to change the ALSA mapping or display what device ALSA is using. That needs to be done outside of Resolve at the OS level.

So what should be done from an ALSA perspective to have the devices displayed in ADR menus?

When running "aplay -l" or "arecord -l" I able to see the devices.

Code: Select all

╰─λ arecord -l
**** List of CAPTURE Hardware Devices ****
card 2: Generic [HD-Audio Generic], device 0: ALC3861 Analog [ALC3861 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 2: ALC3861 Alt Analog [ALC3861 Alt Analog]
  Subdevices: 2/2
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
card 3: EVO4 [EVO4], device 0: USB Audio [USB Audio]
  Subdevices: 0/1
  Subdevice #0: subdevice #0


[Dwaine Maggart]

The Resolve software development team would need to make changes to the Resolve Linux code to support that.

The Resolve software development team would need to make changes to the Resolve Linux code to support that.

So, what are the requirements and what should I check/change to make sure the devices appear in Resolve?

Basically, what did you do/change on your system to have your audio interface listed in Resolve?

[Dwaine Maggart]

What was added was support to capture audio from ALSA.

If you map your audio input device to ALSA in the OS Settings, then that's what Resolve will use, when you select ALSA in the Resolve Fairlight page, ADR Setup area, Record Source.

What was added was support to capture audio from ALSA.

If you map your audio input device to ALSA in the OS Settings, then that's what Resolve will use, when you select ALSA in the Resolve Fairlight page, ADR Setup area, Record Source.

The "Record Source" is set to None, nothing in there such as ALSA.

Alsamixer output:


ADR menu:

[Dwaine Maggart]

You have to select a Record Track first. That will enable the Record Source menu.

You have to select a Record Track first. That will enable the Record Source menu.

Indeed, with the track I'm able to select the "Record Source".
Thanks as usual.

OK, it looks like it's just not going to work on my system

I've set a reasonable record level, tested that it works fine in Audacity and other apps, but I get nothing but silence in Fairlight.

[Dwaine Maggart]

Please show a screen shot of your Fairlight page ADR Setup area.

And to confirm, you are using Resolve 17.3 or 17.3.1?

Sorry, Dwaine. I must have forgotten to include the version I'm running. I'm on 17.3.1

Here's my ADR setup page:

Well, I have good news for anyone having similar trouble to what I have been describing as I have gotten things going!

System: Fedora 34 (with Pipewire)
DR Version: 17.3.2

1) Install alsa-plugins-pulseaudio (I have not needed this in the past but it's important here, evidently)
2) Create a file called /etc/asound.conf with the following content:
pcm.!default pulse
ctl.!default pulse
3) Restart alsactl (or reboot)
4) It works!

This also fixed a problem (perhaps it fixed it, not sure, I was having the problem before the mic fix and now it's gone) where the audio was severely lagging the video during editing.

I now need to figure out how to prevent the audio from coming out of the speakers while recording on the mic!

Problem seems to be fixed now. Works fine with Davinci 17.4. and Ubuntu 21.04

I now need to figure out how to prevent the audio from coming out of the speakers while recording on the mic!

Look in upper third on the right side. There you see a little speaker and a green bar. Kust mute that speaker before you record.

17.3 now has ALSA support. Recording with a mic on Linux should now work.

I really appriciate you fixing this. Verified, it works on Linux Mint 20.04. Now I can record voice natively in DaVinci Resolve without external software and without headache with converting/importing/exporting. Thank you!

Using the latest Studio 17.4.2, the default audio recording buffer 5 leads a lot of pop/crackling for me, however set it to max value 8 makes sound normal (but the monitoring latency is visible, not sure if this is a bug or works as expected).

Also Studio 17.4.2 shows me 8 ALSA input device... while the first one is just work, I suggest to show more info on those devices instead just show ALSA-1 ALSA-2 so I can choose better (maybe I only need a system default choice, I have a Scarlett 2i4 controlled by JACK2, and when Resolve loading ALSA, it's actually passing sound to PulseAudio, and PulseAudio passing sound to JACK2 or other sound card, so I only need to change device with PulseAudio).

If Resolve could support JACK, it will be good, however this is my personal opinion. Working with ALSA is just fine because we have PulseAudio-ALSA bridge, though modern desktop apps use PulseAudio and professional audio softwares use JACK.

Well. I came to check up on this today, to see if there had been any progress, and I discover it's now working, which was a very pleasant surprise.

I don't think it matters that it's using ALSA as opposed to Pulse, or Jack or even Pipewire (which, I'd contend, is what truly modern Linux systems are moving to, as a replacement for both) ALSA pretty much works everywhere and for just setting up an input device it's more than adequate.

I'm using Pipewire on the Arch-based Manjaro, and there were zero issues. The audio support worked out of the box, just chose the first ALSA input(s) from the list and that was my Behringer Q802 picking up the mic. No crackle, no major latency issues for me, at least.

Lovely stuff. Thanks for getting this sorted.

I did only register to thank you Black Magic for implementing support for this on Linux.
I have bought Studio version of your software for my company which mainly works on Linux. Now I have started to record audio in it. Did not know how to do it out of the box. I found this thread, realized that there was a problem with it before. But finally has been resolved during that time. Now I can still use my favorite system environment without any downfalls, even for recording audio with you lovely professional tool. Many thanks! Many thanks from Linux users! Thanks for became aware of the fact that we are using Linux not because it's usually for free, and we got no money for professionals tools, but for it's versality, flexability and scalability. Once again: BIG THANK YOU!

Thank you for fixing this.

Well, I have good news for anyone having similar trouble to what I have been describing as I have gotten things going!

System: Fedora 34 (with Pipewire)
DR Version: 17.3.2

1) Install alsa-plugins-pulseaudio (I have not needed this in the past but it's important here, evidently)
2) Create a file called /etc/asound.conf with the following content:
pcm.!default pulse
ctl.!default pulse
3) Restart alsactl (or reboot)
4) It works!

This also fixed a problem (perhaps it fixed it, not sure, I was having the problem before the mic fix and now it's gone) where the audio was severely lagging the video during editing.

I now need to figure out how to prevent the audio from coming out of the speakers while recording on the mic!

Thank you! that helped!
Did you figure out h ow to prevent audio from coming out of the speakers?

Thank you! that helped!
Did you figure out h ow to prevent audio from coming out of the speakers?

Yes, I did!

Within Fairlight there is a volume slider, just under the video preview window:

Volume control within Fairlight

Screenshot from 2022-04-23 07-22-44.png (76.91 KiB) Viewed 5464 times

To eliminate the audio coming from the speakers when recording you can click the speaker icon (or slide the slider to the far left) when actively recording. When you want to listen to your audio you'll need to click the icon again (or return the slider to its original position).

Hope that helps!

Well, I have good news for anyone having similar trouble to what I have been describing as I have gotten things going!

System: Fedora 34 (with Pipewire)
DR Version: 17.3.2

1) Install alsa-plugins-pulseaudio (I have not needed this in the past but it's important here, evidently)
2) Create a file called /etc/asound.conf with the following content:
pcm.!default pulse
ctl.!default pulse
3) Restart alsactl (or reboot)
4) It works!

This also fixed a problem (perhaps it fixed it, not sure, I was having the problem before the mic fix and now it's gone) where the audio was severely lagging the video during editing.

I now need to figure out how to prevent the audio from coming out of the speakers while recording on the mic!

Well, this is not a real fix yet, but more like a workaround, because what this is doing is basically PipeWire is pretending itself as PulseAudio, and then PulseAudio pretending itself as ALSA, and then ALSA is picked by DaVinci Resolve. However, PipeWire is able to pretending itself as ALSA so it could then directly picked by DaVinci Resolve (and other ALSA clients), so it should theoretically reduce latency by removing an extra layer.

The problem is when use PipeWire's ALSA simulation, DaVinci Resolve won't pick the audio stream it sends. There is an issue opened for PipeWire, but the PipeWire maintainer has problems on getting more debug info so it is still not fixed:

https://gitlab.freedesktop.org/pipewire ... ssues/2870

If Blackmagic could help PipeWire find the reason why it does not work, that will be great as PipeWire is the new default sound server of Linux desktop and is considered better than PulseAudio.

The problem is when use PipeWire's ALSA simulation, DaVinci Resolve won't pick the audio stream it sends. There is an issue opened for PipeWire, but the PipeWire maintainer has problems on getting more debug info so it is still not fixed:

https://gitlab.freedesktop.org/pipewire ... ssues/2870

If Blackmagic could help PipeWire find the reason why it does not work, that will be great as PipeWire is the new default sound server of Linux desktop and is considered better than PulseAudio.

Agreed. Alynx and I have been trying fairly hard to get a solution there, to no avail.

It would be excellent if BMD could look in over there and get involved. Sooner or later, Pipewire will be standard across the board; either support that, or work out why ALSA-via-pulse/pipewire isn't working (specifically for recording, playback works fine).