qtractor

Since I began compiling Qtractor with qt6 I noticed longer start times of Qtractor. Especially on an old Core i5 it takes now 6 seconds until Qtractor is usable. Strace showed that Qtractor (or qt6) scans a lot of dirs, not only in the home directory but also in /usr and /var. It even opens dot-files like .vimrc, makes 1176 stat-calls to /etc/localtime and searches e.g. 2105 times for each icon in many directories including /var/lib/snapd. Having network mounts or links to them in the home dir slows down the process even more.

Hello everyone.
This is a draft of a How-To intended to clarify the use of audio connection tools.

It's intended to prevent us from running into the "self-connection" problem again.

Thanks to the recent forum discussions, I finally understood how the internal flow of the audio architecture is set up...
I've realized that , for example, requests for post-fader sends on the buses are pointless. Those faders were never intended for mixing.

Apologies if it is inappropriate to share this here. Let me know and I'll delete this post.
I wrote a little Qtractor for beginners tutorial and posted it on linuxmusicians.com HOW TOs, Tips & Tricks forum, thought I'd share it here. (https://linuxmusicians.com/viewtopic.php?t=28331)

If we connect the same audio source to multiple input buses, changing the gain on the first one will affect the subsequent ones. It's as if they were nested, related in order of creation, with the first created buses acting as parents of the subsequent ones.

It behaves like a serial signal, not a parallel one.

It does not occur if the audio sources are different.

While this isn't dysfunctional, it does exhibit abnormal behavior. It may be a symptom of a hidden bug.

I've tried both methods, using the Qtractor connections window and also through the qpwgraph.

Currently, I'm using OpenSUSE Tumbleweed with KDE Plasma and X11.

I have Qtractor installed from the Geekos DAW multimedia:proaudio repository. The Qtractor version is 1.5.4, using Qt 6.9.0.

The issue is that when I send the output of one bus to another bus, the receiving bus gets no signal at all.

Apologies for my poor English. I'll try to explain as clearly as I can.

Greetings,

This is the first time I believe I've seen this behavior so I'll attach a few screenshots to help explain.

I have a clip I'm editing which begins at 5.3.000. The clip extends to measure 38 and I'm looping an area of interest as I tweak things. The MIDI Editor's Follow playhead is disabled as I don't want my view to change during playback. The 'midi-editor-1.png` screenshot shows what I have just described.

Greetings all,

I'm seeing this message when starting Qtractor (not using a template).

lilv_world_load_file(): error: Error loading file `file:///home/windowsrefund/.lv2/stegosaurus.lv2/manifest.ttl'

The plugin in question is stegosaurus which I've compiled and installed. Installation adds the plugin to various locations under /usr as well as a single ~/.lv2/stegosaurus.lv2/waves/sine.wav file.

Hi Rui,

please consider including my Mute-patch. The clip's text is placed at the beginning so that it's visible even with small clips.

Qtractor 1.5.3

Steps:
1 Change the proyect BPM
2 Save de proyect
3 Close and reopen
4 MIDI clip content becomes unpredictably out of sync
---

Original

Save

I've attached an example in .qtz: the original file and the saved file.

Greetings, All,

I'm hoping one of you kind and skilled persons can help me figure out how to use the MIDI Velocity Adjust plugin with Qtractor. This was created by Robin Gareus, and is part of the x42 MIDI Filter collection.

The goal is to change all variable keyboard ON velocities from an Arturia Keystep MIDI keyboard to a fixed value, for use within Qtractor (an organ versus a piano). So, this would be global for the composition. I'd like Qtractor just to think it's connected to a plain vanilla keyboard, capable of only sending a fixed velocity for the notes.