FileBot

on linux filebot works fine, on windows however filebot alwas create extra unwanted files with following extentions .mtime, .mediadata, .mediainfo, .filename
in post proccess everything is unchecked.

its a lot off work always to delete these files.

Renaming should only rename without creating these files.

version i use is 5.2.3 x64

You seem to be referring to xattr metadata. These extended file attributes would normally not appear as files in the file system, unless perhaps if you're using a strangely configured remote network file system?

The behaviour you are seeing is not default behaviour that other users are seeing. FileBot itself does not write .mtime, .mediadata, .mediainfo, .filename files, but your SMB remote file system implementation / configuration might do so in response to FileBot trying to write extended file attributes.



What software or device are you using? What network protocol are you using for your network share? SMB? What is your SMB configuration on the server-side? What file system are you using on the server-side?



You can either disable xattr metadata on the client-side in FileBot (i.e. mitigating the symptom rather than fixing the root cause) or you could correctly configure your SMB service to either disable or better handle NTFS Alternate Data Streams. See vfs objects = streams_xattr and vfs objects = streams_depot for details on that.

FileBot on windows 10 en remote nfs shares.
remote is my unraid server.
In linux mint with nfs it is working great, also on unraid with filbot in docker.

So the problem is windows. Als when i create files/ folders on a nfs share in windows , windows make them read only.

Gues , i'll have to use my main computer (linux) for this job. Windows is mainly for watching NF,CrRoll and viki .
Thanks for reply.

NFS on Windows? That's pretty rare. If you look into NTFS ADS and then see if you can configure how that that is handled by your NFS client-side file system driver and NFS server you might find a good solution.


That said, since NFS on Windows is pretty much unknown territory for me, I'd probably just disable xattr metadata as an easy walk-around. Alternatively, switching to SMB will likely fix the issue as well.


You can run this command on your Windows machine to create a configuration file that permanently disables xattr metadata: ** see Advanced Settings for details