Suggestions for Synology Users

[brock]

Thanks for this script, this is super helpful. I'm running a Synology and thought I'd contribute a couple tips that others might find useful.

• The indexing service on Synology can't be stopped easily, and once you start this script, your Synology will likely come to a crawl as it attempts to index and generate thumbnails for all of the new photos. You can pause it in the menu bar at the top of the screen, but I'd recommend setting the Indexing Service to run on a schedule.

• If you try to run ./gpth-linux from SSH, it likely won't work because (I believe) it is expecting a typical linux window environment. What worked for me was to run this on another machine and select the folders over the Samba share, so mount the smb://synology, select photo or some other directory, then running ./gpth-macos

[brock]

Sponsoring you for the year @TheLastGimbus as a thank you!

[TheLastGimbus]

thought I'd contribute a couple tips

Nice of you! If you would want to, we could make some .md file/wiki page for you guys

once you start this script, your Synology will likely come to a crawl

Hmm, if you intend to leave them there, this shouldn't be an issue, because gpth copies each file, changes it's date and it's done - it doesn't modify them afterwards or anything. But yeah, you may want to stop this

... mount the smb://synology, ...

Umm... ;_;

Bro, you can just use cli options to skip whole desktop-enviroment-pickers stuff:

$ unzip takeout.zip
$ gpth --input takeout/ --output my-photos/
# Should work perfectly on any distro

Funny thing, gpth is recommended in offical synology faq 😅 https://kb.synology.com/en-in/DSM/tutorial/How_do_I_migrate_photos_from_Google_Photos although it's old python version

Sponsoring you

Big thanks! Will definietley enjoy some coding'n'pizza with this <3

[TheLastGimbus]

Maybe a separate Synology readme

I get you 👀 - i may add some extra notes soon

The readme says that you can just leave them as-is

Because of the amounts of emails where people just wouldn't read the readme, i dumbed it down to non-techy windoza users, and wish anyone advanced will see options with --help.

It says in options help that you need to extract them:

$ gpth --help
# ...
When ready, download all .zips, and extract them into *one* folder.
(Auto-extracting works only in interactive mode)

Then, run: gpth --input "folder/with/all/takeouts" --output "your/output/folder"
...and gpth will parse and organize all photos into one big chronological folder
# ...
-i, --input                   Input folder with *all* takeouts *extracted*. 
# ...

But yeah, kinda my fault, sorry for confusion 😅

[palijn]

regarding Synology indexing :
yes indeed, Synology Photos looks into the /photos shared folder and all the ~/Photos , and will react as soon as a file pops up in there.
That's why I feel it is best to extract and process files outside of these clearly identified folders, and mv the resulting folder into the appropriate one as the last step - which should protect the last modified time information on every file except maybe the root folder, and be extremely fast as long as you kept the folders within the same filesystem (because then no data will actually move at all). Choosing something akin to ~/Takeout and ~/Takeout-processed would normally do the job fine.
You were very right too, to mention that the Media Indexer will by default look for stuff into some specific folders, something most people would not even know.
Those two caveats should definitely be present in a Synology-specific readme.

Edit: I'm using ~ as the universal notation for "your home folder", usually in /home/username .

[brock]

Okay, it looks like I read that too fast and didn't pay close enough attention. I had downloaded the zips into one location, but not yet extracted them. Once I did that, all of the files are now in the Takeout folder.

The issue I'm running into now is that if I run ./gpth-linux --input Takeout --output google-photos it gives me this error:

Setting VM flags failed: Unrecognized flags: input

I explored this a bit yesterday and discovered that the script isn't recognized unless you elevate to the super user. You must instead run it as sudo ./gpth-linux --input Takeout --output google-photos

So it is running for the first time now.

[TheLastGimbus]

discovered that the script isn't recognized unless you elevate to the super user

Umm... aren't you missing chmod +x gpth-linux to give it execute permissions?

[brock]

I did give it executable permissions, but when run as the normal user, the dart script gave that output.

