RAWcooked
Data is never RAW.
Data is always cooked in a way or another.
Jérôme Martinez
No Time To Wait, London, October 2018
Raw files
Huge size
(4K+ is coming, can be 100 MB/frame, several TB per hour)
1 file per frame (thousands of files in a directory)
Not playable as is by several players (VLC...)
So many DPX or TIFF format flavors
(interoperability issues)
FFV1
Lossless video compression format
Open source, patent free
Adopted by several archives
Being standardized (IETF)
Frames are divided by slices, with checksums
Compression
Example with 1 second at 24 fps 10-bit HD film on a 6-core (12-thread) Skylake-X CPU:
- 24 DPX files (or in ZIP/TAR uncompressed): 189 MB
- 1 compressed ZIP file: 175 MB in 10 seconds
- 1 compressed LZMA2 file: 154 MB in 30 seconds
- 1 compressed LZMA2 solid (don't do that!) file: 144 MB
- 1 FFV1/MKV Intra 16-slice file: 105 MB in 1.5 seconds
Tests on SD 10-bit content
- Sponsored by VIAA
- On several TB of MXF/JP2k/PCM content
- Different sources and kinds of material
- E5-2698V3 (16 cores+HT, 2.3-3.6 GHz)
Tests on SD 10-bit content
Advantages
- Open source and free (FFmpeg)
- Package is 1.5-3x smaller than DPX/TIFF
- Cheksum by "Cluster" (usually 1 second) at container level
- Cheksum by "Slice" (you choose how many per frame) at video level
- Files are natively playable by lot of players (VLC, FFplay...)
Disadvantages
- You lose some metadata
(DPX/TIFF header: scan software, some colorimetry info, film type, DPX time code, shutter angle, gamma...)
- Complicated command line
- But...
RAWcooked
- Easy: just a short command line
"rawcooked YourDirectoryName"
- Store DPX/TIFF headers/footers in a specific Matroska attachment
- Store other sidecar files as Matroksa attachments
- Output is a single Matroska/FFV1/FLAC file
- Encoding is reversible (bit-by-bit to original files)
"rawcooked YourMatroskaFileName.mkv"
Usages
- Storage
Save HDD/LTO space (less €...)
- Transport
Encode, transport, decode; you save bandwidth (€... and transfer speed) without changing something else in your workflow (same files after revert to DPX/TIFF)
Remaining drawbacks
- More CPU intensive than uncompressed ZIP
(future project: use GPU and/or SSE/AVX)
- You lose a complete slice content if there is a single corrupted bit
(Mitigated with several slices per frame, MediaConch can fix a bitflip error and could be extended to a byte error)
Development
Reto.ch commited to main sponsorship end of 2017
Other sponsors showed interest begin of 2018
First Beta releases first half of 2018
Sponsors (and some others) tested with their files during the past 6 months
Flagged as stable 2 days ago
Supported input formats
- DPX/Raw: 8/10/12/16 bit, RGB/RGBA
- TIFF/Raw: 16 bit, RGB
- WAV/PCM: 16/24 bit, 1/2/6 channel, 44/48/96 kHz
- AIFF/PCM: 16/24 bit, 1/2/6 channel, 44/48/96 kHz
- Based on files from our sponsors
- More formats or format flavors on request
Our first sponsors
- AV Preservation by reto.ch (main sponsor)
- National Audiovisual Centre Luxembourg (CNA)
- National Library of Norway
- Irish Film Institute (IFI)
- Northwest University Library
- National Library of Wales
Financial sustainability
- Open source code provided without lock to sponsors
- Deliveries on our website are with a lock
- DPX 8/10 bit RGB & WAV 2ch 48kHz flavors are usable by default
- We provide a key for other format flavors and features (temporary key possible)
- 1000 € for first flavor/feature
+ 500 € per additional flavor/feature
- To be compared with storage cost saving
(cost divided by 2, speed multiplied by 2)
We need you!
Can be improved only if YOU help
- Speed improvement (GPU/SSE/AVX)?
- Error correction code?
- Support of reels?
- CFA/Bayer/RGGB support?
- Graphical interface?
- More input formats?
We need you!
It is not only about money
- Tests
- Documentation
- Advocacy
- Use it :)
- ...
QC Workshop
In Luxembourg on November 29
With support from National Audiovisual Centre (CNA)
Lead by Ashley Blewer
Focus on QCTools, MediaInfo, MediaConch, RAWcooked