Calrec SUMMA, Installation Manual

Page: 78 / 96

78 SUMMA
Networked Audio Production System
Setup - User Logging
USER CONTROL LOGGING SETUP
The requirement for comprehensive control change logging, has been provided to allow after-the-fact analysis of
production problems.
Basically the system captures control data and attaches a timestamp to establish when various controls changes were applied by the
operator on Apollo, Artemis and Summa Consoles and puts the results into a logging file. The logging file is held on the MCS cards
and requires the following entry to be added to the Studio Setup File as shown below:-
Once the User Logs are created on the MCS cards they can be opened using a Web-Browser which initially displays a Directory of User Logs.
When the required log a selected log is accessed a timestamped Table of Control data appears for further analysis.
As well as memory, preset, fader open/close, path copy/paste,time, CSCP and Path events, logging is implemented for as many of the
desk controls listed below as possible.. These are shown in a list of Path Controls on the following pages.
Those marked as (U) are unavailable and indicate that either the control was not available or that the control does not exist..
Filtered events (F) will only be filtered when showing absolute values (‘set to’) but not when showing changes i.e. (‘modified by’).
#######################################################################################
#####################
#
User Logging
#
#######################################################################################
#####################
# set to ‘true’ if wanting to enable user logging i.e. ‘UserLoggingEnabled = true’ (if commented out or
# missing it will default to false)
UserLoggingEnabled = true
# The time between file updates in seconds e.g ‘UserLoggingFileUpdatePeriod = 5’ Minimum value is 1 second
# (if commented out, missing or too low it will default to 1 sec). Note that this also affects the refresh
# period of the shaft and fader level logging so, if you want more resolution on fader movement, then make
# this number smaller, or bigger if you want less fader/shaft messages
UserLoggingFileUpdatePeriod = 1
# Clock time when the current logging file is closed and a new one is started. Format is 24 hour format
# hour:minutes e.g. ‘UserLoggingFileRolloverTime = 08:04’ (if commented out or missing it will default to
# 00:00). Range is 00:00 to 23:59
UserLoggingFileRolloverTime = 00:00
# The maximum disk space on the Master Controller card to allocate to the logging files in MB. When this
# space is exceeded, older files shall be deleted e.g ‘UserLoggingFileFolderMaxStorage = 5’ (if commented
# out or missing it will default to 10 MB). It is up to the user to put in sensible values here but, as a
# guide, 100MB would be much much more than you ever needed.
UserLoggingFileFolderMaxStorage = 10
# You can filter out event types that are logged by adding them to the following list where:
# 0 = PATH_CONTROL_EVENT
# 1 = DESK_CONTROL_EVENT (fader section and panel events)
# 2 = MEMORY_EVENT
# 3 = PRESET_EVENT
# 4 = TIME_EVENT
# 5 = FADER_OPENCLOSE_EVENT
# 6 = PATH_COPYPASTE_EVENT
# 7 = CSCP_EVENT
# So, for example, if you only wanted Path and fader open/close events but wanted to know when a logged fader
# event might be caused by CSCP then you would use: ‘UserLoggingIncludeEvents = 1,2,3,4,6’. If not present
# then all events are enabled
# UserLoggingFilterEvents = 0,1,2,3,4,5,6,7
# Note: User logs can be found in /home/MasterControl/Jetty/webapps/root/UserLogs and are accessible by the
# user from a web browser at <MCS IP address>:8080/UserLogs e.g. 192.178.1.0:8080/UserLogs
STUDIO SETUP FILE - USER CONTROL LOGGING SECTION