Introduction
Library Events is a specialized application that provides additional value to the native Mediabank Library. A typical production company normally use Mediabank Library as a safe and efficient way to store their valuable media content and take advantage of its fast retrieval time and easy re-use of their content. These customers are usually in the Basic price group without access to the Events application.
Professional & Enterprise Mediabank users, however, may hold a library of assets/content intended for sharing or publishing. It could be the content from a sports event or just selected parts of the event, usually referred to as highlights. Sports are, at the present time, dominating the use of the Library Event application.
Note!
These Enterprise/professional companies are also using Mediabank to maximize their ROI with implemented rights management solutions.
The key services that Library Events provide are:
- It can search the entire Mediabank library for already logged highlights, incidents, interviews, etc. Depending on the user's organization, the number of logged incidents could be considerable. Medibank has customers with more than 400 000 logged events all the way back to the '60s. A user can choose an athlete and search all logged events for this person and retrieve the results within a second.
- Search in one particular Event (soccer game, biathlon, etc.) to perform post-production enhancements and add incidents previously missed during logging from a live ingest transmission. The user could also use previously logged events, and add additional to produce material for a follow-up program.
- Make Clips for distribution or publishing. All these logged Events are used to create small video clips from highlights/incidents and then published/distributed to selected destinations. These clips can manually or automatically be published/distributed depending on the incident.
An automated Mediabank workflow could be:
- Goal
- Incident is tagged (logged) by the official Tags user.
- The Mediabank Workflow detects "Goal" and identifies the 2 teams and the player.
- Makes an event (clip) that contains 20 sec prior to the goal and 10 sec after. Tot 30 sec.
- Determines the destination(s) and selects appropriate M-boxes
- M-boxes chooses the correct codec and publish/distributes the newly created media clips.
- In less than a minute the media clip could be published at both playing teams Web sites, distributed to hundreds of broadcasters sports desks, or shared/mirrored within Mediabank Library accounts.
Event View is often used to perform rough-cuts, creating clips and cliplists. The clips are typically highlights from an Event and downloaded for further editing or published directly. The clips are easily distributed or published, simply by selecting the appropriate Mbox.
The Event Workspaces are integrated with the Library, making it efficient navigating between thousands of log entries and event-clips in your possession. The main window still consists of three major elements, Search (2), and asset/search module to the left (3), Media player in the middle (5), and the Meta module to the right (7). All other functions are placed under the contextual button named MENU in the top middle of the screen. The Timeline in the lower-end is combined with destination M-Boxes.
Architectural overview
Mediabank is developed using modules that are shared amongst the Mediabank applications. To simplify the documentation structure, we use the same architectural structure. This documentation will refer to modules and components that this and future applications are sharing.
Each of the below topics is described in related articles found in this document library.
(1) Header module
Many of the less frequently used applications are now moved into the Header module. If you seek information on how to switch accounts, workspaces (ThumbView, ListView, Events; Tags, etc.), login info, logo handling, etc.
(2) Search module
Here you can find more information about the powerful search and filter functions in Mediabank:
(3) Asset module
More details about the asset list and columns are described in related articles
(4) Title module
Read more details about the Title module in the related article.
(5) Player module
(6) Navigation module
Read more on how to navigate within your Event asset and post tags and clips.
[Status module]
The status module has no function in Events and therefore not present.
(7) Meta module
The Meta module contains the most important topics in the Event application. Read more about Tags, Event, and Clips in a related article.
Metamodule - Event view(8) Timeline
The timeline shows all the events in a sequential view. Clicking on a selected event will automatically navigate the media player to that event and pause, waiting for you to hit the play button. At the same time, the Tag list will locate the corresponding tag and highlight it.
A note about Timecodes
Why is there a difference in the visible time-fields between the different modules?
The timeline shows the media-clip time that corresponds to the bottom bar in the media player. The media player's low right time shows the media clips total length. This clock starts from the start of the media clip (asset).
Then there is LTC (Longitudinal Time Code) viewed in the middle top of the media player that is considered (from our point of view) as "the" technical time code related to the exact reference. Everything in our system has this time as the base time reference.
To the right of the LTC is the match time. This clock starts at the game start and it corresponds with the tag list. The event timeline in the pull-up module will start at 0:0 for each period/clip).
----------------------------------
End of article
