<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Modartt user forum - Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
		<link>https://forum.modartt.com/viewtopic.php?id=6843</link>
		<description><![CDATA[The most recent posts in Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts.]]></description>
		<lastBuildDate>Wed, 22 Apr 2020 08:34:23 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=966438#p966438</link>
			<description><![CDATA[<p>You are right EvilDragon, I can&#039;t actually hear any discernible difference between 96k and 48k now (it did strike me as nonsensical). I must have unintentionally changed a setting somewhere when I was trying it out this morning, clearly still asleep <i class="far fa-meh-rolling-eyes smiley"></i></p>]]></description>
			<author><![CDATA[null@example.com (jari_42)]]></author>
			<pubDate>Wed, 22 Apr 2020 08:34:23 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=966438#p966438</guid>
		</item>
		<item>
			<title><![CDATA[Re: Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=966437#p966437</link>
			<description><![CDATA[<p>Considering you put the internal SR of audio engine to the same value regardless of audio interface sample rate, this is pretty much inconsequential. Testing it with a spectrometer you can see nothing really changes in the frequency response between 48k and 96k when you have capped the internal audio engine sample rate to the same value... It just gets upsampled to audio interface sample rate. So when you say &quot;so much richer&quot;, I would say &quot;placebo&quot;. Maybe the audio interface DAC plays into it a little bit, but I&#039;m listening here with a really decent and not cheap audio interface (RME UFX+), and there&#039;s literally no audible difference between 48k and 96k. There are some minor differences in transient response if you change the internal audio engine SR above 48k (transients are slightly more detailed then), but you gotta have Pianoteq Pro for that.</p><p>Here&#039;s some pics:</p><p><a href="https://imgur.com/a/Tm1tP0K">https://imgur.com/a/Tm1tP0K</a></p><br /><p>It&#039;s roughly pretty much the same thing. Really hard to get a screenshot at exactly the same time in the piece, so that accounts for most of those differences in peaks and troughs. If you average the curve you&#039;d get pretty much the same thing. Those tiny peaks above 20k are likely upsampling artifacts.</p><p>Let&#039;s just remember that pianos don&#039;t really have an awful lot of spectral energy above 10-12k.</p>]]></description>
			<author><![CDATA[null@example.com (EvilDragon)]]></author>
			<pubDate>Wed, 22 Apr 2020 08:15:14 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=966437#p966437</guid>
		</item>
		<item>
			<title><![CDATA[Re: Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=966436#p966436</link>
			<description><![CDATA[<div class="quotebox"><cite>EvilDragon wrote:</cite><blockquote><p>I wonder if setting things to 96k might actually create additional CPU load. Did you perhaps try 48k but 128 samples buffer size?</p></blockquote></div><p>For some reason 96k sounds so much richer than 48k and the CPU load at 96k with 256 samples seems to be much the same as at 48k with 128 samples (presumably because the X400 is doing the processing). But then I&#039;m not pushing the polyphony that much with what I play or using crazy reverb.</p>]]></description>
			<author><![CDATA[null@example.com (jari_42)]]></author>
			<pubDate>Wed, 22 Apr 2020 07:07:31 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=966436#p966436</guid>
		</item>
		<item>
			<title><![CDATA[Re: Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=966431#p966431</link>
			<description><![CDATA[<p>I wonder if setting things to 96k might actually create additional CPU load. Did you perhaps try 48k but 128 samples buffer size?</p>]]></description>
			<author><![CDATA[null@example.com (EvilDragon)]]></author>
			<pubDate>Tue, 21 Apr 2020 20:19:55 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=966431#p966431</guid>
		</item>
		<item>
			<title><![CDATA[Re: Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=966429#p966429</link>
			<description><![CDATA[<p>Thanks for the tips.&nbsp; I just ordered a Pi 4 with Hifiberry DAC, we&#039;ll see how it works. . .</p>]]></description>
			<author><![CDATA[null@example.com (hesitz)]]></author>
			<pubDate>Tue, 21 Apr 2020 19:15:29 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=966429#p966429</guid>
		</item>
		<item>
			<title><![CDATA[Re: Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=966418#p966418</link>
			<description><![CDATA[<p>I compiled the RT kernel from scratch using the excellent instructions here:<br /><a href="https://lemariva.com/blog/2019/09/raspberry-pi-4b-preempt-rt-kernel-419y-performance-test">https://lemariva.com/blog/2019/09/raspb...mance-test</a><br />you can either do the same or download the precompiled kernel he used from his github page:<br /><a href="https://github.com/lemariva/RT-Tools-RPi/tree/master/preempt-rt/kernel_4_19_59-rt23-v7l%2B">https://github.com/lemariva/RT-Tools-RP...t23-v7l%2B</a><br />and substitute the binaries as described in the last few sections of his instructions. As far as I know there isn&#039;t a downloadable Raspbian RT image unfortunately.</p><br /><p>As for setting up the Raspberry Pi, there&#039;s a great guide by Edgar Bustamante here:<br /><a href="https://www.modartt.com//downloads/gen/dl200421080437mQ32AcRfJa/Pianoteq_RaspberryPi3_v3.pdf">https://www.modartt.com//downloads/gen/...Pi3_v3.pdf</a><br />and another good guide by jimmi here (he uses a headless setup with VNC):<br /><a href="https://drive.google.com/file/d/1uYW5p3675RZheZQqyLuTiGStu3xxcNAQ/view">https://drive.google.com/file/d/1uYW5p3...xcNAQ/view</a></p><br /><p>Regarding the audio quality, when I tried it this morning with the headphone jack from the Pi it sounded quiet and fuzzy (I guess because it was only designed to drive headphones) but your mileage may vary. The Suptronics X400 sounds fantastic to my ears, powerful, clear with lovely bass. There are other audio boards you could use instead of the X400 like the IQaudIO Pi-DAC+ or the HiFiBerry DAC+ Pro (the main reason I got the X400 was because it was the only high-quality audio board Pi Hut had in stock).</p>]]></description>
			<author><![CDATA[null@example.com (jari_42)]]></author>
			<pubDate>Tue, 21 Apr 2020 07:59:17 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=966418#p966418</guid>
		</item>
		<item>
			<title><![CDATA[Re: Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=966417#p966417</link>
			<description><![CDATA[<div class="quotebox"><cite>jari_42 wrote:</cite><blockquote><p>I&#039;ve managed to get amazing Pianoteq performance on an overlocked Raspberry Pi 4 with RT kernel, no audio dropouts with max audio sample rate and internal sample rate settings!!</p></blockquote></div><p>Wow, that all sounds pretty good.&nbsp; </p><p>Where do I go to get a Raspian with the RT kernel?&nbsp; &nbsp;I see this page on github: <a href="https://github.com/lemariva/RT-Tools-RPi">https://github.com/lemariva/RT-Tools-RPi</a>&nbsp; &nbsp;Which makes me wonder whether there&#039;s a downloadable image for Raspian RT, or whether I need to recompile the kernel or substitute RT binaries for standard binaries of the kernel.&nbsp; How exactly did you get the RT kernel version?</p><br /><p> Also, anywhere other than the Pianoteq readme file that has instructions for how you set yours up?</p><p>I&#039;m also curious about the audio quality.&nbsp; How is it from just the headphone jack of the Pi?&nbsp; And how much better is that Suptronics board?</p>]]></description>
			<author><![CDATA[null@example.com (hesitz)]]></author>
			<pubDate>Tue, 21 Apr 2020 05:39:53 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=966417#p966417</guid>
		</item>
		<item>
			<title><![CDATA[Re: Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=966404#p966404</link>
			<description><![CDATA[<p>I&#039;ve managed to get amazing Pianoteq performance on an overlocked Raspberry Pi 4 with RT kernel, no audio dropouts with max audio sample rate and internal sample rate settings!!</p><p>Hardware setup:</p><p>- Computer: Raspberry Pi 4 Model B 2GB RAM<br />&nbsp; &nbsp;- Running Raspbian Debian Buster Lite (desktop GUI installed after)<br />&nbsp; &nbsp;- Raspbian Real Time Kernel (4.19.71-rt24-v7l+)<br />&nbsp; &nbsp;- Large heatsink (no case covering)<br />&nbsp; &nbsp;- Overclocked to 1.75 GHz<br />- Sound Card: Suptronics X400<br />- Pianoteq v6.7.0<br />- Piano: CLP-170 (GH3) USB MIDI connection</p><p>Pianoteq setup:<br />- Performance governor enabled and limits.conf edit (as described in Pianoteq readme) </p><p>- Devices settings<br />&nbsp; &nbsp;- Audio device type: ALSA<br />&nbsp; &nbsp;- Output: IQaudIODAC Direct hardware device without any conversions<br />&nbsp; &nbsp;- Sample rate: 96000 Hz <br />&nbsp; &nbsp;- Audio buffer size: 256 samples (2.7 ms)</p><p>- Performance settings<br />&nbsp; &nbsp;- Performance index: 19<br />&nbsp; &nbsp;- Multicore rendering: MAX<br />&nbsp; &nbsp;- Internal sample rate: 48000 Hz<br />&nbsp; &nbsp;- Maximum polyphony: Auto (optimistic)</p><p>I&#039;m getting about 50-60% CPU load most of the time, no spikes that I can see with polyphony going up to about 30 with no issues whatsoever. And I&#039;m running it on the desktop as it just works so well, this is more than I was hoping for <i class="far fa-smile smiley"></i></p>]]></description>
			<author><![CDATA[null@example.com (jari_42)]]></author>
			<pubDate>Mon, 20 Apr 2020 09:22:21 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=966404#p966404</guid>
		</item>
		<item>
			<title><![CDATA[Re: Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=963021#p963021</link>
			<description><![CDATA[<p>I&#039;m also interested to know if performance can be improved (setting internal freq. at 44 KHz for instance !) by</p><p>- running without X<br />- using a low latency / RT kernel<br />- starting pianoteq with the options specified in the README LINUX to use an alternate multithreading strategy (max)</p><p>Also, I&#039;d be interested in a way to set it up on a screen-less RPi (and have a couple buttons mapped to switch instruments, active the metronome... and turn the RPi off :-)</p><p>Cheers !</p>]]></description>
			<author><![CDATA[null@example.com (mahen)]]></author>
			<pubDate>Wed, 23 Oct 2019 14:38:33 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=963021#p963021</guid>
		</item>
		<item>
			<title><![CDATA[Re: Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=962566#p962566</link>
			<description><![CDATA[<p>Have you tried without GUI? It improved performance on the RPi3<br />(Runlevel 3 and Pianoteq headless)</p>]]></description>
			<author><![CDATA[null@example.com (marcos daniel)]]></author>
			<pubDate>Mon, 30 Sep 2019 04:50:28 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=962566#p962566</guid>
		</item>
		<item>
			<title><![CDATA[Raspberry Pi 4: Pianoteq 6.6, 98 polyphony, zero audio dropouts]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=962550#p962550</link>
			<description><![CDATA[<p>Hey everyone, I&#039;m excited to say I was able to run Pianoteq v6.6 smoothly without audio dropouts on the latest Raspberry Pi 4!</p><p>Here are the details. This was my first time messing with audio with the Raspberry Pi, and in hindsight this test could have been a lot cheaper (more below).</p><p>-----------------------------------------------------------------------------</p><p>My actual setup:</p><p>- Computer: <a href="https://www.raspberrypi.org/products/raspberry-pi-4-model-b/?variant=raspberry-pi-4-model-b-4gb">Raspberry Pi 4 Model B 4 GB RAM</a><br />&nbsp; &nbsp;- Running unmodified Raspbian Debian Buster Lite (desktop GUI packages installed after)<br />&nbsp; &nbsp;- No real time operating system patches<br />&nbsp; &nbsp;- No heatsinks or fans (but also no case covering)<br />&nbsp; &nbsp;- Not overclocked (using factory 1.5 GHz)<br />- Audio Card: <a href="http://iqaudio.co.uk/hats/8-pi-dac.html">IQaudIO Pi-DAC+</a><br />- Piano VST Software: Pianoteq v6.6.0 Linux, Trial<br />- MIDI Song Played: <a href="https://musescore.com/hmscomp/scores/2437586">Beethoven Symphony No. 6 &quot;Pastoral&quot; (5th movement) arranged for Piano solo</a></p><p>-----------------------------------------------------------------------------</p><p>Settings had to be tweaked down from maximum to allow for smooth playback. Here are the details:</p><p>- Operating System Setup: Followed the Raspberry Pi performance tweaks guide by Edgar Bustamante:&nbsp; <a href="https://www.pianoteq.com//downloads/gen/dl190929090931sGj4m74mM2/Pianoteq_RaspberryPi3_v3.pdf">Setup Guide</a><br />- Output: IQaudIODAC: Direct hardware device without any conversions</p><p>&nbsp; &nbsp;In hindsight, this $51.33 audio card wasn&#039;t necessary. I did a test using the default 3.5mm headphone jack output on the Raspberry Pi and while the sound isn&#039;t as &quot;open&quot; and &quot;deep&quot;, the sound is similar and performance is identical. I had previously read that the default audio of the Raspberry Pi was horrible and would tie up the CPU. However it works, the result is that the default audio from the Pi without the sound card was very usable and even sounds good. It&#039;s just the audio from the sound card sounds better.</p><p>&nbsp; &nbsp;&quot;Direct hardware device without any conversions&quot; is important for performance.</p><p>- Sample rate: 96000 Hz<br />- Audio buffer size: 256 samples (2.7 ms)</p><p>&nbsp; &nbsp;If the buffer size is any smaller, audio crackles and dropouts start appearing. 2.7ms should be great for live performance, though I have yet to test this. Larger buffer sizes are not necessary (the smaller the better).</p><p>- Multicore rendering: MAX (from Edgar&#039;s guide)<br />- Internal sample rate: 24000&nbsp; Hz</p><p>&nbsp; &nbsp;24000 Hz was the highest usable internal sample rate. The next highest option (32000 Hz) caused even 10-note polyphony to peak the performance graph with scary red vertical lines and would cause audio dropouts to occasionally occur. But using 24000 Hz caused <em>zero</em> audio dropouts even at 98 note polyphony.</p><p>- Maximum polyphony: 256</p><p>&nbsp; &nbsp;I didn&#039;t want polyphony to be capped. This is the highest setting.</p><p>-----------------------------------------------------------------------------</p><p>Here&#039;s how I tried to stress Pianoteq, as the screenshots below show:</p><p>- Network: A 200 MB file download test is running (also separately did a 100 MB file upload test)<br />- Other Software Running: Chromium web browser with multiple tabs, Linux desktop (i.e. Pianoteq is not running headless), VNC server and viewer (my Raspberry Pi is not hooked up to a monitor so these screenshots were taking remotely over the VNC software)<br />- Song Playing: <br />&nbsp; &nbsp;- The most complicated section of Beethoven&#039;s symphony<br />&nbsp; &nbsp;- With the &quot;Cathedral&quot; hall for more revert effects (to stress the engine)<br />&nbsp; &nbsp;- With the sustain pedal depressed the entire time (to stress the engine)<br />&nbsp; &nbsp;- Getting up to 98 note polyphony</p><p>Basically, the computer was being lightly used, the network was being heavily used, and the piano passages being played represent some of the most complicated passages a person could would play.</p><p>And Pianoteq took it amazingly well. With the decreased internal sample rate, there were zero audio dropouts. This is incredibly exciting! While there are some red vertical lines in the performance index, there were no audible crackles, dropouts, or static. It sounded like a very good piano VST with excellent audio quality and performance.</p><p><span class="postimg"><img src="https://i.imgur.com/qM8oswD.png" alt="https://i.imgur.com/qM8oswD.png" title="https://i.imgur.com/qM8oswD.png"/></span><br /><span class="postimg"><img src="https://i.imgur.com/fmd2BmY.png" alt="https://i.imgur.com/fmd2BmY.png" title="https://i.imgur.com/fmd2BmY.png"/></span></p><p>-----------------------------------------------------------------------------</p><p>Note on Testing/Audio DAC: I haven&#039;t tried hooking this up to a MIDI keyboard yet. This test is just playing a MIDI file that is being loaded. I can give a more thorough report on performance latency delays later when I use this setup with a keyboard.</p>]]></description>
			<author><![CDATA[null@example.com (sightread)]]></author>
			<pubDate>Sun, 29 Sep 2019 07:55:21 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=962550#p962550</guid>
		</item>
	</channel>
</rss>
