rednoah wrote: ↑04 Jan 2019, 08:14
Try changing:

Code: Select all

-Dnet.filebot.xattr.store=.xattr

to:

Code: Select all

-Dnet.filebot.xattr.store=X:/MyXattrFolder

and see what happens.

This worked beautifully on Win10. Would you have any idea where this is stored or how to change it in Mac OS? I'm digging around in preferences, so far no luck.

Your suggestion worked perfectly, running filebot on Win10 with GDFS. The xattr data is written to a folder at the designated location.

Thank you!

Final query. I can post it as another topic if preferred. Would it be possible to tell filebot where to write/read the .xattr folders/files? Similar to what is done with logs and exclude lists. This would allow storing the xattr data in a separate tree where it could be used/referenced separately ...

Understood. I sadly use the custom naming. My choice, so I accept the implications.

In any case, love filebot. Tx

Apologies: Rebooted after the latest env settings, then reran the script. Working correctly now, thank you. Thank you for clarifying --conflict auto vs the duplicates script. I did misunderstand, thinking that amc included choosing the 'best' version of the same episode or movie. No problem, will ...

I set the environment variable manually, then ran the script again. Same error. I then ran your setx command above, ran the script, same error. It's not critical at the moment as the result is fine for now. But without xattr I imagine the quality compare feature of the amc script would not work as ...

Thanks for the quick reply. "Are you sure that FILEBOT_OPTS is set to -Dnet.filebot.xattr.store=.xattr? Please check your Windows Environment Variables." There is no evidence of FILEBOT_OPTS in Windows Environment Variables. I installed from this link, the X64.msi version. https://get.filebot.net ...

Using filebot r5991 on Windows 10 with GDFS. Filebot amc is working correctly, in that it renames and moves files from one Google Team Drive to another with correct ID and metadata in the filename, and cleans residual files. Thank you. It seems to be doing so with fairly minimal data pulled from GD ...