Running, Part V, VI, VII
This commit is contained in:
parent
779449c19a
commit
2f8aeedf43
29
README
29
README
@ -120,16 +120,39 @@ The steps required for each file depend on the format and destination parameters
|
||||
decoded/resampled file) to 3 (if format can't be decoded using sox and
|
||||
resampling/normalization is required) tasks.
|
||||
|
||||
V. Running tasks
|
||||
----------------
|
||||
V.1 Running tasks
|
||||
-----------------
|
||||
While running tasks, AtOM responds to the following keypresses:
|
||||
+/- Increase/decrease max-load
|
||||
q Quit (will skip all following steps)
|
||||
|
||||
Progress display:
|
||||
L:<current load>/<max-load>
|
||||
W:<active workers>/<concurrency>
|
||||
T:<last task>/<task count> (F:<failed tasks>)
|
||||
<pct>% <remaining time> (A:<average task duration>s/task)
|
||||
ETA:<estimated time of arrival>
|
||||
|
||||
V.2 Renaming files
|
||||
------------------
|
||||
If rename pattern (or FAT32 compatibility) for one or more destinations has
|
||||
changed, files already transcoded will be renamed. Otherwise, this step is
|
||||
skipped.
|
||||
|
||||
VI. Copies
|
||||
----------
|
||||
During that stage, files which mime-types matched copy_mime-type directives are
|
||||
copied (symlinked where possible) to the destination.
|
||||
When a rename pattern is defined and impacts path, files that are not in the
|
||||
same directories as files which have been successfully transcoded are ignored,
|
||||
as AtOM cannot guess what the destination path should be. Otherwise, files are
|
||||
copied with their name and path unchanged.
|
||||
|
||||
VII. Obsolete files 2
|
||||
-------------------
|
||||
|
||||
Whenever a file is transcoded, if it was already present in the database but its
|
||||
name changed, following a rename pattern change, the old file is removed during
|
||||
that stage.
|
||||
|
||||
====
|
||||
Toys
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user