a few bugs

• Oct 4, 2014 - 04:30

just a few bugs

i haven't read thru all the forum posts, but i assume you'll know where i'm redundant:

os: windows 7, 64 bit laptop, elitebook 6930p

bugs:

1 zoomin shortcut control++ doesn't work (tho zoom out is fine)
2 crashes a lot
3 feature request: i want to have a part titled just "guitar" rather than "acoustic guitar" or "electric guitar" both of which take up too much space in the margin, or else i should be able to put them on separate lines like
acoustic
guitar
and align left or right
4 feature: copy and paste voices? voices are all over the place
5 musescore jumps all over the place too much when editing measures
6 when moving notes using the inspector only the note heads move but then the stems wont select - heads stems and tails all separate but then the stems wont select
7 can't edit palette options (options greyed out) so stuck with too big palette
8 feature: please unify chord symbols with chord names above so they can be cut/pasted together and aligned together from outset
9 when inputting lyrics musescore jumps to next page instead of next note
10 feature: would help if arrows for moving objects in inspector weren't opposite of actual direction
11feature: select single voices in a measure?
12 please post an updated manual
13 seemingly additional rests and unwanted/irrelevant marks (lines) are being created when inputing/editing voices

there's lots more but that's all i can remember after reading 20 pgs of ToS & privacy policy just to post these


Comments

1/ What your keyboard layout?

2/ That's not helpful unfortunately. If you can give steps to reproduce the crash, we can try to fix them. Which version are you using?

3/ What sound would you want for a guitar? You can edit the staff name. Right click Acoustic Guitar in the score -> Edit Staff properties

4/ voices are all over the place? Can you explain that? You can copy paste a single voice with the selection filter. Display -> Selection filter.

5/ It shouldn't jump. Can you explain what you are seeing exactly? You mean it goes to the next line when you are at the end of the line?

6/ You can double click a notehead and use the arrow keys of the keyboard. In this case, the stem and hook will follow if the chord has only one notehead. You can select stem and hook from the inspector once the notehead is selected with the button at the bottom.

7/ It's not possible to edit the default workspace. If you want to edit the palette you need to create a new workspace. Edit -> Workspace.

8/ You mean Chord symbols and fret diagrams? Indeed it used to be possible but it's not at the moment. Not sure why.

9/ How are you inputing measure? Pressing space should move to the next note, if the next note is on the next page, then to the next page.

10/ That's a good one. Can you create a formal feature request? http://musescore.org/en/project/issues

11/ That's possible via selection filter.

12/ That's not the way it works... The community (so you too hopefully) will be working on a new manual before the release of MuseScore 2.0. See http://dev-list.musescore.org/Towards-MuseScore-2-0-beta1-tp7578893p757…

13/ Can you explain more in details what you mean?

In reply to by Nicolas

I too once experienced frustration that elements seemed move in the 'opposite direction' when using Inspector, but isn't this limited to vertical movements?

I adapted once I grasped a critical bit of information, i.e., that measured movement of objects in MuseScore is governed by a Cartesian plane of X and Y axes on which values increase to the right on X but downward on Y. When you consider that normal spin-button behavior is 'up-arrow = more' and 'down-arrow = less', it all makes complete sense.

Even assuming this needs 'fixing', is there really any way it can be changed without (1) requiring different spin-button behavior for horizontal and vertical movements, or (2) imposing a consistent but reversed spin-button behavior (which would be inconsistent with how spin-buttons function in other software), or (3) implementing a reversal in the orientation of the Y-axis?

As a practical matter, it's hard for me to see how any of those options would work - especially option (3), given the absolute need for backwards compatibility - but now I'm wondering if perhaps I misunderstood the original poster's complaint entirely.

In reply to by Nicolas

> 1/ What your keyboard layout?

Keyboard layout pretty much like this:
http://www.notebookreview.com/picture/?f=39038

The machine has a history of switching between French and English keyboard layout for no reason but the zoom shortcut CONTROL+ has always been fine in other programs

> 2/ That's not helpful unfortunately. If you can give steps to reproduce the
> crash, we can try to fix them. Which version are you using?

2.0 Beta - Unfortunately, I could not find any unifying theme for the crashes, all different circumstances - except see UPDATE 1 below

> 3/ What sound would you want for a guitar? You can edit the staff name. Right
> click Acoustic Guitar in the score -> Edit Staff properties

