Re: [Alsa-devel] Aprenda o mejore sus idiomas
On Wed, 10 Apr 2002 08:23:07 "londonlanguages" <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] >LONDON LANGUAGE INSTITUTE >Información y reservas Tel.902180066 Fax 931479444 londonlanguages >CLASES CON PROFESOR PRESENCIAL. > >Le ofrecemos un sistema único y genuino de FORMACIÓN "A MEDIDA" para >aprender >IDIOMAS, nuestros profesores se desplazan a su oficina o >domicilio particular. >No importa el nivel que tenga o que disponga de poco tiempo. >Los cursos se diseñan con Ud. para cubrir sus necesidades en las áreas >profesionales >y sociales que le interesan. Pero la reputa madre que te pario, porque no te metes tu spam bien en el orto, te voy a llenar de abogados infeliz.. (damned spam). ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] UDA1341TS (iPAQ H3X00) sound driver for ALSA
Hi all, updated version of $SUBJ is available in ALSA CVS. Let try it and enjoy it. Comments, bugreports and opinions are welcomed. Bye -- Tomas Kasparek (sioux, xkaspa06) tomas.kasparek@[seznam.cz,volny.cz] [EMAIL PROTECTED] student FIT VUT Brno ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] 0.9 ooops... undefined reference to atexit in libm.so.6
Hello everybody... Er... After my migration from 0.5 to 0.9, I've tried to recompile my application about rawmidi. So, my include is now #include . Compilation is good, but linking says "/usr/lib/libm.so.6 : undefined reference to 'atexit' "??? What's goin' on ? Thanx ! Charles PS : If I've really understood, it's better to use 0.9 than 0.5, isn't it ? ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] 0.9 ooops... undefined reference to atexit inlibm.so.6
i had the same problems while compiling alsa-lib and alsa-apps, which depends on alsa-lib. after linking it to libm this error disapears. i really dont know why, there was some changes in glibc, read the glibc FAQ. On Wed, 10 Apr 2002, Charles [iso-8859-1] Flèche wrote: > Hello everybody... > > Er... After my migration from 0.5 to 0.9, I've tried to recompile my > application about rawmidi. So, my include is now #include > . Compilation is good, but linking says > "/usr/lib/libm.so.6 : undefined reference to 'atexit' "??? > > What's goin' on ? > > Thanx ! > > Charles > > PS : If I've really understood, it's better to use 0.9 than 0.5, isn't > it ? > > ___ > Alsa-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/alsa-devel > ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] RE: UDA1341TS (iPAQ H3X00) sound driver for ALSA
I would prefer that the ALSA driver for the iPAQ have a different name than the OSS driver for the iPAQ, since they have different interfaces. How about h3600-alsa? Jamey > -Original Message- > From: Kasparek Tomas [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 10, 2002 6:32 AM > To: [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: UDA1341TS (iPAQ H3X00) sound driver for ALSA > > > Hi all, > > updated version of $SUBJ is available in ALSA CVS. Let try it > and enjoy > it. Comments, bugreports and opinions are welcomed. > > Bye > > -- > > Tomas Kasparek (sioux, xkaspa06) >tomas.kasparek@[seznam.cz,volny.cz] >[EMAIL PROTECTED] > student FIT VUT Brno > > > --- > Subscription options: > http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel > FAQ/Ettiquette: > http://www.arm.linux.org.uk/armlinux/mailinglists.php > > ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] sequencing ALSA ports and clients
Ok, earlier I sent this question to LAD but this is probably a better place to be asking it. Apologies if you've already seen it. Basically I'm still confused about synth clients and ports. My SBLive presents four synth ports as default. I create a port and subscribe or connect_to a specfic SBLive port and client. When I'm sequencing out to this port should I be multiplexing among the other ports to exploit the synth's full polyphony? Should I be adding to the ports myself or can I get away with just using the one? If the latter then why are there four ports made available? I'm sure there's a dunce's document someone can point me to! R -- http://www.all-day-breakfast.com/rosegarden http://www.bownie.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] RE: UDA1341TS (iPAQ H3X00) sound driver for ALSA
On Wed, 10 Apr 2002, Hicks, Jamey wrote: > > I would prefer that the ALSA driver for the iPAQ have a different name > than the OSS driver for the iPAQ, since they have different interfaces. > How about h3600-alsa? No. Please pick a relevant name. H3600 is not the only device with an UDA1341 out there. Nicolas ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] RE: UDA1341TS (iPAQ H3X00) sound driver for ALSA
> -Original Message- > From: Nicolas Pitre [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 10, 2002 9:47 AM > To: Hicks, Jamey > Cc: Kasparek Tomas; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: RE: UDA1341TS (iPAQ H3X00) sound driver for ALSA > > > On Wed, 10 Apr 2002, Hicks, Jamey wrote: > > > > > I would prefer that the ALSA driver for the iPAQ have a > different name > > than the OSS driver for the iPAQ, since they have different > interfaces. > > How about h3600-alsa? > > No. Please pick a relevant name. H3600 is not the only > device with an UDA1341 out there. The alsa driver mentioned is iPAQ specific. It would be useful to restructure it in the way the other SA11x0/UDA134x driver is structured. Jamey ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] sequencing ALSA ports and clients
Hi Richard, At Wed, 10 Apr 2002 14:38:04 +0100, Richard Bown wrote: > > Ok, earlier I sent this question to LAD but this is probably a better place > to be asking it. Apologies if you've already seen it. > > Basically I'm still confused about synth clients and ports. My > SBLive presents four synth ports as default. I create a port and > subscribe or connect_to a specfic SBLive port and client. When I'm > sequencing out to this port should I be multiplexing among the other > ports to exploit the synth's full polyphony? what do you mean exactly "full polyphony"? if it means "playing tones with the same note number on the same channel on the same port at the same time", then, no, emu10k1 and sbawe drivers don't do this. notes are exclusive on the channel, i.e. you can play only a single note A on the channel 1. but of course, notes A can be played on different channels, or on different ports at the same time. if a note on the port 1 is affected by another port, then it's a bug of the driver (except the case when all 64 voices are exhausted). well, it's not difficult at all to reimplement the driver to allow multi-notes-on-a-channel, but i don't think it's common. > Should I be adding to the ports myself or can I get away > with just using the one? If the latter then why are there four > ports made available? I'm sure there's a dunce's document someone > can point me to! four ports are provided to support more than 16 channels. ciao, Takashi ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] RE: UDA1341TS (iPAQ H3X00) sound driver for ALSA
At Wed, 10 Apr 2002 09:55:43 -0400, Hicks, Jamey <[EMAIL PROTECTED]> wrote: > > > -Original Message- > > From: Nicolas Pitre [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, April 10, 2002 9:47 AM > > To: Hicks, Jamey > > Cc: Kasparek Tomas; [EMAIL PROTECTED]; > > [EMAIL PROTECTED] > > Subject: RE: UDA1341TS (iPAQ H3X00) sound driver for ALSA > > > > > > On Wed, 10 Apr 2002, Hicks, Jamey wrote: > > > > > > > > I would prefer that the ALSA driver for the iPAQ have a > > different name > > > than the OSS driver for the iPAQ, since they have different > > interfaces. > > > How about h3600-alsa? > > > > No. Please pick a relevant name. H3600 is not the only > > device with an UDA1341 out there. > > The alsa driver mentioned is iPAQ specific. It would be useful to restructure it in >the way the other SA11x0/UDA134x driver is structured. the alsa modules have "snd-" prefix, so they don't conflict with others anyway. IMO, if the driver is iPAQ specific, i prefer a simple name such as snd-ipaq or snd-ipaq-h3x00. if a part of the driver will be shared by others, then we can split it to a lowlevel module with a proper device name. just my $0.02. ciao, Takashi ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] sequencing ALSA ports and clients
Hi, Takashi Iwai wrote: > what do you mean exactly "full polyphony"? I just meant getting your hands on the full polyphony of the synth. Now I've realised that the sequencer interface (sensibly) treats the on-board synth like any other MIDI device. > it's not difficult at all to reimplement the driver to allow > multi-notes-on-a-channel, but i don't think it's common. No, that's fine. I got a good reply from Matthias on LAD about the same subject and as I said to him I think I'm still suffering under the old OSS delusion that synth devices were still somehow "special" and the application had to deal with its own voice allocations. I was looking for a complicated explanation to the behaviour I was seeing in my undoubtedly buggy code! It took me so long to get my head around that OSS synth idea that I'm having trouble letting go. > four ports are provided to support more than 16 channels. This is good stuff. It all makes sense now. Thanks, R -- http://www.all-day-breakfast.com/rosegarden http://www.bownie.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] RE: UDA1341TS (iPAQ H3X00) sound driver for ALSA
On Wed, 10 Apr 2002, Takashi Iwai wrote: > > > > I would prefer that the ALSA driver for the iPAQ have a > > > different name > > > > than the OSS driver for the iPAQ, since they have different > > > interfaces. > > > > How about h3600-alsa? > > > > > > No. Please pick a relevant name. H3600 is not the only > > > device with an UDA1341 out there. > > > > The alsa driver mentioned is iPAQ specific. It would be useful to restructure it >in the way the other SA11x0/UDA134x driver is structured. > > the alsa modules have "snd-" prefix, so they don't conflict with > others anyway. > > IMO, if the driver is iPAQ specific, i prefer a simple name such as > snd-ipaq or snd-ipaq-h3x00. if a part of the driver will be shared by > others, then we can split it to a lowlevel module with a proper device > name. Hmm ,I expected comments to driver quality and behavior, not to its name :). This is first public release of the driver. UDA1341TS specific part is placed in "snd-uda1341" module and should be ARM-independent. The rest is placed in snd-h3600-uda1341. There you could find H3x00 specific parts same as a bit of SA1100 DMA code. The SA1100 DMA stuff could be moved into independent module (like sa1100-audio in OSS), but it's just "few lines" of code now. The driver could be structuded better of course, but I don't have any other ARM and/or UDA1341 device to be able to exactly select parts which are common. This first release is intended for basic functionality tests. I think, there is enough time to discuss final names of modules. Bye -- Tomas Kasparek (sioux, xkaspa06) tomas.kasparek@[seznam.cz,volny.cz] [EMAIL PROTECTED] student FIT VUT Brno ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel]
Title: Bu ileti Sayesinde sizlerde yabancý ülkelerdeki gibi türkiyedeki en ucuz ürünlerden haberdar olacaksýnýz bizim amacýmýz reklam veren Bu ileti Sayesinde sizlerde yabancý ülkelerdeki gibi türkiyedeki en ucuz ürünlerden haberdar olacaksýnýz bizim amacýmýz reklam veren firmalarýn ürünlerini sizlere en iyi bir þekilde tanýtmak bunun için yerleþim verlerine göre ürün tanýtýmlarýný göndermekdir Aþaðýdaki Bilgileri girip gönderirseniz sizde en iyi þekilde çevirnizdeki ucuzluktan faydalalýn Varsa arkadaþlarýnýzsýn mail adreslerinide yazabilirsiniz. Mail Listesi Bulunduðunuz Ýl;Semt : E-mail: ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel]
On Wed, 10 Apr 2002 23:33:23 "metin" <[EMAIL PROTECTED]> wrote: > Bu ileti Sayesinde sizlerde yabancý ülkelerdeki gibi türkiyedeki en ucuz ürünlerden >haberdar olacaksýnýz bizim amacýmýz reklam veren > > Bu ileti Sayesinde sizlerde yabancý ülkelerdeki gibi türkiyedeki en ucuz ürünlerden >haberdar olacaksýnýz bizim amacýmýz reklam veren firmalarýn ürünlerini sizlere en iyi >bir þekilde tanýtmak bunun için yerleþim verlerine göre ürün tanýtýmlarýný >göndermekdir > > Aþaðýdaki Bilgileri girip gönderirseniz sizde en iyi þekilde çevirnizdeki ucuzluktan >faydalalýn > > Varsa arkadaþlarýnýzsýn mail adreslerinide yazabilirsiniz. > Mail Listesi > > Bulunduðunuz Ýl;Semt : > > E-mail: > haberdar sizlerdeiyi mail adreslerinide, whathever that means! and to your mom too. (haha, mail adreslerinide) (evil spam ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
