You are not logged in.
Pages: 1
Topic closed
Hi guys.
I'm trying to record my screen with SSR but the output file presents a VERY low sound, to hear that i have to set the volume of VLC at 200% and it's still low.
I've tried to do it on ubuntu and SSR works correctly so i think i'm missing something on Arch.
I post here some screen of my configuration:
-SSR: 1 2 3
-PulseAudio: 1 2 3
On pulse audio if i increase the volume of AudioIPC Server in the playback tab the output file presents a terrible background noise.
Last edited by brofjst (2019-09-27 13:16:18)
Offline
Is the volume of the SSR audio stream in the pavucontrol recording tab set correctly?
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
yes it's set correctly
image
Offline
Through all the screenshots you managed not to show the most interesting tab: Input Devices
Offline
i did not post the input devices because i found the same problem on 2 different pc: the laptop and the desktop pc which hasn't a microphone and i tought the issue was not related to it.
Btw here it is the screenshot from the laptop: Image
Offline
What if you put the mic input to 100%? ![]()
Offline
Pulse has better diagnostic tools than posting screenshots of some UI...
pacmd list-sinks
pacmd list-sink-inputs
pacmd list-sources
pacmd list-source-outputs
#Or since pulse 13
pa-infoLast edited by V1del (2019-09-26 15:40:13)
Offline
What if you put the mic input to 100%?
nothing changed
Last edited by brofjst (2019-09-26 15:52:04)
Offline
Source #1
State: SUSPENDED
Name: alsa_input.pci-0000_00_1b.0.analog-stereo
Description: Built-in Audio Analog Stereo
...
Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 8250 / 13% / -54.00 dBThis looks like it is turned down in alsa. Please check your inputs in alsamixer.
Last edited by Swiggles (2019-09-26 16:16:55)
Offline
Your monitor source, which is where the output is actually recording from, is at 15% (also next time you might want to post that while trying to record) Warning with all your other overdrives this might blow your ears out:
pactl set-source-volume alsa_output.pci-0000_00_1b.0.analog-stereo.monitor 50%,50% #Set to whateverHint: in the output devices tab of pavucontrol, scroll down or increase the size of your window.
@Swiggles from what I gather the mic isn't the problem but desktop audio being recorded, it also is generally normal to have a low base volume on Mics, that shouldn't be the inherent issue.
Last edited by V1del (2019-09-26 16:20:45)
Offline
@V1del doesn't the base volume define the 100% mark for PA?
Anyway it sounds like some knob is turned down too much, so I would put all to 100% and adjust once it is clear that this is the issue. Ofc you have to be careful with your output.
Though I would trust on V1dels experience here, because that's usually correct! ![]()
Offline
@Swiggles it does, but from what I've seen it is set generally on the low side for most mics, regardless of the ALSA/PA volume knob (that one might be influenced by mic boost settings, but you often don't want to mess with those), which makes sense as they usually start to clip at a lower overall volume (one could tell pulse to not care with the ignore_dB=true option to udev-detect, but having a lower base volume on the mic is usually the wanted and correct behaviour).
That aside aside, the screenshot showing the SSR recording active actually shows that we are concerned with the output card monitor here (which is also why moving around the mic knob didn't change anything, as it doesn't factor in in that case)
Offline
pactl set-source-volume alsa_output.pci-0000_00_1b.0.analog-stereo.monitor 50%,50% #Set to whatever
Good job mate, this solved the issue, thank you!
Offline
Found this thread via google. The suggested idea worked for me, but the command was different:
1. call `pacmd list-sources` and find "Monitor of Build-in Audio... " there
2. run `pacmd set-source-volume 4 65535` , where 4 is the index of the item in the list from previous command.
Offline
There's really nothing different about your solution other than to expected variances in how hardware is named.
In any case, while I'm glad this helped you as well, please don't necrobump old threads just to confirm that the solution does in fact work as well.
Closing this old topic.
Offline
Pages: 1
Topic closed