so essentially you skip alsalib and interact with the driver only. i
have found this to be the least painful way of dealing with raw MIDI
streams.
Tim, I think this is very bad advice, especially on the alsa-dev
mailinglist!
Charles, you might want to have a look at the documentation:
The first argument is input handle, the second is output handle. And
the
third
is the device. 0 is eq to NULL, and I don't think you have a device
with
that name.
OK ! So, where could I find the device number ? It is the char-major /
char-minor of unix dev ?
And you migth want to have a
Charles Flèche wrote:
Thanx a lot for your help ! I'm working on this project for my
university, and if this soft don't work, I'm going to do another
year... HHAARRRGGG !
although this is probably not the preferred way (by the ALSA team) of
using the interfaces, you can access MIDI
Hello everybody !
I'm french, so I'll **TRY** to speak english correctly...
I'm new in C programming (in programming, in fact...) and I work on a
soft for speaking with an effect rack (alesis microverb IV) with sysex
trough rawmidi for saving my patches, remote control this unit, etc...
So,
Re!
From: Charles Flèche [EMAIL PROTECTED]
So, this is my problem: I don't know how to send sysex through
rawmidi!!
I'm not into midi, so I cant help you here. But I see with one eye on
your program that you don't check for errors at all.
Another small question : how can I force a pause in
Charles FlXche wrote:
Hello everybody !
I'm french, so I'll **TRY** to speak english correctly...
I'm new in C programming (in programming, in fact...) and I work on a
soft for speaking with an effect rack (alesis microverb IV) with sysex
trough rawmidi for saving my patches, remote
