Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - getmusicbee_account1111

Pages: 1 23
16
Bug Reports / Re: Tag Inspector messes up non-Latin metadata
« on: April 03, 2022, 11:28:47 PM »
Hiccup, thanks for the suggestions, I've already accomplished what I wanted:

Quote
Edit 4: I selected all tracks and inserted a space into the Mood tag (which none of the tracks had anything in so I wouldn't have lost any data) and I think that changed all files to ID3V3.2.
Thanks for all the help and hints folks.

I'm afraid trying to go from ascii-only to not-ascii-only wouldn't have been possible outside of MB because those question marks were actual question marks (the ascii character) instead of anything useful, and only MB knew what the real values were (since the transition from to ascii-only was done inside it, so I assume the real values were still stored in the database).

17
Bug Reports / Re: Tag Inspector messes up non-Latin metadata
« on: April 03, 2022, 03:00:51 AM »
Yes, MB displays them fine for me. I just copied them to Desktop and zipped them up.
Starting to think maybe my Windows is borked.

When you say none load with correct data do you mean question marks in place of non-Latin, or is all the metadata just incomprehensible garbage?

Also just to make sure: do you use unicode and utf8 interchangeably?

I dont think the ascii based encoders could possibly represent all characters in those character sets and the source files really need the id3 tags to be encoded with unicode or use id3v2.4 and encoded with utf8 before being imported to MB

Are the ones I sent you not id3?
I thought they were.
At least that's what the tag editor says.

Edit: well, regarding the "before being updated" part, I've used the Undo function a few times by now (to undo the question mark issue).
That reverts things back, right?

Edit 2: Oh is this what you were referring to with ascii only encoders?


Edit 3: Okay so I think that whatever was happening, that was the issue.
No idea when or why I chose that option but after reverting to "ID3v2.3" editing a borked music file (e.g. inserting a space in any tag) fixes the question marks.

The question is: Can this process be automated on all files?

Edit 4: I selected all tracks and inserted a space into the Mood tag (which none of the tracks had anything in so I wouldn't have lost any data) and I think that changed all files to ID3V3.2.
Thanks for all the help and hints folks.

18
Bug Reports / Re: Tag Inspector messes up non-Latin metadata
« on: April 03, 2022, 01:06:14 AM »
https://www.mediafire.com/file/axjf5t52txnhjcu/problem-files.zip/file
The zip has files in Ukrainian, Russian, Korean, Arabic and Japanese.

To clarify:
if the tags are not unicode encoded then then MB uses the default windows encoding page and not iso-8859-1 as per the id3 specs.
Do the specs say to use the Windows encoding or iso-8859-1?

I wonder why MB overrides the unchecked fields at all and if there's a way to make it write UTF-8 only.

19
Bug Reports / Re: Tag Inspector messes up non-Latin metadata
« on: April 02, 2022, 11:09:24 PM »
Then why not use the 'search and replace' feature?
(tools > tagging tools)

Oh thanks that does it  :D
Still wondering with the Inspector in particular not liking the encoding.

20
Bug Reports / Re: Tag Inspector messes up non-Latin metadata
« on: April 02, 2022, 11:05:13 PM »
Steven, but they display fine outside the Tag Inspector.
E.g. the Tag Editor has no problem showing non-Latin chars or editing them.

Also, why is it even changing their encoding if I'm only editing and ticking a single Genre checkmark?

21
Bug Reports / Re: Tag Inspector messes up non-Latin metadata
« on: April 02, 2022, 10:32:50 PM »
Two issues I can see with that method.
1. I don't really wanna resort to custom plugins.. I might end up having more problems that way.
2. If I'm understanding correctly, that method will replace all Trap with Wave.
I just want the files I selected to have Trap replaced with Wave.

22
Bug Reports / Re: Tag Inspector messes up non-Latin metadata
« on: April 02, 2022, 10:16:57 PM »
So you are using the Tag Inspector not on a single file, but on several files?
Yes, according to a forum post by one of the mods, it's the only way to bulk add/remove/edit a common genre.
E.g. how would you know for which track you are editing a specific tag when there are multiple variations displayed as in your example video?
That's what the checkmark is for.
Only the checkmarked fields are supposed to be touched in any way.
Instead of editing a genre tag (what seems to be what you are doing), perhaps use the '+' button to add a tag to all the files?
How would I then remove the genre from all selected files (Trap in this example)?
Besides, doing what you suggest results in the same issue of replacing non-Latin with question marks.
Doing anything other than closing the Tag Inspector results in the same issue.
Or if you intentionally want all selected files to have the exact same genre, delete all existing genre entries, save, and then add the desired genre and save that for all of them.
No, I just want to replace Trap with Wave (as an example).
Or at the very least first add Wave to all, then remove Trap from all.
I don't want to lose all the other different genres the tracks have.
I'm also confused that in your video, there are already tags containing lots of question marks.
Do you believe MusicBee did that, or were they there already?
I am also confused by that.
The weird part is they are displayed fine in the Edit menu (and everywhere else really).
Basically Tag inspector shows all non-Latin fields as question marks from the get-go without me even saving anything.
That leads me to believe that nothing was done per se, Tag Inspector just seems to be unable to render non-English and propagates this if the changes are saved (even if the fields were never touched)?

23
Bug Reports / Re: Tag Inspector messes up non-Latin metadata
« on: April 02, 2022, 09:39:52 PM »
The files were downloaded at different times from entirely different sources using entirely different methods.
Statistically, what are the chances that they are all messed up?
My guess is pretty low.


Your example video shows double entries for e.g. 'album' and 'publisher. The duplicates also display lots of question marks.

Again, in the video, I selected two files.
The album "InLovingMemory" is for Bones, and the album "?????" is for Prvrln.
The "double publisher" is two different tags, one for publisher, the other for the label.

24
Bug Reports / Re: Tag Inspector messes up non-Latin metadata
« on: April 02, 2022, 09:16:54 PM »
As I said, I have tried on multiple files and languages, not just this one, so it's not an issue with the file.

Not sure what you mean with double entries.
If you mean Encoder etc, it's mentioned twice because it's in Tag Inspector.
When you select multiple files in Tag Inspector, it shows the info for both unless the tag value is the same in both (which it isn't for Encoder).

25
Bug Reports / Tag Inspector messes up non-Latin metadata
« on: April 02, 2022, 08:59:28 PM »
Tag inspector seems to mess up non-Latin character encoding.
I wanted to edit a single genre in multiple tracks, and all the non-Latin fields turned into a bunch of question marks.
I have tried with Cyrillic, Japanese, Arabic, Korean metadata, all had the same behavior.

Demonstration: https://imgur.com/a/8SyxVIN

26
That's fair.
FWIW I thought it was a bug at first, as should be evident from the title.
I did search for the "discrepancy" stuff before posting and didn't find anything, but the separator question is indeed a different matter.

B.t.w., if you want to have a quick overview of all these artists you find 'hidden', use 'Artists'. E.g. as a column in track details, or as a field in the 'Track Information' panel.

Thanks!
That's helpful.
If only there were a way to show all the tracks, including the "hidden" ones, for every artist like in Music Explorer..
Edit: To answer my own question: it's possible using Column Browser!

27
Sure, I was being facetious.
I just wonder what the difference is between the ellipses and the semicolon method.
Is one more "proper" than the other?
Are both within the id3 specification?

28
Yes, you're right.
I didn't realize, but there's this little ellipses sign:

next to the Artist field, and when I click on it, sometimes there's extra stuff there.
And that's where that artist shows up in all of the extra 10 songs.
That's so sneaky!

Would you mind explaining how this differs from the "standard" way of including multiple artists using the semicolon?
Is this something in the id3 specification?

More importantly, can I get rid of it in bulk?
I don't see much use for it.
I can't even see the artists hidden under those ellipses at a glance, so all this does is add confusion.

29
Questions / Discrepancy between Library Statistics and Music Explorer
« on: March 27, 2022, 09:39:50 PM »
Library Statistics was showing that I have 23 tracks from an artist, so I went to check what they were in Music Explorer but only saw 13.
This made me wonder how Library Statistics are calculated.

Is simply mentioning an artist (say, in the file name or the Comment tag, not in the Artist, Album Artist or Composer tags) enough to increment the count?
If so, I don't think that should be the behavior.
The behavior should be that only if the artist is listed in one of the aforementioned three tags, should the track count be incremented.

For example, if the filename is red.mp3 and the Artist tag is Tyler, the Creator;Eminem,  the track count should only go up for Eminem and for Tyler, the Creator, while the track count for Red (the band) should remain unchanged.

30
Thanks that answers it!
Kinda off topic, but if the skip count is set higher than play count, say 80% and 50% respectively, would it count every track I skip in the 50-80% range as both skipped and played?

Pages: 1 23