mirror of
https://github.com/tiyn/wiki.git
synced 2026-04-15 16:54:48 +02:00
EasyEffects: Added Autostart
This commit is contained in:
@@ -13,6 +13,53 @@ An installation via [Flatpak](./flatpak.md) is also possible.
|
||||
|
||||
Easyeffects can apply `Effects` to input and output sound.
|
||||
|
||||
### Autostart
|
||||
|
||||
Easyeffects can be started in various ways.
|
||||
|
||||
The service can be started including the window with the following.
|
||||
It will have to be called each startup.
|
||||
|
||||
```sh
|
||||
easyeffects
|
||||
```
|
||||
|
||||
Alternatively it can be started in the background with the following command.
|
||||
This command also has to be called each time the system starts.
|
||||
|
||||
```sh
|
||||
easyeffects --gapplication-service
|
||||
```
|
||||
|
||||
The two former commands will only work if called on each startup.
|
||||
The easiest way to do this is by using [SystemD](/wiki/linux/systemd.md).
|
||||
The following will work analogously to the path explained in
|
||||
[the corresponding section of the SystemD entry](/wiki/linux/systemd.md#run-command-on-boot).
|
||||
|
||||
Run the following command to edit the configuration file for the newly created EasyEffect service.
|
||||
|
||||
```sh
|
||||
systemctl --user edit --force -full easyeffects.service
|
||||
```
|
||||
|
||||
Afterward set the contents of this file to the following.
|
||||
Due to EasyEffect working together with [Pipewire and Wireplumber](/wiki/linux/pipewire.md) some
|
||||
precautions have to be taken to start it before these two.
|
||||
|
||||
```sh
|
||||
[Unit]
|
||||
Description=EasyEffects (GApplication Service)
|
||||
After=pipewire.service wireplumber.service
|
||||
PartOf=graphical-session.target
|
||||
|
||||
[Service]
|
||||
ExecStart=/usr/bin/easyeffects --gapplication-service
|
||||
Restart=on-failure
|
||||
|
||||
[Install]
|
||||
WantedBy=graphical-session.target
|
||||
```
|
||||
|
||||
### Noise cancellation
|
||||
|
||||
Setup
|
||||
|
||||
@@ -10,6 +10,13 @@ It is used for service configuration and startup.
|
||||
To run a command (in this case `/bin/bash /root/run.sh`) create the following
|
||||
file at `/etc/systemd/system/` with a name ending on `.service`.
|
||||
In this case it is called `unturned.service`.
|
||||
Alternatively to creating the command manually the following command can be used.
|
||||
|
||||
```sh
|
||||
systemctl edit --force --full unturned.service
|
||||
```
|
||||
|
||||
And set the contents to the following.
|
||||
|
||||
```txt
|
||||
[Unit]
|
||||
@@ -31,17 +38,8 @@ initializing.
|
||||
After=pve-guests.service
|
||||
```
|
||||
|
||||
Such a service can be started by running:
|
||||
|
||||
```sh
|
||||
sudo systemctl start unturned
|
||||
```
|
||||
|
||||
Alternatively it can be enabled to start at every boot by running:
|
||||
|
||||
```sh
|
||||
sudo systemctl enable unturned
|
||||
```
|
||||
A service that was created this way can then be started as explained in
|
||||
[the corresponding section](#startstopenabledisable-a-service-and-retrieve-its-logs).
|
||||
|
||||
### Start/Stop/Enable/Disable a service and Retrieve its Logs
|
||||
|
||||
@@ -54,6 +52,8 @@ The `disable` keyword stops the service from starting automatically.
|
||||
|
||||
Logs of the last start of the service can be found by running `systemctl status <service-name>`.
|
||||
|
||||
Additionally the `--user` flag can be set to start the service only for the current user.
|
||||
|
||||
### Retrieving the SystemD Logs
|
||||
|
||||
SystemD logs can easily be found using the `journalctl` command.
|
||||
|
||||
Reference in New Issue
Block a user