- MediaMonkey Add-on - by Zvezdan Dimitrijević
This add-on works with MediaMonkey v2.x-4.x. It allows logging of many MM events: OnPlay, OnStop, OnPause, OnSeek, OnTrackEnd, OnTrackSkipped, OnTrackProperties, OnTrackAdded, OnTrackDeleting, OnTrackConverted, OnBeforeTracksMove, OnStartUp, OnShutdown... The next data are stored in the log file: date/time, computer/user name, name of the event and track name. The location of the log file could be specified in the Options dialog box. The log file is saved in CSV format, so it could be imported e.g. in Excel. The events could be also displayed in real-time with the Event Viewer dockable panel.
If you want to discus about this add-on, you could visit its related MediaMonkey forum thread. If you are using some skin which is not supported by default, you could take a look of skin styles for this add-on made by nynaevelan at the next forum thread.
This add-on is donationware. I am its sole developer and I worked on it in my own free time. I am not employed by Ventis Media, the company behind MediaMonkey, nor have I been paid by them for my efforts. If you find my add-on useful and want to help its further development, it would be nice if you could send a small donation using PayPal. You could donate as much as you think that is appropriate, any amount would be really appreciated.
This add-on doesn't work with MediaMonkey v5! No add-on made for a previous version of the program will work with MM5, either by me or any other author, since MM5 has completely different programming interface than before. If you really like my add-on and think that it is essential for your work with the program, you should stay with MM4.
Added: DeviceFileCopied and DeviceSyncCompleted events [MM4];
Added: LogEventToFile(sEvent, sTrack, sFileName) subroutine for logging of custom events, similar to the existing LogEvent(sEvent, sTrack) but with ability to programmatically specify log file;
Added: ClearEventViewer() subroutine for programmatic clearing of Event Viewer;
Added: ClearLogFile() subroutine for programmatic clearing of log file;
Fixed: specifying of log file in the Options dialog box and many other things.
v2.6 - 2015-10-15
Added: LogOnDownloadFinished, LogOnDeviceSyncCompleted and LogOnDeviceFileCopied events [MM4];
Added: Copy/Select All/Print items to the popup menu;
Fixed: error when skipping playback to the next track (broken in 2.3).
v2.5 - 2015-06-20
Fixed: many things.
v2.4.1 - 2012-02-06
Fixed: using of Event Viewer and Logger in other scripts.
v2.4 - 2012-02-04
Added: view of events without writing to the log file: OnChangedSelection, OnTrackListFilling, OnTrackListFilled, OnNowPlayingSelectionChanged, OnNowPlayingModified, OnTrackListSelectionChanged and OnTrackListModified [MMx];
Added: possibility for script developers to use Event Viewer and Logger for displaying/logging messages from their code (please read the Usage section).
v2.3 - 2011-06-22
Added: LogOnTrackSkipped and LogOnCompletePlaybackEnd events [MM4];
Fixed: skin styles path [MM4];
Fixed: visible state of Event Viewer after restart when it is closed on the [x] button from the Titlebar.
v2.2.1 - 2009-06-27
Fixed: View Log File option and display of events in Event Viewer with log files in UTF-8/Unicode format.
v2.2 - 2009-05-13
Added: OnPlaybackEnd event;
Improved: skin styles;
Fixed: error with Maximal log file size.
v2.1 - 2009-03-04
Added: possibility to open a new log file when the file size is greater then specified value;
Added: option in the context menu to open a specified log file into the Event Viewer;
Added: display of information about opened log file and events range;
Added: song position for Pause and Seek events;
Improved: Event Viewer's skin automatically updated after skin change in the Options dialog box (only for supported skins).
v2.0 - 2009-03-01
Added: Event Viewer dockable panel;
Added: possibility to toggle Event Viewer title bar from the contex menu (MM 220.127.116.119 or up);
Added: option Maximal # of rows in Event Viewer;
Added: option Load log file when open Event Viewer;
Added: option to save log file as ANSI, UTF-8 or Unicode.
v1.1.2 - 2009-02-07
Fixed: deleting of tracks when enabled logging of the OnTrackDeleting event.
v1.1.1 - 2009-02-06
Fixed: error with OnBeforeTracksMove and OnTrackProperties events.
v1.1 - 2009-02-06
Added: OnBeforeTracksMove and OnTrackProperties events;
Fixed: log file name when the "Write a new log file every day" is turned on.
For MediaMonkey 3.0 or higher - just double-click on the EventLogger-xx.mmip file; if you are on Vista or Win7 and you got "Product installation error", make sure you have MM3 set to "Run as Administrator"; if you downloaded the installation package with IE7 and it changed its extension to a .zip, you should first change it back to a .mmip.
For MediaMonkey 2.x - rename a .mmip extension to a .zip, extract the EventLogger.vbs and EventLoggerGUI.vbs files to the MediaMonkey's "Scripts\Auto" folder and restart MM program.
Choose View | Event Viewer to show/hide dockable panel. The add-on settings are in the Tools | Options dialog box within the Event Logger sheet (turning on/off of events works immediately after the confirmation only with MM 18.104.22.1685 or higher).
The script developers could use this add-on to display some text from their code by placing few additional lines of code on the appropriate places in the script. The scripters could use MsgBox or SDB.MessageBox instead, but they will halt the execution of the script which is not always desirable. However, Event Logger and/or Event Viewer would log/display such messages without any break of the execution.
Here is what you should do if you want to use Event Viewer to display messages from your script:
- install Event Logger add-on;
- add the line Script.Include "Auto\EventLogger.vbs to your code, e.g. on its begin or end;
- add the line ViewEvent "some_text_e_g_script_name", "actual_text_e_g_some_variable" anywhere where you want to get the displayed message (for example, I could put ViewEvent "Magic Nodes", SDB.MainTree.CurrentNode.Caption in the OnChangedSelection event handler of my script);
- restart the program or use Script.Reload.
If you want to log messages, i.e. to get messages saved to the log file, you should use the LogEvent "abc", "xyz" syntax instead.
This add-on is a false positive reported as a worm by F-Secure. The author of F-Secure promised me that will update its database and put the add-on on white-list, but still didn't. If you go to the www.virustotal.com/en/ site, you will see that it is safe tested by 54 popular anti-virus engines; the only one reporting a worm in it is F-Secure.