Hi,
ok. I tried to set things like you mentioned from FAQ:
alias snd-card-0 snd-ice1712
options snd-ice1712 index=0
alias snd-card-1 snd-usb-audio
options snd-usb-audio index=1
--> I don't know, what to write for the 2 midi controllers
(One is a behringer bcf2000 midi controller, the other is a usb midi keyboard
umx61)
So I just left these 2 lines in /etc/modprobe.d/alsa-base
restartet ... nothing changed!
After I set the Jack device from "Default" to "HW 2 - ICE1712" jack is starting
again ... evertything seems fine with jack.
so i tried:
mplayer -ao alsa /home/matze/Desktop/somemp3.mp3
got output:
MPlayer 1.0rc2-4.2.3 (C) 2000-2007 MPlayer Team
CPU: AMD Phenom(tm) 9650 Quad-Core Processor (Family: 16, Model: 2, Stepping: 3)
CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
Playing /home/matze/Desktop/Dune - Are You Ready To Fly.mp3.
Audio file file format detected.
==========================================================================
Forced audio codec: mad
Opening audio decoder: [libmad] libmad mpeg audio decoder
AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000->176400)
Selected audio codec: [mad] afm: libmad (libMAD MPEG layer 1-2-3)
==========================================================================
[AO_ALSA] Format s16le is not supported by hardware, trying default.
[AO_ALSA] Unable to set format: Invalid argument
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video
Then i tried
mplayer -ao alsa /usr/share/sounds/somesound.wav
and got output
MPlayer 1.0rc2-4.2.3 (C) 2000-2007 MPlayer Team
CPU: AMD Phenom(tm) 9650 Quad-Core Processor (Family: 16, Model: 2, Stepping: 3)
CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
Playing /usr/share/sounds/Tink.wav.
Audio file file format detected.
==========================================================================
Forced audio codec: mad
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 22050 Hz, 2 ch, s16le, 705.6 kbit/100.00% (ratio: 88200->88200)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
[AO_ALSA] Format s16le is not supported by hardware, trying default.
[AO_ALSA] Unable to set format: Invalid argument
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video
still no sound
Then i tried sound output with totem player
Totem started running, but playing the file did not start. Also no sound output
So, where do I have to look at?
some outputs?
>> cat /proc/asound/cards
0 [BCF2000 ]: USB-Audio - BCF2000
BEHRINGER BCF2000 at usb-0000:00:13.1-2, full speed
1 [U61 ]: USB-Audio - UMX 61
BEHRINGER UMX 61 at usb-0000:00:13.1-1, full speed
2 [M1010LT ]: ICE1712 - M Audio Delta 1010LT
M Audio Delta 1010LT at 0xe800, irq 20
>> ps afx |grep jackd
nothing running
>> sudo lsof | grep snd
mixer_app 4922 matze 19u CHR 116,64 6514
/dev/snd/controlC2
qjackctl 4957 matze 13u CHR 116,1 6210
/dev/snd/seq
so i exited jackcontrol (with jack stopped)
now
>> sudo lsof | grep snd
mixer_app 4922 matze 19u CHR 116,64 6514
/dev/snd/controlC2
to set the default HW ... but maybe this has no effect...
>> cat /etc/asound.conf
pcm.!default {
type hw
card 2
}
ctl.!default {
type hw
card 2
}
As you can see, today, I don't get the "device busy" error, but still no sound
output ...
what can I do? I think there're many people out there using normal alsa output,
aren't there?
regards,
mathias
[email protected] wrote:
> (http://www.64studio.com/faq_user)
>
> Yes, this is the correct solution. My system has almost the same setup,
> and I have to do the above to maintain a reliable system.
>
> Mathias, You could try booting with the USB midi disconnected, and only
> connect it after booting. If this works, the solution Ralf copied out of
> the 64 Studio user FAQ is the way to fix it.
>
> Cheers,
> Quentin
>
_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users
