From: Dmitrii Ovchinnikov <ovchinnikov.dmitrii@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] libavformat\matroskadec.c: crop support for matroska demuxer. Date: Mon, 26 Sep 2022 16:22:17 +0200 Message-ID: <CADXbNkTcXgzs0D2WU6baFvZa7di9bwU4rXO8tchZHpNet0e+mg@mail.gmail.com> (raw) In-Reply-To: <GV1P250MB073710558A6BBB0FB0A69C538F4F9@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> Hi Andreas, Thanks for your quick and direct feedback about the patch. Your feedback about the displayWidth, displayHeight and the display aspect ratio shows that you have deep thinking in this area. I have several questions and comments about your feedback. 1. Yes, i will get this change, and put the added fields at the rear part of AVCodecParameters 2. I will split these changes into different commits. Should I also split the edits in the AVCodecContext and codec_pack.c files into different commits? 3. Yes, I will apply the container cropping info additionally to the bitstream cropping. 4. Yes, I will apply the cropping for receive_frame API as well. 5. I'm also working on “clean aperture” for MP4 container. mov is a part of the subset of MP4. I will submit that patch to ffmpeg after i finished it. Maybe one month later. 6. Thanks for a good reference. 7. Yes, there are many problems in the MKVToolNix. MKVToolNix may result in some inconsistent of display aspect ratio when editing crop information. There are two part of work(for support of Matroska cropping), one part is matroska encoder, another is matroska decoder. This time i submit the matroska decoder patch. In the matroska encoder, i have already taken the inconsistent into consideration, and did some work to make sure it keeps consistent. Do you want me to put the matroska encoder and matroska decode together in the same patch to submit ffmpeg, or do you want I put them in two separate patch and submit seperately? _______________________________________________ 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 prev parent reply other threads:[~2022-09-26 14:22 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-21 11:29 OvchinnikovDmitrii 2022-09-21 15:00 ` Andreas Rheinhardt 2022-09-26 14:22 ` Dmitrii Ovchinnikov [this message] 2022-10-01 6:35 ` Dmitrii Ovchinnikov
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=CADXbNkTcXgzs0D2WU6baFvZa7di9bwU4rXO8tchZHpNet0e+mg@mail.gmail.com \ --to=ovchinnikov.dmitrii@gmail.com \ --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