qtractor

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.

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.