<br><br><div class="gmail_quote">On Mon, Mar 22, 2010 at 8:47 PM, Rui Nuno Capela <span dir="ltr"><<a href="mailto:rncbc@rncbc.org">rncbc@rncbc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 03/22/2010 07:18 PM, rosea grammostola wrote:<br>
><br>
><br>
> On Mon, Mar 22, 2010 at 7:50 PM, Rui Nuno Capela <<a href="mailto:rncbc@rncbc.org">rncbc@rncbc.org</a><br>
</div><div><div></div><div class="h5">> <mailto:<a href="mailto:rncbc@rncbc.org">rncbc@rncbc.org</a>>> wrote:<br>
><br>
> On 03/22/2010 10:07 AM, rosea grammostola wrote:<br>
> ><br>
> > Some questions about qtractor:<br>
> ><br>
> > * You can't render the midi track to wav? How do you get an whole<br>
> > session into an audio file?<br>
><br>
> midi is meant to be rendered by a sound generator module, a synth, a<br>
> sampler, a stand-alone or an instrument plugin (dssi, vsti or lv2); you<br>
> can drive external midi outboard equipment as well, which in fact was<br>
> and still is the primordial goal of a midi sequencer like qtractor.<br>
><br>
> qtractor does not include/integrate any midi sound generator per se, so<br>
> you cannot render midi tracks directly to audio files. but you can<br>
> record/bound the sound modules output back into qtractor, ardour or any<br>
> other jack enabled hard-disk recorder if you prefer.<br>
><br>
> qtractor exports audio tracks as audio files; similarly it exports midi<br>
> tracks as standard midi files, nothing else ;)<br>
><br>
><br>
> ><br>
> > * Why are there no new audio tracks showing up in Jack when<br>
> you add<br>
> > a new audio track, like ardour has? Wouldn't this make it more<br>
> > easy to use it with other apps (for example ardour)?<br>
><br>
> qtractor is not ardour (tm) -- internal signal flow models are not the<br>
> same, not even close ;)<br>
><br>
> re. qtractor, each "input bus" feeds a track on recording; each track<br>
> feeds an "output bus" for mixdown/merging on playback; it is these "bus"<br>
> devices that are exposed as jack audio ports or alsa-seq ports (midi)<br>
> from or to the outside world.<br>
><br>
> again, buses in qtractor are not the same as buses in ardour. in<br>
> qtractor, buses are what you ever see in the jack graph. you never see<br>
> tracks ;)<br>
><br>
> I don't understand it totally. Let assume I have to midi tracks in<br>
> qtractor and I want to record those to two audio tracks in qtractor. But<br>
> there is only master_in1 and master_in2.<br>
><br>
> When I add an audio track, I can only choose for master_in. Also for new<br>
> audio track number two, master_in. How to route output of synth 1 to<br>
> track1 and synth 2 to track 2?<br>
><br>
<br>
</div></div>you create more buses. at least one more in addition to master which is<br>
indeed stereo (2channels) and created by default ootb. you can setup<br>
your workspace as with many ins and outs you need and make it a template<br>
for all your future new blank/scratch sessions.<br>
<br>
so, recipe is: create one additional bus, call it master_2 for instance<br>
and assign it as input for audio track_2; audio track_1 stays on Master<br>
for input. now you connect synth_1/outs to Master/ins and synth_2/outs<br>
to master_2/ins. voilá :)<br>
<br>
remember now that qtractor session templates may get very handy here,<br>
for not having to be doing this all the time, as it also includes<br>
connection recall. alas, it won't start your external synths<br>
automatically, you'll have to do that manually, business as usual,<br>
qtractor will wait for them appearing on the radar to reconnect. yep,<br>
qtractor is not a full-blown session manager, i know. let's leave that<br>
for someone else ;)<br></blockquote></div><br><br>Mmh I tried to do what you said, but I get an segmentation fault now, and can't restart the session (just an test session, nothing important)...<br><br>bash: line 1: 6175 Segmentation fault qtractor /home/user/linuxaudio/qtractor/firsttake.qtr<br>
<br><br>\r<br>