Your SlideShare is downloading. ×
FORK Overview
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

FORK Overview

3,881

Published on

This presentation is an overview of the FORK MAM system.

This presentation is an overview of the FORK MAM system.

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,881
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
112
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide


  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Mac/Win
    - Crossplatform
    - FORK Icon = One Source, multiple destinations.
    - Shared storage
    - Clients/Server Based

  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • Workflow example:

    - Start an ingest
    - PDS is looking for available port
    - Two in use
    - Free port used
    - MPR is writing media to storage
    - Client can view media from storage through share/fyber
    - Others can view the same media
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!
  • - Ingest, Edit, Playout
    - While ingesting, add markers and metadata. ANYWHERE! ANY client
    - After editing, export timeline: new clip add metadata, markers
    - PLAYOUT!
    - Why? Central storage!



















  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Prod Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.
  • - A clip contains metadata
    - A smartbin is filtering on metadata
    - Based on this metadata the clip will be visible in multiple Smart Bins.

  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • - Central storage: multiple users can work with the same material
    - FORK Production Server: rack room, 24/7 online, admin only.
    - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time!
    - FORK RFU: transcoding to other formats, QT codecs only.
    - FORK Production Clients: Same central storage
    - Connected via ethernet to FORK Production Server.
  • FORK Playout Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Playout Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Playout Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Playout Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Playout Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Playout Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • FORK Playout Client runs modules.
    Depending on user rights, you have access to these modules
    All modules are in the Client, based on login these modules are activated.

  • - 24/7 playlist
    - Control windows shows the actual part, including ON-AIR
    - Playlist moves throught Control Window
    - Playlist becomes History, short part is visible in the Control Window
    - Playlist can be editted via Playlist Editor, via a segment (timeframe)
    - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.

  • - 24/7 playlist
    - Control windows shows the actual part, including ON-AIR
    - Playlist moves throught Control Window
    - Playlist becomes History, short part is visible in the Control Window
    - Playlist can be editted via Playlist Editor, via a segment (timeframe)
    - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.

  • - 24/7 playlist
    - Control windows shows the actual part, including ON-AIR
    - Playlist moves throught Control Window
    - Playlist becomes History, short part is visible in the Control Window
    - Playlist can be editted via Playlist Editor, via a segment (timeframe)
    - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.

  • - 24/7 playlist
    - Control windows shows the actual part, including ON-AIR
    - Playlist moves throught Control Window
    - Playlist becomes History, short part is visible in the Control Window
    - Playlist can be editted via Playlist Editor, via a segment (timeframe)
    - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.

  • - 24/7 playlist
    - Control windows shows the actual part, including ON-AIR
    - Playlist moves throught Control Window
    - Playlist becomes History, short part is visible in the Control Window
    - Playlist can be editted via Playlist Editor, via a segment (timeframe)
    - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.

  • - 24/7 playlist
    - Control windows shows the actual part, including ON-AIR
    - Playlist moves throught Control Window
    - Playlist becomes History, short part is visible in the Control Window
    - Playlist can be editted via Playlist Editor, via a segment (timeframe)
    - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.

  • - 24/7 playlist
    - Control windows shows the actual part, including ON-AIR
    - Playlist moves throught Control Window
    - Playlist becomes History, short part is visible in the Control Window
    - Playlist can be editted via Playlist Editor, via a segment (timeframe)
    - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.

  • - 24/7 playlist
    - Control windows shows the actual part, including ON-AIR
    - Playlist moves throught Control Window
    - Playlist becomes History, short part is visible in the Control Window
    - Playlist can be editted via Playlist Editor, via a segment (timeframe)
    - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.

  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • - A clip contains Metadata + Markers
    - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file
    - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number.
    - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
  • ×