Greetings ya MusErs!
Dennis check it out. Check the General Settings / Midi tab now.
(TODO: Maybe still sending out controllers between songs,
must check why controllers are being sent BEFORE my warning
box pops up - I didn't tell them to - suspect when clearing/loading
a new song it sends, possibly due to cursor movement.
Anyway the infrastructure is now there, we'll work out any
quirks.)
One point: Even with Send Midi Init and Send Default Instrument Values
settings turned off, I STILL always send out any values that are in the song.
After careful consideration I reasoned that if a controller is in the song,
and it's not currently 'Off' then it should be sent otherwise if one starts
playing the keyboard the wrong sound would be heard.
In other words WYSIWYG - the value shown must match that of the device.
But rest assured it wont send all those instrument-defined defaults if
the controls are 'Off' like before, if you tell it not to.
In other words, load a song, MusE sends a few non-'Off' values
"here and there" that are at the current location in the song so
you can begin playing immediately.
(Well actually the chosen 'Metronome click port' may still send all
controllers. I think I remember why, must investigate.)
MusE now inits only on ports AND their channels that are used in the song.
Before it would send on all channels.
Anyway turn on ye olde -M and -m options to see for yourself
what's really being sent and received.
Hope it helps. I took great care in rewriting the whole init thing.
I think it makes more sense now, especially without Song Type.
The menu "Midi -> Init Instrument" has also been improved to
mirror these same operations. Basically does the same thing
except FORCES it ie. no warning box.
It initializes the instruments, yet obeys your Settings choices.
** Bonus: Midi fans: You'll see what I mean when working with controllers.
I did it because users like Dennis may wonder "why is this thing
sending out controller values - what's happening?".
Now you have visual and quick operational solution to turn the
'offending' controllers to the manual 'Off' state so they don't send
or store a manual value.
Got it in on a Friday, too. Hope you guys get to try it on the weekend.
Cheers. Tim.
----------
For the impatient and squinty-eyed, the ChangeLog:
* Improved: Midi initializations. New settings options, can be
'quiet'. Complete rewrite of initializations coding.
* Improved: Midi controller graphs: Control selector 'S' popup now
stay-open, AND NOW with multi-coloured dots:
Blank: Controller has no current 'manual' value (it is
'Off'), and no stored automation values.
Blue: Controller has a current 'manual' value (it is
not 'Off'), but no stored automation values.
Green: Controller has no current 'manual' value, but
does have stored automation values.
Gold: Controller has a current 'manual' value AND has
stored automation values.
Bonus! Pianoroll and drum edit 'Ctrl' buttons ALSO now
popup this very same menu. No more clumsy
adding of controllers - now just hold the ctrl
key and select away and... "bing bing bing 1 2 3".
* Improved: 'Old' drum track 'drum controllers' display and
operation: Fixed several problems: Incorrect mapping to drum map etc.
Now if more than one drum is pointing to the same
'anote', the others are overlaid as grey slivers. (TODO Not quite done.)
TODO: Although THESE "drum controllers" are improved,
there are conceptual problems with NON-drum controllers old drum map:
If a NON-drum controller such as pan is adjusted,
what then? If the drum map contains more than one port/channel/anote
it should be sent to ALL of them BUT we would like
a 'track override' which when turned off, 'pan' could be locally
adjusted for EACH drum having different
ports/channels/anotes. (So in theory drum track channel should be reinstated.)
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
