QScan User Guide

User Guide
Version 3.3
COMMERCIAL IN CONFIDENCE
Copyright and Disclaimer
Copyright © 2019 by EditShare.

This document, as well as any software described in it, is furnished under either a license or a confidentiality
agreement, is confidential to EditShare, and may be used or copied only in accordance with the above mentioned
agreements. The information in this document is furnished for your use only and is subject to change without
notice. EditShare assumes no responsibility or liability for any errors or inaccuracies that may appear in this
document.
This document is the property of EditShare and is provided in accordance with an EditShare license agreement.
Copying, modifying, or distributing this document is in violation of the license agreement, Copyright Laws of
England and Wales, or the Copyright Laws of any applicable foreign jurisdiction is expressly prohibited.
EditShare is a registered trademark of EditShare in the US and other countries. Universal Media File is a trademark
of EditShare in the US and other countries.
To the best of our knowledge, the information in this document is accurate; however, EditShare assumes no
responsibility or liability for the accuracy or completeness of this information. Mention of trade names or
commercial products does not constitute endorsement by EditShare except where explicitly stated.
EditShare EMEA
Clifton House
Bunnian Place 
Basingstoke
Hampshire, RG21 7JE
England
Tel: +44 (0) 20 7183 2255
Fax: +44 (0) 20 7183 2256
Email: [email protected]
http://www.editshare.com
January 4, 2019
2 COMMERCIAL IN CONFIDENCE
TP-00360-02 COMMERCIAL IN CONFIDENCE 3

