Bug#881715: alsa-utils: High CPU usage on the default device

2017-12-13 Thread Andoru
Okay, so I installed Arch from scratch with a minimalist set-up of OpenBox and tint2, installed alsa-utils and alsa-tools, and made that modprobe config file to disable HDMI output, just like I did when I did the netinstall of Debian. Then installed vlc and played all the files I played previously

Bug#881715: alsa-utils: High CPU usage on the default device

2017-12-06 Thread Andoru
Yes, I was about to do that. Though those distros all have PulseAudio by default, so I thought of installing Arch on a separate partition and test ALSA there.

Bug#881715: alsa-utils: High CPU usage on the default device

2017-12-06 Thread Elimar Riesebieter
* Andoru [2017-12-04 21:54 +0200]: > > As you are the only one out of 60thsd Debian Alsa users who > > reported a high cpu-usage running alsa apps and I can't reproduce > > and don't know your system > > What is there else that you'd like to know? What is it that I should be

Bug#881715: alsa-utils: High CPU usage on the default device

2017-12-04 Thread Elimar Riesebieter
* Andoru [2017-12-04 23:41 +0200]: [...] > Could you (or someone else) perhaps let me know who provided the driver for > ALC887-VD? Maybe that way I could contact them directly. alsa-de...@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel Elimar --

Bug#881715: alsa-utils: High CPU usage on the default device

2017-12-04 Thread Andoru
> As you are the only one out of 60thsd Debian Alsa users who > reported a high cpu-usage running alsa apps Forgot to mention this: just because I'm the only one to report this issue doesn't mean I'm the only one to experience it! I'm sure at least other Debian users with the same sound chip as

Bug#881715: alsa-utils: High CPU usage on the default device

2017-12-04 Thread Andoru
> As you are the only one out of 60thsd Debian Alsa users who > reported a high cpu-usage running alsa apps and I can't reproduce > and don't know your system What is there else that you'd like to know? What is it that I should be doing to diagnose this? That's what I've been asking for the

Bug#881715: alsa-utils: High CPU usage on the default device

2017-12-04 Thread Elimar Riesebieter
Hi Andoru, * Andoru [2017-12-04 17:02 +0200]: > > Did you created an /etc/asound.conf > > No, I have no such file. > > > or adapted some options loading your snd- modules? > > Yes, I mentioned in the first post that I created a rule under > /etc/modprobe.d/ to disable

Bug#881715: alsa-utils: High CPU usage on the default device

2017-12-04 Thread Andoru
> Did you created an /etc/asound.conf No, I have no such file. > or adapted some options loading your snd- modules? Yes, I mentioned in the first post that I created a rule under /etc/modprobe.d/ to disable HDMI audio output through the integrated chips. But you added another reply so you

Bug#881715: [Pkg-alsa-devel] Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-28 Thread Elimar Riesebieter
* Elimar Riesebieter [2017-11-28 21:11 +0100]: [...] > There must be something configured on your system which cauuses your > issue. You don't have an .asoundrc. Did you created an /etc/asound.conf > or adapted some options loading your snd- modules? A clean install of >

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-28 Thread Elimar Riesebieter
Hi Andoru, * Andoru [2017-11-28 15:19 +0200]: > Forgot to check previously, but whenever I use those CLI players you > suggested, they also monopolise the soundcard, making me unable to play > other stuff in parallel, just like how it would happen when setting the > specific

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-28 Thread Andoru
Forgot to check previously, but whenever I use those CLI players you suggested, they also monopolise the soundcard, making me unable to play other stuff in parallel, just like how it would happen when setting the specific subdevice in VLC. So, since I'm not able to use those CLI players to play

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-21 Thread Elimar Riesebieter
* Andoru [2017-11-19 15:11 +0200]: > > I meant .asoundrc. Please notice the dot. > > > > $ find $HOME -name '.asoundrc*' > > > > will do the trick > > Of course, that file search was meant for demonstration. I've already > looked at the home folder with the file manager, but

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-19 Thread Elimar Riesebieter
* Andoru [2017-11-18 01:47 +0200]: > > Maybe your speakersystem needs some rectification? > > You mean the external speakers? I use headphones. I don't know what those > have to do with ALSA or this issue I'm having. > > > Or you can ask here: >

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-17 Thread Andoru
> Maybe your speakersystem needs some rectification? You mean the external speakers? I use headphones. I don't know what those have to do with ALSA or this issue I'm having. > Or you can ask here: >

