4 Aug
2009
4 Aug
'09
11:56 a.m.
Maybe I should start with the Alsaseq python package and HelperMudule,
but I would like to have Jack MIDI so I'll give MidiDings a try.
But remembering the field "Midi driver" on Qjackctl config I wonder,
if it is set to alsa_seq you can see AlsaMidi ports on JackMidi tab,
could it be better to choose Alsaseq python package because you could
also have your MIDI port on JackMidi? (at least for a first release)
Am I missing something?
2009/8/3, harryhaaren(a)gmail.com <harryhaaren(a)gmail.com>om>:
Hey,
Just to say, I think this is mainly related to Lin-Audio-Dev, so I wont be
sending to lin-user in furthur replies..
And on the topic for a second, python bindings exist for MidiDings, a
module that can use both AlsaSeq & Jack Midi.
I have a very limited amound of experince with it, as i found the AlsaSeq
python package to be much simpler to use.
(It does however not support Jack Midi.) Might i suggest to use AlsaSeq
first if this is your first Python/Midi project,
despite there only being a few demos/tutorials for AlsaSeq, its a great way
to get acces to the Alsa Sequencer.
AlsaSeq also has a "Helper-Module", called alsamidi, which helps creating
messages in a generic & easy way without
getting your hands dirty in Midi bytes, commands & the likes. (it comes
with the AlsaSeq tarball, so you'll get it automatically.)
Cheers, -Harry
--
Carlos "Sanchiavedraz"
* Musix GNU+Linux
http://www.musix.es