I'm not sure that this is a good idea since the reload command can not be undone and there is a chance that someone could press the keyboard shortcut by accident.
If you look at other software such as the "File > Revert" command in GIMP and Inkscape, or the "File > Versions" in Microsoft Word, none of these actions have a keyboard shortcut.
Reload is not something that should be used often. If you are using reload frequently then maybe it is due to a bug in MuseScore that needs to be addressed?
The bug's in me, I'm afraid. I use it quite a lot as I am often checking out orchestral voicings - my ear needs to hear the writing to make sure it is acceptable to my mind :-)
As well, I'm sure those other programs could stand to learn a lot from this great new venture :-) :-)
It could be a complex shortcut, Ctl/alt/v/v for example
If I play a piece of music, I cannot edit it without re-loading it. So, once I play a bit and want to edit or add a new part, I have to re-load before I can continue.
Are you saying that once having played the music, MuseScore is locked up and you can't do anything else to the score until you reload? If so, that's not normal.
Or are you using reload to undo multiple changes if you don't like what you hear? It could get pretty ugly if someone accidentlly hit the keyboard shortcut for reload.
In case it helps, you can stop playback by hitting the play button again. Then you should be able to go about editing as normal.
Generally, I must reload after playing any part of the score. Occasionally I am able to work for a bar or 2 and then the program will not respond until I reload.
I had commented on this in one of my previous posts, but it was a small part of the problem I was trying to solve at the time, and I just accepted that the program had to be reloaded.
Now that I know that that is not normal, I will track my movements and try to describe everything more clearly.
I thought that everyone knew what was happening and that it was "just the way this program worked".
When I enter a few bars and then play them to hear if I've been accurate in my transcription, when I stop the sequencer and try to edit a number of things happen, not all the time but most of the time I will try to describe some of them.
I have never had the experience of writing, playing and then doing extensive writing without reloading.
1. Often the program will just basically freeze, The left/right keys will have no impact on the position of the highlighted note and I cannot edit anything until reload..
2. Some times "play line" will move by using the L/R keys, and I may be able to raise or lower a selected note. However, scrolling beyond the visible screen will not change the screen page, neither will pg. up/down, and when I use the navigation window to get to the appropriate part, I will be unable to edit anything.
These are very common experiences, to me. I guess this is a bug.
I have similar experiences while entering multiple voices. Voice 1 works ok, but occasionally when entering other voices, I will not be able to use the left or right keys, and if I try to enter notes beyond a certain point the cursor jumps back to the begining and over-writes what I've written there. I don't use the other voices very much and I'm not sure what I might be doing to cause this. Maybe it is somehow related, since the symptoms are similar?
I only use 1 voice mainly, so I haven't seen quite what you are talking about.
However, intermittent jumps back to the beginning of the score happens fairly often, and I don't believe that it is related to any particular action of mine.
Comments
I'm not sure that this is a good idea since the reload command can not be undone and there is a chance that someone could press the keyboard shortcut by accident.
If you look at other software such as the "File > Revert" command in GIMP and Inkscape, or the "File > Versions" in Microsoft Word, none of these actions have a keyboard shortcut.
Reload is not something that should be used often. If you are using reload frequently then maybe it is due to a bug in MuseScore that needs to be addressed?
In reply to I'm not sure that this is a by David Bolton
Hi David.
The bug's in me, I'm afraid. I use it quite a lot as I am often checking out orchestral voicings - my ear needs to hear the writing to make sure it is acceptable to my mind :-)
As well, I'm sure those other programs could stand to learn a lot from this great new venture :-) :-)
It could be a complex shortcut, Ctl/alt/v/v for example
In reply to Reload by xavierjazz
Are you talking about File > Reload or something else? It sounds like you might be talking about playback.
In reply to Are you talking about File > by David Bolton
If I play a piece of music, I cannot edit it without re-loading it. So, once I play a bit and want to edit or add a new part, I have to re-load before I can continue.
Too much clicking, too much time wasted.
In reply to FIle > reload by xavierjazz
Are you saying that once having played the music, MuseScore is locked up and you can't do anything else to the score until you reload? If so, that's not normal.
Or are you using reload to undo multiple changes if you don't like what you hear? It could get pretty ugly if someone accidentlly hit the keyboard shortcut for reload.
In case it helps, you can stop playback by hitting the play button again. Then you should be able to go about editing as normal.
Generally, I must reload after playing any part of the score. Occasionally I am able to work for a bar or 2 and then the program will not respond until I reload.
I had commented on this in one of my previous posts, but it was a small part of the problem I was trying to solve at the time, and I just accepted that the program had to be reloaded.
Now that I know that that is not normal, I will track my movements and try to describe everything more clearly.
Thanks.
Don
In reply to Re Load by xavierjazz
I am amazed at this conversation.
I thought that everyone knew what was happening and that it was "just the way this program worked".
When I enter a few bars and then play them to hear if I've been accurate in my transcription, when I stop the sequencer and try to edit a number of things happen, not all the time but most of the time I will try to describe some of them.
I have never had the experience of writing, playing and then doing extensive writing without reloading.
1. Often the program will just basically freeze, The left/right keys will have no impact on the position of the highlighted note and I cannot edit anything until reload..
2. Some times "play line" will move by using the L/R keys, and I may be able to raise or lower a selected note. However, scrolling beyond the visible screen will not change the screen page, neither will pg. up/down, and when I use the navigation window to get to the appropriate part, I will be unable to edit anything.
These are very common experiences, to me. I guess this is a bug.
Best regards,
Don
In reply to Reload by xavierjazz
Click on the play button to stop playback instead of the pause button.
Bug filed: http://musescore.org/en/node/1441
In reply to Click on the play button to by David Bolton
Thanks. This has already saved me a ton of clicks.
As you are probably aware now, the bug also appears when I stop the sequencer with the space bar.
In reply to Reload by xavierjazz
I have similar experiences while entering multiple voices. Voice 1 works ok, but occasionally when entering other voices, I will not be able to use the left or right keys, and if I try to enter notes beyond a certain point the cursor jumps back to the begining and over-writes what I've written there. I don't use the other voices very much and I'm not sure what I might be doing to cause this. Maybe it is somehow related, since the symptoms are similar?
In reply to now that you mention it. by MDMilford
I only use 1 voice mainly, so I haven't seen quite what you are talking about.
However, intermittent jumps back to the beginning of the score happens fairly often, and I don't believe that it is related to any particular action of mine.
In reply to Reload by xavierjazz
I filed a bug report for this a week ago: http://musescore.org/en/node/1337