29 May
2010
29 May
'10
2:55 p.m.
Hello everyone!
Sorry to bother again, but I'm confused. I want to do a little skullduggery.
So I started these:
jackd - for basic audio/midi and transport
a2jmidid -e - To expose my ALSA MIDI ports to JACK
j2amidi_bridge - to expose my JACKMIDI stuff to ALSA
jack_midi_clock - to generate a good clocksource, that's bound to the
transport system of JACK
Now I want to start a midi sequencer (alsamidi capable) and connect the
jack_midi_clock to it.
The midi sequencer somehow has it's ports hidden, but can connect to any
input/output alsaseq port.
Now how do I connect the jack_midi_clock to finally end up with it's signal
exposed to ALSA, so I can connect it to my sequencer? Here's my list of
jack_midi_ports:
a2j:Virtual Raw MIDI 0-0 [16] (capture): VirMIDI 0-0
a2j:Virtual Raw MIDI 0-0 [16] (playback): VirMIDI 0-0
a2j:Virtual Raw MIDI 0-1 [17] (capture): VirMIDI 0-1
a2j:Virtual Raw MIDI 0-1 [17] (playback): VirMIDI 0-1
a2j:Virtual Raw MIDI 0-2 [18] (capture): VirMIDI 0-2
a2j:Virtual Raw MIDI 0-2 [18] (playback): VirMIDI 0-2
a2j:Virtual Raw MIDI 0-3 [19] (capture): VirMIDI 0-3
a2j:Virtual Raw MIDI 0-3 [19] (playback): VirMIDI 0-3
a2j:M Audio Delta 1010LT [20] (capture): M Audio Delta 1010LT MIDI
a2j:M Audio Delta 1010LT [20] (playback): M Audio Delta 1010LT MIDI
j2a_bridge:playback
a2j:j2a_bridge [129] (capture): capture
Jack MIDI Clock:midi_out
Can any body please help me clear up the mess a bit?
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
29 May
29 May
4:05 p.m.
On Sat, May 29, 2010 at 8:55 AM, Julien Claassen <julien(a)c-lab.de> wrote:
Hello everyone!
Sorry to bother again, but I'm confused. I want to do a little
skullduggery. So I started these:
jackd - for basic audio/midi and transport
a2jmidid -e - To expose my ALSA MIDI ports to JACK
good decision
j2amidi_bridge - to expose my JACKMIDI stuff to ALSA
unnecessary decision. a2jmidi -e is already there.
jack_midi_clock - to generate a good clocksource,
that's bound to the
transport system of JACK
not sure what kind of clock this generates, but fine.
Now I want to start a midi sequencer (alsamidi
capable) and connect the
jack_midi_clock to it.
but you haven't started one yet. or so it appears ...
The midi sequencer somehow has it's ports hidden,
but can connect to any
input/output alsaseq port.
its ports should not be hidden. do they show up in aconnect -i and/or
aconnect -o?
4:11 p.m.
Hello Paul!
No my sequencer's ports don'te really appear. they appear, when they are
connected to somthing.
I now did it like this:
I saw that jack_midi_clock was automatically connected to
j2a_bridge:playback
In ALSA I have port 129 listed with "aconnect -li".
So I asked my sequencer to connect to 129 and get its clock source there.
The rest of the sequencer connections were pure ALSa for the test.
Then I started jack_transport and told it to "play".
Nothing happened, yet that might be due to the clock. But would you say,
that this setup looks sane?
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
5:27 p.m.
On Sat, May 29, 2010 at 10:11 AM, Julien Claassen <julien(a)c-lab.de> wrote:
Hello Paul!
No my sequencer's ports don'te really appear. they appear, when they are
connected to somthing.
I now did it like this:
I saw that jack_midi_clock was automatically connected to
j2a_bridge:playback
In ALSA I have port 129 listed with "aconnect -li".
So I asked my sequencer to connect to 129 and get its clock source there.
The rest of the sequencer connections were pure ALSa for the test.
Then I started jack_transport and told it to "play".
Nothing happened, yet that might be due to the clock. But would you say,
that this setup looks sane?
i can see no reason to be using j2a_bridge at all for what you're doing.
5:33 p.m.
Hello Paul!
There is a very good reason I use j2amidi_bridge, my sequencer _ONLY_
understands ALSA sequencer ports, no JACKMIDI support and it doesn't look
likely, that it will be implemented soon. :-(
Beyond seeing no reason to use the bridging, should it theoretically work;
jack_midi_clock -> bridge (j2a:playback_ -> ALSA 129 -> sequencer?
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
7:16 p.m.
Hi,
It seems that I'm very confused by the whole jack MIDI system. Are
there some docs to refer to, as in a tutorial? I'm confused why Julien
needs to use so many Jack applications to set up a single MIDI
connection...it's certainly less involved with aconnect. And I've
certainly started jackd with -X and have access to alsa sequencers--so
why the other timer and bridge apps, etc?
Best,
AKJ
On 5/29/10, Julien Claassen <julien(a)c-lab.de> wrote:
Hello Paul!
There is a very good reason I use j2amidi_bridge, my sequencer _ONLY_
understands ALSA sequencer ports, no JACKMIDI support and it doesn't look
likely, that it will be implemented soon. :-(
Beyond seeing no reason to use the bridging, should it theoretically
work;
jack_midi_clock -> bridge (j2a:playback_ -> ALSA 129 -> sequencer?
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
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
--
Aaron Krister Johnson
http://www.akjmusic.com
http://www.untwelve.org
7:30 p.m.
Hello Aaron!
Never mind me. This is a problem related to working commandline only. There
aren't that many midi sequencers, let alone midi/audio recorders/sequencers.
So it can be a bit trying to synchronise MIDI and audio. But I'm gettng there,
slowly. :-)
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
7:33 p.m.
Excerpts from Aaron Krister Johnson's message of 2010-05-29 19:16:51 +0200:
Hi,
It seems that I'm very confused by the whole jack MIDI system. Are
there some docs to refer to, as in a tutorial? I'm confused why Julien
needs to use so many Jack applications to set up a single MIDI
connection...it's certainly less involved with aconnect. And I've
certainly started jackd with -X and have access to alsa sequencers--so
why the other timer and bridge apps, etc?
Best,
AKJ
It's incredible how often I can plug my blog recently :P
It's an attempt to explain what the different kinds of midi do and how
they're used:
http://murks.lima-city.de/serendipity/index.php?/archives/7-ALSA-and-JACK-M…
It doesn't cover everything Julien tries to do. It doesn't cover
jack_transport (it has nothing to do with midi) and doesn't cover midi
synchronisation methods like MTC, SMPTE and whatever else there might
be.
--
Regards,
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und alle Fragen
offen." Bertolt Brecht, Der gute Mensch von Sezuan
11:52 p.m.
On Sat, May 29, 2010 at 1:16 PM, Aaron Krister Johnson
<aaron(a)akjmusic.com>wrote;wrote:
Hi,
It seems that I'm very confused by the whole jack MIDI system. Are
there some docs to refer to, as in a tutorial? I'm confused why Julien
needs to use so many Jack applications to set up a single MIDI
connection...it's certainly less involved with aconnect. And I've
certainly started jackd with -X and have access to alsa sequencers--so
why the other timer and bridge apps, etc?
the timing behaviour of the two -X options (seq and raw) are not very good.
some might be sufficiently uncharitable as to call them "unusable".
a2jmidid (at least versions of it that are less than a year old) are much
much better and for now its the recommended way to make ALSA sequencer ports
show up in JACK.
some people (including julien) want JACK MIDI ports to show up as ALSA
sequencer ports too, so he has an additional program for that (j2a_bridge).
finally, julien is running a program to generate MIDI clock messages.
--p
30 May
30 May
6:01 a.m.
I'm confused, too. But I'm easily confused. I've never had to do
anything else than run JACK to connect things up. (Well, ZynAddSubFX can
still be uncooperative, but Yoshimi meets ZynAddSubFX fixes that.)
What "sequencer" are you using, Julian?
Aaron Krister Johnson wrote:
Hi,
It seems that I'm very confused by the whole jack MIDI system. Are
there some docs to refer to, as in a tutorial? I'm confused why Julien
needs to use so many Jack applications to set up a single MIDI
connection...it's certainly less involved with aconnect. And I've
certainly started jackd with -X and have access to alsa sequencers--so
why the other timer and bridge apps, etc?
Best,
AKJ
On 5/29/10, Julien Claassen <julien(a)c-lab.de> wrote:
> Hello Paul!
> There is a very good reason I use j2amidi_bridge, my sequencer _ONLY_
> understands ALSA sequencer ports, no JACKMIDI support and it doesn't look
> likely, that it will be implemented soon. :-(
> Beyond seeing no reason to use the bridging, should it theoretically
> work;
> jack_midi_clock -> bridge (j2a:playback_ -> ALSA 129 -> sequencer?
> Kindly yours
> Julien
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
9:32 a.m.
Hello David!
I'm using midish, which is - to my best knowledge - the most powerful
sequencer for the commandline. There are others. At least one of them has a
nice feature set, which was partly planned for blind people, but: It's no
longer maintaned, I can't do it.It doesn't even support ALSA midi.
Warm 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
31 May
31 May
5:39 a.m.
Hello, Julien!
I didn't know that midish was a sequencer. I thought it was just some
kind of MIDI utility.
Which sequencer is it that you mention below, that was partly planned
for blind people but is no longer maintained?
Julien Claassen wrote:
Hello David!
I'm using midish, which is - to my best knowledge - the most powerful
sequencer for the commandline. There are others. At least one of them
has a nice feature set, which was partly planned for blind people, but:
It's no longer maintaned, I can't do it.It doesn't even support ALSA midi.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
10:01 a.m.
Hello David!
The other one is cuse. Cuse has an ncurses interface, which basically looks
OK, but the cursor isn't always, where it should be, which is not nice for me.
FNIce features are: You can control start, stop and few more via customiseabe
user commands. So if you like your 12-tone music, configure start to be
c-majro. :-) Otherwise Just use c1 and b4.
Cuse also has a step-sequencer, wich can be a pretty thing. Ye as I said: no
ALSA seq. And I think, that I don't know enough to add it. I also tried
changing the user interface. I managed to do a few minimalistic things, as
best I can remember.
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
6:40 p.m.
On 31/05/2010, Julien Claassen <julien(a)c-lab.de> wrote:
The other one is cuse. Cuse has an ncurses
interface
Have you tried b-tektracker? ( http://bttrk.sourceforge.net/ )
6:44 p.m.
Hi Gwenhwyfaer!
I once tried ttrk. Does b-tektracker support ALSA sequencer?
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
29 May
29 May
8:05 p.m.
Hi all!
I've got the problem solved. I just didn't know, that jack_midi_clock needs
a timer (i.e. klick or ardour). Now it's working. I should write someting
about that, it's tricky enough. :-)
Best wishes
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
5090
days inactive
5092
days old
linux-audio-user@lists.linuxaudio.org
15 comments
6 participants
participants (6)
-
Aaron Krister Johnson -
david -
Gwenhwyfaer -
Julien Claassen -
Paul Davis -
Philipp Überbacher