Change Details

**Short description** Right now apertus cameras are not able to record RAW videos directly to a mass storage medium. Video stream are instead being transferred onto a computer and written to a file on disk there. The format being used is a raw 12 bit image sensor dump without focus on adding potentially important metadata for postprocessing. While this is absolutely adequate for the current development phase, it may sooner or later be not enough and demand for a post-processing oriented container format could raise. This task is about defining the future raw video file format for apertus cameras. **Subtasks**

**Short description** Right now apertus cameras are not able to record RAW videos directly onto a mass storage medium. Video stream are instead being transferred onto a computer and written to a file on disk there. The format being used is a raw 12 bit image sensor dump without focus on adding potentially important metadata for postprocessing. While this is absolutely adequate for the current development phase, it may sooner or later be not enough and demand for a post-processing oriented container format could raise. This task is about defining the future raw video file format for apertus cameras. **Subtasks** This is an example of how the Task could be performed. This list is not compulsive and can be changed if needed. 1. __Current status analysis and requirement definition__ Before any decision or implementation can happen, it is important to depict the current state of how video data is being recorded and written to disk. This includes for example: - technical backgrounds of the current file format (i.e. "why is it as it is?") - examining the technical backgrounds of the signal processing path within the camera (i.e. "how does it work?") - technical possibilites and requirements of the signal processing path in terms of video container format (i.e. "what could we do with it and where are limits?") - defining requirements/recommendations for a container format Hint: When it comes to such requirements, they are often either "hard" and such out of question, or "soft" and a tradeoff between different aims. 2. __Available container formats__ Next step is to determine which free / open sourced options we are able to choose from. Characterizing those formats and checking against requirements from the previous subtask is expected to happen here.

**Short description** Right now apertus cameras are not able to record RAW videos directly onto a mass storage medium. Video stream are instead being transferred onto a computer and written to a file on disk there. The format being used is a raw 12 bit image sensor dump without focus on adding potentially important metadata for postprocessing. While this is absolutely adequate for the current development phase, it may sooner or later be not enough and demand for a post-processing oriented container format could raise. This task is about defining the future raw video file format for apertus cameras. **Subtasks** This is an example of how the Task could be performed. This list is not compulsive and can be changed if needed. 1. __Current status analysis and requirement definition__ Before any decision or implementation can happen, it is important to depict the current state of how video data is being recorded and written to disk. This includes for example: - technical backgrounds of the current file format (i.e. "why is it as it is?") - examining the technical backgrounds of the signal processing path within the camera (i.e. "how does it work?") - technical possibilites and requirements of the signal processing path in terms of video container format (i.e. "what could we do with it and where are limits?") - defining requirements/recommendations for a container format Hint: When it comes to such requirements, they are often either "hard" and such out of question, or "soft" and a tradeoff between different aims. 2. __Available container formats__ Next step is to determine which free / open sourced options we are able to choose from. Characterizing those formats and checking against requirements from the previous subtask is expected to happen here.