SFZ Import - read note names as well as note numbers

[DarkStar]

I have many SFZ definition files where the note range and root key are specified using note names rather than note numbers.

Can TX16Wx have the ability to process note names (adjusting for the Octave Display offset) as well as the numbers?

Here's an example.
... Big pic: http://i.imgur.com/oDdSwSR.png

Currently, TX16Wx is :
(a) reading the root key from the data embedded in the sample (not from the SFZ definition)
(b) reading numeric lokey, hikey and pitch_keycenter values from the SFZ definition

-------------------------------------
As a related question: given that the root key info may be embedded in the sample metadata, is there a way to drag several samples at once into the Key Mapper and for each sample to be mapped to its root key and to that key only? At the moment there is a lot of extra editing, dragging etc to achieve this.

[EvilDragon]

From the "Teasing" thread:

* Optional sample name parsing when loading/mapping

Should hopefully solve it, I guess?

[elcallio]

I have many SFZ definition files where the note range and root key are specified using note names rather than note numbers.

Can TX16Wx have the ability to process note names (adjusting for the Octave Display offset) as well as the numbers?

Here's an example.
... Big pic: http://i.imgur.com/oDdSwSR.png

Currently, TX16Wx is :
(a) reading the root key from the data embedded in the sample (not from the SFZ definition)
(b) reading numeric lokey, hikey and pitch_keycenter values from the SFZ definition

-------------------------------------
As a related question: given that the root key info may be embedded in the sample metadata, is there a way to drag several samples at once into the Key Mapper and for each sample to be mapped to its root key and to that key only? At the moment there is a lot of extra editing, dragging etc to achieve this.

Root keys are currently always taken from the wave file. A non-destructive root key override is planned for later. But reading notes by name should work for all note fields (though the octave offset is _not_ taken into account - truly, that would not make much sense... its after all not related to external material)
I.e lo/hi key at the very least should parse fine. If it does not, please send me the offending file.
Cheers
/C

[elcallio]

From the "Teasing" thread:

* Optional sample name parsing when loading/mapping

Should hopefully solve it, I guess?

No, different feature. And see my reply above.

[DarkStar]

Oops, user error

I had a space in the definitions

Code: Select all

<region> sample=Samples\BassArcoDn A#0.wav
    lokey= A#0 hikey= A#0 pitch_keycenter= A#0 lovel=1 hivel=97

and it should be:

Code: Select all

<region> sample=Samples\BassArcoDn A#0.wav
    lokey=A#0 hikey=A#0 pitch_keycenter=A#0 lovel=1 hivel=97

So the SFZ import looks a lot better.

---------------
Now, any thoughts on my related question above?