Menu

#34 scala kbm file import: Yoshimi ignores "A" Freq, "A" Note and Middle note values

Done
closed
None
5
2018-02-05
2018-02-03
yubatake
No

When importing a scala kbm file, Yoshimi will correctly configure the Keyboard Mapping (right pane) but ignore information in the file which should go in the "A" Freq, "A" Note and Middle note boxes.

Steps to reproduce

  • Scales > Show Settings > Enable Microtonal > Keyboard mapping ON
  • set "Middle note" to something other than 60
  • via "Import .kbm file" button, import the attached two17.kbm (downloaded from the scala site)

two17.kbm has a map size of 24; Yoshimi's Map Size, and the values in Keyboard Mapping (right pane) will correctly reflect the information in the kbm. However, the following issues are observed.

1) two17.kbm has a middle note of 60, but Yoshimi's Middle Note will remain as that set before importing the kbm
2) two17.kbm has a reference note of 60, but Yoshimi's "A" Note will remain on 69
3) two17.kbm has a frequency of 261.6256, but Yoshimi's "A" Freq will remain on 440

From what I can make out, the above is how things "should" work, but please correct me if I'm wrong (there's every chance I've misunderstood something).

FYI, I'm running the latest git version (1.5.6 M) and have tested this with both standalone and LV2 Yoshimi (in Qtractor).

Finally, this issue is likely not that important for most people and it's easy to work around, so there's no rush to investigate. I just wanted to let you know.

1 Attachments

Discussion

  • Will Godfrey

    Will Godfrey - 2018-02-03
    • status: open --> pending
    • assigned_to: Will Godfrey
    • Group: Unknown --> Next Commit
     
  • Will Godfrey

    Will Godfrey - 2018-02-03

    Ok confirmed here.
    It's not quite as bad as it seems. The file is correctly loaded and initialised. It just doesn't update the GUI :(

     
  • Will Godfrey

    Will Godfrey - 2018-02-04

    This has now been fixed (build number 1243)

     
  • Will Godfrey

    Will Godfrey - 2018-02-04
    • status: pending --> closed
    • Group: Next Commit --> Done
     
  • yubatake

    yubatake - 2018-02-05

    Just tested in the latest build and all looks good. Thanks very much for the swift response :-)

     

Log in to post a comment.

MongoDB Logo MongoDB