Piano Roll Editor for TAB
It would be nice if the piano roll editor could have a TAB version similar to the way it has a drum version.
For example:
:
It would be nice if the piano roll editor could have a TAB version similar to the way it has a drum version.
For example:
:
Do you still have an unanswered question? Please log in first to post your question.
Comments
If by Tab version you mean the piano roll editor (PRE) should support fretted string instruments - like ukulele, mandolin, guitar, banjo, etc. - and also handle alternate tunings...
That seems like a pretty tall leap for the PRE of a score writing app.
In reply to If by Tab version you mean… by Jm6stringer
I just mean a simple "overlay" on the piano keys as per image above. There is already such an overlay for drums, (image below), so it's clearly possible and maybe within the scope of a score writing app.
In reply to I just mean a simp!y … by yonah_ag
The drum "overlay" looks to be specifically for manifesting a drum map. This is an extra "virtual" layer and not truly pitch related as relates to the use of a non-pitched (drumset) instrument.
As a user, I'm slightly interested in knowing the use-case of having multiple string-fret markings in the piano roll editor. Does not working with notes on linked-staves of tablature with a regular clef fulfill whatever that use-case is?
In reply to The drum "overlay" looks to… by worldwideweary
The MS manual says that, "the Piano Roll Editor allows you to edit individual notes and tweak aspects of their playback". This can be useful at times, e.g. applying a string based guitar "let ring". The current implementation of "let ring" is quite basic and seems to act more like a piano pedal. (See https://musescore.org/en/node/286670). I have tried the workaround but it's tedious compared with using the PRE.
I am TAB only user so a linked stave doesn't really help me and also doubles the number of pages that I need for a score. Similarly the piano keyboard in the PRE doesn't help as I don't play piano and the black and white keys form a repeating pattern which makes it harder to know where you are.
Imagine the PRE for a drummer but without the drum kit "virtual" layer: it would be much harder to navigate. This is the same difficulty the that I have as a TAB-only guitar player.
In reply to The MS manual says that, … by yonah_ag
Yeah I just noticed the PRE puts a cap on the [Len value], so if you have a quarter note, it doesn't look like it's possible to give it a 4000 value so that it spans the whole measure while retaining the quarter notehead. That would've been useful for L.V. maybe.
It sounds like you'd benefit from being able to extend the length value while looking at the tablature staff from the main view. The plugin Dock Articulate will let you do this, so in the mean time, you should try it out. You can select a tab note, and then have this docked in your inspector area, and give the same value you would in Len in the PRE right there, like 1500 or 2000 (doesn't look like you can get it past 2000), or shorten it.
If you don't have it, here's BSG's link: https://musescore.org/en/project/articulation-and-ornamentation-control.
In reply to Yeah I just noticed the PRE… by worldwideweary
Thanks, I'll take a look. My next MS request was to be able to have length > 2000 in the PRE but this plugin may be ideal. (Playback already supports longer durations as I have tested it by manually editing an mscx file.)
In reply to Thanks, I'll take a look. My… by yonah_ag
The plugin and its API disbelieve end times over 2000 ("these are the end times....")
In reply to The plugin and its API… by [DELETED] 1831606
If I remove the 2000 limit from the plugin will the main program still limit to 2000?
In reply to If I remove the 2000 limit… by yonah_ag
No. It's coded/designed into the core API. Before you cry "#$@#"?##?" think of the likelihood of mistyped input (e.g., failure to remove the value that is there) crashing the app or creating files which crash the app.
In reply to No. It's coded/designed into… by [DELETED] 1831606
Fair enough. I can do it by editing the mscx file then resaving as mscz since this leaves the changes intact. It'll be up to me to choose values which make sense, e.g. no overlaps in the same voice.
In reply to Fair enough. I can do it by… by yonah_ag
Editing the mscx file is the royal road to perdition, a red flag saying "you're doing or thinking something wrong."
In reply to Editing the mscx file is the… by [DELETED] 1831606
But it's useful and fun and is pseudo-recommended in this post: https://musescore.org/en/project/articulation-and-ornamentation-control
In reply to But it's useful and fun and… by yonah_ag
Quite the contrary; I said that you don't have to resort to such horrors any more.
In reply to Quite the contrary; I said… by [DELETED] 1831606
and followed that up by saying that mscx editing remains available, hence only a pseudo recommendation. 🙂
In reply to and followed that up by… by yonah_ag
"Yeah, you don't have to take the new medicine. If you prefer dying in the swamp, go ahead".
In reply to "Yeah, you don't have to… by [DELETED] 1831606
👍👍 I like swamps as long as there are no alligators! (and I can't achieve the required results with MS - with or without the plugin).
It's also a good learning experience as I am looking at plugin development. I have written a simple mscx browser in Excel VBA and this actually helps understand some of the UI layout better, e.g. the < measure > tag and its sub-tree helps "explain" the inspector chords and notes sections, so even if I don't make changes it's interesting.
In reply to Fair enough. I can do it by… by yonah_ag
Wouldn't hidden pedal marks be just a little bit easier than editing the mscx?
In reply to Wouldn't hidden pedal marks… by worldwideweary
Yes but guitar let ring and piano pedal are not the same thing. The MS implementation of let ring appears to be pedal by another name so it has some issues.
https://musescore.org/en/node/286670