Skip to main content

Copied Source Folder Has Different Count Than Target Folder

Comments

10 comments

  • Brian Lawson Community moderator

    What kind of files are there in the folder on the NAS that are not there on your editing drive?

    0
  • Michael Miller

    I set up two file manager windows side by side, but was hoping that I wouldn't have to make a manual comparison. I'd rather know if and why ON1 doesn't copy everything. I want to know the rule.

    I can tell you that there are  .on1s, .jpgs, a couple of .tifs, and possible .xmp from Lightroom.

    Sorry, I forgot the .orfs

    Thanks for the response.

    0
  • Brian Lawson Community moderator

    In order to know why something was not copied it is very helpful to know what was not copied. Sort the windows by file type, that should make it easier to find the differences. My GUESS is that there are files in the source directory that ON1 does not work with. The program ignores file types it does not understand.

    Tell me what was not copied and I'll try to give you a better answer.

    0
  • Michael Miller

    I did a manual match and came up with 194 vs 193

    the difference was a file with the end of the filename including Copy.

    So I copied that one over and it increased the target folder by 1.

    Just found the 2nd one. It is an orphan .on1 file.

    So, ON1 doesn't usually create a Copy suffix. Usually it's v1 or .onphoto.

    0
  • Brian Lawson Community moderator

    What kind of file was it? What is its extension?

    0
  • Rick Sammartino Community moderator

    I get a COPY suffix every time I use 'Send To'. You also get a copy if you try saving and the file already exists.

    0
  • Michael Miller

    I just responded but got an error that the page could not be found, when I submitted it.

    The 'copy' part I mentioned was part of the filename, not the extension. There were two files with 'copy'. The extensions were .on1 and .tif. Must have been the .tif.

    The other was an orphan .on1, but I didn't recognize the filename as being mine. It was a PA190006.on1.

    0
  • Brian Lawson Community moderator

    It was the orphaned .on1 file that did not get copied over. Since the program did not see its matching image file it left the orphan alone and did not move it.

    0
  • Bernd PALMER

    If you are talking about Windows: Windows creates a normally hidden desktop.ini file that wouldn't be copied by ON1.because it doesn't belong to any photo. 

    0
  • Michael Miller

    Bernie,

    No, not an .ini.

    Turns out one was probably a .tif and the other was an orphaned .on1 (PA90006.on1) and there was no raw to match it.

    0

Please sign in to leave a comment.