Obscure Bug: whitespace at end of song title duplicates song listing
Found a weird, annoying, but low priority bug: I recently downloaded an album from Amazon and added it to my OneDrive music. When I imported it into Cloud Player two of the songs were duplicated for some reason. This means that when I shuffle the library it shuffles these songs in twice and plays these songs twice in a row when playing the album in order. I eventually discovered that these two songs had two space characters in the song title in the metadata of the MP3 on OneDrive. Removing these two space characters in each file's metadata fixed the issue. No idea if anyone can replicate this, but it might point to a worse bug about how Cloud Player handles whitespace at the end of metadata strings, IDK.
-
Official comment
Hello,
Thanks for the report. I will try to reproduce this problem on my test accounts.
Was this on the regular version of OneDrive or OneDrive for Business?
For regular OneDrive, CloudPlayer actually uses the Microsoft metadata extractor on the server side so you might be triggering a bug in the Microsoft code.
Also, do you recall which album this was? Thanks!
-
Regular OneDrive. Also I forgot to mention: it only happened when I tried to download the files for offline use. When I do this it has the downloading notification like normal, but after the download is finished a second notification pops up saying "importing file ..." This notification stays up as long as Cloudplayer is running in the background. This is all on my phone which is a Motorola Z Play.
The album is this: https://www.amazon.com/Sacrament-Sin-Powerwolf/dp/B07D24ZZF6/ref=gp_aw_ybh_a_3?_encoding=UTF8&psc=1&refRID=NYSRV09WYM5M0DSGX4YQ
And the two songs are "Killers With The Cross" and "Fist By Fist (Sacralize Or Strike)" I have no idea why these specific songs have metadata with space characters in the song title.
0 -
Hello,
Thanks for the information. I just tried to reproduce the problem by editing the metadata on test files but I wasn't able to trigger that behavior so it might only be caused by specific metadata information that I wasn't able to replicate by editing.
But I will ask the QA/Dev team to investigate further.
0
Please sign in to leave a comment.
Comments
3 comments