Version: 7.x, 8.x
MediaBeacon creates .rej files when there’s an unparseable XMP packet inside of an asset on initial import. When this happens, MediaBeacon archives the asset an to m-<filename>.rej sidecar file and then creates a new viable XMP packet from scratch for use inside of the live asset.
These may also be created if there is some issue writing into the file (like file locking), or for writes to the resource fork (xattr on an HFS filesystem, or the alternate data stream on an NTFS filesystem).
- If the pre-existing metadata is of no concern, the .rej files may be deleted.
- If the metadata is of concern, a system administrator should inspect the examples to recover the metadata manually.