- latropa64 wrote:
- Shouldn't nfo's also follow the stacked name now?
I know when you export the database as separate files within xbmc, you will end up with this:
Movie Name-cd1.avi
Movie Name-cd2.avi
Movie Name.nfo
Movie Name.tbn
Media Companion won't recognize the "Movie Name.nfo" as belonging to the stacked movie and so when you scan it will create a 2nd new file "Movie Name-cd1.nfo".
While Media Companion will go that way in time, the reason it hasn't yet is that I haven't implemented a system that identifies the media file associated with the nfo. At the moment, on startup Media Companion searches folders for .nfo files, if it finds an nfo file containing valid xml then it adds it. At a later time, if someone wants to play the media, or look at the media information or file details then it does a quick search replacing the .nfo with .avi, .mpg, .wmv, etc
By using the stack name for the .nfo this will break the media link with with the file
eg
"moviename cd1.nfo"
looks for
"moviename cd1.mediaextension"
but if this was stacked it would be
"moviename.nfo"
looks for
"moviename.mediaextension" instead of "moviename cd1.mediaextension"
This is high on my list of things to do, but until I change the method by which Media Companion links these files I will not add it.