You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default behaviour of the rename step is to use what was specified in the --action argument.
But even if the user specified copy as that action, when temporary files are created (e.g. the target was a zip file instead of a singular video file), this can be optimized to a move if cleanis enabled since it will be deleted afterwards anyhow.
This would avoid doing an unnecessary copy.
The text was updated successfully, but these errors were encountered:
If input/output are on different filesystems, you won't get around making a physical copy.
If input/output are on the same filesystem then you should be using --action hardlink anyway.
The --action duplicate option is used in all examples to avoid the inefficiencies of physical copy operations if avoidable.
The default behaviour of the rename step is to use what was specified in the
--action
argument.But even if the user specified
copy
as that action, when temporary files are created (e.g. the target was a zip file instead of a singular video file), this can be optimized to amove
ifclean
is enabled since it will be deleted afterwards anyhow.This would avoid doing an unnecessary copy.
The text was updated successfully, but these errors were encountered: