18 Oct
2008
18 Oct
'08
2:06 p.m.
Hello everyone!
If I have a device sending MIDI start/stop and the CLOCK to jack_midi, does
this effect the transport system nowadays?
Kindest 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
18 Oct
18 Oct
2:25 p.m.
On Sat, Oct 18, 2008 at 8:05 PM, Julien Claassen <julien(a)c-lab.de> wrote:
If I have a device sending MIDI start/stop and the
CLOCK to jack_midi, does
this effect the transport system nowadays?
No. jack_midi is just a pipe. You need a
special application to
control jack transport system.
Regards,
Dmitry.
2:47 p.m.
Pity. :-( I'll have to circumvent this then. But thanks for the quick
response!
Kindest 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
2:58 p.m.
On Sat, Oct 18, 2008 at 11:46 AM, Julien Claassen <julien(a)c-lab.de> wrote:
Pity. :-( I'll have to circumvent this then. But
thanks for the quick
response!
Perhaps you can write a JACK midi client that reads the start and stop
messages and issues jack_transport_start() or jack_transport_stop(),
as desired?
If written as a small stand-alone client, that would be an appropriate
candidate for an example client in the JACK distribution.
--
joq
4:10 p.m.
On Sat, Oct 18, 2008 at 11:58:58AM -0500, Jack O'Quin wrote:
On Sat, Oct 18, 2008 at 11:46 AM, Julien Claassen
<julien(a)c-lab.de> wrote:
It's got to be less than 100 lines of code total.
JACK transport start/stop are each just a single C function call.
I'm not familiar with the JACK MIDI API but I'm guessing that checking for MIDI
start/stop shouldn't be more than a few lines of code.
-ken
Pity. :-( I'll have to circumvent this then.
But thanks for the quick
response!
Perhaps you can write a JACK midi client that reads the start and stop
messages and issues jack_transport_start() or jack_transport_stop(),
as desired?
If written as a small stand-alone client, that would be an appropriate
candidate for an example client in the JACK distribution. 
6:53 p.m.
Ken Restivo <ken(a)restivo.org> writes:
On Sat, Oct 18, 2008 at 11:58:58AM -0500, Jack
O'Quin wrote:
Will this work?
http://apps.linuxaudio.org/apps/all/jackctlmmc
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
On Sat, Oct 18, 2008 at 11:46 AM, Julien Claassen
<julien(a)c-lab.de> wrote:
It's got to be less than 100 lines of code total.
JACK transport start/stop are each just a single C function call.
I'm not familiar with the JACK MIDI API but I'm guessing that checking for MIDI
start/stop shouldn't be more than a few lines of code. Pity. :-( I'll have to circumvent this then.
But thanks for the quick
response!
Perhaps you can write a JACK midi client that reads the start and stop
messages and issues jack_transport_start() or jack_transport_stop(),
as desired?
If written as a small stand-alone client, that would be an appropriate
candidate for an example client in the JACK distribution.
5679
days inactive
5679
days old
linux-audio-user@lists.linuxaudio.org
5 comments
5 participants
participants (5)
-
Dmitry Baikov -
Jack O'Quin -
Julien Claassen -
Ken Restivo -
Nedko Arnaudov