jjceresa

I don't quite understand this "autoconnect" need. Please does anyone could explain anymore what is expected ?

>let me know if this clarifies it. Thanks, now it is clear. As far i know i dont think that "autoconnect" can be implemented for Windows (i mean without a...

>Not sure, why synth.midi-channels is ignored by the winmidi driver. To me it seems like the driver is simply optimistic that the synth will not ignore the 17-32 channels: Yes...

>Well, then "midi.autoconnect" is ignored when "midi.winmidi.device" value is not "default". The winmidi driver still needs to be updated to limit the number of MIDI channels to the same value...

>If the "synth.midi-channels" setting value is 32, then the first device won't have channel mapping, and the second will have a 17-32 mapping. The next device will have again a...

Please, note that my previous message is only relevant for auto-connect set to off.

>Your proposal is to avoid implementing midi.autoconnect at all in winmidi. No at all Pedro. Adding midi.autoconnect is a nice idea, please reread my previous message: if(midi-connect is set to...

About the mixer. > variable naming not very intuitive (buf_blocks, buf_count, current_blockcount ???) Some infos follow:  - `buf_count`: is the number of buffers . This number depends of the...

>AFAIU, your change keeps backward compatibility with your original use-case? Right. The original use case is to have a driver behaviour that makes a straightforward aggregation of the MIDI in...

>You leave a comment in the source code, but this won't help the users. The comments are for developers not for end-users. >Then the user plays both controllers in the...