Post Rename Reference

Running FileBot from the console, Groovy scripting, shell scripts, etc
Post Reply
Raptor6L
Posts: 2
Joined: 30 May 2026, 06:01

Post Rename Reference

Post by Raptor6L »

Hi Rednoah

It's taken a while to figure it out but I've got your AMC script working as the part of a larger process. Pretty neat!
I'm wondering if there is a way to reference the file\ folder after AMC has renamed it?
Example: AMC sees the title from qbt using this reference "ut_title=%N", but "ut_title=%N" remains the original (old) title.

Thanks
Raptor6L
User avatar
rednoah
The Source
Posts: 24574
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Post Rename Reference

Post by rednoah »

The -exec custom post-process commands manual is a good way to get started with custom post-process commands.


e.g.

Shell: Select all

-exec /path/to/script.sh {f} {historic.f} {json}
{f} is the new file path
{historic.f} is the previous file path
{json} is the xattr metadata


:idea: "ut_title=%N" is notably not the file name / file path. %N typically refers to the download name which may or may not be the same as the actual file name / directory name. The ut_title variable is notably largely unused by the amc script but we do pass it along in all the examples because there's no reason not to. You can access that field from your format / exec / etc expression via the {defines.ut_title} binding.
:idea: Please read the FAQ and How to Request Help.
Raptor6L
Posts: 2
Joined: 30 May 2026, 06:01

Re: Post Rename Reference

Post by Raptor6L »

rednoah wrote: 30 May 2026, 07:07 The -exec custom post-process commands manual is a good way to get started with custom post-process commands.


e.g.

Shell: Select all

-exec /path/to/script.sh {f} {historic.f} {json}
{f} is the new file path
{historic.f} is the previous file path
{json} is the xattr metadata
Excellent, that I can have a play with.

Thank you again!
Post Reply