Linux-audio-dev March 2004

linux-audio-dev@lists.linuxaudio.org

73 participants
85 discussions

[linux-audio-dev] Announcing USound, the Useful Sound Daemon, version 0.2.0

by Matt Campbell

USound (the Useful Sound Daemon) is an audio I/O daemon for Unix systems, especially GNU/Linux. It provides low-latency mixing of multiple audio streams with resampling and limited format conversion, as well as audio recording. The package also includes a client library, a libao plugin, and patches for madplay and MPlayer. USound is free software; it is distributed under the GNU General Public License (GPL), except for the client library, which is in the public domain. USound is somewhat similar to the Enlightened Sound Daemon (EsounD); but as the name implies, USound aims to be more useful, particularly for consumer desktop and multimedia applications. Applications for which USound is suitable include media players, audio and video conferencing software, text-to-speech software, and any application that plays the occasional sound file to alert the user. USound is still under development and by no means perfect, but in my (admittedly biased) opinion, it has already surpassed EsounD and aRts in usefulness. The USound home page is at: http://pobox.com/~mattcampbell/usound/ Have fun! Matt (who is listening to an MP3 with USound and madplay right now)

20 years, 9 months

[linux-audio-dev] USB Keyboards

by Jens M Andreasen

Hi! Anybodyelse been shopping around for a USB keyboard lately? How come that the offerings available have just about all of the features and flexibility that anyone would want, BUT when it comes to playability of the keyboard itself, then .. how to say .. then it seems like just another sloppy disaster. I have one (as yet) unpatented idea for a cheap-to-build funky keyboard. Anybody have a workshop? /jens

20 years, 9 months

[linux-audio-dev] Status of mLAN?

by Jody McIntyre

What's the status of mLAN on Linux? I found a few discussions in the archives, the latest being http://eca.cx/lad/2003/12/0084.html , but nothing really conclusive. It seems that there is documentation (and even an implementation) for A/M, but nothing for Connection Management. Has anyone tried recently to get documentation? Based on http://www.yamaha.co.jp/tech/1394mLAN/english/ptt.html , it seems that documentation is available for a nominal fee, but it is more than I am willing to pay. I am considering buying a PreSonus FireStation, which does what I need at half the cost of an RME Hammerfall, and am willing to spend a considerable amount of time writing a driver, if documentation is available. Thanks for any information, Jody

20 years, 9 months

[linux-audio-dev] player suggestion

by Juhana Sadeharju

Hello. After years of waiting, AlsaPlayer succeeded to compile. Here is a report. I post here so that authors of other players can take the hints. Given multiple files, I executed the following: alsaplayer *wav All files are played ok, yes. But when one hits (|<) button the player skips two files back and plays only the two last files. Should it skip to the begin of the last file? Or to the begin of the file list? Not something in between. I also suggest a mode in which the play slider represents the all files concatenated together: o----file1---o----file2----o----file3----o That way one has easier access to all files. The mode would be specially good if one has tens of small sound samples. Also: If I first press <stop>, then why (|<) starts the playing? I just want move to the begin and then play later. So, my suggestion: If player is playing and one presses (|<), it continues playing. If player is not playing and one presses (|<), it only skips to the begin. Further: The playing stops at the end of file, making it impossible to continue scrubbing and speeding infinitely. The player should just stay at the end at the play state. Likewise when playing in reverse direction: player should not go to the stop state at the begin. More: The player played the file and stopped. I moved the play slider to middle and started the play: the player started playing at the begin, not where the play slider was at. Neverending: The playing has been stopped and the play slider is at the begin. I try grab and move the play slider, but nothing happens. I should be able to move the play slider at any point and start playing there. Now playing can start only at the begin. Infinity: After speeding backwards to the begin, the player stopped. Then by pressing play button, I got the following errors and nothing was played: an ERROR occured or EOF (10793). -*- Given that AlsaPlayer has been developed for years now, why I found so many problems? Most of the problems are not technical, but artistic. I have alsaplayer 0.99.76. Regards, Juhana

