On December 30, 2015 07:37:08 PM Tim E. Real wrote:
> I must mention this: A note whose resultant velocity is zero
>  /after/ applying such things as track velocity and compression,
>  or drum list note volume, will /not/ be sent to the driver for sounding.
> 
> In Audio::collectEvents() for example:
>       velo += track->velocity;
>       velo = (velo * track->compression) / 100;
> 
>  the note is now /discarded/ if the resulting velocity is zero.

(Pushed small correction tonight, controllers weren't being allowed through.)


Oh no.

Guess what guys: 
Not only do I have to merge the mixer makeover branch (if you want), 
 but now I discovered I /must/ merge my midi_engine_fixes branch as well :-o

Here's why: 
The part above, about discarding, works fine except for one thing: 
It discards only the note-on portion but does /not/ know what to 
 do with the remaining note-off portion when it finally arrives.

We keep a record of stuck /playback/ notes, but no record of what 
 /live/ notes have been pressed, so the engine doesn't know that it
 should also discard the live note-off.

Well, I checked, and guess what - my midi_engine_fixes branch
 added... you guessed it, a /live/ stuck notes list !

Yikes - I need that list !

Bear with me while I clean up the branch. This stuff is all for the better.

We'll delay release a month or so while we cook all of this new stuff
 being added by all of us. 
But that's OK I think. Add the big guns now then sit back and let it 
 simmer for a bit. Mmm.


PS: Andrew you asked for a feature? Can you think about throwing
 two reasonable but non-intrusive sized mixer icons onto the toolbars?
I've a tendency to under-use the mixers, coz there not quite at hand.

PPS:
The improved popup menu <more...> thing is cool, I think I like it :-)
But I noticed tonight it had actually moved one of the grey
 title headers into its very own <more...> section.
The title was the 'solo chaining' thing on the input routes button
 of an Audio Input track. There were quite a few Jack inputs and tracks
 and so on, so I think that's what prompted the <more...> to appear.
Possible to fix? Need more info?

Thanks.
Tim.

------------------------------------------------------------------------------
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer

Reply via email to