search

garzj / google-photos-migrate

A tool to fix EXIF data and recover filenames from a Google Photos takeout, preserving albums within the directory structure.
https://npmjs.com/package/google-photos-migrate
MIT License
104 stars 11 forks source link

0 files migrated #30

Closed alternativesurfer closed 3 months ago

alternativesurfer commented 3 months ago

Hi, I have a full google takeout directory with a significant number of files. Just ran this and it moved 0 files, also 0 failures.

npx google-photos-migrate@latest full "\10.0.0.65\media\gp-bak" "\10.0.0.65\media\output" "\10.0.0.65\media\error" --timeout 60000

image

garzj commented 3 months ago

How does the directory structure of your gp-bak look like?

Is it the similar to this issue?

alternativesurfer commented 3 months ago

.\gp-bak\Google Photos\ With the various album folders and such underneath that. image

I don't think its related to that issue, I can see jpg/png/video files all present in the source folders.

garzj commented 3 months ago

I made a new branch with some changes. Can you try them?

If they don't fix it, it would be interesting if the flat migration works as expected.

alternativesurfer commented 3 months ago

Ty! Updated, no change in behavior. image

Tested flat, it appears to work image

garzj commented 3 months ago

I hope the flat migration was sufficient for you, but as for keeping the album structure, I can't spot the issue. I went ahead and added a verbose flag -v.

Would you try again with these instructions and post any useful output?

cd google-photos-migrate
git pull origin no-files-fix --ff-only
git checkout no-files-fix
yarn deploy full "\\10.0.0.65\media\gp-bak" "\\10.0.0.65\media\output" "\\10.0.0.65\media\error" --timeout 60000

It could also be an issue with the network drive. What if you try it locally?

alternativesurfer commented 3 months ago

It looks like running it on a local directory (or mapping the share to a drive letter) solved it! Thank you so much!

garzj commented 3 months ago

I tried this for myself now and it seems like my latest changes indeed fixed this issue. (The module node-glob didn't like the backslashes as path seperators.) I'll make a new release.