From: Timothée <timothee.informatique@regaud-chapuy.fr> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] [FEATURE PROPOSAL] Extracting codec-level data to binary files Date: Wed, 21 May 2025 15:34:27 +0200 Message-ID: <e6303044-e036-4771-97c6-0f421024e0e1@mail.infomaniak.com> (raw) Hello, I am interested in expanding ffmpeg's capabilities to extract low-level data from video codecs. Specifically, I'd like to implement functionality that would allow exporting frame data, macroblock information, quantization tables, and similar codec-specific elements to binary files for further analysis. After searching through the documentation and existing features, I haven't found similar functionality, though I may have missed something. Has this been implemented before, or are there related features I should examine? I'd appreciate your feedback on whether this feature would be considered valuable for the project and if it aligns with ffmpeg's development goals. If there's interest, I can provide a more detailed technical proposal. I'm new to both ffmpeg development and open source contributions in general, so I welcome any guidance or information that might help me contribute effectively. Thank you for your time and consideration. Timothée _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next reply other threads:[~2025-05-21 13:34 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-05-21 13:34 Timothée [this message] 2025-05-22 11:59 ` Ronald S. Bultje 2025-05-22 12:32 ` Ramiro Polla 2025-05-22 17:02 ` Timothée 2025-05-22 17:43 ` Ramiro Polla 2025-05-22 20:27 ` Ronald S. Bultje 2025-05-23 0:45 ` Michael Niedermayer 2025-05-23 0:57 ` Michael Niedermayer 2025-05-23 9:33 ` Timothée 2025-05-23 11:55 ` Michael Niedermayer 2025-05-26 18:09 ` Timothée 2025-05-26 18:57 ` Ronald S. Bultje 2025-06-06 19:32 ` Tomas Härdin
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=e6303044-e036-4771-97c6-0f421024e0e1@mail.infomaniak.com \ --to=timothee.informatique@regaud-chapuy.fr \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git