Hmmm... Strange, but that did work.

Havent used filebot in a few months. Just renewed my license and took her for a spin. Got the following message: filebot -script 'fn:amc' /volume1/video/Series/TMP/ --output /volume1/video/Series --action move -non-strict --order Airdate --conflict auto --lang nl --def 'ut_label=TV' 'music=y ...

I see. name@SynoResource files are not recognized as known clutter files, so the cleaner script will leave them alone, which then prevents the rest of the folder hierarchy from being deleted. I'll add that pattern to the cleaner script. At this point in time, there is no easy solution for you ...

Yeah, I am a bit used to it already
I'll wait for the update.

Tnx!

Did some reading but it's very complicated (if possible) to remove those directories and to stop them from being created.
Is there a possibility that Filebot Node can delete these if present?

Source: https://community.synology.com/enu/foru ... ort=oldest

Jup, he add's the @eaDir folder. Probably because of the indexing station. admin@CB-NAS:~$ find /volume1/video/Series/TMP/ /volume1/video/Series/TMP/ /volume1/video/Series/TMP/What.If.2021.S01E02.What.If.TChalla.Became.a.Star-Lord.1080p.DSNP.WEBRip.DDP5.1.x264-FLUX[rarbg] /volume1/video/Series/TMP ...

OMG you are right...

Currently this (while it's empty), but I will add two newly downloaded folders.

This behavior started when I upgraded to DSM 7.
But OK, I tested and there is no @eaDir in the folders that are not deleted.
I am also not remote SMB-in to these folders, I do everything from DSM.

First of all, thank you for your help! If that were the case, then ALL my folders magically have hidden files :) I will share with you the console log, in this case, subfolder2 = yrte AND Folder1 = What.If.2021.S01E03.What.If.The..World.Lost.Its.Mightiest.Heroes.1080p.DSNP.WEBRip.DDP5.1.x264-FLUX ...

Nope, Folder1 is not deleted and is completely empty... I think it's a bug on DSM 7? idk.
This is new behavior by the way... It has worked well for a few years now

Sorry, I really do not know how to test: --def clean=y Before I went to DSM 7, Filebot Node did clean up the directory Volume1/Series/TMP. Ok, let's say I have the following structure: Volume1/Series/TMP/Folder1/Subfolder2 Within Folder1 there is a movie file, Filebot node finds it and renames and ...

Jup, it does cleanup except the root folders within the folder that I am checking.

He does cleanup, but not the folders... Lemme test once more.

Ehhhmmm... Where do I type that?

Ohh how stupid, those fields were pre-populated after re-installing so I did not notice...
It works now! Tnx!

Only the cleanup does not work anymore (it did on DSM 6.x but never on 7).

Got it to work after completely uninstalling, restarting my NAS and re-installing the lot. But now I have a new problem. Invalid usage: output folder must exist and must be a writable directory I removed the rights of the filebot user (because I had set them before (also on DSM 7), and re-added the ...

Hi,

I had Filebot Node running on DSM 7, I needed to restore all my settings
Now I wanted to upgrade and got the message: to remove something by running: sudo rm -v /usr/local/etc/nginx/conf.d/dsm.filebot-node.conf
Did that, and now when I run Filebot Node I get the message: Not found

What to do?

Ok, it does... Just run the Java installer twice

This does not work
They all give an error...

Cool!

Direct works... perhaps it was a caching issue
I did not know of the direct link! Cool.

Thank you very much!

I stil get "Sorry the page you are looking for is not found".

Not working here... with the test version (0.2.0)