Re: [FFmpeg-user] retain timecode stream when transcoding v210 to FFV1/MKV

2025-05-05 Thread Christian Sievers via ffmpeg-user
Hello everyone, Thank you, this has been very helpful! So I think I have two options: - Wait until Matroska fully supports timecodes, which might take a while. - Or continue to use Quicktime, but with FFV1. Not as open and free, but supports timecode data. This would be a somewhat unusual way t

Re: [FFmpeg-user] retain timecode stream when transcoding v210 to FFV1/MKV

2025-05-05 Thread Christian Sievers via ffmpeg-user
> Kieran > > On Mon 5 May 2025 at 10:43, Christian Sievers via ffmpeg-user > mailto:ffmpeg-user@ffmpeg.org>> wrote: >> Hello everyone, >> >> Thank you, this has been very helpful! So I think I have two options: >> >> - Wait until Matroska full

Re: [FFmpeg-user] retain timecode stream when transcoding v210 to FFV1/MKV

2025-05-06 Thread Christian Sievers via ffmpeg-user
Hi, Thanks everyone for the timecode primers. Yes, these are archival considerations. Ideally, you don’t want to lose any information. This is what the time code tracks typically look like in our archive, using Mediainfo. There’s never more than one, and staff would have noticed if the digiti

Re: [FFmpeg-user] retain timecode stream when transcoding v210 to FFV1/MKV

2025-05-03 Thread Christian Sievers via ffmpeg-user
ood luck! > John > >> On May 2, 2025, at 10:58 AM, Christian Sievers via ffmpeg-user >> wrote: >> >> Hello world and hello ffmpeg-user list! >> >> We have roughly 30TB of v210 (uncompressed 8 bit 4:2:2 PAL) Quicktime mov >> video files, created

[FFmpeg-user] retain timecode stream when transcoding v210 to FFV1/MKV

2025-05-02 Thread Christian Sievers via ffmpeg-user
Hello world and hello ffmpeg-user list! We have roughly 30TB of v210 (uncompressed 8 bit 4:2:2 PAL) Quicktime mov video files, created when digitizing tape. We would like to transcode these to FFV1/MKV for archival purposes. However, when I’m doing a transcode like this: ffmpeg -i input_file -m

Re: [FFmpeg-user] retain timecode stream when transcoding v210 to FFV1/MKV

2025-05-03 Thread Christian Sievers via ffmpeg-user
Apologies, here is a tiny excerpt that has the timecode track, if you wanted an (imperfect) test file: https://videolooper.de/696trim.mov > On 3. May 2025, at 12:01, Christian Sievers via ffmpeg-user > wrote: > > Thanks! > > @BloodMan Yes I had seen that hint. > >

[FFmpeg-user] prevent clean aperture value cropping

2025-05-12 Thread Christian Sievers via ffmpeg-user
Hello, We would like to transcode v210 (uncompressed 8 bit 4:2:2 PAL) Quicktime mov video files to FFV1/MKV for archival purposes. ffmpeg crops these files, using Quicktime's CLAP atom (clean aperture value). We would like to preserve the full 720 pixel width. How can I do that? I'm using this

Re: [FFmpeg-user] prevent clean aperture value cropping

2025-05-14 Thread Christian Sievers via ffmpeg-user
If anyone had an idea how to make sure that the resulting files have the full 720 px, I’d be grateful! ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg

Re: [FFmpeg-user] prevent clean aperture value cropping

2025-05-15 Thread Christian Sievers via ffmpeg-user
Hello, It looks a lot like the file is actually cropped. At least, I can’t find a player or tool that tells me that the 720 px are still there. See the bottom for mediainfo and exiftool reports for the FFV1 file. Yes, the strange thing is, I did run frameMD5 checks on original and resulting co