Re: MonkeyMatch 0.5.56 - Find & Fix Similar Spelling (7/7/13
Posted: Fri Aug 09, 2013 1:07 pm
It seems to fix both errors. I have to try out more, now.Scottes wrote:Please give this version a try.
![:D](./images/smilies/icon_biggrin.gif)
The Music Manager for Serious Collectors
https://forum.mediamonkey.com/
It seems to fix both errors. I have to try out more, now.Scottes wrote:Please give this version a try.
Excellent. That's good to hear.hintergrundrauschen wrote:It seems to fix both errors. I have to try out more, now.Scottes wrote:Please give this version a try.
Each Match Pair is saved whenever you hit Save Changes, or if you click Next Match Group *and* you have Auto-Save Changes enabled. (Click on Options, and check the lower-left corner.) So Save Changes will be disabled until you make a change to any of the names currently displayed in the list.hintergrundrauschen wrote:I cannot seem to Save Changes, since the button is inactive. I have about 240 match pairs for artists and wanted to save after changing only a few of them.
I set the "preferred" entry of the two variants, i.e. making the field become green.Scottes wrote:So Save Changes will be disabled until you make a change to any of the names currently displayed in the list.
That doesn't make any changes. Once you set the Preferred choice, double-click on any names that you want to change to the Preferred name. The name you double-clicked will be changed, it will turn red, and the Save Changes button will be enabled.hintergrundrauschen wrote:I set the "preferred" entry of the two variants, i.e. making the field become green.
In other words, RTFM.Scottes wrote:Once you set the Preferred choice, double-click on any names that you want to change to the Preferred name.
No, not at all. I understand it's not the most intuitive program to use because I wanted to make changes with the least possible number of clicks or keystrokes. MonkeyMatch's UI is not standard at all, but it requires the absolute minimum number of clicks/keystrokes.hintergrundrauschen wrote:In other words, RTFM.
Much of the time is spent doing queries against the database to find the songs to change. Then the database is changed, one song at a time effectively. If MM is configured to update tags automatically then it will do so as soon as each song's data is changed.hintergrundrauschen wrote:For large quantities of songs to change, it is quite time consuming due to the slow speed of file tagging. It seems to be able to tag only about one file every 1-2 seconds. MM itself is faster.
Yes, I could store changes to be made, then make them all at once. So after you're done making all the changes in MonkeyMatch, you'd click another button that would actually apply all the changes all at once. This really wouldn't save time overall, but would bunch it all at the end when you could switch to another program and go do something else while the changes were being made. The time you spent interacting with MonkeyMatch would be much shorter in the long run, since it would save you a few seconds many times, then apply all those seconds at the end.hintergrundrauschen wrote:Then how about an option to flag changes only (in MonkeyMatch memory) and then batch change everything after I hit a corresponding button. That way I would be able to go through my 200 match pairs quickly and then leave the program to make the changes in background.
I still have to find some time to make it multi-threaded. That will absolutely help with the freezing at times, but there are "freezes" where it's just waiting for MM to finish changing things. Multi-threading could allow it to wait in the background, keeping the UI fast and responsive.hintergrundrauschen wrote:Is this a planned limit to be able to use MM without freezing?
I like this idea, and think it would be nice info to display. But I'm almost positive that I'd have to run a query for every such number, and that takes time. Right now I run one query that gets every unique name (Artist, Album Name or Song Title) in the MM database. For each name, I'd have to run another query that gets the number of songs that match each name. These queries *might* be quick, but there *will* be times when they're not. A quick test on my machine took .13 seconds to count the number of songs I have by an artist. Any artist - each count takes the same amount of time, regardless of the number of songs or even if I give a bogus name. For a database with 140,000 songs, this took .37 seconds. With 200 match pairs, this would add over 2 minutes to the processing time. To me, this seems like a lot of time to spend on such info. Would you think it's worthwhile?hintergrundrauschen wrote:Also, how about displaying the number of corresponding songs/tag fields for each of the match pair entries, i.e.
[Preferred] Bandname [12]
[Preferred] Badname [01]
Code: Select all
************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {148F7BB6-4943-4C53-8E30-0F9115D30283} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache)
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean skipCheckThis, Boolean fillCache)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at MonkeyMatch.Form1.GetDataSet(Int32 DataSetType)
at MonkeyMatch.Form1.btnFindMatches_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1008 (RTMGDR.030319-1000)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MonkeyMatch
Assembly Version: 0.5.4936.35718
Win32 Version: 0.5.4936.35718
CodeBase: file:///C:/Users/Adam%20%26%20Lisa/AppData/Local/Apps/2.0/NYJ950VH.ARD/KOCDLD8X.1YP/monk..tion_1f8636ce9401f4ba_0000.0005_338ca98607b50e92/MonkeyMatch.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1002 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1001 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1001 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.237 (RTMGDR.030319-2300)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1015 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1015 (RTMGDR.030319-1000)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
Microsoft.CSharp
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
MonkeyMatch uses COM to access the MediaMonkey database, so it should work as long as MediaMonkey is running (and it will start MM if it's not running). It should not matter where the database is. If MediaMonkey can access the database properly, then MonkeyMatch will.adamg wrote:I don't have a clue if monkeymatch even works that way though (if it searches ONLY for the DB file)
found at http://www.mediamonkey.com/forum/viewto ... =2&t=73213Postby Peke ยป August 4th, 2013, 8:21 am
External Programs needs to have COM registered locally even Main installation is on NAS.
"MediaMonkey Portable do not support some plugins/Scripts that depend on MediaMonkey COM Server which is due the windows demand that each COM Server needs to be registered/saved in Windows Registry and Admin Access.
To enable MediaMonkey COM Server after installing MediaMonkey as Portable you would need to start MediaMonkey.exe only once using these command line parameters "/elevate /regcomserver".
To do that add command line to properties of Created Shortcut to MediaMonkey.exe (Right click on MediaMonkey.exe -> Create Shortcut -> Right click on created Shortcut -> Properties -> In target Field append "/elevate /regcomserver" (now target should look like MediaMonkey.exe "/elevate /regcomserver") -> Click Apply to confirm that you have created command line correctly -> OK -> Start Shortcut"