Skip to content

Fix #24075 (second part): members of the castilian dulzaina instrument pitched in different key: F and G#33740

Open
pacebes wants to merge 1 commit into
musescore:mainfrom
pacebes:24075-NewInstrumentCastilianDulzaina_InF_InG_WithOboeSoundFont
Open

Fix #24075 (second part): members of the castilian dulzaina instrument pitched in different key: F and G#33740
pacebes wants to merge 1 commit into
musescore:mainfrom
pacebes:24075-NewInstrumentCastilianDulzaina_InF_InG_WithOboeSoundFont

Conversation

@pacebes

@pacebes pacebes commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Resolves: #24075 (second part )

This second PR adds two new members of the Castilian dulzaina instrument with different pitches: F and G

Changes:

  • New "castilian dulzaina in F (quite uncommon)
  • New "castilian dulzaina in G (less common than castilian dulzaina in F#)
  • Pitch range for castilian dulzaina in F# (PR) has been changed to a more realistic values
  • I signed the CLA
  • The title of the PR describes the problem it addresses
  • Each commit's message describes its purpose and effects, and references the issue it resolves
  • If changes are extensive, there is a sequence of easily reviewable commits
  • The code in the PR follows the coding rules
  • There are no unnecessary changes
  • The code compiles and runs on my machine, preferably after each commit individually
  • I created a unit test or vtest to verify the changes I made (if applicable)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support a new woodwind instrument: Castilian Dulzaina

3 participants