Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

7516 discussions

by hexe_2003＠directbox.com

Hello ! I am interested how 2.6.X Linux kernel will handle OSS. I mean that alsa is the driver-layer for these kernels, are OSS-drivers/applications still supported ?? greez, Sascha Retzki __________________________________________________ Verpassen Sie keine eBay-Auktion und bieten Sie bequem und schnell über das Telefon mit http://www.telefonbieten.de Ihre eMails auf dem Handy lesen - ohne Zeitverlust - 24h/Tag eMail, FAX, SMS, VoiceMail mit http://www.directbox.com

22 years

[linux-audio-dev] Question regarding the alsa's audio latency benchmark

by Ivica Bukvic

Hi all, I've had an interesting discussion with a professor and a distinguished member of the electroacoustic music community regarding audio latencies which made me realize that I did not understand the issue in its entirety. Hence, I looked around the net in order to educate myself. I soon stumbled across the following site: http://old.lwn.net/1999/0916/a/latency.html Admittedly, it's quite old but that, if anything speaks only in Linux's favor in terms of its pro-audio readiness. At any rate, I was checking out the benchmark data and was wondering as to how did this person/software app get to the 0.73ms buffer fragment that is equal to 128bytes? In other words, what sampling rate was used? 128 bytes in 44100Hz sampling rate = 3ms 128 bytes in 88200Hz sampling rate = 1.45ms 128 bytes in 176400Hz sampling rate = 0.725ms (this one being obviously closest, but at the same time, what kind of hardware supports this sampling rate, especially in 1999 when this test was done?) 128 bytes in 192000Hz sampling rate = 0.3ms So what gives? It seems like it is some kind of a 176k-ish sampling rate that, AFAIK does not exist. Furthermore, my question is what app was used to produce those graphs/results and whether these latency tests take into account hardware latencies (i.e. DSP converters, PCI->CPU->PCI->output etc.), in other words, is this latency that is achievable with the following setup: Input->soundcard->cpu(with some kind of DSP)->soundcard->Output Your help on this matter is greatly appreciated! Ivica Ico Bukvic, composer & multimedia sculptor http://meowing.ccm.uc.edu/~ico

22 years, 1 month

[linux-audio-dev] Audio in Museum powered by Linux

by Benno Senoner

Hi, yesterday was the opening of the "Southtyrol game", one of the worlds largest hand carved pinball style game machines. (length: 11 metres, weight: 2.6 tons, 16 audio speakers) It is an interesting combination of art, electronics and audio powered by Linux. The game is located in Southtyrol - Italy in a museum dedicated to tourism. The audio part was implemented by me. I created a webpage with a description and some movie clips that demonstrate how the game works. http://www.linuxdesktop.it/benno/southtyrolgame/ Thanks to all Linux developers in particular the LADers that made audio under Linux a viable solution ! comments ? PS: would such a story qualify for slashdot ? Just try to submit it if you want ;-) cheers, Benno http://linuxsampler.sourceforge.net ------------------------------------------------- This mail sent through http://www.gardena.net

22 years, 1 month

[linux-audio-dev] Call for participation: MMA GMPI working group

by RonKuper＠Cakewalk.com

The Generalized Music Plug-In Interface (GMPI) working group of the MIDI Manufacturer's Association (MMA) is seeking the input of music and audio software developers, to help define the technical requirements of GMPI. The objective of the GMPI working group is to create a unified cross-platform music plug-in interface. This new interface is hoped to provide an alternative choice to the multitude of plug-in interfaces that exist today. Among the many benefits of standardization are increased choice for customers, lower cost for music plug-in vendors and a secure future for valuable market-enabling technology. Like MIDI, GMPI will be license free and royalty free. Phase 1 of the GMPI working group's effort is to determine what is required of GMPI: What sorts of capabilities are needed to support existing products and customers? What are the emerging new directions that must be addressed? Phase 1 is open to any music software developer and is not limited to MMA members. It will last a minimum of three months, to be extended if deemed necessary by the MMA. Discussions will be held on an email reflector, with possible meetings at major industry gatherings such as AES, NAMM and Musik Messe. Following the collection of requirements in Phase 1, the members of the MMA will meet to discuss and evaluate proposals, in accordance with existing MMA procedures for developing standards. There will be one or more periods for public comment prior to adoption by MMA members. If you are a developer with a serious interest in the design of this specification, and are not currently a member of the MMA, we urge you to consider joining. Fees are not prohibitively high even for a small commercial developer. Your fees will pay for administration, legal fees and marketing. Please visit http://www.midi.org for more information about membership. To participate, please email gmpi-request(a)freelists.org with the word "subscribe" in the subject line. Please also provide your name, company name (if any) and a brief description of your personal or corporate domain of interest. We look forward to hearing from you. Sincerely, Ron Kuper GMPI Working Group Chair

22 years, 1 month

[linux-audio-dev] any LADCCA lists?

by "horsh

Hi, is there any LADCCA discussion mailing list? horsh PS: this is STRANGE my messages get through to LAU list okay, but I have to resend this particular message to LAD third time (I subscribed) and get no notifications, and don't see my messages in archives.

