Hi Jonathan,

On 1/17/07, Jonathan Murphy <typetosmurky@bigpond.com> wrote:
> > but I think the one you posted gives an alias to the hw cards, but
> > the default is still dmix because you don't have a definition for
> > routing default (I think...).
>
> But that was my point. It's unecessary to enable something that's
> enabled by default, and I think that it might be what's causing the
> problem.

For my computer, dmix routes to whatever device happens to be assigned
hw0:0 first. Sometimes that's the USB device and sometimes that the
onboard soundcard.  If I don't explicitly assign it to the hardware
number of the USB device, I can't get predictable results.

I just tried removing my asoundrc and restarting audacious and other
programs, using whatever is default, and it came up with my laptop's
builtin.

> > If there's only one soundcard on the computer, then you probably can
> > just set it once in an /etc/asoundrc file and forget it.
>
> You can definitely do that, and in fact if you define your usb device
> like so:
>
>         pcm.usb-audio {
>            type hw
>            card 1
>         }
>
>         ctl.usb-audio {
>            type hw
>            card 1
>         }
>
> as your second card, then the problem that you describe (assuming that
> your usb device is standards compliant, and that you don't have to
> load any firmware to initialise it) should disappear. This is what the
> file is designed to do, and in my experience it works. The only gotcha
> is where you have more than one device using the same module, in which
> case you need to name them rather than just number them.

This is only creates aliases, and doesn't tell assign card hw:1 to
usb-audio, just allows calling usb-audio to get hw 1.  Since whatever
hw:x changes at startup unpredictably for me, I don't see how this
will fix anything for me.


> I have the simplest possible /etc/asound.conf (my other card is
> firewire, using freebob not alsa), and I cannot replicate the problem
> that you and Jean describe. I am almost certain that dmix
> configuration is actually unecessary, and is probably causing the
> problem. I strongly recommend that both yourself and Jean try the
> configuration that I've described. If I'm wrong, I'm prepared to eat
> humble pie. Done it many times before. NB. The AC'97 chipset needs to
> have the alsa-driver source code stay on file in the same spot from
> where it was compiled. I have no idea why this is the case, it's a bug
> that I've learnt to live with. If you see boot warnings re AC'97,
> that's probably the problem, and is likely the reason for the modem
> etc screwing with your usb device.

I can only comment on what I'm experiencing here and the results are
consistent and predictable according to what I mentioned in my
previous email.  I'm satisfied with the solution I'm using at the
moment and will go with this for now.  Using the defaults does not do
it for me.

What settings are you using for your testing with Csound?  (-b, -B, sr, -o)

steven

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net