Merge pull request #32 from linerjoe/docs-win

Windows documentation in MD format
3ll3d00d · Mar 3, 2021 · 93eab11 · 93eab11
2 parents 3a6e2c4 + 3202e9a
commit 93eab11
Show file tree

Hide file tree

Showing 71 changed files with 533 additions and 152 deletions.
diff --git a/docs/img/home01.png b/docs/img/home01.png
diff --git a/docs/img/home02.png b/docs/img/home02.png
diff --git a/docs/img/home03.png b/docs/img/home03.png
diff --git a/docs/img/home04.png b/docs/img/home04.png
diff --git a/docs/img/home05.png b/docs/img/home05.png
diff --git a/docs/img/home06.png b/docs/img/home06.png
diff --git a/docs/img/home07.png b/docs/img/home07.png
diff --git a/docs/img/home08.png b/docs/img/home08.png
diff --git a/docs/img/ezbeq-01.png → docs/img/rpi01.png b/docs/img/ezbeq-01.png → docs/img/rpi01.png
diff --git a/docs/img/ezbeq-02.png → docs/img/rpi02.png b/docs/img/ezbeq-02.png → docs/img/rpi02.png
diff --git a/docs/img/ezbeq-03.png → docs/img/rpi03.png b/docs/img/ezbeq-03.png → docs/img/rpi03.png
diff --git a/docs/img/ezbeq-04.png → docs/img/rpi04.png b/docs/img/ezbeq-04.png → docs/img/rpi04.png
diff --git a/docs/img/ezbeq-05.png → docs/img/rpi05.png b/docs/img/ezbeq-05.png → docs/img/rpi05.png
diff --git a/docs/img/ezbeq-06.png → docs/img/rpi06.png b/docs/img/ezbeq-06.png → docs/img/rpi06.png
diff --git a/docs/img/ezbeq-07.png → docs/img/rpi07.png b/docs/img/ezbeq-07.png → docs/img/rpi07.png
diff --git a/docs/img/ezbeq-08.png → docs/img/rpi08.png b/docs/img/ezbeq-08.png → docs/img/rpi08.png
diff --git a/docs/img/ezbeq-09.png → docs/img/rpi09.png b/docs/img/ezbeq-09.png → docs/img/rpi09.png
diff --git a/docs/img/ezbeq-10.png → docs/img/rpi10.png b/docs/img/ezbeq-10.png → docs/img/rpi10.png
diff --git a/docs/img/ezbeq-11.png → docs/img/rpi11.png b/docs/img/ezbeq-11.png → docs/img/rpi11.png
diff --git a/docs/img/ezbeq-12.png → docs/img/rpi12.png b/docs/img/ezbeq-12.png → docs/img/rpi12.png
diff --git a/docs/img/ezbeq-13.png → docs/img/rpi13.png b/docs/img/ezbeq-13.png → docs/img/rpi13.png
diff --git a/docs/img/ezbeq-14.png → docs/img/rpi14.png b/docs/img/ezbeq-14.png → docs/img/rpi14.png
diff --git a/docs/img/ezbeq-15.png → docs/img/rpi15.png b/docs/img/ezbeq-15.png → docs/img/rpi15.png
diff --git a/docs/img/ezbeq-16.png → docs/img/rpi16.png b/docs/img/ezbeq-16.png → docs/img/rpi16.png
diff --git a/docs/img/win01.png b/docs/img/win01.png
diff --git a/docs/img/win02.png b/docs/img/win02.png
diff --git a/docs/img/win03.png b/docs/img/win03.png
diff --git a/docs/img/win04.png b/docs/img/win04.png
diff --git a/docs/img/win05.png b/docs/img/win05.png
diff --git a/docs/img/win06.png b/docs/img/win06.png
diff --git a/docs/img/win07.png b/docs/img/win07.png
diff --git a/docs/img/win08.png b/docs/img/win08.png
diff --git a/docs/img/win09.png b/docs/img/win09.png
diff --git a/docs/img/win10.png b/docs/img/win10.png
diff --git a/docs/img/win11.png b/docs/img/win11.png
diff --git a/docs/img/win12.png b/docs/img/win12.png
diff --git a/docs/img/win13.png b/docs/img/win13.png
diff --git a/docs/img/win14.png b/docs/img/win14.png
diff --git a/docs/img/win15.png b/docs/img/win15.png
diff --git a/docs/img/win16.png b/docs/img/win16.png
diff --git a/docs/img/win17.png b/docs/img/win17.png
diff --git a/docs/img/win18.png b/docs/img/win18.png
diff --git a/docs/img/win19.png b/docs/img/win19.png
diff --git a/docs/img/win20.png b/docs/img/win20.png
diff --git a/docs/img/win21.png b/docs/img/win21.png
diff --git a/docs/img/win22.png b/docs/img/win22.png
diff --git a/docs/img/win23.png b/docs/img/win23.png
diff --git a/docs/img/win24.png b/docs/img/win24.png
diff --git a/docs/img/win25.png b/docs/img/win25.png
diff --git a/docs/img/win26.png b/docs/img/win26.png
diff --git a/docs/img/win27.png b/docs/img/win27.png
diff --git a/docs/img/win28.png b/docs/img/win28.png
diff --git a/docs/img/win29.png b/docs/img/win29.png
diff --git a/docs/img/win30.png b/docs/img/win30.png
diff --git a/docs/img/win31.png b/docs/img/win31.png
diff --git a/docs/img/win32.png b/docs/img/win32.png
diff --git a/docs/img/win33.png b/docs/img/win33.png
diff --git a/docs/img/win34.png b/docs/img/win34.png
diff --git a/docs/img/win35.png b/docs/img/win35.png
diff --git a/docs/img/win36.png b/docs/img/win36.png
diff --git a/docs/img/win37.png b/docs/img/win37.png
diff --git a/docs/img/win38.png b/docs/img/win38.png
diff --git a/docs/img/win39.png b/docs/img/win39.png
diff --git a/docs/img/win40.png b/docs/img/win40.png
diff --git a/docs/img/win41.png b/docs/img/win41.png
diff --git a/docs/img/win42.png b/docs/img/win42.png
diff --git a/docs/img/win43.png b/docs/img/win43.png
diff --git a/docs/index.md b/docs/index.md
@@ -4,179 +4,74 @@ ezbeq is a web interface that works in conjunction with minidsp-rs, which allows
 
 ## Pre-Requirements
 
