I would like for any Pulse Audio developers to see this if possible. I have had this on my mind for some time and I’m getting very frustrated about it:
With the versions of SuSE prior to 11.3 (before Pulse Audio), I was able to simply open my channel mixer (either kmix or alsamixer) and set my treble/bass volume levels and mute the microphone, then open my preferred recording software, push “Record” then start playing my song or whatever. It was that simple! **The sound coming from the computer’s sound card was captured. **
Now, in order to do the same thing, to set up my volume for bass and treble, I have to do this in a terminal:
alsamixer -c 0
because there is no GUI like there used to be for getting to this mixer.
Also, I have to create a null device:
pactl load-module module-null-sink sink_name=something
(insert any name where it says, ‘something’.)
Then a lookback - do this twice:
pactl load-module module-loopback sink=something
(insert the same name --it has to match the first command)
I as an enduser shouldn’t have to do this. I shouldn’t have to hunt around for a solution for something that used to be very simple to do!
Then looking in pavucontrol:
Set 1st. loopback from null to Monitor Internal Analog Stereo.
Set 2nd look back from null just to Internal Audio Analog Stereo.
**Once again, I as an enduser shouldn’t have to do it like this. It is too complicated and takes longer to do the task I want to do. **
>:(
*If a null device and loopbacks are necessary, why can’t the developers include this? *
How about a script like the one used for usb device detection? That does a fine job of detecting what was plugged in, and making the device available to whatever software needs it. Well, do this for any audio devices too: Audio device ‘A’ was detected and is brand A and needs xyz driver. Ok, make a null device and loopback for it. A second audio device was detected? The script makes a 2nd loopback for it. A 3rd audio device detected? The script makes a 3rd loopback for that, etc.
Just my 2¢ worth.
