Another update ready for install now that fixes a few bugs, some new some old.

fix bug that could result in the script waiting for a very long time to proceed with searches if the user switched from MB to Discogs. There was no way to end the script either which made it worse.

fix long standing bug where, if a user made a new selection while the script was running, the dates would be added/changed on the new selection incorrectly (I'm surprised no-one noticed before, or else every one's work flow is the same as mine!)

API throttling was too aggressive resulting in long waits, so made a small tweak

Another update ready for install now that fixes a few bugs, some new some old.

[list][*]fix bug that could result in the script waiting for a [u]very[/u] long time to proceed with searches if the user switched from MB to Discogs. There was no way to end the script either which made it worse.[*]fix long standing bug where, if a user made a new selection while the script was running, the dates would be added/changed on the new selection incorrectly (I'm surprised no-one noticed before, or else every one's work flow is the same as mine!)[*]API throttling was too aggressive resulting in long waits, so made a small tweak[*]Fixed an error if Discogs returned an invalid master release[/list]

Robb
Thanks for the kind words.
Discogs does limit the number of API requests. The script limited the requests to 3/second but Discogs changed the limit shortly after I implemented that rate to 60/minute for authorized requests and 25/minute for unauthorized requests. As MM5 was in alpha I had not bothered to update this script, just let Discogs throttle you, and thought I'd update for MM5.

I haven't even started working on a MM5 version, but, I did start working on using the DiscogsAuth flow instead of oAuth for authentication, and will release this update to the script for MM4.

Going forward only DiscogsAuth will be supported for the Earliest Release Date script. This will be true for MM5 if I ever do update the script for that version. Also at some point in the future I will discontinue the PHP server that processes the oAuth requests presently.

For DiscogsAuth to work you must get a personal access token from Discogs.

Login to Discogs and go to "Settings" --> "Developer" --> copy the personal access token and paste into the Earliest Date Options page "Personal Access Token" edit box. If there is no token present, generate one.

Using your personal access token will provide you with the 60 requests/minute rate on Discogs.

Use response headers from API results to throttle connections. This should be future proof if the API limits change again. Script runs at full speed until only 5 API requests remain. At that point the API requests will start to slow down but the script will continue to run.

Add support for debug logs. Default is off

Move discogs clear keys buttons to options page

other bug fixes

To Do:

Develop MM5 Version

Current Discogs search query with the 'Track' parameter fails with track names with unicode characters and/or some punctuation marks (exclamation mark for example). This is a Discogs API bug. If some searches fail due to this bug, switch to MusicBrainz for those tracks.

RobbThanks for the kind words.Discogs does limit the number of API requests. The script limited the requests to 3/second but Discogs changed the limit shortly after I implemented that rate to 60/minute for authorized requests and 25/minute for unauthorized requests. As MM5 was in alpha I had not bothered to update this script, just let Discogs throttle you, and thought I'd update for MM5.

I haven't even started working on a MM5 version, but, I did start working on using the DiscogsAuth flow instead of oAuth for authentication, and will release this update to the script for MM4.

Going forward only DiscogsAuth will be supported for the Earliest Release Date script. This will be true for MM5 if I ever do update the script for that version. Also at some point in the future I will discontinue the PHP server that processes the oAuth requests presently.

For DiscogsAuth to work you must get a personal access token from Discogs.

Login to Discogs and go to "Settings" --> "Developer" --> copy the personal access token and paste into the Earliest Date Options page "Personal Access Token" edit box. If there is no token present, generate one.

Using your personal access token will provide you with the 60 requests/minute rate on Discogs.

Whats New:[list=1][*]Add Support for DiscogsAuth[*]Use response headers from API results to throttle connections. This should be future proof if the API limits change again. Script runs at full speed until only 5 API requests remain. At that point the API requests will start to slow down but the script will continue to run.[*]Add support for debug logs. Default is off[*]Move discogs clear keys buttons to options page[*]other bug fixes[/list]

To Do:[list=1][*]Develop MM5 Version[*]Current Discogs search query with the 'Track' parameter fails with track names with unicode characters and/or some punctuation marks (exclamation mark for example). This is a Discogs API bug. If some searches fail due to this bug, switch to MusicBrainz for those tracks. [/list]

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

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

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.

[quote="Lowlander"]As MediaMonkey becomes less platform dependent I presume that internet access will also be done by MediaMonkey instead of relying in a Windows component.[/quote]To confirm MM5 uses Chromium engine.

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.

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.

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.

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.

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?

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?

That is strange you should have it See https://answers.microsoft.com/en-us/windows/forum/windows_10-networking-winpc/how-to-locate-and-open-internet-explorer-in/4b067f8b-a0dc-4fba-9e63-00fb14ea82e8?auth=1

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.

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.