qtractor

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:

• Default: a single group-type bus
• Expandable: facilitates the expansion of groups, auxiliary buses and management of the Master bus.

Bus types

I found a complicated bug during testing, which is unlikely to manifest itself in a normal work process.
It's not a big deal. It doesn't affect the functionality, just the interface. Saving and opening the session again fixes it.
I'm reporting it anyway so it's known.

Playback:
- Deletes a bus that has tracks associated with it.
- Deletes a track that was associated with the bus.
- The track doesn't disappear from the mixer.

I don't know since when this has been happening, but it's a recent behavior, maybe since Qtractor version 1.0 or 1.1.

Midi clips have an anomalous behavior when shortening from the left.

Instead of shortening, it moves, as if you had selected the entire clip to move it.
If you move the clip, it is corrected.
If not, it stays moved and not shortened.

Commit 3171791:
I'm working on a new song without incident.
It seems that the indirect loop suppressor fixes the bugs that were coming up.

Let's see if anyone else is willing to do some testing so that we have more guarantees.

I'll keep working with this branch to detect any incidents.

Related:
Since we're working on sending, I'm going to suggest a new request.

Hello. Is it possible to implement functionality that is shown on the image below? This is absolutely not a request. I just wanted to know if it is possible and is it considered valuable. Ardour, as far as I know, also is not capable in this regard. Maybe, there are some technical limitations or it is too sophisticated to add?
Thanks in advance