The reason I'm using loops (bus outs/ins) is because, like Carl, I cannot get my initial buses (e.g., Audio1, Audio2, etc.) to be heard as inputs to another bus (like AudioMix), nor can that output be heard by the input of "Master" (the default, comes with the package).
If I do what Carl describes, i.e., create buses from left to right (spilling eventually into my own-created "Master" replacement bus), then everything works just fine. I've gone as far as to rename "Master" as "Ignore" since I don't use it for anything as it won't "hear" any of my audio bus tracks.
But even this isn't quite enough. These buses I've made still won't hear the audio signal that's coming from another internal bus from "upstream" - just silence. Yet, if I create inserts inside those upper bus tracks and feed them into a downstream bus track (again, only moving from left to right within the Mixer view) then everything works just fine.
I never would've discovered this solution to my original problem (i.e., silence from my audio bus tracks into the Master) without Carl's helpful post(s).
Believe me, I'm NOT trying to complicate things (any more than Carl was) ... I'm simply trying to overcome some kind of limitation within Qtractor on my installation that we both seem to be experiencing. Hopefully that explains (our) situation and why the "insert" solution is needed.
My setup is using the latest rolling version of Arch Linux (Kernel 6.2.etc) as an EndeavourOS distribution and i3 window environment. I have not issues with any other audio software (like Ardour, et al) but the functionality of Qtractor is so much superior - love it!
Perhaps it's the use of these inserts that create the need to use Calf plugins in a different way than directly without the Calf rack app? If I could use the Calf plugins directly within Qtractor, that'd be great!
So far, I can't seem to figure out how to make that happen - hence my original question about which ins & outs are needed to use these cool Calf FX plugins.
FWIW, I don't seem to need to use an outside application for a different set of LV2 plugins I recently installed. Those work right along side or inside of Qtractor. So perhaps I need to explore in more detail what the difference might be between how my Calf plugins are installed and the other.
Anyhow, I probably shared more than you care to read, so hopefully some of this clarification is helpful in further explaining my present situation and how I got here. Simple is always my strong preference! ;-)
Copyright (C) 2006-2024 rncbc aka Rui Nuno Capela. All rights reserved.
Powered by Drupal
Recent comments
4 hours 31 min ago
16 hours 39 min ago
1 day 45 min ago
1 day 2 hours ago
1 day 16 hours ago
1 day 17 hours ago
1 day 17 hours ago
1 day 17 hours ago
1 day 18 hours ago
1 day 19 hours ago