Export assets FAQ
Find answers to frequently asked questions about Media Cart issues, SPS/Media Portal export, and SPS desktop downloads.
You can export up to 1 GB/500 files using SPS. For questions about a full account backup, contact Scene7 Tech Support.
There is no difference between the file that is exported using "Export Original" and the original file. Scene7 stores the original in an abstracted filename, and then creates a copy at export time under the original name. It is the same file that was uploaded.
You receive this error in the job logs if there is an attempt to add more items to an export once a 1-GB threshold has been reached.
You can't add additional files once a 1-GB threshold has been reached, or you've selected 500 files.
The export maximum size and number restrictions do apply to master images in addition to derived images. For more information, see
See the following Help article, which describes the export options in SPS. Once "Export Original" is enabled, your users can export the original files.
In a previous version, the filename of an asset was renamed when the asset ID was renamed. Any asset renamed more recently that September 2011 has updated name when exported. You can rename an older asset, and it has the renamed name when exported.
Deselecting the Active checkbox next to the preset only removes it for Media Portal users and not for other user roles. You are not a Media Portal user, and that is why the preset appears for you.
To resolve this issue, have a company administrator of the account select the “Enable User-Defined Conversion” option. Choose Setup > Image Presets to access this option.
If the Enable User-Defined Conversion option is not available, make sure that the "Show MediaPortal Features" under Personal Setup is selected.
Export links are active until one week after its generation. Once this period is over, the link returns an empty page without any download.
This active period is non-configurable.
The media cart is stored in local Flash cache. SPS doesn’t set any limitation on the
maximum assets that you can add into media cart, but the Flash runtime controls it.
It’s possible that media cart will be cleaned automatically if there are many entries in that cache.
Find the following description from the official Flash runtime Help:
"Local disk space considerations. Local shared objects have some limitations that are important to consider as you design your application.
Sometimes, SWF files aren't allowed to write local shared objects, and sometimes the data stored in local shared objects can be deleted without your knowledge. Flash Player users can manage the disk space that is available to individual domains or to all domains. When users decrease the amount of disk space available, some local shared objects can be deleted.
Flash Player users also have privacy controls that can prevent third-party domains (domains other than the domain in the current browser address bar) from reading or writing local shared objects. On Mac OS, starting with AIR 3.3, the location for local shared objects changed, so if you upgrade to the 3.3 namespace, it can appear as if the objects were lost.”