Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
This just keeps getting weirder and weirder. setdar seems to be a workaround for tinterlace's SAR change for some circumstances but not for others. I'm going to explore further until I figure it out and can present some simple cases. Opinion: tinterlace changing SAR is not a good idea. Anything changing SAR is not a good idea unless the 'anything' is something that differentially changes samples/line and lines/frame (i.e newPAR) _AND_ newDAR/newPAR != oldDAR/oldPAR. ...But no matter. I'll address that issue in the future. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
I've made some mistakes because of so many moving parts: SAR, DAR, 720x240, 720x480. I will slow down my responses and will endeavor to be accurate. Kindly disregard the prior 2 responses. The problem is with tinterlace (and apparently with weave, also), and I'll prove it. Kindly stand by. On 01/04/2021 04:11 PM, Mark Filipak (ffmpeg) wrote: Sorry, I made a typo... On 01/04/2021 03:52 PM, pdr0 wrote: Mark Filipak (ffmpeg) wrote You can't interleave images with different dimensions Aout has separated fields, to 720x240 , but Bout is 720x480 [Bout] is 720x240: I'm using 'mode=send_field' in 'bwdif=mode=send_field', and the following 'decimate' doesn't change that. The problem is that 'tinterleave' is marking the output as "SAR = 16:9" instead of "8:9" (which is what it should be and should never be changed). No, [Bout] is 720x480 bwdif in send_field mode means double rate deinterlacing. 720x480 59.94 fields per second interlaced input becomes 720x480 59.94 progressive images Test it out yourself on the the Bout branch ffmpeg -i "INPUT.VOB" -filter_complex "separatefields, shuffleframes=0 1 2 4 3 6 5 7 8 9, select=eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7), tinterlace, setsar=sar=8/9, bwdif=mode=send_field:deint=all, decimate=cycle=2" -an -c:v libx264 -crf 18 -t 00:00:10 bout.mkv -y Yes, I knew all that, and bwdif is doing that right thing given what it's told to do. What's wrong is with tinterlace. tinterlace is changing SAR from 8:9 to 16:9 before bwdif gets the stream. Adding setsar ahead of bwdif can change SAR back to 8:9, but it also changes DAR from 4:3 (which it should be) to 8:3 [note 1]. [note 1] setsar has no choice. For a 720x240 picture (i.e. PAR = 8:3), if it changes SAR from 16:9 (which is wrong) to 8:9 (which is right), then it has to change DAR from 4:3 (which is right) to 8:3 (which is wrong). The problem is with tinterlace. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". -- 17 Dec 2020 -- early in the 2nd wave of pandemic. Pfizer's 2nd dose in 21 days. Moderna's 2nd dose in 28 days. Yesterday's new cases, China: 12, S.Korea: 1,075, U.S.: 246,996. Yesterday's new deaths, China: 0, S.Korea: 12, U.S.: 3,486. Today, U.S.: 4% of world population, 23% of cases, 19% of deaths. Today, U.S. mortality: Of 10,485,312 resolved cases, 3% are dead. Today, U.S. dead, pandemic: 314,577 (11 mo.), WWII: 419,000 (47 mo.). 22 Jan: U.S. & S.Korea report 1st cases on the same day. 6 Mar, testing to date, S.Korea: 140,000, U.S.: 2000. 6 Mar, test results, S.Korea: 4 hours, U.S.: 1 to 2 weeks. 1 Jun, total care-home deaths, S.Korea: 0, U.S.: 33,000 +/- 7,000. 5 Aug, U.S. testing: only 1/4 of number needed; 4 day results. 1 Sep, Nursing Assoc report: Over 60% of U.S. nurses lack PPE. 18 Sep, U.S. doctors & nurses still acutely lack PPE; 1200 dead. 15 Oct, projected GDP, China: up 1.9%, U.S.: down 3.6%. 19 Oct, CDC report: U.S. test results still take 3 days, average. 12 Nov, National Nurses United: Over 80% of U.S. nurses lack PPE. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
Sorry, I made a typo... On 01/04/2021 03:52 PM, pdr0 wrote: Mark Filipak (ffmpeg) wrote You can't interleave images with different dimensions Aout has separated fields, to 720x240 , but Bout is 720x480 [Bout] is 720x240: I'm using 'mode=send_field' in 'bwdif=mode=send_field', and the following 'decimate' doesn't change that. The problem is that 'tinterleave' is marking the output as "SAR = 16:9" instead of "8:9" (which is what it should be and should never be changed). No, [Bout] is 720x480 bwdif in send_field mode means double rate deinterlacing. 720x480 59.94 fields per second interlaced input becomes 720x480 59.94 progressive images Test it out yourself on the the Bout branch ffmpeg -i "INPUT.VOB" -filter_complex "separatefields, shuffleframes=0 1 2 4 3 6 5 7 8 9, select=eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7), tinterlace, setsar=sar=8/9, bwdif=mode=send_field:deint=all, decimate=cycle=2" -an -c:v libx264 -crf 18 -t 00:00:10 bout.mkv -y Yes, I knew all that, and bwdif is doing that right thing given what it's told to do. What's wrong is with tinterlace. tinterlace is changing SAR from 8:9 to 16:9 before bwdif gets the stream. Adding setsar ahead of bwdif can change SAR back to 8:9, but it also changes DAR from 4:3 (which it should be) to 8:3 [note 1]. [note 1] setsar has no choice. For a 720x240 picture (i.e. PAR = 8:3), if it changes SAR from 16:9 (which is wrong) to 8:9 (which is right), then it has to change DAR from 4:3 (which is right) to 8:3 (which is wrong). The problem is with tinterlace. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
On 01/04/2021 03:52 PM, pdr0 wrote: Mark Filipak (ffmpeg) wrote You can't interleave images with different dimensions Aout has separated fields, to 720x240 , but Bout is 720x480 [Bout] is 720x240: I'm using 'mode=send_field' in 'bwdif=mode=send_field', and the following 'decimate' doesn't change that. The problem is that 'tinterleave' is marking the output as "SAR = 16:9" instead of "8:9" (which is what it should be and should never be changed). No, [Bout] is 720x480 bwdif in send_field mode means double rate deinterlacing. 720x480 59.94 fields per second interlaced input becomes 720x480 59.94 progressive images Test it out yourself on the the Bout branch ffmpeg -i "INPUT.VOB" -filter_complex "separatefields, shuffleframes=0 1 2 4 3 6 5 7 8 9, select=eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7), tinterlace, setsar=sar=8/9, bwdif=mode=send_field:deint=all, decimate=cycle=2" -an -c:v libx264 -crf 18 -t 00:00:10 bout.mkv -y Yes, I knew all that, and bwdif is doing that right thing given what it's told to do. What's wrong is with tinterlace. tinterlace is changing SAR from 8:9 to 16:9 before bwdif gets the stream. Adding setsar ahead of bwdif can change SAR back to 8:9, but it also changes DAR from 4:3 (which it should be) to 8:3 [note 1]. [note 1] setsar has no choice. For a 720x240 picture (i.e. PAR = 6:3), if it changes SAR from 16:9 (which is wrong) to 8:9 (which is right), then it has to change DAR from 4:3 (which is right) to 8:3 (which is wrong). The problem is with tinterlace. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
Mark Filipak (ffmpeg) wrote > >> >> You can't interleave images with different dimensions >> >> Aout has separated fields, to 720x240 , but Bout is 720x480 > > [Bout] is 720x240: I'm using 'mode=send_field' in 'bwdif=mode=send_field', > and the following > 'decimate' doesn't change that. The problem is that 'tinterleave' is > marking the output as "SAR = > 16:9" instead of "8:9" (which is what it should be and should never be > changed). No, [Bout] is 720x480 bwdif in send_field mode means double rate deinterlacing. 720x480 59.94 fields per second interlaced input becomes 720x480 59.94 progressive images Test it out yourself on the the Bout branch ffmpeg -i "INPUT.VOB" -filter_complex "separatefields, shuffleframes=0 1 2 4 3 6 5 7 8 9, select=eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7), tinterlace, setsar=sar=8/9, bwdif=mode=send_field:deint=all, decimate=cycle=2" -an -c:v libx264 -crf 18 -t 00:00:10 bout.mkv -y -- Sent from: http://www.ffmpeg-archive.org/ ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
On Mon, Jan 4, 2021 at 9:21 PM Mark Filipak (ffmpeg) wrote: > On 01/04/2021 02:45 PM, pdr0 wrote: > > Mark Filipak (ffmpeg) wrote > >> > >> You wrote: "What's wrong with using setsar filter after tinterlace?" > >> > >> I tried that from the git-go. I just reran it. > >> > >> ffmpeg -report -i "source 720x480 [SAR 8x9 DAR 4x3] 29.97 fps.VOB" > >> -filter_complex "separatefields, > >> shuffleframes=0 1 2 4 3 6 5 7 8 9, split[Ain][Bin], > >> > [Ain]select=not(eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7))[Aout], > >> > [Bin]select=eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7), > >> tinterlace, > >> setsar=sar=8/9, bwdif=mode=send_field:deint=all, decimate=cycle=2[Bout], > >> [Aout][Bout]interleave, > >> tinterlace, setsar=sar=8/9, bwdif=mode=send_frame:deint=interlaced" > >> -codec:a copy -codec:s copy -dn > >> output.mkv > >> > >> Putting setsar after tinterlace doesn't work. I did investigate that > but I > >> can't recall why -- I > >> think it's because DAR is then wrong. The report is below. > > > > > > You can't interleave images with different dimensions > > > > Aout has separated fields, to 720x240 , but Bout is 720x480 > > [Bout] is 720x240: I'm using 'mode=send_field' in 'bwdif=mode=send_field', > and the following > 'decimate' doesn't change that. The problem is that 'tinterleave' is > marking the output as "SAR = > 16:9" instead of "8:9" (which is what it should be and should never be > changed). > > SAR cannot change unless DAR/PAR changes (which it doesn't). Look: > > SAR = DAR/PAR = (8:3)/(720:240) = (8:3)/(6:2) = 8:9 > SAR = DAR/PAR = (4:3)/(720:480) = (4:3)/(3:2) = 8:9 > > The current tinterlace filter is setting SAR = 16:9. That is just plain > wrong. > That is just invalid statement. > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
On 01/04/2021 02:45 PM, pdr0 wrote: Mark Filipak (ffmpeg) wrote You wrote: "What's wrong with using setsar filter after tinterlace?" I tried that from the git-go. I just reran it. ffmpeg -report -i "source 720x480 [SAR 8x9 DAR 4x3] 29.97 fps.VOB" -filter_complex "separatefields, shuffleframes=0 1 2 4 3 6 5 7 8 9, split[Ain][Bin], [Ain]select=not(eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7))[Aout], [Bin]select=eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7), tinterlace, setsar=sar=8/9, bwdif=mode=send_field:deint=all, decimate=cycle=2[Bout], [Aout][Bout]interleave, tinterlace, setsar=sar=8/9, bwdif=mode=send_frame:deint=interlaced" -codec:a copy -codec:s copy -dn output.mkv Putting setsar after tinterlace doesn't work. I did investigate that but I can't recall why -- I think it's because DAR is then wrong. The report is below. You can't interleave images with different dimensions Aout has separated fields, to 720x240 , but Bout is 720x480 [Bout] is 720x240: I'm using 'mode=send_field' in 'bwdif=mode=send_field', and the following 'decimate' doesn't change that. The problem is that 'tinterleave' is marking the output as "SAR = 16:9" instead of "8:9" (which is what it should be and should never be changed). SAR cannot change unless DAR/PAR changes (which it doesn't). Look: SAR = DAR/PAR = (8:3)/(720:240) = (8:3)/(6:2) = 8:9 SAR = DAR/PAR = (4:3)/(720:480) = (4:3)/(3:2) = 8:9 The current tinterlace filter is setting SAR = 16:9. That is just plain wrong. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
Mark Filipak (ffmpeg) wrote > > You wrote: "What's wrong with using setsar filter after tinterlace?" > > I tried that from the git-go. I just reran it. > > ffmpeg -report -i "source 720x480 [SAR 8x9 DAR 4x3] 29.97 fps.VOB" > -filter_complex "separatefields, > shuffleframes=0 1 2 4 3 6 5 7 8 9, split[Ain][Bin], > [Ain]select=not(eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7))[Aout], > > [Bin]select=eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7), > tinterlace, > setsar=sar=8/9, bwdif=mode=send_field:deint=all, decimate=cycle=2[Bout], > [Aout][Bout]interleave, > tinterlace, setsar=sar=8/9, bwdif=mode=send_frame:deint=interlaced" > -codec:a copy -codec:s copy -dn > output.mkv > > Putting setsar after tinterlace doesn't work. I did investigate that but I > can't recall why -- I > think it's because DAR is then wrong. The report is below. You can't interleave images with different dimensions Aout has separated fields, to 720x240 , but Bout is 720x480 Possibly you want to apply separatefields again before Bout -- Sent from: http://www.ffmpeg-archive.org/ ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
Paul, I apologize for not responding. The ffmpeg-user list server did not send your 2 responses to me -- I checked gmail and they're not there either. I discovered them in the archive: https://lists.ffmpeg.org/pipermail/ffmpeg-user/2021-January/051249.html https://lists.ffmpeg.org/pipermail/ffmpeg-user/2021-January/051250.html I don't know how to get the list server to resend them, so I can't properly respond, so my reponses are out of thread sequence. I'm sorry about that but it seems there's nothing I can do about it. = You wrote: "What's wrong with using setsar filter after tinterlace?" I tried that from the git-go. I just reran it. ffmpeg -report -i "source 720x480 [SAR 8x9 DAR 4x3] 29.97 fps.VOB" -filter_complex "separatefields, shuffleframes=0 1 2 4 3 6 5 7 8 9, split[Ain][Bin], [Ain]select=not(eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7))[Aout], [Bin]select=eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7), tinterlace, setsar=sar=8/9, bwdif=mode=send_field:deint=all, decimate=cycle=2[Bout], [Aout][Bout]interleave, tinterlace, setsar=sar=8/9, bwdif=mode=send_frame:deint=interlaced" -codec:a copy -codec:s copy -dn output.mkv Putting setsar after tinterlace doesn't work. I did investigate that but I can't recall why -- I think it's because DAR is then wrong. The report is below. = You wrote: "Also you can use weave filter as alternative to tinterlace=merge" I tried that also. I just reran it. ffmpeg -report -i "source 720x480 [SAR 8x9 DAR 4x3] 29.97 fps.VOB" -filter_complex "separatefields, shuffleframes=0 1 2 4 3 6 5 7 8 9, split[Ain][Bin], [Ain]select=not(eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7))[Aout], [Bin]select=eq(mod(n\,10)\,2)+eq(mod(n\,10)\,3)+eq(mod(n\,10)\,6)+eq(mod(n\,10)\,7), weave, bwdif=mode=send_field:deint=all, decimate=cycle=2[Bout], [Aout][Bout]interleave, weave, bwdif=mode=send_frame:deint=interlaced" -codec:a copy -codec:s copy -dn output.mkv = I'm unsure what the reports are reporting: "Parameters for input link input1 (size 720x480, SAR 8:9) do not match the corresponding output link parameters (720x240, SAR 8:9)". Either tinterlace or weave should take in 720x240 and ouput 720x480 but the report line above seems to imply the opposite. = REPORTS BEGIN HERE = ADDING setsar = ffmpeg started on 2021-01-04 at 13:16:19 Report written to "ffmpeg-20210104-131619.log" Log level: 48 Command line: ffmpeg -report -i "source 720x480 [SAR 8x9 DAR 4x3] 29.97 fps.VOB" -filter_complex "separatefields, shuffleframes=0 1 2 4 3 6 5 7 8 9, split[Ain][Bin], [Ain]select=not(eq(mod(n\\,10)\\,2)+eq(mod(n\\,10)\\,3)+eq(mod(n\\,10)\\,6)+eq(mod(n\\,10)\\,7))[Aout], [Bin]select=eq(mod(n\\,10)\\,2)+eq(mod(n\\,10)\\,3)+eq(mod(n\\,10)\\,6)+eq(mod(n\\,10)\\,7), tinterlace, setsar=sar=8/9, bwdif=mode=send_field:deint=all, decimate=cycle=2[Bout], [Aout][Bout]interleave, tinterlace, setsar=sar=8/9, bwdif=mode=send_frame:deint=interlaced" -codec:a copy -codec:s copy -dn output.mkv ffmpeg version N-100546-g2c6f532e0a Copyright (c) 2000-2021 the FFmpeg developers built with gcc 9.3-win32 (GCC) 20200320 configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64 --target-os=mingw32 --enable-gpl --enable-version3 --disable-debug --disable-w32threads --enable-pthreads --enable-iconv --enable-zlib --enable-libxml2 --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-opencl --enable-libvmaf --enable-vulkan --enable-libvorbis --enable-amf --enable-libaom --enable-avisynth --enable-libdav1d --enable-libdavs2 --enable-ffnvcodec --enable-cuda-llvm --enable-libglslang --enable-libass --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvpx --enable-libwebp --enable-libmfx --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librav1e --enable-librubberband --enable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --enable-libvidstab --enable-libx264 --enable-libx26 libavutil 56. 63.100 / 56. 63.100 libavcodec 58.115.102 / 58.115.102 libavformat58. 65.100 / 58. 65.100 libavdevice58. 11.103 / 58. 11.103 libavfilter 7. 95.100 / 7. 95.100 libswscale 5. 8.100 / 5. 8.100 libswresample 3. 8.100 / 3. 8.100 libpostproc55. 8.100 / 55. 8.100 Splitting the commandline. Reading option '-report' ... matched as option 'report' (generate a report) with argument '1'. Reading option '-i' ... matched as input url with argument 'source 720x480 [SAR 8x9 DAR 4x3] 29.97 fps.VOB'. Reading option '-filter_complex' ... matched as option 'filter_complex' (create a complex filtergraph) with argument 'separatefields, shuffleframes=0 1 2 4 3 6 5 7 8 9, split[Ain][Bin], [Ain]select=not(eq(mod
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
UPDATE I tested all possible combinations based on my filter complex. I renamed 2 particular outputs of interest: separatefields+shuffleframes+select.mkv separatefields+shuffleframes+select+tinterlace.mkv to indicate the result of ffprobe: separatefields+shuffleframes+select 720x240 [SAR 8x9 DAR 8x3] 59.94 fps.mkv separatefields+shuffleframes+select+tinterlace 720x480 [SAR 16x9 DAR 8x3] 29.97 fps.mkv If SAR had not been doubled, then, according to theory, DAR = PAR * SAR = 720:480 * 8:9 = 3:2 * 8:9 = 4:3. That is ordinary i30. That is what it should be at that point: separatefields ... tinterlace. Paul, why does tinterlace change SAR to 16:9? On 01/03/2021 03:22 PM, Mark Filipak (ffmpeg) wrote: On 01/03/2021 10:24 AM, Paul B Mahol wrote: On Sun, Jan 3, 2021 at 11:45 AM Mark Filipak (ffmpeg) wrote: Version N-100546-g2c6f532e0a (latest git build) Summary of the bug: tinterlace works but sets SAR & DAR to bogus values. The package is here: https://www.dropbox.com/t/0WABzvetTF1eT7E4 Everything needed to reproduce and source video and my result and log are in the package. The change of sar is intended behavior. Okay. Given this: ffmpeg -report -i source.mkv -vf "tinterlace=mode=merge" -c:a copy -c:s copy -dn tinterlace.mkv where source.mpv is this: "Input #0, matroska,webm, from 'source.mkv': " Metadata: " ENCODER : Lavf58.65.100 " Duration: 00:00:01.00, start: 0.00, bitrate: 857 kb/s " Stream #0:0, 4, 1/1000: Video: h264 (High), yuv420p(tv, smpte170m, progressive), 720x240 [SAR 8:9 DAR 8:3], 59.94 fps, 59.94 tbr, 1k tbn, 119.88 tbc (default)" tinterlace.mkv should be this: 720x480 [SAR 8:9 DAR 4:3] but instead is this: "Output #0, matroska, to 'tinterlace.mkv': " Metadata: " encoder : Lavf58.65.100 " Stream #0:0, 0, 1/1000: Video: h264 (H264 / 0x34363248), yuv420p(tv, smpte170m, top coded first (swapped)), 720x480 [SAR 16:9 DAR 8:3], q=2-31, 29.97 fps, 1k tbn (default)" The discrepancy appears to be causing problems with succeeding filters: "[Parsed_interleave_7 @ 0170340dc000] Parameters for input link input1 (size 720x480, SAR 16:9) do not match the corresponding output link parameters (720x240, SAR 8:9) "[Parsed_interleave_7 @ 0170340dc000] Failed to configure output pad on Parsed_interleave_7 "Error reinitializing filters! "Failed to inject frame into filter network: Invalid argument "Error while processing the decoded data for stream #0:0 "Conversion failed!" The succeeding filters are shuffleframes, split, select, tinterlace, bwdif, decimate, interleave, tinterlace, and bwdif. The problem appears to be provoked by interleave. I promise to follow this message with the full command line and full report if you promise not to ask me why I'm doing such seemingly crazy processing. :-) Honestly, I'm not trying to be coy. I'm simply trying to keep this use-case simple and prevent this thread from getting off topic. The problem appears to be with tinterlace's SAR. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
On Sun, Jan 3, 2021 at 9:28 PM Paul B Mahol wrote: > > > On Sun, Jan 3, 2021 at 9:25 PM Mark Filipak (ffmpeg) > wrote: > >> On 01/03/2021 10:24 AM, Paul B Mahol wrote: >> > On Sun, Jan 3, 2021 at 11:45 AM Mark Filipak (ffmpeg) < >> markfili...@bog.us> >> > wrote: >> > >> >> Version N-100546-g2c6f532e0a (latest git build) >> >> >> >> Summary of the bug: >> >> tinterlace works but sets SAR & DAR to bogus values. >> >> >> >> The package is here: >> >> https://www.dropbox.com/t/0WABzvetTF1eT7E4 >> >> >> >> Everything needed to reproduce and source video and my result and log >> are >> >> in the package. >> >> >> >> >> > The change of sar is intended behavior. >> >> Okay. >> Given this: >> ffmpeg -report -i source.mkv -vf "tinterlace=mode=merge" -c:a copy -c:s >> copy -dn tinterlace.mkv >> where source.mpv is this: >> "Input #0, matroska,webm, from 'source.mkv': >> " Metadata: >> "ENCODER : Lavf58.65.100 >> " Duration: 00:00:01.00, start: 0.00, bitrate: 857 kb/s >> "Stream #0:0, 4, 1/1000: Video: h264 (High), yuv420p(tv, smpte170m, >> progressive), 720x240 [SAR >> 8:9 DAR 8:3], 59.94 fps, 59.94 tbr, 1k tbn, 119.88 tbc (default)" >> >> tinterlace.mkv should be this: 720x480 [SAR 8:9 DAR 4:3] >> but instead is this: >> "Output #0, matroska, to 'tinterlace.mkv': >> " Metadata: >> "encoder : Lavf58.65.100 >> "Stream #0:0, 0, 1/1000: Video: h264 (H264 / 0x34363248), yuv420p(tv, >> smpte170m, top coded first >> (swapped)), 720x480 [SAR 16:9 DAR 8:3], q=2-31, 29.97 fps, 1k tbn >> (default)" >> >> The discrepancy appears to be causing problems with succeeding filters: >> "[Parsed_interleave_7 @ 0170340dc000] Parameters for input link >> input1 (size 720x480, SAR 16:9) >> do not match the corresponding output link parameters (720x240, SAR 8:9) >> "[Parsed_interleave_7 @ 0170340dc000] Failed to configure output pad >> on Parsed_interleave_7 >> "Error reinitializing filters! >> "Failed to inject frame into filter network: Invalid argument >> "Error while processing the decoded data for stream #0:0 >> "Conversion failed!" >> >> The succeeding filters are shuffleframes, split, select, tinterlace, >> bwdif, decimate, interleave, >> tinterlace, and bwdif. The problem appears to be provoked by interleave. >> > > What's wrong with using setsar filter after tinterlace? > Also you can use weave filter as alternative to tinterlace=merge > >> >> I promise to follow this message with the full command line and full >> report if you promise not to >> ask me why I'm doing such seemingly crazy processing. :-) >> >> Honestly, I'm not trying to be coy. I'm simply trying to keep this >> use-case simple and prevent this >> thread from getting off topic. The problem appears to be with >> tinterlace's SAR. >> >> Regards, >> Mark. >> ___ >> ffmpeg-user mailing list >> ffmpeg-user@ffmpeg.org >> https://ffmpeg.org/mailman/listinfo/ffmpeg-user >> >> To unsubscribe, visit link above, or email >> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > > ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
On Sun, Jan 3, 2021 at 9:25 PM Mark Filipak (ffmpeg) wrote: > On 01/03/2021 10:24 AM, Paul B Mahol wrote: > > On Sun, Jan 3, 2021 at 11:45 AM Mark Filipak (ffmpeg) < > markfili...@bog.us> > > wrote: > > > >> Version N-100546-g2c6f532e0a (latest git build) > >> > >> Summary of the bug: > >> tinterlace works but sets SAR & DAR to bogus values. > >> > >> The package is here: > >> https://www.dropbox.com/t/0WABzvetTF1eT7E4 > >> > >> Everything needed to reproduce and source video and my result and log > are > >> in the package. > >> > >> > > The change of sar is intended behavior. > > Okay. > Given this: > ffmpeg -report -i source.mkv -vf "tinterlace=mode=merge" -c:a copy -c:s > copy -dn tinterlace.mkv > where source.mpv is this: > "Input #0, matroska,webm, from 'source.mkv': > " Metadata: > "ENCODER : Lavf58.65.100 > " Duration: 00:00:01.00, start: 0.00, bitrate: 857 kb/s > "Stream #0:0, 4, 1/1000: Video: h264 (High), yuv420p(tv, smpte170m, > progressive), 720x240 [SAR > 8:9 DAR 8:3], 59.94 fps, 59.94 tbr, 1k tbn, 119.88 tbc (default)" > > tinterlace.mkv should be this: 720x480 [SAR 8:9 DAR 4:3] > but instead is this: > "Output #0, matroska, to 'tinterlace.mkv': > " Metadata: > "encoder : Lavf58.65.100 > "Stream #0:0, 0, 1/1000: Video: h264 (H264 / 0x34363248), yuv420p(tv, > smpte170m, top coded first > (swapped)), 720x480 [SAR 16:9 DAR 8:3], q=2-31, 29.97 fps, 1k tbn > (default)" > > The discrepancy appears to be causing problems with succeeding filters: > "[Parsed_interleave_7 @ 0170340dc000] Parameters for input link input1 > (size 720x480, SAR 16:9) > do not match the corresponding output link parameters (720x240, SAR 8:9) > "[Parsed_interleave_7 @ 0170340dc000] Failed to configure output pad > on Parsed_interleave_7 > "Error reinitializing filters! > "Failed to inject frame into filter network: Invalid argument > "Error while processing the decoded data for stream #0:0 > "Conversion failed!" > > The succeeding filters are shuffleframes, split, select, tinterlace, > bwdif, decimate, interleave, > tinterlace, and bwdif. The problem appears to be provoked by interleave. > What's wrong with using setsar filter after tinterlace? > > I promise to follow this message with the full command line and full > report if you promise not to > ask me why I'm doing such seemingly crazy processing. :-) > > Honestly, I'm not trying to be coy. I'm simply trying to keep this > use-case simple and prevent this > thread from getting off topic. The problem appears to be with tinterlace's > SAR. > > Regards, > Mark. > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
On 01/03/2021 10:24 AM, Paul B Mahol wrote: On Sun, Jan 3, 2021 at 11:45 AM Mark Filipak (ffmpeg) wrote: Version N-100546-g2c6f532e0a (latest git build) Summary of the bug: tinterlace works but sets SAR & DAR to bogus values. The package is here: https://www.dropbox.com/t/0WABzvetTF1eT7E4 Everything needed to reproduce and source video and my result and log are in the package. The change of sar is intended behavior. Okay. Given this: ffmpeg -report -i source.mkv -vf "tinterlace=mode=merge" -c:a copy -c:s copy -dn tinterlace.mkv where source.mpv is this: "Input #0, matroska,webm, from 'source.mkv': " Metadata: "ENCODER : Lavf58.65.100 " Duration: 00:00:01.00, start: 0.00, bitrate: 857 kb/s "Stream #0:0, 4, 1/1000: Video: h264 (High), yuv420p(tv, smpte170m, progressive), 720x240 [SAR 8:9 DAR 8:3], 59.94 fps, 59.94 tbr, 1k tbn, 119.88 tbc (default)" tinterlace.mkv should be this: 720x480 [SAR 8:9 DAR 4:3] but instead is this: "Output #0, matroska, to 'tinterlace.mkv': " Metadata: "encoder : Lavf58.65.100 "Stream #0:0, 0, 1/1000: Video: h264 (H264 / 0x34363248), yuv420p(tv, smpte170m, top coded first (swapped)), 720x480 [SAR 16:9 DAR 8:3], q=2-31, 29.97 fps, 1k tbn (default)" The discrepancy appears to be causing problems with succeeding filters: "[Parsed_interleave_7 @ 0170340dc000] Parameters for input link input1 (size 720x480, SAR 16:9) do not match the corresponding output link parameters (720x240, SAR 8:9) "[Parsed_interleave_7 @ 0170340dc000] Failed to configure output pad on Parsed_interleave_7 "Error reinitializing filters! "Failed to inject frame into filter network: Invalid argument "Error while processing the decoded data for stream #0:0 "Conversion failed!" The succeeding filters are shuffleframes, split, select, tinterlace, bwdif, decimate, interleave, tinterlace, and bwdif. The problem appears to be provoked by interleave. I promise to follow this message with the full command line and full report if you promise not to ask me why I'm doing such seemingly crazy processing. :-) Honestly, I'm not trying to be coy. I'm simply trying to keep this use-case simple and prevent this thread from getting off topic. The problem appears to be with tinterlace's SAR. Regards, Mark. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] tinterlace broken - SAR & DAR wrong
On Sun, Jan 3, 2021 at 11:45 AM Mark Filipak (ffmpeg) wrote: > Version N-100546-g2c6f532e0a (latest git build) > > Summary of the bug: > tinterlace works but sets SAR & DAR to bogus values. > > The package is here: > https://www.dropbox.com/t/0WABzvetTF1eT7E4 > > Everything needed to reproduce and source video and my result and log are > in the package. > > The change of sar is intended behavior. > Thank you, > Mark. > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
