Author Topic: Translated Error Logs  (Read 1346 times)

Mayibongwe

  • Sr. Member
  • ****
  • Posts: 1139
  • Heal The World
Saw an error report here that encouraged me to finally raise this question I've always had: https://getmusicbee.com/forum/index.php?topic=40177.msg217499#msg217499

More often than not, the only people who can dissect a MB error log are Steven and a handful of other seasoned (English speaking) users.
Which begs the question, is it really wise to translate the error log when other languages are selected in the MB preferences, since:

As far as I've noticed, the reporting user simply dumps the error log in that translated state and I would guess,
Steven and the other aforementioned forum members would then have to take the time to translate the log back into English? (or is this assumption incorrect?)

Just a thought...
The source code to any of my contributions is available on the same download link as the add-ons

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 9453
A good suggestion but I don't think translating it is necessary.

As long as the user posts the error log as text and not an image, Steven feeds the log i1nto his magic machine and it tells him what the error (possibly) is. Those of use who look at the log and offer a suggestion typically see the word "plugin" which then tells me it's probably an issue with a plugin, but nothing more specific than that.

Steven's magic machine can read the "gibberish" generated in the error log.
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

boroda

  • Hero Member
  • *****
  • Posts: 4748
btw, Steven, if you read this topic, how do you decipher all this abracadabra from .net error messages? it's interesting to me to be able to read error messages generated by my plugins and reported by users. i haven't found any information on the internet about these base64 error texts.

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 9453
@boroda...

Steven explained the process for reading the error logs to me once. I'll shift through my PMs (apparently there's no way to search through them) and if I find it, I'll post it. But I think you'd have better luck waiting for Steven to reply.
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34427
There are different parts to the error dump. The first line is the windows/.net error which can be translated if not already in english.
Then for the call stack dump, any parts that relates to a plugin function will be human readable, and any parts relates to musicbee functions will be encrypted/gibberish and i am the only one who can decode that

boroda

  • Hero Member
  • *****
  • Posts: 4748
so, they are regular base64 strings? i've tried to decode tag tools plugin error messages (posted by the user), but base64 decoding gave me nothing.

ok, i'll give it another try next time.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34427
so, they are regular base64 strings?
no - the musicbee parts of the call stack are encrypted and I am the only one who can decrypt it