- #Lilypond notation software software
- #Lilypond notation software code
- #Lilypond notation software free
There simply is no pleasing everyone - no one behavior is what everyone wants all the time.Ĭut and paste work to mvoe things just as they do in any other program.
So no matter how we do it, it is exactly what some people want at some some times but worse than nothing for everyone else the rest of the time. More often, they would want only one note, or just a few, to move, if any. Yes, as I said, for your particular usage, having everything else to the right shift automatically makes sense, but as I explained, this is *not* how most people use notation software, so it is *not* how most people would want things to shift. am I missing something? ( I'm using musescore 2.0.3) I don't understand what you mean about cut/paste? "Cut" simply replaces the cutted note with a rest, it does'nt shift. Having said this, if I am exposing my point of view over here, then it means that I do believe in the way musescore is evolving. I realy like the way denemo gives me that possibility to be busy with my business. I am a programmer and was always opposed to programs which take the user by the hand while he is still concentrating on his job, constantly intervening (read interrupting) the user with annoying messages or prohibiting him to arrange things, even at a time when the score in his totality is unknown. Maybe a user should be able to choose the way he wants the input to behave? Denemo also has the nice feature of splitting/merging measures by hand. I'm speaking out of practice ( I mean this is what I every time encounter when I use musescore ( and as I can read in the forum, others with me). To be brief : is it not far simpler to shift in at the place I want, and insert any measure farther a rest if necessary ? Everybody pleased. Replacing with rests is like taking over my music and preventing me from writing it the way I want it to be.
#Lilypond notation software free
I can't think of any technical obstacle to implement a total free input (where I can use my ears and intuition ), and keeping the check for the end. I read something like hiding bars and measuring, but found out that this is not the solution to the (frustrating) problem. Please programmers of musescore, when I change the length of a note in the middle of my score, do not replace it with a rest, but shift in the notes on that staff (or give me the choice to replace or shift), because shifting is what I (and many other musicians) intend to do. So, if you tell me that musescore is better, I say "yes, it is for some ways, but lilypond is for all ways". The point is that in denemo (based on lilypond), I do have this TOTAL FREEDOM to go on with my music. All this is done without measures or all the stuff that keeps me from going on with my song in musescore. Once that is done, I start putting the rythm as I have it in mind. When I am creating some music, I first put in the pitch-line, without considering the rythm (even though I already have it in mind). I already saw on the musescore forum that a lot of musicians have the same problem with musescore as I do. Why I still use lilypond when I make music ( as an amateur), is the total freedom at input-time (using denemo or text). a Staff for instance should always have the same tag "new Staff", with a TYPE- attribute, instead of having for each type of Staff another tag. Also the way lilypond makes it's reserved words is to complex. Furthermore I think musicxml is a good evolution for a standard music notation.
#Lilypond notation software software
We like to support Lilypond as they are an ally with us to bring open source software to the market, and meet up with members of the the Lilypond community every now and then.
#Lilypond notation software code
Besides that, as both softwares are following a total different software architecture design, there isn't much overlap between the two projects in terms of code sharing. The other one is the open source development approach.
One is the use of the Emmentaler/Feta font in MuseScore which is originally created by the Lilypond founders. In the end, MuseScore is open source under GPLv2 so feel free to fork it.Īs for MuseScore's connection with Lilypond, there are two things which currently connect us. That said, if a developer demonstrates the capabilities and passion to implement an alternative notation format with a considerable market adoption like Jianpu, we'd be happy to support this effort. The MuseScore team has no plans to work on alternative music notation formats.
0 kommentar(er)
