Patent Description:
In broadcast productions covering an event, e.g. a sports event, multiple cameras capture the event from different perspectives. To this end, there are cameras which are installed at positions where most of the action in the event is expected. Consequently, the camera streams provided by these cameras are frequently used in the program output stream of the video production. Therefore, these cameras are labeled "high usage cameras" in the present application. In addition to the high usage cameras, there are other cameras capturing images from a specific perspective that may be interesting or not depending on how the event evolves. An example of such other cameras is a camera mounted in the cockpit of a racing car capturing the perspective of the racing car driver. It may therefore happen that the camera stream from such camera is not used at all in the production. However, if for instance an accident happens just in front of the racing car capturing the scene, the camera stream from such camera is very interesting and will be used in the production. Consequently, these cameras are labeled "low usage cameras" in the present application to distinguish them from the high usage cameras. Since it is unpredictable whether the camera stream of a low usage camera will be important for the production or not it is necessary to record all camera streams of the low usage cameras to enable a replay of the scene which is a valuable contribution to the video production.

The camera streams of the high usage cameras are typically recorded on a video production server providing integrated video recording capabilities. However, the video production server is a very expensive device and has a limited video recording capacity which in most cases does not allow for recording all camera streams from low usage cameras. Rather, the recording capacity is limited to recording the camera streams from the high usage cameras.

Taking this as a starting point there is a need for a video production system and a method enabling cost-efficient recording of camera streams from a plurality of high usage and low usage cameras.

<CIT> relates to a computer-implemented method for presenting, selecting and viewing multi-feed content.

According to a first aspect the present disclosure suggests a video production system comprising a plurality of low usage cameras, a plurality of high usage cameras, and a video production server, which ingests and stores camera streams provided by the plurality of high usage cameras. The system further comprises a cloud recorder. The cloud recorder ingests and stores camera streams provided by the plurality of low usage camera. The cloud recorder is communicatively connected via a first data connection with a replay device enabling an operator to browse through all the recorded camera streams from the plurality of low usage cameras and to select one of the recorded camera streams for replay by sending a corresponding command to the cloud recorder. Furthermore, the cloud recorder is communicatively connected via a second data connection for providing the recorded camera stream that has been selected to the video production server.

The cloud recorder can be rented on an as needed basis in terms of duration and capacity depending on the covered event. This approach is more cost efficient than providing additional video production servers for storing the camera streams of the low usage cameras on site or in a studio because video production servers are expensive devices.

The terms "cloud" and "cloud recorder" are to be understood in a broad sense. The term "cloud" may refer to a public cloud service and/or to infrastructure located in a remote data center that is, for example, reserved for the broadcaster and not accessible to the public.

In an advantageous embodiment the cloud recorder is adapted for transferring the recorded camera streams as low bit rate data streams via the first data connection and for transferring the selected camera stream as a high bit rate data stream via the second data connection.

The low bit rate data stream has a bit rate of <NUM> to <NUM> MB per second per camera stream while the high bit rate camera stream ranges from <NUM> to <NUM> MB per second per camera stream. However, the proposed bit rates are only an example, and the present disclosure is not limited to a specific bit rate or range of bit rates.

It has been found useful to provide for a video encoder for encoding the camera streams of the low usage cameras. An appropriately encoded camera stream can reduce the required bandwidth of data connection for transferring the camera streams.

In a further advantageous embodiment, the second data connection connects the cloud recorder with a file access and transcoder device receiving a command from the replay device identifying the selected camera stream. The file access and transcoder device downloads the selected camera stream from the cloud recorder.

In this case it has been found useful when the file access and transcoder device transcodes the downloaded camera stream and transfers it to the video production server.

Transcoding the downloaded file facilitates the integration of the selected camera stream into the video production because the camera streams from the high usage cameras may have a different format.

According to a second aspect the present disclosure suggests a method for video production. The method comprises.

According to a preferred embodiment of the method, the step of selecting a camera stream also involves defining a beginning and ending of the camera stream. Thus, only the portion of the camera stream between the defined beginning and the ending of the video clip is transferred from the cloud recorder to the video production server. This approach limits the data traffic to a necessary minimum.

Exemplary embodiments of the present disclosure are illustrated in the drawings and are explained in more detail in the following description. In the figures, the same or similar elements are referenced with the same or similar reference signs.

In the figures the same or similar components are labelled with the same or similar reference signs.

<FIG> schematically displays a sports event and more particularly a racing event. <FIG> displays three racing cars <NUM> racing on a racing track <NUM>. Cameras <NUM> are installed along the racing track at the most interesting locations of the racing track <NUM> such as curves, chicanes or the home stretch. The camera streams of the cameras <NUM> are included most of the time in a program output stream of the video production. Therefore, the cameras <NUM> are labeled as high usage cameras. In addition to that, there are cameras <NUM>, which are mounted in the racing cars <NUM> covering different perspectives from the racing car, for instance the view of the racing car driver. Typically, the camera streams of the cameras <NUM> mounted on board of racing cars <NUM> are used in the video production only if the camera <NUM> captures a scene which provides added value to the video production. In other words: Most of the time the camera streams of the cameras <NUM> are not included in a program output stream. Thus, the cameras <NUM> are labeled in the present application as "low usage cameras".