It looks like the permissions were off when I copied it over to the NAS. I ran a chmod 777 gpth-linux though a chmod 644 would probably have sufficed.

[vixius]

Hello, everyone. Thanks for your work. I do not understand many steps due to language and know how. I'm getting freak to fix this problem on my photo folder in synology. Is there some one that could explain me what to do step by step for running it?

[jaimetur]

Repo Statistics

CloudPhotoMigrator

This tool has been designed to Interact and Manage different Photos Cloud services, and allow users to do an Automated Migration from one Photo Cloud service to other or from one account to a new account of the same Photo Cloud service.

As of today, the Supported Photo Cloud Services are:

• Google Photos Takeout

  • Unpack your Takeout Zip files.
  • Process .json files to fix metadata (including creation date and time) of all your assets.
  • Merge Live picture with separate files (.HEIC and .MP4).
  • Separate your assets per Albums (if belong to any album).
  • Organize your assets in a year/month structure for a better organization.
  • Create Symbolic Links for assets within any Album (to save disk space).
  • Detect and remove duplicates.

• Synology Photos - Features included:

  • Upload Album(s)
  • Upload ALL (from folder)
  • Download Album(s)
  • Download ALL (into folder)
  • Remove ALL Assets
  • Remove ALL Albums
  • Remove Empty Albums
  • Remove Duplicates Albums

• Immich Photos - Features included:

  • Upload Album(s)
  • Upload ALL (from folder)
  • Download Album(s)
  • Download ALL (into folder)
  • Remove ALL Assets
  • Remove ALL Albums
  • Remove Empty Albums
  • Remove Duplicates Albums
  • Remove Orphans Assets

• Apple Photos
  (not available yet but is on the ROADMAP.md for next release)

• Google Photos
  (not available yet but is on the ROADMAP.md for next release)

Apart from Manage the different Photo Cloud Services, the Tool also contains some other useful features such as:

• Metadata fixing of any Photo Library in your local drive (not necesarely needs to be a Google Takeout folder)
• Library Organization features:
  • Manage Duplicates assets
  • Splitting of assets with and without associated albums
  • Folder Structure (customizable) for 'Albums' and 'No Albums' folders
• Symbolic Links Support for Albums folders
  • Fix Symbolic Links Broken
• Homogenize Albums folders name based on content
• Remove Empty Albums in Photo Cloud Services
• Remove Duplicates Albums in Photo Cloud Services

Note

The Tool is Multi-Platform and Multi-Architecture, and has been designed to be run directly within a Linux Server or NAS such as Synology NAS (Compatible with DSM 7.0 or higher), so feel free to download the version according to your system.

You can also execute the Tool from a Docker container or from sources files for a better compatibility. In below sections you can find the execution instructions to run the Tool from the different methods.

Live Dashboard Preview:

Download:

Download the tool either for Linux, MacOS or Windows (for both x64/amd64 or arm64 architectures) or Docker version (plattform & architecture independent) as you prefer, directly from following links:

• Latest Stable Release
• Pre-Release
• All Releases

Configuration File:

Youn can see how to configure the Config.ini file in this help section:
Configuration File

Command Line Syntax:

You can check the whole list of functions and arguments with the right syntax here:
Command Line Syntax

All Documentation Links:

• Configuration File
• Command Line Syntax
• Automated Migration Feature
• Google Takeout Management
• Synology Photos Management
• Immich Photos Management
• Other Features

Execution Methods:

There are three different methods to execute this Tool:

• From Compiled Binaries
• From Docker Container
• From Source Repository

The below tables show the pros and cons of each method together with a comparative rating of each one of them for you to decide wich one fits best with your needed:

