MuseScore 1.2 prerelease ready for testing

• Mar 5, 2012 - 23:13

Hi everyone,

The MuseScore 1.2 prerelease is ready for testing. We have one for Windows and Mac users. Install it as usual.

Mac users, note that we will provide MuseScore 1.2 for Mac OSX 10.6+ on Mac Intel only.

While you are downloading the prerelease, it is advised to read what is new. The release notes for MuseScore 1.2 not only list the new features, but also bug fixes and the new translations that have been added to this release.

If you find some weird behavior, don't hesitate to report back. But before you do, do a search first to make sure the behavior/bug/... has not been posted before.

If no critical bugs pop up anymore, we can release MuseScore 1.2 by the end of the week or early next week.


Comments

In reply to by Leon Vinken

Just committed the fix for #15325: [MusicXML import] [1.2] Notes are interpreted as rests, wrong lengths, strange results. It works OK for all MusicXML regression test files, the files that are attached to the issue and the Recordare samples (note that I did not test all of them).

Given the scope of the fix (about 60 diffs in importxml.cpp) and the possible consequences if this fails (potentially breaking MusicXML import completely), I strongly urge not to go to MuseScore 1.2 customer immediately, but generate another prerelease to get a broader test coverage.

In reply to by Leon Vinken

If such a build is made available (whether as an official second prerelease or not), I'm happy to install it and run a bunch of my Finale scores through. I have some variety - multi-voice piano music, single staff leads sheets, arrangements involving transposing instruments, vocal scores, etc. If there are particular types of scores you think need to be hit the hardest, I could focus on those.

In reply to by Marc Sabatella

That would be very helpful, especially since I do not have access to the full versions of either Finale or Sibelius.

The fix changes the way MuseScore voices are translated into MuseScore voices. Biggest risk is in multi-voice / multi-staff / multi-part scores. If all is well no end-user visible changes should be caused by the fix for all Finale files, compared with MuseScore 1.2 prerelease. For Sibelius 7 files a huge improvement is expected, although I cannot (yet) guarantee perfect behaviour in all cases. I am also especially interested in tests by Sibelius 7 users.

As I only build on Linux, I cannot produce a Windows build. Don't know if 1.2 is available as a nightly. The decision to produce another prerelease or not is up to lasconic,

In reply to by Marc Sabatella

Question: didn't it used to be the case you could simply click a note then hit Ctrl-C to copy, then click somewhere else and hit Ctrl-V to paste? That does not currently work; Ctrl-C with only a single note clicked and no selection rectangle clears the clipboard. The workaround is to shift-click the note, thus giving you the selection rectangle.

Assuming this really does represent a change as opposed to me remembering things wrong, I'm betting it has to do with the tuplet copy changes. If this was deliberate, then no big deal - it's a small price to pay for improved stability when it comes to tuplets. But if this was an accidental change, though, it might be worth looking into.

Anyhow, I've done about as much as I see myself doing today - created a new score, edited a few existing ones, loaded a whole bunch of MusicXML files. Aside from the above and the MusicXML issues I mentioned here - which may or may not be anything worth dealing with right now - I didn't run into any other new issues. Good job, everyone who worked on this!

And I must say, I am growing to really *like* having the default nudge action be 1sp, and I definitely appreciate that is works with text/chords/lyrics.

In reply to by Marc Sabatella

Hi Marc, the tuplet changes had to do with checking, they didn't change any of the copy logic. Copying notes at the right length #3482: pasting after copy/cut creates note with wrong duration did change the copy logic and already created one regression - //musescore.org/en/node/15338#comment-53641

The following still works. Select a single note in the score, press Ctrl-C. Now select a rest where you want to paste. Press Ctrl-V. Works. If you select a note and press Ctrl-V nothing happens. That we will look at tomorrow (since it's alreay 1 AM in Europe).

In any case, in 1.1, all notes, long or short, were pasted as a crotchet, so not really useful.

In reply to by jorgk3

This seems odd to me. Using my Mac 1.2, I selected two and half bars, pressed Cmn C, clicked on the rest at the end of what I had written so far and pressed Cmd V and voila: it was all pasted in correctly.

In reply to by rhban

Right, it's only clicking a single note - witthout actually selcting it - and trying to copy the single note that doesn't work, and only if the target is another noteas opposed to a rest. As far as I understand, anyhow. Selecting more than one note, or actually selectong (not just clicking) a single note to copy work, as does copying anything onto a rest. The only ting that fails is copying a single clicked but nit selected note onto another note.

Anyhow, sounds like they are on top of it, or will be when they wake up, anyhow! :-)