It is noted that the important difference between high usage cameras <NUM> in the low usage cameras <NUM> is not whether the cameras are mobile or stationary or their image resolution but rather the fact to which extent their camera streams are used in the program output stream of the video production.

<FIG> illustrates an embodiment of a video production system <NUM> according to the present disclosure. The heart of the video production system <NUM> is a video production server <NUM> which receives the camera streams of the high usage cameras <NUM> via wired and/or wireless data connections <NUM>, e.g. according to the SDI or ST <NUM> standard. Such video production server is commercially available for instance from EVS Broadcast Equipment ®. The video production server <NUM> ingests and stores the camera streams from the high usage cameras <NUM>. Furthermore, the video production server <NUM> provides for mixing functionalities to integrate different camera streams and/or video clips to generate a program output stream PO. For big events with many cameras <NUM> multiple video production servers <NUM> can share the tasks to make the video production. For the sake of simplicity, it is assumed in the following that there is only one video production server <NUM>.

The low usage cameras <NUM> are connected with an encoder <NUM> via wired and/or wireless data connections <NUM>. The encoder <NUM> outputs the camera streams of the low usage cameras <NUM> as encoded data streams. The term "encoded" is to be understood in a broad sense and encompasses e.g. compressed data streams. The camera streams are encoded for example as SRT (secure reliable transport) streams. However, any other suitable transport standard can be used as well. The encoded data streams are transferred via data connections <NUM> to a cloud recorder <NUM> that ingests and stores the encoded camera streams. In <FIG> a vertical dashed line <NUM> separates devices on site of the video production and in the cloud. Devices on the left side of the dashed line <NUM> are on site while the cloud recorder <NUM> on the right hand side of the dashed line <NUM> is implemented in the cloud.

A replay device <NUM> is connected to the cloud recorder <NUM> by a data connection <NUM>. In this way the replay device <NUM> has access to all stored camera streams from the cameras <NUM>. The camera streams are provided as low data rate streams in the range of <NUM> to <NUM> MB per second per camera stream by the cloud recorder. In this way the replay device <NUM> enables an operator to browse through camera streams recorded on the cloud recorder <NUM>. When the operator finds a recorded video clip, the operator defines an entry and exit point for the clip and sends this as a command to a media workflow management device <NUM> that essentially is a single entry point to orchestrate and monitor media files as they move through the live production. The media workflow management device <NUM> sends a command to an access and transcoder device <NUM> that receives the selected video clip via a data connection <NUM> as a high data rate data stream in the range of <NUM> to <NUM> MB per second. The access and transcoder device <NUM> transcodes the selected video clip to facilitate its integration into the program output stream by the video production server <NUM>. To this end the access and transcoder device <NUM> is connected by a data connection <NUM> with the video production server <NUM>.

In an alternative embodiment the selected camera stream is transferred entirely to the video production server <NUM>. The editing of the camera stream is then performed on the video production server. the entry and the exit (beginning and ending) of the video clip is defined on the selected camera stream stored on the video production server.

One important advantage of the architecture of the video production system <NUM> according to the present disclosure is the scalability of the cloud recorder <NUM>. The cloud recorder can be rented on an as needed basis in terms of duration and capacity. if many camera streams from low usage cameras <NUM> need to be recorded, the cloud recorder <NUM> can be scaled accordingly. Therefore, the broadcaster does not the need to provide for a lot of hardware that can handle storage and processing capabilities for big events when such events only occur from time to time. This is an important cost advantage for the broadcaster.

Claim 1:
Video production system (<NUM>) comprisinga plurality of low usage cameras (<NUM>) occasionally used in a program output stream, a plurality of cameras (<NUM>) frequently used in a program output stream and a video production server (<NUM>) which ingests camera streams provided by the plurality of frequently used cameras (<NUM>), wherein the system further comprises a cloud recorder (<NUM>),
- wherein the cloud recorder (<NUM>) ingests and stores camera streams provided by the plurality of low usage cameras (<NUM>) occasionally used in the program output stream,
characterized in that
- the video production server (<NUM>) stores the camera streams provided by the plurality of frequently used cameras (<NUM>),
- that the cloud recorder (<NUM>) is communicatively connected via a first data connection (<NUM>) with a replay device (<NUM>) enabling an operator to browse through all the recorded camera streams from the plurality of low usage cameras (<NUM>) and to select one of the recorded camera streams for replay by sending a corresponding command to the cloud recorder (<NUM>); and
- that the cloud recorder (<NUM>) is communicatively connected via a second data connection (<NUM>) for providing the recorded camera stream that has been selected to the video production server (<NUM>).