You can also use the patchbay in qjackctl (aka Jack Control) -- it
will remember what was connected to what, and the next time it sees
both available it automagically reconnects them. Makes it much easier
to manage/change complex setups involving many different tools.
micromoog
On Tue, May 12, 2009 at 8:23 AM, nescivi <nescivi@xxxxxxxxx
<mailto:nescivi@xxxxxxxxx>> wrote:
On Tuesday 12 May 2009 03:21:22 Peter O'Doherty wrote:
> That's something I discovered as well. You have to make the
connections
> in jack to the hardware outs manually before you get any sound.
It's a
> bit awkward, especially if you're just testing small bits of code.
you can define environment variables
SC_JACK_DEFAULT_INPUTS
and
SC_JACK_DEFAULT_OUTPUTS
then scsynth will use these to connect automatically to jack ports.
There is an example in the example .sclang.sc <http://sclang.sc/>
file in the linux folder.
sincerely,
Marije
> Peter
>
> > Definitely, there's something in the structure client server
or in OSC
> > messages which I can not understand. I tried all ways, including
> > sending messages to sclang via OSCresponder. Fortunately, as I
have
> > suggested altern, using the ixi's library sc all goes well,
provided
> > that the connections are properly carried out jack (on linux) and
> > Synthdefs are added to a folder synthdefs in the working
directory.
> >
> > Thank you.