Table of Contents
CHAPTER 1: INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Intended Readership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Conventions Used in this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
QScan Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
General Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
CHAPTER 2: REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
QScan ONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Minimum Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Recommended Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
High Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
QScan PRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Minimum Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Recommended Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
High Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
QScan MAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Base machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Additional Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Supported Cloud Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Supported Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
General Recommendations and Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
User Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
User Example 1: QScan Pro. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
User Example 2: QScan Max. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
CHAPTER 3: INSTALLING QSCAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Creating an EditShare Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Registering for QScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installing QScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
CHAPTER 4: GETTING STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Logging into QScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Licensing QScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Activating a QScan License Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Activating a QScan License Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
QScan Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Viewing the Default Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Logging out from QScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4 TP-00360-02
CHAPTER 5: BASIC OPERATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Creating a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Creating a Local Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Creating a Remote Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Tips for Networked Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Initial Project Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Selecting the Watch Folder Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring Project Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Configuring File Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuring Loudness Audio Grouping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring Output Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configuring Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Running a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Viewing Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Viewing Reports as HTML files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Viewing Reports as PDF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Viewing Report Video Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Viewing Reports as XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Sending Reports as Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Viewing Report Audio Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
CHAPTER 6: MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Working with Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Viewing Existing Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Adding Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Editing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Deleting Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Working with Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Viewing Existing Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Adding Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Editing Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Deleting Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Blocking Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Setting up network shares as repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Viewing Existing Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Adding Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Editing Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Deleting Repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Locale Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Email Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Task List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
TP-00360-02 5
Displaying Full Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
CHAPTER 7: ADVANCED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Using a Default Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Creating a Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Single Pass Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
The Detailed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Jumping to a Specific Time Code in the detailed view. . . . . . . . . . . . . . . . . 89
Macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Opening the Macro User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Elements of the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Creating a Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Parameters and Logical Gates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
When a macro is ready to use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Finishing a Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Exporting a Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Importing a Macro. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Using Macros in Projects and Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Logical Gates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Sample Macros and Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Integration of QScan with EditShare and Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
How to make QScan use EditShare media spaces . . . . . . . . . . . . . . . . . . . . 111
Installing FlowQScan Trigger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Using FlowAutomation with QScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Triggering a QC automation template from FlowStory or FlowBrowse 119
Can FlowQScanTrigger and FlowAutomation interfere with each other?. .
121
APPENDICES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Appendix 1 - IMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
The Business Benefits of IMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Why do we need a Global Exchange Format? . . . . . . . . . . . . . . . . . . . . . . . . 124
What problems will IMF solve? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
What is IMF? The Shipping Container. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
A Container of Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Additional benefits from IMF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Conclusion: The business benefits of IMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Illustration 1: Storage efficiencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Illustration 2: Performance efficiencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
IMF for Broadcast & Online: The path to adoption. . . . . . . . . . . . . . . . . . . . 141
Preparing your business for IMF adoption . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Appendix 2- PSE (Photo Sensitive Epilepsy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
6 TP-00360-02
Ofcom Guidance Note on Flashing Images and Regular Patterns in Televi-
sion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Appendix 3- Supported Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Appendix 4 - Template Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Format Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
IMF Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Frame Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Baseband/Waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Video Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Video Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Loudness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Appendix 5- Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
System Events List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Configuring Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
File Analysis Does Not Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
File Analysis Remains in “generating PDF” status . . . . . . . . . . . . . . . . . . . . 180
Cannot see Macros in Project area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Cannot Send Reports by Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
GLOSSARY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Analysis General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Analysis Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Audio Grouping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Email notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Output Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Project Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Project Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Simple and "Clean" Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Single Pass Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
SystemConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Task List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
TP-00360-02 7
Watch Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
8 TP-00360-02
Chapter 1: Introduction
Intended Readership
Welcome to the User Guide for QScan; this User Guide is intended for any user of the QScan
application. This guide takes you through installing, licensing, and using QScan to analyze files.
Once QScan is installed and licensed, the guide is divided into three main sections that are
aimed at users that perform different types of tasks:
• “Chapter 5: Basic Operation” on page 33: This section covers the essential tasks that are
required to analyze files. Refer to this section if you are a day to day user of the system.
• “Chapter 6: Management” on page 61: This section covers tasks such as creating users and
nodes. These tasks will most likely be carried out by an administrator of QScan.
• “Chapter 7: Advanced” on page 81 This section covers tasks such as creating templates,
working in the detailed view, and performing single file analysis. These tasks will most likely
be carried out by an administrator of QScan.
Conventions Used in this Guide

This User Guide assumes that the majority of QScan users are using desktop workstations with
a keyboard and a mouse. When the instructions tell the user to 'click', they are referring to
pressing the left mouse button. Users of handheld devices and touch screens should 'tap' when
asked to 'click', and 'tap and drag' when asked to 'click and drag'.
It should be noted that right-clicking invokes functions determined by the web browser, not by
QScan. Similarly, clicking or tapping within the browser address and title bars invokes functions
outside the influence of QScan. Refer to the documentation relevant to the version of browser
you are using for further information.
When you are asked to type text into a field, the text to be typed is represented like
this. This includes the typing of Uniform Resource Locators (URLs) into the web browser.
Menu items on the graphical interface are represented in bold type.
Technical Support
For questions not addressed in our documentation, contact EditShare Technical Support using
the following address: [email protected]
TP-00360-02 9
Chapter 1: Introduction
QScan Overview
QScan is a family of fully-featured Automatic Quality Control (AQC) systems, engineered to
unobtrusively check the integrity of media files at user-definable points in a production
workflow. QScan goes beyond regular QC solutions, offering comprehensive video and audio
analysis. QScan is powered by the award-winning Quales AQC engine and can be used to
provide compliance for file-based content delivery to any global standard. With built-in
templates for common standards, the compliance testing process is extremely quick and easily
managed.
In modern media workflows, the earlier any issues are found, the easier and faster it is to rectify
them. Failure to check could result in major headaches further down the line. For this reason,
Quality Control is often carried out at the start and then at the end of a workflow, manually or
automatically. Unlike most QC solutions, QScan is unobtrusive and highly adaptable and can be
applied at multiple points, seamlessly performing a series of automated tests on both the audio
and video signals to confirm that files consistently meet channel specifications.
With the global exchange of programming content being traded around the world to
broadcasters and VOD suppliers such as Netflix and Amazon, the need to deliver flawless files
is paramount to everyone's business whether you are a large or small operator. Furthermore,
with the requirements of mandatory file checking now becoming mainstream, there’s never a
better time to implement an automated QC solution at your facility.
General Features
• Efficient, fast, intuitive and robust web-based system.

• Scalable to adapt to growing workflows.
• Leading edge multi-format and multi-parameter analysis with DPX support.
• Built in templates for common published delivery standards like AS-11 UK DPP.
• Template macros allow for combined decisions to be made on content tests.
• Pre-roll/post-roll and TC-in/TC-out event evaluation: allows to check events only in specific
parts of the file (for example, detection of test patterns in the first N seconds of the file,
black frames in specific TCs.
• Multi-level reporting environment.
• Simultaneous multi-user support.
• Scalable to adapt to growing workflow environments.
• Efficient usage of hardware and computing power.
10 TP-00360-02
Chapter 2: Requirements
Introduction
The following hardware specifications are given as guidelines because the number of different
variables for automatic quality control hardware and software are too numerous to document
exhaustively.
The make, model, specification and build of any hardware combined with the 83 different test
types and their user selectable variables means that there is no one size fits all approach to
selecting the right platform.
It is important to take, codec, wrapper, resolution, bit-rate into account as much as the number
of tests to perform and the amount of content to be processed.
As a general rule, in order to be able to estimate the size of the system needed, it can be
estimated that a 16 core machine (see recommended specification for QScan Pro) can analyze
at least 96 hours of content per day, assuming worst case as Real Time speed.
Formats such as J2K, DCP, DPX would need special attention, since increasing the number of
cores would not generally result in optimizing speed, given the special nature and
characteristics of these codecs.
Time of analysis is optimized when long files are analyzed, since some initial/final tasks
(detecting files, queueing files, opening files, preparing buffers, reading codec parameters,
format checks evaluation, etc) might take some time, thus these initial tasks will have a greater
impact on shorter files than in long files
TP-00360-02 11
QScan ONE
Minimum Specification
• 4 CPU Cores.
• 4 GB RAM.
• 500 GB HDD (as long as content is read from an external location).
• Windows OS (from Windows 7 or newer).
• Google Chrome browser.
• Note: This hardware is suitable for MPEG2 and H264 formats.
• MPEG2 will be generally analyzed at least 2x Real Time Speed.
• H.264 will be generally analyzed Real Time Speed (worst case scenario).
• Parameters to test will make these metrics vary significantly, but Real Time Speed should be
the worst case for a dedicated QScan machine running no other (non O/S related) services.
Recommended Specification
• 8 CPU Cores.
• 4GB RAM.
• 1TB HDD.
• Note: The worst case would be analysis at Real Time Speed. This would apply for formats such
as: AVC intra, DNxHD 185, mp4, P2 DVCPro, MPEG2 TS, H.264 in MPEG2 TS, XDCAM 50 and
other similar formats.
High Specification
• 16 CPU Cores.
• 8GB RAM.
• 1TB HDD.
• Note: Should be faster than Real Time in most situations and most post-production and
broadcast formats.
12 TP-00360-02
QScan PRO
QScan PRO
Minimum Specification
• 8 CPU Cores.
• 4GB RAM.
• 1TB HDD.
• Note: The worst case would be analysis at Real Time Speed. This would apply for formats such
as: AVC intra, DNxHD 185, mp4, P2 DVCPro, MPEG2 TS, H.264 in MPEG2 TS, XDCAM 50 and
other similar formats.
Recommended Specification
• 16 CPU Cores.
• 8 GB RAM.
• 1TB HDD.
• Note: Most standard post-production and broadcast formats should be analyzed in Real
Time, worst case. But since up to 4 files at a time can be analyzed, the selection of parameters
to check is of high importance here.
High Specification
• 32 CPU Cores.
• 16 GB RAM.
• 1TB HDD.
• Note: Most standard post-production and broadcast formats should be analyzed faster than
Real Time with 4 files at a time. Once again, the selection of parameters to analyze will impact
on the analysis speed.
TP-00360-02 13
QScan MAX
Base machine
• 16 CPU Cores.
• 8 GB RAM.
• 1TB HDD.
• 10Gb ethernet connection to repository.
Additional Nodes
• 16 CPU Cores.
• 8 GB RAM.
• 1TB HDD.
• No browser needed.
• 10Gb ethernet connection to repository.
14 TP-00360-02
Supported Cloud Environments
Supported Cloud Environments

• Amazon AWS
• Microsoft Azure
• Google Compute (requires QScan 3.2 or above)
Supported Virtual Machines

• VMware (Workstation, Fusion, ESXi)
• VirtualBox
• Hyper-V
Note that although the software will run on any Virtual Machine, the license might not work in
specific VMs. Please contact EditShare for assistance if you have any problems when running the
license in VMs.
TP-00360-02 15
General Recommendations and Tips

• Make sure no other processes are running in the background and that analysis is running on
a dedicated machine.
• Adapt your parameters to the workflow stage that you are at, so analysis speed is optimized.
Here are some examples:
– If you are not analyzing content coming from tape ingest processes, you may disable
Digital Betacam Channel Condition Errors, and Digital Dropouts (VIDEO QUALITY
PARAMETERS).
– If you are analyzing content coming from encoding, it is always useful to disable BASE-
BAND analysis, (luminance/chrominance analysis) provided that they were already
checked after production/post production/edit phases.
– Assuming you are not considering analysis of frame statistics such as frame types, or
keyframes, you can disable all frame related content.
• Noise detection, and Digital Drops need additional computing operations to analyze the
images in the frequency domain, so disabling these, if not needed, is recommended.
• New PSE algorithms i n version 2.14 up might require some more CPU bandwidth than in
older versions
• If waveform generation and thumbnail generation are enabled for the PDF report, the total
time from “detected” to “analyzed” will vary depending on the amount of events detected,
since all events will need a waveform and thumbnail to be generated, thus consuming more
time to reach the “analyzed” state.
• Set analysis to high speed for servers up to 12 cores.
• Set analysis to very high speed for servers 12 cores and higher.
• Higher processing power machines (12 core or above) guarantee effective time saving in
analysis of several simultaneous files, but not so much for sequential analysis of one file at a
time. So, it is recommended to run simultaneous (concurrent) analysis when you have more
than 8 cores in your processor.
• SSD Disks are recommended, to prevent bottlenecks due to disk reads/writes. This would
apply mainly for local repositories
• RAID Disk configuration is recommended.
• Other Disk architectures are also recommended: NAS, SAN, etc.
• It is always wise to use more than one node for simultaneous analysis of several files when
you run QScan on machines with 8 cores or fewer.
• Analysis using several nodes will require high speed network connections (GB or 10GB
networks) specially between nodes and the repositories. As generic example, if a speed of 2x
Real Time is desired, the network should be able to handle a sustained bandwidth of 2x the
file bitrate x 4 (files) , for each node.
16 TP-00360-02
User Examples
User Examples
The following are real life metrics based on measurements taken from live systems in the field.
User Example 1: QScan Pro
System Configuration
• 1 Base Machine
• Running 4 files at the same time
• 16 core Machine with 8GB RAM
• 10Gb connection between QScan and repository (shared folder in the network where files are
read from)
Results
• Template analyzing all parameters except for frame statistics

• Approx. 15 minute XDCAM HD File.
• Analysis of 4 files would take approx. 10 minutes per file. I.e. approx 1.5x Real Time Speed.
User Example 2: QScan Max
System configuration
• 1 Base Machine + 4 Nodes.

• Each machine running 4 files at the same time for a total of 20 files at a time.
• 16 Core machines with 54GB RAM.
• 10Gb connection between nodes and repository (shared folder in the network where files are
read from).
• 1Gb connection between nodes and base machine.
Results
• Template analyzing all parameters except for frame statistics.

• Approx. 15 minute XDCAM HD File.
• Analysis of 20 files at a time would take approx 10 minutes per file, which result in approx 1.5x
Real Time Speed.
TP-00360-02 17
18 TP-00360-02
Chapter 3: Installing QScan
Creating an EditShare Account

You must register an EditShare account so that you can gain access to the Editshare portal and
install QScan. To create an EditShare account, complete the following steps:
TASK
1. In your web browser, navigate to https://my.editshare.com/login
3 4 5 6
10 7 8
2. Click Create Account.
3. Enter your email address.
4. Enter your email address again for verification.
5. Enter a password for the account.
6. Enter the password again for verification.
7. Enter your full name.
8. Enter your company name.
9. Click in the Terms and Conditions link, read and confirm that you agree by clicking the
box.
10. Click Register.
Now that you have created an EditShare account, you must register for QScan by providing
your details.
TP-00360-02 19
Registering for QScan

You must register your details to be able to use QScan. To register for QScan complete the
following steps:
TASK
1. Login to the EditShare portal https://my.editshare.com/login with your EditShare
account details.
2. The download tab is selected.
3. Click the QScan AQC tab.
4. Fill in all of the required fields.
5. Click the I have the required hardware check box to select it.
6. Click Try Now.
Now that you have registered your details you can install QScan.
20 TP-00360-02
Installing QScan
Installing QScan
To install QScan, you must have created an EditShare account and registered your details. You will
then have access to the installation file. To install QScan, complete the following steps:
TASK
1. Login to the EditShare portal https://my.editshare.com/login with your EditShare account
details.
2. Click the QScan AQC tab.
3. Scroll down to the bottom of the page and click the download the software from the link
provided, for example QScan-3.2.0.0.msi
4. Click Save File to save the file to your default location.
5. Browse to the location of the .msi file and double click it to run it.
6. The Open File - Security Warning window opens:
7. Click Run.The Welcome installation window opens:
TP-00360-02 21
8. Click Next. The End User License Agreement page displays.
9. Click in the I accept the terms in the License Agreement check box to select it.
10. Click Next.
11. The destination Folder screen is displayed. If you want to install in any other location,
choose the location by clicking Change...
12. Click Next.
22 TP-00360-02
Installing QScan
13. The Auto Discovery Selection screen is displayed. Click in the Enable service auto
discovery check box if you want the service to be automatically discovered by Flow
services. This setting is useful if you are integrating QScan into Flow, and should be
enabled when you are using QScan and Flow together.
14. Click Next.

15. The Service Logon Credential page is displayed. This screen allows you to select the user
that will start the QScan service. The default user is the system user. This setting is useful
when you want to read from network shares, as explained in the repository section. Leave
the default selection of Running as LocalSystem if you are running on your local machine.
If you want to run the service as local or domain user, select the check box and enter your
credentials.
16. Click Next.
TP-00360-02 23
17. The Port Selection screen displays. Enter the Port number that you want top use and click
the Test Port button. The default port setting is 9980. Testing this setting is necessary to
avoid problems when starting the QScan service. You must have the port open and click
the Test Port button to proceed. You can use the test port 9981 to avoid problems when
starting QScan service
18. The Ready to Install QScan screen displays.
24 TP-00360-02
Installing QScan
19. Click Install. The QScan installation wizard starts.
20. Click Yes to allow the procedure to start. The installation procedure starts.
TP-00360-02 25
21. When the wizard haas completed, click the Finish button.
22. When the installation procedure has finished you are prompted to restart your machine. It
is important that you restart your machine.
23. Click Yes.
26 TP-00360-02
Chapter 4: Getting Started
See the following topics about getting started with QScan:
• “Logging into QScan” on page 27

• “Licensing QScan” on page 28
• “QScan Display” on page 30
• “Viewing the Default Node” on page 31
• “Logging out from QScan” on page 32
Logging into QScan

EditShare recommends that you bookmark the QScan LogIn Page or set it as your Home
Page.
TASK
1. Open your web browser and type:
• If you are running from the local QScan machine: http://localhost:8080 (copy and
paste this exact text into your browser).
• If you are running from a browser in another machine on the network:
http://<your_IP>:8080 being <your_IP> the IP address of the machine that is running
QScan.
2. Enter a user name and password. The default user name and password are:
• User name: admin
• Password: admin
3. Click Submit.
TP-00360-02 27
Licensing QScan
You can activate your license for QScan online or offline. To activate a license for QScan you must
have created an EditShare account. See “Creating an EditShare Account” on page 19 for more
information.
Activating a QScan License Online
You can activate a QScan license online if the system that you want to run QScan on has access to
the internet. To license QScan online you must enter the credentials that you registered when you
created an EditShare account.
TASK
1. Login to QScan.
2. Select Management > License.
3. Under the License Online Activation heading, enter your my.editshare.com credentials to
proceed with your online activation:
4. Click Activate to complete the license registration.

5. Check that you have at least 1 node and 1 point listed:
28 TP-00360-02
Licensing QScan
Activating a QScan License Offline
You can activate a QScan license offline if the system that you want to run QScan on is not
connected to the internet. You obtain an activation file in a current QScan system, upload the
activation file to my.editshare.com and then download the license file. You can then load this
license file manually onto an offline QScan system.
TASK
1. Login to QScan.
2. Select Management > License.
3. Click Get Activation File.
4. You are asked to download the JSON activation file. Select the Save File radio button. The
file is saved to the default download location on your system.
5. Click OK.
6. In a web browser, navigate to https://my.editshare.com
7. From the Select an Editshare product screen, click QScan.
8. Select Licenses from the left hand side of the screen.
9. Select the QScan AQC radio button to select QScan as the product that you want to
activate.
10. Click Next.
11. Click Browse... and navigate to the location that you saved the JSON activation file in
before to upload the activation file.
12. Click Open. You may have to wait a few moments for the activation file to be recognized.
13. When the activation file is recognized, click Next.
14. Download the License file.
15. Click Finish.
16. Login to the QScan system that you want to activate the license on.
17. Click Load License.
18. Select the license file that you downloaded from my.editshare.com and copied to your
system and click Open.
19. Check that you have at least 1 node and 1 point listed:
Now that you have installed QScan and configured a valid license, you can start configuring your
first QScan Project. See “Creating a Repository” on page 53.
TP-00360-02 29
QScan Display
When you have successfully logged in to QScan, the projects view is displayed:
30 TP-00360-02
Viewing the Default Node
Viewing the Default Node

A node is a component of a network, connected with other nodes to distribute the work in
different machines. In QScan, nodes are machines other than the "master" machine, where
analysis tasks take place. When you install QScan, a default node is created. You can create more
nodes as required.
To view the default node, complete the following steps:
TASK
1. Select the menu Management - Nodes.
1
2. The default node named localhost is displayed. By default, the node is configured with 1
point. You can edit the localhost node to have the amount of points that the license allows:
• QScan One: 1 point.
• QScan Pro: 4 points.
• QScan Max: 4 points for localhost.
You can now configure a repository, which is the location of the files that you want QScan to
analyze. See “Creating a Repository” on page 34
TP-00360-02 31
Logging out from QScan

To log out from QScan, click on the Logout button at the top right corner of
the screen. You are returned to the Log In page.
32 TP-00360-02
Chapter 5: Basic Operation
This section of the user guide describes the basic operations that you perform to analyze files
with QScan.
See the following sections that describe basic operations in QScan:
• “Creating a Repository” on page 34

• “Creating a Project” on page 37
• “Running a Project” on page 46
• “Viewing Reports” on page 47
TP-00360-02 33
Creating a Repository
A repository is an address book in which an aggregation of data is kept and maintained in an
organized way, and where multiple databases or files are located for distribution over a network,
usually in computer storage. In QScan, a repository is a location for media storage where watch
folders and files to be analyzed are stored.
A repository can reside in the local QScan master machine or any other location in the network
(archive servers, additional nodes). A project in QScan will only access files in a pre-configured
repository.
To create a repository, complete the following steps:
TASK
1. Login to QScan. See “Logging into QScan” on page 27.
2. Select the menu Management - Repositories.
3. Click Add Repository.
2
4. You can now configure either a local repository or a networked repository (to read from
shared folders in a storage location in the network).
Creating a Local Repository
To create a repository on your local machine, complete the following steps:
TASK
1. Click on the local folder icon.
2. Select the local folder that you want as the repository root path.
3
2
4 5 1
3. Click the tick box.
34 TP-00360-02
Creating a Repository
4. When the path is selected, it will be shown in the path field of the repository creation.
5. Click Save Repository.
Creating a Remote Repository
To create a repository that is located in a machine that is accessible in the local network, complete
the following steps:
TASK
1. Click on the networked repository icon.
2. Enter the UNC path to access the networked repository.
2
5 3 4 1
3. Enter the User name.

4. Enter the Password.
In the sample above image, the machine where the repository will be pointing to is
192.168.101.235 and the folder in the remote machine is TestRepo.
5. Click Connect. A new file manager window showing all folders in the selected UNC path
will be displayed. You will then be able to select any subfolder as your networked
repository. Make sure that the selected user has credentials to access the networked
storage location.
You have now created a watch folder that resides in a repository that tells QScan where the
files that you want to analyze reside. You can now create a project and configure the
analysis settings to tell QScan how to analyze these files, and link the project to the watch
folder. See “Creating a Project” on page 57.
TP-00360-02 35
Tips for Networked Repositories
In case of problems accessing the networked path, here are some tips that should help when
creating networked repositories.
• Create a new user in the machine where QScan is running locally.

• Create this same user in the networked storage intended to be your networked repository.
• Log into Windows with the default user (you do not need to log in with the new user just
created).
• Go to Windows services.
• Stop the QScan Service.
• Change the user for starting QScan Service by right clicking on QScan Service and select
Properties, select the Log On tab:
• Start the QScan Service.

• Go to the networked repository creation page, and enter the UNC path and the
username/password to log into the networked storage.
• You should see the folders in the networked repository and should be able to select any
folder as your repository.
If this process does not solve your problems, contact us for further assistance when creating
networked repositories.
36 TP-00360-02
Creating a Project
Creating a Project
A project is a collection of files from one or more repositories that share common templates,
thresholds and parameters. In a project, you can define a set of parameters and configure their
thresholds manually, or select a template that contains pre-set parameters with defined
thresholds. Files are analyzed with the specific parameters and thresholds that are selected when
a project is created or edited. The settings in a project are run as a job when you perform analysis
of files. Information associated with a project include its ID, Name, Status, Progress, Events, and
Errors.
See the following sections about creating a project:
• “Initial Project Settings” on page 37

• “Selecting the Watch Folder Location” on page 38
• “Configuring Project Details” on page 39
• “Configuring File Analysis” on page 40
• “Configuring Loudness Audio Grouping” on page 41
• “Configuring Output Folders” on page 43
• “Configuring Reporting” on page 44
Initial Project Settings
To configure the initial project settings, complete the following steps:
TASK
2. Select the menu Projects - Add Project.
2 3
4 5 5
3. Enter a name for your project.

4. If you want to analyze files in the sub folders of a watch folder when it is selected as the file
input, select the Recursive Folders check box.
5. Use the Filter Out and Filter In fields to select the file types that you want QScan to
recognise, and those that you want it to ignore.
TP-00360-02 37
Selecting the Watch Folder Location
Watch folders are folders or sub folders into one or more repositories, containing the files that
QScan will analyze. When setting up a project you can select either watch folders, specific files, or
both.
To select the watch folder location within a repository, complete the following steps:
TASK
1. In the Create Project panel, click Add File Input.
2. Navigate to the repository that you want to use and click the folder icon next to it.
1 2
3. Click the tick icon to select the watch folder contained in the repository.
3 5 4
4. The Repository and watch folder location are selected and listed in the Input area.
5. Click the x icon to close the Add File Input dialog.
6. Click Save Project.
38 TP-00360-02
Creating a Project
Configuring Project Details
You can configure project details to specify information about the project such as its description,
and which nodes (other machines running QScan) in which the project can be run.
To configure the project details, complete the following steps:
TASK
1. In the Create Project panel, click the plus + icon next to the Project Details heading to
expand it:
2. Type a description for the project.

3. Select the nodes to run the project in. Use All Nodes is selected by default, indicated by a
green box, leave this selected.
4 3
5 6
4. Select the analysis speed. The following are approximate values, based on an 8 core
machine.
• Slow - using 10% of CPU.
• Medium - using 50% of CPU.
• High - using 100% of CPU.
5. Select the number of simultaneous files to be analyzed using the Concurrent Analysis
setting.
6. Select the File Analysis Priority from the drop down list.
TP-00360-02 39
Configuring File Analysis
You select parameters and configure their thresholds to specify what checks QScan makes to
your files, and how it reports them; as a logged event, a warning, or a critical event. For more
information, see “Appendix 6 - Template Parameters” on page 187.
To configure file analysis, complete the following steps:
TASK
1. In the Create Project panel, click the plus + icon next to the Analysis heading to expand it:
2. For each parameter that you want to select, click the Plus icon next to the heading:
2
3. For each parameter that is selected, a padlock icon and a green bar displays, indicating that
the parameter has the default setting of logging an event that complies to the settings for
this parameter. You can change this setting so these events are logged as warnings or
critical events.
4. Scroll down to view the details of the threshold that you have selected.
5. Configure the details for each threshold. See “Appendix 4 - Template Parameters” on
page 147 for the thresholds that you can specify for each parameter.
You will only get notifications about parameters that are selected and have a
defined threshold. If you do not want to use a certain parameter for analysis you
can deselect it by using the no entry icon:
40 TP-00360-02
Creating a Project
Configuring Loudness Audio Grouping
Loudness Audio Grouping settings are used to tell QScan what the audio layout is for the files that
you will be analyzing. This only applies when there are audio loudness measurements on the files
that you are analyzing. For example, if you analyze a media file with 8 Audio channels, QScan
needs to know what the Audio Layout is for those 8 Channels. This information is not always
encoded in the streams, so you must set this up manually in Audio Grouping so that QScan can
do the appropriate Loudness checks on the files in your repository. Once Loudness Audio
Grouping settings are saved, you cannot modify them.
To configure Loudness Audio Grouping, complete the following steps:
TASK
2. Scroll down to the bottom of the screen and, under the Loudness heading, click Add
Group:
TP-00360-02 41
3. Select the channels that you want to group. Two example configurations are explained
below:
• In a stereo setup, you would configure two channels:
Stereo setup –
two channels are
configured
• In a 5.1 surround sound setup you would configure three front channels: left, center,
and right, (1,2, and 3). LFE (channel 4) must be disabled. Channels 5 and 6 are selected
as surround channels for left surround and right surround:
5.1 surround sound setup. Channels 1,2, and 3
are selected for the front. LFE (channel 4) must
be disabled for audio loudness. Channels 5 and 6
are selected for surround sound
42 TP-00360-02
Creating a Project
Configuring Output Folders
You can configure output folders to put or copy files with different levels of severity into separate
folders. This makes the files easier to retrieve and manage.
To configure the output folders for a project, complete the following steps:
TASK
1. In the Create Project panel, click the plus + icon next to the Output Folders heading to
expand it:
2. Click the folder icon that corresponds to the level of where you want the files to be stored,
depending on their level of severity.
3. Select the Copy Files check box to copy the files to the location.
TP-00360-02 43
Configuring Reporting
You can configure the settings for the reports that are created when QScan analyzes the files in
your repository.
To configure the reporting settings for a project, complete the following steps:
TASK
1. In the Create Project panel, click the plus + icon next to the Reporting heading to expand
it:
There are two areas that you can configure; File Report settings and Project Report settings.
The File Report settings give you a list of events per file which is a detailed report per file.
To configure File Report settings:
2
3
4
5 6
2. Select Include events if you want to show the events in the PDF report. You can also select
the severity.
3. Select the maximum amount of events that you want to display in a report. The maximum
is 200.
4. Select Include Waveform to add a waveform reference, showing video levels, to each of
the events in the report.
5. Select Send by email. Note: you must have previously configured your email server. See
“Email Settings” on page 77
44 TP-00360-02
Creating a Project
6. Select Include thumbnails. Thumbnails are resized captured frames that give you a visual
reference of detected events.
The Project Report settings provide you with a summary of all the files in the project, with
the number of events found for each file. To configure Project Report settings:
7 8
9
7. Select Include files to include all of the files in the project in the report.
8. Select whether to include the following types of events in your reports:
• Green - logged events.
• Amber - warning events.
• Red - critical events.
9. Reporting frequency; select the day and hour settings.

10. Click the Select Administrator button under the Send e-mail to heading to configure the
report to send an email to the Administrator user.
10
11. Click Save project.
You have now created a project, and linked it to a watch folder or files within a repository. You
can now run this project to carry out analysis of the files in the watch folder. See “Running a
Project” on page 67.
TP-00360-02 45
Running a Project
You run a project to analyze the files in the watch folder that references the repository you
specified, using the parameters and thresholds you selected in the saved template. You can also
access the details of the project by clicking on the project name. This will take you to the Project
view, where you can also run the project, pause, and see the progress and results for each of the
files. From this view, you can then access the reports for each of the files.
To run a project to analyze files, complete the following steps:
TASK
1. Login to QScan. See “Logging into QScan” on page 27
2. Select the menu Projects.
2 3
4 5
3. Click the Play button that corresponds to the project that you want to run.
If the progress of the file is 0/0 files, this does not mean that the files for the project
have not been loaded, it means that no files have been processed yet.
4. Files in the watch folder of your project are automatically detected and analyzed. You can
view events as they are detected. You can also view projects that are running in the Task
List.
5. Results of the analysis are displayed on screen. Results are color coded for Logging,
Warning, Critical, and Errors, depending on the thresholds that you configured when you
created your project. Numbers for each of the color coded events represent the number of
files that have events of that specific severity.
Now that you have run a project to analyze your files, you can view reports that give you the
results of the analysis. See “Viewing Reports” on page 69
46 TP-00360-02
Viewing Reports
Viewing Reports
Before viewing reports, you must have run a project that analyzes files from a repository location,
together with a template that tells QScan how to analyze these files. See “Running a Project” on
page 67.
A report contains information about the files that you have analyzed when running a project. See
the following sections about viewing reports:
• “Viewing Reports as HTML files” on page 48

• “Viewing Reports as PDF files” on page 49
• “Viewing Report Video Details” on page 51
• “Viewing Reports as XML” on page 58
• “Sending Reports as Email” on page 59
• “Viewing Report Audio Details” on page 60
TP-00360-02 47
Viewing Reports as HTML files
To view the reports as HTML files that were made a result of running the project, complete the
following steps:
TASK
3. Click on the name of the project that you want to view the report for.
4. Click the HTML report icon under the Options heading.

5. The report details are displayed:
48 TP-00360-02
Viewing Reports
Viewing Reports as PDF files
To view the reports as PDF files that were made a result of running the project, complete the
following steps:
TASK
4. Click the PDF Report icon under the Options heading.

Note that in the project view there are two PDF icons. One for the project (next to the
pause, run, edit buttons) and one for the file, on the left hand side of the filename.
5. Select whether you want to open or save the file:
TP-00360-02 49
6. Open the report. It should resemble the following report:
50 TP-00360-02
Viewing Reports
Viewing Report Video Details
Using the Timeline
When you click on any parameter on the table where the parameters are listed, you can see a
graphical representation of that parameter in the timeline, so the behavior of the parameter
throughout the whole file can be easily seen. The table provides information about the values for
each of the parameters on the selected frame. Below the table there is a list of the events
corresponding to the current frame.
To view report video details using the timeline, complete the following steps:
TASK
3. Click on the name of the project that you want to view the report for:
2 3
4. Click the go to video details icon to display a graphical representation of the file
analysis:
4
5. Click on a value in the timeline to view the corresponding details in the table.
6. Click on a parameter in the table to see a graphical representation of that parameter in the
timeline.
TP-00360-02 51
7. In the screen shot below, Highest Chroma Level and Picture Quality Score have been
selected, as indicated by yellow and green lines:
52 TP-00360-02
Viewing Reports
Other Settings
TASK
3. Click on the name of the project that you want to view the report for:
2 3
4. Click the go to video details icon to display a graphical representation of the file
analysis.:
4
5. Step through each of the frames that have been analyzed by using the arrow buttons:
5 5
TP-00360-02 53
6. Toggle the display between 8 and 16 thumbnails by clicking the button:

6
7. Toggle the view between waveform and frame by clicking the button:
7
54 TP-00360-02
Viewing Reports
8. View general file information by clicking the button:

8
9. View stream details by clicking the button:

9
TP-00360-02 55
10. Toggle the view between events and frames mode by clicking the button:
10
Event mode: Will only show thumbnails corresponding to event start frames. Every time
you move to the next frame (by clicking the arrows on both sides of the big frame), it will
show the frame corresponding to the next event. When clicking anywhere in the timeline
graph, it will jump to the next event.
Frame mode: Will go frame by frame, both when stepping through the next frame (with the
arrows next to the big frame) or when clicking on the timeline graph. When clicking on the
timeline graph it will go right to the frame in the TC that was clicked.
11. Switch to audio analysis by clicking the button:

11
56 TP-00360-02
Viewing Reports
12. Select which types of events you want to display:

3a 3b 3c
a) Green - logged events.

