Alternating e.g. flute and piano
I want to use musescore for instruction documents and notes, but I cannot find any way to e.g. write some text, then have a single treble cleff passage (say flute), then write some text, and then insert piano (both clefs) write some text and then have single cleff flute again..
If I try to do that then everything is converted to piano or single cleff.
How can I alternate between different instruments on the same page and same document?
I dont want to always have to use the entire score.
Comments
If you're trying to make like an example sheet or like a print our Word document. you could export each part thats between the texts as a PDF and cut out just the staff and use a word processing program to organize the text and staffs.
In reply to If you're trying to make like by SmokinLettuce
Thanks for the reply,
No it all needs to be in the same document as the parts needs to be played with musescore. If I neded a printable document I would use MusiXTeX, which is enormously powerful and anactual book or journal typesetting program. I need to have a playable (playback) document and that is why I am using musescore, but I seem to have hit a brick wall with this simple and obvious technical aspect.
e.g
Bla bla bla bla text ad lib
SINGLE CLEFF e.g FLUITE
More bla bla bla text ad lib.
Standard Piano, treble and bass cleff.
or other instruments
Bla bla bla text ad lib.
Bassoon or Cello in Tenor Cleff.
And so forth.
How do you do this in Musescore ?
In reply to Thanks for the reply, No it by retnev
Well as far as I know, Musescore is a music composition and notation software. I don't believe what you're trying to do is something that its intended for. You could try adding massive spaces between staffs and inserting the texting in those gaps.
In reply to Thanks for the reply, No it by retnev
Add all instruments, separate systems by text frames for your text, put in the notes, 'Hide empty staves', put in your text
In reply to Add all instruments, separate by Jojo-Schmitz
Thanks Jojo, I will try this.
In reply to Add all instruments, separate by Jojo-Schmitz
Jojo, I tried that and it works great, thanks a million!
In reply to Thanks for the reply, No it by retnev
As mentioned above, "Hide empty staves" will allow you to do what you want.
However, as mentioned, MuseScore isn't really intended as a full featured document creation system the way TeX is, so if you are trying to put together a textbook or similar document, you will soon realize there are far more serious limitations for that purpose.
I have similar wishes - a textbook where you can hear the examples played back or otherwise interact with them - and that is one reason I created the MsueScore Example Manager for LibreOffice. This allows musical examples to be easily inserted into text documents with a link back to the original file, so that a Ctrl+click of the example in the text document will load the corresponding score into MuseScore. This allows not just playback but also editing (for easy updates while developing your textbook) or browsing the note by note with a screenreader (a useful way for visually impaired users to read the score). If you really *just* wanted playback, you could tweak the code to link an audio file instead.
Ultimately, this is something that feels like it should be a standard feature of word processing programs - a way to embed objects from other programs in a way that displays visually in the document and can be printed, but can also be interacted with in ways specific to the object type using the program that created it (or a compatible program). Seems like a no-brainer thing that would be a normal part of the range of products provided for the visually-impaired, but apparently it just isn't. So blind readers of, say, electronic geography textbooks just come to a black hole every time a map appears, rather than being popped into some program that allows them to browse the map meaningfully. Same for most other forms of graphics. It's something I'd very much like to see addressed, but it's obviously a much bigger issue than MuseScore. And I realize your concern may have nothing to do with blind users. Still, that may turn out to be the driving force behind the technology that might eventually be good for your application as well.
Once upon a time there was something called OLE - object linking and embedding. this was Microsoft's solution to this problem. Seems to be largely dead now though.
In reply to As mentioned above, "Hide by Marc Sabatella
The issue is not the text. that I do without problem. I have lots of printed music that doesnt only have Grand Staff throughout, but has sections with only treble cleff.
Since this mixture exists in printed music, musescore is behind the curve here and has nothing to do with creating a text document.
There will be a huge increase in musescore users if it can be used as a live teaching document. All that is needed is to be able to add any type of staff .
In reply to The issue is not the text. by retnev
thanks
In reply to The issue is not the text. by retnev
As mentioned several times already, "Hide empty staves" already solves the issue of changing from one to two staves. There is no missing functionality here in that respect.
In reply to As mentioned several times by Marc Sabatella
Then I do not understand your initial response as you were raising all kinds of related issues which made it seem like there is an issue with what i want to do.
It doesnt matter as user "Jojo" solved it to the point. thanks a lot.
It is usable now which is great!
Thanks
In reply to Then I do not understand your by retnev
For the record, my initial response was mostly about the general issues with creating textbooks. It *is* difficult working with large text blocks in MuseScore. No word wrap just for starters, also tons of other things you'd expect in a word processor are missing (search/replace, spell check, paragraph styles, multi-column text, margin controls, and on and on). So I suspect most people who create textbooks using MuseScore use word processors and import the images from MuseScore, as it really does make the process much more efficient.
The only real downside of using a word processor to produce the text comes if you wish to have an electronic version of the textbook that incorporates playback, which it sounds like you are wanting. So I was talking about some possible strategies for solving that problem in the future.
For now, though, if playback is important, then indeed, you will have to forego the many advantages of using a word processor, and will instead have to deal with the text entirely within MuseScore.