2007-11-13, 23:42
For me saving the file to media location with media name would be fine
but for those unable to then I can see how a few problems may be encountered.
If for example a person wants to keep all of these nfo files local to the xbox - including those that are for files located on a network then this would complicate things greatly.
I think experimentation may be the key here
Once a system of any kind is in place then people will more easily be able to see the problems and possible solutions.
However
For rar files with multiple video files (Messy - Do people actuallly do this)
then how about appending something i.e
rarfilename-1.nfo
rarfilename-2.nfo
rarfilename-3.nfo
rarfilename-4.nfo etc
or allowing xml nfo files to contain more than one item eg
<movie>
<FIlename>content1.avi</FIlename>
</movie>
<movie>
<FIlename>content2.avi</FIlename>
</movie>
For VIDEO_TS then the only way I can think to do it would be to use the parent folder as file name.
For longfilenames on a remote server with the nfo stored local then another table will be needed again (file id) ie lfn001 and (full file name) ie longfilename.avi etc this would remove problems of similar filenames being truncated to the same name
It would be best in my opinion if files were not automatically overwritten at the very least the user should be asked - with perhaps the options - replace all/replace none
As i said above tho - Experimentation may be the key here
but for those unable to then I can see how a few problems may be encountered.
If for example a person wants to keep all of these nfo files local to the xbox - including those that are for files located on a network then this would complicate things greatly.
I think experimentation may be the key here
Once a system of any kind is in place then people will more easily be able to see the problems and possible solutions.
However
For rar files with multiple video files (Messy - Do people actuallly do this)
then how about appending something i.e
rarfilename-1.nfo
rarfilename-2.nfo
rarfilename-3.nfo
rarfilename-4.nfo etc
or allowing xml nfo files to contain more than one item eg
<movie>
<FIlename>content1.avi</FIlename>
</movie>
<movie>
<FIlename>content2.avi</FIlename>
</movie>
For VIDEO_TS then the only way I can think to do it would be to use the parent folder as file name.
For longfilenames on a remote server with the nfo stored local then another table will be needed again (file id) ie lfn001 and (full file name) ie longfilename.avi etc this would remove problems of similar filenames being truncated to the same name
It would be best in my opinion if files were not automatically overwritten at the very least the user should be asked - with perhaps the options - replace all/replace none
As i said above tho - Experimentation may be the key here