Sending bus output to another bus input, but the receiving bus gets no signal/audio.

Forums

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.

Permalink

Thanks in advance for any help.
And also thanks Mr. Rui for all the awesome software and tools including Qtractor and everything else.

Permalink

hi, you're welcome

however the issue has been discussed here for years now, please search for "zero-copy" for instance...

in a sentence:

  • directly connecting a same jack-client (qtractor) output ports (insert sends or output buses) to its own input ports (insert returns or input buses) is not advisable : it often doesn't work, if at all.

the usual solution is to insert another jack-client in between.

hth.
cheers

Permalink

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!

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?

  • when an INSERT send goes to its own receive? I do that to align latencies.
  • when a bus' output goes to another bus' input? That would affect busX out to master in what's very common IMHO.

[EDIT] I use the real jackd, so all of those connections work fine.

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

Permalink

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.

Add new comment

The content of this field is kept private and will not be shown publicly.

Markdown

  • Parses markdown and converts it to HTML.
  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id> <img src alt height width> <strike> <pre> <p> <br>
  • Lines and paragraphs break automatically.

Filtered HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <b> <i> <pre> <img src alt height width> <strike>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.
File attachments
Unlimited number of files can be uploaded to this field.
2 MB limit.
Allowed types: jpg jpeg gif png txt doc docx xls xlsx pdf ppt pps odt ods odp zip gz bz2 xz patch diff wav ogg flac ogv mp4 qtz.