Rowe and Company File Based Workflow Design
•Télécharger en tant que PPTX, PDF•
0 j'aime•555 vues
This Rowe and Company presentation explores Avid Technology's newsroom computer system workflow and Avid's workgroups workflow and how the two separate databases affect broadcast news production.
Recommandé
Recommandé
Contenu connexe
Similaire à Rowe and Company File Based Workflow Design
Similaire à Rowe and Company File Based Workflow Design (20)
Dernier
Dernier (20)
Rowe and Company File Based Workflow Design
- 1. File Based Production Workflows Rowe and Company’s Workflow Design expands Avid’sNewscutter Newsroom Computer System process.
- 2. R&C Workflow Design Send the same metadata/decisions to every UI in Avid workgroups Custom templates. Optimizes your production system investment. Breakout of limits to the NRCS workflow Custom design by Rowe and Company, LLC
- 3. Avid’s NRCS Process Based on slug and video identification Slug and Video ID created in iNEWS Video ID and Slug extracted by NRCS tool in NewsCutter NewsCutter checks media into Interplay with Video ID and Slug Command gets slug and video ID from iNEWS and sends to AirSpeedplayout
- 4. iNEWS and Interplay Two most important production components have separate databases. Metadata between iNEWS and Interplay is limited Only Video ID and Slug are passed via NewsCutter Scripts in iNEWS Media and metadata in Interplay
- 5. NRCS Workflow Avid’s newsroom computer system workflow tracks two most important pieces of metadata for play out over two paths.
- 8. R&C Professional Service Our workflow design deliver metadata from associated media to all Avid broadcast user interfaces Your Solution – Workflow Design
- 9. Start with all data – deliver what is needed where it’s required
- 10. R&C Delivers Non-linear Workflows Rowe and Company’s file based workflow design provides central distribution of editorial decisions/metadata to every user interface in Avid’s workgroup environment creating non-linear access to metadata. R&C designs data flow processes R&C enhances traditional workflow R&C provides every user with information they need where they want it.
- 11. File Based and Non-linear Rowe and Company, LLC professional services deliver designs to fit your Avid workgroups workflow:
- 12. Rowe and Company R&C Professional Services deliver a file based workflow including metadata. Take Avid workgroups workflow to the next level of news production. We design processes to manage distribution to iNEWS (metadata) and Interplay (media and metadata) R&C designs workflow for the entire production process including NRCS steps R&C delivers every user information they need where they want it.
Notes de l'éditeur
- (((((click)))))Avid’s newsroom computer system workflow is hierarchal and dual routed.(((((click)))))It delivers the slug and video ID generated in iNEWS(((((click)))))Through the NewsCutter NRCS Tool to Interplay(((((click)))))Now the Interplay ISIS world knows those two important pieces of metadata and where they belong(((((click)))))Along comes Avid’s device control – Command – and it takes the same slug and video ID and sends it to AirSpeed and existence and play status back to iNEWS(((((click)))))
- That’s how the iNEWS Interplay metadata flow works today.(((((click)))))Your most important editorial decisions regarding video travels dual routes to its destination and lives in two otherwise disconnected databases.(((((click)))))The NRCS workflow is limited to slug and video ID.NewsCutters is the metadata broker for the Interplay route and Command directs link with AirSpeed.(((((click)))))However, the script associated with the video live in iNEWS(((((click)))))And the media and metadata – other editorial decisions live in Interplay(((((click)))))
- It’s a dual path beginning at creation and concluding at destination.(((((click)))))The slug and video ID are definitely the two most important pieces of metadata associated with video for play out or distribution.(((((click)))))This is the hierarchy for slugs and video IDs in the NRCS workflow(((((click)))))
- And one of the twin IDs uses NewsCutter to send it on its Interplay route(((((click)))))And the other ID uses Command to deliver it to AirSpeed and reunion with its twin ID – separated at birth.(((((click)))))
- Rowe and Company professional services uses designs to eliminate confusion in a file based workflows(((((click)))))R&C professional services turns the hierarchy of the NRCS workflow into an “inverted pyramid.”(((((click)))))You still use the NRCS workflow but change its makeup with our services so all editorial decisions associated with a story are trackedThe information goes from one to all but is filtered to each users interfaces requirements.(((((click)))))
- Confidence along the editorial and production processes to keep everyone in sync and comfort.(((((click)))))Rowe and Company professional services add value with guidance in iNEWS and Interplay database configurations to deliver your decisions where they need to be known when the process requires(((((click)))))The promise is information every where its required and including but beyond slug and video ID. How about photographer name, location and time, story contact and number just to mention a few. These are historical editorial decisions affecting all subsequent production decisions. R&C delivers just the information required by the user in the Avid tool designed for their job.(((((click)))))
- Let’s consider how the filed based and non-linear metadata distribution work(((((click)))))Rowe and Company Professional Services complete the file based and non-linear workflow cycle in Avid workgroups(((((click)))))You can take editorial meeting decisions and stamp it to filed based camera media to begin the process before the NRCS workflowand iNEWS stays in sync throughout the process beyond NRCS’s slug and video ID.(((((click)))))Same for Instinct(((((click))))) Assist (((((click))))) Access (((((click))))) NewsCutter(((((click))))) Command (((((click))))) Capture Manager (((((click)))))And AirSpeed (((((click)))))And the information flow with iNEWS becomes two way.(((((click)))))