Extract Movie Video Database to seperate files

I'd suggest save as filename. There would be no issues with too long names as the corresponding file names would already be compliant. Just my 2 pence.

Trouble with that is:

VIDEO_TS.IFO

Among others. Also, RAR paths (or files within RARs) are another special case.

jmarshall Wrote:Trouble with that is:

VIDEO_TS.IFO

Among others. Also, RAR paths (or files within RARs) are another special case

VIDEO_TS.IFO
VIDEO_TS.nfo
VIDEO_TS.tbn

or

isoORimgDVDimageFileName.iso
isoORimgDVDimageFileName.nfo
isoORimgDVDimageFileName.tbn

and

RarArchiveFileName.rar
RarArchiveFileName.001
RarArchiveFileName.002
RarArchiveFileName.003
RarArchiveFileName.nfo
RarArchiveFileName.tbn

Would not work?

No, that won't work.

VIDEO_TS.IFO is the filename for ALL DVD folders.

Thus, if you have 2, and you are saving to somewhere OTHER than the media's own path, it's going to overwrite.

The problem with rars' is 2 video files in the same rar. Saving using XBMC's internal RAR path is useless to the user.

The problem exists only when saving the .nfo files to somewhere OTHER than where the media files lie. Come up with a solution for that and we're in business.

What if in the case of VIDEO_TS.IFO it saved them into a folder structure just like the movie so the file could then be merged with the folder later? for example it would save 300/VIDEO_TS/VIDEO_TS.nfo ? Not really sure about Rars but i think this would work for saving to an path other than the original.

Look i'm all for buyer beware If you choose not to save them to the same dir as the media then you take the risk of the filenames being cut off for fatx limitations and getting over written for mulitple

And basically the whole point of being able to choose a destination was for people without writable shares so they can manually copy them over maybe just maybe if its a generic filename like video.ts and not saved to original source it can use VideoName.nfo instead so people know what movie its for and can rename it ?

P.S when I original suggested it I didn't mean it as a backup/restore feature (we allready have that) I meant it as easy way to make .nfo files

I am extremely pleased to see this feature making it into XBMC.
Let me see if I am understanding the goal:
This option would give you the ability to export the database record for a given element in the library out to an XML formatted plaintext document with the .nfo file extension.
This file could then be placed alongside the file in the share, and thenwhen scanning that location into the database, the record would be pulled from the local file and NOT the selected scraper.

The main sticking point right now is "what do you want me to do if I'm NOT exporting to a file alongside the video file?", right?

I think one other option would be to define a specific directory to export all the dbase files to, either local or via SMB. Would it be possible to determine file system and read / write attributes at export time?

its not just for a given element its for the whole database to seperate files not files one by one

here's another question: what about TV episodes?

Tv episodes can't be scanned by info file currently so it would only work for movies and music videos