Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store persisten configuration #20

Open
pagdot opened this issue Mar 3, 2020 · 6 comments
Open

Store persisten configuration #20

pagdot opened this issue Mar 3, 2020 · 6 comments

Comments

@pagdot
Copy link

pagdot commented Mar 3, 2020

I'm using a combined-sink module, but have to reconfigure it on each boot of the system. Would it be possible to store a configuration persistent? Maybe using an additional button or a checkbox?

@Meister1593
Copy link

Really wanted thing for sure
Implementation could save all of this into some form of file somewhere (or in .local/share) and then on startup be parsed.
If one of the modules wouldn't match, parsing should either stop or don't start at all (pre-check before creating sinks and etc)
For this good thing to be implemented is #4 issue too.

@pagdot
Copy link
Author

pagdot commented Sep 26, 2020

It could generate/own a config file for pulseaudio I don't know how pulseaudio would handle issues but it would probably work even with missing sources/sinks

@REMjn832
Copy link

I love using this tool for sure (thank you!), but needing to recreate my entire sinc/source map every-time I reboot sort of sucks. The ability to save it to a PA config, or something would help a lot!! Thanks

@Meister1593
Copy link

Meister1593 commented Mar 18, 2021

I love using this tool for sure (thank you!), but needing to recreate my entire sinc/source map every-time I reboot sort of sucks. The ability to save it to a PA config, or something would help a lot!! Thanks

In case you urgently need some tool to save/restore configurations, i would consider looking into a Pipewire
It combines Pulse, Jack, Alsa together and you can use some tools like QJackctl. It's mature enough to use it daily (although bluetooth is a bit rough, it's still far better than plain pulse and it's modules setup)

Not only it's pretty easy to use, it also pretty much entirely integrated with pulse. To save/restore you can use Patchbay inside qjackctl.
Patchbay isn't perfect (like, you have to name stuff right and expect the same name), but still better than nothing.

@REMjn832
Copy link

Thanks @Meister1593. I had Pipewire installed, but then every time I tried to do arch updates, I received warnings about running both PulseAudio and Pipewire, I had to remove Pipewire in order to stop receiving those warnings. Having said that, I am going to looking into the QjackCtl module that be used with PA and see if maybe that could work in the interim. Thanks for the suggestion! :)

@Meister1593
Copy link

Thanks @Meister1593. I had Pipewire installed, but then every time I tried to do arch updates, I received warnings about running both PulseAudio and Pipewire, I had to remove Pipewire in order to stop receiving those warnings. Having said that, I am going to looking into the QjackCtl module that be used with PA and see if maybe that could work in the interim. Thanks for the suggestion! :)

Why... do you need to run both pipewire and pulseaudio independently?
Pipewire-pulse replaces pulse server and acts like one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants