| Author |
 Topic  |
|
|
apd
Junior Member
Greece
378 Posts |
 Posted - 19 Jul 2006 : 14:33:21
|
I just started importing movies with Lookup hard disk and I've noticed the following two bugs:
XMM hangs when importing a movie file that has a corresponding .SRT with the same title in the same folder.
When I select a folder, XMM scans the subfolders to. Not practical if one has to deselect the many already imported files. It would be helpful to limit the scan (or add a "Deselect All" button) |
|
|
Alessio Viti
Forum Admin
Italy
9171 Posts |
Posted - 21 Jul 2006 : 13:02:29
|
Hi Apd,
I will try to locate the bug with SRT files.
About the subfolders: XMM can detected automatically if a Movie is already inside the database, so it will NOT add it even if you "check" it.
Alessio |
 |
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 21 Jul 2006 : 13:17:07
|
| Yes, but in the same file structure there may be files that one doesn't want to import at all... |
|
|
|
Markstar
Starting Member
30 Posts |
Posted - 21 Jul 2006 : 22:52:28
|
Hi,
I have a similar problem when importing from a specific folder:
When importing a single file everything works great, but with more files XMM reads the first few (2-4) correctly (codec, length, etc) but then gives the following error:
This version of the DLL is not compatible After this message appears for the first time, it does for all the remaining movies and none of the media information is stored in XMM except the "Movie File" and "Media Labels" entries. 
Next I tried to read a codec manually for one of the movies that were not read correctly. I double-clicked on a movie -> "Read Files" -> "Select Files to Read" and after that I selected the appropriate file for the movie. Then "Read Codecs of Selected Files". But none of the entries changed but I did not get an error either!!!  I tried this with many movies - all with the same result.
After that, when I wanted to exit XMM, it crashed and I got the windows error:
The instruction at "0x77fcaea0" referenced memory at "0x006f0063". The memory could not be "written".
Click on OK to terminate the program
But before you think I had corrupt files: After restarting XMM I was able to read the file information for any of my movies, as long as I did them individually (one at a time)! 
Another thing I've tried is creating a new database. This did not work at all and XMM crashed without an error notice while reading the files (I could briefly see the DLL error again). 
Btw, a little off topic:
@Alessio: I got XMM for my birthday (13th this month) and wrote you an email via the forum but you never responded. I have some questions that might not belong on the forum (about registration etc). Is there any way to contact you? Before I had a different email adress in the forum(mine)than on the registration (my girlfriends), is that the reason you did not respond?
Edit: I did some more testing and there is another error message that briefly appears on the screen:
458Bad vaariable type.
Also, I think I have seen another error message with a negative number in front, but I'm not sure.
Anyway, hope that helps. 
Edit2: Oh, and unlike the other XMM crashes I have experienced (like when importing many movies via text or looking up many movies via script), the crashed when reading from the files leaves XMM in the memory where it can take up a lot of memory (at one time I had 7 instances of XMM taking up around 300MB RAM). |
Edited by - Markstar on 21 Jul 2006 23:46:16 |
|
|
|
Alessio Viti
Forum Admin
Italy
9171 Posts |
Posted - 24 Jul 2006 : 16:02:12
|
Hi!
Please sorry very much for my late reply!
Please write me an email at:
alessioviti -at- binaryworks.it
I haven't get your email, this is why I haven't answer to you.
About all these problem in reading files, I think that is related to mediainfo.dll file. Have you get this error with particular codecs?
Thank you very much!
Alessio |
|
|
|
Markstar
Starting Member
30 Posts |
Posted - 25 Jul 2006 : 11:38:35
|
Alright, I wrote you an email.
About the import issue:
I divided my movies into xvid and divx but XMM still crashed with both. Also the codec info does not get written on the ones that were imported successfully. Again, if I restart XMM and do it manually every one of those movies works.  |
|
|
|
Alessio Viti
Forum Admin
Italy
9171 Posts |
Posted - 25 Jul 2006 : 15:27:53
|
Wow, really strange. I will try to find the bug.
Thank you!
Alessio |
|
|
|
Markstar
Starting Member
30 Posts |
Posted - 01 Aug 2006 : 21:03:20
|
| Any news on the problem? |
|
|
|
Alessio Viti
Forum Admin
Italy
9171 Posts |
Posted - 03 Aug 2006 : 15:52:31
|
Hi,
Sorry, I haven't found time to work on this, I hope next days...
Alessio |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 03 Aug 2006 : 19:30:41
|
There's two more things related.
When I import with Hard Disk Look-Up, the process completes presenting a window "Insert new CD" or something like that. Why, if it's a HD...
Some files get imported but no details appear in the Media tab.
And a request:
Could u pls make XMM remember the last folder used? It's a drag having to navigate every so often to the Incoming folder. |
|
|
|
Alessio Viti
Forum Admin
Italy
9171 Posts |
Posted - 04 Aug 2006 : 10:28:53
|
Hi,
When I import with Hard Disk Look-Up, the process completes presenting a window "Insert new CD" or something like that. Why, if it's a HD...
I haven't found this message in HD Lookup...what release are you using? Probably I haven't understand correctly.
Could u pls make XMM remember the last folder used? It's a drag having to navigate every so often to the Incoming folder.
Should already do this, I will try to find the bug.
Thank you!
Alessio |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 04 Aug 2006 : 12:44:25
|
Sorry Alessio, I closed that window too quickly and I can't replicate it. I'll keep an eye in case it pops up again.
Any ideas about the fact that sometimes the Media tab doesn't get the info from the file read? Today I imported a file which was recognised as XVID (correctly) but the Media tab only show this info:
Resolution: x
Disks: 1
Channels: 0 |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 06 Aug 2006 : 11:37:35
|
Ok, I worked a bit more on it and it seems the HD Lookup function is totally erratic. I tried a folder with 11 files - it imported the first one and then XMM crashed. Tried again, it reimported the same file (which you said shouldn't happen) then crashed again. Third try, it imported the remaining files, and then the import window emptied but remained open. This time, all 11 files have the Media tab filled up.
PS The first file shows these attributes in the media tab:
DivX3 Low. 727kbps. 640*336. 1. MPEG1/2L3. 112000. 48Khz. 2. 23,976. |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 10 Aug 2006 : 10:24:56
|
Kept trying but XMM still crashes a lot. At one point I was asked to sent a Microsoft report with this data:
App stamp 44cb7347
modname mscworks.dll
modver 2.0.50727.42
modstamp 4333e7ec
fdebug 0
offset 001062fa |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 11 Aug 2006 : 20:13:58
|
After installing 5.3.2 and rebooting, I tried HD import again. This time it crashed before even opening the window to select the folder. It also tried to send a report to MS
App stamp 44dc705e
modname ntdll.dll
modver 5.0.2195.7006
modstamp 41e64e8
fdebug 0
offset 004aff8
|
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 12 Aug 2006 : 12:09:03
|
| One thing I forgot to mention is that in the status bar of XMM I keep getting a message starting with a long number and then saying something about writing in protected memory. |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 12 Aug 2006 : 14:36:11
|
And a final note. I can say for sure that the problems are not related to codecs, because I tried importing only a few files at a time and eventually all were recognised (except one .ogg). I do get a lot of messages related to memory and I think that XMM is affected if one works fast (pressing buttons too quickly - I've noticed this in other aspects of the program.
BTW. XMM now remembers the last folder used, but again, we have to press one extra button - why?
|
|
|
|
Alessio Viti
Forum Admin
Italy
9171 Posts |
Posted - 12 Aug 2006 : 16:10:19
|
Hi Apd,
Please don't think I am not reading your post just because I am not answering , I am trying to fix the problem.
Please continue to write your comments on this.
Really thank you very much for your help!!
Alessio |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 17 Aug 2006 : 12:09:07
|
Hi Alessio,
I managed to keep track of an error message that I get sometimes when I import with HD lookup. The import window gets a red X all over and prompts me to quit; then I get the message
The instruction at 0x77fcb861 referenced memory at "0x00000000". The memory could not be written.
Click on OK to terminate the program
After I click OK, XMM remain in memory but is hung. |
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 17 Aug 2006 : 12:18:48
|
Actually, before this error message I get this:
"Unhandled exception has occured...
Attempted to read or write protected memory. This is a"
The second line is exactly as you see it. And there are three buttons, Details, Continue, Quit.
So when i press Quit, I get the message I just wrote about. But if I press Details (Pls remember I run w2k pro), then I get this:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Drawing.SafeNativeMethods.Gdip.IntGdipDisposeImage(HandleRef image)
at System.Drawing.SafeNativeMethods.Gdip.GdipDisposeImage(HandleRef image)
at System.Drawing.Image.Dispose(Boolean disposing)
at System.Drawing.Image.Dispose()
at System.Windows.Forms.ControlPaint.DrawImageDisabled(Graphics graphics, Image image, Rectangle imageBounds, Color background, Boolean unscaledImage)
at System.Windows.Forms.ButtonInternal.ButtonBaseAdapter.DrawImageCore(Graphics graphics, Image image, Rectangle imageBounds, Point imageStart, LayoutData layout)
at System.Windows.Forms.ButtonInternal.ButtonBaseAdapter.DrawImage(Graphics graphics, LayoutData layout)
at System.Windows.Forms.ButtonInternal.ButtonStandardAdapter.PaintWorker(PaintEventArgs e, Boolean up, CheckState state)
at System.Windows.Forms.ButtonInternal.ButtonStandardAdapter.PaintUp(PaintEventArgs e, CheckState state)
at System.Windows.Forms.ButtonInternal.ButtonBaseAdapter.Paint(PaintEventArgs pevent)
at System.Windows.Forms.ButtonBase.OnPaint(PaintEventArgs pevent)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
at System.Windows.Forms.Control.WmPaint(Message& m)
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: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
eXtreme Movie Manager
Assembly Version: 5.3.2.0
Win32 Version: 5.3.2.0
CodeBase: file:///C:/util/XtremeMovieMan/eXtreme%20Movie%20Manager.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
ADODB
Assembly Version: 7.0.3300.0
Win32 Version: 7.10.3077
CodeBase: file:///C:/util/XtremeMovieMan/ADODB.DLL
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.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.
|
|
|
|
apd
Junior Member
Greece
378 Posts |
Posted - 27 Aug 2006 : 15:48:22
|
| Hi, I just got back for a day and tried the new version; sorry to say HD Lookup still has the same erratic behaviour... |
|
|
|
Topic |
|
|
importing movies