4 ms·
One of their recommended archival video formats is FFV1 in a Matroshka container. Following the endorsement, I used it in a GStreamer application that captured
by rgovostes 2y ago
One of their recommended archival video formats is FFV1 in a Matroshka container. Following the endorsement, I used it in a GStreamer application that captured a time lapse in a scientific data acquisition context.
Overall I wasn't too impressed with my choice. Only VLC can play it back, which made it a headache for downstream consumers. It may be a GStreamer issue but I also struggled to record timestamps on the frames.
Were I to do it again, I'd maybe just capture the raw Bayer frames and metadata in something like an MCAP file as my source-of-truth, with an H.264 proxy video on the side that's easier for most people to play back.
- cornstalks 2y agoCodec (FFV1) has nothing to do with timestamps or metadata, which live at the container level. Also, FFV1 and H.264 have different target markets. FFV1 focuses on lossless, whereas H.264 specializes in lossy compression. If you don’t need lossless I highly recommend a lossy codec.
- rgovostes 2y agoI should have said FFV1 in a Matroska container. It was a little while ago so the details are hazy. The use of a lossless codec was intentional for integrity of the captured frames.
- BoredPositron 2y agoThat's not how any of this works...