Beam between two notes AND two staves
In the following link (http://musescore.org/en/node/8535) there's the trick to place a beam between two distant notes.
Now, how to do the same thing BUT between two different staves: the 1st note on the F-stuff and the 2nd note on the G-stuff? Not simply in a grand-stuff! But in a 2-indipendent-staves-system (a grand-stuff made with 2 pianos, the 1st with the F-stuff only, and the 2nd with the G-stuff only).
It could be possible?
Thx guys.
Comments
Cross staff beaming works only in an actual grand staff. Sorry. If you really need both facilities (2 instruments and cross staff beaming), there is an ugly workaround... You can create a grand staff in addition to your fake one and use "Hide empty staves". I used this trick here http://musescore.com/score/20915
In reply to Cross staff beaming works by [DELETED] 5
Infact... I had the same idea this night... Thx Lasconic, you're my guardian angel ;)
In reply to Cross staff beaming works by [DELETED] 5
Ctrl+Shift+down arrow allows notes to be beamed across staves. But what a pain this facility is in practice! It works only on single notes. One of the biggest irritations with MuseScore is you never know when a particular facility will work only on single notes (or rests or whatever) and when it can be applied to a group. In piano music you often need to beam note clusters across staves: being able to do this just one note at a time makes the task a major chore.
Similarly, the Ctrl+Shift+down trick doesn't work on single notes when they're part of a chord. Duh! I don't want to shift a whole chord across staves, just the bottom one or two notes. OK, that's cross-stemming not cross-beaming, but surely a single command could cover both of these eventualities?
I look forward to version 2. I try to resist the temptation to groan about excellent software (like MuseScore) that's provided free of charge, but I find the more I use it, with its truly dreadful user interface and other niggles, the more I contemplate biting the bullet and paying for something better!
In reply to Cross staff beaming by FrankO
If you have other specific issues with the interface, starting new threads with specific suggestions would more be productive than dismissing the entire UI as "dreadful". I'm not sure what experience you have with other programs, but I find the UI in MuseScore superior in most ways to that in the top two notation programs in the world. In the couple of places where there is room for improvement, I post suggestions. Simple and effective.
In reply to If you have other specific by Marc Sabatella
I apologize for the strong words; I DO try to be measured in making comments and have obviously failed this time, producing your reaction. Indeed, there is a case for making no comments at all about a free program, but MuseScore has always welcomed feedback. One problem is that the amount of specific feedback has now grown to the point where it's become more difficult to find solutions to problems than it used to be.
My post was addressing the specific issue of cross-stave beaming. The inability to use this specific function other than one note at a time was, for me, yet another example of the frustration of the MuseScore UI. One never knows when an operation will or will not be applicable to single notes or groups. And the basic UI really is, in the most general sense, dreadful. As one adds or subtracts notes or lyrics the whole page jumps around the screen; it's really difficult to follow where the cursor is located at any given time. Selection of items in a score depends on the nature of what's being selected, unlike selection procedures in most other familiar Windows software. And selecting items is a delicate matter to boot. But these points have been made by many others over a long time: my comment just assumed most users are hoping to see an improved UI in version 2.
I can't compare the MuseScore UI with other score-writing software: I can't afford the 'professional' stuff. But I have used free trial periods for Sibelius and Finale in the past. Neither UI seemed as jumpy and tricky as the one in MuseScore, but I never used either as extensively as MuseScore.
To avoid all misunderstanding: I think MuseScore is amazing for what it offers, and have nothing but great respect for those who produced it and continue to update it (yourself included, perhaps?). Please forgive a user with a lot of scoring work to undertake just now, and who under pressure becomes frustrated with the often non-intuitive nature of the way the software offers its goods.
In reply to Sorry for the tone of voice by FrankO
Thanks for the followup! i think you are correct that the developers welcome feedback on ways of improving the program, so there is never a need to apologize for making a suggestion. Tone is another matter, but well, we all have days like that :-), so I would say, don't sweat it! And for the record, no I haven't done any development work onthe progam itself, but I have contributed some plugins, templates, configuration files, etc to make certain tasks (eg, jazz charts) easier.
So as for your concerns about the UI, again, I suggest you start new threads to discuss each of them indiividually. In particular, if you are find specific problems with selections other than the one in this thread, you should describe them in more detail in those other threads. Keeping issues in separate threads help keep discussion more focused. And eventually, after discussion on the forum yields some kind of consensus that the problem is real and not just a misunderatanding, an issue should probably be submitted to the tracker - again, one at a time
FWIW, the only issue relating to selections and operations on multiple onjects that I can remember ever running into is that while you can multi-select rests, most operations you might like to perform on that selection only affect one rest at a time. But that's really the only thing I've ever noticed that sounds like what you're describing. Whereas with Finale, there are zillions of things I would like to do with selections but cannot (eg, transpose up a step with a single keystroke). And lots of other things I find much more intuitive in MuseScore than in Finale. So for me, MuseScore's UI is infinitely superior to Finale's in the most general sense, demonstrating that impressions of things like this are entirely subjective. Clearly, you use the program differently than I do, and encounter issues I don't. So don't assume that just because you see a problem a lot, that everyone else does too, and that therefore the developers already have it on their list of things to fix for 2.0. I honestly have no idea what issues you might be referring to, and it's quite possible the developers don't, either. That's another reason feedback is really valuable.