Could someone please add firewire 410 from m-audio and put a big NO sign
on it. (there should be blacklist part
of the matrix of avoid devices) Since its m-Lan we wont get any driver
if we can not put pressure on yamaha.
Takashi Iwai wrote:
At Wed, 26 Nov 2003 22:42:44 +0100,
Martin Langer
The yamaha Motif products have mlan interfaces. I guess that they are
not supported by alsa. Should be in the lists too.
Peter Enderborg wrote:
Could someone please add firewire 410 from m-audio and put a big NO
sign on it. (there should be blacklist part
of the matrix of avoid devices) Since
(cvs version 2003-02-13)
/sbin/modprobe snd-trident
Note: /etc/modules.conf is more recent than
/lib/modules/2.4.19/modules.dep
/lib/modules/2.4.19/kernel/sound/pci/trident/snd-trident.o: init_module:
No such device
Hint: insmod errors can be caused by incorrect module parameters,
including
How free is the ADAT format? Is there any public specs? Is there any
standard chips that talks this protocol?
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Is there, or plans for higer level function in alsa lib for motorized
midi controlers? Like Steinberg Houston or Mackie HUI?
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
I have some memory problems with my alsa programming.
And I have tryed to do a small program to see whats wrong.
And I still have the same problem with this little program...
#include alsa/asoundlib.h
int main()
{
while (1)
{
snd_seq_event_t *foo;
foo = snd_seq_create_event();
Takashi Iwai wrote:
At Mon, 06 May 2002 12:09:57 +0200,
Peter Enderborg wrote:
Takashi Iwai wrote:
Hi Peter,
At Sun, 05 May 2002 19:35:04 +0200,
Peter Enderborg wrote:
I have some memory problems with my alsa programming.
And I have tryed to do a small program
I have some memory problems with my alsa programming.
And I have tryed to do a small program to see whats wrong.
And I still have the same problem with this little program...
#include alsa/asoundlib.h
int main()
{
while (1)
{
snd_seq_event_t *foo;
foo = snd_seq_create_event();
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
Jaroslav Kysela wrote:
On Fri, 1 Mar 2002, Peter Enderborg wrote:
Paul Davis wrote:
Yes! And the device that is using running status is alsa rawmidi device.
What makes you think that? AFAIK, the raw MIDI device code does no
parsing of MIDI data at all ...
Parsing? It sends
I have a snd_rawmidi_t. And I want to know what client Id it will have
in the other end.
For example my first rawmidi is card 2 device 0. And that is client id
80:0 but how do I look
that up in the rigth way?
___
Alsa-devel mailing list
[EMAIL
Paul Davis wrote:
I don't know how to be more specific. I have a program that listen to
a raw midi stream generated by alsa. But I try.
You have a program that uses the sequencer to read MIDI data. That's
totally different from a program that uses the raw MIDI interface to
read MIDI data.
Roger E Critchlow Jr wrote:
Peter Enderborg writes:
Jaroslav Kysela wrote:
On Fri, 1 Mar 2002, Peter Enderborg wrote:
Paul Davis wrote:
Yes! And the device that is using running status is alsa rawmidi device.
What makes you think that? AFAIK, the raw
Roger E Critchlow Jr wrote:
Peter Enderborg writes:
Roger E Critchlow Jr wrote:
[ ... ]
Does this help?
Well. I guess it do. I will give it a try. It should work. What about non midi
snd_seq_event_t.
The internal alsa stuff, like subscribe?
Hmm, hadn't
Paul Davis wrote:
I have a program that read's from a raw midi device. In midi there
are some simple compression. It is assumed that if the data flow is
correct, and the data should be interpreted as paramaters to previus
command if it's not a new command. But when I open a raw midi stream
Paul Davis wrote:
This is the configuration:
Roland MCR-8-midi-device-alsa-seq-user_code-alsa-seq-raw_midi
this is a crazy, wierd setup! but i'll try to just let that be. i
suspect you don't mean raw MIDI the way its meant in ALSA.
What so weird about it? The user_code map some event's
I have a program that read's from a raw midi device. In midi there are
some simple compression.
It is assumed that if the data flow is correct, and the data should be
interpreted as paramaters
to previus command if it's not a new command. But when I open a raw midi
stream I can get
in to the
This is realy nice. I do realy hope that we don't have to wait two or three
years for 2.6!
--
foo!
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Dan Hollis wrote:
On Sat, 13 Oct 2001, Peter Enderborg wrote:
It is realy a small market. For example one of the big midi interface
manufactures (Midiman) don't even have full supprt of there new
highend products for windows 2000. You have to go for windows 9x or NT
dave willis wrote:
On Sat, 13 Oct 2001, Peter Enderborg wrote:
It is realy a small market. For example one of the big midi interface
manufactures (Midiman) don't even have full supprt of there new
highend products for windows 2000.
you must be thinking of someone else. all
Paul Davis wrote:
it's been the same with MOTU, some vendors are just ignorant of a
large potential customer base.
lets not kid ourselves. there is a *tiny* potential customer base for
the next several years at least, and the existing customer base is
even smaller.
It is realy a small
21 matches
Mail list logo
