Finding missing images in an image sequence?

[Candlelight]

What Lindley said. It will give you the total file number, but it's only copying the ones that aren't in the destination folder when it checks. It doesn't know that until it gets to them so it gives the total.

It said 30,000 files to copy, 143GB, 5 hours remaining.

I know what I saw. As 12,000 files were already in there it shouldn't have said what it said.

Sure it should. It sees 30000 files in the starting folder, it needs to process all of those. As it progresses it may figure out that some of them don't actually need to be copied, but it doesn't know that up front. (It could check the destination first, but for efficiency reasons it doesn't.) This is exactly what Guartho just said.

As for the estimated time remaining, I think we all know that can be wildly inaccurate sometimes. Although lately it seems like they've been doing a better job at estimating that.

But in Windows it wouldn't do this. It would automatically skip over those in there.

In the Mac the progress bar started from scratch and started counting down from 30,000, IE I'm starting again.

 

[sojourner]

In Windows it would do just as Lindley described. It doesn't know to "automatically skip" the files until it checks each file to see what it is and compare it to what is in the destination directory, hence it will still count down from 30,000. There really isn't much time saved with windows by telling it not to just recopy everything.

 

[Candlelight]

In Windows it would do just as Lindley described. It doesn't know to "automatically skip" the files until it checks each file to see what it is and compare it to what is in the destination directory, hence it will still count down from 30,000. There really isn't much time saved with windows by telling it not to just recopy everything.

But there is an option in both Windows and Mac to apply to all whatever option you chose.

In Windows it'll skip all duplicates right from the get go. In Mac it doesn't seem to.

 

[Lindley]

In Windows it'll skip all duplicates right from the get go. In Mac it doesn't seem to.

I can't say for sure what it did since I wasn't there. Maybe you didn't select the option you thought you did; maybe you just misinterpreted what you saw. But I know the "don't replace files in the destination" option isn't broken.

 

[Candlelight]

I think the Mac might be screwy after all.

I did another copy, definitely selected replace and it ended up making duplicates.

Go figure.

 

[Lindley]

Oh, that's right....one of the options will just rename the new files so that they don't conflict with the old ones. I can't remember which option that is.