Linux-audio-user

linux-audio-user@lists.linuxaudio.org

12 participants
20655 discussions

[linux-audio-user] min hardware requirements

by Bryan Koschmann - GKT

Hello, Can anyone give me some input on minimum hardware requirements for single track recording/playback? This machine will be updated later for multitrack, but right now I have the following to use: celeron 1 gig 256 or 512 megs ram 40 gig or 80 gig ata100 ibm harddrive soundblaster live value I may end up doing dual pentium 3 866 and 512 megs (or more) depending on how my upgrading goes (this is my old machine). I run would be running either slackware 8.1 or 9 with the alsa, jack, audacity/ardour combination. Any input would be great! Thanks in advance, Bryan

22 years, 6 months

Re: [linux-audio-user] Multi Port Midi Interface configuration

by Tracey Hytry

>There is a huge lack of any info here. I wish it was better, but we're all still learning it seems. >So my question is, have any of you successfully configured and used a >Multi-port midi interface with multiple synthesizers on Linux? > >What is your interface? (I'm specifically looking for 8 or more ports) > >How did you configure it? > >What software do you use with it? > >Much thanks to any replies, > >pawL Ok, here goes... First, muse works pretty well driving all of the synths through the MTP AV. The computer is an older 850MHz PIII with 926Meg Ram, an internal lvd scsi subsystem, and external CD writer. Running the RH 7.3 CCRMA setup off of one of the hard disks. Also Qua Synth. On the rack is: M Audio Delta 1010 Mark of the Unicorn MTP AV midi timepiece (8x8 midi router, parallel port style) E-MU Proteus 2000 Roland Vintage Synth M-VS1 Roland JV-2080 Mackie CR1604-VLZ Mixer Keyboards(synths): Kurzweil K2600 xs Roland A-90 Alesis Quadra Synth Yamaha EX5 Alesis Andromeda A6 Misc: Roland SPD-20 Percussion Pad Line 6 POD ver. 2.0 --- Schector electric guitar Tascam DAT stereo recorder Technics CD player (2) Mackie HR824 studio monitors Peavey PC1600x that needs to be integrated into the system as an external controller for linux programs on the computer, and as a peddle controller for the POD. Anyway, things do work in linux now thanks to a lot of creative linux programers :) I'm pretty busy on other things(spring's coming and I need to pay attention to plants and things), so I don't have a lot of time with the computer audio stuff right now. Tracey.

22 years, 6 months

[linux-audio-user] Running Csound

by dbdbdb

Hi everyone! Can you tell me the way to run Csound in Linux. I downloaded the RPM package of the canonical (jffitch v4.23) but I don´t know what is next to RPMize it! (specially to get the executable in the PATH!). Thanks in advance. :-) -- dbdbdb kakarott(a)fastmail.fm -- http://www.fastmail.fm - Choose from over 50 domains or use your own

22 years, 6 months

[linux-audio-user] Anyone using multiface+cardbus?

by Jaakko Prättälä

Hi. Is anyone using rme multiface with the cardbus interface on a linux laptop? I'm thinking of buying one to use with live processing with pd. Are there any problems? Does midi work? I saw a message in the alsa-doc saying that you have to downgrade the firmware (in windows), is this still true? -- Jaakko Prättälä Jaakko.Prattala(a)Helsinki.FI

22 years, 6 months

[linux-audio-user] Laptop Sound

by Angel Gabriel

I have a Compaq Evo N400c, and I have absoulty no ida how to enable the sound. Is there a linux howto on sound setup? -- ***** Not everyone is touched by an Angel... ... Those that are, never forget the experience *****

22 years, 6 months

[linux-audio-user] modprobe failure installing ALSA for SB32 (AWE)

by Max Webb

