no. i'm saying that it depends on the MIDI instrument or plugin that is being driven by.
although, there are some MIDI (N)RPN in the known standards (GM, GS, XG) that comes to mind, which makes up for pitch-bend sensitivity or range (usually in semitones or cents for full-swing or scale) to be set on-demand, a possibility that only gets effective if , and only if, both of the following conditions are met:
1) those pitch-bend range/sens. instructions or messages must be part of the MIDI file being played or sequenced: qtractor will duly pass them on to the instrument, but...
2) the instrument (or plugin) must recognize and react to those messages and set its own pitch-bend scaling factors to fit the desired range or sensitivity upon rendering the normal MIDI performance pitch-bend messages: which as I've demonstrated, are being handed out properly by qtractor, as long there are any in the MIDI sequence, of course.
byee
WAIT! I think I see the problem now: the file "Eagles_(The)_-_Hotel_California.mid" seems to be formed under the MPE (MIDI Polyphonic Expression) specification... alas, qtractor doesn't support the MPE spec. in fact, in qtractor terms and convention for MIDI sequencing, the file is just malformed and thus it wouldn't ever play it right, no matter which instrument or plugin you throw at it, even though the instrument have to support and accept switching into said MPE mode too. sorry :)
so, after all we were both misguided after all this time. it wasn't ever about pitch-bend or not: it was all about MPE instead, that I repeat, qtractor does not conform or accepts.
to my knowledge, there are none of open-source applications (on GNU/Linux at least) that support MPE to date. there are some, non-free, commercial ones that might (bitwig, reaper, and so on...). same for instruments, plugins, unfortunately, whatever.
anyway, I don't know how far and that said support goes on other commercial software, but one thing I'm sure: qtractor doesn't, sorry again; only conventional MIDI files and sequencing do work, which boils down to one rule: one track, one channel, one instrument, one patch.
no. i'm saying that it depends on the MIDI instrument or plugin that is being driven by.
although, there are some MIDI (N)RPN in the known standards (GM, GS, XG) that comes to mind, which makes up for pitch-bend sensitivity or range (usually in semitones or cents for full-swing or scale) to be set on-demand, a possibility that only gets effective if , and only if, both of the following conditions are met:
1) those pitch-bend range/sens. instructions or messages must be part of the MIDI file being played or sequenced: qtractor will duly pass them on to the instrument, but...
2) the instrument (or plugin) must recognize and react to those messages and set its own pitch-bend scaling factors to fit the desired range or sensitivity upon rendering the normal MIDI performance pitch-bend messages: which as I've demonstrated, are being handed out properly by qtractor, as long there are any in the MIDI sequence, of course.
byee
WAIT! I think I see the problem now: the file "Eagles_(The)_-_Hotel_California.mid" seems to be formed under the MPE (MIDI Polyphonic Expression) specification... alas, qtractor doesn't support the MPE spec. in fact, in qtractor terms and convention for MIDI sequencing, the file is just malformed and thus it wouldn't ever play it right, no matter which instrument or plugin you throw at it, even though the instrument have to support and accept switching into said MPE mode too. sorry :)
so, after all we were both misguided after all this time. it wasn't ever about pitch-bend or not: it was all about MPE instead, that I repeat, qtractor does not conform or accepts.
to my knowledge, there are none of open-source applications (on GNU/Linux at least) that support MPE to date. there are some, non-free, commercial ones that might (bitwig, reaper, and so on...). same for instruments, plugins, unfortunately, whatever.
anyway, I don't know how far and that said support goes on other commercial software, but one thing I'm sure: qtractor doesn't, sorry again; only conventional MIDI files and sequencing do work, which boils down to one rule: one track, one channel, one instrument, one patch.
apologies for all the fuss :)
cheers