Earliest Release Date v4.4.0 (2016-02-19)

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Earliest Release Date v4.4.0 (2016-02-19)

Re: Earliest Release Date v4.4.0 (2016-02-19)

by Robb » Sun Jul 01, 2018 1:40 pm

Dear wxdude,
I just realised I've been using MediaMonkey for over 14 years and when WMP moved to version 12 I ditched it all together and have been dedicated to MediaMonkey ever since.

Earliest Release Date has always been an integral part of my MM setup and as its free I've taken it for granted and never thanked anyone involved in the development and maintenance of the plug-in.

Before most people even knew what metadata was I learned how to rip and tag my music, I remember my first hard-drive was 74gb.. 74!! at the time I ripped all my CDs at 190kbps, when the norm was 128 and tagged artist, track, genre and of course date. Date was so important to me, my memories are tied to music throughout my life and the date of the tracks are anchor points for me to remember when and where I was in my life.
I use to have to google each track individually and then try and find a link with a release date. Earliest Release was a gift from heaven, it was almost like witch craft, to tag 110 tracks at once and come back with not only the year but sometimes the month and day as well was genius.

I have to thank you on behalf of all the obsessive audio-files like myself for keeping this project going for so long and for no financial gain, if there's some way I could send you some money so you can at least have a beer or coffee and doughnut on me then please let me know how to as I am so grateful for the work you have done.

I note Discogs is limiting the amount of searches you can carry out in a certain time period now (probably because Earliest Date worked so well, I can imagine all the queries acting like a DDoS attack) would it be possible to stagger the queries so as to conform with Discogs new policy?

Once again thanks for all your hard work maintaining this project! -Robb

Re: Earliest Release Date v4.4.0 (2016-02-19)

by M.Moeritz » Thu Jun 28, 2018 2:28 pm

Is the extension already for MM5? Or is there another way to automatically determine the date?

Re: Earliest Release Date v4.4.0 (2016-02-19)

by Peke » Mon May 07, 2018 9:34 pm

Lowlander wrote:As MediaMonkey becomes less platform dependent I presume that internet access will also be done by MediaMonkey instead of relying in a Windows component.
To confirm MM5 uses Chromium engine.

Re: Earliest Release Date v4.4.0 (2016-02-19)

by cryptus939 » Mon May 07, 2018 8:29 pm

This plugin doesn't work for me at all now. Every time I run it on a song it returns the error, "Error #9 - Microsoft VBScript runtime error | Subscript out of range: ' UBound' | File: "C:\Users\<name>\Appdata\Mediamonkey\Roaming\Scripts\Auto\EarliestDate.vbs", Line: 1522, Column: 1". It's a shame, as this saved me an awful lot of time when I did the initial run through on my library and has proven useful since.

Re: Earliest Release Date v4.4.0 (2016-02-19)

by Lowlander » Sat Dec 09, 2017 2:53 pm

No, this comes from MediaMonkey and it uses a core Windows component. IE is still part of Windows 10. As MediaMonkey becomes less platform dependent I presume that internet access will also be done by MediaMonkey instead of relying in a Windows component.

Re: Earliest Release Date v4.4.0 (2016-02-19)

by M.Moeritz » Sat Dec 09, 2017 9:11 am

It is clear that I do not have the Internet Explorer on my system. Since this will surely be the case with many others in the future because Edge will replace the Iexplorer, it should not be a problem to write the plugin so that the standard browser is taken and not explicitly the iexplorer. Or am I wrong?

Re: Earliest Release Date v4.4.0 (2016-02-19)

by Peke » Fri Dec 08, 2017 10:34 pm

That is strange you should have it See https://answers.microsoft.com/en-us/win ... 2e8?auth=1

Re: Earliest Release Date v4.4.0 (2016-02-19)

by M.Moeritz » Mon Dec 04, 2017 12:29 pm

Hello, I also tested, does not work. I searched for the iexplore.exe on my PC and only found it at the places shown in the picture. I would say my PC has no Internet Explorer anymore. And now?

https://cloud.xn--mritz-jua.com/index.p ... IR36ofVh90

Re: Earliest Release Date v4.4.0 (2016-02-19)

by Peke » Sun Oct 22, 2017 7:39 pm

Open Edge and any Web page then in "..." menu you should have Open in Internet explorer.

FYI it is not IE.EXE but iexplorer.exe ("C:\Program Files\Internet Explorer\iexplore.exe")

Re: Earliest Release Date v4.4.0 (2016-02-19)

by M.Moeritz » Sun Oct 22, 2017 11:26 am

Hi, I have Win 10 Pro. Version 1703 Realease 15063.674. I Search for IE.exe at C:\ and don´t find it :(

Re: Earliest Release Date v4.4.0 (2016-02-19)

by Peke » Fri Oct 20, 2017 6:53 pm

Hi,
in your case ActiveX components:" InternetExplorer.Application " means that IE HTML rendering engine is not available. I have Win 10 and internet explorer is still installed. Check what what version of windows you have as some do not contain full IE.

Re: Earliest Release Date v4.4.0 (2016-02-19)

by M.Moeritz » Thu Oct 19, 2017 6:36 am

Hello, I have the following problem. I deleted the Discogs Keys and reinstalled Earliest Date. Then comes the query for the login of the database, which I confirm with Yes. Then comes

"Error # 429 - Runtime error in Microsoft VB script. Can not create ActiveX components:" InternetExplorer.Application "

I guess the problem because the Internetexplorer in Win10 was replaced by Edge, would not it be better to call the standard browser or ask for the standard browser?

Or how can I replace in the script the "InternetExplorer.Application" by Chrome / Firefox, I have no knowledge about VB

Re: Earliest Release Date v4.4.0 (2016-02-19)

by wxdude » Tue Apr 25, 2017 7:59 pm

cryptus939 wrote:I'm now getting a new error every few songs or so:

"Error #13 - Microsoft VBScript runtime error
Type mismatch: 'ojsonVersions(...)'
File "C:\etcetc\EarliestDate.vbs", Line: 1005, Column: 8"

Running Mediamonkey 4.1.15.1828 Pro on Windows 10
This is most likely due to the API rate limit change at Discogs. They reduced the limit to one API call per second from 3 on April 24th...the script doesn't handle the change gracefully however....

Need time to update the script but that might take some awhile....

Re: Earliest Release Date v4.4.0 (2016-02-19)

by cryptus939 » Tue Apr 25, 2017 6:42 pm

I'm now getting a new error every few songs or so:

"Error #13 - Microsoft VBScript runtime error
Type mismatch: 'ojsonVersions(...)'
File "C:\etcetc\EarliestDate.vbs", Line: 1005, Column: 8"

Running Mediamonkey 4.1.15.1828 Pro on Windows 10

Re: Earliest Release Date v4.4.0 (2016-02-19)

by jcfogerty » Sun Nov 06, 2016 9:22 am

MPG wrote:The solution, as provided earlier is:
It appears that in the MusicBrainz transition to HTTPS, the domain http://www.musicbrainz.org no longer points to musicbrainz.org.

For a quick fix try editing lines 798 and 1479 from http://www.musicbrainz.org to simply musicbrainz.org.

So all I did was open EarliestDate.vbs located in C:\User\<Name>\AppData\Roaming\MediaMonkey\Scripts\Auto and changed the URL to:
http://musicbrainz.org

HTH's
MPG
Thanks so much MPG! That solution worked for me perfectly (Win 10, MM4 Pro).

Top