• Execution Methods Comparison

  Execution Method	Instructions Link	Difficulty	Pros	Cons
  Compiled Binaries	Instructions	🟢 Easiest way	✅ Only basic knowledge on command line commands needed.	❌ Platform and architecture dependent. ❌ Need basic knowledge of running command line instructions. ❌ Some anti-virus may detect the tool as suspicious in Windows systems.
  Docker Container	Instructions	⭐ Recommended	✅ Platform and architecture independent. ✅ Easy configuration via docker.config file (RELEASE_TAG, TIMEZONE). ✅ Automatically pulls latest image if RELEASE_TAG=latest.	❌ Need intermediate knowledge of running command line instructions. ❌ Need to install Docker (if not already installed). ❌ All paths given as arguments must be relative to the execution folder.
  Source Repository	Instructions	🔴 More difficult	✅ Platform and architecture independent.	❌ Need advance knowledge of running command line instructions. ❌ Need to install Git and Python 3.8+ (if not already installed). ❌ Need to pull the source repository again to update to a new release.

• Execution Methods Comparison Rating

  Feature	Compiled Binaries easiest way	Docker Container recommended	Source Repository more difficult
  Platform and architecture independence	⭐☆☆☆☆	⭐⭐⭐⭐⭐	⭐⭐⭐⭐⭐
  Ease of updating to new release	⭐⭐⭐☆☆	⭐⭐⭐⭐⭐	⭐☆☆☆☆
  Allow paths arguments point outside execution folder	⭐⭐⭐⭐⭐	⭐☆☆☆☆	⭐⭐⭐⭐⭐
  No Requires Technical knowledge (Command line syntax)	⭐⭐⭐⭐⭐	⭐⭐⭐☆☆	⭐☆☆☆☆
  No Requires additional tools/software	⭐⭐⭐⭐⭐	⭐⭐⭐☆☆	⭐☆☆☆☆
  No Risk of Antivirus alert (especially on Windows)	⭐⭐☆☆	⭐⭐⭐⭐⭐	⭐⭐⭐⭐⭐
  Average Rating	⭐⭐⭐⭐☆ (3.5)	⭐⭐⭐⭐☆ (3.7)	⭐⭐⭐☆☆ (3.0)

Main Use Case: Automated Migration Feature

Note

Automated Migration Feature

From version 3.0.0 onwards, the Tool supports a new Feature called 'Automated Migration'.

Use the argument '--source' to select the <SOURCE> and the argument '--target' to select <TARGET> for the Automated Migration Process to Pull all your Assets (including Albums) from the <SOURCE> Cloud Service and Push them to the <TARGET> Cloud Service (including all Albums that you may have on the Cloud Service).

• Possible values for:

  • <SOURCE> : ['synology-photos', 'immich-photos']-[id] or <INPUT_FOLDER> (id=[1, 2] to select which account to use from the Config.ini file).
  • <TARGET> : ['synology-photos', 'immich-photos']-[id] or <OUTPUT_FOLDER> (id=[1, 2] to select which account to use from the Config.ini file).

• The idea is complete above list to allow also Google Photos and Apple Photos (iCloud), so when this is done, the allowed values will be:

  • <SOURCE> : ['synology-photos', 'immich-photos', 'google-photos', 'apple-photos']-[id] or <INPUT_FOLDER> (id=[1, 2] to select which account to use from the Config.ini file).
  • <TARGET> : ['synology-photos', 'immich-photos', 'google-photos', 'apple-photos']-[id] or <OUTPUT_FOLDER> (id=[1, 2] to select which account to use from the Config.ini file).

If you ommit the suffix -[id], the tool will assume that account 1 will be used for the specified client (ie: --source=synology-photos means that Synology Photos account 1 will be used as <SOURCE> client.)

Also, you can ommit the suffix -photos in both <SOURCE> and <TARGET> clients, so, you can just use --source=synology --target=immich to set Synology Photos account 1 as <SOURCE> client and Immich Photos account 1 as <TARGET> client.

