Documentation

bpplay user manual: Raspberry Pi

The full end-user edition of the manual, kept up to date here on the page.

↓ Download the image (EN) ↓ Download the image (HU) ↓ README (EN) bpplay x64 kiosk edition → bpplay x64 desktop edition → bpplay for macOS →
SHA-256 checksums of the RC22 images (.img.gz files):
RC_bpplay-pi5-kiosk-v2.2.0-rc22-TRIAL-EN-4c23b0e.img.gz
05f4213e657056b8163539e670ce20070d51af3d334ccb71491ec58145159772
RC_bpplay-pi5-kiosk-v2.2.0-rc22-TRIAL-HU-4c23b0e.img.gz
da5a1a58af08a4379430522076481bec065a15048dbd5300064a9efa6442c56a
§ About 1 Introduction 2 Requirements 3 Using the device 4 Hardware 5 Technical background 6 What's new § Disclaimer
Hardware

Tested where it matters: the connection

The appliance is validated exclusively on Raspberry Pi 4 (CM4 module in the case of Holo Red) and Pi 5, with at least 4 GB RAM. Earlier Pi models, and 2 GB boards, are not tested, not guaranteed.

Board Raspberry Pi 4 / 5 OS Raspberry Pi OS 64-bit (arm64), Debian 13 "trixie" Boot microSD card Kernel PREEMPT_RT (factory-installed) DAC ALSA-compatible USB DAC, or built-in output Network Ethernet / Wi-Fi; required for the selector

§About this edition

This end-user edition is derived from the full v2.2 manual of the bpplay/bptune appliance edition: a condensed version that describes only what you need to know for everyday use of the device. The installation, developer and administrator chapters are deliberately omitted.

The device boots straight into the music selector, with no login; you simply connect to it over SSH (see 3.1.1). You never see a command line, terminal or login prompt during use; a few keys are enough for navigation: arrow keys, Enter, Space, Esc.

1Introduction

1.1 What is bpplay?

bpplay is a command-line, bit-perfect audio file player application for Linux and macOS. It has no graphical interface, no volume control, no equalizer, deliberately. Its goal is one single thing: to deliver the contents of the music file unchanged, via the shortest possible path with the fewest conversion steps, to the DAC (digital-to-analog converter).

Whenever possible, the program plays in so-called "integer mode", which means the integers stored in the file (integer samples) reach the sound card without a single bit shift or conversion. When this is not possible (for example the source is in float format, or the DAC does not support the exact bit depth of the source), the program always states this clearly; it never stays silent about being forced into a compromise.

In the appliance edition the end user never launches this program directly; instead, the zenevalaszto.py Python script invokes it in the background for the selected track(s) (see Chapter 3).

