Library / local folder not showing up in music after indexing

Beantwortet

Kommentare

3 Kommentare

  • Offizieller Kommentar
    Gerben

    Might be IP issue or ghost share, just a guess.....

    Have a look in the controller app at Diagnostics, which shows the current share(s) underneath Connected Shares:

    1. Verify if the IP matches that of your Windows PC. If not, better to assign it a reserved IP in your router.
    2. If two shares are listed, one of them may be a left over from a share you created to your previous Windows install. BluOS has a bug that has been around for years and leaves a "ghost share" behind, if you remove a share from BluOS while that share is not accessible in the network.
  • Tom H

    At the top under diagnostics it shows IP address, is that he IP of he player or ? Cause below where it says Connected Shares, it shows the path to the shared folder, and it has a slightly different IP. The first 6 numbers are the same but the last 3 numbers are different, should it be the same both places ? Im not sure how I can fix that to be the same. I'll try send a support ticket to bluesound and see if they can help me out with that, unless you know how :)

    0
  • Brian
    Lossless

    The IP under diagnostics is the Bluesound player IP, the Connected Shares IP is where the local library is stored.

    If this is an IP issue it may be helpful to unplug the Bluesound player for 5 minutes, reboot the router and storage location, wait 5 more minutes plug in the Bluesound player and see if this resolves it.

    Best practice is to use device address reservations on the router for the player and storage location.

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.