I've tried both methods, using the Qtractor connections window and also through the qpwgraph.
Currently, I'm using OpenSUSE Tumbleweed with KDE Plasma and X11.
I have Qtractor installed from the Geekos DAW multimedia:proaudio repository. The Qtractor version is 1.5.4, using Qt 6.9.0.
The issue is that when I send the output of one bus to another bus, the receiving bus gets no signal at all.
Apologies for my poor English. I'll try to explain as clearly as I can.
I have two audio tracks: Track 1 and Track 2. There’s also the default Master Bus. I’ve created a bus called "MixBus," along with Bus 1 and Bus 2.
Now, if I send Track 1 to Bus 1 with auto-connect enabled, Bus 1 sends the signal to the playback device, and I can hear everything.
However, if I disconnect Bus 1 from the playback device and try to connect it to another bus, which then routes to the output, the signal doesn’t pass through. The meter doesn’t show any activity, and no audio goes through.
For example, if I route Track 1 to Bus 1, Bus 1 to MixBus, and then MixBus to the playback device, I can’t hear anything. The problem is that there’s no signal showing up in the MixBus meter; it shows no activity. Despite connecting Bus 1 output 1/2 to MixBus input 1/2, and then sending MixBus output 1/2 to the playback device, there’s no signal.
I believe this issue also affects MIDI tracks. When I right-click and change the audio output to a bus, I face the same problem.
The bus receiving input directly from a track does show signal, and I can see the green volume meter activity on the bus’s meter. The issue seems to be that the signal isn’t passing from bus to bus.
I think OpenSUSE is using PipeWire with JACK.
Thanks in advance for any…
Thanks in advance for any help.
And also thanks Mr. Rui for all the awesome software and tools including Qtractor and everything else.
re. Sending bus output to another bus input...
hi, you're welcome
however the issue has been discussed here for years now, please search for "zero-copy" for instance...
in a sentence:
the usual solution is to insert another jack-client in between.
hth.
cheers
thank you very much sir. I…
thank you very much sir.
I actually now remember the youtube tutorial by i scores music regarding Qtractor Inserts and Aux Sends i saw several months ago.
I took a little bit of break from Qtractor and music production in between so I forgot about that.
I'm so sorry to bother you with this.
And thanks again, sir, for this awesome software!
re. Sending bus output to another bus input,...
anyway,
next dot release (v1.5.5) will then issue a warning message if one ever tries to connect any output to any of its own inputs.
so there, you've been advised ;)
cheers
Pops out when loading existing projects
Hi Rui,
when loading existing session the warning pops up. It's not of great help especially because it doesn't say where (which bus) I have to look.
What is warned about?
[EDIT] I use the real jackd, so all of those connections work fine.
re. Pops out when loading existing projects...
yes
but it's just a general warning message only, and you may now dismiss it to "don't show again", in qtractor >= 1.5.4.8git.21eb18
thanks
dismiss works
Hi Rui,
the dismiss feature works fine. But when there is a warning even in such simple cases like
track -> bus -> master bus
then it might make new users feel unsecure why buses are there at all.
re. new users feel unsecure...
feeling insecure is not worse than getting no sound at all, I'd say ;)
consider yourself lucky if that it all works for you; the vast majority of users, under regular jack/pipewire, like OP, will get the relief factor (I hope).
cheers
Recommended way to connect a bus to master bus?
In my setup I connect the output of a bus to the input of the master bus. That can be problematic as we discussed. Although I use jackd I experienced silence when I inserted an AUX send (although I didn't activate it). Inserting seems to break connections.
So I tried to disconnect all buses' outputs to the master bus and inserted an AUX send to the master bus instead. That works and it saves one buffer of latency.
It works but is rather unintuitive. I am afraid that redesigning the buses to use an AUX send when doing an internal connection will break old sessions.
re. Recommended way to connect a bus to master bus?...
not only to master bus but to any buses that matter:
a. have a pass-through client in between (adds a period latency at least, ofc.);
b. make sure any direct connection from an output bus to any input bus are not alone or single-handedly: connect something else to either side.
byee
ps. b. works on genuine jackd only; not in pipewire, sorry.
Add new comment