qtractor

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.

Hello again Rui.

I've detected what I consider to be a minor bug.

Steps:
1) Activate the record button in an audio track
2) Activate record in the transport
3) Deactivate record in the transport

An empty audio clip will appear.
The expected behavior is that nothing happens, just like the same process in MIDI.

Greetings

When recording audio, Qtractor performs an offset correction on the clip.
However, it is twice the current latency.
The correction should be equal to the latency.

It still wouldn't be exact, but it would be much closer.
I have verified this by entering the value by hand.

I have noticed this while doing routing tests to be able to record the session on a track dedicated to export.

Fabla is the only DrumSampler plugin that allows me to encapsulate samples in presets.

The GUI gives this error in Qtractor. Carla opens the GUI correctly.
´´´
using block size: 512
FablaUI: Warning, host doesn't support resize extension.
Please ask the developers of the host to support this extension.
´´´

If it doesn't have a fix I'll use it without GUI. I just have to leave one instance preloaded in template, since if I load it from insert plugin it can crash Qtractor.
Presets can be made with a text editor.

I've been doing some tests and I've been surprised.

If the session is from scratch, without templates: the sends between buses are done!!! However, they show the following peculiarities.
1) The Master Default bus only supports sending, not receiving.
2) The incoming signal goes directly to the track, it skips the fader and the volumeter. The output signal skips the fader, the volumeter works.

Similar problems were experienced during the development of the new AuxSend. Maybe there was a solution here too.

Hi.. Just returned to Qtractor after a long spell with Ardour.. Suspect my memory is at fault, but I cant seem to get the audio to work in Qtractor properly.
I create an audio (guitar) track, but the only inputs and outputs available are Master. When I play (guitar) I can only hear it from Master, the guitar track I created seems to do nothing. I did get an output from the guitar track earlier (dont ask me how) but it was on top of the Master output and again, I could not get the audio to just route through the guitar track.
In case that was not too clear, I am trying to;

I've had this problem for some time now.

I'm on Ubuntu Studio Noble. It's not just in Qtractor. It's system wide. It happens on Carla too.

The option to load the GUI doesn't appear.

The only one where the option does appear is Hexter, but if you try to load it Qtractor crashes. It also happens with the LV2 plugins ADLplug and OPNplug.

I think I'm missing some library, but I don't know which one...
If anyone can give me some clue it would be helpful.

Hi Rui.
Sharing and maintaining the integrity of projects is difficult.
From time to time we have to reinstall, things change places, we want to share the project with another person, we want to reorganize our resources differently...

This thread is scoped to a difference I'm seeing between Calf Filter and Filter Stereo, the latter being part of the LSP Plugin suite. Realizing I may need to file an issue upstream, I wanted to post here first to see what can be learned.

In short, the data I'm capturing from Calf Filter makes perfect sense as the automation "node" shows a value of 4053.35 (for example).

Here are the exact steps I'm taking to accomplish the above:

Currently "midi clip properties" share an icon with editClip. I think it should have its own icon.

It would make the functionality clearer. Each feature with its own icon.

Example attached.

P.S.
If you don't want to create a new icon, you could at least implement the clipProperties icon call, duplicate clipEdit.png and rename it to clipProperties.png.