8 Nov
2010
8 Nov
'10
3:19 p.m.
I'm writing to ask for help on an idea i have for building a bash
script to handle jackmidi connect-disconnects for multiple midi ports.
The premise is:
Start the script, and using keybindings assigned in the script,
quickly switch from one jackmidi port to another. (Whatever workspace
i'm in at the time)
I understand the "captured bindings" won't be able to be used by other
apps while the script is running, but i have sufficient obscure
combinations of modifier and <something> in mind.
Is this possible, and if so, could someone give a basic example of the
code required to assign a specific binding as a toggle, for a
jack_connect port out port in/jack_disconnect port out port in pair?
In this experiment, i'm planning to start with 16 jackmidi ports, with
an a2j port for the midi keyboard controller in.
This is with the intent of driving LinuxSampler directly to recorded
audio out. (No midi sequencer, and non-gui for everything)
Regards,
Alex.
--
www.openoctave.org
midi-subscribe(a)openoctave.org
development-subscribe(a)openoctave.org
8 Nov
8 Nov
3:54 p.m.
Hello Alex!
Well I don't know how to setup a script as you described it, but I know,
that there is jackctl.py. This i a text based python script for managing jack
and ALSA connections. I think it should be able to connect JACK MIDI ports as
well. It offers a shell just like Nama or Ecasound and has only one letter
commands. Ports are addressed by numbers (as they appear in the list of
jackctl.py).
Hope that helps.
Kindly yours
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
4 p.m.
New subject: building a bash script for jack midi connect-disconnect with toggle keybindings
On Mon, Nov 8, 2010 at 6:54 PM, Julien Claassen <julien(a)c-lab.de> wrote:
Hello Alex!
Well I don't know how to setup a script as you described it, but I know,
that there is jackctl.py. This i a text based python script for managing
jack and ALSA connections. I think it should be able to connect JACK MIDI
ports as well. It offers a shell just like Nama or Ecasound and has only one
letter commands. Ports are addressed by numbers (as they appear in the list
of jackctl.py).
Hope that helps.
Kindly yours
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
Julien, i'll have a look, many thanks for the tip.
Regards,
Alex.
--
www.openoctave.org
midi-subscribe(a)openoctave.org
development-subscribe(a)openoctave.org
4:01 p.m.
New subject: building a bash script for jack midi connect-disconnect with toggle keybindings
Sorry, posted too soon.
I assume jackctl.py requires the focus to accept commands?
Alex.
4:04 p.m.
New subject: building a bash script for jack midi connect-disconnect with toggle keybindings
Alex!
The focus? If you mean, that jackctl.py must be running to accept commands:
Yes. So it will block a terminal, unless you use screen (Joel mentioned it
before).
Kind regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
9 Nov
9 Nov
9:14 a.m.
New subject: building a bash script for jack midi connect-disconnect with toggle keybindings
On Mon, 8 Nov 2010 17:04:18 +0100 (CET)
Julien Claassen <julien(a)c-lab.de> wrote:
Alex!
The focus? If you mean, that jackctl.py must be running to accept
commands: Yes. So it will block a terminal, unless you use screen
(Joel mentioned it before).
Kind regards
Julien
so you could open screen, run your app, deattach screen, and it would
still listen to your keyboard shortcuts?
in that case, if you want to restrict yourself to bash, I would suggest
letting your WM or something like xbindkeys take care of the keyboard
shortcuts, and just call your script with different arguments in the
background, when you use different keyboard shortcuts.
Dieter
4:15 p.m.
New subject: building a bash script for jack midi connect-disconnect with toggle keybindings
Hello Dieter!
No, the script won't listen to keystrokes, if it isn't active on the real
screen. Screen is just a way to start more than one program on a terminal.
Simply a matter of "Where shall I put these five apps then? There's only one
TTY left." :-)
And as I understand, Alex wants to seperate from the GUI as much as
possible. I suppose xbindkey needs X to run and only works on the Xserver. If
i'm mistaken, shame upon me. :-)
Kindly yours
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
4:51 p.m.
New subject: building a bash script for jack midi connect-disconnect with toggle keybindings
On Tue, Nov 9, 2010 at 11:15 AM, Julien Claassen <julien(a)c-lab.de> wrote:
Hello Dieter!
No, the script won't listen to keystrokes, if it isn't active on the real
screen. Screen is just a way to start more than one program on a terminal.
Simply a matter of "Where shall I put these five apps then? There's only one
TTY left." :-)
And as I understand, Alex wants to seperate from the GUI as much as
possible. I suppose xbindkey needs X to run and only works on the Xserver.
If i'm mistaken, shame upon me. :-)
there are ways to listen to raw keyboard events via the kernel. they
are strongly, strongly not recommended for just about any purpose.
13 Nov
13 Nov
1:21 a.m.
New subject: building a bash script for jack midi connect-disconnect with toggle keybindings
On Tue, Nov 9, 2010 at 5:51 PM, Paul Davis wrote:
this thread got me curious :)
an example using xbindkeys:
setup a script like this for the desired midi switching:
#!/bin/bash
if [ $1 = a ] ; then
jack_disconnect 'Non-Sequencer:midi_out-1' 'yoshimi-01:midi in'
jack_connect 'Non-Sequencer:midi_out-1' 'yoshimi:midi in'
elif [ $1 = b ] ; then
jack_disconnect 'Non-Sequencer:midi_out-1' 'yoshimi:midi in'
jack_connect 'Non-Sequencer:midi_out-1' 'yoshimi-01:midi in'
fi
for testing, invoke it with its arguments
./jmidiswitch.sh a
./jmidiswitch.sh b
install xbindkeys
create an appropriate file ~/.xbindkeysrc, containing:
# xbindkeys configuration
"$HOME/jmidiswitch.sh a"
Alt +a
"$HOME/jmidiswitch.sh b"
Alt +b
run xbindkeys,
and happy switching.
IIRC only jack2 allows for click-free port switching,
the tests I ran with jack1 and jack2-svn confirm this.
best,
d
On Tue, Nov 9, 2010 at 11:15 AM, Julien Claassen
wrote:
...
And as I
understand, Alex wants to seperate from the GUI as much as
possible. I suppose xbindkey needs X to run and only works on the Xserver.
If i'm mistaken, shame upon me. :-)
there are ways to listen to raw keyboard events via the kernel. they
are strongly, strongly not recommended for just about any purpose.
5161
days inactive
5166
days old
linux-audio-user@lists.linuxaudio.org
8 comments
5 participants
participants (5)
-
alex stone -
David Adler -
Dieter Plaetinck -
Julien Claassen -
Paul Davis