Linux-audio-user

linux-audio-user@lists.linuxaudio.org

2 participants
20632 discussions

by Patrick Shirkey

For those of you who don't follow the jack list there was a recent (semi) discovery htat greatly improves performance for journalled filesystems. The main problem is that jack writes data to a /tmp file. It has been found that mounting /tmp as tmpfs (in RAM) solves the problems that many people have experienced with lockups while using JACK. Just put this in your /etc/fstab none /tmp tmpfs defaults 0 0 I have added this info to the low latency howto also. -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide ======================================== Being on stage with the band in front of crowds shouting, "Get off! No! We want normal music!", I think that was more like acting than anything I've ever done. Goldie, 8 Nov, 2002 The Scotsman

22 years, 1 month

[linux-audio-user] (semi)professional "field" recording work, what to use?

by Wilbert Berendsen

Hi, this is my first posting to this list; I'm a professional musician (organist) and avid Linux user from the Netherlands. I want to make good quality recordings with lightweight equipment and to further process the recordings on my Linux desktop PC. Currently I own a DCC recorder, but there are no DCC tapes available anymore. I have some tapes, but they are starting to show problems. So I'm in the market for some new equipment. I researched quite a lot and I think there are the following possiblities: 1. Minidisc recording. consumer minidisc recorders are very compact which is good. But they almost never have a digital out. Some have USB, but will not function as an USB-Audio device under Linux (AFAIK, all use the proprietairy NetMD protocol, which is partially reverse engineered, see: http://www.marcus-brinkmann.de/freemd.en.html). so to use most consumer market MD recorders it looks like I have to have a good audio interface to record the sound from MD to my PC (and still have it D->A and A->D converted in the process.) A professional MD recorder which looks very good (the HHB PORTADISC MDP500, see: http://www.hhb.co.uk/000/int.htm) has an USB interface that if I understand correctly just manifests itself as an usb audio device under Windows, and should thus also work with ALSA (?) so with that recorder I could once record the sound and futher process it fully digitally. The price is around EUR 1600,= which is quite a lot. My main concern would be the availability of MD's. 2. Harddisk/flashcard/cd-rw recorders. It seems these are very expensive now. 3. A laptop with a good (external?) audio interface (M-audio USB?) Just Linux on it and arecord -f cd full_concert.wav :-) My question is: What equipment do other people use? Would the HHB MDP500 be a good choice? Will MD stay for another decade? I think it is important that open standards are used (I feel more confident with usb audio than e.g. NetMD) thanks in advance for sharing your thoughts :) regards, Wilbert Berendsen -- Wilbert Berendsen (http://www.xs4all.nl/~wbsoft/) "You must be the change you wish to see in the world." -- Mahatma Gandi

22 years, 1 month

[linux-audio-user] Re: [Jackit-devel] Ahh

by Steve Harris

On Thu, May 15, 2003 at 09:14:36 +0200, Robert Jonsson wrote: > Hi Nick, > > > I can't imagine what else would cause problems with LADSPA plguins in > > general on my system. It has to be Yet Another Operator Error somewhere. > > If these plugins were this bad everyone would be complaining, > > I'm sorry I missed the beginning of this thread, are there any specific > plugins that are acting up? > > I think Steve will agree with me if I claim that some of the plugs _are_ > buggy. But with so few bugreports it's difficult to fix. (unless there's some > LADSPA/swh list I've missed?) Hey, that's the truth ;) I have got some valuable bug reports from Nick, but I've yet to fix the problems, thier deep and tedious to fix sadly. I have been doing a fair bit of plugin hacking recently, I'l make a new relaese when I've fixed the problem Nick found (flanger IIRC). Theres done seem to be some SSE2/gcc3 wierdness going on too, I saw a mention of some related sounding problems in an article somewhere, but I forgot what the problem they'd found was. I have been considering a mailing list so I can get consensus on bug reports, if there are enough interested people I'l set one up. Another idea (suggested by Dave Phillips) is setitng up a web page where people can make comments agianst the docs or something, but that involves me writing the web stuff, Its a great idea but frankly I'd rather put my efforts into writing plugins. I will get round to it if there aren't enough people for a list though. - Steve

22 years, 1 month

[linux-audio-user] Re: tkeca recording more than four channels?

by Daniel James

> I don't know how the multichannel cards works. I think that using > OSS emulation you could make something like that: > stereo channel 1 ---> input device: /dev/dsp > stereo channel 2 ---> input device: /dev/dsp1 > stereo channel 3 ---> input device: /dev/dsp2 > stereo channel 4 ---> input device: /dev/dsp3 With Audacity (which also uses OSS emulation) you just choose /dev/dsp and the number of recording channels you want, up to 16. Unfortunately Audacity 1.1.3 doesn't seem to scale well beyond four input channels on our machine. Does tkeca have native ALSA support, or does it use OSS emulation only? Thanks Daniel

22 years, 1 month

[linux-audio-user] Jack Audio Connection Kit version 0.71.2

by Taybin

Updated README with tip for better performance. Removed fltk example client from package. This should fix any problems with building the fltk client. Taybin Rutkin

22 years, 1 month

[linux-audio-user] noteedit-2.1.2(ritardando, pedal marks)

by Joerg Anders

