This project facilitates CasparCG Server since version 2.2.0. It abstracts the collection of metadata and generation of thumbnails into a separate process.
This project is designed to be used via the AMCP protocol in CasparCG server. However, there are some endpoints for additional data which can only be access directly over http.
The scanner needs a copy of ffmpeg to be able to scan any media files. On windows, a copy of ffmpeg.exe should be placed in the same folder as the scanner executable. On linux, ffmpeg should be made available on the path.
You can override these locations in the scanner configuration.
There are various options that can be changed for the scanner. These can all be set by environment variables or as arguments. Some features are disabled by default and should be enabled in this way.
To change options with arguments use the following syntax: scanner.exe --metadata.scenes true --metadata.sceneThreshold 0.5
The full set of available options and their default values can be found at config.js
By default the scanner expects there to be a casparcg.config file next to the executable to specify the paths to media. To disable use of this file scanner.exe --caspar null
These endpoints are exposed by the AMCP protocol in CasparCG Server. This means that they have some AMCP syntax wrappings, which will likely need to be stripped off if using in an external client
/tls - Lists available template files/cls - Lists available media files/fls - Lists available font files/cinf/<name> - Gets information on specified media file/thumbnail/generate - Backwards compatibility, has no effect/thumbnail/generate/<name> - Backwards compatibility, has no effect/thumbnail - Lists the available thumbnails/thumbnail/<name> - Gets the thumbnail for a media file/templates - Detailed list of templates in JSON format./media - Lists available media files in json form with an enhanced set of metadata/media/info/<name> - Gets the json enhanced metadata for the specified media file/media/thumbnail/<name> - Gets the thumbnail for a media fileA stream of changes can be accessed with the following. Full docs
const PouchDB = require('pouchdb-node')
const db = new PouchDB('http://localhost:8000/db/_media')
// Listen for changes
db.changes({
since: 'now',
include_docs: true,
live: true
}).on('change', function (changes) {
console.log(changes)
}).on('error', function (err) {
// handle errors
});This project uses the latest LTS version NodeJS (18), so you need that installed. Get it from: https://nodejs.org/en/. We also use Leveldown which uses native modules so if you're on Windows you need to install windows build tools:
npm install --global --production windows-build-tools
After this:
casparcg.config file into the root folderyarn installyarn dev to start the development serverBe aware that because of the native extensions, you may only be able to build for the target you are currently on.
yarn buildyarn build-win32-x64yarn build-linux-x64 or yarn build-linux-arm64 depending on cpu architectureThe built files will be placed in ./deploy, make sure you copy all non-zipfiles into the main CasparCG directory.
CasparCG Media-Scanner is distributed under the GNU Lesser General Public License LGPLv3 or higher, see LICENSE for details.
More information is available at http://casparcg.com/
The most up-to-date documentation is always available at https://github.com/CasparCG/help/wiki