Qtractor

Hi,

I am enjoying Qtractor immensely.

I am working on editing an audio recording file. I need to remove from the recorded audio file parts that I do not wish to include in my final result. I am struggling to understand the best practices in Qtractor to accomplish this result.

It would be cool if there was a way to enter the latency of the returned signal in milliseconds and/or samples. If the Insert Send is active then this latency should be displayed in the track's plugin tab and be compensated if Latency Compensation is checked.

This would make it possible to insert external soft- and hardware devices in tracks and get their latency compensated.

If there were a 'single window position' option for the MIDI editor, working with Qtractor would be more fluid.

That is, instead of each editor window saving its own position, all MIDI windows would save and set the last position.

It should be optional, of course, because the current behavior might be interesting for certain workflows.

I don't know if it's possible, if it's worth it, or if it's of general interest... :)

To try different snare sounds I load different samples into drumkv1in a MIDI track and place midi chromatic transpose from x42 midifilter plugin suite before it. That works fine. So I can choose the snare sound when transposing the MIDI data.

But I noticed that drumkv1 makes no sound if midi chromatic transpose is placed after drumkv1 (which happens when inserting it) and activeted. When I deactivate it then drumkv1 gets the unchanged MIDI data.

Why can midi chromatic transpose have any effect on the MIDI data of drumkv1 when its position is AFTER drumkv1? Is this a bug?

https://sourceforge.net/p/qtractor/wiki/How%20To%20-%2013%20Make%20Succ…

Seeing that the topic of audio interconnections remains confusing, I've expanded the How-to a bit.

I've shown how to "render a final master" and ways to create virtual devices that bridge connections.
I've even shown how to make these virtual devices permanent so you can save the connections in Qtractor templates.

Rui, this FR is for a straight line draw tool in the midi/clip editor, to be used in CC lanes. The user selects a start point with the mouse then, with the mouse button still held down, "draws" to an end point. When the mouse button is released, a line of events appear between the two points.

We currently have three drawing edit options, OFF/ON/Draw. If you want to maintain those three, then i respectfully suggest adding the option of a modifier to the Draw tool. The user would then press something like CTRL or SHIFT, and hold that key down while operating the mouse.

Hey, it's me, the nitpicker again. And I hope I have finally an issue regarding audio clip position in time that's easily reproducable.

Greetings,

These are the only two modes I currently use in my workflow. I bind Select Mode/Automation to a and Select Mode/Clip to Shift-a. This is perfectly fine but I do fumble from time to time in my attempt to select a clip when I forget I'm in Automation mode. Again, not a show stopper. That said, here's the feature request.

Hi Rui, Having spent time setting the patch (program change) for the tracks that I am using. I find every time I copy or edit a clip or create a new clip, Qtractor will write the Program Change info into the start of the new clip midi file. This feature will break any future changes I make to the Track properties. This becomes annoying when a clip ends and opens another clip on the same track. Is there a global way to tell Qtractor to ignore the file Program Change info and use the setting of the Track -> Patch properties or can Qtractor not write program changes to the midi file ?

Hi everyone,
I apologise, but I am unable to understand how aux buses work:
once I have created the buses, added effects and connected the tracks to the aux buses, how do I reconnect the aux output to the main master output? I tried using routing (connecting the aux outputs to the master inputs), but something is not working.
In other words, how do I merge the master and the various aux buses together during the final rendering if the routing I described above doesn't work?
Thank you very much, have a nice day.