b) Amber - warning events.
c) Red - critical events.
13. Make the main viewer larger by clicking on it:
TP-00360-02 57
Viewing Reports as XML
To view the reports as XML files that were made a result of running the project, complete the
following steps:
TASK
4. Click the get XML button.

5. Select whether you want to open or save the file:
6. Click OK.
58 TP-00360-02
Viewing Reports
Sending Reports as Email
To send reports as email you must have an email server and its settings configured on the QScan
system that you are using. See “Email Settings” on page 77. You must also have reporting
configured in the project that you are running. See “Configuring Project Details” on page 39.
When the email has been configured, an email is sent automatically when the analysis is finished
and the report is generated. This email setting can be forced to be sent when changes are made
to the project, such as changing thresholds.
To send reports as email, complete the following steps:
TASK
3. Click on the name of the project that corresponds to the reports that you want to send by
email:
2 3
4. Click the Send PDF report button:

4
5. The status of the report changes to reporting and the email is sent in the background
TP-00360-02 59
Viewing Report Audio Details
To view the report audio details, complete the following steps:
TASK
4. Click the go to audio details icon.

5. All the values for the audio parameters in the table are displayed. When you select one of
the parameters (like audio level) for one of the channels, the measured values for that
parameter are displayed in the timeline graph:
60 TP-00360-02
Chapter 6: Management
This section of the user guide describes the management functions in QSccan. These tasks are
most likely to be carried out by a system administrator. For the basic operation of QScan to
analyze files, see “Chapter 5: Basic Operation” on page 33
See the following sections that describe the management functions in QScan:
• “Working with Users” on page 62

• “Working with Nodes” on page 67
• “Setting up network shares as repositories” on page 72
• “Locale Settings” on page 76
• “Email Settings” on page 77
• “System Events” on page 78
• “Task List” on page 79
• “Displaying Full Screen” on page 80
TP-00360-02 61
TP-00360-02 Chapter 6: Management
Working with Users

See the following topics that describe how to work with users in the QScan system:
• “Viewing Existing Users” on page 62

• “Adding Users” on page 63
• “Editing Users” on page 65
• “Deleting Users” on page 66
Viewing Existing Users
To view the existing users on the system, complete the following steps:
TASK
1. Select the menu Management - Users.
2. The users that have been created are listed. By default there is a user named admin:
1 2
62 TP-00360-02
Working with Users
Adding Users
To add a user to the system, complete the following steps:
TASK
2. Click Add User:
1 2
TP-00360-02 63
3. Enter the following details for the user:
3a
3b
3c
3d
3e
a) Login name.
b) Name.
c) Password.
d) Role. The following roles can be configured:
- Administrator: can do everything in all menu options
- Designer: can perform all actions, except those listed in the management menu.
This menu will not be shown when the designer user logs in
- Viewer: can only view results of the project, but cannot create projects or perform
any administration tasks.
e) Email.
4. Click Add User.

5. The new user is displayed in the list of users:
64 TP-00360-02
Working with Users
Editing Users
To edit an existing user on the system, complete the following steps:
TASK
2. Click the Edit icon (pencil) that corresponds to the user that you want to edit:
1 2
3. Edit the user’s details as required.
TP-00360-02 65
Deleting Users
To delete an existing user on the system, complete the following steps:
TASK
2. Click the Delete icon (bin) that corresponds to the user that you want to delete:
1 2
3. You are prompted if you want to delete the user:
4. Click Delete.
5. The user is deleted from the system.
66 TP-00360-02
Working with Nodes
Working with Nodes

A node is a component of a network, connected to other nodes to distribute the work in different
machines. In QScan, nodes are machines other than the "master" machine, where analysis tasks
take place.
Nodes must have the QScan_node software running; this does not include a GUI. At installation,
a default node is created. Nodes can be configured in QScan in the NODE menu option. The
default password for the nodes is: NodePassword.
See the following topics that describe how to work with users in the QScan system:
• “Viewing Existing Nodes” on page 67

• “Adding Nodes” on page 68
• “Editing Nodes” on page 70
• “Deleting Nodes” on page 70
• “Blocking Nodes” on page 71
Viewing Existing Nodes
To view the existing nodes that are on the system, complete the following steps:
TASK
2. The nodes that have been created are listed. By default there is a node named localhost:
2 1
TP-00360-02 67
Adding Nodes
This task is only for QScan Max users. To add a node to the system, complete the following steps.
TASK
2. Click Add Node.
1
68 TP-00360-02
Working with Nodes
3. Enter the following details for the new node:
3a
3b
3c
3d
4
a) Node Name.
b) IP/Hostname - the IP address of the node. This is needed for the master node to
connect to the worker node.
c) Password - the password for the node. It can be set in the registry of the node (not
recommended). The default password is: NodePassword and should be used by
default unless it has been changed in the node registry.
d) Analysis Points - the number of points assigned to the worker node. It should be 4 in
QScan Max systems, but it can actually be changed and more/fewer points assigned
to the node.
4. Click Save Node.
TP-00360-02 69
Editing Nodes
To edit an existing node, complete the following steps:
TASK
2. Click the Edit icon (pencil) that corresponds to the user that you want to edit:
1 2
3. Edit the node’s details as required.
Deleting Nodes
To delete a node from the system, complete the following steps:
Do not delete the default localhost node, because this will leave your system unstable.
TASK
2. Click the Delete icon (bin) that corresponds to the node that you want to delete.
3. You are prompted if you want to delete the node.
4. Click Delete.
70 TP-00360-02
Working with Nodes
Blocking Nodes
You can block a node so that it is not used for analysis, for example, if another user is using it, or
if it is switched off, blocking a node allows you to avoid using it.
TASK
2. Click the Block icon (padlock) that corresponds to the node that you want to block.
1 2
3. The node is blocked and a message is displayed:
TP-00360-02 71
Setting up network shares as repositories

A repository is a storage location where watch folders reside that contain the files QScan analyzes
when a project is created. A repository can be located in the machine where QScan is running, or
in a remote machine accessible on the network. To use a remote repository, you must enter the
UNC path, user name and password to access the networked drive. When you create a repository,
you must complete the information in the fields that appear in the window. The actions that may
be carried out consist of edit and delete. You cannot assign a watch folder to a project if you do
not have a repository containing the watch folders, added first. You cannot delete repositories
that are being used by projects. See “Creating a Repository” on page 34
See the following topics that describe how to use repositories:
• “Viewing Existing Repositories” on page 72

• “Adding Repositories” on page 73
• “Editing Repositories” on page 74
• “Deleting Repositories” on page 75
Viewing Existing Repositories
To view the repositories that currently exist on the system, complete the following steps:
TASK
2. The repositories that have been configured are listed:
72 TP-00360-02
Adding Repositories
To add a repository to the system, see “Creating a Repository” on page 34
TP-00360-02 73
Editing Repositories
To edit a repository that currently exists on the system, complete the following steps:
TASK
2. Click the Edit icon (pencil) that corresponds to the repository that you want to edit.
1 2
3. Edit the fields as required. See “Creating a Repository” on page 34 for more information on
these fields.
74 TP-00360-02
Deleting Repositories
You cannot delete a repository that is currently being used by a project. You must delete
the project first and then delete the repository.
To delete a repository that currently exists on the system, complete the following steps:
TASK
2. Click the Delete icon (bin) that corresponds to the repository that you want to delete.
3. You are prompted if you want to delete the repository:
4. Click Delete.
TP-00360-02 75
Locale Settings
You can configure locale settings to produce reports that match the language and time zone that
you are working in, and to change the User Interface Language.
To configure locale settings complete the following steps:
TASK
1. Select the menu Management - System Settings.
4 3 2
2. Use the Timezone drop down list to select the timezone that you are working in.
3. Use the Report charset drop down list to select the character set that is used in the reports,
for example Japanese characters. This only applies to PDF reports. If you want to have a
specific parameter name in Japanese in the report, you must translate that parameter
name to Japanese, If you then want to see it in the report, you must add the character set
for Japanese.
4. Use the System language drop down list to select the language for your User Interface.
This setting also affects what language the HTML reports are displayed in.
For the system language to change, a .pot file is needed. This .pot file contains all
the strings that are subject to be translated. The .pot file is then edited, with the
translated strings, and when compiled will generate a .po and a .mo file as outputs.
These files need to be in a specific location in the installation folder to be valid.
Contact our support team for more advice about how to use the .pot file to translate the User
Interface language.
5. Click Update Settings. The next time you run a project the corresponding reports will use
these settings.
76 TP-00360-02
Email Settings
Email Settings
You can configure the email settings so you can send reports to a specific email address.
To configure email settings complete the following steps:
TASK
1. Select the menu Management - Email Settings.
8
9
2. Enter the SMTP address. An SMTP server is the machine that takes care of the email
delivery process in QScan. This takes the format of [email protected]
3. Enter the port that you want the email server to use. The default value is 25.
4. Select the type of protocol that you want to use. You can select from the following three
options:
• None
• TLS
• SSL
5. Enter the name of the email user.

6. Enter a password for the email user.
7. Enter the name of the sender address as it will appear to the receiver.
8. Optional: Enter the name of an email address that you want to send a test email to.
9. Click Update Config.
TP-00360-02 77
System Events
You use the System Events area to view events that have happened in the system. These events
are not editable, they are for information purposes only.
To view system events, complete the following steps:
TASK
1. Select the menu Management - System Events.
4
2. Events are color coded:

• Green - a logged event.
• Amber - a warning for an event.
• Red - a critical event.
3. If you want to delete an event, click the delete icon next to the event.
4. If you want to clear all of the events so the panel is empty, click Clear All Events.
78 TP-00360-02
Task List
Task List
The task list displays information about projects that QScan is running.
To view system events, complete the following steps:
TASK
1. Run a project to analyze some files. See “Running a Project” on page 46.
2. Select the menu Task List. The files that are being analyzed are displayed:
3 4 5 6 7 8 9 10 11
12
13
3. The task number is displayed.

4. The name of the file that is being analyzed is displayed.
5. The name of the project that is running is displayed.
6. The format containers are displayed.
7. The size of the project is displayed.
8. You can change the priority of a file using the Priority buttons.
9. The name of the node that the project is running in is displayed.
10. The progress of the project analysis is displayed.
11. The status of the report is displayed, for example analyzing.
12. You can pause the analysis clicking the pause button under the Actions heading.
13. You can stop the analysis by clicking the stop button under the Actions heading.
TP-00360-02 79
Displaying Full Screen

You can display QScan in full screen, so your browser window and tabs are not displayed.
To display QScan in full screen complete the following steps:
TASK
1. Select the menu Management - Full Screen.
2. QScan is displayed in full screen:
3. You can exit full screen in one of two ways:

a) Press the Escape key on your keyboard.
b) Select the menu Management - Exit Full Screen.
80 TP-00360-02
Chapter 7: Advanced
This section of the user guide describes the advanced functions in QScan that are most likely to
be carried out by a system administrator. For the basic operation of QScan to analyze files, see
“Chapter 5: Basic Operation” on page 33
See the following sections that described advanced functions in QScan:
• “Using a Default Template” on page 82

• “Creating a Template” on page 84
• “Single Pass Analysis” on page 85
• “The Detailed View” on page 88
• “Macros” on page 91
• “Integration of QScan with EditShare and Flow” on page 111
TP-00360-02 81
Chapter 7: Advanced
Using a Default Template
A template is a collection of pre-set parameters and their thresholds to be used for file analysis. A
template is used with a file repository location and project settings. You can either use a previ-
ously defined template for common tasks, or create your own template when you create a
project. Once created, templates can be edited or deleted. This task describes using one the
default templates that is shipped with QScan.
TASK
2. Select the menu Templates. A list of the default templates that are shipped with QScan are
displayed.
2 3
3. Click the heading of the template to display its settings. For example, for Photosensitive
Epilepsy (PSE) the following settings are used:
4. Click the download button that corresponds to the template that you want to use.
5. Choose whether to Save or Open the file.
82 TP-00360-02
Using a Default Template
6. Click OK.
7. If you have chosen to save the file, browse to the location of your downloaded files.
TP-00360-02 83
Chapter 7: Advanced
Creating a Template
A template is a collection of preset thresholds and parameters to be used for file analysis. A
template is used with a file repository location and project settings. You can either use a
previously defined template for common tasks, or create your own template when you create a
project. Once created, templates can be edited or deleted. You can create a template using the
template menu, as described in this task, or when you are creating a project, see “Creating a
Project” on page 37.
To create a template, complete the following steps:
TASK
2. Select the menu Templates - Add Template.
3. Enter a name for the template.
3 2
4. Expand the heading that corresponds to the type of checks that you want to perform.
5. Select the thresholds that you want to search the files with, depending on your video
formats. Click the no entry button next to a parameter to deselect it. Some parameters such
as video dropout take up a lot of CPU usage, so you may want to deselect these
parameters. See “Appendix 6 - Template Parameters” on page 187
6. Note: You can also create a template when you create a project. See “Creating a Project”
on page 37 for more information on the different areas that you must configure.
7. Click Save Template.
84 TP-00360-02
Single Pass Analysis

With Single Pass Analysis you create a template, test a file, and then adjust the threshold for any
parameter and see the results of the change immediately.
In the following example, we will be changing how the severity of freeze frames in one file in a
watch folder are logged. You can apply this example to whatever you are looking for in your files.
In this task, freeze frames are firstly logged as normal events, indicated in green. This threshold
setting is then changed so freeze frames are logged more seriously as warnings, indicated in
amber. When this threshold setting is changed the project is automatically updated, without
having to run it again.
This task gives you an example of a simple threshold parameter change. You can apply this
example to other template thresholds. You can configure template parameters, run projects to
analyze files, and adjust the threshold values until you get the desired results.
Before you can complete this task, you must have a repository configured that contains the files
that you want to analyze. See “Creating a Repository” on page 34.
TASK
2. Select the menu Projects - Add Project.
3. Enter a name for your project. Type Freeze Frames.
4. In the Create Project panel, click Add File Input.
2 3
5. Click the tick icon that corresponds to the watch folder that you want to use. For this
example a watch folder named Freeze Frames has already been created.
7 6
6. The Freeze Frames repository is now listed in the project area.

7. Click the x icon to close the Add File Input dialog.
8. Expand the Analysis heading.
9. Expand the Video Content heading.
TP-00360-02 85
Chapter 7: Advanced
10. Select Freeze by clicking the plus sign + next to it.

8
10
11. The Freeze Video Content threshold value details appear. If you cannot see them scroll
down the screen until they are visible.
12. Select Equals from the drop down list.
13. Type 100.
11
12 13 14
14. Leave the default setting of Logging (green) selected.

15. Scroll down and click the Save project button. A message displays telling you the project
has been saved.
16
18 19 17
17. Click the play button for the newly created project to run the project.
18. You may have to wait a few moments for the results to display.
19. The freeze frames have been logged (indicated in green), along with the number of files, in
this case there is only one file in our watch folder so the UI displays 1.
86 TP-00360-02
20. Click the name of the project in the list.