By default, the whole Migration process is executed in parallel using multi-threads (it will detect automatically the number of threads of the CPU to set properly the number of Push workers.
The Pull worker and the different Push workes will be executed in parallel using an assets queue to guarantee that no more than 100 assets will be temporarily stored on your local drive, so you don't need to care about the hard disk space needed during this migration process.

By default, (if your terminal size has enough width and heigh) a Live Dashboard will show you all the details about the migration process, including most relevant log messages, and counter status. You can disable this Live Dashboard using the flag '-dashboard=false or --dashboard=false'.

Additionally, this Automated Migration process can also be executed secuencially instead of in parallel, so first, all the assets will be pulled from and when finish, they will be pushed into , but take into account that in this case, you will need enough disk space to store all your assets pulled from service.

Also, take into account that in this case, the Live Dashboard will not be displayed, so you only will see the different messages log in the screen, but not the live counters during the migration.
and execute this feature, the Tool will automatically do the whole migration job from <SOURCE> Cloud Service to <TARGET> Cloud Service.

Warning

If you use a local folder <INPUT_FOLDER> as source client, all your Albums should be placed into a subfolder called 'Albums' within <INPUT_FOLDER>, creating one Album subfolder per Album, otherwise the tool will no create any Album in the target client.

Example:
<INPUT_FOLDER>/Album1
<INPUT_FOLDER>/Album2

Important

It is important that you configure properly the file 'Config.ini' (included with the tool), to set properly the accounts for your Photo Cloud Services.

ROADMAP:

v4.0.0:

Release Date: (estimated)

• Alpha version. : (No estimated date)
• Beta version : (No estimated date)
• Release Candidate: (No estimated date)
• Official Release : (No estimated date)

TODO:

• Include Apple Support (initially just for downloading)
  • Create Class ClassApplePhotos with the same methods and behaviour as ClassSynologyPhotos or ClassImmichPhotos. (volunteers are welcomed)
  • -adAlb, --apple-download-albums
  • -adAll, --apple-download-all
  • -auAlb, --apple-upload-albums
  • -auAll, --apple-upload-all
• Include native support for Google Photos through API
  (See: https://max-coding.medium.com/loading-photos-and-metadata-using-google-photos-api-with-python-7fb5bd8886ef)
  • Create Class ClassGooglePhotos with the same methods and behaviour as ClassSynologyPhotos or ClassImmichPhotos. (volunteers are welcomed)
  • -gdAlb, --google-download-albums
  • -gdAll, --google-download-all
  • -guAlb, --google-upload-albums
  • -guAll, --google-upload-all
• Allow Google Photos and Apple Photos as TARGET in AUTOMATED-MODE
• Add option to filter assets in all Immich Actions:
  • by Dates
  • by Country
  • by City
  • by Archive
  • by Person
• Update README.md
• Update RELEASES-NOTES.md

Credits

I hope this can be useful for any of you.
Enjoy it!

(c) 2024-2025 by Jaime Tur (@jaimetur).
Part of this Tool is based on GPTH Tool by TheLastGimbus

Donation / Sponsor:

If you consideer that this Tool has helped you, you can also consider donating me with a ☕
I spent a lot of time developping this Tool for free, so donations will contribute to motivate me to continue working on this project 💖

[vlad-manolache]

Do you know why this gets flagged as a Trojan, for the windows and linux executables?

[jaimetur]

Weird, first notice that I have of that. Let's see if it happens to anyone else.

[aksdroid]

yes, It is getting flagged. :(

[vixius]

Hi, thanks for the great work in primis!! btw: Getting this "cannot execute binary file: Exec format error" I followed all the instruction.. I'm on a Mac by ssh Synology. Files under Zip_Files command that I used: ./OrganizeTakeoutPhotos --zip-folder ./Zips --takeout-folder ./Takeout --albums-structure year/month Any help?

[vixius]

tried on Mac M1, apple recognize like a malware and killed it

[vixius]

I'm trying from windows but don't know hot to start the script by double click on file app in folder it start than it ask if want to continue than it crash and close

[jaimetur]

If you want to run it from Windows you should open a CMD or PowerShell terminal and execute the script with the propper arguments.
FYI: I'm working on a Linux_arm64 version. Hopefully I could finish it soon. Keep you posted.

[vixius]

If you want to run it from Windows you should open a CMD or PowerShell terminal and execute the script with the propper arguments. FYI: I'm working on a Linux_arm64 version. Hopefully I could finish it soon. Keep you posted.

That's so nice. Thank you so much for supporting me. About windows I'm reading how to use cmd and its command.
Is it possible on windows to run it from folder in external SSD? because don't have enough space on laptop windows to put on zips folder (about 250gb)

[vixius]

If you want to run it from Windows you should open a CMD or PowerShell terminal and execute the script with the propper arguments. FYI: I'm working on a Linux_arm64 version. Hopefully I could finish it soon. Keep you posted.

Where is the mistake :( ?

[jaimetur]

In Windows you have you use back slash “\” instead of “/“ and you don’t need to start the command with ./ El 4 ene 2025, 15:13 +0100, vixius ***@***.***>, escribió:

…

> If you want to run it from Windows you should open a CMD or PowerShell terminal and execute the script with the propper arguments. FYI: I'm working on a Linux_arm64 version. Hopefully I could finish it soon. Keep you posted. Where is the mistake :( ? image.png (view on web) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[vixius]

Thanks, I think is finally working.... I'm testing on windows to learn how it work your great job. But then will wait for your nas version.
Thanks a lot, you can't imagine how much your work is useful

[vixius]

so nice to see this 👍
Thanks again

[jaimetur]

Happy to see that at least Windows version works for you.
Can you try now to download linux_arm64 versoin and let me know if it works?

[vixius]

Happy to see that at least Windows version works for you. Can you try now to download linux_arm64 versoin and let me know if it works?

Yeeees It works like a charme, Great Job! I'd like to offer you a beer!
Is there a way to check duplicates inside photo folder in nas? Because now I have some foto from iPhone already in photo folder in as and other from google takeout. But is it possible to do a duplicate check directly on photo folder on nas?

[jaimetur]

Thanks. Yes, you can check duplicates in any folder(s). You can provide one or more folder and the script will look for duplicates in all of them. Give more priority to the file found in the first folder. Check the —help section or the readme.md for more info. El 6 ene 2025, 22:09 +0100, vixius ***@***.***>, escribió:

…

> Happy to see that at least Windows version works for you. Can you try now to download linux_arm64 versoin and let me know if it works? Yeeees It works like a charme, Great Job! I'd like to offer you a beer! Is there a way to check duplicates inside photo folder in nas? Because now I have some foto from iPhone already in photo folder in as and other from google takeout. But is it possible to do a duplicate check directly on photo folder on nas? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jaimetur]

Added Release 2.3.0 to OrganizeTakeoutPhotos Script

Release Notes:

Release: 2.3.0
Date: 2025-01-14

• Removed EXIF Tool (option -re, --run-exif-tool) for performance issues
• Added new argument to show script version (-v, --version)
• Added new argument to Extract Albums from Synology Photos (-sea, --synology-extract-albums)
• Renamed argument -ca, --create-albums-synology-photos to -sca, --synology-create-albums
• Renamed argument -de, --delete-empty-albums-synology-photos to -sde, --synology-delete-empty-albums
• Renamed argument -dd, --delete-duplicates-albums-synology-photos to -sdd, --synology-delete-duplicates-albums
• Added Pagination option to Help text
• Code refactored
• Minor Bug Fixing

Download Script:

Download the script either Linux, MacOS or Windows version (for both x64/amd64 or arm64 architectures) as you prefeer directly from following links:

Linux::

• Download AMD 64 bits version
• Download ARM 64 bits version

Mac OS:

• Download AMD 64 bits version
• Download ARM 64 bits version

Windows:

• Download AMD 64 bits version

Full Changelog: jaimetur/CloudPhotoMigrator@1.2.0...2.3.0

[b4urock]

Hello!

First of all, thank you for your work @jaimetur.

I did everything on my PC and it works like a charm. I'm stuck at the last step, the extra mode -ca to create the albums on Synalogy Photos.

I tried it on version 2.2.1 and 2.3.0, but I'm getting connection errors. My Synology.config file is properly configurated and I tried both in Powershell SSH running on Windows and Linux ARM versions and the result is the same. I've disabled firewall, and 2-factor authentication with no results.
It seems it doesn't recognize my password, so I typed again when asked but the result is the same although the password is correct.

Here is the execution log:

The indexing service is properly started on my NAS as stated in the log but I'm getting the error. Can you help me?

[jaimetur]

Hi Pablo, are you using as username any user with access to Synology Photos? It is weird since if you can connect to Synology Photos throught web interface with that username and password, you should also connect to it using the script. From the log attached it is difficult for me to get more details of the error

[b4urock]

Thank you for your reply @jaimetur

Yes, I'm using a user with access to Syanalogy Photos and admin privileges. Although the password is correct in the config file, it still asks me to type it again, and I do it, but with no success.

Log
INFO: Script running on Linux system in a Synology NAS
INFO: Flag detected '-ca, --create-albums-synology-photos'. The Script will look for any Subfolder in './Photos/Albums' and create an Album with each subfolder name in Synology Photos database.

ATTENTION!!!: This process will connect to your to your Synology Photos account and will create a new Album for each Subfolder found in './Photos/Albums' and will include all Photos and Videos included in that Subfolder.

Do you want to continue? (yes/no): yes
INFO: Continuing...
INFO: Create Albums Mode detected. Only this module will be run!!!

INFO: Find Albums in Folder : ./Photos/Albums

INFO: Looking for NAS config file: 'Synology.config'
INFO: NAS_IP : 192.168.1.XX
INFO: USERNAME : xxxxxx
INFO: PASSWORD : *************
INFO: ROOT_PHOTOS_PATH : /volume1/homes/xxxxx/Photos
ERROR: Unable to Authenticate in NAS with the providen data: {'error': {'code': 400}, 'success': False}
INFO: Albums Folder Path: './Photos/Albums
INFO: Reindexing Synology Photos database before to add content to it...
ERROR: Unable to Authenticate in NAS with the providen data: {'error': {'code': 400}, 'success': False}
ERROR: Unable to Authenticate in NAS with the providen data: {'error': {'code': 400}, 'success': False}
ERROR: Error Starting Reindex: {'code': 119}
Password:
INFO: Reindexing started in Synology Photos database for user: 'xxxxx'.
INFO: This process may take several minutes or even hours to finish (depending of number of files tonindex). Please be patient...
INFO: Starting Reindex with command: 'sudo synowebapi --exec api=SYNO.Foto.Index method=reindex version=1 runner=xxxxxxx type=basic'
ERROR: Error geting Reindex Status.
INFO: Albums creation on Synology Photos Finished!.
Traceback (most recent call last):
File "OrganizeTakeoutPhotos.py", line 802, in
File "OrganizeTakeoutPhotos.py", line 265, in main
File "OrganizeTakeoutPhotos.py", line 690, in mode_create_albums
File "SynologyPhotos.py", line 414, in create_synology_photos_albums
UnboundLocalError: local variable 'albums_crated' referenced before assignment
[PYI-30865:ERROR] Failed to execute script 'OrganizeTakeoutPhotos' due to unhandled exception!

You saved me from a lot of work already, so if this last step doesn't work, I'll create the albums manually. ;)

Thank you

[jaimetur]

I have already published release 3.0.0-alpha. Take into account that this is a pre release in alpha status, so you may expect some bugs and some functionalities not finish yet, but if you want to try it, feel free to download the latest version from: https://github.com/jaimetur/CloudPhotoMigrator

[MingFu64]

Hi new to Synology, been awhile since I’ve worked with Linux. Connecting to a DS223 (DSM Ver 7.2.2-72806) with an M2 Mac Mini via SSH. Script version 2.3.0_linux_arm64.

I have the script folder in the same folder as the Takeout Folder. Used the following command.
./OrganizeTakeoutPhotos_v2.3.0_linux_arm64.run -t ../Takeout/

Got to Step 3 and encountered the following error
OSError: [Errno 8] Exec format error: '/var/tmp/_MEIToMREB/gpth_tool/gpth_linux.bin'
[PYI-7425:ERROR] Failed to execute script 'OrganizeTakeoutPhotos' due to unhandled exception!

Any help/guidance would be appreciated. TIA

[jaimetur]

Are you sure that you are using the right architecture? Can you try with amd64 instead of arm64? On the other hand, is not a good idea to run the script from the same takeout folder, I would move it on folder up, because there is some options that make the script to delete takeout folder when finish.

[MingFu64]

I double checked the processor in the DS 223 I’m running and it’s the RTD1619B SoC which is an ARM 64-bit according to ChatGPT.

I did try to download the Linux AMD version and got the following error
-sh: ./OrganizeTakeoutPhotos_v2.3.0_linux_amd64.run: cannot execute binary file: Exec format error

Folder structure wise I currently have \Temp\OrganizeTakeoutPhotos\ and \Temp\Takeout. Are you suggesting the script needs to be up one level where the \Temp folder is located? I tried moving the script .run file up one level but it didn’t seem to make difference. Still had the same error as before. The complete message I see is the following

===========================================
3. FIXING PHOTOS METADATA WITH GPTH TOOL...

INFO: Running GPTH Tool from 'Takeout' to 'Takeout_fixed_20250127-185542'...
Traceback (most recent call last):
File "OrganizeTakeoutPhotos.py", line 935, in
File "OrganizeTakeoutPhotos.py", line 371, in main
File "OrganizeTakeoutPhotos.py", line 296, in get_and_run_execution_mode
File "OrganizeTakeoutPhotos.py", line 465, in mode_normal
File "Fixers.py", line 61, in fix_metadata_with_gpth_tool
File "subprocess.py", line 493, in run
File "subprocess.py", line 858, in init
File "subprocess.py", line 1704, in _execute_child
OSError: [Errno 8] Exec format error: '/var/tmp/_MEIYdlZz5/gpth_tool/gpth_linux.bin'
[PYI-7081:ERROR] Failed to execute script 'OrganizeTakeoutPhotos' due to unhandled exception!

[jaimetur]

I have already published release 3.0.0-alpha. Take into account that this is a pre release in alpha status, so you may expect some bugs and some functionalities not finish yet, but if you want to try it, feel free to download the latest version from: https://github.com/jaimetur/CloudPhotoMigrator

[jaimetur]

Hi again, I guess that you already solved your Google Takeout processing issues, but just in case that you are still interested, let me introduce you a new very refreshed and improved version of the tool CloudPhotoMigrator (former OrganizeTakeoutPhotos). You can find more information about this new release and the documentation here: https://github.com/jaimetur/CloudPhotoMigrator All the feedback that you can provide is more than welcomed. Saludos, Jaime Tur ***@***.*** El 27 ene 2025, 14:12 +0100, MingFu64 ***@***.***>, escribió:

…

Since I'm running this on the Synology (DS223) I checked with ChatGPT to make sure I had the right architecture. I downloaded the Linux AMD64 based on the following. "The Synology DS223 is powered by a Realtek RTD1296 processor, which is a Quad-Core ARM Cortex-A53 chip. It operates at 1.4 GHz and has a 64-bit architecture. This makes the DS223 capable of handling a variety of tasks efficiently while supporting the 64-bit capabilities for modern applications and larger memory configurations." Folder structure wise I currently have \Temp\OrganizeTakeoutPhotos\ and \Temp\Takeout. Are you suggesting the script needs to be up one level where the \Temp folder is located? I can try both suggestions and circle back later. Thanks — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>