qtractor

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.

Would it be awesome if the Track -> View/Colors dialog were extended to specify the color used to render ghost notes? As things exist currently, I'd say it probably would be very useful. If however, there are any plans to support multiple ghost note tracks (something I have no interest in but I've seen discussed here and there), it would probably get too complicated and impractical.

Throwing it out there...

Hi Rui, if you want to incorporate it it seems to work fine.

I just had to add the setCursor to your implementation.
Attached is qtractorMidiEditorForm.cpp

___Note:
I have also implemented the click animation (2px cursor offset). Curiously, the cursor size had to be increased for it to work. It doesn't work with native icons but it does with the theme icons. This is certainly a minor thing, and also a bit of a mystery.
___

line 717

Personally I find it very useful to record quantized percussion at beat/4, to quickly sketch out rhythms.

From the midi clip editor I set a loop and overdub.

For everything else, recording quantized, in my experience, is completely useless. It is better to correct parts by quantizing afterwards, or move the wrong notes by hand.

However, the option to quantize recordings is hidden in general options, and it is cumbersome to activate or deactivate.

Just a quick report to suggest Tempo changes are no longer being persisted across sessions. Feel free to let me know what additional information is needed.

Greets,

I (finally) just noticed an odd behavior related to the lsp-plugin windows. I suspect they may share some meta info or something as it relates to persisting window sizes but admit that's just my intuition speaking. Here's how to see the annoying end result.

Unfortunately the MIDI SPP is only accurate on 1/16 positions. Qtractor's position have a much higher resolution. At the moment Qtractor rounds the SPP which leads to non-synchronized positions.

Based on my experiences with jack_midi_clock I propose the same or a similar approach:

When playback starts, then send immediately

• MIDI CLOCK
• MIDI SPP of a position in the future, e.g. the next but one beats or 1/8 or 1/16 position

When this position is reached then send

At the moment the quality of time stretched audio clips is better with WSOLA than with rubberband when I use a factor of 1.5.

Since modern version of librubberband have a v3 API the quality can be increased. It's a bit confusing that – for example in Debian Bookworm – the lib is called librubberband2 with version 3.1.2 and the actual library is called librubberband.so.2.2.1. But there are 2 CLI tools: rubberband and rubberband-r3. So there is alreade the v3 API available.

When playback is running Transport/Backward moves the playhead but doesn't stop playback.

Some recent changes made Transport/Rewind and Transport/Fast Forward stop playback. Is it possbile to change it back to "don't stop playback"?