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
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 wrot
(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 invali
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
int main()
{
while (1)
{
snd_seq_event_t *foo;
foo = snd_seq_create_event();
snd_seq_fr
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:
> > > >
> >
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 to see whats wrong.
> > And I still have the s
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
int main()
{
while (1)
{
snd_seq_event_t *foo;
foo = snd_seq_create_event();
snd_seq_fr
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 Wed, 3 Apr 2002, Peter Enderborg wrote:
>
> > I have tryed to get some answer from Jaroslav about subdevices on midi.
> > Im trying to write a driver for midisport 8x8/s and that have 9 midi
> > ports. On my hack to figure out the protocol I u
I get in to allocation error when I try to start a alloc the 8' queue.
Is there any parametes to
tune for this ? Im need 17...
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
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
> > s
Paul Davis wrote:
>How do you solve the problem with sharing hardware
then?
I don't. I intend to wait for (and contribute too, if I can) what I
consider the correct solution:
a) sequencer genuinely split into:
1) a router/multiplexer
2) a scheduler
b) sequencer moves into
Paul Davis wrote:
> >It is the api for midi programming. I don't have to think about
> >active sensing, streaming or anything on the low level. And I get
> >tools for routing the data as I like. I thougth that you should know
> >the concept. Almost everything is in realtime. But some mappings i
>
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
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
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 PROTEC
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 devic
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 raw midi on a stream. That stream is _from_ alsa seq. It is
doing
the bandwith
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 m
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
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 strea
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
Emmanuel Fleury wrote:
I have also a freez.
This is on the midipart. I have got it two times now. And the oops is not
in my kernel log so I got it by paper. I hope this can help.
My test is simple:
run pmidi-1.5.4 (more then one at once)
And start and stop them with kill -STOP/-CONT.
After a whi
dave willis wrote:
> On Sat, 13 Oct 2001, Peter Enderborg wrote:
>
> > dave willis wrote:
> >
> > > you must be thinking of someone else. all of their products list win2k
> > > except for the portmans, but they are old-school.
> >
> > Im a not
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 mus
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 win
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
29 matches
Mail list logo