Bug#881715: [Pkg-alsa-devel] Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-17 Thread Elimar Riesebieter
* Andoru [2017-11-17 15:12 +0200]: > Okay... then what is there to do next? > Call me technologically illiterate, or say that I don't know of the inner > workings of ALSA, but I don't think this can be a given that a simple task > such as outputting audio could take 13-20% of

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-17 Thread Elimar Riesebieter
* Andoru [2017-11-17 15:12 +0200]: > Okay... then what is there to do next? > Call me technologically illiterate, or say that I don't know of the inner > workings of ALSA, but I don't think this can be a given that a simple task > such as outputting audio could take 13-20% of

Bug#881715: [Pkg-alsa-devel] Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-17 Thread Andoru
Okay... then what is there to do next? Call me technologically illiterate, or say that I don't know of the inner workings of ALSA, but I don't think this can be a given that a simple task such as outputting audio could take 13-20% of a quad core CPU!

Bug#881715: [Pkg-alsa-devel] Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-16 Thread Elimar Riesebieter
* Andoru [2017-11-16 23:47 +0200]: > > Tested on ALC892, CX20561, emu10k1 and ES1371/1. None of them showed high > cpu usage. > > Could you let me know how you configured ALSA? It could be that I might > have misconfigured something, but I wouldn't know what... > Is there

Bug#881715: [Pkg-alsa-devel] Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-16 Thread Andoru
> Tested on ALC892, CX20561, emu10k1 and ES1371/1. None of them showed high cpu usage. Could you let me know how you configured ALSA? It could be that I might have misconfigured something, but I wouldn't know what... Is there some advanced testing/diagnonsis that I could try to do to figure out

Bug#881715: [Pkg-alsa-devel] Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-16 Thread Elimar Riesebieter
* Andoru [2017-11-16 02:22 +0200]: > > I tried that on 3 different soundcards. I don't get vlc as a htop > COMMAND. It is always /usr/bin/vlc. > > I swear I'm using the native VLC from the Debian repos. > > > Please tell me how you fired up vlc. > > I started VLC through

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-15 Thread Andoru
> I tried that on 3 different soundcards. I don't get vlc as a htop COMMAND. It is always /usr/bin/vlc. I swear I'm using the native VLC from the Debian repos. > Please tell me how you fired up vlc. I started VLC through OpenBox's menus, and on that menu the command to start VLC is simply

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-15 Thread Elimar Riesebieter
Control: tags -1 unreproducible * Andoru [2017-11-14 23:45 +0200]: > > > > Just run htop while an alsa-process needs high cpu load. Copy the > > line which shows that from (h)top to this bug report. Or just file a > > screenshot to a puplic server somewhere. > > > >

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-15 Thread Andoru
No...? Why would I do something silly like that?

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-14 Thread Elimar Riesebieter
* Andoru [2017-11-14 23:45 +0200]: > > > > Just run htop while an alsa-process needs high cpu load. Copy the > > line which shows that from (h)top to this bug report. Or just file a > > screenshot to a puplic server somewhere. > > > > Alright: > VLC playing a FLAC file on the

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-14 Thread Andoru
> > Just run htop while an alsa-process needs high cpu load. Copy the > line which shows that from (h)top to this bug report. Or just file a > screenshot to a puplic server somewhere. > Alright: VLC playing a FLAC file on the default device: > PID USER PR NIVIRTRESSHR S %CPU

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-14 Thread Elimar Riesebieter
* Andoru [2017-11-14 22:03 +0200]: > > What makes you think an alsa process eats high cpu usage? > > You skipped a paragraph from my report: > > > It's just easy to tell if an app/ALSA uses too much CPU if you just play > some audio files > > and you don't have anything else

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-14 Thread Andoru
> What makes you think an alsa process eats high cpu usage? You skipped a paragraph from my report: > It's just easy to tell if an app/ALSA uses too much CPU if you just play some audio files > and you don't have anything else that might need the extra CPU power, > like rendering the video

Bug#881715: alsa-utils: High CPU usage on the default device

2017-11-14 Thread Elimar Riesebieter
Control: found -1 1.1.3-1 Hi Andoru, thanks for your bug report. * Andoru [2017-11-14 16:13 +0200]: > Package: alsa-utils > Version: 1:1.1.3-1 > Severity: normal > > > As the title says, I'm having a bit of an issue with ALSA, and the high > CPU (~15-20%) usage in some