19 21
20
21. Edit the project by selecting the pencil icon under the project heading:
22. Expand the Analysis heading, then Video Content to view the current freeze frame
threshold settings.
23. Change the severity of the freeze logged event by clicking the Warning tab (amber).
23
24. Scroll down and click the Update Project button. A message is displayed telling you that
the project has been saved.
25. Click the projects heading.
26. The freeze frames are now logged as warning events, indicated in amber. The results have
been automatically updated without having to run the project again.
25
26
TP-00360-02 87
Chapter 7: Advanced
The Detailed View
You can use the detailed view to navigate along a timeline, frame by frame, and understand the
values of selected parameters and tested results. This is also shown in a graph for any given frame.
This makes it particularly easy to spot trends within the content. There is also a waveform monitor
and a vectorscope. If a file has failed, you can make changes to the threshold values in the
templates, and then see the results on the timeline. As with single pass analysis, any changes you
make take effect immediately without having to stop and start the file analysis.
For this example, we are using a file in our repository that contains DigiBeta errors and interlacing
artefacts, and we are going to change their threshold values, and see the effects of this on the
timeline. You can apply this example to whatever you are looking for in your files. Before you can
complete this task, you must have a repository configured that contains the files that you want to
test. See “Creating a Repository” on page 34.
To see changes to file analysis in the detailed view, complete the following steps:
TASK
2. Create a new project. See “Creating a Project” on page 37. Select a repository that contains
the artefacts and DigiBeta error files.
3. Expand the Analysis heading.
4. Expand the Video Content heading.
5. Select Interlacing Artifacts by clicking the plus sign next to it.
6. Leave the default setting of Greater than > 20.
7. Expand the Video Quality heading.
8. Select DigiBeta Error.
9. Leave the default setting of greater than > 20.
10. Run the project.
11. Click the detailed view button to see the levels.
12. Go to the project again and edit it by selecting the pencil icon under the project heading.
13. Change the Interlacing Artefacts value to > 50.
14. Change the DigiBeta Error value to >10.
15. Click Save project.
16. Click Projects.
17. Click the name of the project.
18. Click the detailed view button again.
19. You can see that the result events numbers have changed. In the second case you will see
fewer events for interlacing, and more events for DigiBeta errors.
You can keep adjusting the thresholds for file analysis and immediately see the changes,
until you get the desired results, without having to stop and start your project to perform
file analysis.
88 TP-00360-02
The Detailed View
Jumping to a Specific Time Code in the detailed view
You can jump to a specific time code in your files in the detailed view by using the Go To dialog
box. This is useful when you are working with large files and searching through them becomes a
time consuming task. You must have previously run a project to analyze your files to carry out this
task. See “Running a Project” on page 46.
TASK
2. In the Projects view, click on the title of a project that you have previously run.
3. Click on the go to video details icon to display the detailed view:
4. Click the switch to frames mode button:
TP-00360-02 89
Chapter 7: Advanced
5. Click the Jump to a specific TC in the timeline button:
6. Choose the Unit with which you want to search; you can choose between time code,
frames, and milliseconds:
7. Select the time code text and overtype the number of the frame that you want to jump to:
8. Click the Go To... button. You are taken to the frame that you selected.
90 TP-00360-02
Macros
Macros
Context
Before version 3.1 QScan allowed users to create simple thresholds with only one parameter. The
current Delivery Specifications defined by Networks and Broadcasters present more complex
scenarios that needed to be addressed by QScan.
Situations like detecting if a specific format parameter is not ANY of those in one set of
parameters, or whether some specific combination of format parameters or quality parameters
are met, needed a more innovative way of definition and detection, but maintaining the ease of
configuration into Projects and Templates in QScan.
Some common situations include:
• Detecting whether the frame rate is any of: 23.976, 24, 25, 29.97, 30, 50, 59,94, 60.
• Detecting whether the resolution is any of: 1920x1080, 3840x2160, etc.
• Detecting when there is a black frame with no audio, therefore only detecting black frames
that are also missing audio.
• Detecting when there is a color bar and test tone at the same time.
The idea is to group several thresholds using logical operators into a macro and use that macro
of boolean combinations of simple thresholds as simple thresholds in projects and templates.
See the following sections that describe how to use macros:
• “Opening the Macro User Interface” on page 92

• “Elements of the GUI” on page 93
• “Creating a Macro” on page 94
• “Parameters and Logical Gates” on page 96
• “When a macro is ready to use” on page 97
• “Finishing a Macro” on page 98
• “Exporting a Macro” on page 99
• “Importing a Macro” on page 100
• “Using Macros in Projects and Templates” on page 101
• “Logical Gates” on page 103
• “Sample Macros and Tips” on page 105
TP-00360-02 91
Chapter 7: Advanced
Opening the Macro User Interface
From version 3.1 onwards, there is a new menu option called Macros. To define a Macro, the first
thing to do is to click on this menu option.
Clicking the Macros menu opens the Macro design layout user interface.
92 TP-00360-02
Macros
Elements of the GUI
The following diagram describes the elements of the Graphical User Interface (GUI) in the Macro
design layout:
Logical Operators Parameters
List of Created
Macros
Macro Schema
(where macros
are created)
Macro Macro
Name Schema
Macro (JSON)
Description
Macro
Status
TP-00360-02 93
Chapter 7: Advanced
Creating a Macro
TASK
2. Click Add Macro.
3. Select the Macros menu.
4. The Macro view is launched, with the AND operator displayed as default.
3 7 5 6
7
4
5. Select the Video Content menu. A drop down list of parameters/operators is displayed.
6. Click on the Blackness menu option.
7. Hold down your left mouse button and drag the Blackness option over the AND operator
until you see that the AND operator is highlighted with a white box and displays the text
Blackness.
8. Release the mouse button to link the blackness item to the AND operator:
9. Select the Audio menu.

10. Click on the No Audio menu option.
94 TP-00360-02
Macros
11. Hold down your left mouse button and drag the Blackness option over the AND operator
until you see that the AND operator is highlighted with a white box.
10 8 9
10
12. The Blackness and No Audio components are linked to the AND operator:
13. The macro will search for files with no picture AND no audio at the same time.
14. This macro is now ready to use, as indicated by its status:
15. Type a name for your macro.

15
17
16. Add a description of the macro. This is not mandatory but is useful for example if other
people are going to use it.
17. Click Save Macro. Note: You can save a macro at any time in its creation process. It does
not have to be in the ready state.
18. The newly created macro appears in the list.
TP-00360-02 95
Chapter 7: Advanced
Parameters and Logical Gates
You can drag and drop as many parameters and logical gates, and they can only be attached to
other logical gates. A parameter is the last element of a macro.
Each of the elements in a macro definition have several icons:
1) Parameters - red cross denotes delete parameter.

2) Logical Gates - red cross denotes delete the gate and all its children.
3) Logical Gates - switch button denotes change the kind of gate (AND, OR, XOR).
3
2
1
As you are creating a macro, the JSON schema is automatically generated. This can later be
copied/pasted into another macro if needed:
This JSON schema is editable text. You can change the default value of macro thresholds, copy all
of the schema, or paste other schema into this area.
96 TP-00360-02
Macros
When a macro is ready to use
A macro is ready to use when the last level of logical gates finish with at least two parameters, For
example, in the screen shot above, the macro only has one parameter, so the macro is in the
“editing” state. If another parameter is added, the macro is ready to use:
If you want to hide a macro in the projects view, you can block the macro by clicking on the lock
icon:
TP-00360-02 97
Chapter 7: Advanced
Finishing a Macro
A macro can always be saved, whether it is in the ready status or not.
TASK
1. Type the name for your Macro in the Macro Name field.
2. Click in the description text box below the macro name and add some text. It is always
helpful to edit the description with specific details about the macro, especially when the
amount of macros grow.
1
2
3. Click the Save Macro button.

4. When the Macro is saved, it will be displayed in the macro list.
98 TP-00360-02
Macros
Exporting a Macro
Macros can be exported to be used in other QScan installations, or to have a backup of the macro.
TASK
1. Click on the macro that you want to export.
2. Click the Export Macro button.
3. Choose whether you want to open or save the macro:
4. A file is created and downloaded to your local machine with the format
macro_name.macro.
5. The macro is loaded and displayed in the list of created macros.
TP-00360-02 99
Chapter 7: Advanced
Importing a Macro
You can import a macro that has been created, for example by another user on a different QScan
node (system).
TASK
1. Click Add Macro.
2. Click Import Macro.

3. Browse to the location of the macro file that you want to import and click Open.
4. As soon as it is selected it will be added to the macro list and will be displayed in the macro
design layout.
100 TP-00360-02
Macros
Using Macros in Projects and Templates
Macros can be used in Projects and Templates (note that Macros can only be added to Templates
from version 3.2 and above). When editing a project or template, the last parameter group
contains all macros that are ready or unlocked.
TASK
1. Select the project or template that you want to use. In the example below we will use a
macro in a project. You can use the same instructions from a template.
3. Scroll down to the macros heading:
4. Click the add button to the side of the macro that you want to use. The macro settings are
added as thresholds to the project/template.
TP-00360-02 101
Chapter 7: Advanced
5. You can change all values of each of the parameters of the macro as if they were simple
thresholds, as well as the duration for the macro threshold to be violated as well as the
severity level of the whole macro.
6. Click Save Project.
102 TP-00360-02
Macros
Logical Gates
The following section provides a description of the logical gates that you can use to create
Macros.
AND Gate
An AND gate will result in a TRUE condition, only when all parameters are TRUE. So, in a simple
condition like, A AND B, the result will be TRUE only when A and B are true at the same time. A
simple macro like the one depicted below will only trigger an event when both Start TC
conditions are met.
OR Gate
The OR Gate will always provide a TRUE when at least ONE condition is met. That means that
when ONE, TWO or MORE conditions are met, the result will be TRUE. The following macro shows
a sample macro with an OR Gate:
TP-00360-02 103
Chapter 7: Advanced
XOR Gate
The XOR gate will result in TRUE only, and only when either condition is met. That is, only one
condition needs to be met for the result to be TRUE. It will be FALSE when more than one
condition is FALSE or when more than one condition is TRUE. The following macro shows a
sample macro with an XOR gate:
In this case, the result will be true when ONLY either one of the frame rate conditions is TRUE.
IMPORTANT NOTE: The operation of a macro will depend greatly on the threshold condition
that is configured in a project/template. Therefore, you must be careful when selecting the gates
and conditions on the thresholds, because they can become complex to configure. It is
recommended that you have a clear idea of the conditions that will be configured in the
project/template before implementing a macro.
• So, when you need to detect when something is NOT either one of a set of values, the right
gate to use will be an AND gate, configuring in all thresholds the IS NOT condition.
• If you want to know when something IS in a specific set of values, the OR gate will be the right
one to use.
104 TP-00360-02
Macros
Sample Macros and Tips
This section describes several macro designs that convey how simple also how and extremely
complex a macro can be. It all depends on the creativity of the user.
1. Check if Resolution is not any of...
In this case, the macro will detect whether the resolution is not any of the following:
• 4096x2160
• 3840x2160
• 2048x1080
• 1920x1080
Note that the macro in this case is combined by an AND gate, so will only be TRUE (triggering an
event) when all conditions are met.
The setting for this macro in the project/template would be:
TP-00360-02 105
Chapter 7: Advanced
2. Check when 2 seconds of black are found in 29.97 or 30fps
This Macro is intended to trigger an event when 2 seconds of black are found. Since the number
of frames will depend on the frame rate, we are showing here a simple macro for detection in
29.97 and 30fps case.
Note that for this condition to meet, the frame rate needs to be EITHER 29.97 or 30 fps, AND the
black must be above a certain level.
106 TP-00360-02
Macros
3. Trigger an event when a J2K profile and level/sublevel are NOT according to the
specification...
This macro is a real and complex one. In this case, the goal is to trigger an event when a specific
combination of resolution, framerate and J2K profile and mainlevel/sublevels are NOT met.
In this particular case, the specification is:
• 4K/UHD j2K Level/Sub-Level
– Frame rates up to 30 fps use: IMF Mainlevel 6 (Sublevel 3, Max 800 Mbit/s)
• 2K/HD J2K Level/Sub-Level:
– Frame rates greater than 30 fps use: IMF Mainlevel 5 (Sublevel 3, Max 800 Mbit/s)
So, the macro layout is as follows:
TP-00360-02 107
Chapter 7: Advanced
This also requires that the correct values are configured in the project/template where the macro
is to be used:
108 TP-00360-02
Macros
4. Trigger an event when the video encoding is NOT any of...
This Macro detects when the video encoding is not:
• RGB/4:4:4/12 bits
• YUV/4:2:2/10 bits
The thresholds that need to be configured in the project/template:
TP-00360-02 109
Chapter 7: Advanced
5. Trigger an event when the start time code is NOT 00:00:00:00
In this case, since it is not specified whether it should be drop frame or not, we need to consider
both options. So, the macro would look like this:
And the threshold configuration in project/template would look like this:
110 TP-00360-02
Integration of QScan with EditShare and Flow

There are three ways in which QScan, EditShare, and Flow can work together:
1) QScan only uses media spaces in EditShare storage as repositories, and Flow is not
involved. This is supported by any EditShare version and QScan version 3.1.
2) QScan uses EditShare media spaces and updates Flow with the results of the analysis. This
is supported by Flow version 2018.1 and QScan version 3.1.
3) QScan uses third party storage and updates Flow with the results of the analysis. This is
supported by Flow version 2018.1 and QScan version 3.1.
In the last two scenarios, whenever a file is analyzed by QScan, if such a file belongs to a Flow clip,
the following should happen:
• The resulting QC events are added in Flow as markers in the clip.

• The resulting PDF report can be retrieved and stored in the same media space as the clip and
is associated with the clip.
• The clip in Flow can have a field with the URL to the HTML report in QScan.
There are three ways in which the QC analysis can be started:
1) From the QScan User Interface: By creating a project, adding files and running it. When
the analysis ends, QScan invokes a Flow trigger app, FlowQScanTrigger, which uses the
analysis results to update the Flow database.
2) From the Flow Automation User Interface: By creating a template with a QScan QC task,
which receives a list of clips to analyze, and the media files of those clips are sent to QScan
for analysis. A project is created per clip which includes all its media files. Flow Automation
monitors the progress and when done, retrieves the results to update the Flow database.
3) From FlowStory or FlowBrowse: By triggering a FlowAutomation template similar to the
one described before.
How to make QScan use EditShare media spaces
For QScan, EditShare media spaces are like any other SMB/network share. However, some
prerequisites and considerations must be taken into account.
TP-00360-02 111
Chapter 7: Advanced
The main issue
Most of the problems when setting up QScan to work together with EditShare & Flow come from
the fact that once that Windows establishes access to a remote system with a given set of
credentials (user/password), the same credentials should be used for any other file access to that
remote system, even if it is for a different shared folder. Unix-based systems do not have this
limitation.
Example:
• Program A gets access to \\192.168.97.101\\MyFolder, with credentials "admin"/"123"; this

works.
• Program B tries to get access to \\192.168.97.101\\MyOtherFolder, but with different
credentials; this will fail.
This condition is cleared if the system is rebooted.
Prerequisites
• Make sure that QScan has been set up and tested separately.
• The QScan services must NOT be running using the built-in “System” user, but with a user
with Administrator rights. This is very important, because otherwise the QScan service does
not have access to folders in the network. The QScan setup now allows you to select the user
for its services, so that is the easiest way to set it. But, in case you didn’t do so, or want to do
it manually, follow these steps:
TASK
1. Open the Services window.
2. Look for the two QScan services: QScan service and QScan web service.
3. Right click the QScan service, and from the menu select Properties.
4. Select the Log on tab, and check if Local system account is selected. If so, this must be
changed.
5. Select This account, which will enable the Browse button.
6. Click Browse which will open the Select User window.
7. In that dialog, in the Enter the object name to select field, type the name of the user with
Administrator rights, then, click the Check names button.
8. Click OK to close the Select User dialog.
9. Click OK again to close the Properties window; a message will pop-up notifying that the
service must be restarted so the changes, but don't do it yet.
• In the QScan application, review if there are any repositories pointing to the EditShare media
spaces; if you have any of these (probably created by previous tests), please delete them in
the QScan UI. This is necessary because later we will redo these repositories.
• Reboot the QScan system.
112 TP-00360-02
Adding a Repository
You must create one repository for each EditShare media space that you want to access from
QScan. For the definition of a repository, see “Repositories” on page 186.
TASK
2. Click Add Repository.
2
3. Type a name for the repository. This is the name with which it will be referred to in QScan,
and is not the share’s name.
3 4
4. Leave the Allow All Users check box selected.

5. Click the Set Repository shared folder icon.
TP-00360-02 113
Chapter 7: Advanced
6. The Select a shared folder dialog displays:

6a
6b
a) Fill in the full UNC path to the remote system and the share (don’t forget that EditShare
shares have the “_1” suffix), user and password.
b) Click Connect to test the access to the remote system.
c) If access is permitted a new dialog opens, showing the content of the folder. After
closing that dialog the path field shows the UNC path to be used.
d) Click Save Repository.
7. The newly created repository is displayed.

