INTERACT FORUM
Windows => Third Party Plug-ins, Programs, and Skins => Topic started by: pos on March 08, 2010, 12:10:02 pm
-
I am getting the following error when using the Auto Import function
AutoUpdate Error: Index was outside the bounds of the array
Can anyone explain the cause of this error and suggest a remedy.
Thanks
POs
-
You might post this in the PVDImport thread.
-
AutoUpdate Error: Index was outside the bounds of the array
This message originates from a caught exception in the auto update code. I'll see if I can somehow reproduce the exception.
Do you see anything else in the log window? If yes, "clear log" and then enable the log file. Post output here please.
In the meantime, can you reproduce the error with a smaller/different search expression (instead of the default [.Media Sub Type]=[Movie],[Tv Show] expression)?
-
I reduced the search expression for just [Video] and reset the log file the results are as follows:
08:12:17 - Start Logging...
08:12:19 - Run Auto Import Once...
08:12:19 - AutoUpdate error: Index was outside the bounds of the array.
-
I reduced the search expression for just [Video] and reset the log file the results are as follows:
08:12:17 - Start Logging...
08:12:19 - Run Auto Import Once...
08:12:19 - AutoUpdate error: Index was outside the bounds of the array.
Ok, that doesn't tell me anymore than your original post :), my bad.
But I'm thinking that a good way to isolate the problem would be to
o make a playlist of, say, 4 files
o Enter an expression which selects these four files
o Update the four files in PVD
o Do an auto update.
You'd then see "Change:..." in the log and, hopefully, see if a particular file is the perpetrator.
I'll look into this further, but I'd appreciate if you'd try this...
-
I've created the playlist but could you give me an example of the type of expression you need to see to genereate the change notification.
Thanks
POs
-
I've created the playlist but could you give me an example of the type of expression you need to see to genereate the change notification.
In the search box (upper left corner of mc - you may have to select videos to actually see the search box), start the expression wizard. Using the dialog that pops up, make a filter for the particular playlist.
Afterwards, select "text" in the search box. The expression that now shows can be used directly in PvdImport.
-
have tried what you suggested but it did not generate any further log information
-
If you have AutoUpdated the movies in PVD, you should see "Change: [something]" in the log (assuming the file metadata has been changed in PVD)
Have you ever been able to autoupdate? I.e. have you ever seen "Change: [something]" in the Log window? I'm just trying to narrow down the problem, you see...
-
I have never been able to get autoupdate running I have been trying to get this setup andd this is the latest error i have encountered. I previously had the ModDate error reported in another thread but resolved this one.
The only wokring approach so far has been the Mass Import option but it would be good to get the auto update working.
-
I cannot resolve your issue just now, but I've been working on and off on a new release which has some new debugging facilities.
Hold on and I'll post the release in an alpha thread in the near future...
-
Many thanks for your help I'll keep experimenting
-
Many thanks for your help I'll keep experimenting
One suggestion for further experimentation, if you don't mind:
It seems as if the AutoUpdate functionality works for most of the users. In particular, your error has never been reported and I believe quite a few people are using AutoUpdate quite frequently.
So, I suspect that the source of the error might be on the MC side (mind you, I NEVER suspect this :) ), maybe related to an inconsistency in the library or something.
Could you create a new library, import just one file (copy one file to a new folder), import the file into the new library and try again?
What's your MC version?
-
No joy with your suggestion I'm afraid. I cleared down the library and loaded up just one file. Restarted autoimport and as soon as I created the entry using PVD for the relevent file I got the array out of bounds error again.
With regards versions:
MC = 14.0.155
PVD = 0.9.9.18
-
No joy with your suggestion I'm afraid. I cleared down the library and loaded up just one file. Restarted autoimport and as soon as I created the entry using PVD for the relevent file I got the array out of bounds error again.
With regards versions:
MC = 14.0.155
PVD = 0.9.9.18
Rick.ca, are you using PVD ver. 0.9.9.18 ? I'm using .16
-
Rick.ca, are you using PVD ver. 0.9.9.18 ?
Yes. Works for me.
-
I have posted a new beta version of the plugin (1.3.0) on the Plugin Development Board (http://yabb.jriver.com/interact/index.php?topic=56563.0)
This version has a new logging "Details" checkbox which, when checked, triggers significantly more info in the log.
So:
o Use the library with one movie which you created earlier.
o Change the movie in PVD. (for example import data from a new source)
o Check the details box.
o Start "OneShot" logging
-
I downloaded the plugin but when I attempted to load it in Media Centre I get the message failed to load plugin
-
I have done what you have suggested here is the resultant log. Run once on start up was set hence the action from 14:41 - 14:43. The update using PVD of they file in question took place at 14:43 with the instant result of an array bounds error
14:41:39 - Start Logging...
14:41:39 - Plugin Initiated OK
14:41:39 - Auto Import Cyclic started...
14:41:39 - Auto Import Cyclic Getting Files from MC..
14:41:39 - Auto Import Cyclic Found 0 files.
14:41:39 - Auto Import Cyclic Getting data from PVD...
14:41:39 - Auto Import Cyclic Reader executed OK. Now getting records...
14:41:40 - Auto Import Cyclic finishing ...
14:41:40 - Auto Import Cyclic the total number of items processed were 0
14:41:40 - Auto Import CyclicNow adding 0 files to processing queue...
14:41:40 - Auto Import Cyclic This pass has now finished!
14:41:40 -
14:43:12 - AutoUpdate error: Index was outside the bounds of the array.
14:43:12 - Auto Import Cyclic ended...
-
It seems as if your MC search expression yields 0 files (I.e. PvdImport finds no files to process!). Please try to enter/paste your expression in the search box when video is selected in the tree and see if any files are found. Could you post your expression?
-
It is defintely finding files in PVD see below log file
15:56:56 - Start Logging...
15:56:57 - Plugin Initiated OK
15:56:57 - Auto Import OneShot started...
15:56:57 - Auto Import OneShot ended...
15:57:01 - Auto Import Cyclic started...
15:57:01 - Auto Import Cyclic Getting Files from MC..
15:57:01 - Auto Import Cyclic Found 178 files.
15:57:01 - Auto Import Cyclic Getting data from PVD...
15:57:01 - Auto Import Cyclic Reader executed OK. Now getting records...
15:57:01 - AutoUpdate error: Index was outside the bounds of the array.
15:57:01 -
15:57:01 - Auto Import Cyclic ended...
-
It is defintely finding files in PVD see below log file
15:57:01 - Auto Import Cyclic Found 178 files.
Yes, but that's your big library, isn't it?
Anyways, can you retry with "Details" selected, please? You'll get a lot more info in your log. That's the reason why I originally asked you to make an alternative library with few files...
-
I have tried with a large library and with a small library and with the details box checked the results are always the same with the exception of the 'number of files found'. I always get the out of bounds error after the 'Now getting records' log statement there are no more log messages when the details check box is ticked.
-
I have tried with a large library and with a small library and with the details box checked the results are always the same with the exception of the 'number of files found'. I always get the out of bounds error after the 'Now getting records' log statement there are no more log messages when the details check box is ticked.
Ok, I see. I'm going away for a week now, so I'll have to put this on hold. But I'll probably include some more debugging texts after that.
-
Hey Pos,
Could you try 1.3.2 in the beta thread? There is some new logging there which may shed some light on the above discussed issue...