Version 2.1.2 of the cost free musical score editor NoteEdit is available: http://rnvs.informatik.tu-chemnitz.de/~jan/noteedit/noteedit.html New features: - ritardando - accelerando o to create a audible ritardando (accelerando) simply place the ritardando (accelerando) between two different tempo signatures. NoteEdit assumes the ritardando (accelerando) begins at left tempo signature and ends at right tempo signature - piano pedal marks o TiMidity++ users! NoteEdit uses the MIDI PEDAL COMMANDS to play the pedal on/off signs. Unfortunately, TiMidity++ treats these commands wrong. Therefore, if you are a TiMidity++ user, it is recommended to avoid the MIDI PEDAL COMMANDS during replay (see "configuration section"). Unfortunately, the pedal on/off signs have no effect in this case :-( -- J.Anders, Chemnitz, GERMANY (ja(a)informatik.tu-chemnitz.de)

22 years, 1 month

RE: [linux-audio-user] [OT] ? DVD questions: summary

by Matthew Sargent

> I downloaded and built the very latest Xine, and I must > say, it rocks. > Alas, it's crashing my X server or my window manager (or both). After > using Xine my X session segfaults if I switch workspaces in Blackbox. > Does anyone else know about that problem ? How are you closing it? May sound an odd question but IIRC there's something in the (lengthy and pretty good) documentation for the version I installed some while back that suggests you'll run into memory problems unless it's closed with Ctrl+Q. Sorry if this is a little vague, but it may provide a pointer.

22 years, 1 month

Re: [linux-audio-user] Getting USB Audio Quattro to work

by Denis de Leeuw Duarte

>On Wed, May 14, 2003 at 02:36:21PM +0000, Denis de Leeuw Duarte wrote: > > Hello! > > > > Somebody told me a few of you have managed to get M-Audio's USB Audio > > Quattro to work. > >that would be me :-) you're teh guy from #gentoo right? welcome! Yes :-) Thanks! _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail

22 years, 1 month

[linux-audio-user] Getting USB Audio Quattro to work

by Denis de Leeuw Duarte

Hello! Somebody told me a few of you have managed to get M-Audio's USB Audio Quattro to work. I'd like to join your ranks, but I'm having a small problem. By the looks of things the USB settings are all correct and the ALSA (0.9.3) kernel module loads like it should, but the alsasound script gives me a peculiar message: Starting sound driver: snd-usb-audio done No state is present for card tm It then automatically writes a new asound.state file containing only this: state.tm{ } I don't know if this is good or bad or unimportant, but nonetheless, I don't hear anything when playing back sounds. I found the .asoundrc file for the Quattro by Patrick Shirkey somewhere and I saved it to my own .asoundrc. Here is what some of the aplay commands output: This actually _looks_ good, but I can't hear sound: denis@denlap denis $ aplay /usr/kde/3.1/share/sounds/pop.wav Playing WAVE '/usr/kde/3.1/share/sounds/pop.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono Here I tried to use the device names from the asoundrc file, but then I get an error: denis@denlap denis $ aplay -D quattro1 /usr/kde/3.1/share/sounds/pop.wav Playing WAVE '/usr/kde/3.1/share/sounds/pop.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono aplay: set_params:810: Channels count non available So, my question is, what am I doing wrong? Did I take all the necessary steps? Is there a way do get more diagnostics? I hope you can answer my questions, because this thing is pretty expensive for a paperweight ;-) Regards, Denis p.s. if you need more info, let me know. Just to be on the safe side, here's a few of my files. Note that the device is named 'tm' which is (i think) because of the (tm) in the descriptor. I really don't know how all of this wors though, so educate me please. My /proc/asound/devices: 0: [0- 0]: ctl 16: [0- 0]: digital audio playback 24: [0- 0]: digital audio capture 17: [0- 1]: digital audio playback 25: [0- 1]: digital audio capture 8: [0- 0]: raw midi 1: : sequencer 33: : timer nMy /proc/asound/cards: [tm ]: USB-Audio - USB AudioSport Quattro (tm) M Audio USB AudioSport Quattro (tm) at usb-00:07.2-2 _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

22 years, 1 month

[linux-audio-user] Fwd: Re: Sweep ALSA testing

by Daniel James

Hello Sweep users, Conrad is looking for help with testing the new ALSA 0.9x support in version 0.82. You have to enable ALSA support at ./configure time. Daniel ---------- Forwarded Message ---------- Subject: Re: Sweep ALSA testing Date: Tue, 13 May 2003 21:01:55 +1000 From: Conrad Parker <conrad(a)vergenet.net> To: Daniel James <daniel(a)mondodesigno.com> Hmm, Hi Daniel, you know what? I wish I knew what the right way to get alsa device names was :) until then I'm stuck in this crazy cartoon! till next time, Conrad. On Tue, May 13, 2003 at 11:45:48AM +0100, Daniel James wrote: > Hello, > > I've just built Sweep 0.82 from source on Mandrake 9.0 with the > ALSA option, and there's nothing in the Main device: box under > audio device configuration. > > How does Sweep get ALSA device names? I can see my card with > > cat /proc/asound/devices > > and it works with other programs, such as ecasound. > > I tried putting > > hw:0,0 > > in the box, but it didn't work. > > Thanks for a great program, all the same! > > Cheers > > Daniel -------------------------------------------------------

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