Re: [Qtractor-devel] Bonne rentrée and more stuff

[Rui N. C. <rn...@rn...>]

go music wrote:
> Hi Rui, I hope your rentrée was OK and that you are ready for more
> qtractor talk since Fainty Diva.
> 
> Here is some more stuff.
> 

i'm afraid, i'm very afraid :o)


> MIDI program/bank select
> 
> 1) When the project was saved with program/bank select values entered
> once in the track properties window, a change to "none"/"none" is not
> kept as such, and the only way of getting rid of that program change
> is editing the xml file, which still contains the entries relating to
> program 0 bank 0. This can be annoying with vst plugins that have not
> all of their program patches accessible via program changes. The
> chunks of Crystal.dll for example are well managed (despite no
> qt-GUI) and qtractor greatly saves its last state with the project,
> provided that no program change is sent. 2) The program number in the
> track properties window is stepped down by 1 when you select a
> program, click on OK and reopen the track properties. The internal
> value seems to be correct though.
> 

yes, this program/select logic in the track properties dialog has its 
annoyances. i'll try to assess and review it asap. thanks for the heads-up.


> Native VSTs
> 
> 3) (BTW very happy that these work AT ALL so thanks very much for
> including this) On sequence stop, the native VSTs I tested (example
> mdaePiano) continue playing, maybe they all ignore 'all notes off'
> events.
> 

hmm. fact is, all-notes-off is not being sent to plugins, only to 
outboard midi devices via output bus/port. plugins should be reset when 
playback stops, which i'm afraid is not being done properly atm. will 
look at it again later.


> 
> And the following are more like questions:
> 
> 4) As the midi ports listed seem to be identified mainly by their
> port number which is part of the name, the reconnection pattern
> depends on the order the devices outside qtractor were
> launched/connected, and so the automatic reconnection fails to
> connect the right devices. Would internal MIDI Port aliasing (like
> you did in qjackctl) be a way to get a better consistency for
> reconnection when a project is loaded?
>

yes, midi clients/ports are being identified by its client/port number 
which might change if clients are started out of the original order. 
good you noticed, that knocks an old sloppy assumption of mine down. 
noted and action will follow soon.


> 5) Moving the loop position (left and right) causes interruption of
> the sequence and I think also audio buffer flush, so I cannot set a
> loop, let it play for a while and then place it to another location
> while it plays. Is this normal and necessary?
> 

yes, changing loop points on-the-fly while playback is rolling is prone 
to glitches, most specially if the new loop-points are set in the 
running playhead vacinity. so that's normal i'm afraid.


> 6) On sequence stop and on mute, qtractor seems to send a global "all
> notes off". I understand that for audio it is necessary to stop
> processing. But for MIDI it would be somewhat more elegant to just
> stop the playing notes in these cases, but this would  require to
> keep a trace of all currently playing notes and you will probably say
> "NO WAY! Too complicated", right? ;-)

right :)


> 
> Ooops I noticed I wrote already something about flushing the midi
> track audio buffers...so put it in the same category.
> 

cheers
-- 
rncbc aka Rui Nuno Capela
rn...@rn...