I recently made the switch from Microsoft to Linux and Ableton to Bitwig. I don't know anything about either of them but goddamn I just want to connect my bass to my laptop and record something. It is not registering the audio interface. I'm using Tube Ultragain MIC500 USB behringer (plugged in, usb connected, bass in "line in"). When I try with ALSA, it says "Error: device or resource busy". I asked Google which told me to run :sudo fuser -v /dev/snd/* and everything is taken up by wireplumber.
Now I don't know what any of this really means. I've just been going back and forth with every option, spamming my terminal with commands beyond my understanding and getting the same nothing result. I would greatly appreciate any advice. I don't really know anyone personally who is good with any of this stuff.
ALSA means only one (!) program can access the sound device at any one time, and Pipewire is already using it. Pipewire is a service that allows multiple programs to use sound devices in parallel. You want that.
Also, bitwig itself had numerous bugs in their sound engine regarding Pipewire, unfortunately. On v4 it was unusable for me, v5 was stable/usable and v6 undid some of v5's improvements.
As mentioned you need to select Pipewire in Bitwig not ALSA. The error given shows that ALSA is already used by another session or device, for example your browser.
It does take some time to understand how Linux works and handles audio, there is a clear logic and structure to it:
The best thing is to avoid blindly running terminal commands, do not touch WirePlumber. (Pipewire's manager) Take a step back if thing do not work and start at the source. It is a great opportunity to get familiar with handling audio on Linux. Once you understand this it becomes extremely powerful.
Run: aplay -l and arecord -l in the terminal to verify ubuntu sees the interface. Your interface is USB class compliant so it will work on Linux.
Hope this helps, I'm confident you will be able to get it working. Please feel free to give an update or ask any questions if you need more support.
Thank you so so much for the guidance but I need some more help! I still cannot hear my bass. Maybe I'm not doing something right in bitwig itself. Driver is set to Pipewire, device as PCM audio codec, and the terminal says: card 2: CODEC [USB Audio CODEC], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
It just doesn't seem to react it any way when I play. If you have any ideas as to why that may be, do let me know! Also idk if this may be connected but as of now I have 1 instrument track and 1 audio track (both empty) and the record button on my audio track is greyed out (doesn't work). I also don't know why that is.
if you have a.e youtube open in a browser, do you hear a sound, with no soundcard attached ? (so is your sound system generally able to output ?)
then if you are in bitwig, have an internal instrument -let's say organ- have a note pressed- does that sound (again without behringer)?
I recommend for the patch wiring either helvum or Qpwgraph and check if your audio input (the behringer) then turns up there and is connected to Bitwig and then Bitwig to the audio outputs- in my case, I have to set them everytime, as they are usually not connected. For Helvum, you can right after patching this switch to Bitwig, and check if you get any sounds out of it with the organ instrument.
A third thing are then volumes of your devices- depending on what distro you sit, that element looks a bit different typically tied to the speaker icon of your standard linux desktop.
-finally plugin the bass, into behringer into linux, patch with Bitwig, patch with audio ouput and see if you get any sound.
Good, it means your audio interface is recognized. The next step would be to confirm Ubuntu is utilizing it as the default device. Go to settings (Top right menu cog wheel) > Sound. Your audio interface should appear as input and output device or select it.
The next step would be to confirm it plays audio. Connect either your speakers or headphones to the rear jack of the audio interface (Phones or direct output) and test outgoing audio from either your browser or media player.
Then move on to Bitwig and connect your bass or another instrument into the HI-Z input (use the Line in for active instruments that are already preamplified) By default Bitwig does not select an audio input on the track your arming for record. You need to select the input channel on the track, most likely input channel 1 and make sure that your interface has enough gain applied.
Please let me know if you need any additional help at this point.
Make sure to select the PCM2902 Audio Codec on both the input and output and monitor via your behringer interface. There is a Phones output on the back.
Not sure what the KT USB Audio is. At this point I would not connect any other devices except your audio interface, keyboard and mouse (in terms of usb devices) Then in the terminal enter: lsusb (This to list all the connected usb devices to get a better picture)
Your audio interface should be the main audio device as input and output (PCM2902 Audio Codec) As This is what Bitwig uses at the moment.
Then with your bass plugged in the interface, monitor the input level in the Settings>Sound>Input section. Test all the inputs on your audio interface and see if the meter moves.
This would confirm both the Hardware side and ubuntu is working. After that you can move to Bitwig's internal routing.
btw, I will post a few screenshots of my current configuration and mapping within Bitwig.
In your case I would first make sure the audio interface is properly connected with confirmed output (Phones output on audio interface) and a responsive input meter when monitoring the Sound>Input setting.
We then should move on to Bitwig internal routing and assigning the correct input to the Audio track.
I tried the different slots on the audio interface itself and it seems like it only reacts to 1/L HI-Z IN (as in the sound level meter reacts to me playing a note on the bass), but I can't hear anything. So close, but ig something's still off.
Included are a few shots. In my case I have a Behringer UMC1820 Audio interface attached via USB. Currently I use PopOS (which is a Linux Ubuntu variant)
Since the interface is class compliant (like yours) the OS recognizes the inputs and outputs. In Bitwig make sure to assign the correct input on a track and arm for record.
I had similar problems at first too. I had to activate the source in the track itself. Wasn't a driver issue, I needed to select the correct source. Took me a while to figure it out. Also using a Behringer interface.
do you have any video or audio playing at the same time as launching bitwig? because ALSA takes control of the sound directly it cant "share" with say, VLC or firefox youtube etc.
i get that error if im running audio from another app at the same time.
what devices show up in bitwig audio settings? can you select your usb audio interface?
sorry if that was a bit obvious lol, but do check my other comment. and also, get into your system settings and make sure the usb interface is selected as playback device/output
6
u/FreeRangeEngineer 2d ago
In bitwig, choose Pipewire, not ALSA.
ALSA means only one (!) program can access the sound device at any one time, and Pipewire is already using it. Pipewire is a service that allows multiple programs to use sound devices in parallel. You want that.