In reply to by [DELETED] 5

I reinstalled 1.1. This is what it does:
1) Select a single note, copy, select a single rest, paste: Note copies as crotchet (1/4)
2) Select a single note, copy, select another note (maybe in a chord), paste: Pitch copies, ie. the selected note changes pitch.
3) Select a single note, copy, select a range (so a rectangle shows, may only contain a single note), paste: Nothing happens.

Now in 1.2:
1) Note copies at the correct duration.
2) Nothing happens. That's bad.
3) Nothing happens.

So conclusion: The "pitch copy" in case 2) doesn't work any more and we should fix that.

In reply to by chen lung

I haven't noticed any issues with the pedal symbol or other lines, and that includes newly created scores as well as 1.1-created scores loaded into 1.2.

I reported one issue to the tracker (#15331: Incorrect courtesy accidental applied when copying between staves of different transpositions) that could be called critical *if* it's a regression, but I no longer have 1.1 installed to check.

I have seen the occasional display glitches (eg, symbols that still appear to be present after deletion but disappear on reload) and other occasional unreproducible oddities. But nothing out of the ordinary.

BTW, I take it the new design of MuseScore Connect is intentional? I do like having more complete access to musescore.com, and figured that the "featured scores" would become more work to maintain than it was worth, so no complaints there. But I will miss the news feed and the quick access to support videos and so forth.

In reply to by Marc Sabatella

There has been some major work indeed on MuseScore Connect and that will continue now independently from future MuseScore releases as the Connect panel is now directly served from the musescore.com site.

The help and news section and featured scores will be reinstated, but for now we didn't want MuseScore Connect to postpone the 1.2 release any longer. Also more features will come in such as the ability to favorite a score after you checked it out and see more details from a specific score.

In reply to by Thomas

Regarding MuseScore Connect - that all makes perfect sense. Sounds like it will be an improvement in the long run to have everything served from musescore.com, no big deal at all if not everything is there for 1.2 release.

SteveMerrony
Mar 6, 2012 - 18:41

Cannot build 1.2 from SVN at the moment...

CMakeFiles/mscore.dir/moc_webpage.cxx.o: In function `WebPageDockWidget::qt_metacall(QMetaObject::Call, int, void**)':
moc_webpage.cxx:(.text+0x464): undefined reference to `WebPageDockWidget::saveOnlineFinished()'
collect2: ld returned 1 exit status
make[3]: *** [mscore/mscore] Error 1

Just hit on a bad alignment problem whilst entering Bach's Passacaglia in C minor.

The second in voice two has shifted over to the left instead of the D remaining under the F

Bad Alignment

It is thus obscuring the natural sign for the F - which I'm now wondering why is there :)

[Edit: Hehe because I copied and pasted the bar :)]

Not sure if this is regarded is critical however :)

Attachment Size
BadAlignment.png 5.49 KB

In reply to by ChurchOrganist

I don't have my copy of Gardner Read in front of me, but I'm not sure the alignment of notes is incorrect according to standard practice. The accidental could obviously have been placed better, but it is pretty normal to need to adjust those in multivoice music.

My understanding of the alignment rules for noteheads says the F should be aligned with the C, just as it is. In cases where there are no seconds anywhere, you align the noteheads. In cases where there is a second between the two voices, then you are supposed to align stems. But as far as I know, just because one voice has a second within it somewhere doesn't mean you switch to stem-alignment. And when aligning noteheads, you normally align the non-displaced noteheads. Looking throughthe music I do have on hand, that appears to be the rule followed in all cases I could find. I agree it looks odd in this particular case, but I suspect it is the accidental that is mostly responsibile for that.

Anyhow, it is true that MuseScore doesn't necessarily get everything right even when there is a clear right and wrong. This has always been the case, although my hope is that we'll need less and less of that over time. Luckily, the adjustment is perfectly possible to do via the cursor keys in Edit mode.

