When scanning, clustercode will look for files that end with these extensions. Only the file name matters, not what is in the files. If the files are not video files, ffmpeg will likely fail. Do not provide a leading dot . before the extensions in the setting. Only the last part after the last dot in the file will count as extension.

When a clustercode node has converted a video, all other nodes (including itself) need to know which media have already been processed. One way to ensure that the same media will not get picked again is to create an empty file that matches exactly the original file name and add a special extension. If clustercode detects a video file, but there is another file with the same name but with this skip extension, it won’t get in the list of possible processing candidates. This is why clustercode needs write permissions on the input directories. No other files will be touched, deleted or otherwise modified.

ffmpeg needs some parameters to know how to convert the input files. These parameters are stored in profiles. If you want to create custom ones, copy from the included profiles and start modifying from them.

This is the interval in minutes if no suitable media could be found before and after encoding. If a new video has been added in the meantime, it will be picked up at the next scan.

The setting accepts certain space-separated strings of pre-defined entries. The order in which they are specified does matter. The search for profiles will stop as soon as one is found in the matcher. So if you specify COMPANION DEFAULT DIRECTORY_STRUCTURE The profile scanner will never look in the subdirectories of /profiles if the default profile exists.