No work today so I spent much of it out walking in my fave bits of countryside
- which is a great way to clear ones head :)
Anyway, here are a few pix to show what some of the changes will look like
(including the Vkeyboard change if there are no objections).
http://www.musically.me.uk/images/NewBank.png
http://www.musically.me.uk/images/NewPanel.png
http://www.musically.me.uk/images/NewVkeyboard.png
I still can't get Zyn to perform Pan Depth *exactly* as Paul says is intended
but for the technically minded what I'm intending to use is this:
value = 0 - 127
depth = 0 - 127
mid point = 64
adjust = 64 + (value - 64) * (depth / 127.0) // force float during calculation
If depth is 127, adjust is the same as value
If depth is 64, adjust is half the value shift from the mid point
If depth is 0, adjust is the mid point
So that people's existing MIDI files are not affected we'll have to have a
default depth of 127 i.e. no compression of the pan range, which is what we've
sort of got at the moment.
I think I know where to insert this to get just incoming MIDI modified and
that's in MusicIO.cpp SetMidiController. This is a small common point for jack
and ALSA specifically for controllers so shouldn't disturb anything else at
all. Channel, controller and value are all accessible at this point so it
should be possible to target just the wanted part.
Finally, if this setting is changed while a MIDI file is being processed it
will have no affect until the next pan change occurs. Specifically MIDI pan
changes are not stored anywhere, so you'd have no way of knowing what the
previous setting was.
I still don't know if I'll be able to get it in 1.2.2 although I'd like to.
As an aside, I'm wondering if calling it pan *width* would be more descriptive
of what it does.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
