Asset UPnP R2024 beta.

[Arnold]

With the new Build 2024-11-05 all is good again and works very fast and smooth.
Thanks for fixing.

[psweetie]

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.

[PeterP]

Updated first post with info about downgrading beta >> stable on Synology without loss of config.

[PeterP]

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).

[Spoon]

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.

[Arnold]

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.

[Spoon]

This is just returning data for the control point, Asset can handle 1 million tracks on the right computer.

[Arnold]

Reflection on Build 2024-10-28 (Synology):
Restricted listing to 20000 tracks & 10000 subfolders per folder, to prevent Asset from using large amounts of memory and becoming unresponsive.

Hi Peter.
Can you tell more about this new restriction in Asset?
Restricted listing to 20000 tracks & 10000 subfolders per folder

Does this mean it is better for Asset to divide the music collection in multiple (small) mediafolders?

And when participating in beta-testing, why is it not possible to 'downgrade' to the last released version?
Or is this a Synology restriction?

[Arnold]

Reflection on Build 2024-10-28 (Synology):
Restricted listing to 20000 tracks & 10000 subfolders per folder, to prevent Asset from using large amounts of memory and becoming unresponsive.

Not sure what this means.
But this version is not working for me.
When browsing I'm missing a lot of my collection (approx. 2300 albums).
Browsing albums only shows 779 albums, and all my composers are gone (only 9 are shown).

Oh, oops... I can't change back to an older version.

[PeterP]

Feature request for clearing known clients list noted.
You can manually locate KnownControlPoints.txt and edit/clear it to get rid of unwanted entries, but shut Asset down first / restart later or else it will be overwritten with old contents.


Today's build adds simple integration with radio-browser.info (hidden by default / edit browse tree to enable).

[Arnold]

Reflection on present beta R2024-10-09:
All working fine.
The display of album art is indeed better then previous. It’s smooth and fast with display for all albums.

The list of control points is long (for me). Did not see this before, and not sure if this is important to keep an eye on.
The list is long because all old versions of the control point are listed. And I can’t edit this list?

[Spoon]

Restart your router, then all your devices, it means discovery is not working on your network.

[Spymaster]

Does anyone know if there's a hiccup with the newest version for Synology: R2024-09-23? I needed to restart my NAS today, to correct a hangup in PhotoStation indexing, and on both occasions Asset failed to start without a manual re-start, with "can't find media server on network" displayed on my smartphone's media player. It shows as "running" and everything looked fine, but only when I manually restarted Asset did everything snap into place on my devices.

[umgfoin]

Errors with MP3 transcoding have just been addressed.

As for the Foobar2000 mobile client transcoded radio-playback still fails with the above aac-streams (network error).
mp3-encoded stations play correctly, now.

If you use foobar2000 as client, it's generally not desirable to let Asset transcode in first place, but Asset must do this by default because many UPnP renderers can't deal with Internet radio streams properly.

Understand - makes sense.

To suppress transcoding, go to Asset settings, streaming options, set RADIO to "as is single". This will hand your foobar2000 the original radio link, causing foobar2000 playback to connect to the radio entirely bypassing Asset, get live track titles, etc.

Great - also works fine with client-specific settings:

=foobar2000-mobile
[ForceToSINGLE]
.RADIO

And I was always wondering, what that mysterious "RADIO"-fileext. might be...

++umgfoin.

[PeterP]

Thanks for the bug report.
Errors with MP3 transcoding have just been addressed.
If you use foobar2000 as client, it's generally not desirable to let Asset transcode in first place, but Asset must do this by default because many UPnP renderers can't deal with Internet radio streams properly.
To suppress transcoding, go to Asset settings, streaming options, set RADIO to "as is single". This will hand your foobar2000 the original radio link, causing foobar2000 playback to connect to the radio entirely bypassing Asset, get live track titles, etc.