I have found a way to make both staffs become compatible. (all tritones go
down)
It is a fairly big workaround, but works!
I kind of followed my previous idea.
> So, maybe, if I export the chromatically written music to MIDI, open it
> with encore or finale, adjust the key signature, then exporti
> Well, it is not a big problem anymore, i actually found a way to get both
> chromatic and traditional notations in the same file with the dodecapitch.
> It would just make thing easier.
>
> [...]
>
> its like starting a new file in the same page.. So when I click engrave,
> it displays both.
Well.. i may still think in a way to get that compatibility.
But for now, i think i will use the chromatic names with dodecapitch thing,
and keep the tritones to be manually corrected whenever I need the
traditional staff. Hopefully never hahah!
I think it is easier than keep in mind all the correc
> This makes it easier to input and read, and then when using your music on
> a traditional staff, you can just set these variables to an empty music
> expression, and they will have no effect on the music.
>
> extendStaffUp = {}
>
> That way you only have to make the change in one place inst
>>(Rookie scheme tip: a single quote (') is not the same as a backtick (`).
This tripped me up!)
did i use the wrong one somewhere???
ok, now... For my taste, the way i did for solving the Chromatic/traditional
notation compatibility is satisfying. Extra note names could be added so you
can inp
Hi, earlier today i just copied/pasted this to my file, and it worked fine.
All tritones go down.
I didnt really understand what the hell that code is doing, but worked the
way i want.
---
/dodecaPitchNames = #(map (lambda (pitchname)
I think i have all i need now, it will just take some time to digest.
About the \include, can i just add my chromatic.ly language files and other
templates to this directory, instead of having a copy with every musical
file I make?
/"Files which are to be included in many scores may be placed in
