Add new comment

all your questions are considered normal behavior, so nothing is flawed on your side :)

MIDI tracks in qtractor timeline are not the very same as MIDI file tracks (SMF MTrk header chunk)--there's of course a mapping between qtractor MIDI tracks and MIDI file tracks and/or channels, which is not always a one-to-one (1:1) business, grossly depending on the SMF format type in effect on export time (see View > Options... > MIDI > Capture / Export > File format).

you can argue that on SMF Format 1, track names are actually set on the exported file (one MTrk chunk per channel), while they are not on SMF Format 0 files (one single MTrk chunk for all channels). however, qtractor creates one MIDI track for each MIDI channel that it finds present on an imported MIDI file, giving it always the same name derived from the base filename, no matter it's a SMF Format 0 or 1.

yes, qtractor stores its automation control data series in a pretty regular SMF, named after *curve*.mid files. so it stores automation data points as MIDI controller events alright but these are NOT performance data from MIDI clips on regular MIDI tracks: they're just control data and should be one "curve.mid" for each track, be that an audio or MIDI track, that has at least one automation curve defined.

and yes again, MIDI clip events, the so called performance data, are of course stored as SMF as well, but this time it's one .mid file at most per MIDI clip--as against to automation curve .id files which are exactly on a per track basis.

and finally, all this said normal behavior is not specific to qtractor 0.7.9: it's just like so for ages and keep counting :)

hth.
cheers