Re: [Lmuse-developer] Midi users: Opinions needed: Meaning of midi track mute?

[Florian J. <fl...@wi...>]

On , Tim E. Real wrote:
> I've hit a bit of a snag I can't seem to decide.
> Some users may prefer to keep midi output traffic a low as possible.
> Other may prefer that features just work even if it may mean more 
> traffic.
> 
> Should midi track 'Mute' inhibit sending of *all* midi messages to the
>  track's output port?
> Or should 'Mute' inhibit only *notes* but allow all other message 
> types,
>  like controllers, to *always* pass through?

I want both!

I think, they should be set "on", "muted" and "off"
"mute" sends everything except notes, while "off" sends nothing at all 
(except pending note offs to prevent stuck notes)


> So there are two solutions - my indecision:
> 1)
> When a track is muted and midi controller input is received or played 
> back,
>  *do* allow it through to the *output* device so that the knobs can be
>  updated and represent the true state of the output device as we know 
> it.
> Drawback: Traffic! With many midi tracks driven from the same input,
>  or when simply playing, even with the track *muted* there's gonna be 
> traffic
>  on those outputs !
> Advantage: Output device, even hardware, always has truly current 
> controller
>  values even while track is muted.
> (Note: If and when midi automation modes are added, OFF mode would 
> typically
>  inhibit sending of midi graph data - there is currently no such 
> inhibition,
>  except when muted of course. But that still leaves the problem of 
> live midi
>  controller data from midi inputs.)

this!


> 2)
> When a track is muted and midi controller input is received or played 
> back,
>  use the mechanism above to *update* the GUI controls but *not* send 
> midi
>  to the output, thus keeping the output lines quiet.

no!


> Lastly, there is our TrackInfo 'Midi Through' button !
> Here's a confounding case muddying all of the above. We simply 
> *cannot*
>  send anything to the output device when midi thru is off and yet, we 
> would
>  like the knobs to at least show us what might be arriving at inputs
>  (playback is sent normally, thru does not play a roll there).

this should not be a special case. Either, the knobs display the 
output's state.
Then don't update them in this case.

Or, the knobs display what is actually stored on the track (this is my 
preference).
In this case, always, even when the tracks are "off", update their 
meters/knobs.

>  Commits hopefully soon. See ya!

cool. => git :)
see ya too :)

florian