OK thanks. But it is not obvious. I just want "Guitar" - the default names take up too much space in the margin, unless the title is expanded to 2 lines aligned right like I said.

> 4/ voices are all over the place? Can you explain that? You can copy paste a
> single voice with the selection filter. Display -> Selection filter.

OK thanks on selection filter. The rests appear anywhere in the measure, mixed with rests of other voices, then everything has to be aligned with the inspector which has directions arrows labelled backwards.

> 5/ It shouldn't jump. Can you explain what you are seeing exactly? You mean
> it goes to the next line when you are at the end of the line?

It goes to another page. I was using arrows instead of a space bar to move between words. To have to press control+spacebar, control+dash, etc.. I find very anti-intuitive _ I think space bar and dashes should be normal input, and arrows should be used to move between notes/words for lyric input. because arrows don't produce any trace/effect into the actual text field.

> 6/ You can double click a notehead and use the arrow keys of the keyboard. In
> this case, the stem and hook will follow if the chord has only one notehead.
> You can select stem and hook from the inspector once the notehead is selected
> with the button at the bottom.

OK I'll try it again, but I spent some time before and couldn't get it to work, can't believe I missed this.

> 7/ It's not possible to edit the default workspace. If you want to edit the
> palette you need to create a new workspace. Edit -> Workspace.

Then you leave the user wondering why they can't access all these greyed-out commands they see in the palette options. You could have on hover in palette "open workspace in menu to edit" etc or something or make the palette editable from within the palette like photoshop.

>
> 8/ You mean Chord symbols and fret diagrams? Indeed it used to be possible
> but it's not at the moment. Not sure why.

Yes, also the chord names above the diagrams open the text field in the wrong places, inside the chord diagrams rather than above them.
>
> 9/ How are you inputing measure? Pressing space should move to the next note,
> if the next note is on the next page, then to the next page.

I want to use the left/right arrows to enter/move between lyrics, not the space bar, or at least have the option. spaces and dashes are too often needed between every multi-syllable word/lyric to have to press CONTROL all the time for space bar and dash

> 10/ That's a good one. Can you create a formal feature request?
> http://musescore.org/en/project/issues [1]

OK.

> 11/ That's possible via selection filter.
>
> 12/ That's not the way it works... The community (so you too hopefully) will
> be working on a new manual before the release of MuseScore 2.0. See
> http://dev-list.musescore.org/Towards-MuseScore-2-0-beta1-tp7578893p7578...
> [2]

The link doesn't work for me. I don't understand how I can help write new manual when I'm still trying to figure out the software myself because what is written in the old manual is wrong and some things are completely changed, unless you are suggesting I bring all my questions here and compile your answers, which is something I'd probably be willing to do if I stick around that long (see UPDATE 1 below). But I'd need an editable version of the existing manual.

> 13/ Can you explain more in details what you mean?

Sometimes musescore gets the incorrect duration for the measure. for instance i was working in 12/8 time and i would see a 32nd rest in the measure with no balance rest or note, and no dotted rest, etc. It would be giving me the measure a 32nd note short or extra. And no way to edit the measure duration anymore, stuck in the wrong duration for the measure effecting playback. This is after editing the measure several times of course - the missing or extra 32nd note was ghost from previous edits that were now stuck in the measure. I had to delete the measure and start all over.

I thought at first it was me not counting right because I'm just learning and the time was fairly complex for me, but I started counting the measures very carefully to make sure, going over it several times, looking for any balancing note/rest in the measure, and it wasn't me. This is going to be very frustrating for learners if not fixed. It doesn't happen often fortunately, or musescore would be unusable. It must have to do with repeated edits/pastes in the measure.

UPDATE 1
________________________

1 changing instruments: i'm writing a guitar part where there is a foot-tap during silence in the same staff. i tried using the "change instrument" function in text but there's a problem. there are sections of intermittent silence with the foot-tap, then back to guitar, then back to foot-tap etc. so i'm having to "change instrument" back and forth. but each time i "change instrument" i seem really to ADD an instrument. so i have all these different instruments in the mixer when there is really only 2 different instruments in the same staff - the guitar and the foot-tap.

Yet now, not even all the different different instruments i had to add just to get the guitar and foot-tap to change back and forth, even show in the mixer any more and i can't adjust their different volumes

I also seem to be limited in how I load percussion soundfonts in choosing instruments - it strikes me that there will be many cases where percussion appears in the same staff as a rhythm instrument during periods of rest

