Posted
Sometimes it takes a while to understand things, even for me. I just realized that the way KIM generates octaves is wrong (and also the way I happened to notate them until now). A diatonic step of 7 or -7 denotes an octave only when the underlying scale has 7 steps. And possibly, sometimes also voice leading constraints may get in the way.
The correct way to notate octaves obviously is to use a chromatic shift of 12, -12 or any multiples thereof (slap on forehead).
I amazes me how sometimes the most basic things can be so elusive, although they are right in front of your eyes.
Mon, 2022-11-14 - 11:23 Permalink
It is still human work , because you are not a machine....
Knowledge sinks in if you don't maintain it that's how the brain works.
Yesterday I did some work with Orb composer and it's kind of easy if you can generate a motif straight from an instrument track, but yeah that won't work with the factories I guess?
But with a library is more versitale.
I tried to generate a piano motive with a line or phrase factory ?
The phrase (possible to do) adjustments in Orb composer is done well, maybe a idea for Synfire?
Tue, 2022-11-15 - 08:53 Permalink
It means that if you want an octave interval, for instance starting from zero, you'll set diatonic=0 chromatic=12 for the second symbol instead of diatonic=7 chromatic=0.
This is merely a reminder to also consider the chromatic shift when editing phrases. The factories will be fixed to do so.
Tue, 2022-11-15 - 09:09 Permalink
> I amazes me how sometimes the most basic things can be so elusive, although they are right in front of your eyes.
Thanks for honestly sharing, and for keeping working on improving even the foundations!
(Working on modelling compositional knowledge myself for a very long time, I can related how tricky it is to revise fundamental design decisions.)