Musescore for banjo

[Jody Stecher]

Does anyone know how put the  "flag" on G to indicate the open  5th string when using Musescore 4?

[Jody Stecher]

I got it to work. To get rid of the rest I have to select and click x.  

thanks. It looks good now and didn't take too long.  

Jody Stecher said:

I'm using a Mac. And I updated today. I'll keep trying.

Trapdoor2 said:

Me too. Are you using a Mac? I'm Windows based. According to the handbook, it shouldn't make any difference though.

There have been multiple updates lately and some have been buggy. Check that you have the latest update.

[Trapdoor2]

Great! Lots of subtle differences between commands in Windoze and Mac. The handbook is always way behind the latest updates.

[Jody Stecher]

Thank you ! I couldn't have done it without your help.

Trapdoor2 said:

Great! Lots of subtle differences between commands in Windoze and Mac. The handbook is always way behind the latest updates.

[Jody Stecher]

Chaos returned. I almost have gotten it back. I can still get rid of the rests via a right click command but v no longer bizarrely moves the rests to the right. Now it makes them pale. 

[Banjowaif]

The pale rest will not be visible on a printed out or pdf version. At least that's what happens on my computer

[Trapdoor2]

They should go pale.

You don't want to delete them, just make them pale. If you delete them it causes chaos in the software, the gremlin that counts rhythm gets the hiccups and eventually weird things happen on the following measures ..

[Jody Stecher]

Oh!  How strange to design this so that it looks ok printed or as pdf but not when viewed on Musescore itself.

Banjowaif said:

The pale rest will not be visible on a printed out or pdf version. At least that's what happens on my computer

[Jody Stecher]

Yes that chaos issued, and not only in the software. Also in my poor little brain.  It *should* go pale!  Perhaps I will discover a use for this.

Trapdoor2 said:

They should go pale.

You don't want to delete them, just make them pale. If you delete them it causes chaos in the software, the gremlin that counts rhythm gets the hiccups and eventually weird things happen on the following measures ..

[Trapdoor2]

Musescore wants you to see you've made an object "invisible"...but that it still exists and is working with the system. Early on (version 2 or something like that) I could put a 5th string flag in the very last measure and the gremlin would fill every preceding measure with whole measure rests...which I attempted to delete (not knowing I was causing problems). I lost a whole score to chaos and had to re-enter everything.

Every little thing you put on the page is used by the software. Adding a new voice to create a 5th string note is like adding a choral voice that only sings one note. Its sheet would be solid rests until that note is needed. Musescore hides all that from you (thankfully) and only needs to use visible (pale or solid) rests in the measure where you use it. When you make it pale, you're just telling the software that you don't want to see it on the printout.

I use this a lot. I like to hear the music thru the computer, so I input metrognome settings and other stuff that doesn't exist in the original and then just make them pale so they don't print out. When I'm doing a Morley piece, "Moderato" is often way too slow for "The Lightning Player", so I may boost it to "Presto" but then hide (pale) that tempo for the printout.

It is a very powerful and complicated software. There are many parts I've never used...and you can customize just about every aspect. OTOH, it was never made to do some things like they did in the 19th cent. I've been lobbying for a special 5th string flag for years. One little button...boop! Add a double-flag to any note. I'm not smart enough to create a custom button.

[Jody Stecher]

Thanks. It does help when I understand the underlying reasons.  

Trapdoor2 said:

Musescore wants you to see you've made an object "invisible"...but that it still exists and is working with the system. Early on (version 2 or something like that) I could put a 5th string flag in the very last measure and the gremlin would fill every preceding measure with whole measure rests...which I attempted to delete (not knowing I was causing problems). I lost a whole score to chaos and had to re-enter everything.

Every little thing you put on the page is used by the software. Adding a new voice to create a 5th string note is like adding a choral voice that only sings one note. Its sheet would be solid rests until that note is needed. Musescore hides all that from you (thankfully) and only needs to use visible (pale or solid) rests in the measure where you use it. When you make it pale, you're just telling the software that you don't want to see it on the printout.

I use this a lot. I like to hear the music thru the computer, so I input metrognome settings and other stuff that doesn't exist in the original and then just make them pale so they don't print out. When I'm doing a Morley piece, "Moderato" is often way too slow for "The Lightning Player", so I may boost it to "Presto" but then hide (pale) that tempo for the printout.