Bluesound stand alone server

Answered

Comments

6 comments

  • Official comment
    krang

    'I forwarded your request to the quality assurance and development department for consideration' might be the standard answer you'll get in here obviously but let's try to help and understand you better:

     

    Are you concerned about the CPU handing out / sharing the library information amongst all (new) players and storing them? Have you seen any CPU load while this is happening to concern you? For me, this process was very fast and no problem at all. It also should not interfere with the DAC at all...

    But also to explain your Roon/Bluesound comparison: Roon wants and supports you to use multiple Roon endpoints that would normally not talk to each other from various manufactures to play from the same sources without the hassle of setting up everything all the time. This is why the information is stored centralized and handed out to the endpoints when needed. Bluesound does NOT want you to use various manufactures but keep you in their ecosystem making a server solution unnecessary.

    If I where you I would rather ask for more API stuff allowing the community to code something that could tie in with the Bluesound ecosystem to be generally controlled/changed/interacted with as we as users please.

    My answers are my personal view on your question, of course :)

  • Scott Reynolds

    Hi Krang Thanks for your answer. I have a large library of 6TB. Bluesound cannot support this because obviously there is hardware limitations to the size of the database.Your can control bluesound using http functions that works well. I think they consider that the API. I understand Bluesound will keep it a closed system, maybe a comparison to plex would be better. They have a plex server and plex clients.

     

    Thanks!

    0
  • Bjørn Ulvik
    Hi-Res

    I have a large library of 6TB. Bluesound cannot support this because obviously there is hardware limitations to the size of the database.

    No issues indexing a "large" library. Got memory issues above 392' files. Reduced and keeping the share at 350' files, and all is good.

    0
  • krang

    Oh wow, I'm close to that but not there. This is surprising as I don't think it's actually the hardware rather some odd way of storing, sharing, and handling the database. If you have 400k files the actual database should still be easy to handle. At least in a SQL world...

    I was once running a forum with ~1.8M Accounts txt based (including posts). That was no fun. Same hardware to SQL, smooth for another 10 years...

    0
  • Scott Reynolds

    Maybe its cause a lot of my files have metadata embedded. To be honest I stopped using the Bluesound frontend 2 years ago it started to feel sluggish at times. I've been using Roon but Bluesound would be fine and the wife prefers it. So Bluesound uses SQL? I just like centralizing everything on a server, that's the job of a server. Doesn't Bluesound allow you to choose one node as a kinda sever, you just index on that one and all the others update from that?

    0
  • Tony W.
    Product Support Manager

    Maybe its cause a lot of my files have metadata embedded

    Unlikely, unless you are using a rare form of WAV files. WAV files have no standardised metadata format, why most have given up and move to FLAC which does have standardised metatags and 0 lossless ability. That being said, BluOS searches tags on WAV files in three of the most common ways. 

    Indexes are not track limited but size limited. Consider right sizing your artwork using the optimise artwork toggle in the Settings menu. This will slow down the index process but will allow for more music as Artwork accounts for over 70% of the size of your Library.

    Your Indexing issues can easily be diagnosed by Searching Index in the above query window in the top Right.

    Check these out;

    https://support.bluos.net/hc/en-us/articles/360000230288-Can-BluOS-index-over-200-000-songs-in-my-Library-

    https://support.bluos.net/hc/en-us/articles/360000364067-Why-is-my-music-not-sorted-correctly-after-an-Index-

    https://support.bluos.net/hc/en-us/articles/360000235328-Why-Did-Indexing-Cause-My-BluOS-Player-to-Restart-

    For all other questions or specific issues you are having with the BluOS Local Library, please select Help, Send Support Request in the BluOS App and our Support Crew will be happy to provide some hints and tips.

    0

Please sign in to leave a comment.