Another option is to use EditShare connect to map network drives in the host system.
If you are using mapped network drives, follow the same steps as before, but change these
steps from step 5:
8. Click Set Repository Folder. A dialog displays, showing the available drives (including
network drives).
10 9
9. Select the root of a network drive by clicking the blue tick to the left of the drive letter.
10. To browse to a folder path within a drive, click the folder icon to the left of the blue tick icon
and then click the blue tick icon that corresponds to the folder that you want to use.
11. The path field shows the local path that has been chosen.
114 TP-00360-02
Installing FlowQScan Trigger
Follow the prerequisites in “Prerequisites” on page 112.
TASK
1. Run the installer of the Flow QScanTrigger:
FlowQScanTrigger-<version>-<revision>-x64.msi
2. Navigate to the folder in which the installer leaves the software. By default this is:
C:\Program Files\EditShare\Flow\QScanTrigger
and locate the file flow.bat.
3. Copy flow.bat to the folder
C:\Program Files\(x86)\Quales.TV\Quales\triggers\1\analyzed\
One limitation of the way QScan executes the trigger applications is that the environment
variables do not work, so the batch file cannot use %PROGRAMFILES(x86)% and instead
have the hardcoded path. You must manually edit this in systems with Windows in
languages other than English.
4. The trigger application:
• Requires an .ini file.
• Writes a log file every time it is run.
The .ini file and the .log file are stored in the following locations:
C:\Users\<user>\AppData\Roaming\EditShare\FlowQScanTrigger.ini
C:\Users\<user>\AppData\Local\EditShare\FlowQScanTrigger\*.log
5. Edit the FlowQScanTrigger.ini set the host IPs, user, and password that will be used
(description of those parameters is below).
6. Open the QScan User Interface:
a) Add one repository per each Flow Media Space with clips that need to be analyzed.
b) Create a project and add as inputs the media files for those media spaces.
7. When the analysis has finished, use FlowBrowse/AirFlow/FlowStory, and look for the clips
or files that have been analyzed; load each one into the browser by double-clicking on it
and check the following:
• The right-hand pane, under the Marker tab shows all of the QC events found, with their
descriptions.
• The central pane, under the Metadata section, shows the PDF report as an associated
file (only in FlowBrowse).
• The PDF file appears next to the clip in the Media Space content list.
TP-00360-02 115
Chapter 7: Advanced
Parameters in FlowQScanTrigger.ini
The following parameters are in the General section:
• qscan-host: The IP address of where the QScan web service runs; by default, this is the local
host (127.0.0.1) because the trigger app runs in the same system as the rest of the QScan
software. This setting is useful when performing tests on other systems.
• flow-host: The IP address of the where the Flow API service is running.
• flow-username: The user to log in to Flow services (usually this would be automation).
• flow-password: The password of the above user.
• test-mode: A boolean setting. When enabled, the application does not try to access the Flow
services; this was added to facilitate testing of QScan.
• generate-pdf: A boolean setting that tells if the PDF report must be generated and
associated with the Flow clip.
• keep-all-pdf: A boolean setting that determines what to do if the analyzed clip already has a
PDF report associated with it; if set to 'true', then it will keep all PDF reports; otherwise, it will
keep only the most recent one.
116 TP-00360-02
Using FlowAutomation with QScan
Follow the prerequisites in “Prerequisites” on page 112 but consider the third party storage
managed by Flow. Review if there are any repositories pointing to EditShare media spaces or to
the third party storage managed by Flow; if you have any of these (probably created by previous
tests), delete them in the QScan User Interface. This is necessary because later we will redo these
repositories.
Setup in EditShare
The steps differ depending on the storage used:
• EditShare storage: Make sure that all the media spaces that are going to be used for QC can
be accessed by the default user in FlowAutomation. (This is set in FlowControl).
• Flow Standalone with third party storage: The same rule as before applies, only that the
default user in Automation is set in the Settings of FlowAutomation (cogs icon). Remember
that if those media spaces are in the same system, they must be accessed using the same
user/password.
TP-00360-02 117
Chapter 7: Advanced
Setup in FlowAutomation
TASK
1. Create a new template.
2. Add nodes so that clips are selected and then sent to a QC QScan task. The following are
suggested to test how it works:
a) Manual trigger.
b) Media Space Input (pointing to one of the media spaces that have been check in the
previous step).
c) QScan QC filter.
d) Metadata Tasks, connected to the “Pass” pin code of the QC node, and set the
“Comment” field to “QC passed”.
e) Metadata tasks, connected to the “Fail” pin code of the QC node, and set the
“Comment” field to “QC failed”.
3. Go to the QC QScan task node and edit its properties as follows:

• User: The user to access the QScan system (for example, admin).
• Password: The password for that user.
• HostIP: The host IP where the QScan service runs.
• Template: The template allows you to choose which QScan QC template to use; this
drop-down list is filled only if the Automation can login to the QScan system, and
therefore, only works if the user, password and IP are correct.
• Priority: 1: low, 2: medium, or 3: high.
• Speed: 1: for slow 5: for medium, 10: for full speed, 15: for very-high.
• Max. concurrent analysis: The maximum number of files of the QScan project that will
be simultaneously analyzed.
• Create PDF: If checked, then at the end of each analysis, the PDF report will be retrieved
and associated with the clip, stored in the same media space, and they will be
associated.
• Field for URL report: This setting lets the user choose a custom metadata field where
to set the URL to directly access the QC report in HTML format; this field must be of type
"URL link".
• Delete project: If checked, then the QScan Project will be deleted once the analysis has
been completed; by default, is disabled, as if the Project is deleted, all the analysis
results are deleted too in QScan (but in Flow will remain as Log Entries and PDF report).
Setup in the Automation template.
TASK
1. Click Test Template to test the Automation template; this will retrieve the list of clips in
the media space and instruct the QScan service to create one project per each clip (adding
to the project all the media files that belong to the clip). The Project will be created in
QScan, but not started, so you can review if everything is OK.
2. To review it, click on the Project, and don't panic if it says "0 files", because that's what
happens when the Project hasn't been started;
118 TP-00360-02
3. Click Edit to check the files that were added:
4. A new page is displayed with the features of the project.

5. If the files are OK, you can manually start the Project, by clicking the Play button:
6. If the previous step was OK, the run the Automation template, by clicking the Activate
button; this will create the Projects and start them.
7. When each one of its files reaches the analyzed state, its results will be added to the Flow
DB as Log Entries and PDF report (as described above for the FlowQScanTrigger section).
Troubleshooting
If these procedures do not work, check the following:
• In the QScan UI, go to Repositories and there the "_flow" repository should have been
created, pointing either to the IP where the shared folders are (either the EditShare or the
third party). Unfortunately, from there it is not possible yet to check which user is being used.
• Open the QScan log file, located in the following folder:
C:\Program Files (x86)\Quales.TV\Quales\QAPI\log\quales.log
• Search for the IP of the system. There may be error messages such as “A specified logon
session does not exist”. If this is the case, there is a problem with the network credentials, so
double check the above prerequisites.
Triggering a QC automation template from FlowStory or FlowBrowse
TASK
1. Create a new FlowAutomation template following the steps in the previous section, only
that instead of using a Manual trigger, choose an External trigger.
2. Set the following properties for this trigger:
• Trigger on: Clips.
• Allowed users: Here you can choose "All" or select particular users.
• Showclients: Must be checked.
3. Save the template with the name you want to appear in the client application
(Story/Browse) menu.
TP-00360-02 119
Chapter 7: Advanced
4. Activate the template; only active templates are seen by the client applications.
5. Go to the client application, select a clip, and open the context menu; there is an
Automation sub-menu, which in turn has a sub-menu with the templates for the current
user.
120 TP-00360-02
Can FlowQScanTrigger and FlowAutomation interfere with each other?
Given that a user may want to start analysis either from Flow or from QScan, is desirable that both
Flow-QScan integrations can be installed and used at the same time.
Of course, as at the end of each analysis, the FlowQScanTrigger is always called, we could end up
with having repeated log entries and PDF reports, if such analysis was ordered from
FlowAutomation.
To prevent that, FlowQScanTrigger checks the name of the project, and if it includes the words
"Flow" and "job" means that it was created by FlowAutomation, and then no further processing
is done.
TP-00360-02 121
Chapter 7: Advanced
122 TP-00360-02
Appendices
See the following appendices for more information about QScan:
• “Appendix 1 - IMF” on page 124

• “Appendix 2- PSE (Photo Sensitive Epilepsy)” on page 143
• “Appendix 3- Supported Formats” on page 145
• “Appendix 4 - Template Parameters” on page 147
• “Appendix 5- Troubleshooting” on page 179
TP-00360-02 123
Appendices
Appendix 1 - IMF
The Business Benefits of IMF
New mastering formats don’t come along very often in the media industry. So when they do, they
need to justify the investment and change management required to make them the new way of
doing things.
IMF is such a new mastering format. It has existed for a while as a mastering standard suitable for
premium content. But now it is also being developed as a specification for broadcast and online.
And that means IMF will be used throughout the industry. It will truly be a new way of doing
things.
Why do we need a Global Exchange Format?
We are part of a fast growing and increasingly global business. The sales and exchange of
programmes is set to accelerate over the coming years.
It is estimated that:
• Worldwide OTT (over the top) television & video revenues will reach £37 billion in 2020.
• Pay TV revenues and OTT revenues combined will reach £205 billion by 2020.
• China & India together will account for half the global pay television subscribers by 2022.
• SVOD (subscription video on demand) will generate half of the OTT revenues by 2022. The
remainder will be made up of ad supported video on demand, TV on demand and download
to own purchases.
What problems will IMF solve?
Problem1:
Creating multiple copies of a TV programme has consequences. These include duplicated

processes and Quality Control (QC), and the need for more storage and additional asset
management capabilities.
Problem 2:
In a flexible production market, as production and technology teams move onto other
programmes, information and knowledge associated with the original piece of content is difficult
to retain.
Problem 3:
As content passes through each stage of localization (with associated compliance processes and
format changes), and moves from system to system, the quality of the original asset is impacted.
124 TP-00360-02
Appendix 1 - IMF
Localization Process
The localization process is particularly complex.
It varies from organization to organization but, for a typical programme, this is the order of
events:
1) Ingest the master.

2) Localise a version for a territory or region.
3) Complete the audio dubbing and subtitling.
4) Create a self-contained programme file for the region.
But it doesn’t end there. As assets continue to be exploited overtime, there may be new
customers and territories with further requirements for additional languages, titles and credits.
Some assets will also require maintenance further down the line. This could include changes to
music for licensing or rights reasons, or changes made due to cultural sensitivities.
To solve these issues, we need a solution that:
• Reduces duplication, which means less storage and a lighter storage footprint overall.
• Preserves Asset Knowledge, which speeds up the localization process and increases speed to
market.
• Maintains Mastering Quality, which ensures customers receive the best quality content.
The Solution
If we can use a standard mastering approach throughout the localization process, which
manages the way we create and store versions, it’s possible to avoid duplication, preserve asset
information and maintain the highest quality.
We are proposing the use of a global exchange format that will:
• Create operational workflow efficiencies in the content supply chain. This standardises the
production and transformation of programme assets internationally. It also enables potential
automation of processes.
• Handle complicated multi-platform multi-versioning for delivery to a range of different
devices.
• Standardize distribution formats.
• Make international sales and distribution more efficient.
Our proposed solution is IMF.
What is IMF? The Shipping Container
In order to explain IMF in real world terms, there is a perfect metaphor in the shipping container.
Just 70 years ago, the movement, sale and exchange of goods was based on hundreds of
labourers lifting parcels, barrels, boxes and crates in and out of boats.
It was normal for a ship to spend more time in port being loaded and unloaded than at sea. Goods
were also highly prone to accident, loss and theft.
TP-00360-02 125
Appendices
The shipping industry faced a similar challenge to the media industry today. It needed to move
away from hand-cranked delivery systems, full of error, loss and unpredictability.
The solution was the shipping container. Shipping containers enabled the standardised
movement of goods. They all had the same dimensions, and enabled the creation of new,
standardised technical tools. A container ship could now be off loaded in a matter of hours.
Containerization also enabled interoperability in onward transport methods (with trucks and
trains designed to carry standardised containers).
IMF is the shipping container for media.
IMF (Interoperable Master Format) is a container of different content elements (audio, video,
language, subtitles etc) that can be re-packaged for different outputs.
A Container of Components
IMF Explained
• Internationally recognized, SMPTE standard.

• Maintains programmes in their highest quality.
• Business-to-business Master format.
• Already used to exchange high value content.
• Now also being adapted for use in TV and online.
• Easy to create.
IMF is an internationally recognized SMPTE standard that can be used for the interchange of
file-based, multi-version, finished audio-visual content.
Sky and Netflix already mandate IMF as a delivery format.
126 TP-00360-02
Appendix 1 - IMF
We are modifying it so that it also works for broadcast and online.
We are working with manufacturers of tools to ensure that it’s easy to create an IMF package.
Importantly, we are not trying to re-invent the wheel.
IMF is based on the tools and technologies that the feature film industry has successfully used to
create and distribute international versions of their films for at least five years.
We are making content exchange easier by modifying this existing standard so that it works for
TV and online.
What problems does IMF solve?
The benefits of IMF relate to the efficiencies it delivers to the content supply chain. IMF makes it
easier for broadcast and online content owners, producers and distributors to exchange high
value media around the world.
To illustrate how IMF does this, let’s look at three key problems in the versioning process, and how
IMF solves them.
We’ll begin with the way that localized versions are currently created and modified over time.
Problem 1: Multiple Copies
The example above shows international versioning, but it could equally apply to a single region
where multiple copies are needed.
TP-00360-02 127
Appendices
• The process starts with a single master.

• One copy is made for each region.
• From the region specific version, further compliance versions are made – these may be
generated by different teams and can therefore be very hard to match back to the regional
version.
• From the compliance versions, subtitling and audio dubbing is added.
• These different versions may not be stored together. It becomes difficult to track assets and
versions because there is no relationship between them.
• Finally, the localized copies are distributed to multiple customers, and this generates lots of
deliverables.
What does this mean for our business?
• We are paying to store a huge number of versions unnecessarily.

• Lots of complex asset management, often between incompatible systems.
• Processes are often duplicated, due to the large number of versions.
Solution 1: IMF makes visioning lighter
Versions contain mostly the same components as the programme master. They typically have a
few small additions. In the example below, a French master has been created by adding a local
language track to the UK master. A version complied for the Middle East has also been made by
making a few small changes.
The darker green area demonstrates the content that is the same across all versions. The lighter
boxes demonstrate where localized content is added or subtracted from the programme master
to create a new version.
As you can see, all versions are nearly identical with the exception of very small changes.
128 TP-00360-02
Appendix 1 - IMF
IMF allows us to only save the changes to each version; it references the majority of content from
the programme master. This reduces the need to store multiple full length copies of the finished
programme in different languages or compliance edits.
At the end of the IMF mastering process, we have replacement scenes, new localizations and the
necessary controls to know where to put them.
By storing only this information at master quality, we save a huge amount of space compared to
storing high quality versions of everything.
It’s also now much easier to rebuild a programme should a change become necessary.
This significantly reduces storage costs and removes complexity from asset management and
processing.
TP-00360-02 129
Appendices
Problem 2: Loss of Knowledge over time
The second problem is the loss of knowledge that occurs throughout the asset life cycle.
Over time, more and more versions of a programme are created as it sells internationally. The
number of assets continues to increase, but knowledge associated with the original piece of
content is difficult to retain.
One of the big problems of the media industry today is that there is no way systematically to store
the knowledge associated with a master asset.
To put it more precisely, knowledge is not so much lost as scattered.
Once initial work has been completed, it is difficult to gather knowledge about a programme,
since production teams tend quickly to disperse onto other projects.
The need to try and gather information about an original asset once the production team has
dispersed can slow down speed to market and programme sales fulfilment.
130 TP-00360-02
Appendix 1 - IMF
Solution 2: IMF is faster
IMF solves the problems caused by loss of knowledge because it has the concept of systematic
preservation of knowledge, passed on from the master edit all the way down to the various
versions.
IMF allows the creation of versions linked to the original master version.
A description of any changes, and instructions for where to put them, are held in a control file
called a CPL (Composition PlayList). This enables us to create new versions faster, which increases
speed to market.
TP-00360-02 131
Appendices
132 TP-00360-02
Appendix 1 - IMF
Problem 3: Loss of Quality
As content is transformed through each stage of the localizations process, the quality of the asset
can be affected.
Today a programme asset might change frame rate multiple times before its final delivery. There
are also likely to be changes in codec, bit rates, definition and colour space for different versions,
on different platforms and devices, in different territories. Together, all these changes will begin
to degrade the overall quality of the programme.
TP-00360-02 133
Appendices
134 TP-00360-02
Appendix 1 - IMF
Solution 3: IMF maintains quality
IMF is designed to use mastering quality codecs. This keeps all video, audio, subtitling and
metadata in the highest quality throughout the localization process.
The master is maintained at a single frame rate, in a single high quality codec, and at a single
resolution. This safeguards the quality of programme sales fulfilment.
TP-00360-02 135
Appendices
136 TP-00360-02
Appendix 1 - IMF
Additional benefits from IMF
In the process of solving the three key problems outlined above, IMF brings some further
benefits:
• A reduction in storage space and costs because there is no longer a requirement to store
numerous localized files
• Content becomes easier to manage because there is now only one master asset for each
programme
• The systematic preservation of knowledge means it is now easier to identify the
consequences of any changes made to the media
• Content reversioning becomes easier and cheaper.
TP-00360-02 137
Appendices
Conclusion: The business benefits of IMF
Because IMF allows different iterations of a programme or series to be created from one core
editorial asset, the distribution of multiple versions is greatly simplified.
IMF makes it possible to improve efficiency by:
• Eliminating unnecessary creation of multiple versions, and by reducing QC and archive

