Hi all,

I'm sorry for having created this flood of mails. (I was in a kind of
gold-rush with 64studio, as all these things look so promising) I will try
to re-identify my problem i one single Mail:

>> jackd is definetly NOT running. As I wrote in my mail before, I am not
>> able to run jack anymore...

>I'm confused.
>The last mail I read was saying: "Sound works fine with JACK. But I
>thought, when JACK is not running, ALSA sound output should work, too"
>Possibly, you answered only Ralf instead of the list?

Yeah, there was a second mail. Maybe I answered only to Ralf. Sorry for
that. Now here again:

After the fresh install of 64studio JACK was running fine. When i stopped
jack, ALSA was not running. Then, after playing a little bit around with
things, they told me in other forums (re-intalling alsa, esound, ...)
nothing is working anymore. No alsa and no Jack.

>> Your MAudio isn't a firewire (FFADO) one?
> No, the MAudio 1010LT is a PCI-Soundcard.

That's right. Sorry, it seems like I did not mention the really
interesting things...

> "sudo lsof |grep snd" might help you to discover what is locking your
> sound device.

This i a great tip. Thank you. I will try this out later.

In the meantime, I discovered, why ALSA is not working anymore, also with
jack. It's because it has lost its default hardware. Jack tells me, that
it wants to start alsa on a USB-Midi soundcard. I don't know how to set
the ALSA default hardware in the right way? I heard something about
"asoundconf set-default" but I don't know how to name the right card. Then
I read something about the "etc/asound-conf" which sets "hw 2" now. But
nothing seems to help at the moment?

> Weird, because jack runs on top of ALSA, meaning that if ALSA is broken,
> jack will not work (this is a generalization, unless you specifically do
> something different).  Is the Delta 1010 one of two sound devices in
> your computer?  Perhaps you just need to set the default sound device?

Thats right. It's the only one with sound output, but there're some midi
devices in front of it (hw 0 is a usb midi controller and hw 1 is a usb
midi keyboard.)

> Can you right click on the volume icon on the status bar, and then
> select Preferences?  What sound device is selected?

I will try that out later. But I'm pretty sure i checked this several
times. Can you explain me about all the config file for alsa?
I found something about default device in "/etc/asound.conf" in
"~/.asound.conf" and also in "~/.asound.conf.???". Then there's also a
sound-device-default-setting in the System-Sound-Settings of gnome. May it
be that i missed something? Which of them do I need?

> The system defaults can usually be found in System -> Preferences -> Sound

Yeah. There I selected the ALSA output as default. But the TEST buttin is
not working, too (Device already in use)

It would be a good idea to test first.

> I like to use mplayer from the command line, as we can specify the
> output easily:
> eg.
> mplayer -ao alsa some-random.wav
> "mplayer -ao help" for more options.

Also a very good tip. Thank you for your help. Really amazing how good
this community seems to work!

> That's bad. You don't get an output if you run
> sudo pidof jackd
> ?

I'll try that out.

> What messages do you get if you run jackd?

At the moment, the problem is that alsa trys to use "hw 0", but should use
"hw 2"

Thanks for your help all together. I will do some investigations later on.
It would be fine, if somebody could explain me, where to set the default
output device for alsa, and which config file I need. In the meantime, I
will use your tips, to see who is locking my sound device.

Regards,
Mathias
_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users

Reply via email to