pon., 25 lut 2019 o 21:37 Christian Schoenebeck
napisał(a):
> What do you mean with common interface released?
By final solution and common interface I thought about adding
parameters you have already mentioned (amount of voices per key group,
and whether a key group shall use a soft release or
On Montag, 25. Februar 2019 21:05:22 CET Jacek Roszkowski wrote:
> pon., 25 lut 2019 o 19:10 Christian Schoenebeck
>
> napisał(a):
> > From what you described so far, I don't see why you would need to open a
> > separate concept to the existing key group conflict concept. As far as I
> > can see
pon., 25 lut 2019 o 19:10 Christian Schoenebeck
napisał(a):
> From what you described so far, I don't see why you would need to open a
> separate concept to the existing key group conflict concept. As far as I can
> see it, the key group concept just would need some additional options for
> allow
On Montag, 25. Februar 2019 16:56:33 CET Jacek Roszkowski wrote:
> napisał(a):
> > Then it might make sense to extend the existing key group handling code by
> > optionally using the number provided by the patch. You might want to have
> > a
> > look at AbstractEngineChannel::HandleKeyGroupConflic
niedz., 24 lut 2019 o 23:34 Christian Schoenebeck
napisał(a):
> Then it might make sense to extend the existing key group handling code by
> optionally using the number provided by the patch. You might want to have a
> look at AbstractEngineChannel::HandleKeyGroupConflicts().
That method was my s
