Hi,
I have just inputted Fmin add9 in the chord symbols.
I can’t understand why this behaviour is happening:
Thanks
-m
I am also seeing this behaviour which I don’t understand, in the chord symbols editor:
Looks like the brackets are “hidden” ?
With any chord symbol issue, we really need to see the file, even if it’s just cut down to a single bar that shows the issue. There are too many ways to have modified chord symbol elements, so it’s really impossible to know what’s been done without seeing the file. If you can post a cutdown file here, we can take a look.
4 Likes
When I load your project. I get these font warnings.
When I just click OK, I get this
So I guess it has something to do with the PetaChords symbol, which I have not.
I have bought the Scoring Express templates and started from them…
Sorry, I don’t have your fonts either. You have a gazillion manual overrides in your chord library though …
If I remove all the left-column manual overrides and set the Chord Symbols Font to Helvetica, I get this:
So the fact that those parentheses aren’t appearing is either due to a manual override that you have done, or an issue with the location of those glyphs in the font you are using.
4 Likes
Thanks,
Yes it’s true, I am investing (and occasionally feel like I might be wasting…) an enormous amount of time to make the chord symbols appear professional and readable.
This issue I have just encountered yesterday was not there a few months back so perhaps it has to do with an update. I should probably contact Scoring Express to ask about it too…
Did you update the templates, or fonts?Or did you add more customizations?
In the mean time, you undoubtedly gained more knowledge in this field. It might be the best in the long time, to start all over again, remove all those overrides, and use that knowledge to go through to engraving options so the result is almost what you would like, and just then do the fine tuning with those overrides.
2 Likes
Unrelated and no offence, but I think you misunderstood how tokens work. The tokens belong in the text frames in the page templates, so that when you write regular text in the project info dialog, the tokens get replaced by the info text. Or perhaps you just wrote them there as a reference.
Jesper
1 Like
Thanks, but that is definitely not my case.
As I am starting from their templates, which I always update as well when they release them, and that I also use in Sibelius. The problem is that Dorico requires to tweak almost every possible chord or chord inversion in order to get to a professional looking result. I decided to do it and take some time to tweak every chord I need to input and come across as needing tweaking.
It has been working out well so far and I considered it an investment into my work in Dorico…it’s just this new hiccup I came across that looks like an anomaly (especially since it looks differently whether I click and select it or not).
I have contacted Scoring Express in the meanwhile.
That’s unexpected for me. I would guess that if you pay Scoring Express for their templates, they should have done that tweaking for you.
Hope you get a solution from them
they were there in the template I bought and didn’t even look into it yet actually
Hm, strange that they put them there. Maybe for reference, so that you know what to put into the text frames.
Jesper
Philip’s just asked me to take a look at this, as it’s me that built the Dorico Scoring Express Templates. I’ll do so in the next hour or so, though looking at this thread it seems you may have been down quite a rabbit hole editing things in such a way that they don’t really work in the way we intended. Still, I’ll see what I can do!
@jesele, the tokens within Project Info work in such a way that (in a single flow project, at least) it doesn’t matter whether the user types into the Project fields or the Flow 1 fields - the tokens on the page will always populate with the information. Flow fields can automatically resolve to Project Tokens if you ask them to!
3 Likes
Thanks, didn’t know that @pianoleo
Jesper
The specific override that’s causing this behaviour for your F-(add 9) is the All roots min(+alterations). If I select the white parenthesis behind the “a” of “add 9” and edit it I can see you’ve coloured it white. Same goes for the right bracket.
Looking at the quantity and type of overrides you’ve made in Library > Chord Symbols > Chord Symbols, I’d suggest resetting all of those individual overrides (using the reset button in the bottom left, to the left of the trash can), and then working in the following order:
- For general appearance of chord symbols (e.g. whether they use a minus or an m for minor, parantheses for alterations etc.) look in Library > Engraving Options > Chord Symbols. Get this right first.
- For kerning (the positioning of accidentals, alterations, bass notes under a chord etc.) look in Library > Chord Symbol Kerning Pairs. These pairs are the positioning of any one glyph relative to any other glyph, and are recycled wherever that pair of glyphs occurs, across all chord symbols. I’ve spent multiple hours getting the kerning the way I like it within the Scoring Express templates, but obviously it’s subject to opinion, and if you’re using styles of chord symbol I’ve not accommodated (such as minus for minor, rather than ms) these may need some tweaking.
- If you’ve exhausted the options above, make overrides in Library > Chord Symbols… but use the Apply To All Roots button in the bottom left corner wherever possible. Note that if you edit a chord symbol component, those edits will apply to that component wherever that chord symbol component is used. For instance, if you edit the flat glyph in an Eb chord, even though the override may be assigned to only Eb chords, the component edit applies to wherever that particular flat glyph is used (Bb chords, Ab chords, Db, Gb etc.). If you want to make an edit to a component in one chord only, use the plus button to create a new custom component, edit it as necessary and don’t assign it to any other chords.
4 Likes