Description:This MediaMonkey extension allows you to submit new discs to the freedb database using your MediaMonkey album and song data. It will NOT allow you to update or revise discs that already exist on freedb.

Requirements:MediaMonkey 4+

Installation:Double click the freedbSubmitter1.01.mmip file.

If you prefer to install manually, follow these steps:

- Open freedbSubmitter1.01.mmip in a Zip utility - Copy the freedbSubmitter folder to C:\Users\<username>\AppData\Roaming\MediaMonkey\Scripts\ - Add the following entry to the Scripts.ini in the Scripts folder:

[freedbSubmitter]Filename=freedbSubmitter\freedbSubmitter.vbsProcname=launchSubmitterOrder=125DisplayName=Submit to freedbDescription=Allows you to submit new discs to freedb from MediaMonkeyLanguage=VBScriptScriptType=0

Configuration:The extension allows you the options to preview your entry before submitting, and to include extended data from your Album Comment and Song Comment fields. You can configure default values for these options by opening the freedbSubmitter.hta file in a text editor and changing the values of the viewSubmitDefault and sendExtDefault variables.

It's also a good idea to ensure that you have a valid email address entered into MediaMonkey's User Name and User Domain fields under Options>Network (Proxy and Freedb)>Freedb Settings.

Usage:Follow these steps to submit your disc with freedbSubmitter:

- Expand the Location node in the MM Music Tree - Select the CD you would like to submit to freedb (no disc needs to be in the CD drive) - Ensure that the Song List is sorted by ascending Track Number - Open freedbSubmitter from the Tools>Scripts menu - In the freedbSubmitter window, click the Query freedb button - The freedb query results will be displayed - If your disc does not exist on freedb, you will see a freedb Category dropdown list and a Submit button - Select a category for your disc (the category doesn't need to match your MM genre) - If you would like to preview your submission, check the Preview Submission checkbox - If you would like to include extended disc and track data with your submission, check the Submit Extended Data checkbox (Extended disc data is obtained from your Album Comments field, while extended track data is obtained from your Song Comment fields) - Click the Submit button - The submission results will be displayed - If you see a message that a DiscID collision (http://www.freedb.org/en/faq.3.html#27) has occurred, select a different freedb category and click Submit again (once again, the category doesn't need to match your MM genre)

If your submission is successful, your entry will appear in the freedb database after about one to six hours.

Even if you receive a message that your submission was successful, that doesn't necessarily mean it was accepted. The server does some post-submission checks, and if it finds a problem, it can still reject your entry. If that happens, you are supposed to receive an email at the address you provided that explains the reason. That hasn't been my experience. Except for some early failures while I was still working out the coding, all of my submissions using this extension have been successful.

History Version:1.00 2016-08-14 initial release1.01 2016-08-17 changed install/uninstall configuration to eliminate the requirement to run as admin

Additional Information:You may be wondering why this extension only permits you to submit discs that don't already exist on freedb, but doesn't permit you to update already existing discs.

The reason is to avoid any unintentional damage to existing freedb data. I recently discovered that MediaMonkey does not seem to download and save extended disc data from freedb. For more information, see my earlier post:

If that's the case (and please correct me if I'm wrong), it would be possible for a user to get album info from freedb, clean up the data and maybe make some useful additions. Then being a good Samaritan, the user would submit the cleaned up data back to freedb so that others would benefit from the user's improvements and enhancements. The revised submission would overwrite the old, but if the original submission included extended disc data, that data would be lost because the MediaMonkey user would have never received it and his or her submission would contain no data in the disc extended data field.

I would prefer to err on the side of caution by not allowing this extension to make revisions. Part of my rational is that I think it's more important to add new discs to the freedb database than it is revise existing data. It's not an ideal situation, but at least now MediaMonkey users can finally contribute to the freedb community.

Hey, I really think it might be useful to "update" the freedb sometimes...i'm a avid hardcore music user and have notice that the freedb is sometimes wrong or useless and i'm having to correct data that is already on freedb...so i would love to correct this incorrect data or make additional usage metdata song data available to anyone that might need it in the future. Please advise or update this app if you can ...it only adds or contributes to the date already exitstin on freedb, why not? Thanks for the contribution and addition to MM..Cheers!

Thanks for sharing your thoughts, and apologies for my late response. I just today (7 May 2017) received an email informing me there was a new post in this thread.

I totally agree with your view on updating and improving freedb data. and I did seriously consider including an update capability. However I'm still concerned about MM's limitations retrieving all data from freedb. I detailed those concerns in the "Additional Information" section of my original post, but to recap here, MM does not appear to download and save extended data from freedb (or at least for me it doesn't). Given that, a MM revision to an existing freedb entry would result in the loss of the extended data. Some freedb entries include very extensive and useful details in their disc and track extended data fields. It would be a pity to lose that data, and a disservice to the original contributor.

Even if MM v5 included the capability to save extended data, and I added a revision capability to the extension, there is still the danger of all the existing MM v4 records to potentially wipe out freedb extended data in revised entries.

I think we are on the same page regarding cleaning up freedb, so I hope you'll understand my reasoning. But I'm also interested in extending the usefulness of MM and freedb, so if you have any thoughts on how to do that without wreaking further havoc on freedb data, please let me know.

Configuration:The extension allows you the options to preview your entry before submitting, and to include extended data from your Album Comment and Song Comment fields. You can configure default values for these options by opening the freedbSubmitter.hta file in a text editor and changing the values of the viewSubmitDefault and sendExtDefault variables.

Not a stupid question at all, and definitely nothing to be sorry about. I should have noted the possible values in the the configuration with a comment instead of assuming users would intuit the options.

You are correct The options for both settings are true and false (not case-sensitive, and no quotes).