Linux-audio-user December 2006

linux-audio-user@lists.linuxaudio.org

161 participants
166 discussions

[linux-audio-user] SE electronics USB2200a microphone, success report

by Atte André Jensen

Hi I just bought a SE electronics USB2200a microphone (a 2200a with build-in usb sound card) and was pleasantly surprised to find that it was instantly recognized and working out of the box with linux. I understand that USB sound cards are not the best to go real low in latency, but with heavy load (13 parts in zyn, +10 tracks in ardour w fx + specimen + seq24) I was able to go to 23ms which is the same as the onboard on my laptop. With lighter loads it works well with lower latencies. Thought someone might be interested in this successful report... -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

17 years, 4 months

Re: [linux-audio-user] lashd wows, fst and qsynth

by njcross＠sbcglobal.net

Date: Thu, 14 Dec 2006 23:59:51 +0000 From: Rui Nuno Capela <rncbc(a)rncbc.org> Subject: Re: [linux-audio-user] lashd wows, fst and qsynth To: A list for linux audio users <linux-audio-user(a)music.columbia.edu> Message-ID: <4581E577.7080805(a)rncbc.org> Content-Type: text/plain; charset=ISO-8859-1 rncbc aka Rui Nuno Capela wrote: > AFAICT qsynth is not lash enabled. Is there a real need for it? I can > only find the one for jack/alsa connections recall, for which I've been > using qjackctl patchbay since its very own inception ;) FWIW all other > qsynth state is preserved as its own, as usual. > > However, if there's any sufficient demand for it, I believe some lash > enabling patch to qsynth is not that really hard to put up. Someone > could just borrow the fluidsynth's one and bring it to me? Does qjackctl load the applications as well as the connections? If not, then qsynth lash enabled would be very useful to me.

17 years, 4 months

[linux-audio-user] Very new and unfinished

by Folderol

I've just started on a new melody (well last night actually). It has a long way to go, but I thought you might like to hear the outline. I'm not yet sure where to take it. It sort of conveys the idea of some sort of exotic caravan journey across the ancient middle east. A small band of friends maybe? It is at http:/www.musically.me.uk/music/Orient.ogg Comments welcome -- Will J G

17 years, 4 months

[linux-audio-user] Re: New member wants to build a reliable DAW

by Kjetil Svalastog Matheussen

