The bug is fixed. You need to download both the new engine 5.5.1 and the new KIViR.ptq file from the user area.

Thank you, Philippe. You and your team are amazing. Look forward to trying out the updated version.

You may even want to challenge yourself with a completely reversed keyboard: reverse.kbd

Download from above or create a .kbm file by yourself by copy-paste:

I found it on this forum sometime ago, sorry, don't remember who posted it.

Also the pitch upon hitting the note and the fall in pitch upon release is independent of key velocity. When you strike a clavichord key harder, the initial pitch should go up because the string is being stretched more as it's being struck.

Well, this is a bug; Stevely, it seems you are very good at finding them . It will be fixed in the next release (coming very soon).

I must say I don't like how the pitch droops when one releases the key (for the lowest several notes). The clavichord my spouse had was a lot more stable w.r.t. pitch (sold to a student a coulple of weeks ago, unfortunately; but it'll get played a lot more, so it's a good thing really). Also the pitch upon hitting the note and the fall in pitch upon release is independent of key velocity. When you strike a clavichord key harder, the initial pitch should go up because the string is being stretched more as it's being struck.

Anyway, these are shortcomings of the Neupert physical model in Ptq. Your kbd file code is perfect, and it's nice that it's just human readable text. Thanks again!

[Edit] The Files section here doesn't accept .kbm files, but again it's a really simple format, just a plain text file with the .kbm filename extension. Here's a short-octave mapping, with unused keys disabled. Just copy the entire contents of the code box below, save it in plain text format as short-octave.kbm (or whatever you'd like to call it), and load it into PT. There might be a more efficient way to map this; again I'm new to Scala. But it's not a repeating pattern so this is what I came up with.

! short-octave.kbm
! Size of map:
128
! First MIDI note number to retune:
0
! Last MIDI note number to retune:
127
! Middle note where the first entry in the mapping is mapped to:
0
! Reference note for which frequency is given:
60
! Frequency to tune the above note to (floating point e.g. 440.0):
261.625565
! Scale degree to consider as formal octave:
12
! Mapping.
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
0
5
2
7
4
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x

But maybe I need to look at what can be done with Scala files.

2. You could use the scale/tuning feature for this.

Q1. Is there a way to limit the range of notes, as is done by default e.g. for Church Bells, Cimbalom (as well as some other instruments in the KIViR collection)? That is, I want to disable notes/keys below and above a certain point (or individual keys). (I realise that I could turn the volume setting right down but it'd be preferable to explicitly disable keys.)

Q2. Can one reassign notes to different keys or can this only be done by detuning?

Practical application of this is, e.g., to model a short-octave tuned clavichord.