FileBot

Lately since updating to 4.0 i have been getting the following error when using my script to rename and move files after they have been downloaded:
Which in turn would seem to cause the file to not have the proper creation date. (creation date comes out as 01/01/year of modified date)The files is still moved and renamed. The issue seems to be absent in 3.8 (tried with same file running my script manually and file transfers with proper creation date and no errors)

You can ignore this warning, it's just trying to set extended attributes (i.e. tags). But I guess this is a samba drive or FAT32 FS so it doesn't work. That's normal, so it's just a warning you can ignore.

It should be setting CreationDate to the episode airdate / movie release year. But if it's a Samba drive on a Linux server (which doesn't support CreationDate) it might just default that to last Modified.

You can add -no-xattr to your filebot call to disable these features.

rednoah wrote:You can ignore this warning, it's just trying to set extended attributes (i.e. tags). But I guess this is a samba drive or FAT32 FS so it doesn't work. That's normal, so it's just a warning you can ignore.

It should be setting CreationDate to the episode airdate / movie release year. But if it's a Samba drive on a Linux server (which doesn't support CreationDate) it might just default that to last Modified.

You can add -no-xattr to your filebot call to disable these features.

Its a WHS2011 and its moving the files to a pooled drive which has full ntfs permissions (using PoolHD). This doesnt happen with version 3.8 and at first didnt happen with 4.0 till recently. Anyways i reverted to 3.8 for now since the creation date is important for media center applications to tag the movie as latest.