2015-01-01, 03:43
Hi guys,
first of all a big "thank you very much" for creating and still developing KODI aka XBMC!
This nice peace of software worked fine for me, till i tried to give my music library in KODIs hands.
I have a very big music library, filled with tons of CDs and stuff from jamendo - all in all about 40k+ files.
Scrapers worked fine for many files, missing information is acceptable.
But the mess began, as i tried to use KODI (my first attempt was with XBMC 13.x) as a music player for this large collection. Obviously KODI should need a minute to collect all neccessary information from the database "(it needs round about 1 minute on my Raspberry Pi, same time on my Amazon FireTV with SPMC and round about 20 secs on my Win-Laptop). Collection the stuff and rendering is a time consuming process and during my search i already found some threads regarding this issue.
But as soon as i start to play a song, i got surprised: KODI crashed, needed more then 10 minutes or did nothing to play a simple MP3 from the shown list!
Just on the Windowsinstallation all worked fine (all devices had a fresh install and this behaviour was already present in the 13.x-stream).
The minute to collect all items is fine for me, but the process to start a song from the list should be done in microseconds!
Unfortunately i haven´t found a thread regarding this problem, so i have to think, that just me is using KODI as a MP3-player on the Pi or other "small" devices.
But i guess, that you should take a deep look inside your code, because this behaviour seems totaly senseless: there should no calculation, no memory clean up or whatever. Just a request on the database for path and file and a final "go" to the player (ffmpeg?).
I am neither a developer nor an expert in computers or even bug reporting.
So just give me a hint, what i have to do, to help you solving this issue. I already took a look inside the "log"-folder, but there is a ton of them and i do not know, which information you realy need to examine this mess.
Some detailed technical information:
device: Pi with XBMX and KODI, FireTV with SPMC
database: local and MySQL
behaviour: isn´t clear: sometimes crashes, sometimes do nothing, sometimes work after many minutes. Mostly system "freezes" for the user
If i start the MP3 from the "file" section, all works fine, all "database" actions fail.
From my side, it looks like a problem with the length of the list, because the time between starting and playing the selected MP3 grows with the size of the indexed files (size of list eg number of indexed songs) inside the database. It is not a problem of the database itself, because local and remote databases have the same issue.
I hope, that any of the devs can confirm this behaviour.
Thx a lot and happy new year
first of all a big "thank you very much" for creating and still developing KODI aka XBMC!
This nice peace of software worked fine for me, till i tried to give my music library in KODIs hands.
I have a very big music library, filled with tons of CDs and stuff from jamendo - all in all about 40k+ files.
Scrapers worked fine for many files, missing information is acceptable.
But the mess began, as i tried to use KODI (my first attempt was with XBMC 13.x) as a music player for this large collection. Obviously KODI should need a minute to collect all neccessary information from the database "(it needs round about 1 minute on my Raspberry Pi, same time on my Amazon FireTV with SPMC and round about 20 secs on my Win-Laptop). Collection the stuff and rendering is a time consuming process and during my search i already found some threads regarding this issue.
But as soon as i start to play a song, i got surprised: KODI crashed, needed more then 10 minutes or did nothing to play a simple MP3 from the shown list!
Just on the Windowsinstallation all worked fine (all devices had a fresh install and this behaviour was already present in the 13.x-stream).
The minute to collect all items is fine for me, but the process to start a song from the list should be done in microseconds!
Unfortunately i haven´t found a thread regarding this problem, so i have to think, that just me is using KODI as a MP3-player on the Pi or other "small" devices.
But i guess, that you should take a deep look inside your code, because this behaviour seems totaly senseless: there should no calculation, no memory clean up or whatever. Just a request on the database for path and file and a final "go" to the player (ffmpeg?).
I am neither a developer nor an expert in computers or even bug reporting.
So just give me a hint, what i have to do, to help you solving this issue. I already took a look inside the "log"-folder, but there is a ton of them and i do not know, which information you realy need to examine this mess.
Some detailed technical information:
device: Pi with XBMX and KODI, FireTV with SPMC
database: local and MySQL
behaviour: isn´t clear: sometimes crashes, sometimes do nothing, sometimes work after many minutes. Mostly system "freezes" for the user
If i start the MP3 from the "file" section, all works fine, all "database" actions fail.
From my side, it looks like a problem with the length of the list, because the time between starting and playing the selected MP3 grows with the size of the indexed files (size of list eg number of indexed songs) inside the database. It is not a problem of the database itself, because local and remote databases have the same issue.
I hope, that any of the devs can confirm this behaviour.
Thx a lot and happy new year
