Forums
When doing everything in Qtractor then exporting tracks works fine, even with
"track -> somebus -> aux send to master bus" and "track -> aux send to reverb bus -> aux send to master bus".
But if the reverb bus has an insert send to/from another plugin host with a reverb plugin then the reverb is missing. To make sure that the other plugin host has no problem with jack freewheeling I tried a 2nd Qtractor instance as the plugin host, too.
I use the real jack2.
Does this work as designed?
re. Exporting Tracks, success and failure...
only the later may foster any improvement.
can't tell... what is not really working? if that's an insert send/return to/from the same client instance (qtractor) than you prolly know the answer--proverbial undefined behavior.
otherwise, it's not clear what really the problem is: is it that you're sending from and then returning to different qtractor instances? and expect the audio export will work? i'm afraid you're expecting and confusing the roles of one or each instance, as for their respective outputs may now be quite independent...
know that qtractor multi-instance is only there and indulged because of NSM support; all other use cases are not really a feature and might actually behave as terribly buggy--you've been warned ;))
so, the answer to this is..., not quite.
cheers
Send/return to another plugin host
I have the usual setup for reverb:
When the reverb bus hosts the reverb plugin everything works as expected.
When the reverb bus doesn't host the reverb plugin but has an insert send /return to another plugin host with the reverb plugin then this signal is missing in the export file although it's audible when playing the song.
To make sure it's not the plugin host's fault I tried 2 different hosts: Calf Plugin Pack and a 2nd Qtractor instance.
For me it looks as if a signal that goes to another plugin host and returns from there (via insert send/return) is missing when exporting.
Is this supposed to work or can Qtractor export only signals inside Qtractor?
If it's not clear what I do I can make a Screencast.
re. if a signal that goes to…
returns to what exactly?
obviously, by design if that's the original question, qtractor can only export signals that go through (internally) and appear at its output buses.
hth.
send/return
The reverb bus sends the signal to another host with a reverb plugin and gets its output back.
send volume is set to 1, dry to 0, wet to 1.
So the reverb signal is in the bus as if the reverb plugin was in the bus. This has to be paid with one buffer of latency but distributes realtime CPU load among multiple cores.
Exporting only exports the…
Exporting only exports the bus outputs. For mixing, in Qtractor, we use aux sends because Qtractor can't directly connect buses.
For mixing, we don't use bus outputs, but rather aux sends.
Therefore, it will always be impossible to export a mix with the current exporter design.
Exporting only works for exporting specific buses, not mixes.
You can export multiple buses at once, but there's never a guarantee of clipping, because to have that guarantee, you must mix the signals on a master bus with a limiter. Here, the master bus would just be another bus that adds another signal; it doesn't concentrate them.
The exporter doesn't concentrate signals, it doesn't mix them; it only sums all the buses. It doesn't take into account the aux sends (which are what we mix), but rather the bus outputs (which we don't use for mixing and which don't correspond to the aux send signals).
The only way to export a mix is to record the master output audio in real time.
Then I misunderstood the concept
Thanks for clarifying. I thought I can export a wav-File that's like recording the song with Audacity or jack_rec – provided that I don't use hardware synths.
So back to „If you can't stand your own song in real time, you shouldn't release it." :D
I don't think you misunderstood the concept
It's simply that the export function doesn't work as the user expects.
Just as I select a bus to connect it to an external recorder and can record all the audio involved, including sends, I expect that if I select a bus in the export function, it will do the same.
That's the expected behavior.
Will it ever work that way? No idea.
I've never really focused on this functionality because using an external recorder or recording the final signal on another track works fine, and I think it will always be the best way to get exactly what you hear, because you're recording what you literally hear.
Sometimes I use Qtractor as an audio editor. In that template, I only use the Master bus. In those cases, exporting works fine... Although something tells me that the result is still subtly different from what you get by recording the signal you hear. And I think that happens in all DAWs... but that's just a hunch, I can't be sure. If you use different processes for real-time/rendering, it's logical that you won't get the same result.
re. If you can't stand...
If we're working only with sends (no latency), as we know, we can always increase the processing time (there is no limit) with the buffer and samples to give the processor time to do its work. It's always worked for me so far. It's also true that, at least for me, I work with a computer that's over 15 years old. And we ask it to work in real time with virtual instruments and dozens of plugins. Maybe it's time to upgrade the hardware, but at least for me again, as long as there are tricks to get the job done, I'll stick with it :).
Add new comment