Moonsound Music Editor and Replayer Using only Samples

Indeed there is a mapping from the instrument to a specifc 'region' i.e. per range of notes there is another region of an instrument to be played (to overcome the samples are stretched too much from very low to very high frequencies). The file mentioned in the linux driver provides the table to perform this mapping, based on instrument number and note number.
The first and second value on every line indicates the range of note numbers it is applicable to, the region table name itself is the number of the GM instrument.

Thanx !

This makes implementing these instruments in a DAW even more complicated.
Not only do I need to add several samples per instrument. I also need to convert them to their own unique frequency in my replayer... Wow.

Well... it's keeping me busy

Another thing I noticed is when outing values to the moonsound registers, I should not out too fast... Is that correct ?
I found nops in between out instructions in the original code:

  ld    a,b                   ;channel number
  add   a,$20                 ;register number
  out   (pcm_reg),a           ;frequency
  inc   de                    ;f-number, octave
  ld    a,(de)
  nop
  nop
  out   (pcm_data),a

How much time exactly do I need to wait between out instructions ?
I was wondering for instance if this code would be viable on a real msx (it works in an emulator)

  ld    c,pcm_data
  ld    a,(hl)                ;register number
  out   (pcm_reg),a
  inc   hl                     ;data
  outi

I found this in the Moonsound manual:

But how do i translate this to Tstates ?
A nop instruction for instance takes 1 M cycle and 4 Tstates (4 MHz E.T. = 1 ??) according to the z80 manual.

And then you put your Z80 in turbo mode (Z80B) and...
All that about timmings are a pain in the *ss, having the CPU a WAIT pin, and the MSX slot also a WAIT signal, too bad it's never used by any device. The software itself should not care about those matters and more in a multi-configuration environment, like the MSX is.
The only solution I see is to standardize things. Collaborative drivers and sources prepared for all machines, but made once, then anyone who require it would get from there, updated and fixed at that moment.