ichthyo/LUMIERA.clone
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

rewrap and clean up asciidoc structure (no content change)

Browse source
This commit is contained in:
Fischlurch 2010-11-28 07:03:11 +01:00
parent bfc7e70c99
commit 06ca9f68bd
1 changed files with 142 additions and 89 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

231
doc/design/workflow/LumieraWorkflowOutline.txt
View file

@ -1,105 +1,158 @@
Lumiera Workflows Lumiera Workflows
=================
:Author: Brian J.M. Rytel :Author: Brian J.M. Rytel
:Email: <tesla.drummer@gmail.com> :Email: <tesla.drummer@gmail.com>
:Date: :Date: July 2010
:Revision: 2.1 :Revision: 2.1
Lumiera Workflows
-----------------
----
Considerations:
-Technical
-User
----
1.Requirements & Considerations 1. Requirements & Considerations
(a)Ingest --------------------------------
It seemed easiest to me to just go through chronologically It seemed easiest to me to just go through the workflow chronologically
i.Technical
A.All ingest sources need a solid metadata structure, suggestions welcome: === (a) Ingest
Media Type attributes (codec, frame mode/rate, aspect, color science/LUT) ==== i.Technical
Clip Attributes (name, length, I/O, media I/O, bitrate, size All ingest sources need a solid metadata structure, suggestions welcome:
Acquisition Attributes (Modified EXIF data, ie: format, frame mode/rate, aspect, resolution, ISO, f-stop, shutter speed focal length, color format, camera,)
UID & Project/Sequence & Subclip & Render Reference - Media Type attributes (codec, frame mode/rate, aspect, color science/LUT)
Production Info (scene #, shot #, angle #, take rating, night/day, production name, DP, Camera Op, Director, set/location, date shot, actors/characters) - Clip Attributes (name, length, I/O, media I/O, bitrate, size
B.Tape/Video Ingest - Acquisition Attributes (Modified EXIF data, ie: format, frame mode/rate,
aspect, resolution, ISO, f-stop, shutter speed focal length, color format,
camera,)
- UID & Project/Sequence & Subclip & Render Reference
- Production Info (scene #, shot #, angle #, take rating, night/day, production
name, DP, Camera Op, Director, set/location, date shot, actors/characters)
===== Tape/Video Ingest
Connect to capture system through back-end/modules/plug-in Connect to capture system through back-end/modules/plug-in
Deck-control needs to handle both Firewire (1394) and Serial (RS232, RS422, Sony, Panasonic, JVC) could be internal controller, but at least a timecode hand-off to a plug-in. Needs to be able to control decks in single frame increments with precise TC. Deck-control needs to handle both Firewire (1394) and Serial (RS232, RS422,
C.Data Ingest Sony, Panasonic, JVC) could be internal controller, but at least a timecode
hand-off to a plug-in. Needs to be able to control decks in single frame
increments with precise TC.
===== Data Ingest
Extract/Write metadata to file module needed. Should parse files to make sure they're not corrupted Extract/Write metadata to file module needed. Should parse files to make sure they're not corrupted
ii.User
A.Should we look into set metadata collection systems to see if modules to sync and copy that data to the clip is viable? ==== ii.User
B.The GUI Ingest element should be logical and convenient to use, and in my opinion should handle both tape-based logging-capturing and data ingest. - Should we look into set metadata collection systems to see if modules to sync
(b)Edit and copy that data to the clip is viable?
i.Technical - The GUI Ingest element should be logical and convenient to use, and in my
A.Video & Audio playback opinion should handle both tape-based logging-capturing and data ingest.
#1-Coding should handle at least 4k, 32-bit, 200+MB/s, selectable LUTs (?)
=== (b) Edit
==== i.Technical
===== A. Video & Audio playback
*Requirement-1*: Coding should handle at least 4k, 32-bit, 200+MB/s, selectable LUTs (?)
Real-time of native codecs is important. Real-time of native codecs is important.
Coding should handle in-sync minimum 8 audio tracks, 96kHz/24bit Coding should handle in-sync minimum 8 audio tracks, 96kHz/24bit
(2) Main media playback windows, clip selector & timeline output both should meet #1
*Requirement-2*: Main media playback windows, clip selector & timeline output both should meet *Req-1*
Live scope simulators, vector and waveform a must, 3d/wheel good choice Live scope simulators, vector and waveform a must, 3d/wheel good choice
Live playback TC readouts from playheads Live playback TC readouts from playheads
Compatibility for low-latency hardware output to video & audio devices, w/timecode, likely a hand-off but would latency is important.
Integration to JACK, ALSA, or OSS would be ideal. *Requirement-3*: Compatibility for low-latency hardware output to video & audio devices,
Real-time (OpenGL?) rendering of simple filters w/timecode, likely a hand-off but would latency is important.
Back-ground CPU rendering - Integration to JACK, ALSA, or OSS would be ideal.
B.File Handling - Real-time (OpenGL?) rendering of simple filters
Other apps (FCP) are unable to or inconsistently work with updated media files mid-session, this is a back-end design concern. - Background CPU rendering
C.Project/Sequence Requirements
Project 'bins', user-created bins, media filtering (ex: all video or everything in scene #1) ===== B. File Handling
Thumbnail & list views Other apps (FCP) are unable to or inconsistently work with updated media files
Drag & Drop of clips between bins, playback windows & timelines. mid-session, this is a back-end design concern.
File and directory import
D.Timeline ===== C. Project/Sequence Requirements
All the normal essentials - Project 'bins', user-created bins, media filtering (ex: all video or everything in scene #1)
- Thumbnail & list views
- Drag & Drop of clips between bins, playback windows & timelines.
- File and directory import
===== D. Timeline
_All the normal essentials_
Render indicators (needs render, RT) on clips and/or timeline Render indicators (needs render, RT) on clips and/or timeline
Should be adjustable (frame mode/rate, would require script to translate old TC numbers to new timebase) Should be adjustable (frame mode/rate, would require script to translate old TC numbers to new timebase)
I recommend that the timeline video format setting be the “box” and clips “fill in” the box. FCP for example does weird things to the clips when you change the resolution/aspect of the sequence. Further it would make sense to have options in the sequence for how to handle non-native resolutions and aspect ratios (stretch, scale w/boxes, leave alone)
We have Track Nesting, but we need to have some way to gang sync/lock video with its audio track so both are cut and move simultaneously. I recommend that the timeline video format setting be the “box” and clips “fill
Currently, NLEs all use vertical, additive layering. We should work on including the ability to “flowchart” tracks (AE's pick-whip) like a compositor would, and change the “blend” modes. in” the box. FCP for example does weird things to the clips when you change the
resolution/aspect of the sequence. Further it would make sense to have options
in the sequence for how to handle non-native resolutions and aspect ratios
(stretch, scale w/boxes, leave alone)
We have Track Nesting, but we need to have some way to gang sync/lock video with
its audio track so both are cut and move simultaneously.
Currently, NLEs all use vertical, additive layering. We should work on including
the ability to “flowchart” tracks (AE's pick-whip) like a compositor would, and
change the “blend” modes.
Draw-on automation/keyframes & editing for both video & audio tracks. Draw-on automation/keyframes & editing for both video & audio tracks.
B.Misc
We need to have accessible, easily scriptable FX/Filter menus for clips, all NLEs throw a tab into the clip selector pain. ===== E. Misc
Whole app should be multi-core aware, especially any rendering engines. - We need to have accessible, easily scriptable FX/Filter menus for clips, all
Needs to work on multiple monitors NLEs throw a tab into the clip selector pain.
ii.User - Whole app should be multi-core aware, especially any rendering engines.
A.The 6 things an editor thinks about at work: - Needs to work on multiple monitors
The clips in the bin
Timeline
Timeline output
The edit tools ==== ii.User
Transitions ===== A. The 6 things an editor thinks about at work:
Filters/FX - The clips in the bin
B.Features that make life better - Timeline
Edit review/edit on the fly (Avid) - Timeline output
Quick Transitions (1-2 key/click transitions) - The edit tools
Match-frame - Transitions
Media Search - Filters/FX
(b)Export/Finishing
i.Technical ===== B.Features that make life better
A.EDL export - Edit review/edit on the fly (Avid)
Should export all major EDL formats - Quick Transitions (1-2 key/click transitions)
B.XML - Match-frame
We should look into something along the lines of the Apple XML, so that the project could be passed to XML compliant programs - Media Search
C.Media Export
Need to build a module that will render project and possibly re-encode it as well, but that could be a hand-off
D.Tape Export === (c) Export/Finishing
Essentially the reverse of the Ingest issue, must pass frame accurate deck control and fully synced audio/video. ==== i.Technical
E.Finishing EDL export::
I'm not sure if they plan to integrate color grading/finishing into Lumiera at some point but if not we need to look into compatibility for those applications. Should export all major EDL formats
ii.User XML::
A.EDL/XML Export We should look into something along the lines of the Apple XML, so that the
We need to leave the workflow that passes on lists in standardized forms. These also need to be easy enough to use without some application console script. project could be passed to XML compliant programs
B.Media Export Media Export::
Whether handled internally or externally we need to build an interface to make this seamless and intuitive, my favorite exporter is Premiere's which will render the output with any given setting. Need to build a module that will render project and possibly re-encode it as
C.Tape Export well, but that could be a hand-off
Should be able to handle both straight lay-off and “edit-to-tape”. Tape Export::
2.Types of Workflows Essentially the reverse of the Ingest issue, must pass frame accurate deck
(a)Film control and fully synced audio/video.
i.Captured Film-TK-Sound Sync Finishing::
ii.Ingest-NLE- I'm not sure if they plan to integrate color grading/finishing into Lumiera at
iii.(3) Possible output formats some point but if not we need to look into compatibility for those
A.EDL-Optical Print+Neg Cutting applications.
B.DI (Either new or oringinal TK)-Film
C.DI (Either new or oringinal TK)-Video/Media ==== ii.User
EDL/XML Export::
We need to leave the workflow that passes on lists in standardized forms.
These also need to be easy enough to use without some application console
script.
Media Export::
Whether handled internally or externally we need to build an interface to make
this seamless and intuitive, my favorite exporter is Premiere's which will
render the output with any given setting.
Tape Export::
Should be able to handle both straight lay-off and “edit-to-tape”.
2. Types of Workflows
---------------------
=== (a) Film
. Captured Film-TK-Sound Sync
. Ingest-NLE-
. (3) Possible output formats
.. EDL-Optical Print+Neg Cutting
.. DI (Either new or oringinal TK)-Film
.. DI (Either new or oringinal TK)-Video/Media