Everyone else complained about the old behaviour (one track per channel), and I'm not sure if it ever makes practical sense to use this old behaviour. Do you have any use case in mind where your actually need to have one track per channel?

Under normal circumstances it's better when it's per instrument, but when you have more channels for the same instrument (eg. one for left stereo channel, second for right stereo channel), the export merges them together which isn't good. This option might also make you able to export tracks with panning, since that's per channel, not per instrument.
I always could export more MIDI tracks, though. Oh, I didn't think of that... not to mention there's often more than 16 channels in a module, so it would be pretty much necessary.

In your example with a left and right stereo channel, you should maybe just mute one of the channels - it won't get exported to MIDI then. You will have to either do it before or after the export anyway, and doing it before the export will save me from rewriting everything. ;)

This option might also make you able to export tracks with panning, since that's per channel, not per instrument.

Yeah, I found out about that after I submitted the suggestion, but I was wondering if I oculd minimize the amount of MIDI files, it's fine though, in the end they're going to be merged, anyway. :D

About the panning and volume, if I would assign each channel its own MIDI track, it should be fine, right?

If you assign everything to its own MIDI channel, then yes. Assigning everything to its own MIDI track won't change anything though, unless you send every track to its own plugin / or MIDI device. But when playing your file on a single MIDI device, you are always limited by the 16 MIDI channels, no matter how many MIDI tracks you use.

Damn, swapped the terms... I meant channels, sorry. Anyway, I think we (or just I) don't need this feature, anymore. Thanks!