**Viaplay Improvements**

# **Viaplay Improvements** ## USE CASE 1 - The user can import multiple packages and add naming conventions for them that overwrite Connect naming conventions ### **Accep Crit**: a) Have a mandatory column to add the package name. In this column the user will add the desired Package configuration and the name of the package E.g. LRCLfeLsRsLtRtLtRt/Package name 001 , LRCLfeLsRs / Package name 002 , LtRt / Package name 003. b) When the column Package name and configuration is left empty the plugin will follow the naming convention from Connect / Org Settings. c) When the column Package name and configuration will have values inserted then the Plugin will discard the naming convention from Connect / Org Settings (csv attached). d) There will be no limit for the number of packages / configurations that you can setup in the plugin. ### **Questions** 1) Q: What happens when we complete only the audio configuration in the Package Column A: We need either the Column left empty or complete with audio configuration 2) Q: Will there be validations for when we add more audio configs, or duplicates or any other wrong entries? A: There will be validations ### **-Scenarios-** ***Positive***: 1) Insert Package column in a CSV - [x] QA - All good. 2) Add individual naming for a package - [x] QA - All good 3) Naming convention applied in CSV ignores naming convention from Connect - [x] QA - All good 4) Add multiple (at least two) package names with different audio configurations for the resulting CPL-s - [x] QA - All good. Two package names were added in a csv: 1st with a "{{title.name}} _ package_1" and 2nd with pachet_random_2. Both were completed successfully 5) Different audio and package configurations: a) Skipped first track on first package/Skipped first track on second package b) Two packages per row c) Three packages per row d) Two title rows with two packages e) Two title rows - one with 2 packages, the other with 3 packages f) Three title rows with 2 and 3 packages combination per row g) Multiple packages that have different audio configuration CPL-s are properly combined when listening to the resulting outputs for each CPL. - [x] QA - All good. All attempts proved successful after minor tweaks 6) Import multiple packages from a .mov source file + a sidecar .wav track - [x] QA - All good. The output from the sidecar .wav track is added to the first package created ***Negative***: 1) Nothing added in the Package column means that naming convention for package in Connect is applied and only one package is created - [x] QA - All good. If nothing is added in the Package column, you can only have 1 package output and it is based on Connect namging convention 2) Add same package name for 2 packages with same audio configurations - [x] QA - All good 3) Add same package name for 2 packages with different audio configurations - [x] QA - All good 4) Add only audio configs for 2 packages - [x] QA - All good. The process will fail at 0% with validation error. 5) Validation errors for wrong configurations: a) The number of configurations doesn't equal the number of languages b) Bad audio configuration in Pack column vs Spoken Language column c) One row does not have languages in Spoken Language while the others do - [x] QA - All good. All attempts showed validation errors ## USE CASE 2 - The user can add language tags to multiple audio tracks ### **Accep Crit**: a) In the Spoken Language section, the number of tracks is equal to the number of languages b) Use a “/” separator between languages in the csv c) The order of the languages is the same as the order of the tracks (based on the audio config) d) If the CPL contains multiple audio tracks, for different languages, then the language set on CPL will be the one of the first track ### **-Scenarios-** *Positive:* 1) Check if language tag is added to a track from the audio configuration - [x] QA - All good 2) Check if language tags are added in the order of the tracks from the audio config - [x] QA - All good. Multiple languages added and in media warp you can check that the order is followed by the outputs 3) Check if language set on CPL will be the one of the first track when there are multiple languages for audio configs - [x] QA - All good. CPL lang is the same as the first track 4) IMF Import passes for Custom Language code(s) - [x] QA - All good. Checked multiple combinations and codes and all passed. 5) IMF Import fail validation for an Inexistent Language code - [x] QA - All good 6) IMF Import fail validation for multiple Inexistent Language code(s) - [x] QA - All good 7) No content added for Language column - [x] QA - All good 8) Add separate language for an extra .wav file track - **Is this doable?** - [x] Solutions Engineer - Would be nice - [x] QA - Will be done for future improvements *Negative:* 1) Check if next tracks are tagged if language tags are not separated by / but by , - [x] QA - All good. Validation error appears. 2) Validations for wrong audio config on sidecar .wav files - **Is this doable?** - [x] Solutions Engineer - Would be nice for future projects - [x] QA - Will be done in future projects ## USE CASE 3 - Add a "delete" tag in S3 to source files (without parent) used in IMF Import processes ### **Accep Crit:** a) Create a script to add the “Delete” tag to all .mxf files (without a parent) .wav and .mov files in the Uploads folder b) Create a cron to run monthly ### **-Scenarios-** ***Positive**:* 1) Check if tag is added for .mov source file used in IMF Import process - [x] QA - All good 2) Check if tag is added for .mxf source file used in IMF Import process - [x] QA - All good 3) Check if tag is added for .wav source file used in IMF Import process - [x] QA - All good ***Negative**:* 1) Check tag is not added for .mxf children files used in IMF Import process - [x] QA - All good 2) Should the tag be ommitted if no process (Imf plugin, media warp, transcode etc.) has been done for a source file in the last 60 days? - [x] Solutions engineer - Will investigate if necessary in the future - [x] QA - Will check the modifications if this is needed in a future improvement ## **Issues** 1) Completed processes remain InProgress in Connect - [x] BE - Done - [x] QA - All good 2) 403 Errors appear that don't allow the user to create any new IMF imports after the recent deploys - [x] BE - Investigated latest deploys and fixed the gateway issues that were occuring - [x] QA - All good. For now, the errors have not appeared anymore after multiple IMF imports. If the situation resurfaces in the future, we will issue a ticket.