2 repeated crashing when trying to delete stray slur/tie, sustain line for a lyric that wont delete, super-long stems that happened when trying to adjust space between staffs that wont delete, other random marks that won't delete. CRASH REPORT:

Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: mscore.exe
Application Version: 0.0.0.0
Application Timestamp: 0b307fa0
Hang Signature: 18bb
Hang Type: 0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 4105
Additional Hang Signature 1: 18bbed5e17095a979133c9df6f6f3b97
Additional Hang Signature 2: 174e
Additional Hang Signature 3: 174edb60ab07dc42ed66e600ef6cc2c5
Additional Hang Signature 4: 18bb
Additional Hang Signature 5: 18bbed5e17095a979133c9df6f6f3b97
Additional Hang Signature 6: 174e
Additional Hang Signature 7: 174edb60ab07dc42ed66e600ef6cc2c5

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

3 now the file will not play at all. i don't know how many days i spent on this score, and now it refused to play back at all and instantly freezes if i touch space bar or play or rewind even once. I restarted my machine and tried various things and it happened about 15 times in a row now. if i can spend this much time on a score and then have it rendered useless i'm beginning to think maybe i should be going back to sibelius until this gets a lot more stable

4 sometimes beams in palette work and sometimes not (connecting/disconnecting) - dotted 8th note w/ 16th

5 update: now even trying to just open the said file causes musescore to crash

6 when i login i see all kinds of things for social functions i don't want, yet, i don't see direct link to bugs report i posted and am looking for to follow up

In reply to by ihatefacebook

As you can see, even if we number our answers, it will not work out. If you encounter an issue, you need to create a specific forum post for this issue.

3/ you didn't answer my question. We can add a "Guitar" instrument but what you or users in general would expect this instrument to sound? which staff type etc..?

4/ You are probably doing something wrong. There is almost no reason that you should have to use the inspector to move notes or rests. Did you read Voices ?

5/Thank for your input. As far as I know, a lot of users really love the fact that space and dash move to next chord. Maybe you have a very particular use case? right arrow or space should work more or less the same, can you give a proper example where it doesn't behave like it should?

7/ True, switching and creating workspaces should be more obvious from the palette. Let's create an dedicated issue in the issue tracker: http://musescore.org/en/project/issues

8/ Do you have an example? If yes, can you file an issue http://musescore.org/en/project/issues

9/ See 5. In my experience, it's very rare to have - in lyrics so you might have a particular use case. For most users, it's very convenient to have the - works the way it works. Can you share your use case?

10/ Thanks #35536: Arrows for offset in Inspector should match actual directions that objects move; one spinbox with 4 directional arrows

12/ Try here http://musescore.org/en/node/35416 In short, the community effort is not started yet. And in short, some people are good are discovering and documenting features without anyone holding their hand, if you are this kind of people, then you can help.

13/ Obviously that shouldn't happen. If you find steps to reproduce it, we can probably fix it.

I would not address update 1 here, or it will become a mess. Could you post each point of update1 in different threads on the forum?

In reply to by Nicolas

Once again, my own comments and concerns here - written as carefully, clearly and concisely as I am able to express them - have been completely overlooked. I'll try not to take umbrage - LOLOL!

So ... I simply chose to copy and paste my entire post into the 'bug' report.

Is there really any reason to think that this is a bug rather than a misapprehension on the part of the original poster about how spin-buttons work? Seriously - all we're talking about here is standard spinner behavior, which is consistent with how software works generally and is consistent with the the orientation of MuseScore's Y-axis. At some point very early on, a decision was obviously made that the Y-axis in Musescore would increase in value proceeding downward instead of upward; that may indeed be unexpected, but isn't it too late to change that? Why should normal, established spinner behavior - up-arrow means more, down-arrow means less - be changed to suit one user when it would negatively affect all other users who are used to the way it currently operates and to whom it does make sense within the framework of MuseScore?

Also ... assuming a 'fix' were imposed here where nothing seems broken - would every spinner in every menu of MuseScore also be changed such that UP should equal 'less' instead of 'more'? If not, why not? Consistency matters, after all.

In reply to by [DELETED] 448831

Your point was valid, so I had nothing else to add. Sorry if you feel your comment was overlooked.
The spinboxes are indeed working and once you know it, it's ok. However we might want to make it clearer right away for new users. That's why it's great that an issue is logged and we can discuss it there. Thank you for posting your point in the issue tracker btw. This thread is already messy enough like this.

