Neck position
Maybe there's a simple (and powerful) way to do this, but I haven't found it. If I enter a three note chord consisting of A-flat, D-flat, and A-flat(8va) in standard notation and then switch to tablature view, MuseScore notates it as E4, D1, and G1. Whereas most guitarists would play that as E4, A6, and D6. If I could select the chord, bar, or entire passage and tag it as being at neck position IV, I would expect the tablature to render in a more playable form.
I know I can select individual notes and Cmd(Ctrl)-down arrow and switch to the desire string/fret combo but when working with midi files imported from other programs where this is an issue in multiple places throughout the score, this quickly becomes a dauntingly laborious task. Even if it were possible to drag a marquee selection box around multiple notes (while excluding other notes in the chords) that would make the task way more feasible.
Comments
" If I enter a three note chord consisting of A-flat, D-flat, and A-flat(8va) in standard notation and then switch to tablature view, MuseScore notates it as E4, D1, and G1"
If it's a power chord, I imagine you meant to write A-flat, E-flat (and not D-flat), A-flat.
Of course, the only way to solve this would be to enter the notes/frets directly in the TAB staff. But I understand that you're coming from a midi score with standard notes. In this case, Musescore is not supposed to guess that you want a power chord. In blues/rock/hard rock etc. styles, surely, but not necessarily for another music styles, classical eg.
To minimize this editing work and change the frets position throughout the whole score in a single action, you can do the following:
And do it again for the A-flat.
NB: for Select/More, I advise you to create a shortcut in Preferences/Shortcuts for "Select similar elements with more options". You'll save a lot of time. For my part, I've chosen "P" (like Plus in French! instead of Piano, which I never use). Other advantage: you don't have to right-click the fret, only click -> "P" etc. (This is what I do on the GIF below)
See:
In reply to " If I enter a three note… by cadiz1
Yes, I know all this. I'm looking for a better way (although the custom shortcut tip will help a little). As for changing a note's string/fret position throughout the whole score, that is likely to cause as many problems as it solves--the same note may be played in different chords in different neck positions in different locations in the score.
In reply to Yes, I know all this. I'm… by stiffmittens
Ok, in Selection/More, there's another "In selection"option, which automatically ticks when you make a selection of, say, one or more measures. This allows you to process a section more quickly.
Also: once a change has been made, copy and paste can also speed things up. But you already know that.
Otherwise, there's no magic solution.
As already mentioned, you can't ask the program to guess things for you. In the image below, the result is correct in both cases. Sometimes you'll want (me too!) to see the first measure, sometimes the second.
The question wouldn't arise with a piano; it does with a guitar, by nature. Advantage or disadvantage?! :)
You're the only one who knows which result you want in which case, so it's an editing job to be done, like any other. Of course, the frustration comes from having to change things. This wouldn't be the case if you entered the desired frets directly from the TAB staff. But since that's not the case with your MIDI import, we're back where we started! :)
In reply to Ok, in Selection/More,… by cadiz1
Okay, good to know. The within selection option will speed things up. But to be clear, what I am suggesting would speed it up even more. Most notes playable on a guitar are playable in a few different locations on the fret board. But at a given neck position the potential locations of playing a given note reduces to one possible location—so the software would not be guessing at anything. RealLPC uses a system of keyswitches to achieve this. Unfortunately that vsti has no feature to export as tablature (but I can get the midi out of it). Having a way to define neck position for midi guitar parts in museScore would be a godsend for me (and I have to imagine others would also find it useful). Anyway, thanks for the advice.
In reply to Okay, good to know. The… by stiffmittens
It may be possible to write a plugin to do this but you would need to add special text markers to your score so that the plugin could know what position you're playing in. It would then be possible to choose the closest relevant string/fret combination for the note.
The markers would only need to be present when the position changed and the initial default could be zero, i.e. playing in open position.
In reply to It may be possible to write… by yonah_ag
Indeed, I had imagined that this could be the subject of a plugin. For the record, would you volunteer to write it, or not?
In reply to Indeed, I had imagined that… by cadiz1
I would enjoy doing so, especially as TAB is involved, but probably won't be able to find time until near the end of the month, so please feel free to take it on.
In reply to I would enjoy doing so,… by yonah_ag
"so please feel free to take it on."
It's neither my skills nor my desire. I leave it to those who are motivated and know how to do it.
In reply to "so please feel free to take… by cadiz1
Fair enough.
I need to check whether the plugin API allows changing string & fret otherwise it's a non-starter. Is there a convention for indicating position on the neck?
In reply to Fair enough. I need to check… by yonah_ag
Ok.
Positions are defined by Roman numerals: I, II, III, IV, V, VI and so on.
For example, looking at the image in a previous commentary with G power chords, the position III (= G, third fret on the 6th string) would prohibit fourth and third open strings, D, G.
In reply to Ok. Positions are defined by… by cadiz1
I'll need to use a prefix of some sort so that special 'guitar position' Roman numerals are not confused with any other Roman numeral texts. The TAB Ring plugin uses a $ prefix for special stop codes so I'll need a different prefix for position , maybe @ because it means at which could be short for "At Position".
So, @V would indicate "At position 5" etc. This would be placed on the TAB stave.
In reply to I'll need to use a prefix of… by yonah_ag
"So, @V would indicate "At position 5" etc. This would be placed on the TAB stave."
Why not.
In reply to "So, @V would indicate "At… by cadiz1
Other factors to consider: Capo/barre lines and String Number Objects.
It would make sense if the user could opt to have String Number objects and Capo/Barre lines influence the tablature string designation.
Please respond at the link provided above.
In reply to Indeed, I had imagined that… by cadiz1
Another potential wrinkle would be if you wanted to account for open string drones and/or extended finger stretches. Plenty of examples when a chord is played primarily at a higher neck position but open strings are included. Also in some situations a chord may be played at a certain neck position but one finger might stretch to fret a note outside the expected range for that position.
In reply to Another potential wrinkle… by stiffmittens
I regularly use drone open strings but not so much extended stretches.
String and Fret number can be changed via a plugin provided there is no change to the note's pitch - which there wouldn't be for this plugin. If a plugin is going to be useful then it needs to get it right most of the time; otherwise there is still so much manual work to do that you may as well do the whole job manually.
So, If a specification for this process can be defined then it is probably possible to code it. This would need to cover how to define position, (e.g. @VII style texts), and handling exceptions, (maybe a special @ code to say "leave this note alone: I'm taking care of it manually). Depending how much effort is required for the scorer to add these codes would be the basis for determining whether the plugin is worthwhile.
Plugins can have options so it would be possible to have tick boxes for things like "Use open string where possible", or "Capo at fret NN", etc.
In reply to I regularly use drone open… by yonah_ag
"If a plugin is going to be useful then it needs to get it right most of the time; otherwise there is still so much manual work to do that you may as well do the whole job manually."
You are right, well said.
Go to the point, it will be already a good step forward.
In reply to I regularly use drone open… by yonah_ag
.