May I ask a question about my specific use case ? I own a Roland digital piano. I’d like to use Pianoteq + external speakers instead of the kinda muffled built-in ones (kinda ruins my pleasure of practising !!).
But I also use an Android tablet with a piano method app (Musora / Pianote).
Would it be possible to use a Rapberry, with Pianoberry, that would :
play the notes from my digital piano (of course) but also
send the digital audio of my Android tablet to the analog output of the raspberry (if connected by USB - if it can consider the Raspberry as an external sound card for the tablet) ?
This way it would solve all my problems at once
I own a Pianoteq pro licence (no Pi ATM, will have to get one back).
I think this scenario is best served by Patchbox OS; which is the official Blokas distribution for general sound applications. What you describe sounds like something Patchbox OS would solve almost out of the box. You might take a minuscule hit on latency but I very much doubt it would be noticeable.
The simplest solution to your problem would be to connect the headphone output on the tablet to the line input on the Pisound. No USB. USB will depend heavily on how the tablet handles audio, which I guess is very limited.
Sending audio from a tablet to a Raspberry Pi would be troublesome - while Pi 5 should have USB OTG / Gadget Mode support on its USB C port (USB A ports are host-only and the tablet probably can’t pretend it is an external audio card), at the same time, the tablet would be responsible for powering the system, so it would be limited by its battery.
Furthermore, configuring all of it might be complicated as it is a complex feature. I haven’t ever done that myself, but it would involve enabling USB Audio Gadget mode in the kernel, and occasionally the steps necessary change completely as newer kernel versions get released (one relevant guide is here: RPi Zero 2 W Audio Gadget - Hackster.io)
I agree with this as the most straightforward and probably the best way to go about it - as powering the Pi up is trivial too.
The issue where the new version of Pisound didn’t work should now be resolved.
I also added a broader MIDI device mapping. You should now be able to connect to the Pisound DIN MIDI port as well as via USB MIDI.
Hi ! Thanks a lot for your replies / suggestions ! Yep, I’ll rather try to find an OTG DAC for my tablet. That’s not top priority anyway !
BTW, did you guys & gals notice the release of Pianoteq 9 ? I wonder if it’s more CPU intensive and compatible with Pianoberry…
Can I use a full configuration file I make on my main Linux PC beforehand, including MIDI mappings and import it onto Pianoberry ? This way, I’ll still be able to switch instruments, right ? (and add fancy stuff like release velocity or assign various actions to my 3 pedals
The issue of preset selection is discussed further up the thread; in summary it’s not the focus of the Pianoberry core, but perhaps it should be. I always though of Pianoberry as a jumping off point for creating specialized instruments. My use-case is to have a physical piano running Pianoteq that I can turn on and immediately start playing without any distractions.
The way I will deal with presets in my own instrument is to have 2-3 ready made presets which I will select with a physical selector switch on the instrument. This selector switch will be connected to the Raspberry Pi and generate MIDI messages. Pianoteq will be set up with a MIDI map that will change presets on these messages.
There is already an example MIDI map in the Pianoberry project. The easiest way to generate such a map is to generate it from a Pianoteq instance running with full GUI on macOS, Windows or Linux.
Hope this helps.
I will be including instructions for my suggested MIDI map solution when I get to that point in my own project.
I stumbled upon this post about a week ago, immediately ordered a Pisound, and was up and going within a few minutes today with a Raspberry Pi 5 and a MK1 Rhodes preset on Pianoteq 9.
I’ve wanted something like this for a long time! This is great.
I haven’t assembled my Pianoberry yet, but considering my digital piano (Roland FP30) does not send CCs from its panel buttons, I bought a cheap used mini controller (Akai LPD8). Considering it has 8 pads, I will be able to map 8 instruments from the Pianoteq config menu on the PC and then transfer the config file to the Pi. (I’ll probably use the 8 knobs for effects etc.)
If Pianoteq enabled to map a combination of events (like, pushing an unused pedal then a key), I wouldn’t need this but I guess it’s not possible. Might file a feature request
Yep, the issue is, ATM, next preset also cycles through the presets belonging to instruments you do not own. (I have filed a feature request about this to Modartt).
BTW you may be interested to know that Pianoteq 9.1 was released with a new instrument pack ; a synth “engine” ! (it makes use of the same acoustic modeling engine)
Hi. New to the world of Raspberry PI, but have put an Raspgerry Pi 5 together with a Pisound Micro. All working with the standard OS and Pianoteq 9. I’m impressed with the performance, but really want to go with your headless streamlined version - especially the power down advantage.
I’ve tried your image, but was not surprised to hear nothing. I’m aware you use the original pisound and I’ve had a look at the github scripts but i’m not seeing what needs to be changed. Could you provide some pointers?
I haven’t tested Pianoberry with the Pisound Micro, only with Pisound.
There shouldn’t be any need to change anything in the config or build script to make it work though. As long as the Pisound Micro is the only audio device it should have worked.
I hope someone else can chime in that have had success with the Pisound Micro.