My wishlist
1) be able do delete a range of bars without having to select via the mouse a region . It’s much faster to delete a range x-y in a single command.
2) be able to change to change tempo of an entire song by a given percentage and be able to save that change to a midi file or MuseScore file . Today it only works in the play panel but you cannot save it . Rationale for this feature is when you want to make backing tracks with midi files and want to change the tempo . Of course you can always export the audio and change the speed of the audio but the quality will be lower.
3) one functionality ( nice to have ) would be the possibility in the play panel to select a region and repeat it X times , starting at tempo Y finishing at tempo Z and increasing the tempo at every repeat by a factor of (Z-Y)/X . I have only seen this feature once but it extremely useful in practice mode
Comments
1) Select by keyboard? (only half joking)
I do wonder how often you know the x-y to type in into a delete range command without first navigating to it and thus kind of doubt the use-case scenario for such a feature compared to the already available select-range and delete command. Perhaps you can elaborate on the use-case you have in mind?
2) Have a look at https://musescore.org/en/project/tempostretch
3) Some practice mode ideas have been floating in the forums so I don't doubt that one day it'll make it in. I don't really find an existing issue for it other than #329781: Play Panel as study guide which isn't exactly the same as what you're requesting.
There is already loop mode, but you still have to manually adjust the tempo slider during practice.
In reply to 1) Select by keyboard? (only… by jeetee
Thks for reply .
(1) use case
I am working on a large file with many instruments . If I want to delete bar 1 to 40 for all instruments, I have to select bar 1 scroll down to select all instruments while holding the shift key then still holding the key, I have to browse 40 pages and then delete the section which I guarantee you takes more time than typing a range . Maybe there is faster way to do it .
Moreover there is a bug with the delete fonction , I can send you the score if you need it if that
helps as it doesn’t work on this particular score .
2) thank you II will have a look today for sure
3) Thks that’s only a nice to have , but when you have tried it , it becomes indispensable!
In reply to Thks for use case . (1) use… by [DELETED] 47906502
Are you saying you have a score in which only measure fits on a page, for forty pages? I can't say I've ever created one quite like that. In general, I usually find at least half a dozen or so measures per page in the worst case. So one question is, do you have a reasonable staff size and page size? Attaching your score would help us assist better.
Normally, the way I'd select around 40 bars - I don't think I've known it would the exact number before deleting - is to click the first measure, then hit Ctrl+PgDn a few times until I reach the page with the end bar. Or, zoom out and just swipe left until I get there. Then just Shift+click the desired measure. This would normally be no more than about half a dozen keystrokes/gestures - about the same as actually typing a measure range :-). And, no holding of Shift required either way - click first measure, then Shift+click last.
That said, if you actually do for some reason know exact measure numbers often, presumably a plugin could prompt for that info. So if enough others find this useful, no doubt it could be coded up.
Anyhow, if you are saying you are also encountering some sort of bug with actually deleting once you've selected the range, indeed, we'd need you to attach the score and give precise steps to reproduce the problem.
In reply to Are you saying you have a… by Marc Sabatella
I have attached the score, I use the default settings A4 , I guess the issue is the number of notes/per bar per instrument is very different which I think leads Musescore to present a view with more or less a bar per page.
Bar 40 is on page 37. I have attached the score for ref. Now I use the trick that you and Jetee recommended using the keypad which is definitely faster than the way I was doing it. I understood what caused the issue with the delete , it was happening because I was still pressing the shift key during the selection phase when I pressed the delete key function.
In reply to I have attached the score, I… by eleos2021
That's not a "score" but a set of playback instructions (midi) which upon import is attempted to be turned into notation.
But because of the non-quantized input you'll end up with lots of tuplets and little notes to capture the timing inaccuracies which in turn indeed result in rather large measures.
In reply to That's not a "score" but a… by jeetee
I guess that’s why indeed . Semantically speaking , I beg to differ though , as when I refer to the score I refer to the notes transcribed and visualised through MuseScore sheet music Viewer . No matter the way notes were entered : manually , while recording or importing external midi file ,it doesn’t change the fact that the final result are notes written using standard music notation convention , which is the definition of a score;). It just happen and agree with you that recorded midi sequence are by default ‘humanised’ and create challenges for any music notation sofware included MuseScore ( which becomes my favourite ! )
Cheers
In reply to I guess that’s why indeed … by [DELETED] 47906502
A score, in the sense of MuseScore, is an mscz (or mscx) file, nothing else.
In reply to A score, in the sense of… by Jojo-Schmitz
I hear what you say and in fact you agree with me . I. E if I import à midi file , save file as a mscz file we both call it a score ;)
In reply to I hear what you say and in… by [DELETED] 47906502
I realized that after having sent it 😉
In reply to I realized that after having… by Jojo-Schmitz
No worries mate ! Have a great day !
In reply to I guess that’s why indeed … by [DELETED] 47906502
Definitely, knowing that you were trying to import a MIDI file rather than entering the notes normally makes a big difference in understanding some of the unique problems you will face. As mentioned, the nature of the unquantized rhythms in this particular creates quite a mess, and each measure will require much more space than a normal score would. It also ends up being completely unreadable. So, one of the things you will need to do here - assuming you do in fact continue to keep working from this MIDI file rather than simply entering the notes yourself into a new score, which would probably be much faster - is to correct all those rhythms to make sense from a notation perspective, simplifying them to be readable while still conveying the original intent, Which will cause them to take less space.
But the other reason your score is taking so much space is that indeed, your staff size is too large - and/or, your paper too small. The defaults in MuseScore for imported MIDI files don't take into account how many instruments there are and how small the staves would need to be in order to fit onto a page or how large a page a conductor would likely want to work from. For a score with this many instruments, you need a much smaller staff size. So, go to Format / Page Settings and reducing the staff space setting until things fit. This would normally be set up by default when creating a score from a template, or it would be the first thing you would normally do when creating a score "from scratch", before attempting to start entering notes.
Meanwhile, I'd also recommend switching to Continuous view instead of the default Page during your initial work on this score (see control on main toolbar). Because as it is, some of those measures are such a a messy they don't fit on a page after reducing the staff size to get all staves to fit.
But again, realistically, for a MIDI file like this that was never optimized for notation, it would be far simpler and faster to start over with a new score and enter the notes normally, figuring out the best way to represent each rhythm yourself. MuseScore is going to be far too literal, which is why this score ends up being so unreadable, You could also try quantizing it in your favorite MIDI sequencer / DAW software, and then reimporting, to see if that gives you a better starting point for editing.
In reply to Definitely, knowing that you… by Marc Sabatella
Marc, thank you for exhaustive reply. It makes perfect sense and I will try several options yiu mention!!
In reply to 1) Select by keyboard? (only… by jeetee
I have tried the time stretch plugin , it works like a charm in 3.6.2 , so Thks for that
Regarding use case for (1) I forgot to mention that when you navigate just scrolling to find bar numbers , you can use the trackpad and then browse very quickly , but as far as I can see , the selection doesn’t work with the trackpad , hence the pain having to scroll and press the right arrow key when you have more than 40 pages of score . The numbers of key press exceeds by far the number of keys you have to type in a x-y range.
But again I may miss something , so if I m incorrect just give me the trick and I ll pay you a beer !
In reply to I have tried the time… by [DELETED] 47906502
Anything for a beer ;-)
I don't usually have to remove that large of a range, but here are the two approached I do use:
Method 1 - Scrolling
1. Click on the starting position for the selection
2. Scroll to the end position (for example with trackpad)
3. Shift+click the end position
Method 2 - Timeline
Especially useful for entire measure selections imho
1. Open the Timeline (F12)
2. Click on the starting measure in the desired instrument
3. Scroll to the end measure (Shift+scroll works horizontally, just like on the score!)
4. Shift+click on the end measure in the desired instrument.
Again though, not to say that typing a range can't have some added value as well, but these methods definitely seems a lot faster than what you're currently using.
In reply to Anything for a beer ;-) I… by jeetee
Brillant ! You are a shooting star !