Back again after a year. This time to stick with musescore.
Hi, I posted here more than a year ago, when this site was new: http://www.musescore.org/en/node/106
I tried musescore, but was quite unstable at the moment, so I made a donation and resolved to come back after some time. I've carrying on using sibelius in the meanwhile, being the lack of a "sufficient" score editor under gnu-linux the main reason to not switch from windows completely. Well, I'm back, and after some days of intensive testing, I have to say I'm delighted.
I donated 30 $ to the project a few minutes ago.
It's only a sign of appreciation for the work done. Of course I don't feel myself specially entitled to ask for features. And I'll surely find other ways of being helpful to this amazing project. For one thing, all my musician friends, who mainly rely on me for computer-related advice, know now that "MuseScore is ready to use". Two of them are in fact using it at this moment as a result of that. Well, let's see my "not so big" whishlist (I'm using MuseScore 0.9.5 under Ubuntu Jaunty 9.04):
---> Parentheses for the notes <---
I'd expect it to be in the menu of "articulation/ornament" for the note. The present workaround of picking parenthesis from the symbols palette is a bit annoying. I use parentheses quite often.
---> No (or lower) minimum distance between systems<---
The default settings are sane/safe ones, they're fine as they are. But when you use the spacer tool (much enjoyable to my friends, btw), you can't get the systems (or the staves for that matter) closer than the default. This shouldn't be so bossy, imho.
---> Improve dot placement (staccato signs) <---
Dots over the notes (staccato) usually are placed too close to the note. Some dots even appear inside the note head. See for example "una cosa improvisada" in this post: http://www.musescore.org/en/node/3280 (bar 7, viola voice)
---> Autosave <---
Just my opinion: it should be enabled by default. The program is quite stable, but it still closed unexpectedly a couple of times this week, and I got lost a signficant amount of work. This simple detail can improve the so called "user experience".
That's it. See you in the forums :-)
JC
_______________________
Comments
I would agree with this only if there was a way to undo it. Each auto save could be a new file, for example.
Regards.
In reply to Auto Save by xavierjazz
I have to admit that didn't try autosave in musescore so far (too many things to try out!), so I didn't realize how it works in this very moment. I'd assumed a different file. Indeed the present way of autosaving in the same file can be a bit inconvenient.
I mean, if you are making experimental changes in your music, what you plan (most likely) to discard reverting to the version YOU saved, and the program saves the changes in the meanhwile, then you've lost the version you were interested in.
For example, sibelius creates a sub folder and saves there every backup file it makes with different names (you'll find a ton of them if you've been working in a score for long). This seems a bit excessive to me.
I'd rather MuseScore to simply backing up to a single file, overwriting it each time. For example, if your file is
something_nice.mscz
the backup file, overwriten each few minutes, would lie in the same directory, and be named
something_nice.bak.mscz
My idea is: implement backup for safety, but not in a bossy way (I hate bossy programs :-) )
In reply to Yes, backing up to a different file is what I meant by jc cheloven
This is implemented in latest revision (rev. 2324).
You can change the default distances for the articulations. Maybe "Una cosa improvisada" was initially created in an earlier version of MuseScore. Go to Style > Edit Style > Articulations. The new defaults are 1.0 for all three distances.
Thank you for your answers. Two out of 4 things were already done!! Amazing.
Although I'm not very confident on my source-compiling skills (which I assume are needed), I'll try to find my way around and use the "cutting edge" version of MuseScore. This way I'll also be able to file more relevant reports, and be more helpful to the project.
In reply to Thank you everybody by jc cheloven
There are prereleases available for testing. See Comparison of stable, prerelease, and nightly builds for details.
In reply to There are prereleases by David Bolton
Well, the developers made it much easier than I expected :-)
I've installed the current prerelease, v 0.9.6 rev 2148 in a spare computer: A Dell mini 9 with Ubuntu karmic.
For my last question in this thread: ¿where should I post my findings about the prereleases? I don't know wheter in these forums or in a launchpad page...
BTW: rev 2148 makes a mess of my screen when opening the palette (will post properly elsewhere). On the other hand, nice to see implemented the pitch change for a whole selection. Also works to change octave.
Greetings.
In reply to ok. Where do I post about prereleases? by jc cheloven
If you are able to post [[nodetitle:How to report bug or ask for support | detailed bug reports]] , you can post in the issue tracker.
For discussion about what might be a bug etc..., the forum is a good place. Open a new subject per problem.
Btw, the current trunk is r2331, so the last ubuntu prerelease is a little bit old.
Last point, I've just checked what a dell mini 9 is. The max resolution is 1024*600. Maybe it's related to your palette issue.