I hope this isn't a stupid question, but I'm fairly inexperienced with both linux and the ALSA driver. I believe I followed the instructions closely for building and installing the driver, libs, and utilities for ALSA; I have a PnP soundblaster 32 (AWE) card (not isa), and selected the sbawe name for the card from the table at www.alsa-project.org/alsa-doc/ . Everything seemed to be going okay, until I got to doing the modprobe to install the module in the kernel. When I issued the "modprobe snd-sbawe" command, I got a failure. Since modprobe has a "-d" option, I have included it's output below, in case that yields a clue. I see that the insmod portion of the command failed, so I also issued that at top level, so you could all see the way that fails - issued by itself, it finds unresolved symbols - but I don't know if that is the way it failed inside modprobe. BTW, the "modprobe snd-seq-oss" failed with "device busy" - the other two modprobes seemed to succeed. Can anyone tell me what I need to do? Thanks in advance, Max Script started on Sun Mar 23 11:27:04 2003 sh-2.05a# modprobe -d snd-sbawe ============================================= Module soundcore kname soundcore objkey soundcore names: soundcore mode: NORMAL Module matching soundcore: /lib/modules/2.4.18/kernel/drivers/sound/soundcore.o.gz ============================================= ============================================= Module snd kname snd objkey snd names: snd mode: NORMAL Module matching snd: /lib/modules/2.4.18/kernel/sound/acore/snd.o ============================================= ============================================= Module snd-seq-device kname snd-seq-device objkey snd-seq-device names: snd-seq-device mode: NORMAL Module matching snd-seq-device: /lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq-device.o ============================================= ============================================= Module snd-rawmidi kname snd-rawmidi objkey snd-rawmidi names: snd-rawmidi mode: NORMAL Module matching snd-rawmidi: /lib/modules/2.4.18/kernel/sound/acore/snd-rawmidi.o ============================================= ============================================= Module snd-mpu401-uart kname snd-mpu401-uart objkey snd-mpu401-uart names: snd-mpu401-uart mode: NORMAL Module matching snd-mpu401-uart: /lib/modules/2.4.18/kernel/sound/drivers/mpu401/snd-mpu401-uart.o ============================================= ============================================= Module snd-timer kname snd-timer objkey snd-timer names: snd-timer mode: NORMAL Module matching snd-timer: /lib/modules/2.4.18/kernel/sound/acore/snd-timer.o ============================================= ============================================= Module snd-hwdep kname snd-hwdep objkey snd-hwdep names: snd-hwdep mode: NORMAL Module matching snd-hwdep: /lib/modules/2.4.18/kernel/sound/acore/snd-hwdep.o ============================================= ============================================= Module snd-opl3-lib kname snd-opl3-lib objkey snd-opl3-lib names: snd-opl3-lib mode: NORMAL Module matching snd-opl3-lib: /lib/modules/2.4.18/kernel/sound/drivers/opl3/snd-opl3-lib.o ============================================= ============================================= Module snd-sb-common kname snd-sb-common objkey snd-sb-common names: snd-sb-common mode: NORMAL Module matching snd-sb-common: /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb-common.o ============================================= ============================================= Module snd-sb16-csp kname snd-sb16-csp objkey snd-sb16-csp names: snd-sb16-csp mode: NORMAL Module matching snd-sb16-csp: /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16-csp.o ============================================= ============================================= Module snd-page-alloc kname snd-page-alloc objkey snd-page-alloc names: snd-page-alloc mode: NORMAL Module matching snd-page-alloc: /lib/modules/2.4.18/kernel/sound/acore/snd-page-alloc.o ============================================= ============================================= Module snd-pcm kname snd-pcm objkey snd-pcm names: snd-pcm mode: NORMAL Module matching snd-pcm: /lib/modules/2.4.18/kernel/sound/acore/snd-pcm.o ============================================= ============================================= Module snd-sb16-dsp kname snd-sb16-dsp objkey snd-sb16-dsp names: snd-sb16-dsp mode: NORMAL Module matching snd-sb16-dsp: /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16-dsp.o ============================================= ============================================= Module isa-pnp kname isa-pnp objkey isa-pnp names: isa-pnp mode: NORMAL Module matching isa-pnp: /lib/modules/2.4.18/kernel/drivers/pnp/isa-pnp.o.gz ============================================= ============================================= Module snd-sbawe kname snd-sbawe objkey snd-sbawe names: snd-sbawe mode: NORMAL Module matching snd-sbawe: /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o ============================================= /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: init_module: No such device /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o failed /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: insmod snd-sbawe failed sh-2.05a# insmod /lib/modules/2.4.28/kernel/sound/isa/sb/snd-sbawe.o insmod: /lib/modules/2.4.28/kernel/sound/isa/sb/snd-sbawe.o: No such file or directory sh-2.05a# insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_seq_device_new /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_sb16dsp_pcm /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_sbmixer_read /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_verbose_printk /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_sb_csp_new /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_opl3_hwdep_new /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_sb16dsp_configure /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_kcalloc /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_sbmixer_write /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_sbmixer_new /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_ctl_add /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_device_new /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_mpu401_uart_interrupt /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_ctl_remove /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_sbdsp_create /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_card_register /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_ctl_new1 /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_sb16dsp_interrupt /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_card_free /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_card_new /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_opl3_create /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: unresolved symbol snd_mpu401_uart_new sh-2.05a# exit Script done on Sun Mar 23 11:28:23 2003 --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!

22 years, 6 months

[linux-audio-user] Vocal removal?

by Darren Landrum

Sorry if this question has been posed before, but I couldn't find anything in a search of the archives. I have a friend that needs to remove the vocals in one of her own songs (due to a conflict in getting the masters back that is too long of a story to go into right now). Are there any good Linux tools for this task? Thank you for all of your help. Regards, Darren Landrum

22 years, 7 months

