DoctorD1501
Deleting video files that are spilt into multiple parts
I was using the scraper testing on a few files and it works well :) However, when I click "write file" using it for the following files it only renames the 1st file but delete the 2nd, 3rd and 4th which fortunately I have backup of them.
eg:
FHD IPZ-001 1.WMV
FHD IPZ-001 2.WMV
FHD IPZ-001 3.WMV
FHD IPZ-001 4.WMV
I'm not able to reproduce this issue. Can you provide more detail on the steps you took where the program deleted your files as well as any program settings you have enabled? Are you scraping a folder with those files in it, or did you select the files only? Was there more than one file selected?
I have the renaming option turned on. I believe that might be the issue where it is "replacing" (deleting the 2nd, 3rd and 4th) as they will all have the same file name.
I am scraping just the video files itself by selecting those files only. All 4 files are selected at the same time.
Hope this helps. Thanks!
I see two problems here, but I'm still not able to reproduce the issue.
Problem one is that you should only be selecting one file for a stacked / split movie because it will automatically detect the stack.
The second problem is that your movies are not named correctly to be detected as a stack. You can't just put a number at the end of the file for part one, two, etc. You need to put in a word like CD1 or disc1 etc. See this website for the naming convention: http://kodi.wiki/view/Naming_video_files/Movies#Split_video_files_.28file_stacking.29
Even then, when I run the test using your methodology and file names, I get this message in the console and only one of the files gets renamed (which is OK) :
A file or directory already exists at path_of_file_here - skipping overwrite or creation of new folder.
May I ask what operating system you are using? Perhaps on a different OS, the check to see if a file is a duplicate is not working? I'm using windows.
Hi there,
Thanks for your reply and advice on the file name, clearly I was not doing it correctly.
I am using Windows 10 64bit as well. I will try to run it again to see if I can replicate the issue and report further.