-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
peter wrote: | On Tuesday 22 January 2008 10:59 pm, Gustin Johnson wrote: |> The short answer is no. I use jack only for "serious" audio work. |> For day to day browsing and media playing I don't bother with jack. |> Jack is great for the projects that require heavy lifting but it is |> overkill for youtube. | | Yeah, I understand. However, it seems kinda dumb that I have to turn | off jack and switch to some other sound server, be it aRts or ALSA or It is what it is. Alsa is doing the rendering in both cases. Jack uses alsa to actually produce the sound you hear. Trying to run jack all the time is an unneccesary complication. To make things easier, I use qjackctl, and I save my jack config in this program. All I do is run the program, and click the start button. | whatever, to get sound in my browser. The funny thing is that lmms | actually sounds better using KDE's default sound server than it does | in jack (so I guess I don't have jack configured right yet--I just | followed the settings in the article). Jack does not by default "do" anything to the sound you hear. It does allow you to pass the output from any jack enabled program through another program, which may be a filter or an effect. In either case, alsa is doing the actual rendering of the audio you hear. Unless arts is doing some EQ-ing of the sound, there should be no difference in the sound you hear. |> Arts has also been depreciated, and should not be used anymore. At |> any rate, you don't need to enable arts to get audio to work in a |> browser. | | I guess what I'm trying to achieve is to use jack (once it's | configured correctly) for the "serious" audio work and still have | sound in my browser or mplayer without having to change my settings. I don't really understand the why of it yet. For me jack is an essential tool when I am working with audio, but it is not necessary for day to day tasks. Most apps like mplayer and your browser will work with the default which should be vanilla alsa. Essentially what I am trying to say is that you should use the right tool for the right job. A lot of the day to day apps still need to be made jack aware before you can accomplish what want. In most cases you will need to specifically tell the app to use jack since it will autodetect the presence of alsa anyway (with mplayer you specify the audio out mechanism with -ao jack, other apps may vary). There are some good tutorials out there, but there are also a lot of out of date ones. Some good places to start would be: http://64studio.com -- This is a media production orientated distro, but they do have some decent how-tos and documentation. If you get more into this sort of thing, I would recommend finding a distro that is specifically targeted at this task. Building your own low latency (rt) kernel is not fun, even though I do build kernels for fun. http://jackit.sourceforge.net/docs/ -- should be obvious what this is http://ardour.org/ -- This is an app that is aimed more at the professional or serious hobbyist (I would consider myself to be in the latter category). Some good documentation here about linux audio. Hth, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHl7mWwRXgH3rKGfMRAlqWAKCK3Fhc5z8ANt+B8OENlSJ2qjOF1QCeIwVs YkAxE/QANBFP0kmO6ZSjV0c= =ym7U -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
