Qtractor - A MIDI/Audio multi-track sequencer
To visualize it better we stop at a strange BPM of 4 beats per minute.
This is correct
___
Now let's move on to a 3x4, the tempo should not influence the total beats in a minute.
However, now we get only 3 BPM as seen in the image instead of 4.
___
It should look like this.
1.2.0.20git.042593.dirty [develop]
First track imports correctly.
After that it refuses to import clips.
Importing tracks works correctly.
I don't know what to call this feature request so please forgive the poorly worded title.
Greets,
Can the outputs field be highlighted or something when any of the channels are in a connected state? Right now, the only way to know if something is connected is to click on the button in order to bring up the Connections window and scrolling, potentially quite a bit.. By highlighting (or whatever makes sense), the end user would know at a glance if anything is connected.
Hi, Rui. I found one feature request on git. Discussion there is about topics that were recently brought on this forum.
Here is the link: https://github.com/rncbc/qtractor/issues/24
You are saying there: "there's something in the plans, like introducing a plugin-chain
separator as a movable pseudo-plugin insert, representing the fader
controls (volume/pan) allowing for pre-fader plugin inserts (the current
standing) as well as post-fader plugin-inserts.
Snap to grid (e.g. Beat/4) to place clips works fine. But there is no visible grid smaller than Beat as it's in the MIDI editor.
Am I doing it wrong or is a visible grid smaller than Beat not available in the main pane?
Routing has been a bit of a moving target for me. For years I outsourced everything to Carla over many MIDI and audio buses.
Then I switched to pulling the plugins back into Qtractor and only using Carla as a bridge by way of placeholder buses to serve as over-glorified bridges.
I'm investigating how to automate buses and I've found a working way.
I'm sharing screenshots and an example file.
I want to share my doubts and conclusions:
1_
Despite deactivating Control from options, it seems that if they are internal sends from the open instance, the MMCs continue to work.
Aux sends get a bit tricky when we're dealing with sidechain plugins. In some case it can be handled as described in
https://sourceforge.net/p/qtractor/wiki/How%20To%20-%206%20Alternative%20Sidechain%20Workflow%20with%20Aux%20Sends/
Here we show you to apply the concept of "Group", "Auxiliary bus" and "Master" in Qtractor.
This is my personal way of seeing it, others may find other approaches.
MIDI buses are excluded from the article.
We will also cover project start configurations:
Bus types