[linux-audio-user] alsa rme hdsp driver, firmware rev 11

by Jaakko Prättälä

Hi all. Has anyone got a rme hdsp with firmware revision 11 working with alsa? If you do, could you send me your hdsp.c (maybe hammerfall_mem.c too) as an attachment? Or even better, a diff against current alsa cvs. I'd *so* like to get my multiface running. The red error led is nice, but a bit less than what I need from the card :-) If you have a non-working version, what error message do you get from the driver in /var/log/messages? I get: Mar 23 16:54:29 kiertotahti kernel: Hammerfall memory allocator: no Hammerfall cards found... Mar 23 16:54:29 kiertotahti kernel: RME Hammerfall-DSP: no cards found and on the command line: [root@kiertotahti jaakko]# /sbin/modprobe snd-hdsp /lib/modules/2.4.19scsi_lowlat_acpi/kernel/sound/pci/rme9652/snd-hdsp.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.19scsi_lowlat_acpi/kernel/sound/pci/rme9652/snd-hdsp.o: insmod /lib/modules/2.4.19scsi_lowlat_acpi/kernel/sound/pci/rme9652/snd-hdsp.o failed /lib/modules/2.4.19scsi_lowlat_acpi/kernel/sound/pci/rme9652/snd-hdsp.o: insmod snd-hdsp failed I'm just trying to track where the error is. I don't even know my firmware version number but I suppose it's the latest since I just bought the multiface a few days ago. -- Jaakko Prättälä Jaakko.Prattala(a)Helsinki.FI

22 years, 7 months

[linux-audio-user] Low latency patch for Mandrake 9.0 kernel

by Luke Yelavich

Hi folks I don't have the bandwidth, download allowance, or time to grab a Planet CCRMA kernel patched with low latency. I am wondering whether anybody knows where I could find patches that would successfully patch the Mandrake 9.0 default kernel source for low latency and pre-empt. Thanks in advance Luke.

22 years, 7 months

[linux-audio-user] Midi output

by Alexander Feder

Hi! I'm new to that list, i'm Alexander Feder, student in Vienna. I play synthesizer and [E-]violin and finally want to try to sequence and record what i'm playing. It seems though there is lots to do before i can do that. I've bought a M-Audio Audiophile 24/96 card which i've set up using Alsa. Audio works fine when using the oss-emulation, but trying to access the card directly (aplay -D hw:0,0, or using the alsa-xmms plugin or with ecasound) fails with "Sample format non available". Isn't that odd? I've thought alsa-oss-emulation would be just another layer on top of what i would access when using aplay & co. .. Recording works fine (also using oss), i've used ecasound for adding nice real time effects while playing my e-violin. i can control everything with envy24control though.... Another problem i have is sequencing, actually midi as a whole. Neither outputting with pmidi, playmidi or muse works. I'm quite sure i've put all cables correctly into the Audiophile and my Yamaha CS1x synth. Both cables (male-male) are 5 pin, the one that i've plugged into the [in] in my soundcard and to [out] on my synth has 3 pins used (4,2,5 - the three in the middle) and the other cable has all 5 pins used. I've checked every combination with my ohm-meter, so there is no short-circuit. All pins are mapped 1:1. 'pmidi -l' gives 64:0 Rawmidi 0 - M Audio Audiophile M Audio Audiophile 24/96 MPU-401 trying to output a midi file with pmidi (which i have successfully outputted using playmidi on a pc with an sb16 and oss, iirc) results in no audible result. :/ (pmidi -p 64:0 test.mid) muse outputs something more interesting whenever a note should be played: MidiAlsaDevice::putEvent(): midi write error, returns -19 expected 28: No such device Which i further find odd is that muse is not willing to start playing unless i've first stepped into the config->audio system to apply the already activated setting of No Audio. Before that the transport indicator will not move. Further when i activate "Use Alsa" muse exits with the "ALSA: Sample format not available" message. So does this mean i can't trust what /proc/asound/seq/clients and pmidi -l says? or does that mean that at the other end, where my synth should be, is no device attached? same problem in the other direction. muse does not receive any signals from my cs1x. I've recorded with this cs1x successfully on another pc with.. another os.. so i think the hardware works. I'm using Debian GNU/Linux Sid on an Athlon, alsa 0.9.1-2 (for base and libs). The things i described both happen on vanilla 2.4.20 with the alsa drivers coming with debian (also 0.9.1-2) and on a 2.4.20 WOLK-kernel (rc3) with the integrated alsa-drivers. (these behave slightly different, for example i can't set the DAC volume with envy24control with the wolk-kernel - the sliders don't move. this works fine with the vanilla kernel.) what could i be doing wrong? or could it be that the soundcard itself is broken? i have no other OS to falsify that.. :/ thank you very much for any help in advance bye xandi

22 years, 7 months

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-user