In reply to by [DELETED] 448831

all I'm suggesting is that the arrows match the actual direction the objects move, instead of the arrow pointing in the opposite direction as they make objects move - will this not make the GUI far more intuitive for most users?

the poster seems to be saying he's gotten used to doing everything backwards, so he thinks that's the way it should be

In reply to by ihatefacebook

With due respect, ihatefacebook, you apparently don't understand why the behavior is as it is. If you're interested in understanding those reasons from another end-user, re-reading my explanation would be a good start.

Your speculation that "the poster seems to be saying he's gotten used to doing everything backwards, so he thinks that's the way it should be" is baseless, by the way, and comes across as antagonistic - as if I were to say that you seem to think you know more about how MuseScore works (and should work) after two days on this forum than someone who's been here for over five years.

In reply to by [DELETED] 448831

sorry if i offended you, that wasn't my intent

i'm just depressed and frustrated because i spent all this time on this score which now won't play or even open half the time

so i'm wondering how can i go on using musescore not knowing if all my work will be rendered useless at any point, with musescore crashing every 5 minutes or so in the meantime?

i was really excited about all the new functionality when i first started using it, but after recent experience its looking more like a very bad investment of time

i have to give it a break for a while and consider whether or not i should participate

best wishes to you

In reply to by ihatefacebook

Apology accepted, and it honestly pains me to know you are having so much frustration.

I have extreme enthusiasm for MuseScore, but everyone's experiences are different because of so many different factors (different computing environments, different needs from notation software, etc.). My only use for MuseScore is the re-engraving of 18th-century piano music, so there are many features and functionalities to which I have no exposure whatsoever - but within my narrow realm, I've found even the Nightly versions to be pretty consistently reliable except for the occasional minor annoyances.

I don't think anyone can answer whether you should continue despite the risks and setbacks you're experiencing, but - based on the excellent track record of the development team so far - I can confidently predict that the official release of 2.0 will be a wonderful thing. Please don't let a less-than-stellar experience with the Beta keep you from trying - and, hopefully, enjoying - the 'real' 2.0 when it is finally deemed ready.

Best wishes to you as well.

In reply to by ihatefacebook

Do keep in mind this is *Beta* software - so it's expected it won't be completely stable yet. That said, it *does* work quite well, especially the nightly builds which have dozens of additional bug fixes.

If you are having good a specific problem with a specific score no longer opening, please start a separate thread on that topic, attaching the score and giving all relevant info you can think of.

In reply to by ihatefacebook

Regarding the spinbox - I hope you have read the the responses so at this point you *do* realize why the up arrow appears to work backwards in the vertical position spin box. In case you missed it:

These are ordinary numeric, and they work the way all numeric spinboxes everywhere always work: up arrow increases the number in the spinxbox, down arrow decreases it. Anything else would seem *extremely* counterintuitive to anyone who has used spinboxes before. It's just an unfortunate fact that MuseScore measures distances in such a way that large numbers in vertical offsets mean something is moved *lower. So a vertical offset of +1sp moves an element *below* its default position, -1sp moves it *above* its default position. That's just kind of fact of life that is been baked into MsueScore since long before the Inspector or spinboxes to give you direct control over vertical position was ever thought of.

So indeed, the spinboxes *do* work exactly as they should, and it would be ultimately counterintuitive to have these spinboxes alone out of all spinboxes reverse the normal direction of how "up" increase and "down" decreases. However, lasconic's idea of replacing the spinboxes with some other type of control is certainly interesting and doable at some point if it seems there is sufficient interest. Personally, I *like* spinboxes, as i am quite used to them, know exactly how they work, and they have a well-defined behavior with respect to keyboard navigation. I would want to be sure any custom control had these same advantages.

A few more responses:

5) There are a couple of open issue reports regarding the score jumping on certain operations in certain conditions. If your issue is one of these, then it is known and should hopefully be addressed before release. If your is *not* one of these, please post a sample score and sterp by step instructions on how to reproduce the problem (that's a good idea *any* time you wish to post a bug report). Here are the known issues:

#7724: During playback, display jumps to top of page if last staff of system is showing
#32866: Score jumps out of focus in 2.0 beta1
#33391: Paste / "R" repositions continuous view to point of last note entry

6) When moving a note, ber sure to use the "Chord" section of Inspector if you want the whole chord moved (eg, stem & all. The "element" section does indeed control just the specific element you clicked - the notehead, presumably.

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