title
Products            Buy            Support Forum            Professional            About            Codec Central
 
Results 1 to 15 of 17

Thread: Asset UPnP for Linux, R6.4 beta

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Super Moderator
    Join Date
    Jul 2011
    Posts
    812

    Asset UPnP for Linux, R6.4 beta

    Current version: R6.4 beta 4

    Downloads:
    QNAP: https://www.dbpoweramp.com/beta/Asset_R6.4b4.qpkg
    Synology: https://www.dbpoweramp.com/beta/Asset-R6.4b4.spk
    Linux x86 32-bit: https://www.dbpoweramp.com/beta/Asse...nux-x86.tar.gz
    Linux x86 64-bit: https://www.dbpoweramp.com/beta/Asse...nux-x64.tar.gz
    ARM / Raspberry Pi: https://www.dbpoweramp.com/beta/Asse...x-ARM32.tar.gz

    Change since R6.3:
    • Fixed missing folder watching inotify code on Linux. Music folders are monitored in real-time again.


    Changes in beta 2:
    • Added a workaround for some control points failing to show Asset after its unique identifier formatting was changed in R6.3.


    Changes in beta 3:
    • Fixed --shutdown command not working reliably.
    • Improved feedback to manual rescan of media library folders - in some scenarios, the information about rescan-in-progress would only show with a delay.
    • Added INSTALL.sh and UNINSTALL.sh scripts. Just unpack the tarball and run ./INSTALL.sh in the folder to get Asset installed in ~/bin/AssetUPnP and registered to run on startup (via crontab). If Asset is already installed there, existing installation is upgraded. UNINSTALL.sh reverts these changes, removing Asset and its configuraiton. No need to run as root.


    Changes in beta 4:
    • Added ARMv5 binary.
    • Once again compatible with old QNAP models where R6.3 would not run.
    • Should work on ARMv5 based Synology models.


    No Mac version right now, the changes only affect Linux.
    Last edited by PeterP; 11-22-2019 at 12:58 PM. Reason: Beta 4

  2. #2
    dBpoweramp Enthusiast
    Join Date
    Dec 2013
    Posts
    235

    Re: Asset UPnP for Linux, R6.4 beta

    Hi Peter, The Rescan folders detecting changes function on the Web page does not work and has not since R6.3 Beta 3
    This is on RPi2 running DietPi.
    So the change introduced that causes the inotify to not work, in R6.3 beta 3 & R6.4 may have affected other areas.
    The time based rescan does work!

    Simon

  3. #3
    dBpoweramp Enthusiast
    Join Date
    Dec 2013
    Posts
    235

    Re: Asset UPnP for Linux, R6.4 beta

    However the auto-detect may also be working over my RPi and ReadyNAS configuration.
    Will do some more testing, however anything I added this weekend is showing, but this could just be the time based forced scan.
    Thanks,
    Simon

  4. #4
    dBpoweramp Enthusiast
    Join Date
    Dec 2013
    Posts
    235

    Re: Asset UPnP for Linux, R6.4 beta

    No, the Auto-detect does not work for me from a RPi to a ReadyNAS unit - but it never has.
    So, the Manual push to rescan and detect changes does not work, and has not since R6.3 Beta 2 or 3
    As such, it is only the interval based rescan which causes an changes or additions to be reflected.
    If you could take a look at this area, please

  5. #5
    Super Moderator
    Join Date
    Jul 2011
    Posts
    812

    Re: Asset UPnP for Linux, R6.4 beta

    Automatic detection of changed folder contents may indeed not work with network shares, it's a known issue and not something we can help with - if the network server isn't feeding the relevant information in the first place.

    However, "Rescan folders detecting changes" should work regardless of that.
    Please enable debug logging, apply press "Rescan folders detecting changes", then download the library log file and post it here - or send to peter@dbpoweramp.com for analysis.

  6. #6
    dBpoweramp Enthusiast
    Join Date
    Dec 2013
    Posts
    235

    Re: Asset UPnP for Linux, R6.4 beta

    Logs sent, however I am now getting a forced rescan following reboot of the RPi & restarting Asset.

    If we could see that the logs are reporting the correct behaviour, now.

    Thanks,
    Simon

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •