MaartenBaert / ssr

SimpleScreenRecorder, a screen recorder for Linux
http://www.maartenbaert.be/simplescreenrecorder/
GNU General Public License v3.0
2.58k stars 290 forks source link

PULSE_SOURCE #669

Open mikhailnov opened 6 years ago

mikhailnov commented 6 years ago

Is it possible to take the value of PULSE_SOURCE as a pre-defined value of the recording device for SSR?

e.g. env PULSE_SOURCE=pa_joined_sink1.monitor PULSE_SINK=alsa_output.pci-0000_00_14.2.analog-stereo audacity

I want this feature for some automation in scripts. I've made a simple GUI https://gitlab.com/mikhailnov/pulsejoin which allows to clikc a button and make a virtual PulseAudio device which will combine both microphone and "Monitor of" sound output, it works with SSR to record both sound output and microphone. But I can't make a button to run SimpleScreenRecorder as Audacity because SSR does not use PULSE_SOURCE.

man pulseaudio | grep PULSE_

mikhailnov commented 6 years ago

For reference: https://bugs.chromium.org/p/chromium/issues/detail?id=880180

MaartenBaert commented 6 years ago

Can't you just modify the settings file in ~/.ssr/settings.conf before launching SSR to achieve this?

mikhailnov commented 6 years ago

That's a working variant, thank you. But what if, for example, I have more than one copy of SSR running?

MaartenBaert commented 6 years ago

This is currently not really supported, they will interfere with each others settings. I would have to add a command line option to use a different settings file to make that work. I can do that.

mikhailnov commented 6 years ago

I would appreciate that

12 сентября 2018 г. 4:33:21 GMT+03:00, Maarten Baert notifications@github.com пишет:

This is currently not really supported, they will interfere with each others settings. I would have to add a command line option to use a different settings file to make that work. I can do that.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/MaartenBaert/ssr/issues/669#issuecomment-420481511