20 years, 9 months

Re: Re: [linux-audio-dev] Major problem with RME HDSP/Multiface and a 64-bit AMD laptop

by ico＠fuse.net

Hi, > wait ... this seems to be similar to the problem i have with my hdsp ... > i can't run it on my linux system at all, althouth it works fine with > windows xp: > > can you try jack as super user with -R flag? I will try to next week. Right now I am in a bind until this coming Sunday. I will let you know as soon as I am done. > > if you use an input signal, some of the input gets copied to the output > if a sound application is running, which results some distortion ... > could you start jack / pd, and try to use any of the input channels try > several settings of hdspmixer... > > the problem with my hdsp is definitely a cardbus driver issue ... from > what i heard from people who tried to help me is, that there are some > problems in mapping the memory from the kernel to the buffer inside the > cardbus bridge ... > the problem with the kernel driver for the yenta socket is, that it's > not properly supported ... thomas charbonnel, who maintains the hdsp > driver and i wrote a message to both the kernel and the pcmcia-cs > mailing-list, but didn't get any answer... > > of course, it could be a problem of the cardbus controller hardware, > that the windows driver may handle differently than the yenta-socket > module for linux my machine has an o2micro cardbus controller, that, > conserning rme's support may produce problems ... > i'm able to sell my notebook to my mother ;-) and get a new one, soon... > the only reason, why i won't get an amd64 is that the notebooks that are > equipped with this chip, have either ene or ricoh cardbus controllers, > controllers rme warns against ... that's why i'll order a p4 inspiron, > soon... I would encourage you to hold off for a couple months, of course if you can afford to wait. It took me literally a good year on my old Inspiron 8000 (later replaced for 8100) before most of the quirks were resolved on it (both Win32 and Linux-side). This is pretty much the case with most of the new technology. For instance my newest toy, the aforementioned m6807 by eMachines has been on the market for barely 2 months and it is in dire need of a BIOS update. Hopefully one will be released by eMachines (although I am a bit skeptical about this one as most of their other products don't have such low-level updates available), but if not, there are plenty of other resellers that might since this model is being rebranded by over half-dozen companies across the world. > > anyway, when i talked to thomas a short time ago, he considered going to > the lad conference, i'll go there, and concerning the schedule, you'll > be there, too ... maybe we could try to track this problem down and try > to contact the kernel mailinglist again... Absolutely! Looking forward to meeting you! > > i hope that you will be more luck than i was ... > Thanks :-) Best wishes, Ico

20 years, 9 months

[linux-audio-dev] [ANN] vsti v0.0.2

by Kjetil Svalastog Matheussen

http://www.notam02.no/arkiv/src/ vsti v0.0.2 SHORT DESCRIPTION Run a windows vsti plugin as a jack and alsa-seq client. REQUIRES alsa(>=0.9), jack(>=0.94), python(>=2.0) and vstserver(>=3.0). (might work with lover versions) INSTALL 1. Set the INSTALLPATH and JACKINSTALLPATH variables in the top of the Makefile. 2. make 3. sudo make install USAGE The name of the executable is "vsti". Run it with the plugin-name as the last argument, and quit by pressing return. Examples: "vsti JX220" "vsti B4" "vsti --help" LICENSE GPL CREDITS Made by Kjetil S. Matheussen, k.s.matheussen(a)notam02.no. Sponsored by Lionstracs, manufacturer of Linux based musical instruments http://www.lionstracs.com. --

20 years, 9 months

[linux-audio-dev] we need some delegates for mLAN@musikmesse

by Paul Davis

I got this today from Yamaha: ---------------------------------------------------------------------- Thank you for your e-mail about Linux community's interest in mLAN. We think that it might be good to have a chance to meet with you or other person from the Linux audio development community and explain the current status and activity of mLAN. We will be available at a couple of exhibitions such as Musikmesse, AES Berlin soon. Or we may have a separate meeting. Please let us know your preference. We look forward to hearing from you soon. ---------------------------------------------------------------------- Unfortunately, the ZKM meeting is basically a 100% overlap with the musikmesse. I don't see any feasible way to do a meeting with Yamaha that weekend. Is anybody else interested (anyone who considers them up enough on 1394 and associated technologies to go talk to Yamaha)? Alternatively, does someone see a way to combine LAD@ZKM and the musikmesse? --p

20 years, 9 months

[linux-audio-dev] Major problem with RME HDSP/Multiface and a 64-bit AMD laptop

by Ivica Ico Bukvic

First off I would like to extend my sincere apologies for my atrocious cross-posting. I am currently in a rather desperate situation and would highly appreciate any help I can get in this matter. <Begin long blurb> I recently got my hands on the eMachines M6807 64-bit Athlon 3000+ and I must say that the notebook is very nice. The gripes I do have about it are mostly of cosmetic nature. The performance is in many ways unmatched. After owning the notebook for just about a month I finally found some free time to install the Multiface/HDSP on it. I was immediately very unpleasantly surprised by the fact that the sound output using the ASIO drivers (and Linux ALSA drivers) yielded similar results -- distorted audio. Now here's the catch. When I use the soundcard in mme, DirectX, or any other driver form, the soundcard works perfectly (albeit no multichannel capability). But when I use ALSA in Linux or ASIO in Windoze (XP Home version), the sound plays as if it's interpreted slower than it should be (2 whole steps, or 4 semitones lower and comparably slower) with a bad distortion, as if one is using a very lousy vocoder. There are no drop-outs or choppiness (I did not try JACK, though, so I don't know about the explicit xruns) which leads me to believe that the throughput is not the culprit, but the output simply is useless. Here's some additional info/problems I am aware of: 1) The manufacturer of the notebook is Arima (company that supplies many other companies with the same chipset/chasis) has shipped this notebook with a crappy BIOS (Linux at boot time complains about DSDT being all fubared and fails to properly allocate IRQ's with the acpi turned on; also apic seems to be fubared as well). Some of these issues have been addressed in the 2.6.2 kernels via several patches with a spotty success and currently I need to boot with no acpi or apic to get everything working properly (otherwise almost no peripheral works properly). So, I know for a fact that BIOS is sucking rather bad... Contacting support so far has only suggested that there should be some bios updates coming up soon, but I'll believe it when I see it (OTOH this model is supposedly selling rather well as it has been apparently licensed by at least 6 different companies across the world including the voodoopc, so I guess that should provide some leverage). 2) I am using Mdk 10.0 Community release. No problems there that I can notice. Installed the hdsp utils and everything worked like a charm, except of course for the sound output. 3) The pcmcia card in XP is detected as the generic pcmcia and is using default XP drivers without any conflicts and/or apparent problems. 4) The pcmcia card (at least in Windows) is sharing its IRQ only with the HDSP when plugged in (IRQ 17 -- there are total of 24 due to APIC being enabled in XP), but I don't think that should be considered a conflict (please correct me if I am wrong). 5) In Linux due to fact that the computer boots without APCI and APIC enabled, my guess is that it is using only first 15 IRQ's (like the old APM-based PC), although I need to further investigate this. To the best of my knowledge no IRQ conflicts have been reported by the syslog when using this setup. 6) The pcmcia cardbus is using the yenta_socket driver in Linux, but curiously cannot be used with the APCI (most likely due to fubared BIOS), as that immediately freezes the system. 7) In Windows, I tried 2.53 and 2.62 drivers, with the latest firmware (11). Using different drivers made no difference. I tried several ASIO-capable applications in order to make sure this was the case. 8) No errors during use of Multiface are reported in either Linux nor Windows. Finally, having used Multiface on Inspiron laptops, I am quite familiar with the sound that is being generated by the lousy throughput (crackly stuff) and I must say that while this sounds very similar, there are couple of things that make this sound different: 1) No matter which latency I select in hdsp configuration tool, the sound remains the same. 2) When overclocking the laptop (this beast that runs at 1.8GHz oc's via software without a hitch to 2GHz with no overheating and no instability whatsoever), the pitch and the speed of the output rises (wtf?). At 2GHz it's about 2 semitones higher (and comparably faster). I am having a feeling that if I could oc it for another 200MHz, I would have the right playback speed :-). OTOH, when the laptop downclocks to preserve battery (800MHz) the sound playback remains at approx. the same speed but with a timbrally somewhat different artifacts like the one at 1800MHz. 3) When using mme, or DirectX or any other non-ASIO playback format in Windows, no matter what the latency in the hdsp config tool, the sound output is flawless. 4) I also read that some of the 2.6.2 Linux kernel patches were incorporated to fix the fact that Bios represents the CPU speed (via ACPI?) as 1600MHz which is apparent in the Windows if one right-clicks on the My Computer icon and clicks on Properties. However, programs like CpuID read the frequency properly as 1800MHz. 5) FSB on this beast to the best of my knowledge should be plenty fast (200MHz x ? -- I heard it's like 1600MHz (8x), but I find that hard to believe). Hence, I would be seriously surprised that it is a case of a lousy cardbus implementation... Although, I guess everything is possible... <end long blurb> Whew! That should be about it. If you need any syslogs or any other info, please contact me and I will gladly provide them. I would simply appreciate any insight at this point as I have purchased this laptop primarily for the music-making purposes and not being able to use it with the expensive Multiface makes either this laptop or the Multiface an expensive brick (I say this as I did hear that M-Audio Firewire 410 runs just fine in combination with this notebook). Cc: RME support US/international LAD/LAU Alsa-dev/user I would also appreciate any help from the RME tech department as this may potentially stem from the fact that the system is 64-bit (although I am NOT running 64-bit versions of either Windows or Linux) and that the drivers are somehow not taking that into account. Best wishes, Ivica Ico Bukvic, composer & multimedia sculptor http://meowing.ccm.uc.edu/~ico/

20 years, 9 months

[linux-audio-dev] ANN: cmpci 6.64 released

by C.L. Tien - 田承禮

Hi, I made many changes for cmpci.c since last release. Changes are made as follows: 1. Fix the S/PDIF out programming bug appeared in 6.16. 2. Support 8338 4-channel playback. 3. S/PDIF loop can be used after AC3 playback. 4. Legacy devices (FM, MPU401 and gameport) are served by other modules. Now the code is thinner. 5. Remove parameters setting from kernel configure menu, they can be set easily when loading the module. 6. Add spdif_out to output 44.1K/48K 16-bit stereo to S/PDIF out. 7. Add hw_copy to duplicate audio of front speakers to surround speakers. 8. Change code to minimum patch for kernel 2.6. The attached cmpci.c in cmpci-6.64.tar.bz2 is the updated driver, and 46.diff is the patch file that needed for kernel 2.6. The cmpci-patch-2.4.25.tar.bz2 and cmpci-patch-2.6.4.tar.bz2 are patches for kernel 2.4.25/2.6.4 tree patch, they are needed to support legacy devices, otherwise you may ignore them. The cmi8738.tar.bz2 contains CMI8738, which is modified from CMI8338. It describe the parameters cmi8738 can support. Please feedback if you have any question, I will post to kernel maintaner if no serious problem with it. Sincerely, ChenLi Tien

20 years, 9 months

[linux-audio-dev] [announcement] kluppe 0.1

by d

hi everyone! this is the announcement of my first standalone soundapp "kluppe". it's a jackified gtk-based loopplayer for files and live-input, supporting various playmodes. you can find it at http://dieb13.klingt.org/content/projects/kluppe.html since i'm not an advanced programmer, the sources are "learning-by-doing-code", but it works fine for me. i will be on tour next week, so i won't check my mail very frequently. please be patient if you have questions, bugreports... regards d13b -- Military intelligence is a contradiction in terms. -- Groucho Marx

20 years, 9 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

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 March 2004