Quote:
Originally Posted by
Sulljason
That sounds right. Used a dual male 3.5mm cable (green to blue analog line in) then accidentally changed a setting some where. Idk where, sounds horrible now -.- so finicky. Virtual is preferred, so a config would be very much appreciated.
Edit: Some how the mic volume maxed it self to above 100% so it was getting amplified (horribly I might add). Virtual is still desired though.
Question: Will "no mixing" disable the "feature" where it lowers the volume on louder parts of the song to make it around the same volume as the beginning?
Okay, so here's an excerpt from a config I never had working properly:
Code:
Code:
...
### Load audio drivers statically
### (it's probably better to not load these drivers manually, but instead
### use module-udev-detect -- see below -- for doing this automatically)
...
...
load-module module-null-sink sink_name=pamix
load-module module-loopback latency_msec=2 sink=pamix
load-module module-loopback latency_msec=2 sink=pamix
...
...
Notice that the lines above are very undescriptive - this is probably where I went wrong, looking into things for you, I may have realized how to fix my own problems;
The problem with the above is that I name a "null-sink" which you can think of as a "virtual audio device" and then route two audio sources to it with a 2msec delay. Problem: What audio sources?
Solution:
Code:
Code:
load-module module-null-sink sink_name=pamix
load-module module-loopback source=0 sink=pamix
load-module module-loopback source=2 sink=pamix
You can obviously use the names for your sources or their numeric identifiers...
To find out what the number is run the following:
Code:
Code:
pactl list | grep -A2 'Source #'
Obviously after making any changes to your /etc/pulse/default.pa you will need to restart pulse to test it; to accomplish this run the following:
Code:
Code:
pulseaudio -k && pulseaudio -D
Anyways hope this at least gets you pointed in the right direction.
Edit: You may be able to get by just loading the loopback module as then a new input device should appear in pavucontrol or whatever pulse control you use. Haven't tested this - also I'm unable to load the loopback module myself currently it just errors out. You may also need to enter the Pulse command line using "pacmd" and use list-sources to get proper source names or numbers. The command I posted should work.
Even more interesting I can load the loopback module in pacmd using load-module module-loopback.
Edit: success! kind of. I was able to get it working succesfully adding a "monitor of null output" input device, but only by doing the commands manual in pacmd. I'll see if I can get it working with the config later I have to leave for work.