Pianoberry – Pianoteq 8 @ 1.33 ms latency on Raspberry Pi 5

Weird that you couldn’t get the same performance as me - given we’re using such similar systems. I’m using a 96K sample rate, but with an ‘internal sample rate’ of 48K, which I think is what PT (Pro) defaults to if you switch to 96K. I have in the past tried switching to 96K internal rate but couldn’t hear the slightest difference so now don’t bother. I’ve left polyphony on the default of 48 and am currently seeing a ‘performance index’ of about 70.

I’m sure the PT sample rate figure is correct in its own right. I’m just not sure what exactly it might correspond to in the real world. That’s why the approach I took before was to measure latency between onset of key strike noise and onset of sound from the loudspeaker. The idea was to take in the whole chain to arrive at a figure which might correspond to how the thing felt to play.

I.

Hi there.

I’m trying a new install of Pianoberry v1.1.0 onto a raspberry pi 5 (4gb) with a pisound board connected - and I’m drawing a blank. (I also have the Raspberry Pi Active Cooler kit on)

I followed the instructions to flash pianoberry.img.zip onto the micro SD card
(I found I did have to unzip it, otherwise Raspberry PI Imager writes the .img file onto the card as a single file)

When I then insert the microSD card into the Pi 5, the status light goes Red, then Green, then after a few seconds the LEDs on the PI Sound flash once.

I then connected a USB midi keyboard (I’ve tried 2), and I don’t get any sound out?

Because it’s headless - I’m not sure what to do next?

I tried flashing the microSD card with Raspberry Pi OS, and it boots fine with that?

Any help appreciated.

This should definitely not be needed. Open Raspberry Pi Imager (v1.8.5 or later), click “CHOOSE OS” and click “Use Custom”. Flash without setting anything else, we just want to flash the image to the SD card.

This is the error right here. Pianoberry is set up to use the MIDI port like it says in the readme and in the release notes.

  • Rune

Pianoteq has a “Listen to all MIDI inputs” option, this should allow it to listen to both USB MIDI and Pisound MIDI input.

Hi Elektrofon,

Thanks for your reply.

Apologies — you’re absolutely right, and you even mentioned it in an earlier message: the pre-built image is set up to receive input from the Pisound MIDI In. Connecting a USB MIDI keyboard is possible, but it requires rebuilding Pianoberry.

I installed Pianoteq for Linux with the intention of exploring how USB keyboards are defined, but we got a bit sidetracked trying out different pianos.

In the end, we concluded that we’ll want access to the Pianoteq UI, so we’ll be going in a different direction.

That said, I did rebuild the Pianoberry image with a few configuration tweaks — and I have to say, I’m a big fan of your Docker-based build system. I’m definitely adding that to my bag of tricks!

Best wishes

1 Like

I’m very interested in purchasing a Pi 5 and Pisound hat to use with Pianoberry. However, the Pisound is currently out of stock, while the Pisound Micro is available. I don’t mind doing a little soldering so that I don’t have to wait for the regular Pisound to become available again.

Does Pianoberry work with the Pisound Micro out of the box? If not, is it straightforward to modify it to make it work, and are there any instructions available for doing so?

I haven’t tested the Pisound Micro, but with a few tweaks to the Pianoberry build script(s) it should work. If there are instructions depends on what your definition is and where you are coming from in terms of experience. The readme is all there is except the source code. All of it is open source on GitHub.