Page 1 of 1

Filter List, Only Items Needing Renaming

Posted: 08 Feb 2020, 00:39
by arrmo
Hi,

After I have selected the source directory, and matched items ... is there a way to filter the rename list to only those items that will be renamed? Meaning ... of 195 of 200 items show a green arrow (nothing to be done), how to filter the list to only show the 5 that will be renamed?

Thanks!

Re: Filter List, Only Items Needing Renaming

Posted: 08 Feb 2020, 00:57
by rednoah
Unfortunately, there is no such filter.


:idea: You could however filter by "files not yet xattr tagged" which means you'll only ever get files that haven't yet been processed with FileBot and thus already xattr tagged.


:idea: Typically, you'd have separate input / output directories, loading files in from the input folder, organizing files into the output file structure, in one go. This way, your input folder only ever has new files needing to be renamed, and your output folder only ever contains files well-name and organized by FileBot.

Re: Filter List, Only Items Needing Renaming

Posted: 08 Feb 2020, 01:01
by arrmo
Hi,

Yes, that makes sense - no argument here. I admit, as I am using Plex, it sorts / organizes the files automatically ... but once in a while it "messes" up a name or two. So every so often I go in and correct it, but then I do see quite a lengthy list of items that don't need to be renamed, and a few that do.

Thanks!

Re: Filter List, Only Items Needing Renaming

Posted: 08 Feb 2020, 08:06
by rednoah
Ah yes, if you're using Plex, then you definitely want to haver a dedicated Plex folder, and and a dedicated Input folder, so that files that appear in Plex always have to go through FileBot first.

e.g. use an absolute format like this to move & rename in one go from any location:

Code: Select all

/path/to/Plex/{plex}

Re: Filter List, Only Items Needing Renaming

Posted: 08 Feb 2020, 11:48
by arrmo
OK, that makes sense. I admit, have to think about it a bit, as I have multiple users (family members ... LOL). And as I only rename once a month or so - not sure if this will block them from watching their shows or not (until I get around to renaming).

Thanks!!

Re: Filter List, Only Items Needing Renaming

Posted: 08 Feb 2020, 12:51
by rednoah
Time to set up some sort of automation. ;)

Have an incoming folder that everyone has read/write access to, so everyone can drop their files, and then make your Plex destination folder read-only, so nobody can write files there (except filebot running locally on the NAS). Then you can set up automation somehow, either via regular cron tasks, or manually kicking off filebot somehow on demand.

Re: Filter List, Only Items Needing Renaming

Posted: 08 Feb 2020, 15:28
by arrmo
That makes sense, will dig more. And I admit, wondering in the back of my mind if I can integrate this with my post-processing script (that transcodes to save space, removes commercials).

Thanks!

Re: Filter List, Only Items Needing Renaming

Posted: 07 Nov 2022, 23:43
by GaryMac
Over 2 years later, and I'm looking to know same thing.

If I run 100s of movies through the match process, then in the "rename" panel on the right, I only want to see the files that are slated to have their names changed, not the titles with the green mark that are staying the same.

Someone offered a workaround, but I would need more detailed instructions on how to accomplish that.

Re: Filter List, Only Items Needing Renaming

Posted: 08 Nov 2022, 02:16
by rednoah
What is your use case?

You would typically have separate folders for well-organized and not yet well-organized files that need renaming. FileBot will move files from somewhere to well-organized. Those two should never overlap. So already well-named files never need renaming and so you wouldn't drop them into FileBot as input in the first place.

If you use Presets, then you can also use file filter expressions to select / not select files. Note though that "files that need renaming" cannot be known in advance. However, checking for specific file name patterns, or the existence of xattr metadata, etc, might be easy depending in your specific use case.

Re: Filter List, Only Items Needing Renaming

Posted: 08 Nov 2022, 17:11
by GaryMac
Understood. Thanks for the response.

I just have files dumped into alphabetical folders. Occasionally I want to run them through FileBot to catch any that need cleaning up... keeping them in those same folders. It sounds like the person who made this thread is in the same boat.

If it isn't possible after the matching process, for the rename panel to just show the files FileBot wants to change, it's all good, I'll just scroll through the list and look for ones without the green mark.

I was just hoping there was a way to NOT show the ones with a green mark... because they are already done.

Thanks again.

Re: Filter List, Only Items Needing Renaming

Posted: 09 Nov 2022, 03:37
by rednoah
rednoah wrote: 08 Nov 2022, 02:16 If you use Presets, then you can also use file filter expressions to select / not select files. Note though that "files that need renaming" cannot be known in advance. However, checking for specific file name patterns, or the existence of xattr metadata, etc, might be easy depending in your specific use case.
Yes, what you're trying to do should be possible. Because files already processed with FileBot have xattr metadata and files not yet processed with FileBot have not, and so it should be easy to select files based on that.

e.g. use xattr metadata to select / not select files:

Code: Select all

none{ f.metadata }

:?: Can you give us example file names of files that are not yet processed vs files that are already processed?


:?: Do the files that do not need renaming have xattr metadata? Confirmed?


:?: Do the files that do need renaming not have xattr metadata? Confirmed?


Image




EDIT:

:idea: If xattr metadata does not work for you (i.e. you're processing files on a file system that doesn't support xattr) then you may we may still be able to use the {historic} binding to check the given file against the local rename history to check if the file has previously been processed already:

Code: Select all

none{ historic }