When a file is uploaded to MediaBeacon, but cannot be found by a Global Administrator, or a file exists in the server's file system and does not appear in MediaBeacon, this may be attributed to one of two things, XMP packet size or filename exclusions.
XMP Packet Size
MediaBeacon’s maximum XMP size in bytes is 1 Mb by default. Files with an XMP packet larger than this size will not be imported. This can be verified by a Global Administrator; the following error would be present in their Global Log:
com.brightech.xmp.XmpPacketTooBigException caught [XMP packet is too big (16207872) in file D:\MBAssets\Content\Buildings, Environments, Abstracts\Home Office\Abstract Photography\_MG_9607.jpg]
This is known to occur specifically with InDesign Files as they have capability to store large binary previews in the XMP packet.
If not above logs are not present, the next most likely reason is that the filename contains one of MediaBeacon’s Excludes. Files or Directories prepended with "m-" or "M-", for example, will not be visible within MediaBeacon.
Adjusting Allowed XMP Size
If the XMP packet is too big, you will need to increase the default or adjust the existing maximum XMP size with the system property:
Note: If the
mb.max.xmp.size is set too high, ~30MB or more, the file will not be imported despite having increased the XMP size. We don't recommend setting this property to a value greater than 26214400 bytes (25Mb).
Avoid Using Excluded Filenames
If the file name contains one of MediaBeacon's Excludes, such as m- or M-, you will need to rename the file. If you aren't familiar with MediaBeacon's default Excludes, refer to the "Excludes" element of the
mb_import_conf.xml.template file (located in the 'etc' directory of your core MediaBeacon installation).