qtractor

I think there is a simpler solution.
I appreciate the effort anyway.

---OPTION 1---

The simplest solution:

If we create a "comments" property on tracks the need to have to put long names disappears.
I think implementing a new property on tracks is less effort than what you have had to do.

Hi and a happy new year,

not sure if this is a Qtractor or PipeWire problem, I am trying to use PipeWires resampling for recording. Here is my setup:

I bought an Intech Studio Grid TEK2 MIDI controller. It can be programmed to send MIDI data when pushing buttons or turning knobs and to do things like switching on/off LEDs.

Is it possible to automate buses with the Qtractor automation tool?
Of course, Qtractor offers you enough modules so that you can do almost anything possible.
You just have to create the way (the workflow) to achieve it.
You just have to combine the automation tool with the CC control tool.

(As a transmitter event we have the 7 volume and the 10 panning. I will continue investigating how to use more. On the other hand, the receiver can be any element on the bus)
*See P.S. 2

Hi Rui,

my Linux Mint (24.04 based) system with the PPA does no longer get the actual version of qtractor because of librubberband3:
The following packages have unmet dependencies:
qtractor : Depends: librubberband3 but it is not installable
E: Unable to correct problems, you have held broken packages.

Is there a way to use Linux Mint with your PPA?

Frank

Before I file a bug report I'd like to discuss it here:

The audio metronome is exact and in sync.
But the MIDI metronome is not in sync to anything.

Is it on my systems only?

Hi, Rui:
I propose to rename it to "collaborations" or something equivalent that makes clearer the generic functionality of a place where anyone can collaborate without putting the master or development branches at risk.

Honestly, I'm a bit embarrassed, and it doesn't make much sense when I'm not able to contribute due to knowledge limitations.

When doing some fine tuning on audio clips View->Zoom->Max Ctrl+0 would be really helpful.

Yesterday I did some heavy editing including clips in choir tracks (similar clips in multiple tracks).
It would be cool if crossfade was applied on the selected clips in multiple tracks, similar to mute and split.

Uncrossfade (Fade in and out set to 0) would be helpful, too.

I think that the mute information is more important than the clip name. So I suggest prepending "[Mute]" instead of appending to make it visible even on short clips.

It's in qtractorClip.cpp at QString qtractorClip::clipTitle

I use

sClipTitle = QObject::tr(" [Mute]") + std::move(sClipTitle);

instead of

sClipTitle += QObject::tr(" [Mute]");

Since I have lots of short clips I would even prefer "[M]" instead of "[Mute]".