In reply to by Marc Sabatella

In actual fact i got round this one by moving the D to Voice 1.

MuseScore then promptly squashed the C in voice 2 up against the D instead of aligning it properly offset to the right.

It would be nice if it did this automatically instead of having to enter edit mode and move the note manually.

Maybe in version 2 :)

In reply to by musiclover007

Supporting Mac 10.5 is not planned, but you never know, someone might compile it for this platform.

Apple OS (and products) is evolving at a very fast pace and it's very hard for open source projects to keep with this pace. Mac OSX 10.8 is planned for this summer, only one year after 10.7... Choose your hardware wisely.

Hi all.
Yesterday I installed Musiscore 1.2 and I decided to write a score. Everything was perfect until I started to add lines.
Everytime I drag a line into the desired note my computer hunged. I did it five times with the same result. I decided to roll back to the previous version, 1.1 and everything went fine.
I´m using Windows 7 Enterprise SP1 32 bits on a Dell laptop E6410, Intel Core i5 M560, 4GB of RAM. 150GB HD with 50GB free.
I hope this helps
Good luck and many thanks for this fantastic product!!

I'm sure (although I could be hallucinating) that in 1.1 I could highlight a dynamic or an ornament, then Ctrl-C and highlight a new note and then Ctrl-V it in to the new note. It was most useful if, for example you had a >, fp or tr which you had repositioned at a different distance from the stave, then by copying it it would keep its relative distance to the stave (rather than double-clicking the palette which puts it in at a default distance)... erm... did that make sense? In 1.2 (on XP) copying and pasting these have no effect.

I did also end up with 4 crotchets and a quaver in a bar of 4 4 by copying notes from another section in 6 8, but I fixed that by deleting the whole bar and reinputting it. So I'm not sure it's calculating pastes from other sections correctly sometimes.

But hey, minor gripes - fantastic software!...

1. 'Open'.
2. Select score.
3. 'Open'.
4. 'Play'.

Result: Doesn't play.

Workaround: Click on the program, then play.

Discussion: Only seems to apply if you do via 'Open' (as opposed to double-clicking file, or 'Open Recent').

Using MuseScore 1.2 (Pre-release 1) - Mac 10.6.8.

I didn't look too carefully when I desperately needed a music program, so I inadvertently downloaded version 2. I have had no real troubles with it, except I find it very difficult to put lines or slurs over notes - when it succeeds, I am never sure what I have done differently - and I don't find lyrics terribly easy either - "delete" works within a word, but if I want to delete more, it seems I can only use Undo. I might also want to add chords (just the A, B7 kind), which I suppose I could use "lyrics" for, but in addition, I would like to be able to label sections of the music "A", "B" or "C" above the stave. Is that possible?

In reply to by rhban

You can add slurs by selecting the note and hit s
You can delete multiple lyrics syllables by 'shift-select' them
You can enter chords by selecting a note and hit Ctrl-k
You can label a section using system- or staff text, select a note and hit Ctrl-t resp. Ctrl-Shift-T

None of this has really to do with 1.2 or 2.0 though and all is described in the [[nodetitle:handbook]]

In reply to by rhban

I suggest you use version 1.2 and not 2. Version 2 is in pre-alpha state, it's not stable, subject to change and some features don't work. It's really only for people who want to test or develop. Version 2 has a new file format, so you won't be able to open the files created with this version in the stable version 1.2.

In reply to by jorgk3

I did it with no problems: I exported it as an XML file, which v1.2 was able to open with no difficulties.

One problem I have found with both versions: at one time I had althernate endings correctly labelled 1. and 2., but when I changed my mind and deleted one ending, I still had the 1. bracket there and the only way I found of getting rid of it was to drag it off the screen.

In reply to by rhban

In fact dragging it off the sheet would probably merely hide it and not delete it, so you have a hidden, possibly corrupt volta somewhere in your file.

Probably the reason it won't play back.

Best plan would be to attach it to a post here so that one of the guys who know how to hack MuseScore files directly can have a look.

In reply to by rhban