"Jon H": >>> serve you well to follow that thread too: >>> >>> http://lists.agnula.org/pipermail/users/2006-December/011707.html >>> >>> Basically I build pretty much the same machine I would build for >>> serious "gaming", perhaps dropped back a few notches on the video card. >>> The motherboard and PSU being the true heart of the system, it's >>> certainly no place to skimp! Asus has long been my favorite brand of >>> motherboard... out of the last dozen or so machines I've built around >>> their boards I've only had one with problems and their 3 year warranty >>> is genuine. >>> >> >> I second that. Asus is a safe one. But even more important is the chipset >> in use, because not everyone works very well with linux. Personally, I >> have always had good experience with via or intel, but I have heard SiS >> is working fine too. Stay away from nvidia, at least the newest models. >> (the older the chipset, the less problems you will have) > > > I disagree. I've built on Asus boards for linux several times now including > the SiS chipsets, which worked just fine, and the latest nforce4 chipsets > which also performed under a modern kernel and distro just dandy "out of the > box". Nvidia is linux friend :D > Nvidia is not a linux friend because it doesn't give specifications, at least as far as I know. If the latest nforce chipsets suddenly have started to behave nice for linux, thats good though. >>> than for serious audio production. I currently run a 32bit debian based >>> linux on a 64bit AMD single core but Intel should serve you well also... >>> more of a matter of personal preference here as far as brand goes. >>> >>> I mentioned video cards... I really prefer nvidia under linux, due to >>> the quality of the proprietary drivers and ease of installation, and >> >> This is a bad advice. The proprietary drivers from nvidia cause xruns, and >> should be avoided. But older (ie. at least 2-3 year old) nvidia cards can >> be used with the open nv driver instead, which I will recommend, because I >> have had experience with numerous nvidia gfx cards, and have had very >> little problem. > > > Actually anything you do visually will require a video card. The more > capable the card and the drivers the less resources it will take away from > the remaining system that is busy processing your audio. With a good video No, you are wrong. This does not matter because the audio programs runs with something called "Realtime Priority". Which means that as far as the graphic card drivers itself doesn't cause xruns because its programmed the wrong way (which is the case for the nvidia driver [1]), the choise of graphic card does not cause more or less xruns. [1] I think there is only have observational data for this claim though, because the source is not available. But it is revealing that when I change to the VESA driver, all the xruns dissappear. (Yes, I have to use the nvidia driver, the nv driver doesn't work for mine) > card that handles the majority of graphical rendering I experience almost NO > xruns, that's at 5.8ms latency using an onboard (nforce4) chipset, and lower > than that with a dedicated soundcard like the M-Audio stuff. Relying on the > CPU and system ram to render FFT graphics and such will cause xruns, a good > video card will not. > Thats not correct. Read what I wrote above. > Further more gaming is pretty much on the forefront of graphics as far as > linux is concerned. Gamers under linux means big money to any game company > that chooses to support linux as well as hardware manufacturers like Nvidia > or ATI. I know you aren't talking about wanting to play games here but any > piece of hardware that is optimized for gaming WILL be optimized for audio > as well, I guarantee it. > Nope, as long as the audio software is somewhat properly programmed, your claim is plain wrong. > Nvidia's proprietary drivers work quite well. I > can't really comment on ATI's drivers because I've long been an Nvidia fan. If you can get the nv driver to work, you should use that one. Then you might get rid of those last xruns. Do also try the VESA driver. >> dual monitor (dvi) is something I couldn't live without in my studio. >>> Currently I run 2 x 21" Dell CRT for a combined desktop of 3200x1200 >>> which makes tending to several music apps at the same time much easier >>> than crowding everything together on a single screen. Any mid-range >>> gaming card should do this well. Plan on spending at least US$100 here >>> (monitors extra!) >>> >> >> Well, not everyone thinks so. Using a descent windows manager, where you >> can change virtual screen quickly, makes multiple monitors unnecessary. >> What is faster, moving your head or eyes (where you have to refocus) to >> look at a different screen. Or, pressing a button on your keyboard? In >> windows, with its horrible unconfigurable interface, I guess it can make >> sence, but in X, you don't need more than one monitor. > > > When I'm composing music I'd rather not have to touch the keyboard at all. Really? Well, in that case, having more monitors might make sence. How do you compose? > Most modern video cards support multiple monitors these days... why not make > use of it? Half the desktop space when you don't have to? Why? Throw a > dozen samples at Ardour (plus it's mixer), envy24control, qjackctl, seq24, > plus a handful of DSSI or VSTi plugins and you have a very busy desktop. > Why worry about flipping between virtual desktops when you can see all of it > at the same time? > I guess it differse between person to person, but personally, I find it much more convenient to press a key rather than to start looking at a different monitor. >> I run a pair of Western Digital IDE drives but if I could afford the >>> upgrade I really want it would be at least four (maybe with a few spares >>> for backup) 200 GB or larger SATA drives set up in a software RAID 0+1 >>> or maybe RAID5. Firewire or SCSI would be nice as well as would an >>> outboard rack if you are going with many more drives than that. >>> >> >> Do you really need RAID for audio work? How many tracks do you use? >> Are you sure you couldn't get a way with a single IDE drive? > > > The original thread asked a question about rack mounted arrays. RAID is a > natural for this discussion. If I'm recording several takes of several live > feeds I can easily burn up many gigs of storage in a single session. Also > the cost of harddrives is going down rapidly. Soft RAID now offers an easy > and relatively inexpensive way to not only increase storage performance but > redundancy at the same time. I wouldn't consult on a serious studio setup > without pushing for redundant storage regardless. Anything worth recording > is worth protecting, don't you think? > No, its a waste of time and money. The money part is obvious, the time part comes from building and configuring, but the most important reason is that it highers the risk of losing data in case one of your harddisks break down. Another harddisk also generates more heat -> making more noise. >> I run a Delta44 which works great under linux but do most of my actual >>> mixing and line-in in a seperate mixer. A Delta1010 should be >>> fantastic! >>> >> >> Good advice. The ice1712 driver works really well on linux. >> >> >> I also want to add another important thing to concider, which is noise. >> It can be better to degrade the performance a bit to also reduce the >> noise. Power hungry processors cause more heat inside the case, which >> cause the fans to go faster. Same with lots of harddisks, don't do >> that, only use one. Same with gfx card, don't buy a fancy fast one that >> either makes a lot of heat or have a large fan. You don't need a fast gfx >> card for audio use. You should also use most of your money on the power >> supply. Not because of stability problems, but because of noise problems. >> The power supply is usually the noisiest part in a computer, and buying >> an expensive silent one is well worth the money. It doesn't matter if it >> can support 500W, 300W or even 200W is usually enough, but it must be >> silent. > > > I run an Enermax 500w "Liberty" in my personal studio machine. It is so > quiet that for a long time I would catch myself holding my hand by the back > of the case, on occasion, to make sure it was actually moving air at all! > It uses a 120mm fan at relatively low RPM to do the cooling. An excellent > unit. Other companies make similar hardware as well. > > As for graphics card? It is exactly as Kjetil has said, without meaning to, > I'm sure... it's *either* "a lot of heat OR a large fan". Which do you > prefer? Modern cards, at least Nvidia's, are almost dead silent in relation > to ambient noise levels in a recording enviroment. Especially if you plan > on running anything that requires OpenGL accelloration or VSTi > compatibility, as many of them are quite graphically intensive. If you run > dual monitors as I have suggested then *definately* pass on anything that > doesn't have dedicated active cooling! Anything that relies on passive > cooling (without getting into water cooling and other exotics) is just > asking for trouble in this sort of enviroment. > But even if you have a fan on your graphics card, it will still generate the same amount of heat, which will make the case hotter, and other fans to go faster. Better _not_ buy a gamer card for audio use, that is my advice. (wish I had followed that advice myself though. :-) ) Which means that gfx cards that only have passive cooling, probably are the ones to generate the least heat, and are therefore probably the best ones if you need a silent computer.

17 years, 4 months

[linux-audio-user] jackd forcing me to choose input or output exclusively

by Hans Fugal

On OS X on the MacBook, which has two input sources (mic and line in) and one output source. $ jackd -d coreaudio jackd 0.102.20 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with POSIX SHM support. loading driver .. Default input and output devices are not the same !! Cannot open default device Cannot open the coreaudio driver cannot load driver module coreaudio no message buffer overruns 'jackd -d coreaudio -C' works fine, as does 'jackd -d coreaudio -P'. Fine as in it does what you expect, which is give you either capture or playback, but not both. The -l output is (snipped): Device name = 'Built-in Microphone', internal_name = 'AppleHDAEngineInput:1' (to be used as -d parameter) Device name = 'Built-in Input', internal_name = 'AppleHDAEngineInput:2' (to be used as -d parameter) Device name = 'Built-in Output', internal_name = 'AppleHDAEngineOutput:0' (to be used as -d parameter) I can select which capture device to use using the -d parameter. So if I do "jackd -d coreaudio -D -d 'AppleHDAEngineInput:1'" that doesn't crash, but gives me only capture and no playback. I've tried a few other variations on the theme, including things like "jackd -d coreaudio -C -d 'AppleHDAEngineInput:1' -P -d 'AppleHDAEngineOutput:0'" but to no avail. Am I missing something obvious? Has anyone else had this trouble? Thanks! -- Hans Fugal ; http://hans.fugal.net There's nothing remarkable about it. All one has to do is hit the right keys at the right time and the instrument plays itself. -- Johann Sebastian Bach

17 years, 4 months

[linux-audio-user] Usable linux accompaniment software?

by iain duncan

There seem to be a few partially developed options and I'm not sure where to start. I would like to hear subjective opinions on whether any of the linux options are usable for learning/practicing jazz standards, preferably from people with some experience playing jazz who can evaluate whether the auto-accompaniment is good enough to practice with. I intend to start working on learning tunes in a big way this year and would ideally like to come up with an integrated toolset that I can use to make lead sheets the way I like them, and from the same data files generate halfway usable auto-accompaniment tracks. System could preferably run on linux and OSX under fink. Opinions? Thanks Iain

17 years, 4 months

[linux-audio-user] jack_capture crashes jackd

by Ken Restivo

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is not a big deal, because I decided to use ecasound instead (which works! yay!) but here's the details just incase anyone is interested: $ jack_capture cannot read result for request type 6 from server (No such file or directory) jackd watchdog: timeout - killing jackd Killed JACK error: zombified - calling shutdown handler jack_mgr_shutdown_cb: JACK server shut us down; telling server to quit Cleaning up JACK server shutdown detected, reopening in OSS mode JACK error: cannot send request type 7 to server JACK error: cannot read result for request type 7 from server (Broken pipe) jack_mgr_destroy: could not deactivate jack client JACK error: cannot send request type 7 to server JACK error: cannot read result for request type 7 from server (Broken pipe) Finished Huh? All other jack apps I have: rosegarden, fluidsynth, qjackctl, ardour, hydrogen, swami, etc, all work perfectly well. Ecasound works with no problems. But jack_capture tends to crash the whole server. Sad. This is with: $ uname -a Linux mac 2.6.18-1-preempt #1 SMP PREEMPT Fri Dec 15 17:25:10 PST 2006 i686 GNU/Linux $ jackd --version jackd version 0.101.1 tmpdir /dev/shm protocol 15 jack_capture-0.9.2 libsndfile1 1.0.16-1 $ jack_lsp alsa_pcm:capture_1 alsa_pcm:capture_2 alsa_pcm:playback_1 alsa_pcm:playback_2 alsa_pcm:playback_3 alsa_pcm:playback_4 alsa_pcm:playback_5 alsa_pcm:playback_6 alsa_pcm:playback_7 alsa_pcm:playback_8 mpg123_0:out_1 mpg123_0:out_2 processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Genuine Intel(R) CPU 1300 @ 1.66GHz stepping : 8 cpu MHz : 1666.785 cache size : 2048 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor vmx est tm2 xtpr bogomips : 3336.19 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Genuine Intel(R) CPU 1300 @ 1.66GHz stepping : 8 cpu MHz : 1666.785 cache size : 2048 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor vmx est tm2 xtpr bogomips : 3333.30 - -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFFidGQe8HF+6xeOIcRAqnMAKDjSjUO/k/yQApUN1baMDxt9CATQwCgiOTE zNM5kVB1eclXo64RId3IMfY= =BVEf -----END PGP SIGNATURE-----

17 years, 4 months

[linux-audio-user] usb2200a

by Atte André Jensen

Hi I just recieved the monthly magazine from my musicstore and found an interesting microphone in sE Electronics usb2200a. It seems to be a studio condenser mic with build-in usb 2.0 interface. Anyone... 1) ...tried this with linux, and has any successes or failures to report? 2) ...has heard and can comment on the sound of the non-usb version sE2200A? If the store actually has it in stock, I think I might bring my laptop friday and see if I can get it working... -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

17 years, 4 months

Re: [linux-audio-user] SMPTE timecode reader

by plutek

On 12/19/2006 04:11:47 AM, Maarten de Boer wrote: > > hi, > > > generator, i am now interested also in software capable of parsing a > > > SMPTE timecode stream (audio, NOT MTC), and displaying the > > corresponding numerical timecode, as the audio track is running. > > you might want to check this SMPTE decoder code i wrote years ago: > > ftp://www.iua.upf.es/pub/mdeboer/projects/SMPTE/ thanks maarten! yes, your code seems to parse a wav file correctly from the command-line. it cannot currently take realtime audio input though, right? .pltk.

17 years, 4 months

[linux-audio-user] Re: Pd produces many Xruns

by Kjetil S. Matheussen

"chris beagles": > > Today i tryed playing around with pd for the first time, and enabled > the audio system to use jack, which works fine except for: > > If I move the mouse and it crosses the boundary between two windows, I > then get reports of Xruns from within pd in the main window and the > sound crackles accordingly. > Qjackctl does not report any of these xruns. > > This is getting a little annoying and may leave me having to leave pd > for now as i need to utilise my mouse whilst using it. > > I am running Ubuntu Edgy with a 2.6.17-rt kernel and jack as realtime. > If I do not enable the audio system within pd then this problem does not occur. > > Any help much appreciated. > Did you start pd with the "-rt" switch? In case not, that will help. (PS. Always add the terminal switches you start a program with when asking for help)

17 years, 4 months

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

Jump to page:

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 December 2006