Starting beam over rest, buggy interface
in Finale, I'm able to start or end a beam over a rest:
Is this possible in MuseScore?
After selecting the beam, I go to "Beam Properties" and select "Beam Start", but then can't adjust the start:
This tool seems to deselect itself, unless I fiddle with it a bit:
Tooltip seems to clip there as well.
OS: macOS 10.15, Arch.: x86_64, MuseScore version (64-bit): 3.5.0.28537, revision: 43c5553
Comments
Select the rest, then apply the "Start Beam" palette item to it.
Which chord/rest is beamed is a property of the chord/rest, not of the beam, the "Beam properties" of a chord/rest
Reg. tooltip see #296116: [macOS] Hover tooltip is cut off
In reply to Reg. tooltip see #296116:… by Jojo-Schmitz
Sorry for being dense here, but still not getting it:
In reply to Sorry for being dense here,… by jasonsturges
Works for me
![Beispiel3.png]( "Beispiel3.png")
In reply to Works for me by Jojo-Schmitz
Thanks for showing this is possible.
Not sure what factors are preventing me from doing this in MuseScore. Exported MusicXML from Finale, which perhaps this notation isn't part of MusicXML spec as per why it's not there in the first place.
In reply to Thanks for showing this is… by jasonsturges
Can you share the score? And the MusicXML?
In reply to Can you share the score? And… by Jojo-Schmitz
MuseScore and MusicXML attached.
Thanks for looking - clearly not pressing, but appreciate your time and insight.
In reply to MuseScore and MusicXML… by jasonsturges
You need to other chord/test's beam properties to Auto, like that of the 8th note following that 1st 8th rest, which is set to Beam Start instead, there you want Beam Middle or Auto instead. Or even 16th Subbeam
In reply to You need to other chord/test… by Jojo-Schmitz
Thanks for that. Struggling with the interface a bit, but getting the gist.
It would be great if the MusicXML included this - that might be Finale, or MusicXML spec itself.
Thanks, again.
In reply to You need to other chord/test… by Jojo-Schmitz
By default, beam properties are set to auto, except for MusicXML import, which takes the information present in the MusicXML more literally, because MusicXML normally (always?) have this hard-coded. The same is true of stem directions, BTW. So as a general rule, I almost always reset everything to defaults after a MusicXML import. Ctrl+A, Ctrl+R, then the Auto button in Beam properties.
In reply to By default, beam properties… by Marc Sabatella
Thanks for that insight, Marc - appreciated.
In reply to MuseScore and MusicXML… by jasonsturges
Dear Jason, dear Jojo-Schmitz, dear Marc,
i kind of stumbled upon the very same issue. xml-format actually supports following beam values (in musescore term roughly: beam value = beam propertie): "begin", "continue","stop","forward hook" and "backward hook". For this exact situation at hand here that you, Jason, are describing, "forward hook" and "backward hook" would be the weapon of choice. "forward hook" and "backward hook" are both beam values that would be assigned to the actual note element in xml file that is supposed to have the hook, not to the rest.
Is there any plan to implement support of these beam values? It would be greatly appreciated.
I hope my comment isn't redundant or unfiiting to this very thread, since i am new to this forum i am not quite sure how to contribute and take part in a senseful manner.
Best regards
Marco
In reply to Dear Jason, dear Jojo… by lehnemar
lehnemar,
Really appreciate your information regarding the MusicXML specification.
Likewise, I hope MuseScore team will incorporate this functionality.
Thanks,
Jason Sturges