...
| Source ID | string | A unique ID for the company generating the media that can be used to get back to the original media. The main use of this is if the filename changes as it goes through different company pipelines. This may only be for reviewed media, rather than all media, and ideally its something reasonably compact and human readible, for example <SHOWCODE>-<REVIEWID> – spy-1234 – where reviewid is an incrementing ID per show. For this document we dont care about its structure, only that it exists. |
| Source Entity | string | Identifies the shot, asset or entity. Potentially useful as a burn-in. |
| Source sub entity | string | This would be the way to identify the media within the source entity without versions. e.g. lets say I have a filepath /shows/spy01/bat001/pix/rnd/precomp_v001/precomp_v001.0001.exr spy01 = SHOW bat001 = SHOT = Source Entity precomp = Source subentity This would be used by an asset management system to group versions, without having to guess what the versioning system is. |
| source sub entity version | float | Version ID for sub-entity. |
| Task | string | Taskname if known at creation - |
| colorspace | string | Many file-formats do already have options for color spaces, but certainly for internal reviews facilities may decide to encode to a non-standard color space. For media that is crossing facilities we should stick to known embedded colorspaces, and allow existing tools to remap where necessary. |
| date authored | string | The latest date of the original authored content. This would be carried through any transcoding, so we dont end up with the transcoded timestamps. |
...
| Date Submitted | date string | repeated on each line for cases where the resulting excel sheet is merged. |
| Vendor | string | Vendor name, repeated on each line for cases where the resulting excel sheet is merged. |
| Filename | string | The filename that is being shipped to be reviewed. |
| Source ID | string | Used to map the following fields to the actual media. |
| review task name | string | The reviewing company may have their own task names, which could be "comp", "anim" |
| Review for | string | Notes on why the media is being reviewed, e.g. For Final, For Feedback, WIP. |
| Notes | string | Notes for the reviewer, so they know what they should be commenting on. |
...
| Date Reviewed | String | |
| Reviewer Names | String | Who was doing the reviewing. |
| Review Location | String | Where it was. |
| ReviewID | String | A unique ID that can be used to map annotations to a review. Ideally this is something human-readable, e.g. YYYYMMDDHHMM-<Location> but from the file format point of view, its simply a string. |
| Source ID | String | Reference back to the media source. |
| Source Entity | String | i.e. the shot |
| Sub-source entity | String | i.e. the sub-source |
| Notes | String |
...
Annotations would need to be in a more computer readable format such as XML or JSON. e.g. :
<review reviewid="<REVIEWID>">
<media sourceid="<SOURCEID>">
<annotation frame="<FRAMENUMBER>">
<line thickness="<SIZE>" style="<LINESTYLE>" color="<COLOR>">
<coord x="<X>" y="<Y>">
<coord x="<X>" y="<Y>">
<coord x="<X>" y="<Y>">
</line>
<brush style="" color="<COLOR>">
<coord x="<X>" y="<Y>" thickness="<SIZE>" opacity="<OPACITY>"/>
<coord x="<X>" y="<Y>" thickness="<SIZE>" opacity="<OPACITY>"/>
<coord x="<X>" y="<Y>" thickness="<SIZE>" opacity="<OPACITY>"/>
</brush>
<text x="<X>" y="<Y>" size="<SIZE>" label="<TEXT TO DISPLAY>" />
<colorcorrect x="<X>" y="<Y>" size="<SIZE>" area="<AREATYPE>" asccc="<ASC COLOR CORRECT>" />
</media>
</review>
...
RV has notes on performance here - https://support.shotgunsoftware.com/hc/en-us/articles/219042268-Optimizing-RV-Playback-Performance
Are there recommendations on versions of EXR that are better for review, particularly externally?