v2.0.104 pull from dev.

Dev
This commit is contained in:
Robin Davies
2026-06-04 10:05:19 -04:00
committed by GitHub
47 changed files with 190 additions and 93 deletions
+2 -2
View File
@@ -1,13 +1,13 @@
cmake_minimum_required(VERSION 3.16.0)
project(pipedal
VERSION 2.0.103
VERSION 2.0.104
DESCRIPTION "PiPedal Guitar Effect Pedal For Raspberry Pi"
HOMEPAGE_URL "https://rerdavies.github.io/pipedal"
)
execute_process( COMMAND dpkg --print-architecture COMMAND tr -d '\n' OUTPUT_VARIABLE DEBIAN_ARCHITECTURE )
set (DISPLAY_VERSION "PiPedal v2.0.103-Release")
set (DISPLAY_VERSION "PiPedal v2.0.104-Release")
set (PACKAGE_ARCHITECTURE ${DEBIAN_ARCHITECTURE})
set (CMAKE_INSTALL_PREFIX "/usr/")
+2 -2
View File
@@ -9,11 +9,11 @@
<img src="https://img.shields.io/github/downloads/rerdavies/pipedal/total?color=%23808080&link=https%3A%2F%2Frerdavies.github.io%2Fpipedal%2Fdownload.html"/>
Download:&nbsp;<a href='https://rerdavies.github.io/pipedal/download.html'>v2.0.103</a>
Download:&nbsp;<a href='https://rerdavies.github.io/pipedal/download.html'>v2.0.104</a>
Website:&nbsp;[https://rerdavies.github.io/pipedal](https://rerdavies.github.io/pipedal).
Documentation:&nbsp;[https://rerdavies.github.io/pipedal/Documentation.html](https://rerdavies.github.io/pipedal/Documentation.html).
#### Announcing PiPedal 2.0 (2.0.103)&mdash;a major update to PiPedal, including exciting new features, ioncluding support for NAM A2. See the Pipedal website [documentation](https://rerdavies.github.io/pipedal/PiPedal.html) for more information.
#### Announcing PiPedal 2.0 (2.0.104)&mdash;a major update to PiPedal, including exciting new features, ioncluding support for NAM A2. See the Pipedal website [documentation](https://rerdavies.github.io/pipedal/PiPedal.html) for more information.
&nbsp;
+76 -30
View File
@@ -2,17 +2,18 @@
PipPedal consists of the following components:
* A web application built using vite/React, found in the `vite` subdirectory.
* A web application built using vite/React, found in the `vite` project directory. The web application is built using the Vite build system as static content.
* `pipedald`
A web server, written in C++, serving a web socket, and pre-built HTML components from the React app.
All audio services are provided by the pipedald process.
A web server, written in C++, serving a web socket, which serves both static content built by the
Vite build system, and dynamic content generated at runtime by the C++ code. The pipedald process also manages the audio services, and provides a web socket interface for the web application to control the audio services, and to get status information about the audio services.
* `pipedaladmind`:
A service to execute operations that require root credentials on behalf of pipedald. (e.g. shutdown, reboot,
and pushing configuration changes).
and pushing configuration changes that require root credentials -- currently, configuration files for the
Wi-Fi hotspot which contain the Wi-Fi hotspot password).
* `pipedalconfig`:
@@ -29,24 +30,24 @@ You must stop the pipedald service before launching a debug instance of pipedald
or
pipedalconfig --stop #Stops the Jack service as well.
pipedalconfig --stop
which also stops the pipedaladmind service.
Although not strictly necessary, you should probably add your login account to the pipedal_d group.
You need to add your login account to the pipedal_d group.
sudo usermod -a -G pipedal_d *youruserid*
This will allow you to run `pipedald` under the debugger of your choice using the
same /etc/pipedal and /var/pipedal directories as an instance of `pipedal` running
under systemd. Note that when running under systemd, `pipedald` runs under an unprivileged
`pipedal_d` service account, and relies it's group (also `pipedal_d`) in order to access its
data files, and to communicate with the `pipedaladmin` service, which does run with root
privileges when `pipedald` needs to perform operations that do required root privileges (e.g. shutdown/reboot and starting and stopping WiFi services).
`pipedal_d` service account, and relies on its group (also `pipedal_d`) in order to access its
data files, and to communicate with the privileged `pipedaladmin` service (which also requires membership in
the `pipedal_d` group). The `pipedaladmin` service runs under with `root` credentials in order to perform
operations that require root privileges (e.g. shutdown/reboot and updating the password for the Wi-Fi hotspot
connection).
For what it's worth, `pipedaladmin` is virtually un-debuggable, because it does require root privileges to run.
If you really _must_ debug pipedaladmin, you can fire up a sudo instance of Visual Studio Code
and attach to the running daemon process. But running program as large as VS Code with root privileges
is a dangerous process, that VS Code firmly (and rightfully) complains about. And configuring
VSCode to run with root privileges as a painful process. Avoid if you can.
`pipedaladmin` is difficult to debug. The best way to do it is to start the service, and attach to the process in which it runs using the VSCode debugger. (Watch out for the prompt for root access that VSCode excentricly sends to the terminal window).
The pipedald service will run with or without the pipedaladmind service, but some operations (shutdown, reboot,
audio and Wi-Fi configuration changes) may fail if the pipedaladmind service is not running. Pipedal communicates
@@ -55,7 +56,7 @@ added your own account to the `pipedal_d` group, debug instances of `pipedald` w
In production, the pipedald web server serves the PiPedal web socket, as well as static HTML from the built
vite/React components. But while debugging, it is much more convenient to use the Vite debug server for
React sources, and configure pipedald to serve only the websocket.
React sources, and run a debug instance of `pipedald` to serve dyanmic content, and service websocket connections.
Note that a debug instance of `pipedald` cannot bind to port 80, since that requires either root privileges or
access to port 80 via `authd`. So you will have to configure the debug instance of `pipedald`'s web server to
@@ -68,38 +69,83 @@ you are debugging. However, when using the vite/react debug server, the PiPedal
use the pipedald web server on port 8080 to provide dynamic content (e.g. the web socket connect, and various
pieces of dynamic content served out of the `http://localhost:8080/var` URL and children thereof.
See the `sample_vscode_launch.json` file in the root project directory for an example of how to configure the VSCode
debugger to launch a debug instance of `pipedald'. (Or just copy the entire file to `.vscode/launch.json`). If you are using another debugger, the invocation you will need for pipedald is:
pipedald /etc/pipedal/config /etc/pipedal/react -port 0.0.0.0:8080
which runs pipedald with the same configuration and react web app sources as the systemd instance of pipedald, but with the web server bound to port 8080 instead of port 80. Earlier debug procedures pointed the two supplied directories to locations that provided debug configurations and content. But it has subsequently proven easier just to ensure use the same configuration files and data as a systemd instance of `pipedald` would use. You will need to ensure that the systemd configuration directories have been properly provisioned with the necessary configuration files and data first. You can do that either by running `./install.sh` after a successful builde, or by installing a recent debian package for PiPedal downloaded from the Github releases page of https://githumb.com/rerdavies/pipedal .
You may find it convenient to reconfigure the systemd instance of `pipedald` to bind to port 8080 as well.
That will allow the vite/react debug server to point clients to either a debug instance or the systemd instance of `pipedald`
depending, depending on which instance of pipedald is currently running. Run the following command to
depending, on which instance of pipedald is currently running. Run the following command to
make the systemd instance of `pipedald` bind to port 8080 instead of port 80:
pipedalconfig --install --port 8080
(which will also restart the `pipedald` service).
To start the web app debug server, from a shell, `cd` to the `./vite` directory, and run `npm run dev`. The
To start the Vite debug server, from a shell, `cd` to the `./vite` directory, and run `npm run dev` (or './debug.sh' which does the same thing.
Vite debug server will automatically detect any changes to web app sources, and rebuild them automatically (no build step required). Note that the `pipedald` service must be running in order for the web app to function properly, either
as a the `pipedald` service, or by running `pipedald` in a debugger.
Actual debugging is performed using the Chrome debugger (which is remarkably well integrated with Vite/React).
Actual debugging of the web client is performed using the Chrome debugger (which is remarkably well integrated with Vite/React).
You won't actually see changes to the version of the systemd version of the static web app until you
do a full _Release_ or _RelWithDebInfo_ build of PiPedal, followed by running `./install.sh` which pushes
the built react app in the location where the systemd version of `pipedald` serves static web content.
By default, the debug React app will attempt to contact the pipedald server on ws:*:8080 -- the address on which
the debug version of pipedald listens on. This can be reconfigured
in the file `react/src/public/var/config.json` if desired. If you connect to the the pipedald server port (port 80), pipedald intercepts requests for `http://./var/config.json` and points the react app at itself, so the file has no effect when running in production.
However, you can refresh the Vite-generated content by running:
The React app will display the message "Error: Failed to connect to the server", until you start the pipedald websocket server in the VSCode debugger. However, it's quite reasonable to point the react debug app at a systemd instance of the pipedald server instead, if you don't intend to debug C++ code.
```
cd ./vite
./build.sh # Full build of the react app.
./install.sh # Copy the built react app to the directory
# from which the systemd version of pipedal serves static content.
```
react/public/var/config.json:
{
...
# (PiPedald's port number. 80 for the production service, 8080 (by default) for
# pipedal running under a debugger.
"socket_server_port": 8080,
"socket_server_address": "*",
...
By default, the debug React app served by the Vite debug server will attempt to contact the pipedald server
on ws:*:8080 -- the address on which the debug version of pipedald listens on. This can be reconfigured
in the file `vite/vite.config.ts` if desired. Locate and edit the two URLS given in this section of the file:
vite/vite.config.ts:
```
...
server: {
proxy: {
'/resources': {
target: 'http://localhost:8080',
changeOrigin: false,
},
'^/var/(?!config\\.json$).*': {
target: 'http://localhost:8080',
changeOrigin: false,
},
}
}
...
```
The Vite debug server proxies requests to `http:/localhost:5173/var/*` and `http:/localhost:5173/resources/*` to the pipedald server on port 8080. The critical request from the web client is actually `http://localhost:5173/var/config.json`, the results of which contain, among other things, the address and port number of the `pipedald` web server. Once `config.json` has been downloaded, the client has the address it needs to make subsequent requests for non-static content and web socket connections directly to the `pipedald` web server instead of the Vite debug server.
The React app will display the message "Error: Failed to connect to the server", until you start the pipedald web server server in the VSCode debugger. However, it's quite reasonable to point the react debug app at a systemd instance of the pipedald server instead, if you don't intend to debug C++ code.
vite/vite.config.ts:
```
...
server: {
proxy: {
'/resources': {
target: 'http://localhost:80',
changeOrigin: false,
},
'^/var/(?!config\\.json$).*': {
target: 'http://localhost:80',
changeOrigin: false,
},
}
}
...
```
The original development for this app was done with Visual Studio Code. And it's probably easiest to go with the flow when building
+63 -5
View File
@@ -13,18 +13,18 @@ page_icon: img/Install4.jpg
Download the most recent Debian (.deb) package for your platform:
- [Raspberry Pi OS bookworm (aarch64) v2.0.103](https://github.com/rerdavies/pipedal/releases/download/v2.0.103/pipedal_2.0.103_arm64.deb)
- [Ubuntu 24.04 through 25.04 (aarch64) v2.0.103](https://github.com/rerdavies/pipedal/releases/download/v2.0.103/pipedal_2.0.103_arm64.deb)
- [Ubuntu 24.04 through 25.04 (amd64) v2.0.103](https://github.com/rerdavies/pipedal/releases/download/v2.0.103/pipedal_2.0.103_amd64.deb)
- [Raspberry Pi OS bookworm (aarch64) v2.0.104](https://github.com/rerdavies/pipedal/releases/download/v2.0.104/pipedal_2.0.104_arm64.deb)
- [Ubuntu 24.04 through 25.04 (aarch64) v2.0.104](https://github.com/rerdavies/pipedal/releases/download/v2.0.104/pipedal_2.0.104_arm64.deb)
- [Ubuntu 24.04 through 25.04 (amd64) v2.0.104](https://github.com/rerdavies/pipedal/releases/download/v2.0.104/pipedal_2.0.104_amd64.deb)
Version 2.0.103 has been tested on Raspberry Pi OS bookworm, Ubuntu 24.04 (amd64), Ubuntu 24.10 (aarch64), and Ubuntu 25.04 (aarch64). Download the appropriate package for your platform, and install using the following procedure:
Version 2.0.104 has been tested on Raspberry Pi OS bookworm, Ubuntu 24.04 (amd64), Ubuntu 24.10 (aarch64), and Ubuntu 25.04 (aarch64). Download the appropriate package for your platform, and install using the following procedure:
```
sudo apt update
sudo apt upgrade
cd ~/Downloads
sudo apt-get install ./pipedal_2.0.103_arm64.deb
sudo apt-get install ./pipedal_2.0.104_arm64.deb
```
You MUST use `apt-get`. `apt` will not install downloaded packages; and `dpkg -i` will not install dependencies.
@@ -37,6 +37,64 @@ If you are using Raspberry Pi OS, proceed directly to [Configuring PiPedal after
you are using Ubuntu, there are additional post-installation steps you must take to reconfigure the Ubuntu kernel
to provide support for low-latency real-time audio.
### Installing PiPedal on a Server that Does not have a Graphical Desktop Environment
The easiest way to do this is to download the appropriate Debian package for your platform to your desktop computer, and then copy the downloaded package to the server using `scp` or a similar file transfer method. Windows 10 and 11 provide a pre-installed `scp` command that you can use from the Command Prompt or PowerShell. On Linux desktops you may need to install `scp` using:
```
sudo apt install openssh-client
```
You must first ensure that you have SSH access to the server. Raspberry Pi OS and Ubuntu both provide a way to ensure that SSH is installed and running at first boot. First, ensure that you have SSH access to the server. If you have not yet set up your Raspberry Pi, the Raspberry Pi Imager application, and the Raspberry Pi Network Install utility allow you to pre-install and enable SSH on first boot.
See [the Raspberry Pi official documentation](https://www.raspberrypi.com/documentation/computers/getting-started.html#install) for detailed information on how to enable SSH on first boot. Navigate to the Customisation section of the Raspberry Pi Imager, and configure a default username and password. Then select the "Remote Access" subsection of the Customization section, and enable SSH. You can do this from either the Raspberry Pi Imager application, or when configuring your Raspberry Pi OS using the Network Boot installer. You can also enable SSH by creating an empty file named `ssh` in the root of the boot partition of the SD card after you have flashed the OS image to the SD card, as long as you have not yet booted using the SD card.
On Ubuntu, you will typically have had to attach a keyboard and monitor to complete the initial installation anyway. Consult Ubuntu documentation for how to enable SSH access to your Ubuntu server.
Once you have SSH access to your PiPedal server, you should download the appropriate Debian package for your platform to your desktop machine. You can then copy the downloaded package to the server using `scp` or a similar file transfer method. Note that Windows 10 and 11 provide a pre-installed `scp` command that you can use from the Command Prompt or PowerShell. On Linux desktops you may need to install `scp` using:
```
sudo apt install openssh-client
```
Use the following command to copy the downloaded package to the server from Linux or Windows. Windows 10 and 11 have `scp` installed by default.
Adjust `username`, `server_address` and the actual name of the Debian package you downloaded as needed:
```
scp Downloads/pipedal_2.0.104_arm64.deb username@server_address:/home/username/
```
This will copy the downloaded package on your desktop computer to your home directory on the PiPedal server computer.
Once you have copied the package to the server, you can SSH into the server and install the package using `apt-get`:
```
ssh username@server_address
sudo apt-get install ./pipedal_2.0.104_arm64.deb
```
The PiPedal package installer will print out the port number that the PiPedal web server is listening on. It defaults to port 80, but if you have another web server already running on port 80, it will select the next available port. Ubuntu default installs have Apache Server running on port 80, so the PiPedal web server will default to port 81 on Ubuntu.
### Acessing the PiPedal Web Application after Installation
The PiPedal server has now been installed, and should be up and running. You can access the PiPedal web application by navigating to `http://server_address:port_number` in a web browser on your desktop computer.
If you are using Ubuntu, see the [next section of the documentation](Ubuntu.md) for steps that you must take to before using the PiPedal Web Application.
Windows, Linux, and MacOS all support MDNS network naming. You can connect to your PiPedal server on Raspberry Pi OS by navigating to
http://raspberrypi.local
(raspberrypi.local is the default hostname for a Raspberry Pi OS installation; adjust the hostname as appropriate, if you changed the hostname at pre-configuration time).
On Ubuntu, you will have had to select a custom hostname during installation. You can connect to your PiPedal server on Ubuntu by navigating to
http://yourservername.local:81
--------
[<< System Requirements](SystemRequirements.md) | [Up](Documentation.md) | [PiPedal on Ubuntu >>](Ubuntu.md)
+1 -1
View File
@@ -11,7 +11,7 @@
<a href="https://rerdavies.github.io/pipedal/download2"><img src="https://img.shields.io/badge/Download-008060" /></a>
<a href="https://rerdavies.github.io/pipedal/Documentation"><img src="https://img.shields.io/badge/Documentation-0060d0"/></a>
_To download PiPedal v2.0.103-alpha, click [*here*](download.md).
_To download PiPedal v2.0.104-alpha, click [*here*](download.md).
To view PiPedal documentation, click [*here*](Documentation.md)._
Use your Raspberry Pi as a guitar effects pedal. Configure and control PiPedal with your phone or tablet.
+7 -1
View File
@@ -1,6 +1,12 @@
# Release Notes
## PiPedal 2.0.103
## PiPedal 2.0.104-Release
Bug fix:
- Revert a breaking change to TooB Cab IR that changes the output levels of existing presets that use TooB Cab IR. (The volume of output from TooB Cab IR was dramatically louder than it should have been in version 2.0.103).
## PiPedal 2.0.103-Release
PiPedal 2.0 is a big release, with exciting new features, improvements, and bug fixes.
+5 -5
View File
@@ -1,13 +1,13 @@
## Download
# Download PiPedal 2.0.103-alpha
# Download PiPedal 2.0.104-alpha
Download the most recent Debian (.deb) package for your platform:
- [Raspberry Pi OS bookworm (aarch64) v2.0.103 Alpha](https://github.com/rerdavies/pipedal/releases/download/v2.0.103/pipedal_2.0.103_arm64.deb)
- [Ubuntu 24.x, 25.04 (aarch64) v2.0.103 Alpha](https://github.com/rerdavies/pipedal/releases/download/v2.0.103/pipedal_2.0.103_arm64.deb)
- [Ubuntu 24.x, 25.04 (amd64/x86_64) v2.0.103 Alpha](https://github.com/rerdavies/pipedal/releases/download/v2.0.103/pipedal_2.0.103_amd64.deb)
- [Raspberry Pi OS bookworm (aarch64) v2.0.104 Alpha](https://github.com/rerdavies/pipedal/releases/download/v2.0.104/pipedal_2.0.104_arm64.deb)
- [Ubuntu 24.x, 25.04 (aarch64) v2.0.104 Alpha](https://github.com/rerdavies/pipedal/releases/download/v2.0.104/pipedal_2.0.104_arm64.deb)
- [Ubuntu 24.x, 25.04 (amd64/x86_64) v2.0.104 Alpha](https://github.com/rerdavies/pipedal/releases/download/v2.0.104/pipedal_2.0.104_amd64.deb)
Install the package by running
@@ -15,7 +15,7 @@ Install the package by running
```
sudo apt update
cd ~/Downloads
sudo apt install ./pipedal_2.0.103_arm64.deb
sudo apt install ./pipedal_2.0.104_arm64.deb
# or ... _amd64.deb as appropriate for your platform
```
The message about missing permissions given by `apt` is
+1 -1
View File
@@ -93,7 +93,7 @@ cabir:impulseFile3
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
TooB Cab IR is a convolution-based guitar cabinet impulse response simulator.
+1 -1
View File
@@ -50,7 +50,7 @@ toob:frequencyResponseVector
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
mod:brand "TooB";
mod:label "Cab Simulator";
@@ -53,7 +53,7 @@ toobimpulse:impulseFile
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
Toob Convolution Reverb Stereo uses convolution reverb impulse/response files in order to produce highly
@@ -51,7 +51,7 @@ toobimpulse:impulseFile
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
+1 -1
View File
@@ -66,7 +66,7 @@ inputStage:filterGroup
doap:license <https://two-play.com/TooB/licenses/isc> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
mod:brand "TooB";
mod:label "Input";
+1 -1
View File
@@ -68,7 +68,7 @@ pstage:stage3
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
mod:brand "TooB";
mod:label "Power Stage";
+1 -1
View File
@@ -57,7 +57,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment "TooB spectrum analyzer" ;
mod:brand "TooB";
+1 -1
View File
@@ -57,7 +57,7 @@ tonestack:eqGroup
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
uiext:ui <http://two-play.com/plugins/toob-tone-stack-ui>;
+1 -1
View File
@@ -52,7 +52,7 @@ toob:frequencyResponseVector
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
uiext:ui <http://two-play.com/plugins/toob-three-band-eq-ui>;
@@ -52,7 +52,7 @@ toob:frequencyResponseVector
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
uiext:ui <http://two-play.com/plugins/toob-three-band-eq-stereo-ui>;
Binary file not shown.
+1 -1
View File
@@ -40,7 +40,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
Emulation of a Boss CE-2 Chorus.
+1 -1
View File
@@ -41,7 +41,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
A straightforward no-frills digital delay.
+1 -1
View File
@@ -41,7 +41,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
Emulation of a Boss BF-2 Flanger, based on circuit analysis and simulation of the original.
@@ -41,7 +41,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
Digital emulation of a Boss BF-2 Flanger.
+1 -1
View File
@@ -41,7 +41,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
Toob Freeverb is an Lv2 implementation of the famous Freeverb reverb effect. FreeVerb delivers a well-balanced reverb with very little tonal coloration.
+1 -1
View File
@@ -41,7 +41,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
A 7 octave graphic equalizer, with frequencies chosen to be useful for EQ-ing guitar signals.
""" ;
+1 -1
View File
@@ -92,7 +92,7 @@ myprefix:output_group
doap:license <https://opensource.org/license/mit/> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 3 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
ui:ui <http://two-play.com/plugins/toob-looper-four-ui>;
+1 -1
View File
@@ -78,7 +78,7 @@ myprefix:output_group
doap:license <https://opensource.org/license/mit/> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 3 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
ui:ui <http://two-play.com/plugins/toob-looper-one-ui>;
+1 -1
View File
@@ -67,7 +67,7 @@ toobml:sagGroup
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
The TooB ML Amplifier plugin provides emulation of a variety of amplifiers and overdrive pedals that are implemented
using neural-network-based machine learning models of real amplifiers.
+1 -1
View File
@@ -40,7 +40,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
Remix a stereo input signal.
@@ -74,7 +74,7 @@ toobNam:calibrationGroup
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
TooB Neural Amp Modeler is a neural network based Amp Simulator. It uses .nam model files that are generated by training nueral networks
on audio recordings of actual guitar amps, effects pedals and other equipment. .nam files contain data from the trained models, which can be loaded into
+1 -1
View File
@@ -54,7 +54,7 @@ noisegate:envelope_group
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
A noise gate is an audio processing tool that controls the volume of an audio signal
by allowing it to pass through only when it exceeds a set threshold.
+1 -1
View File
@@ -87,7 +87,7 @@ parametric_eq:hfGroup
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
uiext:ui <http://two-play.com/plugins/toob-parametric-eq-ui>;
@@ -87,7 +87,7 @@ toob-parametric-eq-stereo:hfGroup
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
uiext:ui <http://two-play.com/plugins/toob-parametric-eq-stereo-ui>;
+1 -1
View File
@@ -40,7 +40,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
A loose emulation of an MXR® Phase 90 Phaser.
+1 -1
View File
@@ -60,7 +60,7 @@ toobPlayer:seek
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
Play audio files. Audio files can optionally be loooped by pressing the "Set loop" button.
+1 -1
View File
@@ -51,7 +51,7 @@ recordPrefix:audioFile
doap:license <https://opensource.org/license/mit/> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 3 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
ui:ui <http://two-play.com/plugins/toob-record-mono-ui>;
+1 -1
View File
@@ -88,7 +88,7 @@ myprefix:loop3_group
doap:license <https://opensource.org/license/mit/> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 3 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
ui:ui <http://two-play.com/plugins/toob-record-stereo-ui>;
+1 -1
View File
@@ -43,7 +43,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
TooB Tone is a simple tone control. For more flexible EQ plugins, see TooB 3 Band Eq, or TooB Parameteric EQ.
+1 -1
View File
@@ -43,7 +43,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
TooB Tone is a simple tone control. For more flexible EQ plugins, see TooB 3 Band Eq, or TooB Parameteric EQ.
+1 -1
View File
@@ -41,7 +41,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
A tremolo effect, equivalent to "vibrato" on vintage Fender tube amps.
+1 -1
View File
@@ -41,7 +41,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
A tremolo effect, equivalent to "vibrato" on vintage Fender tube amps.
+1 -1
View File
@@ -44,7 +44,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
TooB Tuner is a chromatic guitar tuner.
""" ;
+1 -1
View File
@@ -39,7 +39,7 @@
doap:license <https://rerdavies.github.io/pipedal/LicenseToobAmp> ;
doap:maintainer <http://two-play.com/rerdavies#me> ;
lv2:minorVersion 0 ;
lv2:microVersion 79 ;
lv2:microVersion 80 ;
rdfs:comment """
Volume control.
Binary file not shown.
Binary file not shown.
-1
View File
@@ -26,7 +26,6 @@ add_custom_command(
public/css/roboto.css
public/html/t3k_response.html
public/var/current_pedalboard.json
public/var/config.json
public/var/uiplugins.json
public/var/plugin_classes.json
public/testTone300Popup.html
-12
View File
@@ -1,12 +0,0 @@
{
"socket_server_port": 8080,
"socket_server_address": "*",
"debug": true,
"max_upload_size": 536870912,
"fakeAndroid": false,
"ui_plugins": [],
"enable_auto_update": true,
"has_wifi_device": false,
"tone3000_A2_models": true,
"end": true
}