Best practice on creating new Instrumentation Codes

[Hubert Léveillé Gauvin]

Hello **HUGers,

I'm curious, how do you deal with instrument that do not have a "standard" Instrumentation Code, i.e. an instrument that does not appear in the Appendix II Instrumentation Codes list of the Humdrum Manual?

Do you  simply create a new code? Or is there a good way to indicate that the new code is "not standard"?

Any advice on best practice would be helpful.

Cheers!

-Hubert

[Craig Sapp]

Hi Hubert,

> Do you  simply create a new code? Or is there a good way to indicate that the new code is "not standard"?

The best way may be to post proposed instrument code(s) to **HUG, and then if there are no complaints or suggestions for alternate codes for the instrument(s), then they could be added to the official list:

https://www.humdrum.org/instrument-codes

In addition, I would propose a reference record, such as INS, to allow for encoding instrument code meanings within a file, particularly useful if it is not in the standard list:

!!!INS: mukr = mukkuri

See https://en.wikipedia.org/wiki/Mukkuri

Also note that if you want an instrument name to be displayed in notation, there are two interpretations for that.  To display a free-form name of the instrument at the start of a score:

*I"Mukkuri in Bb

And to display an instrument abbreviations at the start of each subsequent system:

*I'M. in Bb

[Note that instrument abbreviations are suppressed for single-instrument systems.]

This system works in Verovio Humdrum Viewer as well as the Humdrum Notation Plugin, which both use verovio to render the Humdrum data to music notation.

**kern
*ICww
*Imukr
*I"Mukkuri in Bb
*I'M. in Bb
*ITrd1c2
*clefG2
*k[b-e-]
=1
1B-
=2
1c
=3
1B
=3
1A
=
*-

-=+Craig

--
--
This is a message is from the **HUG newgroup.
To post to this group, send email to stars...@googlegroups.com
To unsubscribe from this group, send email to
starstarhug...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/starstarhug?hl=en
---
You received this message because you are subscribed to the Google Groups "starstarhug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to starstarhug...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/starstarhug/fa80d2cf-ffd4-43f2-9183-e40467243edbn%40googlegroups.com.

[Craig Sapp]

Related to this thread, I need the following instrument codes, so I am proposing adding these to the list at:
https://www.humdrum.org/instrument-codes/index.html


(1) *Iphysh == physharmonica

https://en.wikipedia.org/wiki/Physharmonica

(2) *Iophic  == ophicleide

https://en.wikipedia.org/wiki/Ophicleide

(3) *Iserp  == serpent

https://en.wikipedia.org/wiki/Serpent

Five letters is common for codes of longer instrument names, but the second "e" is a schwa (ə) so it would be superfluous, and adding the "n" or "t" seems unnecessary as well.

-=+Craig

[Hubert Léveillé Gauvin]

Hi Craig et al.,

The additions you are suggesting are sensible. I think the only thing is that we need to make sure to add them to the documentation (which you already did).

I'm currently working on a Sibelius plugin to export to Humdrum directly from Sibelius. I did an initial mapping of the instruments available in Sibelius to the existing Humdrum codes, but some new codes will likely need to be created. More on that later.

Cheers!

-Hubert

--
--
This is a message is from the **HUG newgroup.
To post to this group, send email to stars...@googlegroups.com
To unsubscribe from this group, send email to
starstarhug...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/starstarhug?hl=en
---
You received this message because you are subscribed to the Google Groups "starstarhug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to starstarhug...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/starstarhug/CAPcjuFfkyUkNMw1B8YXzEky8VdO7iX4KQykhRvsYAU9tJxOk1A%40mail.gmail.com.

[Craig Sapp]

Hello Hubert, et al.

That sounds interesting!

Related to this and in general, it would be good to create a Humdrum instrument code database, which I have just done:

http://bit.ly/humdrum-instrument-codes

This is a Google Spreadsheet for registering Humdrum instrument codes.  From this database, I can create the contents of the Humdrum documentation page:

     https://www.humdrum.org/instrument-codes/index.html

as well as add a search/sort features as well as target a specific language for the lists, etc.

If anyone wants to help in filling out the database, you can email me to be added as an editor of the spreadsheet.  I have put all of the information from the webpage in already, but other niceties such as filling in the instrument names in other languages (or adding new language columns) as well as links to the instruments in Wikipedia (in various languages as well could be done. (Hint: you will be able to add your own codes if you are an editor of the Instrument codes spreadsheet.)

The Humdrum documentation can be setup to dynamically update when there are changes to this spreadsheet.  In addition, I have created links to export the data in various formats:

JSON: https://script.google.com/macros/s/AKfycbxtpzIBumhXjNd30fsWuFdsBco2EqrezXMsUxQ2lrylvwls1AMyI7MuLrW3qRh6_HDp/exec?format=json

ATON (analogous to JSON, but allow for embedding comments, see https://aton.sapp.org):

https://script.google.com/macros/s/AKfycbxtpzIBumhXjNd30fsWuFdsBco2EqrezXMsUxQ2lrylvwls1AMyI7MuLrW3qRh6_HDp/exec?format=aton

TSV (Tab separated values):
https://script.google.com/macros/s/AKfycbxtpzIBumhXjNd30fsWuFdsBco2EqrezXMsUxQ2lrylvwls1AMyI7MuLrW3qRh6_HDp/exec?format=tsv

Humdrum:
https://script.google.com/macros/s/AKfycbxtpzIBumhXjNd30fsWuFdsBco2EqrezXMsUxQ2lrylvwls1AMyI7MuLrW3qRh6_HDp/exec?format=humdrum

-=+Craig

[Joe Plazak]

Hello all,

I’d be happy to help scrape some strings from Sibelius to assist with this effort.  We have some pretty wild entries. Sibelius is translated into 9 languages, yet by convention, many of these languages opt to just use English names for certain instruments. 

I’ll sync up with Hubert. Thanks for streamlining the process, Craig!

All best,

Joe

On Jan 30, 2022, at 5:40 PM, Craig Sapp <crai...@gmail.com> wrote:



--

--
This is a message is from the **HUG newgroup.
To post to this group, send email to stars...@googlegroups.com
To unsubscribe from this group, send email to
starstarhug...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/starstarhug?hl=en
---
You received this message because you are subscribed to the Google Groups "starstarhug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to starstarhug...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/starstarhug/CAPcjuFdrq7hVnFrPtu3Y2buFEj%2BVPz6b6ku6gwaubF3mjz9V3Q%40mail.gmail.com.

[Craig Sapp]

Hi Everyone,

I have hooked up the Humdrum Instrument Code spreadsheet:

     http://bit.ly/humdrum-instrument-codes

to the instrument code documentation page:

    https://www.humdrum.org/instrument-codes

When you load that page, the instrument code tables on the page are generated dynamically from the spreadsheet data.

-=+Craig