Slow Track Change From Command Line

[Rob McAuley]

Exaile version: source bzr, checkout 2010-03-23
Distro: Arch Linux (up to date)
Debug output: None

Expected behaviour: Reasonably fast track switch. Times were acceptable in official release of 0.3.1 but have greatly increased since.
Actual behaviour: There's a 2 second delay between the key press and the actual response of Exaile. Add in the extra time it takes Exaile/gstreamer to switch tracks in general, and the delay on an actual track change can reach 3 seconds on a reasonably fast machine. (1.66GHz Core 2 Duo, 2GB RAM, Vertex SSD)

I'm not sure what's taking Exaile so long to fire up and send a dbus signal along to the main Exaile window. But it sure is taking a lot longer than it did in 0.3.1. When I first went to pause a song I wondered for a few seconds if I had even pressed the right button, or if the shortcuts were working at all. It can be extremely troublesome when trying to work backwards through a playlist, as the delay leaves me uncertain in regards to what Exaile is doing.

[Rob McAuley (rmcauley)]

Should be a little more thorough, apologies:

Exaile 0.3.1:

rmcauley@distorted:~$ time exaile --next

real 0m0.291s
user 0m0.210s
sys 0m0.027s

Exaile 0.3.1.0+bzr2933:

rmcauley@distorted:~/exaile-dev/exaile$ time ./exaile --next

real 0m1.337s
user 0m1.213s
sys 0m0.037s

It's a minor complaint, but a very noticeable one for people who make use of the command line shortcuts for global hotkeys.

[reacocard (reacocard)]

please try with trunk/2938, it should be much faster.

[Rob McAuley (rmcauley)]

Fixed. Thank you!