storage requirements
• Automating the content supply chain.
• Becoming, over time, the global exchange format for the sales and acquisition of high quality
content.
• Allowing programme masters to be held at the highest possible quality, enabling future sales
fulfilment at UHD resolution, or higher.
138 TP-00360-02
Appendix 1 - IMF
Illustration 1: Storage efficiencies
As can be seen from the table and graph below, multiple versions of content create the need for
more and more storage.
But by using IMF, the increase in storage requirements is dramatically less, because only the
original version, together with small changes, need to be retained.
For example, 10 versions of a TV programme stored as full length files, rather than IMF, would
require 1TB of storage.
With the use of IMF, the storage requirement would be just 139GB.
These savings become even greater when productions migrate to UHD. As the table below
shows, 10 versions stored in UHD requires 3.3 TB – but only 370GB if IMF is used.
TP-00360-02 139
Appendices
Illustration 2: Performance efficiencies
Media businesses incur significant bandwidth and compute costs when moving and transcoding
large video files.
As the table below demonstrates, it would take 25 hours to transfer 10 localized versions of a one
hour programme without IMF. But with IMF that time is reduced to less than 4 hours.
When it comes to transcoding, it would take more than 300 minutes to transcode those same 10
localised versions. But with the benefit of IMF, the times falls to less than 90 minutes.
As these figures make clear, the use of IMF reduces delivery timelines and increases the efficiency
of sales fulfilment. As speed to market becomes of greater and greater importance in the world
of consumer-led media, such efficiency becomes essential.
Once aggregated to thousands and thousands of programme assets, such performance

efficiencies also represent major cost savings, since more activity can be achieved by fewer
people in less time.
140 TP-00360-02
Appendix 1 - IMF
IMF for Broadcast & Online: The path to adoption
The extension of IMF to the wider broadcast and online community offers significant benefits to
the industry.
The work has been actively supported by numerous companies and organizations, listed below.
This enabled the DPP to take the lead in defining user requirements. Next came the creation, in
partnership with SMPTE, of a draft specification.
The published specification for IMF for Broadcast and Online is due to appear in summer 2018.
Meanwhile, the DPP has already begun work with broadcasters, industry organizations,
production companies, distributors and suppliers to drive adoption of IMF for Broadcast & Online.
This is the work that will ensure that consistent workflows are implemented across global
organizations, and that there is interoperability between different parts of the content supply
chain.
TP-00360-02 141
Appendices
Preparing your business for IMF adoption
The DPP will help unify the industry’s approach to IMF. But the exact path to adoption will
inevitably vary from company to company.
IMF offers enormous opportunity. But it is also a major change, and every company will need to
consider the impact on its business.
Here are the key next steps in preparing for IMF:
• Use the analysis in this document to help build an understanding of the financial and
operational benefits IMF will deliver to your organizations, together with the timescales for
achieving those benefits.
• Conduct a full risk vs benefits analysis, with an understanding of how individual processes
will be affected by the move to IMF.
• Decide on your implementation approach. Select the appropriate technologies, tools and
partners.
• Define your change management strategy. This will ensure that the migration to IMF is a
success with your staff, partners and customers.
The DPP will co-ordinate an IMF implementation group for its Member companies. Contact the
DPP if you would like further information: [email protected]
Conclusion
The media industry is now global, and the demand for content is greater than ever. Almost every
content maker and provider now needs to create versions of its content for a wide range of
territories, cultures and users.
This scale and diversity of demand represents enormous business opportunity. It enables delivery
of content in a speedy, agile and cost effective manner.
IMF offers a new approach to mastering and versioning that equips media businesses for the task
at hand.
The transformation offered by the widespread adoption of IMF is exciting; but it is also
considerable. The change process will happen more effectively and smoothly if the industry
works together. The DPP is committed to promoting such collaboration. We hope you will work
with us.
142 TP-00360-02
Appendix 2- PSE (Photo Sensitive Epilepsy)
Appendix 2- PSE (Photo Sensitive Epilepsy)
Ofcom Guidance Note on Flashing Images and Regular Patterns in Television
Flickering or intermittent images and certain types of regular pattern can cause problems for
some viewers who have photosensitive epilepsy. These guidelines have been drawn up following
consultation with leading medical opinion in this area with the aim of reducing the risk of
exposure to potentially harmful stimuli.
Television is by nature a flickering medium. In Europe each transmitted picture is refreshed 50

times each second and interlaced scanning generates flicker 25 times each second. It is therefore
impossible to eliminate the risk of television causing convulsions in viewers with photosensitive
epilepsy. To reduce risk the following guidelines on visual content should be applied when
flashing or regular patterns are clearly discernible in normal domestic viewing conditions. It
should be noted that the level of any cumulative risk arising from successive sequences of
‘potentially harmful’ flashes over a prolonged period is unknown. If, as medical opinion suggests,
the risk of seizures increases with the duration of flashing, broadcasters should note that it is
possible that a sequence of flashing images lasting more than 5 seconds might constitute a risk
even when it complies with the guidelines below.
A potentially harmful flash occurs when there is a pair of opposing changes in luminance (i.e.,
an increase in luminance followed by a decrease, or a decrease followed by an increase) of 20
candelas per square metre (cd.m-2) or more (see notes 1 and 2). This applies only when the screen
luminance of the darker image is below 160 cd.m-2. Irrespective of luminance, a transition to or
from a saturated red is also potentially harmful.
Isolated single, double, or triple flashes are acceptable, but a sequence of flashes is not permitted
when both the following occur:
• The combined area of flashes occurring concurrently occupies more than one quarter of the
displayed (see note 3) screen area; and
• There are more than three flashes within any one-second period. For clarification, successive
flashes for which the leading edges are separated by 9 frames or more are acceptable,
irrespective of their brightness or screen area.
Rapidly changing image sequences (e.g. fast cuts) are provocative if they result in areas of the
screen that flash, in which case the same constraints apply as for flashes.
A potentially harmful regular pattern contains clearly discernible stripes when there are more
than five light-dark pairs of stripes in any orientation. The stripes may be parallel or radial, curved
or straight, and may be formed by rows of repetitive elements such as polka dots. If the stripes
change direction, oscillate, flash or reverse in contrast they are more likely to be harmful than if
they are stationary. If the patterns obviously flow smoothly across, into, or out of the screen in one
direction they are exempt from restriction.
Potentially harmful patterns are not permitted when either of the following two conditions apply:
TP-00360-02 143
Appendices
• The stripes are stationary and the pattern occupies more than 40% of the displayed screen
area; or
• The stripes change direction, oscillate, flash, or reverse in contrast and the pattern occupies
more than twenty five per cent of screen area; and in addition to either of the above two
conditions applying, when
• the screen luminance of the darker bars in the pattern is below 160 cd.m-2 and differs from
the lighter bars by 20 cd.m-2 or more (see notes 1 and 2).
Notes:
Video waveform luminance is not a direct measure of display screen brightness. Not all domestic
display devices have the same gamma characteristic, but a display with a gamma of 2.2 may be
assumed for the purpose of determining electrical measurements made to check compliance
with these guidelines (see appendix I).
For the purpose of measurements made to check compliance with these guidelines, pictures are
assumed to be displayed in accordance with the ‘home viewing environment’ described in
Recommendation ITU-R BT.500 in which peak white corresponds to a screen illumination of 200
cd.m-2.
It may be assumed that overscan on modern domestic television receiver displays will normally
be in the range 3.5% ± 1% of the overall picture width or height (as indicated in EBU Technical
recommendation R95-2000).
First issued as an ITC Guidance Note November 1994, first revised September 1999, revised and
re-issued July 2001. Re-issued by Ofcom (date tbc).
144 TP-00360-02
Appendix 3- Supported Formats
Appendix 3- Supported Formats

The following tables list the formats that are supported by QScan.
TYPE
DV AVCHD P2 DVCPRO 25
VC-1 AVCHD2 P2 DVCPRO 50
DV AVI DVCAM P2 DVCPRO 100 720P
DVD BLU-RAY P2 DVCPRO 720P NATIVE
HEVC XDCAM EX P2 DVCPRO HD 100 1080i
XAVC JPEG2000 PANASONIC P2 LongG 6
MPEG-2 XDCAM HD PANASONIC P2 LongG 12
VC-3 DNxHD XDCAM IMX PANASONIC P2 LongG 25
AVC-INTRA 50 AVC-INTRA 100 PANASONIC P2 LongG 50
ADOBE FLASH RP 2027 AVC-INTRA DPX
CONTAINER
mp4 MXF OP1A ASF File Format
WAV DV-AVI stream MXF GENERIC 1B
Mpeg TS MXF GENERIC 1A mp4 estandar MDAT
MPEG PS DVC PRO HD 100 MXF P2 DVCPRO Atom
Quicktime MXF XDCAM DV OP1A MXF P2 AVCI Atom
XDCAM MDAT XDCAM HD OP1A XDCAM IMX OP1A
VIDEO CODEC
DV VC-3 MPEG1
H.264 WMV9 MPEG4
H.261 VC1-PRO MJPEG
HEVC JPEG200 MPEG2
H.263 DVCPRO HD 100 DNxHD
TP-00360-02 145
Appendices
VIDEO CODEC
Apple ProRes
AUDIO CODEC
AAC WMA MPEG 1 LII
LPCM PCM MPEG audio
DV AUDIO Dolby Digital
146 TP-00360-02
Appendix 4 - Template Parameters

This appendix describes all of the parameters that you can use with templates in QScan.
Format Checks
Parameter Range Description Possible Values
Container Format: is/is not the format that is used to wrap Video/Audio see DropDown Menu
files
File Size: >,<,= the number of Bytes per File Bytes
Duration: >,<,= the length of the File in seconds seconds
Has Video: detect/not boolean value that checks if the analyzed File
detected has (or has not) Video inside
Number of Audio >,<,= number of encoded audio streams in the Integer

Streams Media File
Format Version is/is not MXF version specification 1.1, 1.2, 1.3
Format Profile is/is not MXF profile specification see DropDown Menu
Start TC is/is not Start Timecode encoded in the Media HH:MM:SS:FF

Container (e.g. MXF)
Timecode Present detect/not checks if a Timecode is available in the

detected Container
Commercial Name is/is not Naming of the File Format see DropDown Menu
Closed Caption is/is not specifies if there is a EIA-608 or EIA-709 see DropDown Menu
Closed Caption stream encoded
AS-11 is/is not specifies if the Media File is compliant to the see DropDown Menu
AS-11 standard (or to a subset of AS-11)
Package Format is/is not specifies if the Media Files belong to a certain see DropDown Menu
Package (e.g. IMF, DPX)
Pixel Format is/is not specifies the encoded Pixel/Chroma Format see DropDown Menu
(such as yuv422, yuv420,…)
Video Codec is/is not specifies the Codec used for encoding the see DropDown Menu
Video
Video Bit Rate >,<,=,… specifies the bit rate (Bits/sec) used by the Integer (Bit/sec)
the Video Encoder
TP-00360-02 147
Appendices
Frame Rate is/is not specifies the bit rate (Frames/sec) used by predefined or user
the Video Encoder defined values
Resolution >,<,=,… encoded picture width and picture height in Integer (Num of Pixel)
Pixel
Coded Aspect Ratio is/is not specifies the relation between picture width predefined or user
and height of the encoded picture defined values
Display Aspect Ratio is/is not specifies the relation between picture width predefined or user
and height of the display picture defined values
Chroma Subsampling is/is not Luma/Chroma Format used for encoding the see DropDown Menu
video
Video Packet ID is/is not the ID of the Video stream used to identify Integer
the stream in the media file. (See PID in TS
Files)
Video Bit Depth is/is not specifies the number of Bits per Pixel see DropDown Menu
GOP Structure is/is not GOP layout defined by M (distance of Intra

Frames) and N (Distance between P Frames)
GOP is open / is specifies if a GOP is open (has references to

closed neighbouring GOPs) or closed (no references
to other GOPs)
Format Profile and level is/is not specifies Profile and Level of the Video see DropDown Menu
Codec. Possible values depend on the used
codec
Video Bit Rate Mode is/is not specifies if the Video Codec used constant or boolean
variable Bitrate
Color Space is/is not specifies the Color Space used by the see DropDown Menu
encoder (e.g. RGB, YUV, XYZ,…)
Scan Type is/is not specifies if Video was encoded in Interlaced see DropDown Menu
or Progressive mode
BitsPixelFrame >,<,=,… specifies the average number of Bits used to float val
encode 1 Pixel => BitPixelFrame = Bits /
(Pixel * Frames)
Active Format is/is not specifies if the Active Format Description boolean
Description (AFD) Packet is encoded in the stream
Field Order (Scan Type) is/is not specifies if Frame the scan order in the Video
(in case of Interlace) is Top or Bottom Field
first
148 TP-00360-02
Color Primaries is/is not specifies the standards/formulas/parameter see DropDown Menu
used to transfer the encoded Pixel values to
RGB
Transfer Characteristics is/is not specifies the standards/formulas/parameter

RGB
Matrix Coefficients is/is not specifies the standards/formulas/parameter

RGB
Audio Codec is/is not specifies the Codec used for encoding the see DropDown Menu
Audio
Audio Bit Rate >,<,=,… specifies the bit rate (Bits/sec) used by the Integer (Bit/sec)
the Audio Encoder
Number Of Channels >,<,=,… specifies the number of encoded Audio Integer

