First of all I want to thank Modartt for this great update! At the moment I have one question: Why do you call the MIDI name "Juce Midi Input" in Pianoteq 4? Why not "Pianoteq Midi Input" as in version 3.x?
This name appears in qjackctl or when I perform 'pmidi -l' (Linux 64 bit).
Hi Moby,
This is a detail we overlooked, it is fixed in the 4.0.1 update released yesterday.
Julien, what exactly was fixed in 4.0.1.? I don't particularly like when vendors say "various little fixes" in the changelog... I love detailed changelogs, like those Cockos does (the masterminds behind Reaper).
Ok I have edited http://www.pianoteq.com/pianoteq_changes -- I'll try to avoid "various fixes" in the future
Thanks, Julien, and sorry if it's bothersome!
Hi Julien,
thanks for the correction. However, in 4.0.1 I still see "Juce" as MIDI port name:
4.0.1:
markus@markus-laptop:~$ pmidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
131:0 Pianoteq Midi Input Juce Midi In Port
3.6.6:
markus@markus-laptop:~$ pmidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
131:0 Pianoteq Midi Input Pianoteq Midi In Port
Sorry, I do not like it to be pedantic. But perhaps you want to see "Pianoteq" in the MIDI port name as well.
Just for information: I have Python script running in the background. It waits for controller events from the buttons and the knob on my NI Audio Kontrol 1. And if Pianoteq is opened, the script sends MIDI program change events to Pianoteq. The script scans the available port names here, of course.
Thanks, I noticed that a bit late. Pianoteq 4.0.2 will have the correct naming also on the the port name -- same name as it was in version 3.