Topic: Pianoteq's behavior with tuning files

Hello,

I notice that when I use a tuning file like the following pianoteq std 4 shrinks its playable keys towards the center of the keyboard. In cases like these it would be useful to have the option of forcing pianoteq to use all 88 keys even if it is not realistic. Is this possible? - perhaps I'm missing a setting?

Thanks,

Chris

!12-EDe.scl
!
!12 equal divisions of e.
12
!
1/1
144.26950
288.53901
432.80851
577.07802
721.34752
865.61702
1009.88653
1154.15603
1298.42554
1442.69504
1586.96454
1731.23405

Re: Pianoteq's behavior with tuning files

As I understand it, each instrument is limited to the range of frequencies it can produce. A scala file redistributes the intervals differently but for instance D4 with its extended range has more notes available than say Blüthner and even more than a range limited instrument like a celesta. When you exceed the range, keyboard notes are correspondingly grayed out. You can still transpose the keyboard of course but you can't get out of the range.

Re: Pianoteq's behavior with tuning files

Here's a scala file I use -

! lehman2.scl
!
Bradley Lehman Bach squiggle keyboard temperament II (2005)
12
!
98.04500
196.09000
298.04500
392.18000
501.95500
596.09000
698.04500
798.04500
894.13500
998.04500
1094.13500
2/1

It's very similar to yours, and to get it going, I need to have the alternate mode to the default selected (which you get by making as many clicks on the little Mu-button as it takes to get the two lines to toggle - this seems to be a bit reluctant  to 'take', at least on my system). Once toggled, I can select either 'default' or '88 notes' modes from the second line's dropdown menu to make that file run as  expected, all 88 notes showing and playable.

A big difference is the presence of a "1/1" preceding your 12 numbers list, and the replacement of my 12th number entry with a "2/1" instruction, which we can take to mean "use the octave of the 1st entry".

If you do these things (first mu-button 'take', then 'default' or '88-note' selected from the second line's dropdown menu), plus (if that doesn't work), edit your scala textfile to take out your "1/1" instruction and replace your 12th number with "2/1" as in mine, then drag and drop the result onto your Pianoteq GUI, the result should be equivalent to the result I get - 88 notes of keyboard.

Whether the results accord with what you expect (which you don't reveal) is another matter. The file I'm quoting delivers a particular tuning for the twelve tones in every octave. If that intent's the same as yours, all should be well.

ADDED: I see that if you divide your 1st entry into your 9th and 10th entries, you get near as dammit 10 and 11 respectively. Do the same with mine and the approximations are worse, but still close to 10 and 11. I know the tuning I'm using is somewhat quirky by design, which all suggests yours is much the same kind of berry, and more regular also.

Last edited by custral (15-09-2013 19:24)

Re: Pianoteq's behavior with tuning files

Gilles wrote:

As I understand it, each instrument is limited to the range of frequencies it can produce. A scala file redistributes the intervals differently but for instance D4 with its extended range has more notes available than say Blüthner and even more than a range limited instrument like a celesta. When you exceed the range, keyboard notes are correspondingly grayed out. You can still transpose the keyboard of course but you can't get out of the range.

Also on the subject, when I use the file Carlos Super Just, it adds an extra note for all pianos ending in A.