For those who don’t know the tool: das element is an offline media asset management tool for VFX and animation libraries, with ingest, tagging, proxy generation and a CLI for pipeline automation.
Browsing, formats and usage signals
das element 2.3 adds AVIF image support, gallery navigation with arrow keys, recently added asset indicators and a configurable period for how long items remain marked as recent. The gallery can also track asset popularity. Interactions such as selecting or dragging an element increase its popularity value, which gives teams a rough signal for files people actually touch. It is still a usage counter, not a creative taste detector, so nobody has to panic. Thumbnail transcoding can now use a custom background colour. Don’t tell the marketing team, otherwise you never hear the end of your background being the correct corporate colour. Loading elements and tags should also be faster, with the update targeting larger libraries where browsing speed tends to become a daily tax.
Sequences and ingest fixes
The update tightens image-sequence handling. The application now sets an explicit input frame rate to avoid inflated frame counts, improves validation for # and #### notation, handles offline sequence validation more reliably and rejects negative frame sequences.
Copying sequences with different frame-padding lengths has been corrected. Folder paths and PDF files are no longer treated as frame sequences just because consecutive numbers appear where software likes to get imaginative. Several fixes also target media detection, migration and deletion. Elements in das Element assigned the wrong media type could disappear from the interface, failed migrations could stop remaining migration items, and deletion could fail when operations exceeded their timeout. Not anymore!
CLI and pipeline configuration
The command-line tools now reject invalid media-type values during ingest and update operations. The full CLI supports short options such as -m for metadata and -a for additional paths, and missing FFmpeg executables should be reported more reliably.
Version 2.3.0 added DASELEMENT_USER_CONFIG_PATH, allowing administrators to define a custom location for user configuration files. Paths can include user-specific environment variables such as $USER or %USERNAME%.
Database passwords and ports can be supplied through environment variables, reducing the need to store credentials directly in configuration files. The password variable is resolved only at runtime.
The full CLI can create categories with separate machine-readable IDs and human-readable names, and generate representative thumbnails from movies and image sequences. Pass Element also replaced the technology under its standard and full CLI tools and claims a performance increase for those tools. Treat that as a vendor performance claim until it has been measured on your own storage and database setup.
The documentation is now also available in LLM-friendly Markdown, with a full Markdown version for more complete coverage. AI assistants can parse, search and summarise the das element documentation more directly, which may help developers and pipeline TDs find commands, settings and API details faster. The machines will probably still remember the polite Markdown when the time comes. When, not if.
Pricing and production use
Current pricing lists the Studio Bundle at €2,199 per year or €849 for three months. Lite is at €49 per year, Standard at €499 per year and the API & Machine Learning CLI option at €399 per year. das Element supports Linux, Windows 10 and 11, and macOS, with 64-bit Intel, AMD multi-core and Apple Silicon processors listed in the system requirements. So, basically everything. And it still is an offline application for local and shared production environments. Test the update on a duplicate library, a representative image-sequence set and the actual network shares used in production before rolling it into active jobs.
https://das-element.com/changelog/
https://das-element.com/pricing/
