Can mute trumpet but not unmute it
In the score I'm working on, I used the "mute" text given in the Text section of the Advanced palette, which works like this page to mute a few trumpet parts. However, even when I have applied the "open" text, and ensured that a voice is actually selected to change back to normal, the trumpets remain muted for the rest of the score.
This issue persists upon deletion and reapplication of the offending "mute" and "open" text. I have a double bass part with arco and pizzicato notations in the score as well, and those are not affected by this issue (i.e. pizz and arco switches work as expected).
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.4.5763, revision: cda4080
Comments
Can you take a screen shot of the mixer that shows the trumpet. Make sure you have clicked the arrow in the top left corner of the trumpet volume box so we can see the sounds assigned to both the normal and muted trumpets.
In reply to Can you take a screen shot… by mike320
Is this what you meant?
In case this is particularly what you're looking for, the "normal" channel is MIDI port 1, channel 3, using the "Trumpet" patch. The "muted channel" is port 1, channel 16, using the "Harmon Mute Trumpet" patch.
In reply to Is this what you meant? In… by techieboy45
If you entered the "Open" text correctly, then you should have an open trumpet playing since you have the correct instrument in the mixer. There must be something else going on where we'd need to see your score.
In reply to Is this what you meant? In… by techieboy45
Looks like maybe this score was created in 2.x? I see the first channel for trumpet is called "normal" rther than "open"; that is probably why the "open" isn't working. To fix, just use right-click / Staff Properties / Change Instrument to change the instrument to trumpet - this will update the info.
In reply to Looks like maybe this score… by Marc Sabatella
This was the last thing I looked at before I went to bed last night and almost woke up to see if this was created in version 2 and the open trumpet had a normal channel.
In reply to This was the last thing I… by mike320
Or change that text's channel assignment to 'normal'
In reply to Or change that text's… by Jojo-Schmitz
Updating the instrument is easier, especially if there are (or will be) multiple mute/open texts. They get fixed all at once that way.
In reply to Looks like maybe this score… by Marc Sabatella
Just woke up recently, sorry. Did this and it fixed the issue -- thanks!
For reference, though, it appears that simply placing the text (i.e. double clicking a note and then double clicking "mute" or "open") does not automatically change the patch -- it appears that one needs to right-click on the text, go to "Staff Text Properties", and hit OK before the patch change will actually take effect. I don't know if this is intended behavior or not.
In reply to Just woke up recently, sorry… by techieboy45
What you describe is what I've always done since 2.x.
In reply to What you describe is what I… by mike320
Indeed that was the way to go prior to addition of those tests to the palette and the corresponding channel name changes for the affected instruments
In reply to Just woke up recently, sorry… by techieboy45
If your score was createds in 3.0 or if you do the instrument change as suggested here, then staff text properties are not needed - the palette texts work right away.
If you continue to have trouble, please attach your score so we can understand and assist better. I just tried it and it worked fine for me.
In reply to If you continue to have… by Marc Sabatella
If the thread with mike320 doesn't end up resolving things, I'll upload it here. Disclaimer: There are a bunch of formatting issues related to upgrading from 2.x to 3.x, and I'm tempted to manually copy it into a new score as is.
In reply to If you continue to have… by Marc Sabatella
When you used the staff text, to get the change between the muted to open trumpet sound, Did you check the MIDI action panel values???
Maybe (I'm just guessing), you use the muted sound into the voice 1 (let's say), and the open sound into the voice 2. But... You wanted to get the open sound into the voice 1, so... The change will be present only into the voice 2 (which is not your desire).
In reply to When you used the staff text… by jotape1960
All sounds are in voice 1. Since the patch change usually works, I never bother with putting different sound effects into different voices.
In reply to All sounds are in voice 1… by techieboy45
Weird!!!
Those changes work so fine to me. I use MuseScore 3.0.4 in UbuntuStudio 18.04.2 LTS (64 bit Linux).
I don't know what to say. Sorry!!!
In reply to All sounds are in voice 1… by techieboy45
Oh!!!
Now I can see your problem!!!
Definitively, it seems to be a bug.
When I used the "Mute" and "Open" text... The muted sound was still present ("Open" doesn't work).
BUT... When I used "Staff text", and I use the "Mute" in the "Staff panel properties", and then I used the "Normal" (in the same panel)... I got the full change!!!
So... The muted trumpet sound and open trumpet sound full control works fine using "Staff text", only.
In reply to Oh!!! Now I can see your… by jotape1960
Open works fine for me in a score created in 3.0. For a score created in 2.x, you will need to first change the instrument back to trumpet in order to get the new naming of the channels.
In reply to Open works fine for me in a… by Marc Sabatella
Very weird!!!
I'm using MuseScore 3.0.4 rev. cda4080, in Ubuntu Studio 18.04.2 LTS (64 bit Linux).
Yesterday, it doesn't work. Today... It works!!!
I adjust a file to test this. this file is made "from the scratch".
Maybe, it is about the kind of instrument we chose originally to some specific staff... Maybe.
In reply to Open works fine for me in a… by Marc Sabatella
I tested 10 different scores. Two of them created, from the scratch, with MuseScore 3.0.4. The others were created with MuseScore 2.3.2.
The "Open" and "Mute" text commands work so fine with the scores created from the scratch, but don't work with the others (if you mute the trumpet, the "Open" command doesn't work).
Of course, the "Staff text" command works every time to fix this, but... I guess there is some kind of bug here.
In reply to I tested 10 different scores… by jotape1960
See my previous comments. This is a known result of the change in the name of the channel from Normal in 2.x to Open in 3.0.
In reply to See my previous comments. … by Marc Sabatella
But... Isn't it something MuseScore should do automatically, when we change the staff properties???
In reply to But... Isn't it something… by jotape1960
Not sure what you mean. Again, for scores created in 3.0, you don't need to touch staff text properties. Only scores imported from 2.x need an extra step. You can either use staff text properties once for every time you want to add "open", or can use change instrument once for the entire score and it's done forever. Your choice :-)
In reply to But... Isn't it something… by jotape1960
If changing staff properties involves change instrument, your good to go. Else you're not.