On 7/15/12, Robin Paulson <robin.paulson(a)gmail.com> wrote: alsamixer and envy24control will remain entirely relevant. to the original poster: you have multiple audio devices. if you're using aplay to test things with, you need to be sure that you specify which device you want it to use.

On Mon, Jul 16, 2012 at 2:28 PM, Ivan K <ivan_521521(a)yahoo.com> wrote: the relevant output is really what this command says: cat /proc/asound/cards the complication is that some devices have multiple PCM devices on a single card. then it gets a bit more complex. but in the common case, the "one to pick" is hw:CARDNAME (as described here: http://jackaudio.org/device_naming

On Mon, Jul 16, 2012 at 5:28 PM, Ivan K <ivan_521521(a)yahoo.com> wrote: have you tried aplay -D hw:M2496 /path/to/an/actual/wav/file/on/your/system.wav (changing the file name appropriately, of course)? the problem is that you may *also* need to play with the h/w mixer settings. envy24control is a better program for that with the 2496 than any of the standard generic mixer tools (and it has meters too).

Might the file /etc/asound.conf an issue? With my previous OS (CentOS 5.6) this file looked like:   #Generated by system-config-soundcard, do not edit by hand   #SWCONF   #DEV 0   defaults.pcm.card 0   defaults.pcm.device 0   defaults.ctl.card 0 though in Fedora 17, this file is blank except for the comments:   #   # Place your global alsa-lib configuration here...   # Also, in the past, with CentOS and other RedHat distributions, I use to use the tool system-config-soundcard.  It does not appear that this tool is still available for Fedora17. Thanks;

On 07/16/2012 09:09 AM, Charles Henry wrote: Jack will automatically request the card from Pulse Audio and release it when it is done, you don't need to do anything special. -- Fernando

On 07/16/2012 11:30 AM, Ivan K wrote: "Envy 24 Control" will directly control your soundcard. Make sure you go to the "Analog Volume" tab (I think that is the name) and get the output volume up in each output channel you want to use. You do not normally need to touch or use the internal chipset mixer. If you want to use a Jack based application you would need to point jack to the proper soundcard. What I usually do is to look at the output (in a terminal) of "cat /proc/asound/cards", this will show you a list of the cards your system recognized. In my laptop for example I see: ---- $ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xf2420000 irq 44 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xcdefc000 irq 16 29 [ThinkPadEC ]: ThinkPad EC - ThinkPad Console Audio Control ThinkPad Console Audio Control at EC reg 0x30, fw 6MHT38WW-1.13 ---- Just to test if things start you could start jack from the command line like this: ---- jackd -R -d alsa -d hw:Intel ---- (just replace "Intel" with the name that is between '[]' in the card you want to use) Jack should start cleanly and just sit there waiting for clients to connect. If that hurdle is behind you you can start qjackctl (a gui front end) instead, change the "Interface" name in the Setup panel to hw:Intel (or whatever is the name of your card), select "Realtime" and start Jack. To test you could, for example, install Hydrogen, start it and use one of its demo patterns to test sound. You might need to go to the preferences and make sure it is using Jack as the backend. Also, make sure that its outputs are connected to the Jack output ports in qjackctl's "Connect" pane... Press play and you should get sound out of your card (if the analog volumes are up). If you want to test with aplay and output directly to ALSA then you also need to tell aplay which card to use. A basic command in my case would be "aplay --device=hw:Intel soundfile". If your soundfile is not exactly of the right type aplay may complain, and you can usually make it happy again by saying "aplay --device=plughw:Intel soundfile" instead, which will automatically convert formats... If you want to, say, play sounds from your internet browser (and from most system programs) you will deal with Pulse Audio. Again, like before, you will need to tell it which card to use. Depending on which window manager you use you might have a small speaker icon somewhere which you can use to left click and set the overall volume. Usually if you right click you can start the "Sound Preferences" panel which will let you set which card is used for input and output. On Fedora 17 you can go to the System Preferences dialog and select "Sound" (if I remember correctly) and start the same Pulse Audio Manager. Best of lucks! -- Fernando

On 07/18/2012 09:09 AM, Ivan K wrote: Different profiles that are recognized by Pulse Audio (for the same card). -- Fernando

On 16 July 2012 at 10:15, Fernando Lopez-Lezcano <nando(a)ccrma.Stanford.EDU> wrote: Not doing anything special is my experience too. But, I use M-Audio cards for pro and the built-in sound card for day-to-day audio. -- Kevin