Channels
Sample Rate >,<,=,… specifies the Audio Sample Rate (Samples Integer
per Second - 48.000 = 48 kHz)
Audio Packet ID is/is not the ID of the Audio stream used to identify
the stream in the media file. (See PID in TS
Files)
Audio Bit Depth >,<,=,… specifies the number of Bits used to encode Integer
an Audio Sample
Audio Bitrate Mode is/is not specifies if the Bitrate mode used by the see DropDown Menu
Audio Encoder. Can be constant or variable
Endianness is/is not specifies the byte order that was used to see DropDown Menu
store PCM Audio Data in the stream
Sign is/is not specifies if the PCM Audio Data in the stream see DropDown Menu
was encoded as signed or unsigned values
Audio Mapping is/is not specifies the Audio channel layout for all see DropDown Menu
Detection channels (L, R, C, …)
Audio Wrapping is/is not detects if a certain wrapping Format was see DropDown Menu
used for Audio
TP-00360-02 149
Appendices
IMF Checks
The following parameters are IMF specific:
Number of files
Checks that the number of IMF specific XML files (CPL, PKL, AssetMap, Volume Index, OPL)
correspond to what has been configured.
File exists
Checks whether the IMF specific XML files exists or not.
Essence linked
Checks that all essence is referenced to in the PKL and CPL.
Application identification
Checks the application identification parameter and identifies whether the IMF package complies
to a specific application specification (application#2 and application#2 extended).
150 TP-00360-02
Frame Statistics
Picture Coding Type
Parameter Picture Coding Type
Range I/P/B/S/SI/SP/BI
Usage Detection of types of

coding frames
Is Keyframe
Parameter Is Keyframe
Range Detected/not detected
Usage Detection of Key Frames
• Analyzes video and detects any Key Frames (I frames).
Bytes Per Frame
Parameter Bytes Per Frame
Range 0... bytes
Usage Detection of Frame size
TP-00360-02 151
Appendices
Stream Syntax Errors
Parameter Stream Syntax Errors
Usage Detection of Errors in

encoded streams/files
• This parameter detects an error in an encoded stream which results in decoding problems.
• A bit error or packet loss could cause these kinds of errors which often result in visible
distortion of the Video/Audio content.
• If no syntax errors appear, the stream is standard confirm and can be decoded without any
problems.
• Limitation: Depending on the kind of error, it could be that the error is not visible at all.
152 TP-00360-02
Baseband/Waveform
Highest Luminance Level

Parameter Lowest Luminance Level Highest Chroma Level
Range -7...110% 0...115%

-50...750mV 0...400mV
0...255 8-bit scale 0...128 8-bit scale
Usage Detection of highest/lowest Detection of highest

Luminance levels Chrominance levels
Lowest Luminance Level

Range -7...110% 0...115%

-50...750mV 0...400mV

TP-00360-02 153
Appendices
Brightness
Parameter Brightness
Range 0...100
if avg level < 0% ? 0
if avg level < 100% ? 100
Usage Analysis of average

Brightness of the video
frame
• This parameter returns the average

Video Level within a frame.
• A value of 0 means that the average Video Level within a frame is ≤ 0% (average Pixel Level
≤16 in a 8 Bit System)
• A value of 100 means that the average Video Level within a frame is = 100% (average Pixel
Level =235 in a 8 Bit System).
• Limitation: the algorithm does not detect any errors, it provides statistical information. To
detect “out of range” Video Levels, use the Max/Min Video Level parameter.
Contrast
Parameter Contrast
Range 0: lowest possible contrast

100: highest possible
contrast
Usage Analysis of max. pixel

contrast within a frame
• This parameter gives the maximum pixel

contrast in a frame
• The highest and lowest pixel value is used to calculate this parameter.
– 0 means that the highest and lowest pixels have the same value.
– 100 means that the highest and lowest pixels have the maximum difference (255/1024
in 8-bit/10-bit Video).
154 TP-00360-02
• Limitation: the algorithm does not detect any errors, it provides statistical information. To
detect “out of range” video levels, use the Max/Min Video Level parameter.
Luma Footroom Violations
Parameter Luma Footroom Violations
Range 0...100
0 : no Luma Footroom
Violations
100: max Luma Footroom
Violations
Usage Detection of pixels below

0% video level
• This parameter calculates the percent of

the Pixels that have a Video Level below 0%.
• The Video Level of every pixel is analyzed and used to calculate the this Value.
• A value of 10% means that 10% of the Pixels have a Video Level below 0%.
Luma Headroom Violations
Luma Headroom
Parameter Violations
Range 0...100
0 : no Headroom Violation
100: max Headroom
Violation
Usage Detection of pixels above

100% video level
• This parameter calculates the percent of the pixels that have a Video Level above 100%.
• The Video Level of every pixel is analyzed and used to calculate the this value.
• A value of 10% means that 10% of the pixels have a Video Level above 100%.
TP-00360-02 155
Appendices
Chroma Headroom Violations
Chrominance Headroom
Parameter Violation
Range 0...100
0: no Headroom Violation
100: max Headroom
Violation
Usage Detection of pixels

violating the Chroma
Headroom
Highest Chroma Level

Range -7...110% 0...115%

-50...750mV 0...400mV

156 TP-00360-02
Gamut Errors
Parameter Gamut Errors
0...100
Range 0 : no Gamut Errors
100: max Gamut Errors
Usage Detection of pixels with

Gamut Error
• This parameter analyzes the picture to

detect if any YUV combination is producing illegal colors when converted to RGB domain.
• According to the EBU recommendation R103-2000, a signal that has RGB components must
be in the range of -5...105%, and the luminance signal must be in the range of -1...103%
• QScan is analyzing/reporting the percentage of "illegal" pixels appearing in a picture.
TP-00360-02 157
Appendices
Video Content
Blackness
Black Frame Detection.
Parameter Blackness
Range 0...100
Usage Detection of Black Frames
• This parameter returns the Average Pixel

Brightness, which is calculated by dividing
the square sum of every pixel level in a
frame by the pixel count.
• A lookup table classifies the average brightness per pixel into a black level from 0 to 100.
• This method detects a Frame as a Black Frame even if there are some white (or non-black)
Pixels in the Frame (which is often the case in a noisy black frame).
• A Black Level of 100 is only set when all pixels have a Pixel Value of 0.
• Limitation: this could give some false alarms on black frames - for example black frames with
some white text.
Freeze
Freeze Frame Detection
Parameter Freeze
Range 0...100
Usage Detection of Freeze

Frame
158 TP-00360-02
• This parameter estimates a Freeze Level between two successive frames.

• The calculation of the Freeze Level is based on per pixel variations of those frames.
• A Freeze Level of 100 means that EVERY pixel is frozen (identical to the previous frame).
• An algorithm based on the lookup tables is used to provide the best possible Freeze Level for
the appropriate variations between two frames.
• This method allows QScan to detect a frame as a Freeze Level even if there are some “moving”
pixels in the frame (which is often the case in a noisy freeze frame).
Blockiness
Blocking detection
Parameter Blockiness
Range 0...100
Usage Detection of Blocking

Artefacts
• This parameter defects Blocking Artefacts by analyzing

the 8x8 block pattern in the picture.
• Several methods are used to detect if a block border is
showing blocking artefacts.
• The number of Blocks with detected Blocking Artefacts are counted inside a frame.
• A lookup table is used to provide a best possible blocking level (0...100) for the corresponding
number of distorted blocks
• That means, there is no formula used to score the blocking level. The lookup table is trying to
reflect the user experience as well as possible.
• Limitation: The blocking is only detecting the “typical” overall MPEG-2 Blocking coming from
low bit rate encoding as shown in the frame example.
Blurriness
Blurring Detection
Parameter Blackness
Range 0...100
Usage Detection of Blurring

Artefacts
TP-00360-02 159
Appendices
• This parameter detects Blurring Artefacts by analyzing the 8x8 Block Pattern in the picture.
• Several methods are used to detect if a Block Border is showing blurring artefacts coming
from the AVC / H.264 filtering process.
• The number of Blocks with detected Blurring Artefacts are counted.
• A lookup table is used to provide a blurring level (0...100) for the corresponding number of
distorted blocks.
• There is no formula used to score the Blurring Level. The lookup table is trying to reflect the
user experience as good as possible.
• Limitation: the blurring algorithm can give some false alarms where there are some frames
that are intentionally blurred.
Interlacing Artifacts
Interlacing Artifacts
Parameter Interlacing Artifacts
Range 0...100
0: no interlacing
100: maximum interlacing
Usage Detection of interlacing /

combing artifacts
• This parameter detects Interlacing (combing)

Artifacts.
• The picture is analyzed line by line to find these kinds of artifacts.
• The parameter value depends on the “intensity” of the interlacing artifacts as well as on the
number of interlacing regions found.
• For example, in a non-moving sequence, the visible interlacing is much lower than in a fast
moving sequence.
• The relation between number and “intensity” of visible interlacing is not linear. A lookup
table is used to provide a best possible value.
160 TP-00360-02
Field Order
Parameter Field Order
Range -50: Bottom Field first

0: Progressive Sequence
50: Top Field First
Usage Detection of Field Order
• This parameter detects the "real" Field Order within a Sequence.

• The algorithm is analyzing the Frame Movement within a Sequence and is detecting which
Field order is the correct one.
• The resulting value (-50...+50) depends on the detected probability of the detected
Top/Bottom Field first order.
• By comparing the measured field order with the expected field order, the user can detect
problems related to the wrong field order.
• For example, in a non-moving sequence it is difficult to detect the correct field order.
Therefore the resulting values will be smaller than in a fast moving sequence with clear
movement.
• Limitation: This measurement can lead to some false positives, depending on the picture
content. The result should be handled with care, since it is only giving the user a hint of which
field order the sequence most probably has.
TP-00360-02 161
Appendices
Temporal Complexity
Parameter Temporal Complexity
Range 0...100
0: No Temporal Complexity
100: High Temporal Complexity
Usage Detection of sequence changes
• This parameter measures the level of change between two successive frames.
• High complexity means that there are high changes form the previous frame to the current
frame (for example, a change form black to white – or from white to black – would result in
high temporal complexity).
• Low complexity means that there were low changes from the previous frame to the current
frame (for example, a Freeze Frame will have a temporal complexity of 0).
• This parameter can help to detect scene cuts (each scene cut normally results in a high
temporal complexity).
Field Dominance Error
Parameter Field Dominance Errors
0...100
Range 0: no error
100: error
Usage Detection of wrong field

dominance
• Field dominance refers to the choice of which field of an interlaced video signal is chosen as
the point where the video edit occurs.
• In a sequence of Top and Bottom fields T B T B T B T B, there are two possible choices:
– T B T B |edit point| T B T B
– B T B T |edit point| B T B T
162 TP-00360-02
• Wrong field dominance results in “Scene Cut Errors” as shown in the screen shot above.
Test Pattern
Parameter Test Pattern Detection
Range 0...100
0: no test pattern
75: 75% video level test
pattern
100: 100% video level test
pattern
Usage Detection of a test pattern
• This parameter detects standard color bars at 75% and 100% video level.
Constant Color Frame

Parameter Detection
Range 0...100
Percentage of constant
color pixels
Usage Detection of constant

color frames
TP-00360-02 163
Appendices
• This parameter detects the percentage of the pixels in an image that present constant color.
• A completely green frame will, for example, cause a score of 100, whereas smaller green
portions in the frame will cause lower values.
• The relation between constant color parts and resulting score is not linear. A lookup table is
used to provide the best possible value.
Pillar Box
Pillar Box
Parameter Pillar Box
Range 0...50%
Usage This parameter analyzes

the size of the pillar box
(black pixel columns at left
and right of the picture) as
a percentage of the total
picture width. If the size of
left and right borders
differ, the smaller value is
used.
Letter Box
Parameter Letter Box
Range 0...50%
Usage This parameter analyses

the size of the Letter Box
(black lines at top and
bottom) as percentage of
the total picture height. If
size of Top and Bottom
differs, the smaller value is
used.
For example, when your picture height is 1000 (pixel) and you set an alarm for "Letter Box greater
than 10", QScan will raise an alarm when the Letter Box is greater than 100 pixels. 100 pixel = 10%
of the picture height.
164 TP-00360-02
Video Quality
DigiBeta Error
Digital Betacam Error
Parameter DigiBeta Error
Range 0...100
Usage Detection of Channel

Condition Error from Sony
Tape Machine (Digital
Betacam)
• This parameter detects artefacts coming

from Sony Digital Betacam Tape Machines.
• These Artefacts are also known as "Channel Condition Errors" or "Tape Hit Errors" or "Head
Clog Errors“.
• The picture is analyzed pixel by pixel to find the typical artefacts caused by this kind of error.
• The visibility of a single Dropout detected in a Frame influences the dropout score. Therefore,
the score for a single dropout depends on the "intensity/visibility" the algorithm is detecting.
For example: there can be single dropout scored with 5 as well as single dropouts scored with
15. This would depend on the "intensity" of the detected dropout.
• The number of Dropouts (Blocks) detected in a Frame influences the total score. The more
Blocks detected, the higher the value.
• The exact calculation of the Dropouts is not linear. A lookup table is used to provide the best
possible values for a given Dropout pattern per Frame.
• Limitation: the algorithm can only detect artefacts from this kind of tape machine. This
parameter can sometimes cause false alarms by detecting "normal" Picture content as
Dropouts.
Digital Dropouts
Parameter Digital Dropouts
Range 0...100
Usage Detection of dropouts
TP-00360-02 165
Appendices
• This parameter detects Digital Dropouts in the decoded picture. One possible source are
channel condition errors coming from Panasonic DVC PRO tape machines. Furthermore there
are other errors that can cause these kind of dropouts (e.g. bit errors in Files, encoding errors).
• The picture is analyzed Pixel by Pixel to find these typical artifacts.
• To find a single dropout, the algorithm is checking for different Indicators. The more
indicators the algorithm detects, the higher the score for the Dropout.
• For example: detecting a single indicator could cause a value of 5, detecting a second one
could raise the value to 10.
• The number of Dropouts (Blocks) detected in a Frame also influences the total score. The
more blocks that are detected, the higher the dropout value will be.
• The exact calculation of the Dropouts is not linear; there is no single formula used. A lookup
table is used to provide the final Parameter Values.
• Limitation: the algorithm can sometimes cause false alarms by detecting "normal" picture
content as Dropouts.
166 TP-00360-02
Luminance Line Errors
Single Luminance Line Error
Parameter Luminance Line Errors
Range 0...100
0: no Line Errors
100: long Line Error
Usage Detection of single

Luminance Line Errors
• This parameter detects single line errors in

a frame.
• The picture is analyzed line by line to find these kind of artefacts.
• The resulting value for this parameter depends on the length of a continuous single line.
• Note: The relation between the length of a line and the value is not linear. A lookup table is
used to scale the parameter to the range from 0...100 and to express the best possible relation
between visible distortion and the resulting value.
• Limitation: The algorithm can detect only SINGLE line errors.
Chrominance Line Errors
Parameter Chrominance Line Errors
Parameter Chrominance Line Errors
Range 0...100
0: no line errors
100: long line error

chrominance line errors.
TP-00360-02 167
Appendices
• This parameter detects single line errors in the chrominance channel of a frame.
• The picture is analyzed line by line to find these kinds of artefacts.
• The value depends on the line length.
• Limitation: the algorithm can detect only SINGLE line errors.
Picture Quality Score
Parameter Picture Quality Score
Range 0...100
0: bad encoding
50: fair encoding
100: excellent encoding
Usage Detection of video quality
• This parameter detects the encoded

Picture Quality.
• This parameter is a single ended (non-reference) based method, which means there are no
PSNR measurements or comparisons done.
• The proprietary algorithm is based on detecting Encoding Artifacts such as Blocking, Blurring,
Picture Coding Types, Bitrate.
• In order to match as good as possible with the viewer experience, a set of files with different
Quality Levels were scored by different viewers.
• Using this method, the calculated Quality Score scaled is based on human reference.
• Note: the main goal of the Picture Quality Score is to detect bad encoded files rather than
distinguish a good from a perfect encoded file. That is, it could be that a score of 70 looks no
worse than a score of 80. The goal is to detect bad encoded sequences with bad/poor
Encoding Quality.
• Limitation: this measurement is a proprietary algorithm. It can lead to some false positives,
depending on the picture content and codec that is used. The Quality Index was developed
for H.264 + MPEG encoders and therefore could give less valid results for any other codecs.
168 TP-00360-02
Flash/Strobe
Parameter Flash / Strobe / PSE
Range 0...100
0: no Flash / Strobe / PSE
100: high Flash / Strobe /
PSE
Usage Detection of Flash /

Strobe Artifacts
• This parameter detects Flash Lights and Strobe

Errors.
• The video is analyzed Frame by Frame to find these kind of Artefacts.
• The resulting value (0..100) depends on the intensity of the Luminance Change from frame to
frame.
Dead Pixel Detection
Parameter Dead Pixel Detection
0...100
Range 0: no dead pixel
100: dead pixel
Usage Detection of dead pixels
• This parameter detects a “Dead” Pixel within a picture. A Dead Pixel comes from a CCD chip
camera that has a "broken" pixel element. This Pixel element is not receiving any picture
information.
• The parameter value depends on the intensity of the "Dead" Pixel compared to the
neighboring pixels. A single white pixel within a black Frame would cause a higher value than
a single grey pixel within a black frame
• Limitation: this measurement can lead to some false positives, depending on the picture
content. Furthermore, the accuracy of Dead Pixel detection is limited by the codec used to
compress the picture. A high compression is "smearing" the Dead Pixel around neighboring
pixels... which makes it more difficult to be detected.
TP-00360-02 169
Appendices
Photo Sensitive Epilepsy (PSE)
Parameter Photosensitive Epilepsy (PSE)
Usage Detection of video segments that

contain potentially harmful flashes for
viewers with PhotoSensitive
Epilepsy(PSE)
Noise Detection
Parameter Noise Detection
Range 0...100
Usage This parameter analyzes

the noise level inside a
frame.
Blanking
Parameter Blanking
Range from 0 to 200
Usage This parameter analyses

the number of black pixels
at top, bottom, left or
right side of the picture.
170 TP-00360-02
Audio
Level
Parameter Level
Range +3...-100dbFS
Usage Detection of audio levels
• This parameter gives the audio levels in dB full scale.

• Formula: vu = cur_vu_level / MAX_LEVEL audio_level = 20 * log10 (vu).
• The audio frame size can be set by the user (Audio Integration Time).
Mute
Parameter Mute
Usage Detection of audio mute
• Analyzes if an audio channel is muted.

• Mute is signaled when the Audio Level is smaller or equal to -54 dbFS.
No Audio
Parameter No Audio
Usage Detection of audio data
• Analyses if an audio channel contains data.

• This parameter detects if there is NO AUDIO data encoded in an audio frame.
– Detected: There are NO audio samples encoded in the audio frame.

– Not detected: There are audio samples encoded in the audio frame.
TP-00360-02 171
Appendices
Clipping
Parameter Clipping
Usage Detection of Audio

Clipping
• This parameter detects clipping within an audio frame.

• Clipping is detected when the audio level is greater than -1 dBFS.
Sample Clipping
Parameter Sample Clipping

sample clipping
• Analyzes if a single Audio Sample is clipped.

• Whereas “normal” clipping is based on the whole audio frame, sample clipping refers to
clipping of a single sample within an audio frame.
172 TP-00360-02
Frequency
Frequency
Parameter Level
Range 0...20
Usage Measuring the frequency

inside an Audio Frame
• By performing spectrum analysis (FFT), Qscan is able to calculate the "dominating" Frequency
inside an Audio Frame. Displayed as a graph, this parameter gives a good overview of how
the Audio Frequencies evaluate over time.
• A special use case could be to detect Test Tones because these line up tones have a constant
frequency over time. If the threshold is setup in a way to detect constant frequency with a
certain duration, those kind of tones can be detected. A more powerful option is to combine
this parameter in a Macro together with an Audio Level parameter, since typical Test Tones
have a constant Frequency at a certain Audio Level (for example 1 kHz @ -18dBFS).
TP-00360-02 173
Appendices
Audio Phase
Parameter Level
Range -1...1
Usage • This parameter can be used to measure if 2 given channels are Mono (or
not) and if the phase between the channels is inverted (or not). The corre-
lation value can vary from -1 ... 1.
• A value of -1 means that the channels have inverted phase and will cancel
each other when playing back. This is the case for inverted mono chan-
nels.
• A value of +1 means that the channels are in phase. This is the case for
Mono channels.
• Typical stereo channels have values pending between 0…+1 depending
on the audio content. Certain sound effects can have values smaller than
0. Values smaller than 0 does not necessarily mean that the stereo
channel is wrong (out of phase). However, over time a correct stereo
signal should have values larger than 0.
• Stereo channels with inverted phase will result in values smaller than -0,5.
But again, it depends on the audio content.
174 TP-00360-02
Correct Audio Phase is an important criterion for Audio Programs. Mono/stereo channel pairs
should always be in phase. In case of 2 Mono channels, the signals are supposed to be identical.
In case of inverted phase, channels do still have identical but inverted waveforms (e.g. signal
shifted by 180°). The effect of those inverted phase signals will be that they cancel each other out.
Theoretically, the result in front of the speakers will be silence. In case of Stereo, there will be no
complete cancellation, but the effect will be similar, since a stereo pair also has similar
Waveforms. Out of phase stereo channels will also result in bad sound, due to cancellation effects.
TP-00360-02 175
Appendices
Qscan has algorithms to measure the phase correlation of 2 channels.
176 TP-00360-02
Example Settings:
• To detect whether L and R channel are in phase (correct channel pair), the threshold should
be set to “larger than 0".
• To detect whether L and R channel are out of phase and would cancel each other, the
threshold should be set to “smaller than 0".
The duration of the event should also be taken into account because even correct (in phase)
stereo pairs can have certain parts/sections with correlation smaller than 0. That means: not each
and every Audio Frame with a Audio Phase smaller than 0 has an incorrect phasing. Only if larger
parts of the Audio Stream is below 0, it could mean that the phase is inverted.
TP-00360-02 177
Appendices
Loudness
Loudness M, Loudness I,
Parameter Loudness S Loudness LRAA
Range -125...0 LUFS/LKFS 0...125 LUFS
Usage Loudness Analysis
• Analysis of loudness according to ITU BS.1770-2 and BS.1770-3.

• Compliant with EBU R128 and ARIB TR-B32 recommendations.
178 TP-00360-02
Appendix 5- Troubleshooting
System Events List
The main place to look for feedback within QScan is the System Events list. The first event in the
list is the most recent.
To open the System Events list, select the menu Management - System Events:
Events are color coded in the same way as other events in QScan:
• Green - logged events.

• Amber - warning events.
• Red - critical events.
Installation
If you have errors when you are trying to install QScan, try one of the following actions:
• The installer file may be corrupted. Trying downloading and running the .msi file again.
• If the service cannot be started when the installation is complete, check that Visual C++ 2015
is installed. If it is not installed, reinstall it from the following URL:
https://www.microsoft.com/EN-us/download/details.aspx?id=48145
• If you have any other error messages, send the installation log to us. It is located in
C:\Users\<activeuser>\AppData\Local\Temp
• Network issues. Stop the service and run as another user. Node installer instead of “master”
installer:
– Webservice will not run.

– There is one installation folder called (quales node).
TP-00360-02 179
Appendices
– No GUI.
Licensing
You must install a license to create a repository. If you are having trouble with licensing perform
one of the following actions:
• Get the thumbprint or activation file under the Management - License menu item in the
Web UI.
• Send the thumbprint or activation file to our support team.
Configuring Repositories
If you cannot install a repository the first thing to do is check that you have a valid license
installed.
If you are getting an “internal error” message, try doing one of the following:
• Check the license is valid.

• Check the services are running.
• Restart the services.
• Check the path is correct.
• Check the UNC is correct.
File Analysis Does Not Start
If analysis does not start, check the following:
• Check that the services are running.

• Restart the services.
• Check that you have a valid license.
• Check that the node you are trying to run the project on is not blocked.
File Analysis Remains in “generating PDF” status
• Check the processes in task manager.

• Sometimes there are too many php.exe or php-cgi.exe processes running. One process might
be stuck. Stop the services, kill the processes, and restart the services.
Cannot see Macros in Project area
Check that the macros are not blocked.
180 TP-00360-02
Cannot Send Reports by Email
Check that the sender address is in a valid format, corresponding with the Outgoing Mail Server
type, for example, a gmail address with an Outgoing Mail Server of smtp.gmail.com should end it
@gmail.com
TP-00360-02 181
Appendices
182 TP-00360-02
Glossary
Analysis
In analysis it is possible to configure the parameters that will be analyzed, as well as
establish the thresholds that will determine the events that are reported.
The parameters can be enabled/disabled individually. It is important to bear in mind that
the fewer the number of parameters configured, the greater the analysis speed.
QScan has three levels of severity for events: Logging, Warning and Critical. Users of
QScan may choose the severity of the event according to the type of event: audio or
video; and the detection thresholds for each of the analysis parameters chosen.
It is possible to delete or edit a previously created condition, or change the severity of an
event.
Analysis General Settings

The analysis general settings enable:
• Selection of the number of lines to be omitted in the analysis process.

• Choice of the audio integration time (40ms default setting).
• With this option, the user may create a template with the analysis configuration
created in the project for use in the future configuration of other projects.
Analysis Parameters
Analysis parameters determine what the files are analyzed for, for example frame rate or
pixel format. QScan enables the analysis of multiple parameters regarding the
audiovisual content. The analysis of all available parameters will be performed by
default.
Audio Grouping
Audio Grouping is an audio loudness setting that specifies how audio channels are
grouped when files are analyzed. QScan enables the analysis of up to 16 audio channels
that can be grouped into different audio streams.
TP-00360-02 183
Glossary
Email notifications
Reports can be sent by email to the selected recipients so they receive an email
containing the PDF report.
License
You must activate a license before using QScan. After you have installed a license, you
can view details of the license that you acquired when purchasing QScan. You can view
information such as the number of nodes and points with which it is possible to work to
analyze your files.
You can extend the license with more nodes and points if you need to. Contact
support@ editshare.co.uk or your local distributor to extend your license.
Macros
You can use macros to create complex checks starting out with the simple
audio/video/format checks that are provided. You can create new complex checks by
combining logical operators (AND, OR, XOR) to existing checks. For example, "detect
only freeze frames that are not black frames and that do have audio". This is a very
powerful tool allowing any combinations that enhance the AQC capabilities of the
system.
Nodes
A node is a component of a network, connected with other nodes to distribute the work
in different machines. In QScan, nodes are machines other than the "master" machine,
where analysis tasks take place.
• They are connected to the master machine through a LAN/WAN.

• Nodes must have the QScan_node software to run.
• The QScan_node software does not have a Graphical User Interface.
• Nodes can be configured in QScan in the NODE menu option. Default password for
the nodes is: NodePassword
Output Folders
Output folders are where the files that are analyzed will be moved or copied, depending
on the result of the analysis. Output folders can be located on your local machine or on
remote mapped network folders.
184 TP-00360-02
Projects
Projects
A project is a collection of files from one or more repositories that share common
templates, thresholds and parameters. In a project, you can have a defined set of
thresholds, or a selected template. Files are analyzed with the specific parameters and
thresholds that are selected when a project is created or edited. The settings in a project
are run as a job when you perform analysis of files. Information associated with a project
include its ID, Name, Status, Progress, Events, and Errors.
Project Details
Project details contains information such as the nodes that you want to use for the
project, and the users that are authorized to use the project. Project details contain the
following fields:
• Description: project description (optional)File Analysis Priority: select the priority of

the analysis for this project (High, Normal, Low)
• Analysis Speed: enable configuration of the speed of analysis for the project files.
This will indirectly configure the percentage CPU usage during the analysis of this
project (Full, Medium, Slow)
• Concurrent Analysis: determines the maximum number of concurrent analyses
that may be made in the project, in other words, the number of files that the system
may simultaneously analyze in the execution of this project.
• Nodes: shares the analysis workload among various nodes
• Users: authorizes users to work on the project
Project Input
The first step in the creation of the project is to provide it with a name. The file sources
or watch-folders will subsequently be added. Previously created analysis templates may
also be used. On selecting the files, it is also possible to create new folders
TP-00360-02 185
Glossary
Reporting
QScan enables customization of the project results reporting options. You can select the
following options:
• The minimum severity of the events shown in the report

• Include/exclude waveforms and thumbnails in the reports
• The maximum number of events to be shown in the report. The maximum number
of events will amount to 200, although it is possible to configure a greater number
if the option to show the thumbnails in the report is not selected.
• Frequency of reports generation.
• Dispatch of reports via email
Repositories
A repository is an address book in which an aggregation of data is kept and maintained
in an organized way, and where multiple databases or files are located for distribution
over a network, usually in computer storage. In QScan, it is a location for media storage
where watch folders and files to be analyzed are stored.
A repository can reside in the local QScan master machine or any other location in the
network (archive servers, additional nodes, etc). Any project in QScan will only access
files in a pre-configured repository. Any project in QScan will only be able to move/copy
files to a folder in a pre-configured repository.
Simple and "Clean" Reports

QScan provides reports in several different formats, such as HTML, PDF, XML or JSON.
The reports are designed to provide you with a clear view of what is wrong in the files by
listing the events found. Every event can show a thumbnail of the frame that has an
error, and can also display the waveform and vectorscope to have a clear view of the
video levels for each frame.
186 TP-00360-02

One of the biggest problems that users have when adopting AQC solutions is setting up
templates. Even if they purchased the software for compliance checking of delivered
content, and use a built-in template because this makes the adoption process easy, they
soon start to use AQC elsewhere in their workflows. In this case trying to find the right
threshold value for a certain type of test can take a long time. This is because you have
to create a template first, set the value, test the file, read the results, then modify the
threshold in the template again, save the template, retest the file, read the results. You
can quickly see how this can be frustrating because if you get the threshold wrong; it can
create a lot of false positives.
The QScan Single Pass Analysis allows the user to create a template, test the file, and
then adjust the threshold for any parameter and see the results of those changes
immediately without the need to retest the file again. This makes the adoption of AQC
much easier in other parts of an operation ingest, production and archive, as well as
delivery.
SystemConfig
Use the SystemConfig option to configure character sets for other languages, for
example, Japanese, Thai, Korean. You can also use this setting to configure the time zone
where the QScan system is located.
Due to the fact that it works with the Unicode standard, QScan supports extended
character sets for other languages.
Task List
The Task List window shows the analysis operations being carried out. The Task List
window additionally shows the License information and configuration of Nodes.
You can change the analysis priority of the files queued and obtain an overview of the
analysis tasks performed and the projects to which they belong.
Templates
A template is a collection of preset thresholds and parameters to be used for file analysis.
A template is used with a file repository location and project settings. You can either use
a previously defined template for common tasks, or create your own template when you
create a project. Once created, templates can be edited or deleted.
TP-00360-02 187
Glossary
Users
You can create users and give them different authorization access. There are three user
profiles available in QScan: Admin, Designer and Viewer.
• Admin: Privileges for all functionality within QScan.

• Designer: Privileges for the creation, configuration and viewing of projects and files
for which authorization has been given.
• Viewer: Solely enables viewing of the project and files for which authorization has
previously been given.
When you create a user, you must complete the fields in the window. QScan additionally
enables the editing and deletion of previously created users.
Watch Folders
Watch folders are folders or sub folders into one or more repositories, containing the
files that QScan will analyze. When setting up a project you can select either watch
folders, specific files, or both.
188 TP-00360-02
ABCDEFGHIJKLMNOPQRSTUVWXYZ Index
Index
A E
Activating a License 184 Editing
Adding Nodes 70
a License 28 Repositories 74
a Repository 34 Users 65
Nodes 68 EditShare
Users 63 Technical Support 9
Advanced 81 Email
Advanced Functionality 81 Notifications 184
Analysis 183 Settings 77
General Settings 183 Exporting a Macro 99
Parameters 183
Audio 171 F
Grouping 183
File Analysis 40
Configuring 40
B Does Not Start 180
Baseband/Waveform 153 FlowQScan Trigger 115
Basic Operation 33 Format Checks 147
Blackness 158 Frame Statistics 151
Blocking Nodes 71 Full Screen 80
C G
Configuring General
File Analysis 40 Features 10
Loudness Audio Grouping 41 Notes about Macros 96
Output Folders 43 Recommendations and Tips 16
Project Details 39 Getting Started 27
Reporting 44
Repositories 180
Conventions Used in this Guide 9
H
Creating HTML files 48
a Macro 94
a Repository 34
a Template 84 I
an EditShare Account 19
IMF 124
Importing a Macro 100
D Initial Project Settings 37
Default Node 31 Installing 19
problems with 179
Deleting
QScan 19
Nodes 70
Repositories 75 Installing FlowQScan Trigger 115
Users 66 Installing QScan 21
Displaying Full Screen 80 Intended Readership 9
Introduction 9
L
License 184
License Offline 29
TP-00360-02 1
Index ABCDEFGHIJKLMNOPQRSTUVWXYZ
License Online 28 Q
Licensing 184
Licensing QScan 28 QScan
Display 30
Locale Settings 76
MAX 14
Logging into QScan 27 ONE 12
Logging out 32 Overview 10
Loudness 178 PRO 13
Loudness Audio Grouping 41 using EditShare media spaces 111
with EditShare and Flow 111
M
R
Macros 91, 184
Creating 94 Registering for QScan 20
Elements of the GUI 93 Report 60
Exporting 99 Audio Details 60
General Notes 96 Reporting 44, 186
Importing 100 Reporting, Configuring 44
Management 61 Reports 47
Viewing 47
N Repositories 186
Adding 73
Network Shares 72 Deleting 75
Nodes 67, 184 Editing 74
Adding 68 Repository
Blocking 71 Creating 34
Deleting 70 Location 38
Editing 70 Requirements 11
Viewing Existing 67 Running a Project 46
O S
Offline License 29 Selecting the Repository Location 38
Online License 28 Sending Reports as Email 59
Output Folders 43, 184 Setting up network shares as repositories 72
Configuring 43
Single Pass Analysis 85
Overview 10
Supported Cloud Environments 15
Supported Formats 145
P Supported Virtual Machines 15
System Events 78
Parameters in FlowQScanTrigger.ini 116
System Events List 179
PDF files 49
SystemConfig 187
Project 46
Creating 37
Details 39 T
Input 185
Running 46 Task List 79, 187
Project Details Technical Support 9, 9
Configuring 39 Template Parameters 147
Projects 185 Templates 187
PSE (Photo Sensitive Epilepsy) 143 Creating 84
Troubleshooting 179
Configuring Repositories 180
File Analysis Does Not Start 180
Installation 179
Licensing 180
System Events List 179
2 TP-00360-02
ABCDEFGHIJKLMNOPQRSTUVWXYZ Index
U
User Examples 17
Users 188
Adding 63
Deleting 66
Editing 65
Using FlowAutomation with QScan 117
V
Video Quality 165
Viewing
Default Node 31
Existing Nodes 67
Existing Repositories 72
Existing Users 62
Report Audio Details 60
Report Video Details 51
Reports 47
Reports as HTML files 48
Reports as PDF files 49
Reports as XML 58
W
Working with Nodes 67
Working with Users 62
X
XML 58
TP-00360-02 3
Index ABCDEFGHIJKLMNOPQRSTUVWXYZ
4 TP-00360-02
TP-00360-02

QScan User Guide

Uploaded by

Copyright:

Available Formats

QScan User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

QScan User Guide

Uploaded by

Copyright:

Available Formats

User Guide

Copyright and Disclaimer

Copyright © 2019 by EditShare.

TP-00360-02 COMMERCIAL IN CONFIDENCE 3

CHAPTER 3: INSTALLING QSCAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

CHAPTER 4: GETTING STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Conventions Used in this Guide

• Efficient, fast, intuitive and robust web-based system.

Supported Cloud Environments

Supported Virtual Machines

General Recommendations and Tips

User Example 1: QScan Pro

• Template analyzing all parameters except for frame statistics

User Example 2: QScan Max

• 1 Base Machine + 4 Nodes.

• Template analyzing all parameters except for frame statistics.

Creating an EditShare Account

Registering for QScan

7. Click Run.The Welcome installation window opens:

8. Click Next. The End User License Agreement page displays.

12. Click Next.

14. Click Next.

16. Click Next.

18. The Ready to Install QScan screen displays.

19. Click Install. The QScan installation wizard starts.

23. Click Yes.

• “Logging into QScan” on page 27

Logging into QScan

Activating a QScan License Online

4. Click Activate to complete the license registration.

Activating a QScan License Offline

Viewing the Default Node

To view the default node, complete the following steps:

Logging out from QScan

See the following sections that describe basic operations in QScan:

• “Creating a Repository” on page 34

To create a repository, complete the following steps:

Creating a Local Repository

To create a repository on your local machine, complete the following steps:

3. Click the tick box.

Creating a Remote Repository

3. Enter the User name.

Tips for Networked Repositories

• Create a new user in the machine where QScan is running locally.

• Start the QScan Service.

See the following sections about creating a project:

• “Initial Project Settings” on page 37

Initial Project Settings

To configure the initial project settings, complete the following steps:

3. Enter a name for your project.

Selecting the Watch Folder Location

Configuring Project Details

To configure the project details, complete the following steps:

2. Type a description for the project.

Configuring File Analysis

To configure file analysis, complete the following steps:

Configuring Loudness Audio Grouping

To configure Loudness Audio Grouping, complete the following steps:

Configuring Output Folders

9. Reporting frequency; select the day and hour settings.