| On this page |
Tip
You may want to avoid using destructive file operations such as move/rename and remove. They can make files appear to be missing, triggering the dependency system to do extra work. They can also make it harder to debug the network after it runs if intermediate files are not where they were.
This node can work in two different ways:
Do the rename(s) whenever the node generates work items (Async rename off)
The node tries to rename the files synchronously when it generates work items (including when you choose TOPs ▸ Generate Static Work Items), blocking until the renaming is done. This can lead to the node working once and then erroring because the "source" file has been moved/renamed.
Do the rename(s) inside work items (Async rename on)
The node performs the renames asynchronously at runtime.
TOP Attributes
|
|
string |
The directory where the source file will be moved |
|
|
string |
The extension of the destination file |
|
|
filename |
The filename of the destination file |
Parameters
Original File Path
The path to the file to move/rename.
New File Path
The new path of the file. This is used as the output of the work item(s).
Result Data Tag
The file tag to assign to the output filename.
Async Rename
When this is off, the node tries to rename the files synchronously when it generates work items (including when you choose TOPs ▸ Generate Static Work Items), blocking until the renaming is done. This can lead to the node working once and then erroring because the "source" file has been moved/renamed. When this is on, the renames are performed asynchronously at runtime (potentially on a render farm).
Examples
example_top_filerename Example for File Rename TOP node
This example demonstrates how to use the File Rename node to rename a group of files.
The following examples include this node.
example_top_filerename Example for File Rename TOP node
This example demonstrates how to use the File Rename node to rename a group of files.