Supported file formats: WAV, FLAC, ALAC (M4A), AIFF/AIFC, DSD (DSF/DFF, natively and via DoP), and SACD ISO (the disc's stereo layer, DST-compressed or uncompressed; see 3.4).

1.2 No tricky or hidden conversions behind the scenes

This is the most important design principle of bpplay. If, for any reason, the program cannot achieve exactly the sample rate, bit depth or format the file requires, it:

  • clearly states on screen what happened;
  • never silently conceals a format deviation;
  • if a DAC does not return exactly the requested sample rate, the program retries rather than quietly accepting a wrong rate.
1.3 Native DSD and DoP

DSD (Direct Stream Digital) is a high-resolution audio format used by SACDs and some downloadable/streamed releases. Many players repackage DSD data into PCM frames (DoP, DSD over PCM) before sending it to the DAC. bpplay can send DSD data directly, without repackaging, if the DAC supports it; this is called native DSD playback.

Important, Pi-specific limitation.
Native DSD and DoP support depends entirely on the chip of the connected DAC/USB interface and on the design of the DAC, not on the Raspberry Pi. Tested hardware gave different results; before planning DSD playback with a given device, see the hardware table in Chapter 4.
1.4 What is bptune?

bptune is a standalone system-tuning tool that optimizes Linux kernel and hardware settings for low-latency, glitch-free audio playback, and also handles background services that would interfere with playback.

In the appliance edition, the factory installer has already configured bptune; as an end user, there is nothing for you to do with it.

1.5 Important: trial period

This device is issued as a trial unit: it can be used for 15 days from the first time you actually power it on, not from whenever the SD card was written. The trial period is a flat 15 days with no extension.

The music selector shows Trial: N days left on the information line below its header.

After the trial period expires, the device shuts down automatically and completely at power-on; the music selector never appears, only a brief message explains the reason for the shutdown. This restriction cannot be bypassed by setting the system clock back.

Important.
This SD card is device-locked: on its first real boot, the software records the hardware serial number of the specific Raspberry Pi it is running in, and from then on it will only start on that exact device. Moving the card into a different Pi will make it refuse to boot at all. This is not a bug; it is a deliberate protection mechanism.

2System requirements

This manual assumes a Raspberry Pi 4 or Pi 5 running Raspberry Pi OS (64-bit, Debian-based). Operation as described is not guaranteed on earlier Pi models.

  • Raspberry Pi 4 or 5, with at least 4 GB RAM (the OS itself now boots into memory too, not just the music); more RAM allows a larger playlist to be loaded. The zenevalaszto.py also shows the estimated memory requirement of the selected list at startup, which can serve as a guide.
  • Raspberry Pi OS 64-bit (arm64), based on Debian 13 (trixie).
  • Boot medium: microSD card (used by this appliance edition).
  • PREEMPT_RT kernel (installed automatically by the factory installer).
  • ALSA-compatible USB DAC (see Chapter 4 for tested hardware), or the Pi's built-in audio output if no external DAC is connected. Connect the DAC directly to the Pi, not through a USB hub; a hub can make the connection unreliable.
  • Network connection (Ethernet or Wi-Fi); required, since the music selector is reached over an SSH connection to the device (see 3.1.1); without it, the end user cannot select and play music.
2.1 Writing the microSD card (installing the image)

The downloaded .img.gz file is a complete disk image, not an ordinary file to copy onto the card. If you simply copy it, the Pi will not boot. The image must be written to the card with a dedicated tool; this erases everything on the card.

You need: a microSD card of at least 8 GB, good quality (Class 10 / A1 or better), and a card reader; Balena Etcher (free, identical on Mac and Windows: etcher.balena.io); the downloaded .img.gz file (no need to unpack it).

  • Open Balena Etcher, choose "Flash from file", then the downloaded .img.gz.
  • "Select target": choose the microSD card. Double-check its name and size; the selected drive is erased completely.
  • Click "Flash!". Etcher writes and verifies the card (a few minutes). If it reports an error, repeat it or try another card/reader.
  • After "Flash Complete!", remove the card and put it into the Pi. If the computer offers to format it, do not format it.

Check: after a successful write the card shows a small volume called bootfs containing config.txt and cmdline.txt. If the card looks empty, or contains only an .img.gz file, the image was not written: repeat the procedure.

Alternative: Raspberry Pi Imager can be used as well ("Choose OS" → "Use custom"). If it offers "OS customization" settings, choose No: the device is preconfigured.

3Using the device

No technical knowledge is required for use; which is exactly why the appliance (kiosk) mode does not offer administrator privileges.

3.1 Powering on

Connect the Raspberry Pi to its power supply (and if you have a separate DAC, connect it to the Pi's USB port as well). It is recommended to connect the DAC via USB 2.0 rather than USB 3.0; these are usually the two outermost connectors on the back panel. Switch the DAC on first, then the RPi. The device starts by itself.

No monitor or keyboard is needed for use: the music selector does not appear on a screen attached to the device; it is reached over an SSH connection from your own tablet, phone or computer. If a monitor happens to be connected to the Pi, its screen goes dark shortly after boot and stays off for the rest of the session; this is deliberate, not a fault, it is not stuck or frozen, it is simply switched off.

After powering on, wait about half to one minute, then establish the SSH connection to the device (see 3.1.1) and enter the password if prompted; the music selector screen then appears, with no further commands to type.

If instead you see a brief message that the device can no longer be used, followed by the machine switching itself off: the trial period has expired (see 1.5). Contact the person you received the device from.

What survives a reboot: your favorites, saved playlists and a few settings are saved automatically to the device's own storage and survive a reboot. Not kept: the currently selected (but not yet played) tracks, and the last folder you had open.

3.1.1 Connecting via SSH

No technical knowledge is needed for this either; just a simple connection with an app, the same way as with any other app. You get the device's IP address or network name from the person you received the device from. Kiosk machines are typically reachable at kiosk@bpplay-kiosk-en-XXXX.local (hu instead of en for the Hungarian image, XXXX the last four hex digits of the MAC address) or kiosk@IP-address. The usual password, should it be needed: bitperfectsound. Both the user name and the password use only characters that sit in the same place, without Shift, on the common keyboard layouts (QWERTY, QWERTZ, AZERTY), so the login works even if your computer's layout differs from what you're used to.

macOS terminal (Fig. 1)
koscso1@Koscso-MacBook-Air-3 ~ % ssh kiosk@bpplay-kiosk-hu-a1b2.local

Figure 1: Connecting via SSH from a macOS terminal.

Important.
The network connection (Wi-Fi or Ethernet) must stay up for the entire listening session; the SSH connection keeps the music selector screen alive through it. If the network drops, the connection drops too, and you need to reconnect.
macOS / Linux: built-in terminal + ssh command.
Windows: on Windows 10/11, the built-in OpenSSH client from PowerShell or Windows Terminal, or PuTTY.
Android: Termux (full terminal emulation), JuiceSSH or ConnectBot.
iOS / iPadOS: Termius or Blink Shell.
3.1.2 If the device can't be found

Out of the box the device connects to your network over wired Ethernet; no Wi-Fi network is set up on the image. If no Ethernet cable is connected, the device will not get an IP address and no finder tool will locate it. If kiosk@bpplay-kiosk-<lang>-XXXX.local is not reachable, check the following, in order:

  1. Confirm an Ethernet cable is actually connected between the device and your router or switch.
  2. Give it enough time; especially after a fresh SD card write, first boot can take one to two minutes.
  3. Check your router's own admin page for connected devices, rather than relying only on a separate scanner tool; this does not depend on mDNS (.local resolution), which can be blocked on some routers or VLANs.
  4. Confirm you are on the same network; a laptop on Wi-Fi on a guest network may not see a Pi that is wired to the main network, even though both are working.
  5. Watch the SD card activity LED at power-on; a green blink followed by a solid red light around the 30 second mark is a known, documented failure with a known fix.
  6. Try re-writing the SD card; a partial or corrupted write can cause exactly this symptom.
  7. As a last resort, connect a monitor and keyboard directly to the Pi and read the boot console; that immediately shows whether the device is even reaching network initialization.
3.2 Selecting storage

If you have just connected a USB drive (flash drive, external HDD/SSD) with music to the device, you can reopen the storage selector on the screen at any time with the m key:

  • The selector lists the available drives that contain (or may contain) music; both those already mounted and those plugged in but not yet mounted.
  • Navigate with the Up/Down arrows, select with Enter.
  • If you choose a drive that is not yet mounted, the system mounts it automatically; no password is needed for this.
  • Some music-selector versions also offer a "Mount network share (NFS/SMB)..." line in the storage selector. With it you can reach a shared music folder on another machine (for example your NAS) by entering its address (for example 192.168.1.10:/zene for NFS, //192.168.1.10/zene for SMB). The music selector automatically recognizes the type from the form of the address. The share itself must be set up in advance on the NAS or the other machine; that is not the job of bpplay/the music selector, which only mounts an already existing, reachable share. Network shares are mounted read-only, as a guest: no user name or password is asked. A share that requires a password is not supported; enable guest (anonymous) read access for the music folder on the NAS. SMB shares are connected with SMB version 3.0, so a NAS that offers only SMB 1 or 2 cannot be mounted. Enter the share as //server/share.
  • Accessing network storage is naturally slower than local storage and strongly depends on the state of the network. The first indexing takes about 5 to 6 minutes per terabyte, depending on the speed of the drive.
  • If only a single storage location is available, the screen automatically skips this step.
3.3 Selecting the audio output

If several audio outputs are connected to the device (for example the Pi's built-in output AND an external USB DAC at the same time), it offers a choice at startup: Up/Down arrows, Enter. If there is only one output, it automatically skips this step too.

The selector's cursor cannot land automatically on a built-in (onboard/HDA-type) sound card if an identifiable external DAC is also present in the list; so you cannot pick the wrong output even by accident.

3.4 Browsing and playback
  • If your music is organized into folders (albums), you first see an album list: Enter opens the track list of a given album, Esc takes you back.
  • If there is no folder organization (all files are in one place), the track list appears immediately.
  • Tracks are selected with the Space key. The selection of any track can be removed with the n key.
  • The memory usage counter at the bottom of the window tracks how much of the memory your selection fills. At 70% usage the counter turns red, warning of the risk of overfilling. If you still overfill the memory with your selection, playback will not start.
  • When you have finished selecting, pressing p starts playback of the playlist, loading the tracks into memory one by one. Playback starts after the loading completes.
  • Loading speed depends on the storage devices and, in the case of a NAS, on the transfer capability of the network. From an SSD, even 96 kHz/24-bit FLAC tracks load instantly, without any waiting.

If the assembled playlist contains files with different sample rates, bpplay groups the tracks with identical sample rates into one playlist for the sake of gapless playback. When the next part of the original playlist, with a different sample rate, starts playing, a short pause of one or two seconds will be audible. This is not an error; the switchover simply takes this long. To avoid clicks, the bpplay software mutes the output for a few tenths of a second.

SACD ISO playback: opening a folder that contains an SACD disc image (.iso) is recognized automatically; the disc's stereo layer tracks appear as ordinary entries in the track list, selectable and playable the same way as any other track. Only the stereo layer is supported (DST-compressed or uncompressed); an uncompressed multichannel area cannot be played, and the music selector shows a clear message about this.

During playback a second status line also appears, showing the track's album, artist and title, derived from the folder and file name where this can be recognized.

3.5 All keys needed for operation
KeyFunction
↑/↓Navigation
EnterEnter a subfolder; on a track row it deliberately does NOTHING (so it cannot accidentally undo a selection made with Space)
EscBack to the previous (parent) menu item/folder
SpaceSelect a track (in track view), or select all tracks of an entire album at once (in album view)
aSelect all (under the currently open folder, recursively)
nClear selection
rToggle repeat mode; when on, the playlist automatically restarts from the beginning after it finishes
sSave the current selection as a playlist (asks for a name)
lLoad a previously saved playlist
oManually re-select the audio output (DAC) during playback; complements (does not replace) the automatic re-check before each playback
/Search all drives at once (global search; every word must appear in the name)
mSwitch drive/storage (x there: exclude a mounted drive from, or include it in, search and indexing)
cCPU isolation mode (A, B0, C0)
uFull Pure on or off
gMachine survey and DAC diagnostics (report)
iImport a playlist (.m3u, .m3u8)
pStart playback in the selected order
qQuit without playing (the screen then restarts automatically, it does not stay "out"); in kiosk mode, at the top level it shuts the device down completely instead

During playback: the table above applies to the browsing/selection screen. Once playback starts, different keys take over, note that Space and n mean something different here than while browsing.

KeyFunction
nNext track
bPrevious track
SpacePause / resume
f (or *)Add the currently playing track to the Favorites playlist; reachable again later via l (load a saved playlist) on the browsing screen, under the name "Favorites"
qStop playback, return to browsing
3.6 If something doesn't work
  • No sound: check that you selected the right audio output (3.3) and that the DAC is switched on and connected.
  • You can't see your music: open the storage selector (m, 3.2) and choose the correct drive.
  • The device does not start, only shows a message, then switches off: the trial period has expired (1.5); contact the developer.
  • The monitor shows only the Raspberry Pi logo and boot text (for example Failed to open device: 'sdcard'): the card holds no bootable system. The image was not written or the card is faulty; write it again as in 2.1, or try another card.
  • If the volume seems unusually quiet: bpplay is intentionally designed to never touch any volume control; playback is always bit-perfect, meaning the source file reaches the sound card without modification. If the DAC (or sound card) has its own firmware-level volume control, and that was previously set to a low level by a different playback program, that setting will persist under bpplay too; the player neither can nor will override it. This is not a bug, but a necessary consequence of bit-perfect operation.
    • Check your operating system's audio mixer / ALSA controls (on Linux, for example alsamixer or amixer), and set the DAC's own volume control to maximum (0 dB).
    • If the DAC (or its USB interface) has multiple, independent volume controls, which occurs on some unusual, multi-channel USB interfaces, make sure all of them are set to maximum. If you are unsure, contact whoever gave you the system.

    This phenomenon is not a random quirk of any particular chip vendor, but a design choice. Reference-grade devices intended purely as an audiophile digital-to-analog bridge (XMOS, Amanero) typically deliberately omit any software volume control, while general-purpose USB audio bridge chips aimed at playback and recording, or at the consumer sound card/headset market, often do include one by default.

  • Known general-purpose chip families worth checking in advance (not empirically tested by us; the risk is inferred from the general design pattern, not confirmed case by case):
    • C-Media CM6631A / CM6632A
    • Savitech SA9018 / SA9023 / SA9027 / SA9227 / SA9228
    • Texas Instruments/Burr-Brown PCM2704 / PCM2706 / PCM2707
    • Tenor TE7022 / TE8802
    • Any consumer-oriented "USB sound card/headset" style chip in the C-Media CM106/108/119 family

    Rule of thumb: the more a DAC/interface resembles a general-purpose USB sound card (playback plus microphone, headset compatibility), the more likely it is to have a software-adjustable volume control; the more it resembles a purely audiophile, playback-only bridge, the less likely.

  • If the device cannot be found on the network: before anything else, out of the box the target device connects to your network over wired Ethernet; no Wi-Fi network is set up on the image. See 3.1.2 above for the full diagnostic sequence.
  • Anything else unusual: there is nothing for you to do; the machine can be maintained remotely; just let the developer know. You can also ask the experimental bpplay chat assistant, which is based on more than 100 bpplay/bptune documents and links (a Google sign-in is required): open the chat.
3.7 Full Pure

Full Pure is an optional mode of the kiosk editions (x86_64 kiosk and Raspberry Pi). With it switched on, bpplay first loads the whole selection into RAM (for a playlist with mixed sample rates, the whole segment), then switches the network interface off at link level, and only then starts playing. The SSH and NetworkManager services keep running, but the link itself is down, so the machine is cut off from the network while the music plays. In our hardware checks the link LED goes dark on the x86_64 kiosk, and on the Raspberry Pi the Ethernet RJ45 LEDs go dark.

When does the network come back? The network comes back when playback ends; the connection is usually available again within about a minute on the Raspberry Pi. A safety timer, set to the playback length plus 60 seconds, is only a backup in case bpplay is killed, so that the machine does not stay cut off.

Limits:

  • While Full Pure is active there is no remote control: the SSH session is cut when playback starts, and the machine can be reached again when the network returns.
  • Playback cannot be stopped by anything while Full Pure is active: the SSH session is cut and the local keyboard does not work during playback. The list plays to the end, and the safety timer, set to the list length plus 60 seconds, returns the network.
  • Full Pure cannot be combined with repeat mode: with repeat on, Full Pure cannot be switched on, and the other way round.
  • Network drives (NAS) are not indexed for search while Full Pure is on.
  • On a playlist that needs a change of sample rate or format, the network can come back briefly between the segments, because each segment is played by its own bpplay run.
  • Full Pure is switched on and off with the u key in the music selector. It is off by default, and the setting is remembered.
  • It is not available on the x86_64 desktop edition.
3.8 CPU isolation mode (selectable)

Isolation of the playback core is the same in every mode. The mode, set with the c key in the music selector, decides which other cores stay awake at all times (a power-management latency of 0 µs):

  • A: All cores stay awake. Highest power draw and heat, for well-cooled machines only.
  • B0: Only the playback core stays awake; the others may enter power-saving states. This is the default.
  • C0: The playback core and core 0, which handles interrupts, stay awake; the others may enter power-saving states.

A change takes effect when the next playback starts, and does not affect playback already running. On a machine with only two active cores, C0 and A are equivalent.

3.9 Music library and search

Drive selector. The m key opens the drive selector. It lists mounted drives, drives that are plugged in but not yet mounted, and network shares (NFS or SMB, mounted read-only); the five most recent shares are remembered. Local drives are mounted read-only. Choosing a drive that is already mounted asks The drive is already mounted. Check for changes? (y/N); answering y re-indexes it.

Global search. The / key searches all drives at once. Every word you type must appear in the name, regardless of accents and capitals. Enter opens the folder of the result, with the cursor on the file.

Index. The search index is stored and restored, so search is ready soon after start. Hidden files and macOS ._ files are left out. While a drive is being indexed, playback waits for the first pass to finish, and the status line shows the progress.

Excluding a drive. In the drive selector, the x key excludes a mounted drive from search and indexing: it is marked (excluded from search), stays in the selector, and can still be browsed and played. The same key switches it back.

3.10 Machine survey and DAC diagnostics

Press g in the browser for the machine survey and optimization report: machine and kernel, motherboard and BIOS, the isolated core and the CPU isolation mode, power management and scheduling, memory, the quiet profile and, where present, the Intel management engine. It is followed by DAC diagnostics: the formats the DAC advertises, the format actually used during playback, and the mixer and mute state. A short summary is shown at the first start.

3.11 Known limitations
  • After mounting a new drive, wait about a minute before starting playback, so the first indexing pass can finish.
  • When loading DSD (DSF) files, the player briefly uses extra memory roughly equal to the size of the largest track. A list that nearly fills the loading limit may therefore, in rare cases, stop with an out-of-memory error on a machine with little memory. If this happens, select fewer tracks.

4Hardware

4.1 Board/computer

Validated exclusively on Raspberry Pi 4 (CM4 module in the case of Holo Red) and Pi 5, with at least 4 GB RAM. Not tested, not guaranteed on earlier Pi models (Pi 3 and older) or on 2 GB boards.

4.2 Boot medium

The appliance edition boots from a microSD card. Use a good-quality card of at least 8 GB; counterfeit or worn cards are a frequent cause of boot problems.

4.3 Tested USB DACs and receivers
DeviceChip/interfacePCMNative DSDDoP
Gustard USB Audio 2.0(direct USB DAC)YesYesYes
TT-DAC-2026 / TT-DAC-NVAmanero Combo 384 and 768YesYesYes
Audio-GD DDC → Gustard (I2S)Amanero Combo384YesNo: due to the 384 kHz sample-rate ceiling, DSD256 is ruled out at the hardware level both natively and via DoPNo: the chip's DoP detector only recognizes 24-bit frames at firmware level; the 32-bit DoP attempt produced audible noise with both byte orders, and the display showed PCM instead of DSD

5Appendix: technical background

5.1 The signal path philosophy

bpplay's design goal is for sound to travel from the file's loading into memory to the DAC through the fewest, best-documented steps possible. When an integer source meets an integer DAC format, this means zero arithmetic conversion.

5.2 The role of the sound driver

The phrase "the sound driver performs the last step" in the signal-path messages refers to the audio subsystem of the underlying operating system (ALSA on Linux); a platform-independent, precise wording.

5.3 Boot-time measurement

bptune measures the CPU cores at boot and chooses the playback core.

5.4 Quiet profile

When the quiet profile is on, the following background services are stopped for playback: cron, avahi, rpcbind, polkit, udisks2, the periodic maintenance timers, the udev control sockets, the user session manager, and Wi-Fi supplicant services when no Wi-Fi connection is active. These are never stopped: journald, ssh, NetworkManager, dbus and logind. If any of them is not running after the stop, everything is restored at once. The profile is switched off again when playback ends. During playback, the system spins down the hard disks connected to the machine, including external USB drives, because the music is already in memory. Nothing is written to the drive. It spins up again the next time it is accessed, which can take a few seconds. On the Raspberry Pi the SD or MMC card is kept awake during playback instead of sleeping.

Stopping playback and the local keyboard: during playback the keyboard attached to the device does not work (this is part of the quiet profile: the login service on the device's own screen is stopped). In normal mode (Full Pure off) playback can be stopped over SSH (with the q key of the player). In Full Pure mode playback cannot be stopped by anything: the list plays to the end, and the safety timer returns the network after the list length plus 60 seconds.

5.5 Language editions

bpplay is released in Hungarian (HU) and English (EN) editions. The language is fixed in the image: it sets the texts of the music selector and of bptune, the default music folder (Zenék in the HU edition, Music in the EN edition) and the time zone (Europe/Budapest in HU, UTC in EN). On the desktop edition the keyboard layout follows the language (hu or us).

Articles on medium.com about the development of the software and the workings of computer audio systems:

6What's new: RC21 and RC22

RC21

  • Full Pure (u key): the network is switched off at link level while the music plays.
  • Global search across all drives with the / key, with a stored index; playback starts only after the first indexing pass.
  • The g machine survey: report texts, the CPU isolation mode screen, a short summary at the first start, the Intel management engine runtime state, USB controllers.
  • Trial: the settings area is used only on the boot stick, and a new image is a new trial. A new image's first boot does not take over a settings area left by another image, so the trial starts from the first boot.
  • A drive that disappeared behind a search result is handled with a message; hidden and ._ files are not indexed.
  • The now-playing line keeps Artist and Title visible when the album name is long; reaching the folder or row limit is reported (bpplay 1.5.8 and 1.5.9). When bpplay's output is piped, the line fits the terminal width (bpplay 1.5.15).
  • ID3 tags are read from AIFF and WAV files, with the artist per track (bpplay 1.5.10 and 1.5.12).
  • The output selector can be canceled with q or Esc.
  • SACD ISO: more reliable track paths and indexing; folder mode accepts DFF files and SACD ISO tracks (bpplay 1.5.13).
  • DSD files: the file's own end padding is no longer played as audio.
  • The English image contains no Hungarian text, and the default music folder follows the image language (Music in EN, Zenék in HU).

RC22

  • Full Pure and repeat mode are kept apart: repeat blocks Full Pure, and the other way round.
  • The output chosen in the selector is remembered in the settings area; short help for a and n; an SSH banner on the Raspberry Pi; the HU desktop edition gets the Hungarian keyboard layout.
  • The Hungarian image runs in local time (Europe/Budapest); the English image stays on UTC.
  • The g report has a DAC section: the formats the DAC advertises, the format used during playback, and the mixer and mute state.
  • Desktop edition: the quiet profile stops a shorter list, so that the graphical session stays open.
  • bpplay 1.5.16: no hang with a non-terminal, open input, and a clean stop on TERM, INT and HUP. bpplay 1.5.17: the escape sequence of an arrow key no longer triggers a player command.
  • bpplay 1.5.18: on TEAC/Esoteric (0x0644) and Luxman (0x3255) DACs, 16 and 24 bit sources are sent in their own width first (S16 or S24 packed), with 32 bit as fallback; other DACs keep 32 bit first.
  • Raspberry Pi: the remaining trial time is shown in the music selector header line (Trial: N days left).
  • The short summary is no longer truncated; the 5 minute NAS re-check is gone; the R key is gone from the drive selector, and an already mounted drive asks whether to check for changes.
  • The x key excludes a drive from search and indexing only; the drive stays in the selector with the mark (excluded from search), and the same key switches it back.
  • bptune 0.3.8: the Renesas hint appears only without a working device, Bay Trail TXE is recognized, and a firmware version of 0.0.0.0 is shown as unknown.

§Disclaimer

The bpplay and bptune software, as well as the music selector serving this device (zenevalaszto.py) is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability or fitness for a particular purpose.

The developer accepts no liability for direct or indirect damages arising from the use, malfunction or failure of the software or the device, including possible damage to connected audio equipment (DAC, amplifier, speakers), loss of data, or any damage resulting from use other than the intended purpose.

This manual strives to describe the most accurate, current state possible, but the developer does not guarantee the completeness or error-freeness of its contents, and reserves the right to update it without prior notice. The device and the manual are made exclusively for the end-user music-listening purpose described herein; any other use is at your own risk.

All rights to the software and the device are reserved; copying, reverse engineering or passing them to third parties may only take place with the prior written permission of the developer.

Happy listening!

bpplay / bptune · Class A Computing · Koscso Media Engineering Kft. · Contact