Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

When upgrading to 5.10 , the includes a new and improved transcode system is automatically used. The old transcode system can still be used in 5.10, but it is considered deprecated and will not be available in future releases. Customers must therefore be migrated to the new transcode system before upgrading to a 6-version.

If you are a consultant, please see DC 5.10 Formats - Migration for more information on how the migration to the new transcode system is handled and things to be aware of in relation to this migration.

...

  1. Handling of unavailable renditions.

  2. Search2.

  3. New thumbnail formats.

  4. Source formats.

  5. jpg/jpeg formats

Handling of unavailable renditions

...

The new transcode system now supports a special SourceFormat that can be used to refer to and get the source files of assets. A special “Original” format of this type is now defined out-of-the-box. If you have previously hard-coded the “Original” format in a list of available download renditions, this can lead to two “Original” formats being shown. It should no longer be necessary to have any special-case handling for getting source formats.

jpg/jpeg formats

The new transcode system uses the jpeg extension for jpg/jpeg files and renditions. Existing renditions that have not been generated with the new transcode system will have the same extension as before. Thus, existing jpg/jpeg files and renditions will still be returned with the jpg extension if this was the behavior before upgrading to 5.10. New jpg/jpeg renditions that are generated with the new transcode system will have the jpeg extension.

Please be aware of this if you have any custom logic that relies on the jpg extension and does not handle the jpeg extension.