Re: Raspberry Pi 4

Hello all,

I managed to get pianoteq up and running on pi 4 following Edgar's great guide, but when I click the desktop icon to launch pianoteq it always give to me the options to execute file in terminal or execute or to open the text file, does this mean that I haven't made the file executable?

Also what is the easiest way to make pianoteq start on boot up?

Thanks a lot for your help

James

Re: Raspberry Pi 4

jamesb5 wrote:

Hello all,

I managed to get pianoteq up and running on pi 4 following Edgar's great guide, but when I click the desktop icon to launch pianoteq it always give to me the options to execute file in terminal or execute or to open the text file, does this mean that I haven't made the file executable?

Also what is the easiest way to make pianoteq start on boot up?

Thanks a lot for your help

James

Actually figured out that the execute in terminal problem was a permissions thing in file manager, for anyone with a similar problem go to preferences in file manager and tick "don't ask options on executable files".

Now to figure out how to make pianoteq start on boot.

Cheers,
James

Re: Raspberry Pi 4

Hello,

I've acquired a Raspberry Pi 4 for a headless pianoteq standalone controlled via a USB midi controller. I have two questions before I jump into the setup process:

  1. I'm considering buying a DAC to offload the sound generation part off of the pi and get other connectors (RCA or 1/4" jack, 5-pin midi would be nice too), but there are so many options.
    I'd like the best and most stable realtime performance but fanless if possible. I've read that USB DACs tend to be surprinsingly good, but the use cases mentioned there are very different. Do you guys have any recommandations as to what to prioritise, promising options etc. ?

  2. In the spirit of headlessness, I'd like to use my controller's midi buttons and faders to change the sound. I couldn't find a midi control change to cycle between presets however. Is this currently not possible?

Thanks a lot for reading me!

Last edited by DrJedd (22-08-2020 12:10)

Re: Raspberry Pi 4

DrJedd wrote:

I'm considering buying a DAC to offload the sound generation part off of the pi and get other connectors (RCA or 1/4" jack, 5-pin midi would be nice too), but there are so many options.
I'd like the best and most stable realtime performance but fanless if possible. I've read that USB DACs tend to be surprinsingly good, but the use cases mentioned there are very different. Do you guys have any recommandations as to what to prioritise, promising options etc. ?

I think using a DAC with RPi is less about offloading processing than it is about improving quality of sound output.  The built-in audio output of the RPi is not good.  Just about any DAC solution you get will make it quite good.

For me priorities are simplicity, good sound, and price (and avoiding over-analyzing and steering clear of audiophile tendencies many have on these issues, which I consider mostly worthless).  Not sure what you reference to "use cases" is about.  You just want some decent audio out of your RPi.  Sounds like a simple use case that can be solved by either a DAC HAT or a USB DAC.

I've used both a HifiBerry DAC+ Standard w/RCA plugs HAT ( $29 at pishop: https://www.pishop.us/product/hifiberry...a-version/ ) and a Behringer UCA202 USB DAC ($29 at b&h: https://www.bhphotovideo.com/c/product/...rface.html )

I started with the HifiBerry DAC and really liked it.   At one point I rebuilt my Raspbian with different version/setup and I had an issue with enabling the HifiBerry, plugged the UCA202 in and it worked fine, so I've gone with it since.  Not sure of any audio difference, both sound fine, but I prefer using the HAT so I'm going to solve the configuration issue or go back to the prior build of Raspbian that I was using to get it going again.

Last edited by hesitz (22-08-2020 18:06)

Re: Raspberry Pi 4

Thank you hesitz for your input on both these devices!

hesitz wrote:

Not sure what you reference to "use cases" is about.  You just want some decent audio out of your RPi.  Sounds like a simple use case that can be solved by either a DAC HAT or a USB DAC.

Most of the discussion I've linked is for home cinema hi-fi use. I'd argue that there's a major difference with my/our use case because we're dealing with an audio stream that can't be pre-buffered as it gets fed midi notes in real time. And the lower the latency, the better for me (although anything under 15ms should be fine).

For stage use, I think the DAC will never be the bottleneck in terms of sound quality (rather the PA and the room acoustics), but I also intend to use the little devil in my studio so it would be nice to push it to the limits. Hence why I haven't purchased a DAC yet and I'm probing around.

