track & artwork mismatch with latest asset version

[Spoon]

Asset was fully released last week on all platforms.

https://forum.dbpoweramp.com/forum/read-only/news-updates-read-only/44223-asset-version-changes#post328037

[pjohann]

Thanks for the problem report.
New version of Asset UPnP reverts this change, embedded covers are again preferred over external.

Hi PeterP, - thx you're right this new Beta-Version solved the/my problem! But unfortunately its available for QNAP, etc. only and not for Windows. Any plans when the respective version will be available for Win-PC as well?!

[pjohann]

If there is no solution on short notice, then I'd prefer to revert back the previous Asset version (probably the 2023’rd version) for both platforms: Windows 10 and QNAP alike. How could I get access to these two previous installer files?

[pjohann]

I'd attached three screen shots (pls. see earlier post from Sept. 04, 2024, 06:32 PM) to make the problem clearer. One shows the file structure of my media HDD, high lightening for instance the folder associated with the playlist ‘Jazz 111’, then there is a screen shot of my mobile phone running BubbleUPnP showing also the contents of playlist ‘Jazz 111’ how Bubble presents it. One can clearly see that the artwork of John Coltran’s CD ‘Lush Life’ is falsely attached to all the music files. As an example I#d also attached the screen shot of the tagging label of the title track ‘Bird Cry’ of Alon Faber as proof that it’s correctly tagged and Asset - probably while indexing - is replacing Alon Faber’s cover artwork with Coltrane’s artwork.

Pls. kindly advice on how to proceede ...

[pjohann]

... and, again folks: all those issues were not there up to release R2023-05-15

[pjohann]

Thanks for the problem report.
New version of Asset UPnP reverts this change, embedded covers are again preferred over external.

... thx PeterP for the recommendation! I’ve downloaded and installed the beta version as hinted to by you at:
_____________________________________
Asset UPnP R2024 beta.
February 08, 2024, 01:26 PM

Current version:
R2024-08-30 (beta)

Download links:
Mac | QNAP | Synology | Linux x86 32-bit | Linux x86 64-bit | Linux ARM 32-bit | Linux ARM 64-bit

Windows builds are only available for stable releases.
_______________________________________
Because the Win version seems to be not yet available I’ve taken the QNAP version. But funnily after installation, starting Asset UPnP from the QNAP AppCenter it shows:
__________________________________________________ __
Library Contains 16611 Tracks, 3249 Albums
Version: R2024-08-30 beta [Linux-ARM32]
Functionality: Premium Registered
Update to R2024-8-7
Running as user: root
Configuration data: /share/CACHEDEV1_DATA/.qpkg/Asset/data/.dBpoweramp/
___________________________________________
i.e. Linux-ARM32 not Windows!
Anyway after performing a full “Restart Asset UPnP” my hopes for improvement were disappointed. The problem with pixelwise downgraded and wrongly allocated artworks persisted.
Furthermore – to be on the save side – I’ve also tried out a different control point SW, i.e. “Yamaha MusicCast” and the problem turned out to be exactly the same; so, it cannot be a problem with the control point SW, MusicCast or BubbleUPnP likewise! The false allocation must happen during the build-up of the database when Restart Asset or performing a Rescan.
Hoping that one of you experts will provide further help in solving this effing nuisance problem I’ve attached some screenshots demonstrating those annoying behavior …

Pls. kindly help!

[Spoon]

Asset does not assign from the internet, it uses only what is there, check for hidden files if on Windows.

[pjohann]

... interestingly further: some of the misallocated covers are pixelwise downgraded, though the enbedded covers are highly pixeled. This phenomena indicates to me, that Asset is assigning new covers from/via the internet ...

[pjohann]

This may have something to do with the problem you are seeing. But to be clear, embedded covers in the music file are not the same as having a separate cover.jpg file located in the same directory. If you only use embedded covers, these should always stay associated with the song. Separate image files regardless of your naming structure run the risk of having issues especially when there is more than one image in a single folder.

... also aware of this fact GBrown, but as mentioned above I'm using Asset already for 10 years, following all the upgrades, and never have run into this problem. Addtionall & funnily: The current version of asset will be mixing up covers also if there aren't any *.jpg files in the folder with tracks from diffrent CDs.

[pjohann]

Is there a reason you're not using the standard approach to create playlists, that of m3u/m3u8? With this approach you wouldn't need to duplicate tracks (assuming they're already part of your indexed collection) and the artwork will be inherited from the source album.

A m3u/m3u8 playlist is just a text file containing the locations of the tracks you want included e.g.

./AlbumArtist1/Album1/01.flac
./AlbumArtist1/Album2/01.flac
./AlbumArtist2/Album5/07.flac

... no Simbun, sorry for me being not clear enough on this! And yeah, I'm aware of the standard approach to create playlists, via m3u/m3u8, indeed I use foobar therefor. But for conveniance reasons I additionally keep the files associated with these playlist in a seperate folder, just for in case the corresponding *.m3u file gets lost. I also don't keep the files duplicated, but in the original 'CD-folder' is just a shortcut file kept

[pjohann]

Thanks for the problem report.
New version of Asset UPnP reverts this change, embedded covers are again preferred over external.

Hi PeterP, thx, this sounds promising. Does it mean, that I have to download Asset again?! and is it already available from the home page? - Pls. kindly confirm ...

Anyway, I'm using Asset already for 10 years, following all the upgrades, and never have had to face this problem

[simbun]

Thanks for the problem report.
New version of Asset UPnP reverts this change, embedded covers are again preferred over external.

Are the artwork naming conventions and priority documented anywhere e.g. embedded > {folder.jpg|cover.jpg} e.t.c.

[PeterP]

Thanks for the problem report.
New version of Asset UPnP reverts this change, embedded covers are again preferred over external.

[GBrown]

...I keep within most of the folders the *.jpg's assosiated with the albums. And - as you again rightly guessed - the covers (*.jpg's) are all embedded within each of the files; ...

This may have something to do with the problem you are seeing. But to be clear, embedded covers in the music file are not the same as having a separate cover.jpg file located in the same directory. If you only use embedded covers, these should always stay associated with the song. Separate image files regardless of your naming structure run the risk of having issues especially when there is more than one image in a single folder.

[simbun]

... well yes, they are structured in the same fashion on my HDD as you assumed, - this especially for directories which are dedicated to one CD/album only!
Then I have for each playlist a dedicated directory filled with the repective music files (from various albums), - and yes, I keep within most of the folders the *.jpg's assosiated with the albums.

Is there a reason you're not using the standard approach to create playlists, that of m3u/m3u8? With this approach you wouldn't need to duplicate tracks (assuming they're already part of your indexed collection) and the artwork will be inherited from the source album.

A m3u/m3u8 playlist is just a text file containing the locations of the tracks you want included e.g.

./AlbumArtist1/Album1/01.flac
./AlbumArtist1/Album2/01.flac
./AlbumArtist2/Album5/07.flac