Mede8er Forum

Mede8er Community => Mede8er Community Tools => Offline Scantool => Topic started by: thisgeek on November 25, 2013, 07:42:59 PM

Title: Windows GUI based scan tool
Post by: thisgeek on November 25, 2013, 07:42:59 PM
Hello,

I have written a small utility similar to Lupissimo's Offline Scantool for X2/X3 devices, however it is Windows GUI based (will run on 32 or 64 bit), and will allow you to scan a list of Jukebox folders.

I wrote it based on some information provided by various people in Lupissimo's thread, so thanks to them. http://www.mede8erforum.com/index.php/topic,8099.0.html

You can download it from my site, here:

http://midnightreign.org/downloads/moni8er-a-mede8er-utility/

Usual warranty disclaimers apply. I have only tested this against my own movie folders, and it works like a charm. I have no idea if this will work with TV xml as I don't manage my TV stuff, and it definitely will NOT work with music.

The supplied README.txt in the archive should explain basically how it works. There is no installer, simply extract the archive and run the exe. Add your jukebox folders and click the 'Create' button.

At some stage I hope to implement the 'Monitor' function which will monitor your Jukebox folders for changes and update the databases as required.

I hope someone finds this useful.
Title: Re: Windows GUI based scan tool
Post by: docbill on February 17, 2014, 01:55:18 PM
This exception happens every time I click create.   I tried adding the top level drive "X:\"  and I tried adding just a single movie folder.   Either way, it does the exact same thing.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Index and count must refer to a location within the string.
Parameter name: count
   at System.String.Remove(Int32 startIndex, Int32 count)
   at Moni8er.ProcessPaths.CreateDatabase(String JukeboxPath)
   at Moni8er.MainForm.buttonCreate_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.34011 built by: FX45W81RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Moni8er
    Assembly Version: 1.0.5135.39438
    Win32 Version: 1.0.5135.39438
    CodeBase: file:///D:/Y2M/Moni8er-1.0.5135.39438/Moni8er.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    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.33440 built by: FX45W81RTMREL
    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.34003 built by: FX45W81RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Update
    Assembly Version: 1.0.5135.39190
    Win32 Version: 1.0.5135.39190
    CodeBase: file:///D:/Y2M/Moni8er-1.0.5135.39438/Update.DLL
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.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>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Title: Re: Windows GUI based scan tool
Post by: thisgeek on March 19, 2014, 07:15:40 PM
Thanks to docbill I have made some significant enhancements to the utility.

I've just released a brand new version that is significantly faster, especially as it can now update the databases instead of creating them from scratch every time.

It also correctly handles mjbignore.xml / .mjbignore files.

Title: Re: Windows GUI based scan tool
Post by: thisgeek on April 30, 2014, 06:50:06 PM
Hi everybody - if you're using the utility and experiencing crashes, it is most likely due to extraneous XML files in your movie folders - if possible do a clean up of your movie folders and remove any cruft XML docs - stuff left over from other programs, etc. To help you along, you can enable logging in the program (restart the program once you enable logging - a crash won't allow the program to save the setting). The log file will list additional XML files it finds and ignores. In some cases this could be legit XML docs you actually want processed, so go take a look through the reported path name and see what is there.

I'll release a new version in a while with some workarounds.