My comment about not being able to remove a - I don't know what you call them: those numbered square brackets that show first or second endings - was something about version 1.2.

True, and that's worth resolving here. But there was a fair amount of other stuff being discussed that kind of obscured this, and that definitely belonged elsewhere.

Right now, as a new user, it still isn't clear how many of the problems you might be having stem from simply not knowing how to do certain things in MuseScore. In any particular, it is entirely possible that your volta problem will turn out to be an example of that. Hard to say without a specific reproducible example. This thread is getting long and rambly enough as it is, so I think the desire is being expressed to limit further posts here to specific and hopefully reproducible bugs that are known to be issues with 1.2. If you experience other issues, I do think it better to do so in a new thread. That's the usual way we work around here anyhow.

FYI, I've been hitting the prerelease pretty hard this week, both with some of own work and with a project for a client that's a little outside what I might normally be doing, and I am happy to report no new issues encountered.

"Save online" (from Menue->File) is not translated nor translatable, nor is any of the dialog boxes behind it.
Is this on purpose, work in progress or just overlooked?

MuseScore 1.2 (Pre-release 2) for Mac is available. I have a couple of minor comments, if quick fixes are available:

Two Undos to remove a slur are required after it is applied.
In Preferences, the 'program start' options aren't lined up.

Attachment Size
Program Start.png 13.83 KB

In reply to by jorgk3

All I see with my Mac version is that two undo are required. I would prefer with a number of items like this to go the logical way of highlighting the object and pressing Delete, but that does not work.

SteveMerrony
Mar 12, 2012 - 08:38

This is quite hard to describe, but in orchestral scores I am having occasional difficulties with brackets and braces that appear spaced too far from the stave.

You can replicate by opening the ActorPreludeSample.mxl from the xmlsamples_v3 collection.

You will see first that the brace and bracket are in the wrong order for the Trumpets. The fun comes when try to correct them by deleting and re-inserting. You cannot get the brace close to the staves.

I have noticed this behaviour for quite a while in the 1.2 series.

In reply to by SteveMerrony

I tried Googling to find that file to try to reproduce this issue, but couldn't find a working link. Apparently it's part of recordare's test suite?

If fhe error you see is only on scores imported by MusicXML, this falls under the category of things I don't really expect to work, so I didn't report each and every place where layout was not what it was in the original. But I'd agree, sometimes things like this go awry with MusicXML import. When you say you cannot get the brace close to the staves, though, I wonder - is the setting for this distance good in Style->Edit General Style?

In reply to by SteveMerrony

I see what you mean - with certain imported MusicXML files, any brackets and braces you insert after import always appear too far from the left barline, even with the Style setting to 0sp. It doesn't affect *all* MusicXML files, though.

I was able to reproduce this using one of my own MusicXML files, but not with another. Looking at the MusicXML source itself, i think I see why. The one that exhibits the problem has existing brackets with non-zero distance from staff, and it appears than any newly added brackets are added *outside* that distance even if they are not covering the same staves. If you delete *all* the existing brackets and *then* start adding your own, they appear where you would expect. At least, that's what I am finding.

So, a bug to be sure, but perhaps not one worth holding up release for at this point?

  1. Please update polish handbook in pdf and mscore_pl.qm file for stable version 1.2 of MuseScore.
  2. I created new schleifer symbol and a few other fixes (arrows in accidentals and more) for mscore-20 font but... I can't attach zip file - "An HTTP error 0 occurred.
    /en/comment-upload/js"... !!! If someone could help me, I'll be very greatful.
  3. Great job.
  4. I look forward to version 2.0 :D

In reply to by Gootector

Hi, it's too late to include modification to the font in MuseScore 1.2, the stable release is planned for the next hours and the font is one of the basis of MuseScore. Different slides symbols will be available in MuseScore 2.0. Check the nightlies and if you miss a symbol, don't hesitate to contribute a modified font for MuseScore 2.0.

In reply to by Thomas

lasconic: Ok, thx.
Thomas: Firefox 10.0.2, Windows XP Service Pack 3.

I have a question - why I can't register at sourceforge.net? I didn't get e-mail to finish setting up an account. I tried twice.

Do you still have an unanswered question? Please log in first to post your question.