Releases · TheTaylorLee/docker-transcodeautomation

The latest tag has been deprecated in favor of the requirement to specify the specific version in your docker compose or docker run command. This will be maintained for all future releases and help enforce breaking changes are not pushed without the release notes being first read.

It is required that the container is first run once with the UPDATEMETADATA=true environment variable applied. After it completes processing files, the variable should be removed and the container restarted. This is necessary for the database and file indexes to be updated with new immutable index numbers.
Failure to follow that step will result in a loss of statistics and files being transcoded a second time.
This will remux comment data. Make a backup prior.

Warning

UPDATEMETADATA does not extend the same protections the normal transcode process does. You should absolutely not migrate without backing up files first.
If you have any file watching services like plex, jellyfin, or emby, TURN THEM OFF during the update-metadata process. File watching can corrupt the files as they are remuxed.

Immutable File Indexing - Filenames (not just folder paths) can now be changed without transcode statistics being lost.
All files will receive a unique index number. Future releases will leverage this to allow the same filename to exist in different directories. Currently all filenames must be unique. (Not currently implemented)
Introduced support for adding files to watched directories without transcoding them. See additional notes in the readme.