Stable: 2.5.2
Development: 2.6-alpha3
When i start playing some music in moc i can't play any other music like youtube in my browser or even sound in terminal. I don't know it is only for me but in linux live cd version everything is ok. When other music source playing music moc displaying error: device or resources is busy. I don't know what can i do now.
OS: Kali linux.
MOC version: 2.6-alpha3
tomaszg
Sun, 2018-12-09 18:19
Permalink
It seems you're not using
It seems you're not using ALSA's dmix or similar thing. Check what ALSA device are you using.
Lektor
Sun, 2018-12-09 18:27
Permalink
aplay --version: 1.1.7 by
aplay --version: 1.1.7 by Jaroslaw Kysela
cat /proc/asound/version: Advanced Linux Sound Architecture Driver Version k4.18.0-kali3-amd64
Need i to install something newer or else?
tomaszg
Sun, 2018-12-09 18:31
Permalink
My guess is you don't need
My guess is you don't need newer version of ALSA. You just need to check MOC config file if it is using ALSA's "default" device or e.g. some "hw" device which bypass dmix. Also, your .asoundrc file might specify something that breaks dmix. It's really hard to guess without any hard data (e.g. debug output from MOC, aplay -l, aplay -L, ...).
Lektor
Sun, 2018-12-09 18:38
Permalink
Ok, i removed moc config file
Ok, i removed moc config file and i don't have .asoundrc file, nothing was happened. output from:
Lektor
Sun, 2018-12-09 22:07
Permalink
Ok now i know what is the
Ok now i know what is the problem. It is libasound2 package, when it is upgraded moc can't play music with others sound source and displaying "no valid sound driver" or "device or resources is busy". libasound2 version 1.1.6 working good but 1.1.7 generate this above problem (for me). Thanks Tomaszg for help and everything :)
tomaszg
Sun, 2018-12-09 22:28
Permalink
That's surprising. I'm on
That's surprising. I'm on alsa-lib 1.1.7 myself and everything works fine. Maybe this package ships together some different default settings.
Lektor
Sun, 2018-12-09 23:12
Permalink
Yeah that is strange, they
Yeah that is strange, they maybe fix this in next update. Now i hold libasound2 package with "apt-mark hold libasound2" and waiting for update. Thanks again Tomaszg