Part of the new DAM 4.5.1 release is represented by the support offered for the new DAM for Sitecore module. The 2 main changes are:
...
The default preview feature is used through the assetstreamerasset-streamer. The meaning of this feature is to have the assetstreamer asset-streamer deliver another media file, if the requested file was not found, so the user does not get 404 file not found.
You configure this in the config manager under the tab "Default previews".
...
How to configure the new implementation?
CreatedADGroupsAndUsers
CreatedADGroupsAndUsers have moved.
It now resides in the dam center .zip file. Som from version 4.45.1 you while find it here:
4.45.1\4.45.1.zip\CreateADGroupsAndUsers
...
- Upload the substitute assets to the catalog folder called Default preview icons.It is important that you place them there, because there is a workflow (AssetSyncFolder) that automatically publishes to the channel folder Default preview icons.
- Create the formats you want your substitute assets to be transcoded into and then create a profile with these formats.
- Add this profile to Profiles and destinations in config manager. Only add this one time pointing to the chanel folder Default preview icons. We recommend that you add is to the relevant version.
- Go to the config version where you want to enable the default preview feature. In the screenshot you can see that we have configured it for Dam For Sitecore version 5.0.0.
The
Note: The Default previews is an iterativ iterative metagroup. The group consists of 4 fields:
Assettype (required)
The assettype you want a substitute for.
Preview Asset (required)
The asset you want as the subsitute.
Input Mediaformat
Select the mediaformat that this substitute should match up against.
Output Mediaformat
Select the mediaformat that the selected substitute asset should be returned in.
The assetstreamer logic when default preview is configured
If the requested assetId and mediaformatId did not return any content, then we go into the default preview logic.
a) Get default configuration for the version bound in the accesskey. If empty, it fall back to the dam center version to see if it has any configuration.
b) Test if there is any configuration for the requested assettype.
c) We then test if there is any configuration where Input mediaformat equals the requested mediaformat and the output mediaformat is set. Then we try to stream that format for the configured preview asset.
d) If c did not find anything, then we find the first configuration, where input mediaformat equals 0 and streams that with the requested mediaformat or the output mediaformat if defined.
e) return 404 if none of the above was a success. - On the config version you just added the default previews to. You have to set the config param Default Preview Destination to the destination where the substitute assets are published to. For most of the times this will be FrontenData SM.
Adaptive Bitrate
a A new video quality has been added to the DamCenter, : "Adaptive Bitrate HQ"
How to Add the format
- Go to System Tools / Profiles
- Select the profile "Digizuite™ Video Portal Videos"
- Select "Adaptive Bitrate HQ" in the "Format qualities" drop down.
- click Click the "+" icon
- click Click Save.
See VideoPortal Video Portal Installation & Configuration guide, for instructions regarding the ConfigManager configuration.
How to remove the format
- Go to System tools / Profiles.
- Select the "Digizuite™ Video Portal Videos" profile
- Select the "Adaptive Bitrate HQ" in the format qualities list.
- Click on the "-" icon
- Click Save
| Info | ||
|---|---|---|
| ||
| Batch System version 2.4.21 or newer |
| Info | |
|---|---|
|
...
|
...
| If the Adaptive |
...
| Bitrate feature is not used, the "Adaptive Bitrate HQ" quality should be |
...
| deselected, as it places a high load on the transcode system. |
...
DOs
...
Tips & Tricks
What has been released?
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
What is in the next release?
The next release it will contain bug fixes.