re. 1- "exporting" audio is not quite the same as "bouncing": the first is a faster-than-realtime process that run *internally* to qtractor premises; the second is recording the normal playback output in real-time, having the output signal going through *externally* via jack into its own inputs; the actual signal processing path is different in either case, so some slight differences might occur between the two. Not likely as much different but "different" as in theory, for sure :)
re. 2-what you're experiencing is probably leftovers in the plugin own buffers when stopping playback (or export) abruptly at a point where there's still a significant data in the plugin buffers to be rendered out (the remaining "tail" as you say); it is a nuisance, i know, but rather difficult to tackle in general sense, at from the host side (qtractor); sorry about that.
re. 1- "exporting" audio is not quite the same as "bouncing": the first is a faster-than-realtime process that run *internally* to qtractor premises; the second is recording the normal playback output in real-time, having the output signal going through *externally* via jack into its own inputs; the actual signal processing path is different in either case, so some slight differences might occur between the two. Not likely as much different but "different" as in theory, for sure :)
re. 2-what you're experiencing is probably leftovers in the plugin own buffers when stopping playback (or export) abruptly at a point where there's still a significant data in the plugin buffers to be rendered out (the remaining "tail" as you say); it is a nuisance, i know, but rather difficult to tackle in general sense, at from the host side (qtractor); sorry about that.
hyu.
cheers
re. 2-