(Also I'd love that 5-pin midi so I can plug any hardware without pesky adapters )

Thanks again, hope you manage to get the hifiberry working again!

Re: Raspberry Pi 4

DrJedd wrote:

Thank you hesitz for your input on both these devices!

hesitz wrote:

Not sure what you reference to "use cases" is about.  You just want some decent audio out of your RPi.  Sounds like a simple use case that can be solved by either a DAC HAT or a USB DAC.

Most of the discussion I've linked is for home cinema hi-fi use. I'd argue that there's a major difference with my/our use case because we're dealing with an audio stream that can't be pre-buffered as it gets fed midi notes in real time. And the lower the latency, the better for me (although anything under 15ms should be fine).

For stage use, I think the DAC will never be the bottleneck in terms of sound quality (rather the PA and the room acoustics), but I also intend to use the little devil in my studio so it would be nice to push it to the limits. Hence why I haven't purchased a DAC yet and I'm probing around.

(Also I'd love that 5-pin midi so I can plug any hardware without pesky adapters )

Thanks again, hope you manage to get the hifiberry working again!

For home cinema use, I use HDMI for video and sound. No need for an extra DAC.

Re: Raspberry Pi 4

Hi everyone,

I'm writing here to share my Raspberry Pi 4 touchscreen project and how I managed to achieve:

Maximum polyphony of 96
64 sample buffer
24000Hz internal sample rate

I'm using:

Raspberry Pi 4 Model B w/ 2GB RAM (£34)
HiFiBerry DAC2 Pro (£45)
Official 7" Touchscreen display (£60)
SmartiPi Touch 2 Case (£24)
SmartiPi Touch 2 Back Cover 35mm (£7)
USB-C Cable with On/Off Switch (£3)
Pianoteq 6 Stage

(all prices rounded up, and from The Pi Hut)

I followed Edgar's brilliant guide (https://forum.modartt.com/viewtopic.php?id=5351) for the Raspberry Pi 3, but seemingly had to spoof the Pianoteq software to run at a 24000Hz internal sample size, whilst the hardware was running at 48000Hz.  Pianoteq doesn't like it and complains of the wrong buffer size, and I get consistent spikes on the CPU graph, but the performance is flawless with no audio hitches whatsoever.

To do this I had to switch around the device sample rate, internal sample rate and buffer size - setting the buffer size I wanted first, with a setting that Pianoteq didn't complain about, then changing the sample size to one with which it thinks the buffer size is suboptimal.  The buffer size stays, but if I go to change it the 64 sample buffer size isn't one of the options from the drop down menu.

I'm sorry I can't be more specific - I've set the settings and don't want to go through the rigmarole of fiddling around, but if anyone has any questions please let me know.

A question for the forum - does this sound like a bug?  I don't want them to fix it in case I can't get these results again!

I was sceptical about the project, but I'm really happy with results.  I've wired the output from the Pi through a small amplifier (Lepy LP-2020A) and into the built in speakers on my Yamaha P-45.  The speakers aren't great, but the treble and bass settings on the little amp make it sound more alive.

I've set up the OS to start Pianoteq fullscreen when I turn on the Pi, and have a shutdown shortcut on the desktop, so I can turn it all off quite easily.  I don't have links to the guides, but searches relating to Linux brought be to results quickly.

To address something I read in my travels through the forums; in my experience RAM has little to no effect on the performance - 2GB is enough to run both the OS and Pianoteq with plenty of room to spare (current usage with Pianoteq open is consistently c.237MB).  CPU effects performance, and using a DAC hat offloads the processing of audio, increasing performance, and allowing for more connectivity.

Thanks to everyone for your posts and to Edgar, and Niclas for his help in posting Edgar's guide!

Tom

Last edited by tjp (14-02-2021 14:58)

Re: Raspberry Pi 4

tjp wrote:

Hi everyone,
24000Hz internal sample rate

Isn't 24000 Hz a bit low? I think that means, your frequency spectrum doesn't go higher than 12 kHz (?)
I don't have any problems with 32000... even with polyphony 128 and no overclocking.
My audio device is a Sharkoon Gaming DAC Pro S (USB-Stick).
But if you don't hear a significant difference, it's not a problem, of course.

Martin

Re: Raspberry Pi 4

MartinGr wrote:

Isn't 24000 Hz a bit low?

In my opinion the minimum internal sample rate should be 32000 Hz (~16000 Hz frequency spectrum incl. roll-off). Even with 32000 Hz sample rate especially the reverb and "naturalness" degrades significantly compared to 44100 and 48000 Hz in my experience. But that does not mean, one can't be perfectly happy with a less "natural" timbre. There might be cases, where a well balanced velocity and latency is more important, than the sound quality.

Re: Raspberry Pi 4

MartinGr wrote:
tjp wrote:

Hi everyone,
24000Hz internal sample rate

Isn't 24000 Hz a bit low? I think that means, your frequency spectrum doesn't go higher than 12 kHz (?)
I don't have any problems with 32000... even with polyphony 128 and no overclocking.
My audio device is a Sharkoon Gaming DAC Pro S (USB-Stick).
But if you don't hear a significant difference, it's not a problem, of course.

Martin

Hi Martin - what is your buffer size?

Re: Raspberry Pi 4

tjp wrote:
MartinGr wrote:
tjp wrote:

Hi everyone,
24000Hz internal sample rate

Isn't 24000 Hz a bit low? I think that means, your frequency spectrum doesn't go higher than 12 kHz (?)
I don't have any problems with 32000... even with polyphony 128 and no overclocking.
My audio device is a Sharkoon Gaming DAC Pro S (USB-Stick).
But if you don't hear a significant difference, it's not a problem, of course.

Martin

Hi Martin - what is your buffer size?

96 Samples...

Re: Raspberry Pi 4

Indeed, if you upgrade to Pianoteq 7 and switch to a 64bit OS (e.g. 64bit raspbian) you should even be able to use 48000Hz internal sample rate, the performance increase is about 50% going from 32bit to 64bit (see relevant threads in the forum).

In this way my Pi 4B happily runs at 48000 internal sample rate with 128 buffer size, admittedly I'm not using crazy reverb (and have it overclocked slightly to 1800Mhz with heatsink but even that's not really necessary).

Re: Raspberry Pi 4

tjp wrote:

Hi everyone,

I'm writing here to share my Raspberry Pi 4 touchscreen project and how I managed to achieve:

Maximum polyphony of 96
64 sample buffer
24000Hz internal sample rate

I'm using:

Raspberry Pi 4 Model B w/ 2GB RAM (£34)
HiFiBerry DAC2 Pro (£45)
Official 7" Touchscreen display (£60)
SmartiPi Touch 2 Case (£24)
SmartiPi Touch 2 Back Cover 35mm (£7)
USB-C Cable with On/Off Switch (£3)
Pianoteq 6 Stage

(all prices rounded up, and from The Pi Hut)

I followed Edgar's brilliant guide (https://forum.modartt.com/viewtopic.php?id=5351) for the Raspberry Pi 3, but seemingly had to spoof the Pianoteq software to run at a 24000Hz internal sample size, whilst the hardware was running at 48000Hz.  Pianoteq doesn't like it and complains of the wrong buffer size, and I get consistent spikes on the CPU graph, but the performance is flawless with no audio hitches whatsoever.

To do this I had to switch around the device sample rate, internal sample rate and buffer size - setting the buffer size I wanted first, with a setting that Pianoteq didn't complain about, then changing the sample size to one with which it thinks the buffer size is suboptimal.  The buffer size stays, but if I go to change it the 64 sample buffer size isn't one of the options from the drop down menu.

I'm sorry I can't be more specific - I've set the settings and don't want to go through the rigmarole of fiddling around, but if anyone has any questions please let me know.

A question for the forum - does this sound like a bug?  I don't want them to fix it in case I can't get these results again!

I was sceptical about the project, but I'm really happy with results.  I've wired the output from the Pi through a small amplifier (Lepy LP-2020A) and into the built in speakers on my Yamaha P-45.  The speakers aren't great, but the treble and bass settings on the little amp make it sound more alive.

I've set up the OS to start Pianoteq fullscreen when I turn on the Pi, and have a shutdown shortcut on the desktop, so I can turn it all off quite easily.  I don't have links to the guides, but searches relating to Linux brought be to results quickly.

To address something I read in my travels through the forums; in my experience RAM has little to no effect on the performance - 2GB is enough to run both the OS and Pianoteq with plenty of room to spare (current usage with Pianoteq open is consistently c.237MB).  CPU effects performance, and using a DAC hat offloads the processing of audio, increasing performance, and allowing for more connectivity.

Thanks to everyone for your posts and to Edgar, and Niclas for his help in posting Edgar's guide!

Tom

You are playing back into the P-45 through an amp? That really doesn't sound like a good idea! The P-45 has no input, it only has a headphone out, so how do you have the amp connected?