Mathias Krause wrote:
> At the moment, the problem is that alsa trys to use "hw 0", but should use
> "hw 2"
"I have multiple audio interfaces. How can I make sure they are given
consistent device numbers by ALSA?
As root, add lines like these to the end of your
/etc/modprobe.d/alsa-base file:
PS:
> Mathias Krause wrote:
>
>> At the moment, the problem is that alsa trys to use "hw 0", but should use
>> "hw 2"
>>
>
> "I have multiple audio interfaces. How can I make sure they are given
> consistent device numbers by ALSA?
>
> As root, add lines like these to the end of your
> /e
Hiho,
I'm not sure whether it is already there...
but, it would be great to see SuperCollider as a package(s) for 64studio.
We already build Ubuntu-packages, and these seem to be getting quite popular
by users, and don't seem to give much cause for trouble.
It would be great if we could get thes
(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 Ral
> it would be great to see SuperCollider as a package(s) for 64studio.
>
> We already build Ubuntu-packages, and these seem to be getting quite
> popular
> by users, and don't seem to give much cause for trouble.
> It would be great if we could get these into the actual distribution
> lanes...
64
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
Mathias Krause wrote:
> --> 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)
>
Install and run hwinfo to see what the driver names are.
hwinfo --usb
hwinfo --sound
> So I just left these 2 lines
Sorry, again I need a second mail.
First just try this and reboot:
cat /etc/asound.conf
>> pcm.!default {
>> type hw
>> card 2
>> }
>> ctl.!default {
>> type hw
>> card 2
>> }
>>
>
> There is no such file for a 64 Studio 3.0-beta3 by a clea
Sorry, a third mail.
It might has not the effect to "inform" applications that the default
audio device should be hw:2 insetad of hw:0, but maybe it changes the
default hw:0 to become hw:2.
> to set the default HW ... but maybe this has no effect...
>
>>> cat /etc/asound.conf
>>>
> pc
On Thursday 30 July 2009 11:56:23 quen...@64studio.com wrote:
> > it would be great to see SuperCollider as a package(s) for 64studio.
> >
> > We already build Ubuntu-packages, and these seem to be getting quite
> > popular
> > by users, and don't seem to give much cause for trouble.
> > It would b
Ok ... me again creating a lot of traffic on this list...
Now i removed the /etc/asound.conf file
and added the 2 line to /etc/modprobe.d/alsa-base
"alias snd-card-0 snd-ice1712
options snd-ice1712 index=0"
I restarted the system and now with
cat /proc/asound/cards
0 [BCF2000]: USB-Audio
And again:
I don't know what was going wrong before,
now, the dmesg error message is no longer present. ICE1712 is now my
first card.
Starting jack says:
Device busy
Totem does nothing
System-preferences-sound test says device is busy
sudo lsof | grep snd
mixer_app 5416 matze 19u
Hey folks !!!
I've good news. I will stop flooding this mailing list with mails ... i
got the solution ...
it was SOOO simple ...
i just did a
"sudo killall esd" ...
and everything works fine ...
now i did "apt-get remove esound" and everything is moving fine !!! ...
1000 thanks to all of you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mathias Krause wrote:
>
Glad you got everything sorted. esound should not be installed anyway.
> Then i tried
> mplayer -ao alsa /usr/share/sounds/somesound.wav
>
For future reference when testing alsa with mplayer, you may need to
specify the s
Mathias Krause wrote:
> Hey folks !!!
>
> I've good news. I will stop flooding this mailing list with mails ... i
> got the solution ...
>
> it was SOOO simple ...
>
> i just did a
> "sudo killall esd" ...
> and everything works fine ...
>
> now i did "apt-get remove esound" and everything is movi
3.0-beta3 OT:
Some time ago I couldn't hear sound of a video by ALSA, while JACK +
connected clients were running. Today it's possible to run JACK +
connected clients and to hear the sound of a video by ALSA. I was fine
with the first situation and I'm more fine with today's situation :). I
ju
16 matches
Mail list logo
