> is it really 80-rc1 or whole line ?
> i think it's core bug and it's always been like that
I do not know, this is the first release i try since a very very long time.
> btw when you stop text interface it takes 100% of your cpu
I confirm this. Well, i suppose i will stick to the GTK2 interface for the moment then. Or i may experiment with the XOSD one, which seems to have the same problem of CPU consuming while idle (up to 3%, not 100% like in text mode).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With the JACK output, the GTK interface and the last git code: 8.9 playing, 11.9 idle (instantaneous values).
The same with the text interface 5.8 playing, no idle.
The same with mplayer at the console 7.8 playing, no idle.
With ALSA output and the daemon interface: 0% CPU when idle, 12.1 when playing.
With JACK output and the daemon interface: 1.5% CPU when idle, 6.8 when playing.
mplayer in slave mode vary between 0 to 1% when idle, 4.9 playing.
Different interfaces give different values, and different outputs seam to give different values too. But the only interface that consume cycles is the GTK one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
is it really 80-rc1 or whole line ?
i think it's core bug and it's always been like that
btw when you stop text interface it takes 100% of your cpu
Logged In: YES
user_id=303929
Originator: YES
> is it really 80-rc1 or whole line ?
> i think it's core bug and it's always been like that
I do not know, this is the first release i try since a very very long time.
> btw when you stop text interface it takes 100% of your cpu
I confirm this. Well, i suppose i will stick to the GTK2 interface for the moment then. Or i may experiment with the XOSD one, which seems to have the same problem of CPU consuming while idle (up to 3%, not 100% like in text mode).
Logged In: YES
user_id=303929
Originator: YES
update : alsaplayer-0.99.80_rc2 behave the same.
From the strace output it looks like alsaplayer is polling on /dev/snd/timer,
which wakes it up all the time.
With the JACK output, the GTK interface and the last git code: 8.9 playing, 11.9 idle (instantaneous values).
The same with the text interface 5.8 playing, no idle.
The same with mplayer at the console 7.8 playing, no idle.
With ALSA output and the daemon interface: 0% CPU when idle, 12.1 when playing.
With JACK output and the daemon interface: 1.5% CPU when idle, 6.8 when playing.
mplayer in slave mode vary between 0 to 1% when idle, 4.9 playing.
Different interfaces give different values, and different outputs seam to give different values too. But the only interface that consume cycles is the GTK one.