-ezbeq and minidsp-rs run on Linux, Windows, or Mac operating systems, but this document walks through the installation process on a Raspberry Pi. The following systems are required to follow this document:
+ezbeq and minidsp-rs run on Linux, Windows, or Mac operating systems. Basic instructions are provided for installation and setup on Raspberry Pi (running RaspberryOS/raspbian) and Windows. The RPi documentation may also be used on an x86 machine running a Debian-based linux distribution (Debian, Ubuntu, Mint, etc).
 
-- MiniDSP 2x4HD
-- Raspberry Pi (RPi) – device should be accessible on the network, and already have Raspbian installed and updated. Raspbian Buster is used for this document.
-- USB cable connecting the Raspberry Pi and MiniDSP 2x4HD
+The following requirements should be met before attempting an installation:
+
+- Functional MiniDSP 2x4HD ([https://www.minidsp.com/products/minidsp-in-a-box/minidsp-2x4-hd](https://www.minidsp.com/products/minidsp-in-a-box/minidsp-2x4-hd))
+- Windows or Linux based system (Raspberry Pi) with network connectivity
+- USB cable connecting the computing system to the MiniDSP 2x4HD
 - Internet connection
 - Backup copy of all MiniDSP 2x4HD settings.
 
 NOTE – ezbeq and minidsp-rs will be modifying the INPUT settings of the MiniDSP 2x4HD, but please take appropriate backups.
 
-## Installation Steps
-
-### Install and verify minidsp-rs
-
-minidsp-rs is a utility, written by mrene on avsforum.com, which allows the system to communicate with the MiniDSP 2x4HD, without using the proprietary minidsp plugin. Pre-compiled binaries are available for most operating systems, and there is an available Debian package.
-
-1\. Open a shell on the RPi, or SSH to the RPi.
-
-2\. Download the latest version of minidsp-rs for Arm from [here](https://github.com/mrene/minidsp-rs/releases)
-``` 
-wget https://github.com/mrene/minidsp-rs/releases/download/v0.0.5/minidsp_0.0.5_armhf.deb
-```
-Note that the filename above is current as of 2/2/2021. Please use the current version.
-![Figure 1 – Example downloading of v0.0.5](./img/ezbeq-01.png)
-
-3\. Install the downloaded .deb file via `sudo apt install </path/to/file>`
-```
-sudo apt install ./minidsp_0.0.5_armhf.deb
-```
-![Figure 2 – Example installation of the .deb package](./img/ezbeq-02.png)
-
-4\. To confirm basic functionality, type `minidsp` and press Enter.
-![Figure 3 – Example of &quot;minidsp&quot; output](./img/ezbeq-03.png)
-
-5\. If the MiniDSP 2x4HD is connected properly, similar information to Figure 3 will be displayed. Note the &quot;preset: 1&quot; in the image. That indicates that the MiniDSP 2x4HD is set to Config slot 2. The minidsp-rs application starts at 0 for the config presets, so 0 = Config slot 1, and so on.
-
-6\. If the MiniDSP 2x4HD is not detected, or is not connected, the following error will appear.
-![Figure 4 – Example of minidsp error message](./img/ezbeq-04.png)
-
-### Install and verify ezbeq
-
-ezbeq is a web application which uses minisdsp-rs installed earlier to send the BEQ filters to an attached MiniDSP 2x4HD. The following steps walk through installing ezbeq.
-
-1\. Open a shell on the RPi, or SSH to the RPi.
-Install the pre-requisite python packages. Raspbian Buster had all but one needed package already installed. Run this command to install all of them (already installed packages will be skipped): `sudo apt install python3 python3-venv python3-pip libyaml-dev`
-![Figure 5 – Example of installing python pre-requisites](./img/ezbeq-05.png)
-
-2\. Setup the python environment by running the follow commands:
-```
-mkdir python
-cd python
-python3 -m venv ezbeq
-cd ezbeq
-```
-![Figure 6 – Example of preparing environment](./img/ezbeq-06.png)
-
-3\. Start the install of the ezbeq application. The required python modules will be installed. Run the following commands:
-```
-. bin/activate
-pip install ezbeq
-```  
-![Figure 7 – Example of launching the installer](./img/ezbeq-07.png)
-
-The installer will download and install the required modules. This may take quite a while, depending on the speed of your RPi and internet connection. The information below is truncated.
-
-![Figure 8 – Example of successful installation of ezbeq](./img/ezbeq-08.png)
-
-4\. Launch ezbeq manually, to verify functionality. Type the following:
-```
-    cd bin
-    ./ezbeq
-```
-![Figure 9 – Example of launching ezbeq](./img/ezbeq-09.png)
+## Suggested interaction of ezbeq and official MiniDPS plugin
 
-5\. ezbeq runs on port 8080 of the RPi by default. On another device connected to the local network, open a web browser and connect to the RPi port 8080. Note that the web server is not encrypted, so the URL must be entered as http, otherwise most current browsers will automatically try to connect using HTTPS (secured) and fail.
-Open a browser window to `http://<ip address of Rpi>:8080`
-![Figure 10 – Example of ezbeq interface](./img/ezbeq-10.png)
+- Neither ezbeq/minidsp-rs or the official plugin are able to read the configuration from the MiniDSP 2x4HD
+- If changes are made with ezbeq, the next time the official plugin is loaded, it will want to initialize or load from a backup, because it detects a change (but doesn't know what is).
+- When using ezbeq, there is no need to merge the BEQ with any applicable house curve.
 
-6\. To load a BEQ onto the MiniDSP 2x4HD, select a title (search is available in the upper right corner), then click on the &quot;up arrow&quot; on the corresponding config slot to be used.
-![Figure 11 – Example of selecting a title and uploading to config slot 2](./img/ezbeq-11.png)
+1\. Use the official plugin to set an initial configuration, including enabling input to output routing, output gain, delay, and filters. House curves should be loaded on the outputs.
 
-7\. If the update is successful, the title will be display in the &quot;Loaded&quot; column. Otherwise, &quot;ERROR&quot; will be displayed.
-![Figure 12 – Example of successful title load](./img/ezbeq-12.png)
+2\. Save this initial configuration, in case it needs to be loaded in the future.
 
-### Automatically launch ezbeq on boot
+3\. Use ezbeq to load BEQ's on the inputs. The output configurations will not be touched.
 
-These steps are optional but are highly recommended. If these steps are not followed, ezbeq will need to be started manually after every reboot of the RPi.
+## Installation
 
-1\. Open a shell on the RPi, or SSH into the RPi.
+Follow one of the two guides provided (Windows or RPi).
 
-2\. Create the service file, issuing the following command:
-```
-sudo nano /etc/systemd/system/ezbeq.service
-```
-![Figure 13 – Example editing the service file](./img/ezbeq-13.png)
+## Usage
 
-3\. Add the information below to the file. When complete, save the file (Ctrl-O), then exit (Ctrl-X).
-NOTE – If the ezbeq software was installed using a different user than &quot;pi&quot;, ensure to modify the settings below, replacing &quot;pi&quot; with the correct userID.
-```
-[Unit]
-Description=ezbeq
-After=network.target
-    
-[Service]
-Type=simple
-User=pi
-WorkingDirectory=/home/pi
-ExecStart=/home/pi/python/ezbeq/bin/ezbeq
-Restart=always
-RestartSec=1
+### Initial Screen
 
-[Install]
-WantedBy=multi-user.target
-```
-![Figure 14 – Example service file](./img/ezbeq-14.png)
+- The * next to a config slot indicates that slot is active (and also shows that ezbeq + minidsp-rs is working properly). If no * is present, then there is a problem talking to the MiniDSP 2x4HD.
 
-4\. Register and start the service. Note that if ezbeq is still running from the earlier steps, it needs to be stopped (Ctrl-C), otherwise the service will not start.
-```
-sudo systemctl enable ezbeq.service
-sudo service ezbeq start
-```
-![Figure 15 – Register and start the ezbeq service](./img/ezbeq-15.png)
+![Initial Screen](./img/home01.png)
 
-5\. Verify the service started by issuing this command:
-```
-sudo journalctl -u ezbeq.service
-```
-![Figure 16 – Log messages showing the service is running](./img/ezbeq-16.png)
+### Activate a config slot
 
-6\. Reboot the RPi, and then check the website again.
-```
-sudo shutdown -r now
-```
+Click the play icon next to a slot number to change to that configuration slot. This will not make any changes to the BEQ loaded, just switches to a configuration slot.
 
-### Updating minidsp-rs
+![Change Config Slot](./img/home02.png)
 
-Updating minidsp-rs is the same process outline in section I above.
+If successful, the * will now denote the newly active config slot.
 
-1\. Open a shell on the RPi, either locally, or via SSH.
+![Successful config slot change](./img/home03.png)
 
-2\. Download the latest Arm .deb package from [https://github.com/mrene/minidsp-rs/releases](https://github.com/mrene/minidsp-rs/releases)
-Example: `wget https://github.com/mrene/minidsp-rs/releases/download/v0.0.5/minidsp_0.0.5_armhf.deb`
+### Search
 
-3\. Install the .deb package using the following command: `sudo apt install ./<filename>`
-Example: `sudo apt install ./minidsp_0.0.5_armhf.deb`
+To search for a title, type a portion of the name into the search field in the upper right corner. The listed titles will automatically change to match the search parameters.
 
-### Updating ezbeq
+![Search for a title](./img/home04.png)
 
-Updating ezbeq follows a similar approach as the initial install, with an extra flag.
+### Load a BEQ
 
-1\. Open a shell on the RPi, either locally, or via SSH.
+Select a title from the list, and then click the Up arrow on the slot to which the BEQ should be loaded. If the chosen slot is different than the currently active slot, ezbeq will make the requested slot active, and then load the BEQ.
 
-2\. Run the following commands:
-```
-cd python
-cd ezbeq
-. bin/activate
-pip install --upgrade ezbeq
-```
+![Load BEQ](./img/home05.png)
 
-3\. If ezbeq is configured to run on boot (section III), restart the ezbeq service to ensure the update takes effect:
-```
-sudo service ezbeq restart
-```
+If the BEQ loaded correctly, the title will be listed in the Loaded column, and the * will show the config slot is active.
 
-## Which Raspberry Pi should I buy?
+![Loaded BEQ](./img/home06.png)
 
-This question has been asked a few times. The biggest key to a successful Raspberry Pi implementation is a solid power supply.
+### Clear a BEQ
 
-For North American users, kits from CanaKit ([https://canakit.com](https://canakit.com)) have been recommended by some users. Note that this is not an endorsement of their product, nor is there any affiliation with this company.
+To clear a config slot, click on the "X" for the appropriate slot.
 
-The software has been run on Pi3 successfully, and should also run on Pi4.
+![Clear slot](./img/home07.png)
 
-## A few other notes.
+If the clearing process was successful, the Loaded column will now display "Empty".
 
-Bear in mind that, so far, settings cannot be read back from the MiniDSP 2x4HD. This means that no applications are able to show your currently loaded configs, including the official plugin. The official plugin handles this by detecting a change to the local data and forcing that down to the MiniDSP. It may be worth periodically reloading any custom EQ&#39;s on all output channels and clearing all inputs.
+![Cleared slot](./img/home08.png)
diff --git a/docs/rpi.md b/docs/rpi.md
@@ -0,0 +1,182 @@
+## Overview
+
+ezbeq is a web interface that works in conjunction with minidsp-rs, which allows for simplistic selection of a movie / TV show BEQ filter and configuration of a MiniDSP 2x4HD, without having to use the proprietary minidsp plugin. The web interface is usable from phones, tablets, laptops or desktops.
+
+## Pre-Requirements
+
+ezbeq and minidsp-rs run on Linux, Windows, or Mac operating systems, but this document walks through the installation process on a Raspberry Pi. The following systems are required to follow this document:
+
+- MiniDSP 2x4HD
+- Raspberry Pi (RPi) – device should be accessible on the network, and already have Raspbian installed and updated. Raspbian Buster is used for this document.
+- USB cable connecting the Raspberry Pi and MiniDSP 2x4HD
+- Internet connection
+- Backup copy of all MiniDSP 2x4HD settings.
+
+NOTE – ezbeq and minidsp-rs will be modifying the INPUT settings of the MiniDSP 2x4HD, but please take appropriate backups.
+
+## Installation Steps
+
+### Install and verify minidsp-rs
+
+minidsp-rs is a utility, written by mrene on avsforum.com, which allows the system to communicate with the MiniDSP 2x4HD, without using the proprietary minidsp plugin. Pre-compiled binaries are available for most operating systems, and there is an available Debian package.
+
+1\. Open a shell on the RPi, or SSH to the RPi.
+
+2\. Download the latest version of minidsp-rs for Arm from [here](https://github.com/mrene/minidsp-rs/releases)
+``` 
+wget https://github.com/mrene/minidsp-rs/releases/download/v0.0.5/minidsp_0.0.5_armhf.deb
+```
+Note that the filename above is current as of 2/2/2021. Please use the current version.
+![Figure 1 – Example downloading of v0.0.5](./img/rpi01.png)
+
+3\. Install the downloaded .deb file via `sudo apt install </path/to/file>`
+```
+sudo apt install ./minidsp_0.0.5_armhf.deb
+```
+![Figure 2 – Example installation of the .deb package](./img/rpi02.png)
+
+4\. To confirm basic functionality, type `minidsp` and press Enter.
+![Figure 3 – Example of &quot;minidsp&quot; output](./img/rpi03.png)
+
+5\. If the MiniDSP 2x4HD is connected properly, similar information to Figure 3 will be displayed. Note the &quot;preset: 1&quot; in the image. That indicates that the MiniDSP 2x4HD is set to Config slot 2. The minidsp-rs application starts at 0 for the config presets, so 0 = Config slot 1, and so on.
+
+6\. If the MiniDSP 2x4HD is not detected, or is not connected, the following error will appear.
+![Figure 4 – Example of minidsp error message](./img/rpi04.png)
+
+### Install and verify ezbeq
+
+ezbeq is a web application which uses minisdsp-rs installed earlier to send the BEQ filters to an attached MiniDSP 2x4HD. The following steps walk through installing ezbeq.
+
+1\. Open a shell on the RPi, or SSH to the RPi.
+Install the pre-requisite python packages. Raspbian Buster had all but one needed package already installed. Run this command to install all of them (already installed packages will be skipped): `sudo apt install python3 python3-venv python3-pip libyaml-dev`
+![Figure 5 – Example of installing python pre-requisites](./img/rpi05.png)
+
+2\. Setup the python environment by running the follow commands:
+```
+mkdir python
+cd python
+python3 -m venv ezbeq
+cd ezbeq
+```
+![Figure 6 – Example of preparing environment](./img/rpi06.png)
+
+3\. Start the install of the ezbeq application. The required python modules will be installed. Run the following commands:
+```
+. bin/activate
+pip install ezbeq
+```  
+![Figure 7 – Example of launching the installer](./img/rpi07.png)
+
+The installer will download and install the required modules. This may take quite a while, depending on the speed of your RPi and internet connection. The information below is truncated.
+
+![Figure 8 – Example of successful installation of ezbeq](./img/rpi08.png)
+
+4\. Launch ezbeq manually, to verify functionality. Type the following:
+```
+    cd bin
+    ./ezbeq
+```
+![Figure 9 – Example of launching ezbeq](./img/rpi09.png)
+
+5\. ezbeq runs on port 8080 of the RPi by default. On another device connected to the local network, open a web browser and connect to the RPi port 8080. Note that the web server is not encrypted, so the URL must be entered as http, otherwise most current browsers will automatically try to connect using HTTPS (secured) and fail.
+Open a browser window to `http://<ip address of Rpi>:8080`
+![Figure 10 – Example of ezbeq interface](./img/rpi10.png)
+
+6\. To load a BEQ onto the MiniDSP 2x4HD, select a title (search is available in the upper right corner), then click on the &quot;up arrow&quot; on the corresponding config slot to be used.
+![Figure 11 – Example of selecting a title and uploading to config slot 2](./img/rpi11.png)
+
+7\. If the update is successful, the title will be display in the &quot;Loaded&quot; column. Otherwise, &quot;ERROR&quot; will be displayed.
+![Figure 12 – Example of successful title load](./img/rpi12.png)
+
+### Automatically launch ezbeq on boot
+
+These steps are optional but are highly recommended. If these steps are not followed, ezbeq will need to be started manually after every reboot of the RPi.
+
+1\. Open a shell on the RPi, or SSH into the RPi.
+
+2\. Create the service file, issuing the following command:
+```
+sudo nano /etc/systemd/system/ezbeq.service
+```
+![Figure 13 – Example editing the service file](./img/rpi13.png)
+
+3\. Add the information below to the file. When complete, save the file (Ctrl-O), then exit (Ctrl-X).
+NOTE – If the ezbeq software was installed using a different user than &quot;pi&quot;, ensure to modify the settings below, replacing &quot;pi&quot; with the correct userID.
+```
+[Unit]
+Description=ezbeq
+After=network.target
+    
+[Service]
+Type=simple
+User=pi
+WorkingDirectory=/home/pi
+ExecStart=/home/pi/python/ezbeq/bin/ezbeq
+Restart=always
+RestartSec=1
+
+[Install]
+WantedBy=multi-user.target
+```
+![Figure 14 – Example service file](./img/rpi14.png)
+
+4\. Register and start the service. Note that if ezbeq is still running from the earlier steps, it needs to be stopped (Ctrl-C), otherwise the service will not start.
+```
+sudo systemctl enable ezbeq.service
+sudo service ezbeq start
+```
+![Figure 15 – Register and start the ezbeq service](./img/rpi15.png)
+
+5\. Verify the service started by issuing this command:
+```
+sudo journalctl -u ezbeq.service
+```
+![Figure 16 – Log messages showing the service is running](./img/rpi16.png)
+
+6\. Reboot the RPi, and then check the website again.
+```
+sudo shutdown -r now
+```
+
+### Updating minidsp-rs
+
+Updating minidsp-rs is the same process outline in section I above.
+
+1\. Open a shell on the RPi, either locally, or via SSH.
+
+2\. Download the latest Arm .deb package from [https://github.com/mrene/minidsp-rs/releases](https://github.com/mrene/minidsp-rs/releases)
+Example: `wget https://github.com/mrene/minidsp-rs/releases/download/v0.0.5/minidsp_0.0.5_armhf.deb`
+
+3\. Install the .deb package using the following command: `sudo apt install ./<filename>`
+Example: `sudo apt install ./minidsp_0.0.5_armhf.deb`
+
+### Updating ezbeq
+
+Updating ezbeq follows a similar approach as the initial install, with an extra flag.
+
+1\. Open a shell on the RPi, either locally, or via SSH.
+
+2\. Run the following commands:
+```
+cd python
+cd ezbeq
+. bin/activate
+pip install --upgrade ezbeq
+```
+
+3\. If ezbeq is configured to run on boot (section III), restart the ezbeq service to ensure the update takes effect:
+```
+sudo service ezbeq restart
+```
+
+## Which Raspberry Pi should I buy?
+
+This question has been asked a few times. The biggest key to a successful Raspberry Pi implementation is a solid power supply.
+
+For North American users, kits from CanaKit ([https://canakit.com](https://canakit.com)) have been recommended by some users. Note that this is not an endorsement of their product, nor is there any affiliation with this company.
+
+The software has been run on Pi3 successfully, and should also run on Pi4.
+
+## A few other notes.
+
+Bear in mind that, so far, settings cannot be read back from the MiniDSP 2x4HD. This means that no applications are able to show your currently loaded configs, including the official plugin. The official plugin handles this by detecting a change to the local data and forcing that down to the MiniDSP. It may be worth periodically reloading any custom EQ&#39;s on all output channels and clearing all inputs.