Aurora ingest error messages, Appendix b, Appendix – Grass Valley Aurora Ingest v.6.1 User Manual

Page 81

Advertising
background image

May 2007

Aurora Ingest System Guide

71

Appendix

B

Aurora Ingest Error Messages

The following table describes the Aurora Ingest error messages.

Error Message

Description

No available channel at the time of record

Could not allocate channel for recording. Please make
sure that AppCenter is running and channel is set to
AMPRecorder.

Could not switch router

Could not switch router. Please make sure that the
destination is not locked and router is running.

Could not switch timecode mode

Could not switch timecode mode

.

Could not cue the clip

Could not cue the clip. Please make sure that channel
is set to AMPRecorder, not AMPPlayer.

Clip already exists at this location

Clip already exists at this location. Please use a
different name.

Could not start record

Could not start record. Please make sure your Media
Server is running and responding.

Could not stop record

Could not stop record. Please make sure your Media
Server is running and responding.

The server storage is full

The server storage is full. Please clean up the server
storage.

Could not eject clip

Could not eject clip. Please make sure your Media
Server is running and responding.

Event may not start record as it conflicts
with another allocated event

Event did not/may not start record as it conflicts with
another allocated event.

Could not control CompuSat for recording

Could not control CompuSat for recording. Please
ensure that you have the correct CompuSat
configuration.

Aurora Ingest Server could not complete
record due to system shutdown

Aurora Ingest Server could not complete record due to
system shutdown. Please restart the system in order to
resume.

A user has canceled this Ingest event

A user has cancelled the Ingest event.

This event was prematurely stopped by the
media server

The event was prematurely stopped by the Media
Server. Please check your storage status.

This event may not have started and/or
stopped at correct timecode

The event may not have started and/or stopped at
correct timecode.

Advertising