Skip to content

Commit

Permalink
Update Case_study.md
Browse files Browse the repository at this point in the history
  • Loading branch information
digitensions authored Feb 19, 2024
1 parent c1009bc commit d560eec
Showing 1 changed file with 9 additions and 3 deletions.
12 changes: 9 additions & 3 deletions Doc/Case_study.md
Original file line number Diff line number Diff line change
@@ -1,16 +1,17 @@
# RAWcooked Case Study

## BFI National Archive
#### Joanna White, Knowledge & Collections Developer
By Joanna White, Knowledge & Collections Developer

At the [BFI National Archive](https://www.bfi.org.uk/bfi-national-archive) we have been encoding DPX sequences to FFV1 Matroska since late 2019. In that time our RAWcooked workflow has evolved with the development of RAWcooked, DPX resolutions and flavours and changes in our encoding project priorities. To find out more take a look at my [NTTW5 presentation about the BFI's RAWcooked use](https://www.youtube.com/@MediaAreaNet/streams). Today we have a fairly hands-off automated workflow which handles 2K, 4K, RGB, Luma, DPX and Tiff image sequences. This workflow is built on some of the flags developed by the Media Area and written in a mix of BASH shell scripts and Python3 scripts and is available to view from the [BFI Data & Digital Preservation GitHub](https://github.com/bfidatadigipres/dpx_encoding). In addition to our RAWcooked use I will also consider how we use other Media Area tools alongside RAWcooked to complete necessary stages of this workflow.
At the [BFI National Archive](https://www.bfi.org.uk/bfi-national-archive) we have been encoding DPX sequences to FFV1 Matroska since late 2019. In that time our RAWcooked workflow has evolved with the development of RAWcooked, DPX resolutions and flavours and changes in our encoding project priorities. Today we have a fairly hands-off automated workflow which handles 2K, 4K, RGB, Luma, DPX and Tiff image sequences. This workflow is built on some of the flags developed by the Media Area and written in a mix of BASH shell scripts and Python3 scripts and is available to view from the [BFI Data & Digital Preservation GitHub](https://github.com/bfidatadigipres/dpx_encoding). In addition to our RAWcooked use I will also consider how we use other Media Area tools alongside RAWcooked to complete necessary stages of this workflow.

This case study is broken into the following sections:
* Server configuration
* Image sequence assessment
* Encoding the image sequence
* Encoding log assessments
* FFV1 MKV validation
* FFV1 Matroska validation
* FFV1 Matroska demux to image sequence
* Conclusion & helpful test approaches
* Additional resources

Expand Down Expand Up @@ -53,6 +54,8 @@ rawcooked -y --all --no-accept-gaps -s 5281680 <path/sequence_name/> -o <path/se

## FFV1 Matroska validation

## FFV1 Matroska demux to image sequence

## Conclusion & some helpful test approaches

The workflow covers most of the the areas we think are essential for safe automated encoding of the DPX sequences. There is a need for manual intervention when repeated errors are encountered and an image sequences never makes it to our Digital Preservation Infrastructure. Most often this indicates a different image sequence flavour we do not have covered in our licence, but sometimes it can indicate a larger issue with either RAWcooked of FFmpeg encoding. Where errors are found these are reported to an error log named after the image seqeuence, for easier monitoring.
Expand All @@ -77,3 +80,6 @@ The results of these three enquiries is always a brilliant way to open an Issue


## Additional resources

['No Time To Wait! 5' presentation about the BFI's evolving RAWcooked use](https://www.youtube.com/@MediaAreaNet/streams). Link to follow.
[RAWcooked cheat sheet](https://github.com/bfidatadigipres/dpx_encoding/blob/main/RAWcooked_Cheat_Sheet.pdf)

0 comments on commit d560eec

Please sign in to comment.