Add new comment

Re. 1... move notes in piano roll...
- Yeah there's a snap-to-beat mistake all over moving and pasting multiple events that will get fixed ASAP. The way it will get round is that only the anchor event (eg. the one you're point-n-dragging with the mouse) gets snapped/quantized effectively, all others will just move and placed in their relative positions to each other. Guess that's what you really mean. Watch for qtractor 0.4.3.1463, in svn trunk tonight ;)

Re. 2... one midi clip and [multiple] instances of it...
- IOW this is what has been discussed under the subject of linked clips. Right, hasn't met any implementation to date. Still lingering in the (un)official TODO list :)

Re. 3... Paste repeat...
Somewhat related or quite similar to 1. but already thought fixed in a recent svn commit (one week ago). The repeated pasted clips were being quantized to current snap-to-beat setting. This behavior would cause some of the pasted clips to be misplaced and even overlap. Not anymore or so I thought. The paste-repeated clips are now simply concatenated, one after the other. BTW, which version are you testing?

Re. 4... Loop mode - either midi or audio.
Please, can you elaborate (with step by step detail) on what you are trying to achieve? What MIDI driven synths, samplers are you using? Either plugins, external or even outboard hardware? What system/studio setup? Truth is, every case is a case and what's fair game to one side of things (eg. plugins) it is not quite the same for others (outboard hardware). The sync'ing issues, latency, jitter differences are abysmal so that one cannot even talk on such a thing as perfect loop mode :) Throwing more gasoline to the fire: Have I told you that Qtractor does NOT have any kind of latency compensation whatsoever, yet? Yeah, too much to swallow in one take, sorry :)

Re. 5... putting audio clips during playback, they go out of sync
Well, that can happen, I know, specially when in loop-playback mode and one tries to cut, move or paste clips over the playhead and worst, when the later is nearing the end of the loop range. Although these editing actions are possible and allowed, I would not recommend this kind of operation in a, er, live oriented performance. It's way too risky anyway. It has been reported to crash without warning though (ain't all crashes like that?:). Don't even think of doing any of the sort while recording is engaged :/

Anyway, and ever again, if you can isolate any reproducible steps or behavioral patterns that lead to the problems you're facing, the least will certainly help a lot. Relax. It might help me doing a lot better than covering all this mess with some lousy excuse ;)

Cheers