Qtractor

Usually I have no problems merging audio clips. But when testing drum samples I tried to merge them. Qtractor crashes both on my oldish system and Debian Trixie.

See example session.

Can you reproduce it?

Hi,

I am using Qtractor with my audio work. All is fine with my efforts, but it would be nice to have the final work louder. I am unable to accomplish louder without having my work being distorted.

I record and add effects where all signal lights are either green or yellow. What do I need to share about my setup to contextualize my working environment? Is there an effect I can add to the end of my signal chain to accomplish the loudness?

Kindly,
Stephen

For some time now we can chain audio output buses with no latency via aux sends, eg
track -> audio output bus 1 -> audio output bus 2 > master audio ouput bus

This works fine but it's not very intuitive for new Qtractor users, they will probably use the outputs button. And the fader has no effect and the LED meter is misleading..

So my proposal is:

Hi,
I have a question about Qtractor and desktop environments—or rather, window managers—for X11 and Wayland.
Is it generally better to use Qtractor (which is built with Qt) with Qt-based desktop environments like KDE and LXQt, or is there no difference compared to GTK-based alternatives like GNOME and XFCE? Would the system load be lower? Would Qtractor be more stable or perhaps perform better?
The same questions apply to window managers under X11 and Wayland: is one preferable to the other for Qtractor? Does Qtractor actually support Wayland?

There are a few things I don't understand.

When the option is enabled, a window appears to select the type with an option to not ask again.

However, even when it's enabled, it still asks again if you load a new instance. If I've already specified that I want that particular plugin with a specific GUI, it should logically apply the option to all instances.

On the other hand, it only remembers it per session... instead of for general settings.

When an audio clip has an offset then the time stretch/squeeze after a tempo change works but the offset is changed although it shouldn't.

See example session http://suedwestlicht.saar.de/download/tempochange.qtz

Steps to reproduce it:
1.) Place an audio clip with offset on an audio track
2.) Copy that clip to a later position
3.) Add a tempo change between those 2 clips
4.) In the 2nd audio clip the offset has changed but it shouldn't

At the moment Qtractor does it for plugins and insert sends in a track. Putting a limiter with latency in a bus is not compensated.

How about including the audio bus that a track is connected to? I think of 2 lines in a track's "plugin"-tab instead of the one that's there now:

[ ] track trackname latency compensation (current value)
[ ] bus busname latency compensation (current value)

In this case it would make sense again to add the latency input for insert sends in buses.

What do you think?

Hello everybody,

There is a successor of the Calf plugin suite: CalfNXT. As I understand they run the GUI in a separate process to avoid problems with other toolkits/versions.

I managed to build them on Debian Trixie. They load and work (including GUI) in Carla and non-mixer-xt. But Qtractor (build from Git on the same machine) crashes immediately when I load one of them.

Not an urgent problem but it would be cool if Qtractor users could benefit from the next generation Calf plugins.

This only happens in the appImage, not in the compiled version.
It doesn't happen every time, but it is frequent.
Interestingly, it doesn't happen with Calf Suite, but it does with most plugin GUIs, apparently only LV2.

Steps to reproduce:

1. Load a synthesizer on a MIDI track.

2. Load an LV2 effect plugin with a GUI afterward (LSP, GX (Guitarrix, etc.).

When you close the effect's GUI, sometimes Qtractor crashes.

This doesn't happen if: