From: Ed W. <li...@wi...> - 2005-01-15 00:15:38
|
>...and i was so happy with my newly bought JBL speakers! :-) > > Aha, well that of course depends which JBL's you bought.... They do some excellent quality compression drivers in the pro end of the market. Consider that a normal "hifi" tweeter struggles to handle more than 10W of power, and a cheapo tweeter will probably burn out with perhaps 1W. JBL do a bunch of pro compression stuff which can hit 100W, and compression drivers go higher than that... One of the guys in the local hifi circle here has a pair of things that they fit in stadiums... JBL pro audio stuff is a very high benchmark that much hifi kit would struggle to beat.... The biggest pain fitting my big woofers was the size of the magnets... I needed to use a socket wrench to fit them into the boxes, and the magnets are so string you keep getting the darn socket stuck to the back of the driver - you then can't physically pull the socket away from the magnet! You have to slide the socket wrench to the side of the magnet and lever it off.... (Oh and your watch stops when you put it in such a strong magnetic field...) Great fun though - these 15" drivers have about 1" of travel when going flat out! >that sounds like a pretty cool setup indeed! i will visit a friend in >London sometime (maybe later this year), in that case i'll drop you a >note... > > Definitely. Drop me a note. >yes, jack support will surely be accepted. i haven't seen your patch >though and i personally prefer to test everything before commiting to >cvs - so that mean i would have to install jack... > > No problem. Personally I am a gentoo user so installing jack was just a case of typing "emerge jack-audio-connection-kit".... I think that the process for others though is just to whack on the binaries or compile up a recent-ish source (exact version is not very important). It's then an audio server, so kill off any other audio servers (like artsd) or anything else which locks the audio device, and fire it up with "jackd". It also takes a bunch of command line params, the most useful ones are those for frequency and output device (if you have more than one soundcard or need something other than ). My own command line for an RME9632 card is: jackd --realtime -d alsa -d rme9632 -r 44100 -p 1024 OK, now the only other thing to bear in mind is that you have to run xine or any other jack client as the SAME USER AS THE JACKD PROCESS!!! I use the capabilities patch for recent 2.6 kernels in order to run with realtime priority when not as root. OK, the only other background info on jack is that now it's running you can load "plugins" to jack and treat it like a point and click sound mapping server. So you can send output from xine through to the echo filter, then on to the reverb filter, then to a volume control filter, then to a delay line, and so on, etc, etc, and finally send the output of that to the physical output device. By default it will just send stuff to the physical output so you don't need to do anything to test this stuff, just tell xine to use jack. In my case I use brutefir as a realtime fir convolution engine to apply some filters to the audio and the output of brutefir goes to the physical device. I am happy to write up how to use brutefir, but it's a complicated piece of software so write to me offlist if you are interested. Eventually there will be much more info on DRC and brutefir here: http://drc.wildgooses.com Thanks to all those who made xine what it is today! All the best Ed W |