Thanks @anton , I’m gonna check it tomorrow and I’ll let you know how it works 
PS: btw, it’s necesary to run both scripts everytime is needed to?
Hey, good day/night
With latest changes that I made, you just need to run the setup once, and then just use run every time that you need to use the proxy.
Previous issues were tied to how one of the components was being configured and used in setup and run (respectively), so recent changes were aimed to fix that
Nonetheless, please let me know if you have any issues.
Regards.
Hi @anton, tomorrow I’ll be testing the scripts, I’ve been dealing with a massive crash and data loss in my computer (corrupted HDD 
). Best regards!
Oh no! That’s awful mate 
I’m so sorry, and hope that you can recover most, if not all of lost data.
1 Like
Luckily, I could fully recover all my data, only the OS partition was damaged so it was a close call. Anyway, I’ll have to buy an SSD to upgrade my 10-year HDD hahaha
I tried the new script, but it gave me this error:
I tried both with VPN and without VPN, and the result it was the same. Any clue?
Best regards.
A very close one indeed… I know that you’ve upgraded your old HDD (and almost as old as a couple that I have since at least 2007 / 2012 lol), but maybe you would like to consider get a 2nd HDD/SSD for your data (or backup). That strategy has saved me a couple of times heh
Ok, let’s go to the topic at hand
QQ: When running the proxy does it show a message that says:
Proxy MA with Playwright available at http://localhost:5000
or
Success! Preload completed in XXX seconds (XXX can be any number)?
I saw that message a couple of times when I ran MP3Tag and proxy wasn’t working (by whatever reason).
Hi again! Well, I made my tests. Using the cmd file the script finally worked, for some reason the python file it didn’t for me, but anyway:
“Search by band”, “Search by album” and “Search band + album” scripts gave this error:
If this was reported earlier by you, my bad, it didn’t know.
In the other hand, the remaining scripts are working smooth and fine.
For me, this is a banger!
PS: is it a way for “customize” the script like the old one using the "set” command like?
Hi,
Let me go issue by issue:
These are the “proxy” versions (that have “(Proxy)” on their name), or the regular ones?
Could you please expand more about these? I am not quite following you at the moment (I blame how my day was at office lol).
Ah, the proxy version gave that error. At least for me, only 2 scripts are working.
The second issue, is just a recalling with a function present in the code of the older scripts, when you write SET “field” to let out from the query that field. But I’ve digging in the code, and well, the same result it can achieved with deleting the “unwanted” fields for the user.
The third issue is the link in the lower left aside with the “Utils” button: in the older script, that link redirects directly into the page album in MA; in the new script, it shows a page like the one I sent early in the screenshot.
That’s for the moment.
Ah, one more thing, the new script it doesn’t call a list with all the versions of the release, like the old “Search by band + album (advanced)” and “Search by band + album (advanced by format)”, maybe in a future release it can be added?
That’s for now, if I find something else, I’ll report it. And congratulations again, you’ve made a great work with this upgraded version of an nearly 20-years script 
Weird, I’ll check if not today, before Saturday (long weekend for me and I’ll be offline).
Maybe I am wrong, but I believe that maybe you’re thinking on “outputto" and "sayrest" functions, as "SET" is/was only used while getting the Disc Number. Those are also used on Proxy versions, although logic if quite different with code in-between those two (thanks to JSON).
Ok, you got me with that one lol
Being honest, in all those years using MP3Tag (you can see when my first post here was, and go back a year or so lol) I’ve never noticed, nor used that link 
But yeah, as far as I can tell, that link uses the source from where the data is coming from, and considering that data is coming from Proxy, that’s what is being shown.
Honestly, I don’t know if that can be changed/configured, but I could take a look at it.
That’s something that I’ve in my mind/my goals since the beginning, but I want to make sure that current implementation works as expected before going into that task - specially since advanced search works a little bit different than the regular search.
Moreover, next weeks will be very annoying due to “end of year” activities on my workplace, as well holidays and what not, so I can’t compromise with having those scripts done… Yet… Nonetheless, once I figure out what’s going on with your case I’ll take a look at “advanced search” scripts whenever I have a chance.
Thank you for the kind words, although I like to think that it has been a team effort (starting with dano, and including all of you) nonetheless, I appreciate your words 
2 Likes