6 Sep
2009
6 Sep
'09
8:57 a.m.
Hi,
I isn't possible to start a patchbay xml file, made in qjackctl, with
jack using the command line.
Is such a thing totally unthinkable? If not, wouldn't it be a nice feature?
Is there another way to make connections with jack using the command line?
Regards,
\r
6 Sep
6 Sep
12:33 p.m.
Grammostola Rosea wrote:
Hi,
I isn't possible to start a patchbay xml file, made in qjackctl, with
jack using the command line.
Is such a thing totally unthinkable? If not, wouldn't it be a nice feature?
Is there another way to make connections with jack using the command line?
patchbay .xml files are only understood and processed by qjackctl. you
don't actually need to start jackd from qjackctl, you can start and
activate a patchbay via the qjackctl command line:
qjackctl -a /path/to/patchbay.xml
but if what you really want is to avoid the gui (x11) then please forget
all this.
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
12:37 p.m.
Rui Nuno Capela wrote:
Grammostola Rosea wrote:
oops, sorry. this qjackctl -a option is only available from cvs head
(qjackctl 0.3.4.15)
byee
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Hi,
I isn't possible to start a patchbay xml file, made in qjackctl, with
jack using the command line.
Is such a thing totally unthinkable? If not, wouldn't it be a nice feature?
Is there another way to make connections with jack using the command line?
patchbay .xml files are only understood and processed by qjackctl. you
don't actually need to start jackd from qjackctl, you can start and
activate a patchbay via the qjackctl command line:
qjackctl -a /path/to/patchbay.xml
but if what you really want is to avoid the gui (x11) then please forget
all this.
7 Sep
7 Sep
10:51 a.m.
>> Is there another way to make connections with
jack using the command line?
>>
One option is to write a little script using jack_connect and
jack_disconnect for Jack connections (jack_lsp lists avaliable ports)
and aconnect for Alsa MIDI
Probably easier than writing scripts: jack_snapshot from the 'Affenbande'.
http://tapas.affenbande.org/wordpress/?page_id=14
I've never tried it myself though.
best,
d
11:07 a.m.
David Adler wrote:
Thanks for the hint:
$ make
g++ jack_snapshot.cc -o jack_snapshot `pkg-config jack --libs`
jack_snapshot.cc: In function ‘int main(int, char**)’:
jack_snapshot.cc:21: error: ‘exit’ was not declared in this scope
jack_snapshot.cc:35: error: ‘exit’ was not declared in this scope
jack_snapshot.cc:113: error: ‘strncpy’ was not declared in this scope
make: *** [jack_snapshot] Error 1
:(
/r
>> Is
there another way to make connections with jack using the command line?
>>
>>
One option is to write a little script using jack_connect and
jack_disconnect for Jack connections (jack_lsp lists avaliable ports)
and aconnect for Alsa MIDI
Probably easier than writing scripts: jack_snapshot from the 'Affenbande'.
http://tapas.affenbande.org/wordpress/?page_id=14
I've never tried it myself though.
12:12 p.m.
On Mon, Sep 7, 2009 at 3:06 PM, Grammostola
Rosea<rosea.grammostola(a)gmail.com> wrote:
David Adler wrote:
Thanks for the hint:
$ make
g++ jack_snapshot.cc -o jack_snapshot `pkg-config jack --libs`
jack_snapshot.cc: In function ‘int main(int, char**)’:
jack_snapshot.cc:21: error: ‘exit’ was not declared in this scope
jack_snapshot.cc:35: error: ‘exit’ was not declared in this scope
jack_snapshot.cc:113: error: ‘strncpy’ was not declared in this scope
make: *** [jack_snapshot] Error 1
The same here, this seems to be related to "a major header cleanup in
GCC 4.3", at least that's what a web search revealed.
After adding the following to the include section of jack_snapshot.cc
it compiles.
#include <string.h>
#include <cstdlib>
if this is an unsound solution, someone please tell me. I have no
background knowledge.
by the way, thanks for reminding me of this app, it seems to be a
simple and very helpful tool.
best,
d
>>
Is there another way to make connections with jack using the command line?
>>
>>
One option is to write a little script using jack_connect and
jack_disconnect for Jack connections (jack_lsp lists avaliable ports)
and aconnect for Alsa MIDI
Probably easier than writing scripts: jack_snapshot from the 'Affenbande'.
http://tapas.affenbande.org/wordpress/?page_id=14
I've never tried it myself though.
3:43 p.m.
David Adler wrote:
On Mon, Sep 7, 2009 at 3:06 PM, Grammostola
Rosea<rosea.grammostola(a)gmail.com> wrote:
Thanks again, works nice here :)
\r
David Adler wrote:
Thanks for the hint:
$ make
g++ jack_snapshot.cc -o jack_snapshot `pkg-config jack --libs`
jack_snapshot.cc: In function ‘int main(int, char**)’:
jack_snapshot.cc:21: error: ‘exit’ was not declared in this scope
jack_snapshot.cc:35: error: ‘exit’ was not declared in this scope
jack_snapshot.cc:113: error: ‘strncpy’ was not declared in this scope
make: *** [jack_snapshot] Error 1
The same here, this seems to be related to "a major header cleanup in
GCC 4.3", at least that's what a web search revealed.
After adding the following to the include section of jack_snapshot.cc
it compiles.
#include <string.h>
#include <cstdlib>
if this is an unsound solution, someone please tell me. I have no
background knowledge.
by the way, thanks for reminding me of this app, it seems to be a
simple and very helpful tool.
>>
Is there another way to make connections with jack using the command line?
>>
>>
>>
One option is to write a little script using jack_connect
and
jack_disconnect for Jack connections (jack_lsp lists avaliable ports)
and aconnect for Alsa MIDI
Probably easier than writing scripts: jack_snapshot from the 'Affenbande'.
http://tapas.affenbande.org/wordpress/?page_id=14
I've never tried it myself though.
8:33 p.m.
On 09/08/2009 12:12 AM, David Adler wrote:
Indeed, with errors like this, if you do `man strncpy', the man page
will tell you which header should be #included.
On Mon, Sep 7, 2009 at 3:06 PM, Grammostola
Rosea<rosea.grammostola(a)gmail.com> wrote:
..
g++
jack_snapshot.cc -o jack_snapshot `pkg-config jack --libs`
jack_snapshot.cc: In function ‘int main(int, char**)’:
jack_snapshot.cc:21: error: ‘exit’ was not declared in this scope
jack_snapshot.cc:35: error: ‘exit’ was not declared in this scope
jack_snapshot.cc:113: error: ‘strncpy’ was not declared in this scope
make: *** [jack_snapshot] Error 1
The same here, this seems to be related to "a major header cleanup in
GCC 4.3", at least that's what a web search revealed.
After adding the following to the include section of jack_snapshot.cc
it compiles.
#include<string.h>
#include<cstdlib>
11:08 p.m.
The same here, this seems to be related to "a major header cleanup in
GCC 4.3", at least that's what a web search revealed.
After adding the following to the include section of jack_snapshot.cc
it compiles.
#include<string.h>
#include<cstdlib>
Indeed, with errors like this, if you do `man strncpy', the man page will
tell you which header should be #included. 
10 Sep
10 Sep
6:39 a.m.
On Sun, 2009-09-06 at 12:57 +0200, Grammostola Rosea wrote:
Hi,
I isn't possible to start a patchbay xml file, made in qjackctl, with
jack using the command line.
Is such a thing totally unthinkable? If not, wouldn't it be a nice feature?
Is there another way to make connections with jack using the command line?
There is jack.plumbing which uses a regexp-based configuration file for
managing connections. It seems to have issues with jack2, though,
regarding trying to connect ports of inactive clients.
Peter.
7:18 a.m.
Peter Nelson wrote:
On Sun, 2009-09-06 at 12:57 +0200, Grammostola Rosea
wrote:
I start to get the feeling I need to follow a course JACK, but they
don't offer that on Berklee...:
$ jack
jack_alias jack_lsp jack_simple_client
jack.clock jack_metro jack-smf-player
jack_connect jack_midiseq jack-smf-recorder
jack.ctl jack_midisine jack_snapshot
jackd jack_monitor_client
jack_disconnect jack_netsource
jack-dssi-host jack.play jack_transport
jackeq jack.plumbing jack_transport_client
jack_evmon jack-rack jack.udp
jack_freewheel jackrec jack_unload
jack_impulse_grabber jack.scope
jack_load jack_showtime
....
\r
Hi,
I isn't possible to start a patchbay xml file, made in qjackctl, with
jack using the command line.
Is such a thing totally unthinkable? If not, wouldn't it be a nice feature?
Is there another way to make connections with jack using the command line?
There is jack.plumbing which uses a regexp-based configuration file for
managing connections. It seems to have issues with jack2, though,
regarding trying to connect ports of inactive clients.
10:37 a.m.
On Thu, Sep 10, 2009 at 5:17 AM, Grammostola
Rosea<rosea.grammostola(a)gmail.com> wrote:
I start to get the feeling I need to follow a course
JACK, but they
don't offer that on Berklee...:
$ jack
jack_alias jack_lsp jack_simple_client
jack.clock jack_metro jack-smf-player
jack_connect jack_midiseq jack-smf-recorder
jack.ctl jack_midisine jack_snapshot
jackd jack_monitor_client
jack_disconnect jack_netsource
jack-dssi-host jack.play jack_transport
jackeq jack.plumbing jack_transport_client
jack_evmon jack-rack jack.udp
jack_freewheel jackrec jack_unload
jack_impulse_grabber jack.scope
jack_load jack_showtime
compare with the number of FX pedals made for the BOSS brand, and then
contrast with the range of functionality offered by JACK clients, and
you'll see that this is actually a very limited set of tools to
comprehend. Note also that of the list above, at least 4-6 are
actually "example" clients and not "utilities" - they are intended to
be packaged separately by distributions and not installed by default.
They exist primarily to provide code samples for other developers.
5543
days inactive
5547
days old
linux-audio-user@lists.linuxaudio.org
11 comments
6 participants
participants (6)
-
David Adler -
Grammostola Rosea -
M Watts -
Paul Davis -
Peter Nelson -
Rui Nuno Capela