Abstract: An automation plugin to a digital asset editing program. In one embodiment, for example, a method performed by the automation plugin to the digital asset editing program executing on a computing device having at least one processor and memory comprises: allowing a user of the digital asset editing program to filter a library of digital assets by custom metadata associated with the digital assets; receiving custom metadata filtering criteria from the user; and responsive to determining one or more of the digital assets are associated with custom metadata satisfying the custom metadata filtering criteria, allowing the user to select at least one filtering result, corresponding to one of the one or more digital assets, which, when selected, causes the corresponding digital asset to at least be loaded into the digital asset editing program for editing by the user.

Abstract: An automation plugin to a digital asset editing program. In one embodiment, for example, a method performed by the automation plugin to the digital asset editing program executing on a computing device having at least one processor and memory comprises: allowing a user of the digital asset editing program to filter a library of digital assets by custom metadata associated with the digital assets; receiving custom metadata filtering criteria from the user; and responsive to determining one or more of the digital assets are associated with custom metadata satisfying the custom metadata filtering criteria, allowing the user to select at least one filtering result, corresponding to one of the one or more digital assets, which, when selected, causes the corresponding digital asset to at least be loaded into the digital asset editing program for editing by the user.

Abstract: Embodiments are provided for a media player. In some embodiments, locally stored media player data is obtained from a first device on at least one of a device setting, a media player setting, and a media player state of a media player module of a web application, the data is stored in a data store of a content management system for a first account, and based on the media player data, locally stored data is selectively synchronized on a second device associated with the first account to provide a continued experience with media on the second device.