Behringer x32 usb record audacity windows

You might find though that you can't start the zita utilities on a specific card if you recently used it with PA.

In your case I don't think there will be a problem getting the soundcard that JACK wants from PA as you run JACK2-dbus and that will ask PA to release the soundcard. One problem might be that PA and JACK might fight about who gets access to the soundcard. If you stop JACK and run pavucontrol, you find the missing soundcards under Configuration? I don't know why they aren't available as sinks in pavucontrol. So we have to be pragmatic and live with what we have. I think it would be much better if we had 'raw' alsa, jack, and pulseaudio integrated in the kernel as a common interface with better integration and userspace tools, but for various reasons it can't really be done (yet maybe), and it wasn't done. IMO, all of this is needlessly complicated, but once you have it setup it's easy to use. I know where close and I must be missing something. Is it this hard to get configured for everyone else? I'm am at a loss why I'm having so many issues yet there's tons of people using pulse and jack. I loaded qjackctl and verified the following: **** List of PLAYBACK Hardware Devices ****Д¬ard 0: SB, device 1: ALC892 Digital Д¬ard 1: NVidia, device 3: HDMI 0 Д¬ard 1: NVidia, device 7: HDMI 1 Д¬ard 1: NVidia, device 8: HDMI 2 Д¬ard 1: NVidia, device 9: HDMI 3 **** List of CAPTURE Hardware Devices ****Д¬ard 0: SB, device 0: ALC892 Analog Д¬ard 0: SB, device 2: ALC892 Alt Analog Д¬ard 2: USB, device 0: USB Audio We can cover that later, just concentrate on getting JACK and zita-ajbridge setup first. Once you have it setup and working, then add pulseaudio to allow easy output from browsers, games etc to the soundcard you want to output to.

You might need to add more parameters later to fine tune things, but to just get it working go with the simple.ДЄlso leave pulseaudio out of it until you have the basic JACK setup that allows you to do what you want with audacious (or other JACK clients). AFAIK it picks up the rest of the settings from the running JACK server. Also something like zita-j2a -d hw:SB or zita-a2j -d hw:USB ought to be enough. You might also need to use alsamixer to verify that nothing is muted or has it's volume turned down.Дo run the zita-ajbridge utilities in a terminal window, so that you see that they are working and if there is some terminal output before you stick them in a script or add them to qjackctl. You might need to make connections in the qjackctl GUI, or do it from a script with the jack_connect utility. No need to use only capture or playback for the device JACK is using. In that case run JACK either on the hw:USB or hw:SB device, and connect the other's input/outputs (depending on what you want) with the zita utilities. pulseaudio-jack is installed, and once I start jack2dus and go into qjackctl/connections, I can see the following: So it is easy via pavucontrol or general sound configuration to make it work, rather than looking into internal devices and alsamixer, which is what jack is exactly what I'm trying to do, and so far not succeeding, no audio is played back in audacity. The fact is that jack doesn't allow to touch the internal mixer whereas pulseadio does. In contrast, the USB card is simpler it only has a duplex device so it is easy to get it up and running via jack. It could even have more than one internal device in which case things would be more involved. I assume that the SB live has an internal mixer which alsa can access to, via alsamixer. Pablo wrote:I think that it makes more sense for your use case if you use jack with the USB card (capture-only mode seems more adequate if the audio outputs are not in use) and the pulseaudio jack sink for the SB and I will try to explain the reason why.

Behringer x32 usb record audacity windows