22 years, 1 month

[linux-audio-dev] Sick of rebooting

by Hans Fugal

I'm hoping there's a simple solution to this that I've just missed somewhere along the line. Occasionally something will crash while using oss emulation and I can't use the sound card until I reboot. I've tried lsof /dev/dsp and as many other variations as I can think of and I never get anything (even when sound is playing), which I think is related to using devfs. I've also tried fuser, and good old visual grep on the output of ps and nothing is running that would use the soundcard yet I can't unload the snd-pcm-oss module. This time it was timidity (which I have promptly uninstalled since this version seems capable of nothing other than locking up my soundcard), but it has been mplayer in the past. Is there some way to restore access to the sound card short of rebooting? -- Hans Fugal | De gustibus non disputandum est. http://hans.fugal.net/ | Debian, vim, mutt, ruby, text, gpg http://gdmxml.fugal.net/ | WindowMaker, gaim, UTF-8, RISC, JS Bach --------------------------------------------------------------------- GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460

22 years, 1 month

[linux-audio-dev] oss wrapper

by Hans Fugal

esound has a wrapper of some sort that will take most oss applications and play them via esound. Is there some sort of equivalent for jack or perhaps alsa? It would be different from oss emulation in alsa in that it would be user-space and explicitly invoked. I ask for three reasons. The first might just be ignorance, but I can't figure out how to use the oss emulation for my second card - things just play through the first card. Some sort of wrapper could help direct it to wherever I want it to go. The second (if it were jack) is to do mixing. The third reason is I'm curious to see which programs are still using oss, but not curious enough to go look at the docs/source of every program. This way I'd see sound doesn't work but could still run the program with the wrapper and get sound. -- Hans Fugal | De gustibus non disputandum est. http://hans.fugal.net/ | Debian, vim, mutt, ruby, text, gpg http://gdmxml.fugal.net/ | WindowMaker, gaim, UTF-8, RISC, JS Bach --------------------------------------------------------------------- GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460

22 years, 1 month

Re: [linux-audio-dev] GMPI?

by John Lazzaro

> Steve Harris <S.W.Harris(a)ecs.soton.ac.uk> writes: > > Standards processes that I've been exposed to generally mandate regular > weekly meetings (teleconference and/or irc), with less frequent > face-to-face meetings and most business is sorted out during the meetings. > Email is only used for tying up loose ends and exchanging text, minuites > etc. The IETF is a successful counter-example -- email is the only way any decision can be made, meetings are optional, and no decision made at any meeting is binding until consensus occurs on the mailing list to confirm it. I'm hesitant to comment further about GMPI and its chances for success or failure, because I've been too busy trying to finish RTP MIDI to keep a close eye on it. My only worry stems from a common IETF belief -- that the standards process is a great way to polish and reach consensus on a substantially complete design, but using the standards process as the vehicle to do the design is a much harder road to hoe. A good example of this is 801.11, which was an incredibly long and painful experience because many parties brought bits and pieces of wireless Ethernet to the IEEE table. Only the inherent goodness of the core idea (packet radio) kept everyone at the table to eventually produce a standard that could be interoperably deployed (801.11b, aka Wi-Fi, and its lettered follow-ons). ------------------------------------------------------------------------- John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro -------------------------------------------------------------------------

22 years, 1 month

Re: [linux-audio-dev] GMPI?

by Steve Harris

On Mon, Sep 29, 2003 at 09:08:31 -0700, Tim Hockin wrote: > On Mon, Sep 29, 2003 at 09:06:06AM +0100, Steve Harris wrote: > > I have my own thery about why it didnt work out, but I'm keeping my mouth > > shut for once :) > > Don't do that! :) I want to learn from the failure of this process, even if > it was entirely my fault. Please share, even privately. The reason I'm keeping my mouth shut is not reluctance to offend anyone :) its because it wont help, and I dont want to be too negative about it. Standards processes that I've been exposed to generally mandate regular weekly meetings (teleconference and/or irc), with less frequent face-to-face meetings and most business is sorted out during the meetings. Email is only used for tying up loose ends and exchanging text, minuites etc. The W3C (for example) are quite stict about it - if you miss too many meetings or face-to-face's then you're not allowed to vote for the rest of the process. Sadly that wont really work for GMPI as there are too many key contributors who couldn't, or wouldn't commit to weekly meetings. I dont think the GMPI process is domed, its just likely to be slow. The recent suggestions should help. Also, the fact that theres no real pressing need for it doesnt help either - most platforms allready have OK instrument APIs and we have ALSA Seq + JACK for synths, which does work. - Steve

22 years, 1 month

[linux-audio-dev] GMPI?

by Juhana Sadeharju

>discussion about it moved to the GMPI list. GMPI is an industry-wide >attempt to define a platform+vendor neutral music plugin API. > > majordomo: gmpi-request(a)freelists.org > archives: http://www.freelists.org/archives/gmpi Is there a digest mode? (I'm not familiar with majordomo.) Could anyone post a summary about what has been discussed, what about is discussed now, and what are open issues? Juhana

22 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-dev