Pianoteq 7

Software
1

Hi,
I just see that Moddart team release Pianoteq 7 : https://www.modartt.com/pianoteq#overview , the cost to upgrade is 29€

It does not install on Zynthian, I will take a look later.
The structure in the 7z file is not the same.
structure

2

Interesting! I am planning to buy this for Christmas so a new version may be good but… the modelling enhancement may increase resource requirements so it will be good to get the demo working so we can assess our on Pi 4. Note that some new features are only available with Standard and Pro, the more expensive versions.

3

I saw this news too. Usually it’s great if software gets updated. For Zynthian, there are a lot of unknowns, so I am sticking with Pianoteq 6 for now. :slight_smile:

4

/zynthian/zynthian-sys/scripts/recipes/install_pianoteq_binary.sh /tmp/pianoteq_linux_trial_v701.7z’ returned non-zero exit status 1.

ln: failed to create symbolic link ‘/zynthian/zynthian-plugins/lv2/*.lv2’: File exists

in the install recipe, the /arm needs to be replaced by /arm-32bit

Then it installs and existing snapshots work.
BUT

  • We are still using pianoteq6 as folder. We should discuss this, @jofemodo, before we change the recipe
  • Zynthian-ui doesnt show the Engine in the Layers…investigating…
  • Is it ok, that in data, there is a Pianoteq 6 Stage.lv2 folder? And no other lv2 folder
5

@jofemodo
The Pianoteq 7 Layer shows, when I Remove All Layers.
But as soon as I select it and go back, the Pianoteq option is gone.
When I select a FluidSynth or any other, Pianoteq is still there.
The Log doesn’t show anything suspicious.
Where should I insert more log messages?

6

I committed something, so that you can play with version 7.
But the described error exists…But it existed when I used the latest 6 as well.
So could somebody please confirm, that the Pianoteq engine disappears from the Layers list, once you created a Layer…and removed it.
@jofemodo, I think it has something to do with removing it from list, once the first one is created, so that only one PT layer exists.
But you need to free it up when the layer is removed. (and not only with RemoveAll)

7

Hi @mheidt!

Thanks for the fix to the install script. I also think we should change the directory name. I will do ASAP.

I can’t reproduce the problem with Pianoteq6. I’ve not tested with PT7 yet …
Please, could you describe the exact steps for getting the issue?

THanks!

8

Ah, you mustn’t create a PT layer and remove it but try to create a PT layer.

  • empty layers
  • click on PT
  • In MIDI channel view, go back to LAYERS
  • Click New Layers, PT is gone

When you select the MIDI Channel, the layer is created and when removing it, everything is ok.

1 Like
9

OK! I understand …
Please, could you create an issue with this? I will solve it ASAP …

10
11

Will Pianoteq update automatically when you have fixed the hiccups?

12

You have to upload the binary yourself.
It doesn’t download the latest version from the modartt site.
The hiccup doesn’t seem to be that relevant.
It only appears when you press the Back button in the Midi channel selection view.

3 Likes
13

there is an entry in the FAQ on https://www.modartt.com/faq?category=pianoteq_troubleshooting:

I cannot activate Pianoteq 7 on Raspberry Pi.
- Make sure you have installed update 7.0.2 or later.

14

Release notes show the arm fix in 7.0.2. Also note 32-bit support in Windows & MacOS is dropped.

I read a user comment that code changes appear to improve resource efficiency:

Additionally, physical model improvements appear to come with greater efficiency on an engine resource, since I can now lower its Audio buffer size without it incurring normally crackles and spikes.

This is not from Mordatt and not arm specific but might be a good sign for us. I will run benchmark comparison when we have 7 working.

15

phew, 7.0.3 still has the same directory structure…

16

Hi,
I make modification to get the new instrument of V7 Steinway grand D New York and Steinway Grand D Hamburg

I make the modification directly on the web editor on github, normally same as my local zynthian

1 Like
17

@jofemodo, could you confirm the pull request? I can’t

18

It’s confirmed!

19

Is there a plan to update to PT7 or allow user to do so (with instructions)?

20

Bad new on the resource front - Pianoteq 7 is more hungry than Pianoteq 6. I did not run the benchmarking I have done before but I did a simple manual test:

  • Stop Zynthian
  • Stop Jack
  • Start Pianoteq with no preferences
  • Configure to use ALSA, 44100, 128 sample buffer, internal samplerate 44100
  • Play whilst observing performance and hearing xruns

PT6 can play 48 notes simultaneously without xruns. PT7 starts to xrun around 32 notes.

Obviously this is pusing the configuration for Raspberry Pi - Zynthian configures Pianoteq to use half samplerate internally (e.g. 22050) and JACK is usually configured with larger buffers but I wanted to see how the two compare.

I also found using the UI via X-forwarding very slow to the point of unusable and had to resort to HDMI output to test.

This is a shame and a bit of a worry that Raspberry Pi may struggle to match the release cadence of Pianoteq, i.e. PT uses more resources faster than Raspberry Pi increases physical resources.

When I find time I will run the JACK based benchmark to see how PT 7 fares. It will probably be fine for most uses but be warned that PT 6 may provide a more stable experience.

[Edit] I played some more with PT6 without Zynthian or Jack but with 64 frames per period at 48000 samples power second (1.3ms latency) and it was quite good. Too much sustain pedal or effects will push it over the edge but for most playing it is fine

1 Like