Additional Tagging & Reporting Tools

[redwing]

I'm not sure I understand why the tag history command uses so much CPU. Now each backup saves changed tags only and thus in a very small size. Then loading those backups and listing those changed tags shouldn't require much operations even though there's a difference in that backup checks against a baseline file and tag history against current tags. At least the scope of changed tags and changed files to handle should be very small because they had to be recorded in one of incremental backups.

[boroda]

you are right. maybe 'tag history' can significantly optimized now. at the moment baseline is restored for *every* backup included in command window. thanks for the tip.

[Steven]

anyone using v3.1, should redownload as i forgot to update one thing that would affect the tag backup plugin

[boroda]

new version:

http://www.mediafire.com/file/5rx4f21zcp1wk7n/mb_NowPlayingToExternalFiles_2015-09-06.zip

* overall performance is better, but i'm not sure if the difference is noticeable.
* tag history command loads baseline backup only once now.

source code:

http://www.mediafire.com/file/890wv21zk9myzd6/TagTools_2016-11-03_11.03.28.rar

[boroda]

new version:

http://www.mediafire.com/file/5rx4f21zcp1wk7n/mb_NowPlayingToExternalFiles_2015-09-06.zip

* overall performance is better, but i'm not sure if the difference is noticeable.
* tag history command loads baseline backup only once now.

source code:

http://www.mediafire.com/file/890wv21zk9myzd6/TagTools_2016-11-03_11.03.28.rar

[phred]

new version:

http://www.mediafire.com/file/5rx4f21zcp1wk7n/mb_NowPlayingToExternalFiles_2015-09-06.zip

@boroda74- you're linking to one of your other plugins.

[redwing]

Tested the new version included in the source code archive file.
For backing up, there's not much differences compared with previous versions. But I noticed while comparing tags with baseline it uses 20 to 30% of CPU and about 1.4 GB of memory. MB is almost unusable during the task - mouse and keyboard lag and visual glitches in UI.
Tag history command too shows not much improvement in terms of CPU usage. Still I get "Not Responding" message while it's loading just two backups.
Thanks for making layout changes so that it now shows changed backups and changed tags only. But there are some bugs.



- The name of each backup is displayed incorrectly as the timestamp of the first backup file for every backup. Tooltip shows a different (correct) timestamp for each.

- It draws three lines for the same field (play count) maybe because three backups have a different value from that of library. But just one line can deliver the same information. If a cell has the same value as library, it can be left blank.

Also, tag history command sometimes didn't work with the following error. Restarting MB sorted out.

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.BackupType.Load(String fileName, String backupFileExtension)
   at MusicBeePlugin.TagHistoryPlugin.fillTable(String folder, Boolean includeSubfolders, Int32 maxBackupCount, Int32 trackIndex, Boolean reuseCache)
   at MusicBeePlugin.TagHistoryPlugin.TagHistoryPlugin_Shown(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnShown(EventArgs e)
   at System.Windows.Forms.Form.CallShownEvent()
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

[boroda]

redwing, thanks for bug reports, will look into it. as for cpu usage, only tag history can be affected, because all other functionality is very slightly improved and definitely improved (there are only couple of lines changed outside tag history), so maybe its some other reasons?

[boroda]

you are right, sorry for that. correct link:

http://www.mediafire.com/file/3juwddn1bp5ybmt/mb_TagTools_2016-11-03.zip

edit: mediafire uses flash and flash works very strangely in my browser (cyberfox for 64-bit intel).

[boroda]

redwing, if you haven't recompiled plugin, then i'm not sure what binaries are contained in source project. correct link to compiled plugin:

http://www.mediafire.com/file/3juwddn1bp5ybmt/mb_TagTools_2016-11-03.zip

[redwing]

Yeah, that's the one I tested. You have included it in the source project file (\obj\release\).

The high CPU usage while comparing tags with baseline might be an existing behavior that I happened to notice this time.

[boroda]

various bugfixes:

http://www.mediafire.com/file/rc6lyaay185dc05/mb_TagTools_2016-11-05.zip

source:

http://www.mediafire.com/file/rmsj1arbxa7vnnx/TagTools_2016-11-05_13.49.53.rar

[phred]

various bugfixes:

http://www.mediafire.com/file/rc6lyaay185dc05/mb_TagTools_2016-11-05.zip

Does this new version take care of this error?

Code

MusicBee v3.1.6152.39912 (Win6.1), 5 Nov 2016 8:13:

System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.Collections.ArrayList.get_Item(Int32 index)
   at System.Windows.Forms.DataGridViewRowCollection.SharedRow(Int32 rowIndex)
   at System.Windows.Forms.DataGridViewRowCollection.get_Item(Int32 index)
   at MusicBeePlugin.TagHistoryPlugin.buttonOK_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)

This error was thrown with the previous version (2016-11-03) when trying to do 'tag history.' Which wouldn't even show the library tags for the track in question. I also couldn't create a new baseline.

[redwing]

Great job! Working much better. Now the whole backup process no longer uses excessive resources, and MB can be used during the task.

Tag history too is working better with those reported bugs fixed. The only wish is tag history command too won't use too much CPU (still it uses over 30% of CPU briefly).

[boroda]

Does this new version take care of this error?

suggest, yes.

I also couldn't create a new baseline.

i need more info: is there some error dialog box?