I was able to get it to work like this.

Thank you, so much, Red!

Hello, I get an error message described in the title when I run jlesage/docker-filebot https://github.com/jlesage/docker-filebot?tab=readme-ov-file for hardlinks. https://snipboard.io/8Szs43.jpg https://snipboard.io/F3lkEv.jpg https://snipboard.io/zZioVf.jpg It seems to be fine when I run it through ...

I see. Thank you, for the explanation.

I’ll try Docker filebot-watcher.

Could this be the reason for the error?



The original files are located in .../_Remux/_test

edit: oops, nevermind. They're both 'media' folders. hmm

Thanks for the reply, Red. https://snipboard.io/xMsaeA.jpg https://snipboard.io/7tDBE0.jpg https://snipboard.io/z8WsMo.jpg I think when I ran for the first time after changing the network folder path using the folder icon it created a folder (as I requested), but no actual file was hardlinked. And ...

I have the same issue with the OP with my Synology. https://snipboard.io/aNQZwA.jpg https://snipboard.io/Hc0UWX.jpg https://snipboard.io/i0uqne.jpg I'm running the Non-MAS FileBot on MacOS 14.4, and I CAN rename files on mount volumes (Synology) via MacOS Finder. I have NOT done the FileBot 'folder ...