A MIDI/Audio multi-track sequencer
I've noticed some translation errors.
The most serious is "Pich Bend," which appears as "Portamento," when they are different things.
The translation is "Inflexión de tono", however, since it's a technical term, I'm not sure if it should be kept as "Pich Bend," which is how everyone knows it, even Spanish speakers.
I've translated it as "Inflexión de tono."
The other two were typographical errors.
I've attached the file.
Seeing that some people still have questions about working with multi-channel percussion instruments, I've added a new section 3 to the "How To 13...".
// While writing it, I checked if carla.lv2 could save presets in Qtractor format, and it didn't work. I don't know if it's a bug or how it's intended.
EDITED: Yes it works... sorry. I was confused because the load preset button appears, which shouldn't be in LV2.
...
If you see anything incorrect, please let me know.
When we minimize a track, several elements disappear (track number and volumeters), however, the track name remains behind the track buttons... and it doesn't look very nice XD.
If the pseudo-plugins (they all perform a send function) were the same color as the audio, and the MIDI pseudo-plugins the same color as the MIDI, the "sends" could be much more easily distinguished from the actual plugins, which would help to have a clearer overall view.
In Qtractor the LSP limiter (stereo and mono) gives different results depending on its format:
LV2: always correct
VST3: always 5 ms regardless of the lookahead time
CLAP: always 0 ms regardless of the lookahead time
I tested the VST3 in Ardour and the latency determination was correct, so it may be a Qtractor bug.
I couldn't test CLAP in Ardour so I can't say if it's a LSP or a Qtractor bug.
We have a MIDI Controller pseudo plugin.
How cool would it be having an OSC Controller pseudo plugin for automating other stuff like plugins in non-mixer-xt?
Answer: very cool :)
I think we had the same with Insert Sends.
When I move or copy an audio Aux send from one bus to another then its destination is set to "(none)" instead of preserving the old destination.
I'd never done this before, so I didn't notice it.
If you drag a file (MIDI, audio) to the track header, it imports it wherever you want (which is great)... However, a window pops up asking you to save. If you save, it imports the file, closes the session, and opens a new one with the file. What?! ?¿?¿?
If I wanted to import, why does it close the session?
If I wanted to open the file, why does it save it in the previous session?
The window is completely unnecessary and causes unwanted behavior.
Create a new session without a template.
Create a track.
Import audio.
Select the clip.
Set the clip to loop.
The audio becomes inconsistent, randomly appearing and disappearing.
The problem disappears.
I think I've found a workable way to solve the problem of not being able to use bus faders for aux sends.
Add a checkbox to the properties of the aux sends:
[ X ]Apply track/bus gain/pan values to the aux send.
It would work like this:
Before applying the "send gain," it would take the current gain value (just the number) and apply the same gain formula used by the bus. The same goes for panning.
Then, the send gain of the aux send itself would be applied.
Just sharing my progress.
Qtractor.cpp line 159:
sLocPath = (QDir(QCoreApplication::applicationDirPath()).filePath("../share/qtractor/translations"));
This allows Qtractor to always find the translations, even if the local installation directory changes.
You just need to respect the structure: bin | lib | share.
---
QtractorOptions.cpp line 72: