Vidimport

[tvshowman]

One other problem that I'm having now, which I wasn't before:

In the <title> tag in the videos.xml file, ampersands ("&") are put in as "&amp;amp;" which doesn't get processed properly and display in GBPVR as the "&" character.

I would like to report the same problem in PVRX2.

I have 170 file imported and 91 have the ("&")("&amp;amp;_ in the file name

What's interesting is that American Idol turns into Maverick and Ariel&asos;s First Ever Movie

lol

any ideas?

It's a great tool and I have added it to my "send to" shortcuts to send a directory to be entered into it.

I am on XP

Cheers

[carpeVideo]

I am using VidImport to good advantage in a number of batch files. However, I can't seem to get it to do something the docs say it should: specifically, I want it to search the recording-dump file and use the same details for any entry with an identical path-and-filename. (In fact, it would be great if it did this ignoring the extension, but that seems pretty hopeful).

When I run VidImport, it leaves the channel as IMPORT and the description blank (or scraped from IMDB) regardless of whether that same file is already in the database.

Responders may wonder why I would want to Vidimport a file already in the database; I don't, exactly, but I am importing different file streams recorded from the internet as TV recordings.

It does do what it says - it essentially skips any files with the same name (including extension) in the recordings dump and assumes gbpvr has the correct description.
It does not re-import the description to do this just skips the import. If you have a different extension two things would happen, first it won't find it in the dump file and second it would do a lookup. I would have to change the code to look for entries in the recording dump with different extensions and then create a new entry in the import file. I am unsure how GBPVR would handle two recordings of essentially the same name though.

[carpeVideo]

I would like to report the same problem in PVRX2.

I have 170 file imported and 91 have the ("&")("&amp;amp;_ in the file name

What's interesting is that American Idol turns into Maverick and Ariel&asos;s First Ever Movie

lol

any ideas?


Cheers

Before I go checking into this - are you using the very latest release? (1.32 I believe, I just quietly dropped it onto the site). I may have fixed the issue. If not let me know and I will take a look.

[tvshowman]

Hi!,

Thanks for your reply.

The version I have is 1.32.0.0.

I got it from the wiki just now. Is there another source?

Cheers

[keith_leitch]

It does do what it says - it essentially skips any files with the same name (including extension) in the recordings dump and assumes gbpvr has the correct description.
It does not re-import the description to do this just skips the import. If you have a different extension two things would happen, first it won't find it in the dump file and second it would do a lookup. I would have to change the code to look for entries in the recording dump with different extensions and then create a new entry in the import file. I am unsure how GBPVR would handle two recordings of essentially the same name though.

Interesting. I guess I am having a different problem, then. Vidimport is importing descriptions and channel names for files that already exist in the database, rather than leaving the more descriptive entries. This is the case for exact duplicates, extension and all, except that the case of the letters may not be the same. Now that you have explained the code, I have looked more closely, and this seems intermittent: some files have kept their original descriptions, some have been overwritten. I will look for more of a pattern.

[carpeVideo]

Hi!,

Thanks for your reply.

The version I have is 1.32.0.0.

I got it from the wiki just now. Is there another source?

Cheers

Can you check again with a new file and a freshly dl'd 1.32 , here is what I am getting importing "the princess & the pea.avi" (just a text file that I changed the name of) Since vidImport doesn't overwrite if the error was caused by a previous version of vidImport it would remain

[carpeVideo]

Adds the x64 registry key lookup for the GBPVR path. (untested since I don't have a 64 bit os - let me know if it does not work)


Also adds a switch - nfo=on|off (defaults to off) that causes vidImport to create an XBMC compatible NFO for all video files in the path, based on the metadata generated.

CV

[tvshowman]

Can you check again with a new file and a freshly dl'd 1.32 , here is what I am getting importing "the princess & the pea.avi" (just a text file that I changed the name of) Since vidImport doesn't overwrite if the error was caused by a previous version of vidImport it would remain

Hi thanks for your help.

If I rename a movie directory and start gbpvr to clear the movies would importing with vidimport work as intended or would it create the same error since an older version was used first?

I will be moving my movies out of single directories and putting them all into one folder and that should remove the movies out of the database so I will need to import them again.

I am working for many hours so I will have to do this later on tonight.

Cheers

[carpeVideo]

Hi thanks for your help.

If I rename a movie directory and start gbpvr to clear the movies would importing with vidimport work as intended or would it create the same error since an older version was used first?

I will be moving my movies out of single directories and putting them all into one folder and that should remove the movies out of the database so I will need to import them again.
Cheers

That should work (althouth save the old export file) - although an easier test would be to create a text file and then rename it as an avi or mpg and do the vidimport on that. You could even put it in the same directory as another file that has an ampersand and use a very similar name.

CV

[BrettB]

Adds the x64 registry key lookup for the GBPVR path. (untested since I don't have a 64 bit os - let me know if it does not work)

I'm happy to report that the new version works with Win7 64-bit. Thanks for the great work!