Support for a private local music library

Answered

Comments

4 comments

  • Official comment

    Thanks for the tip Hans;

    For those having slow re-indexing of a music library stored on a NAS, I was able to improve my re-indexing performance drastically by specifying a more explicit share/folder on the NAS.

    So, previously, I was just pointing to my global share on my NAS (e.g. \\server\share), but this share contains more than just my music files. It also contains copies of thousands of other files.

    I now point in BluOS to a more explicit path (\\server\share\music\iTunes\iTunes Media\Music). Re-indexing performance has improved immensely since then. It make sense if you think about it, I know, but in 2019, I expect things to "just work", fast. I should have known better :-)

    Comment actions Permalink
  • Avatar
    Frans R

    Hi Hans,

    What helps in my case:

    only put one folder.jpg with max 600x600 pixels in the root and move all the other artwork to a subfolder called artwork. In that way the impact on memory and speed is limited.

    0
    Comment actions Permalink
  • Avatar
    Hans

    Hey Frans

    Thanks for the tip!

    I'm in the process of adding a cover.jpg in all my album folders (due to BluOS not always picking up cover art stored inside the music files -- but that is another story).

    What indexing performance improvement can I expect?

    0
    Comment actions Permalink
  • Avatar
    Hans

    For those having slow re-indexing of a music library stored on a NAS, I was able to improve my re-indexing performance drastically by specifying a more explicit share/folder on the NAS.

    So, previously, I was just pointing to my global share on my NAS (e.g. \\server\share), but this share contains more than just my music files. It also contains copies of thousands of other files.

    I now point in BluOS to a more explicit path (\\server\share\music\iTunes\iTunes Media\Music). Re-indexing performance has improved immensely since then. It make sense if you think about it, I know, but in 2019, I expect things to "just work", fast. I should have known better :-)

    Still lacking the automatic re-indexing when something changes to my library.

    I think most music library software have their own database file or files (e.g. for iTunes, it is an XML file). Can BluOS just not monitor this file for any change (say check the modification date of this file every 5 minutes), and when a change is detected, just perform a re-index? This way, BluOS can be agnostic about the music library software, and thus supporting potentially all/most of them, and provide a near-seamless integration for its customer base?

    0
    Comment actions Permalink

Please sign in to leave a comment.