shawn/op-pedal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixes to Changes.

Browse Source 
Added helper functions to combine and intersect ALSA device capabilities, ensuring validation works across separate input and output devices

Updated buffer handling logic to use both selected devices and compute min/max sizes appropriately

Revised validation to check both ALSA input and output devices when enabling the OK button

Simplified rendering logic to intersect sample rates and buffer options for the chosen devices

AlsaDriver single device err calls fixed.

Added guidance on using USB audio interfaces or Raspberry Pi audio HATs and choosing separate ALSA input and output devices during setup

Clarified that the Audio Device Settings dialog allows independent configuration of input and output devices, with updated instructions for selecting audio channels
This commit is contained in:
ExtremesecrecyOne
2025-07-22 17:51:33 -07:00
parent 54926871fc
commit 1ca0973833
3 changed files with 107 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/Configuring.md
+4
View File
@@ -8,6 +8,10 @@ icon_float: left
Before using PiPedal, you will need to configure settings for the audio device that PiPedal will use.
PiPedal works with either external USB audio interfaces or Raspberry Pi audio HATs. You can now
select a distinct ALSA input device and output device, so recording and playback can use different
hardware if desired.
{% include pageIconL.html %}
You will also want to configure PiPedal to provide a Wi-Fi auto-hotspot so that you can connect to using your using your Android phone or tablet. It's fine to use your home Wi-Fi network to connect to PiPedal when you're at home; but don't forget that when you take PiPedal out to a gig, you will need to ensure that PiPedal's Wi-Fi auto-hotspot is enabled before you do.