Lag on Banshee due to empty track info + amazon cover downloading
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CoverGloobus |
Fix Committed
|
Medium
|
Alexandr Grigorcea |
Bug Description
When you are using Banshee and you manually change the song, CoverGloobus suffers from a short lag (of about 5 seconds) and then reacts to the change. For the more technical of you, the terminal output [INFO] Song changed: (...) is displayed after the 5 seconds.
However, when the song is changed naturally --as in when the previous song ends the next one starts playing-- CoverGloobus exhibits a perfect, normal behavior and changes the cover (along with other metadata) instantly.
So I tried to fix the problem myself to write a patch, but while troubleshooting the players/Banshee.py module I found out what I explained in the paragraph above, and then I had no clue where the problem would be. I believe, however, that the problem is located where CoverGloobus interacts with the designated player.
summary: |
- Extreme lag on Banshee + Banshee not getting track info automatically |
summary: |
- Banshee not getting track info automatically + Lag on Banshee due to cover downloading and empty track info |
summary: |
- Lag on Banshee due to cover downloading and empty track info + Lag on Banshee due to empty track info + amazon cover downloading |
Changed in covergloobus: | |
assignee: | nobody → Alexandr Grigorcea (cahr-gr) |
status: | Confirmed → Fix Committed |
Ok, I have found there is a debug flag one can enable, and I found as well that the problem occurs because there is some Amazon cover downloader that is called when the cover is not found. This implies that the problem resides in that the object CoverGloobus. track.cover is not working properly when Banshee is selected as a player.
However, the solution consists of two steps:
1. Make the CoverGloobus.track object work when Banshee is selected the player.
2. Make the Amazon cover downloading function asynchronious.