Asset UPnP R2025 beta.
Collapse
X
-
Thanks for the bug report.
Please use Troubleshooting / Save Configuration Dump [normal] to download a copy of your Asset profile and email to peter@dbpoweramp.com for analysis, including specific search queries returning incorrect results for you. I'll then be able to replicate the behavior on the development machine.Leave a comment:
-
Please use Troubleshooting / Save Configuration Dump [normal] to download a copy of your Asset profile and email to peter@dbpoweramp.com for analysis, including specific search queries returning incorrect results for you. I'll then be able to replicate the behavior on the development machine.Leave a comment:
-
I'm really not sure of the best place to report this, but the newest version (2025-02-03) hasn't fixed the "search tracks/songs" issue that I reported above - so that's still outstanding.Leave a comment:
-
The newest Asset beta for Synology (R2025-01-09) doesn't fix the problem I've been having for a few weeks now, whereby entire albums are being overlooked during "track/song search". I don't know how many of my 13,181 albums are affected, but there appears to be a lot. The albums themselves are found during "album search", and they play perfectly fine, but the tracks contained within them are overlooked entirely during searches. Rebuilding the database hasn't helped.
I have a Synology DS923 running version 7.2.2-72806 of the OS, and am searching using Hi-Fi Cast on an Android Samsung S21.Leave a comment:
-
Hi, It might be helpful to provide your exact NAS model and DSM version/build as some users are reporting issues with Asset UPnP while others are not. Mine works on my DS1821+ running DSM 7.2.2 -72806 build 2.
Leave a comment:
-
Just installed the 2025-01-09 build on Synology DSM7 and I seem to have a problem in that the package manager remains at "Getting Status" and does not show it is Runninf or offer the ability to Stop etc. It will unisnstall and when in Getting Status it seems actrually to be running - the web interface works ok and music can be streamed. Not had this problem before . . .
Leave a comment:
-
With the new Build 2024-11-05 all is good again and works very fast and smooth.
Thanks for fixing.Leave a comment:
-
I too was experiencing some lost albums. They were in the count, but not appearing in the control point. When lookking at logs it seemed to be saying that the albums in question were hidden, althgough there was no change in permissions on the folders in question. Updated to latest beta last night and albums have appeared again. Thanks Peter.Leave a comment:
-
Updated first post with info about downgrading beta >> stable on Synology without loss of config.Leave a comment:
-
Thanks for the bug report.
Missing albums on your config are most certainly NOT inflicted by the new limit of files/folders listed. This affects only browsing of extremely large libraries.
If you run into such bugs again, please first try "clear database, rescan all folders"; if that doesn't help, save configuration dump (normal good enough) and email to peter@dbpoweramp.com including info what exactly is missing (album/artist names etc).Leave a comment:
-
Because some control points ask for the 1 million tracks in one view, then ask for another view with another 1 million items, and these are cached and take up memory.
Most control points behave better and are sensible.
The issue you are seeing should not be this.Leave a comment:
-
Sorry, I don't understand what you try to say.
Why then these new restrictions, if Asset can handle 1 million tracks?
My collection is much, much, much smaller than 1 million tracks.
Until the last beta, Asset worked super for me.
It was responsive and very fast in detecting changes in the collection.
But with the last beta and the new introduced restrictions something broke.
Asset still reports the correct number of albums and tracks.
But when browsing (on an iPad control point or on a Win11 computer) I don't see most of my collection. So, somehow almost all tags aren't read or not shown.
I also did a complete new scan of my collection, but that makes no difference.
Because I couldn't downgrade, I de-installed this beta and re-installed the latest official release.
And now browsing my collection is okay again.
So, I didn't change my collection, just upgraded to the last beta.
And for me, the latest beta broke something.Leave a comment:
Leave a comment: