Tab with unison overlapping -> red
Hi everybody,
I'm trying to create a tab as attached.
following recommendations in
https://musescore.org/en/node/45091
by making the unwanted sign invisible. I'd like to keep the staves linked!
Works fine exept for the lowest string where there is a collision marked in red as suggested in
https://musescore.org/en/node/8125
I simply would like to disable the colouring but found no way, at least when printing.
Does anyone have an idea?
Thanks Matthias
Attachment | Size |
---|---|
String collision.JPG | 47.84 KB |
Comments
Version 2.0.1 b25f81d
In reply to Version 2.0.1 b25f81d by MatthiasM
That red background for fret conflicts is hard-coded in the code, so I strongly fear that at the moment it cannot be disabled.
Can you please file a report in the issue tracker for this feature request, so it does not get lost?
You can try to use a workaround as shown in this attached file, even if the final appearance is not 100% perfect.
How I did it:
- changed one of the G into A (so it jumps on the next string);
- double-clicked on it and adjusted its horizontal position (the position of the stem is automatically adjusted after exiting edit mode);
- made it invisible and silent (i.e. un-checked "visible" and "play" in the inspector).
Ciao,
ABL
In reply to That red background for fret by ABL
You could also use a line (found in the advanced palette) to mimic the stem (and marking the stem of the previous comment as invisible). The linked line must also be made invisible in this case.
See attachment.
Ciao,
ABL
In reply to You could also use a line by ABL
Well, there is a very effective trick to solve this question ... it was enough to think about it! :)
So: the display of your current file:
You may easily receive the expected result:
How? ;-)
Well, make:
1) right-click of the Tab staff -> Staff Properties
2) Edit String Data -> Add a new "fictive" 7th string, tuned exactly as the 6th string, i.e. E2 -> Ok -> Ok
You must obtain this display:
And so, the red squares disappear...
I attach the two .mscz files (I have reproduced your image in these files)
- With 6str: your file1.mscz
- With "7"str : your file2 with 7th str..mscz
EDIT: with the adapted key signature, it's better, sorry... :)
- your file1 in A.mscz
- your file2 with 7th str. in A.mscz
So, with this trick, no more red squares for the notes E, F, F#, G, and G# in unisons on the 6th string :)
Before:
After (adding a "7th string" or, if one can prefer to say: "a double 6th string")
Seems to me this should not be in the exported / printed file, but I see it is. I'd consider that a bug.
In reply to Seems to me this should not by Marc Sabatella
"Seems to me this should not be in the exported / printed file, but I see it is. I'd consider that a bug."
I am also very surprised by this result which I had not remarked in my memory in an obvious way.
It seems there has been a change around the 17-18 February. On February 16, if you begin to save and reload the MSCZ file, the red squares do not display, and so no later also when exporting PDF (this is probably or maybe the reason why this had escaped to my attention?)
In contrast, from 17-18 February, save and reload changes nothing. The red squares remained, and therefore also on the PDF.
This commit could be relevant ?: https://github.com/musescore/MuseScore/commit/802fa8aededb5e3b122950542…
but it is on February 18, and I think I see the same result the eve, with 1 or 2 nightlies (so, February 17), but without commit really obvious (after a beginning of check) explaining this change. This requires further verification...
In reply to Seems to me this should not by Marc Sabatella
I filed a bug #60651: Fret conflict shouldn't be exported to PDF or printed
Hi everybody again,
perfect!
There is a workaround and it's considered for future update.
Thank you very much for promt help!
Matthias
In reply to Hi everybody by MatthiasM
This thread is a wonderful demonstration of what I love about MuseScore and its community :-). Thank you for bringing the issue up.