-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MU4 Issue] Drumset not yet mapped in Muse Sounds #14016
Comments
It would also be nice to have one of these for an orchestral percussion staff so we don't have to split the percussion staves per sound |
I suggest to keep a single issue with MuseSounds mappings, otherwise it'd be hard to collect scattered info |
I think the drumset is unique though. We need to agree on mappings before plugging in the new drumkit sounds. Any other 'missing instrument' mapping should be kept together though. I agree with that. I have one document outlining all the incorrect mappings so far, so I can keep track. |
I would agree the “orchestral percussion” instrument mapping is way more important than the “drumset” instrument. The latter really isn’t a good fit for Muse Sounds even if the available sounds map decently. |
We are going to postpone this for now because we don't have all the available sounds we need for the drum kit in Muse Sounds. |
@bkunda are there any plans to do a general "orchestral percussion" sound set for combined staves? |
@erinic04 Unfortunately I don't think this is going to be possible for the 4.0 release because we don't yet have the full complement of instrument sounds in Muse Sounds. But this is certainly something we'll want to tackle as soon as we can :-) |
Cool thanks :) |
Hi there, now 4.0 is released, is this still a planned feature? I currently have a score for drum kit that has to be on MS Basic as there's no combined Muse Sounds equivalent (just individual sounds for kick, snare etc under percussion). Would love for it to have the full 4.0 sound without splitting each drum into separate parts. Thanks, Graham |
Yes, this is still going to happen! Not sure yet when, though. |
I was trying to use the Drum Kit (which is available now in MuseSounds) in a score and found that I cannot alter the placement and look of the notes without this effecting the sound being played. This also happens when using the Drum Kit available in the CinePerc samples but effect is slightly different. For instance, I don't want the hi-hat to be placed above the staff but instead I would like it to show between the two top staff lines and also want to show this with a normal notehead (not a cross). After altering the Drum Set definition, the notes are placed as desired but the sound has changed from hi-hat to bass drum. Seems changing the notehead type is effect the sound. Not sure where I should report this issue and found this one on github which related to mapping drumset, hence I added my comment here. If a separate issue for this is preferred, let me know. FYI, I am using MS 4.3.2 + MuseHub 2.0.15.1305. |
@henkdegroot, please describe the exact process you used. Were there notes in the score before you changed sound in the Mixer? Did you change notation via the Edit Drumset dialog? Did you edit the appearance an existing pitch in that dialog (which pitch was it?) or did you create a new pitch and define notation for it? |
Here are steps:
Obvious it is not common to use a normal notehead for a hi-hat but when I enter a drumpart from an existsing paperscore, I normally like to keep the same notation as the original. At first I thought moving the note to a different staff line caused the sound to change, later I discovered it was the notehead changed which caused this. |
Describe the bug
The Drumset instrument does not seem to map to anything in Muse Sounds.
To Reproduce
Expected behavior
MS Basic contains 25 different instrument sounds within the Drumset instrument. Where these are available in Muse Sounds, they should be mapped accordingly (see relevant noteheads below):
Platform information
@Tantacrul FYI
The text was updated successfully, but these errors were encountered: