Re: [FFmpeg-user] minterpolate ...for Paul
On Sat, Jan 30, 2021 at 1:02 AM Mark Filipak (ffmpeg) wrote: > On 01/29/2021 07:10 PM, Carl Eugen Hoyos wrote: > > Am Sa., 30. Jan. 2021 um 01:00 Uhr schrieb Mark Filipak (ffmpeg) > > : > > > >> I don't know what you mean by "This does not look like the input file > from your command line" > > > > I meant that you provided the output file but you should (always) provide > > the input file. The output file is very, very rarely useful. > > > > Carl Eugen > > Wait, let me get this right... > > "This does not look like the input file from your command line" is your > way of saying "you should > (always) provide the input file"? > > Can you see that providing such ...oblique? ...misleading? ...cryptic? > clues to what you actually > mean instead of providing straightforward statements ...Can you see that > that's going to confuse > people? ...Can you see that, when it becomes clear what you really mean, > it can cause people to > resent you? ...Can you see those things? > > No, he's trying to help and it's best to just post the input file. Your response here isn't helpful at all and it's kinda nasty. K ___ 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] minterpolate ...for Paul
Am Sa., 30. Jan. 2021 um 02:19 Uhr schrieb Mark Filipak (ffmpeg) : > Then you said that I should always submit the input > (which I eventually did). Sorry, I missed this: Where can I find the input file? Carl Eugen ___ 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] minterpolate ...for Paul
On Sat, Jan 30, 2021 at 11:46 AM Phil Rhodes via ffmpeg-user < ffmpeg-user@ffmpeg.org> wrote: > > > On Saturday, 30 January 2021, 08:24:10 GMT, Moritz Barsnick < > barsn...@gmx.net> wrote: > > Please don't throw dirt around here. Carl Eugen is trying to help. > > I think it's worth being clear that it sometimes isn't very easy to tell > whether Carl Eugen is trying to help. > Censor yourself out. > P > ___ > 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] minterpolate ...for Paul
On Saturday, 30 January 2021, 08:24:10 GMT, Moritz Barsnick wrote: > Please don't throw dirt around here. Carl Eugen is trying to help. I think it's worth being clear that it sometimes isn't very easy to tell whether Carl Eugen is trying to help. P ___ 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] minterpolate ...for Paul
On Fri, Jan 29, 2021 at 20:16:12 -0500, Mark Filipak (ffmpeg) wrote: > Carl Eugen, it appears you're sniping at me. It appears you're throwing dirt > in the air in the hope that some of it will land on me. It appears that > you're trying to discredit me. Carl Eugen, the dirt lands on both of us. Carl Eugen wrote: > Command line, complete, uncut console output and an input file missing. You provided a link to a file: > https://www.dropbox.com/t/8sKE0jEguUxQgPjD Carl Eugen noticed: > This does not look like the input file from your command line. and you claimed: > Well, it is. Now you say that a) it wasn't obvious to you that the input file was required, and b) it wasn't the input file after all. Please don't throw dirt around here. Carl Eugen is trying to help. Moritz ___ 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] minterpolate ...for Paul
On 01/29/2021 07:10 PM, Carl Eugen Hoyos wrote: Am Sa., 30. Jan. 2021 um 01:00 Uhr schrieb Mark Filipak (ffmpeg) : I don't know what you mean by "This does not look like the input file from your command line" I meant that you provided the output file but you should (always) provide the input file. The output file is very, very rarely useful. Carl Eugen You questioned that the input for minterpolate.mkv was the same input that I posted. Then you contested my assurances that it was. Then you said that I should always submit the input (which I eventually did). In this case, it's the output that shows strangeness in the macroblocks and the input would be useless, but no matter. Carl Eugen, it appears you're sniping at me. It appears you're throwing dirt in the air in the hope that some of it will land on me. It appears that you're trying to discredit me. Carl Eugen, the dirt lands on both of us. ___ 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] minterpolate ...for Paul
On 01/29/2021 07:10 PM, Carl Eugen Hoyos wrote: Am Sa., 30. Jan. 2021 um 01:00 Uhr schrieb Mark Filipak (ffmpeg) : I don't know what you mean by "This does not look like the input file from your command line" I meant that you provided the output file but you should (always) provide the input file. The output file is very, very rarely useful. Carl Eugen Wait, let me get this right... "This does not look like the input file from your command line" is your way of saying "you should (always) provide the input file"? Can you see that providing such ...oblique? ...misleading? ...cryptic? clues to what you actually mean instead of providing straightforward statements ...Can you see that that's going to confuse people? ...Can you see that, when it becomes clear what you really mean, it can cause people to resent you? ...Can you see those things? ___ 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] minterpolate ...for Paul
Am Sa., 30. Jan. 2021 um 01:00 Uhr schrieb Mark Filipak (ffmpeg) : > I don't know what you mean by "This does not look like the input file from > your command line" I meant that you provided the output file but you should (always) provide the input file. The output file is very, very rarely useful. Carl Eugen ___ 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] minterpolate ...for Paul
On 01/29/2021 06:49 PM, Carl Eugen Hoyos wrote: Am Sa., 30. Jan. 2021 um 00:48 Uhr schrieb Mark Filipak (ffmpeg) : On 01/29/2021 04:49 PM, Carl Eugen Hoyos wrote: Am Do., 28. Jan. 2021 um 20:40 Uhr schrieb Mark Filipak (ffmpeg) : On 01/28/2021 02:05 AM, Carl Eugen Hoyos wrote: Am 28.01.2021 um 07:26 schrieb Mark Filipak (ffmpeg) : I'm seeing problems with minterpolate that manifest as occasional visual errors in particular areas. Command line, complete, uncut console output and an input file missing. Here's the video: https://www.dropbox.com/t/8sKE0jEguUxQgPjD This does not look like the input file from your command line. Well, it is. No. Carl Eugen For minterpolate.mkv, I did not provide the input file. In my last reply I said this: ffmpeg -i "source=24FPS.mkv" -map 0 -filter_complex "minterpolate=fps=6/1001:mi_mode=mci:mc_mode=obmc:scd=fdiff:scd_threshold=10:vsbmc=1:search_param=20" -codec:v libx265 -x265-params "crf=20:qcomp=0.60" -codec:a copy -codec:s copy minterpolate.mkv 'source=24FPS.mkv' == '24p-original (480 frames).mkv' I don't know what you mean by "This does not look like the input file from your command line" -- the name doesn't look the same or the video doesn't look the same? -- but it is the same input file. ___ 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] minterpolate ...for Paul
Am Sa., 30. Jan. 2021 um 00:48 Uhr schrieb Mark Filipak (ffmpeg) : > > On 01/29/2021 04:49 PM, Carl Eugen Hoyos wrote: > > Am Do., 28. Jan. 2021 um 20:40 Uhr schrieb Mark Filipak (ffmpeg) > > : > >> > >> On 01/28/2021 02:05 AM, Carl Eugen Hoyos wrote: > >>> > Am 28.01.2021 um 07:26 schrieb Mark Filipak (ffmpeg) > : > > I'm seeing problems with minterpolate that manifest as occasional visual > errors in particular areas. > >>> > >>> Command line, complete, uncut console output and an input file missing. > > > >> Here's the video: > >> > >> https://www.dropbox.com/t/8sKE0jEguUxQgPjD > > > > This does not look like the input file from your command line. > Well, it is. No. Carl Eugen ___ 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] minterpolate ...for Paul
On 01/29/2021 04:49 PM, Carl Eugen Hoyos wrote: Am Do., 28. Jan. 2021 um 20:40 Uhr schrieb Mark Filipak (ffmpeg) : On 01/28/2021 02:05 AM, Carl Eugen Hoyos wrote: Am 28.01.2021 um 07:26 schrieb Mark Filipak (ffmpeg) : I'm seeing problems with minterpolate that manifest as occasional visual errors in particular areas. Command line, complete, uncut console output and an input file missing. Here's the video: https://www.dropbox.com/t/8sKE0jEguUxQgPjD This does not look like the input file from your command line. Carl Eugen Well, it is. ffmpeg -i "source=24FPS.mkv" -map 0 -filter_complex "minterpolate=fps=6/1001:mi_mode=mci:mc_mode=obmc:scd=fdiff:scd_threshold=10:vsbmc=1:search_param=20" -codec:v libx265 -x265-params "crf=20:qcomp=0.60" -codec:a copy -codec:s copy minterpolate.mkv 'source=24FPS.mkv' == '24p-original (480 frames).mkv' I have several balls in the air. I rename files appropriate to my performance (my messages to user-ffmpeg and to various people who are not here). ___ 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] minterpolate ...for Paul
Am Do., 28. Jan. 2021 um 20:40 Uhr schrieb Mark Filipak (ffmpeg) : > > On 01/28/2021 02:05 AM, Carl Eugen Hoyos wrote: > > > >> Am 28.01.2021 um 07:26 schrieb Mark Filipak (ffmpeg) : > >> > >> I'm seeing problems with minterpolate that manifest as occasional visual > >> errors in particular areas. > > > > Command line, complete, uncut console output and an input file missing. > Here's the video: > > https://www.dropbox.com/t/8sKE0jEguUxQgPjD This does not look like the input file from your command line. Carl Eugen ___ 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] minterpolate ...for Paul
Hello administrators, please ban this corporate evangelist from here, thanks. On Fri, Jan 29, 2021 at 4:02 PM Phil Rhodes via ffmpeg-user < ffmpeg-user@ffmpeg.org> wrote: > >You can technically, but minterpolate is not very user friendly - It's > too> slow for real work and feedback, and you cannot keyframe the settings > on> different scenes very easily. It's barely usable unless you program > your own> GUI around libavfilter > Yes - this is somewhere that commandline tools tend to start to become > less suitable, when you can't really audition settings and evaluate > tradeoffs very easily. > If you have a problem you need to solve quickly, there is optical flow > interpolation in the free version of Resolve, with better optical flow > interpolation in the paid version, which might make life a bit easier. Much > of Resolve is multi-threaded and GPU-accelerated (I'm not completely sure > if the optical flow is, to be honest, but I'd be astounded if it wasn't) > and you can to tweak things visually for the best possible compromise. > Naturally if you're just tweaking around with ffmpeg for fun, fine. > P > ___ > 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] minterpolate ...for Paul
>You can technically, but minterpolate is not very user friendly - It's too> >slow for real work and feedback, and you cannot keyframe the settings on> >different scenes very easily. It's barely usable unless you program your own> >GUI around libavfilter Yes - this is somewhere that commandline tools tend to start to become less suitable, when you can't really audition settings and evaluate tradeoffs very easily. If you have a problem you need to solve quickly, there is optical flow interpolation in the free version of Resolve, with better optical flow interpolation in the paid version, which might make life a bit easier. Much of Resolve is multi-threaded and GPU-accelerated (I'm not completely sure if the optical flow is, to be honest, but I'd be astounded if it wasn't) and you can to tweak things visually for the best possible compromise. Naturally if you're just tweaking around with ffmpeg for fun, fine. P ___ 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] minterpolate ...for Paul
pdr0 wrote > More settings would help too - maybe you can improve the filter. I'll post > an example later similar to one posted by Mark, where it's "solvable" > using > other methods, but not using minterpolate. Minterpolate maxes out at a > block > size of 16, and that causes problems in that and similar examples, nor > does > it have internal pad options to improve motion vectors. Here are some test videos - https://www.mediafire.com/file/9inkxdvi8iuo5hi/interpolation_test_videos.zip/file I made a source video "interp_test_src.mp4" @23.976p which has simulated camera pan movement similar to Mark's example. "minterpolate_default.mp4" is the using the default settings . Similar artifacts along top and bottom of frame near the letterbox edge. Cropping and padding (both external to the filter) did not help much. Central portion along the windows have some bad areas in some frames too. Typical motion interpolation artifacts Test1_mvtools2 using typical settings (default blksize of 16) . Similar artifacts test2_mvtools2_nocrop_nopad has a blksize of 32, but no crop or pad internally. It's better in the central and top and bottom, but still some "edge dragging" artifacts Test2_mvtools2 has blksize of 32, is cropped and padded internally to improve motion vectors (this makes a difference along the frame borders along the letter box bars), then letterbox bars added back. This is much cleaner with only minor artifacting. This one would actually be usable by most people On this sequence, a larger blocksize of 32 helps with the central artifacts, and the and internal padding helps with frame edges for mvtools2. I suspect if minterpolate had options for larger blocksizes and internal padding it would improve too -- Sent from: http://ffmpeg-users.933282.n4.nabble.com/ ___ 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] minterpolate ...for Paul
Paul B Mahol wrote >> The problem is ffmpeg minterpolate is s slow, and you have no usable >> preview. Some of the other methods mentioned earlier do have previews - >> so >> you can tweak settings, preview, readjust etc >> >> > > Why you ignore fact that libavfilter also allows usable preview and > readjust of parameters. You can technically, but minterpolate is not very user friendly - It's too slow for real work and feedback, and you cannot keyframe the settings on different scenes very easily. It's barely usable unless you program your own GUI around libavfilter More settings would help too - maybe you can improve the filter. I'll post an example later similar to one posted by Mark, where it's "solvable" using other methods, but not using minterpolate. Minterpolate maxes out at a block size of 16, and that causes problems in that and similar examples, nor does it have internal pad options to improve motion vectors. -- Sent from: http://ffmpeg-users.933282.n4.nabble.com/ ___ 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] minterpolate ...for Paul
-- Sent from: http://ffmpeg-users.933282.n4.nabble.com/ ___ 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] minterpolate ...for Paul
On Fri, Jan 29, 2021 at 2:01 AM pdr0 wrote: > Mark Filipak (ffmpeg) wrote > > I've never heard of "optical flow errors". What could they be? (Got any > > links to > > explanations?) > > The artifacts in your video are optical flow errors :) > > If you've ever used it - you'd recognize these artifacts. There are very > common > > > > There are about a dozen prototypical "fail" categories or common errors > that > plague all types of optical flow > > These are errors either of motion vectors, or object flow (object > boundaries > or "masks"), occlusion errors. > > Internet is full of examples, explanations. The topic is rather large, just > search google, there is lots of info. If you have a specific question then > ask. > > Sometimes you get clean interpolated frame results; but sometimes there > are > massive distracting errors. It varies by situation and sources. > > Your example has one of the common categories of "fail" where there are > repeating patterns and textures. It falls under the "Picket Fence" fail . A > prototypical tracking or dolly shot by a picket fence, or brick wall will > come up with interpolation errors > > The peripheral edges error are common because there is less data beyond the > periphery of the frame, for n-1, n+1 and the motion vectors are less > accurate compared to the center of the frame > > Another common one is when objects pass over another. The flow masks aren't > perfect and you end up with blobby edge artifacts around objects > > > > > > > > >>...For artifacts around frame edges, letterbox edges usually some form > >> of padding is used. I don't think ffmpeg minterpolate has those. > > > > I've done that. The result was just okay. The slight riffling on the > frame > > boundaries during camera > > panning isn't all that objectionable to me. It occurs to me that > > minterpolute could queue frames and > > look 'forward' to later frames in order to resolve boundary macroblock > > artifacts -- afterall, it has > > the motion vectors, eh? > > Some algorithms can use N-3, N-2, N-1, N, N+1, N+2, N+3, I don't think > minterpolate can. More is not always better. Often you get more > contamination with a larger "window" > > Sometimes just changing the blocksize can produce better (or worse) > results. > The problem is ffmpeg minterpolate is s slow, and you have no usable > preview. Some of the other methods mentioned earlier do have previews - so > you can tweak settings, preview, readjust etc > > Why you ignore fact that libavfilter also allows usable preview and readjust of parameters. Amount of false information propagation here is astounding. > > > > > > > > > -- > Sent from: http://ffmpeg-users.933282.n4.nabble.com/ > ___ > 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] minterpolate ...for Paul
Mark Filipak (ffmpeg) wrote > I've never heard of "optical flow errors". What could they be? (Got any > links to > explanations?) The artifacts in your video are optical flow errors :) If you've ever used it - you'd recognize these artifacts. There are very common There are about a dozen prototypical "fail" categories or common errors that plague all types of optical flow These are errors either of motion vectors, or object flow (object boundaries or "masks"), occlusion errors. Internet is full of examples, explanations. The topic is rather large, just search google, there is lots of info. If you have a specific question then ask. Sometimes you get clean interpolated frame results; but sometimes there are massive distracting errors. It varies by situation and sources. Your example has one of the common categories of "fail" where there are repeating patterns and textures. It falls under the "Picket Fence" fail . A prototypical tracking or dolly shot by a picket fence, or brick wall will come up with interpolation errors The peripheral edges error are common because there is less data beyond the periphery of the frame, for n-1, n+1 and the motion vectors are less accurate compared to the center of the frame Another common one is when objects pass over another. The flow masks aren't perfect and you end up with blobby edge artifacts around objects >>...For artifacts around frame edges, letterbox edges usually some form >> of padding is used. I don't think ffmpeg minterpolate has those. > > I've done that. The result was just okay. The slight riffling on the frame > boundaries during camera > panning isn't all that objectionable to me. It occurs to me that > minterpolute could queue frames and > look 'forward' to later frames in order to resolve boundary macroblock > artifacts -- afterall, it has > the motion vectors, eh? Some algorithms can use N-3, N-2, N-1, N, N+1, N+2, N+3, I don't think minterpolate can. More is not always better. Often you get more contamination with a larger "window" Sometimes just changing the blocksize can produce better (or worse) results. The problem is ffmpeg minterpolate is s slow, and you have no usable preview. Some of the other methods mentioned earlier do have previews - so you can tweak settings, preview, readjust etc -- Sent from: http://ffmpeg-users.933282.n4.nabble.com/ ___ 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] minterpolate ...for Paul
On 01/28/2021 02:55 PM, pdr0 wrote: Mark Filipak (ffmpeg) wrote In the video, Look at the behavior of the dots on the gate behind the police here: 0:5.422 to 0:10.127. Look especially at the top of roof of the building here: 0:12.012 to 0:12.179, for apparent macroblock errors. Here's the video: https://www.dropbox.com/t/8sKE0jEguUxQgPjD Here's the command line: ffmpeg -i "source=24FPS.mkv" -map 0 -filter_complex "minterpolate=fps=6/1001:mi_mode=mci:mc_mode=obmc:scd=fdiff:scd_threshold=10:vsbmc=1:search_param=20" -codec:v libx265 -x265-params "crf=20:qcomp=0.60" -codec:a copy -codec:s copy minterpolate.mkv Those are not macroblock errors. They are typical optical flow errors... Thank you, pdr0. I've never heard of "optical flow errors". What could they be? (Got any links to explanations?) To me, the visual manifestation appears to be math errors inside the freshly interpolated macroblocks. The reason I 'say' that is because, though they appear to be sporadic, when a macroblock anomaly pops up, the effect is vary regular and persistent (not fleeting). In other words, the effect displays mathematical regularity. ... Motion interpolation is never perfect , there are always some types artifacts, occlusions, edge morphing Not with the regularity and persistence (longevity) I'm seeing. There are several other methods and algorithms you can use outside of FFmpeg, some are GPU accelerated. e.g. svpflow, mvtools2, DAIN, twixtor, resolve. ... Thanks. That gives me something specific for search. ...For artifacts around frame edges, letterbox edges usually some form of padding is used. I don't think ffmpeg minterpolate has those. I've done that. The result was just okay. The slight riffling on the frame boundaries during camera panning isn't all that objectionable to me. It occurs to me that minterpolute could queue frames and look 'forward' to later frames in order to resolve boundary macroblock artifacts -- afterall, it has the motion vectors, eh? That 'said', the slight riffling on the frame boundaries (example: At the end as the red tile tiles atop the wall come into view. If you slow the playback, it becomes quite evident that the same math errors are occurring there, but only sporadically, not constantly. Look at the offending macroblocks carefully. As the scene pans outside those macroblocks, the scene inside the macroblocks gets 'stuck'. Since there was no time restraint on transcode, the 'stuck' symptom must be math errors -- in the case of segmented (macroblock) issues, math controls the logic. ___ 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] minterpolate ...for Paul
Mark Filipak (ffmpeg) wrote > > In the video, > > Look at the behavior of the dots on the gate behind the police here: > 0:5.422 to 0:10.127. > > Look especially at the top of roof of the building here: 0:12.012 to > 0:12.179, for apparent > macroblock errors. > > Here's the video: > > https://www.dropbox.com/t/8sKE0jEguUxQgPjD > > Here's the command line: > > ffmpeg -i "source=24FPS.mkv" -map 0 -filter_complex > "minterpolate=fps=6/1001:mi_mode=mci:mc_mode=obmc:scd=fdiff:scd_threshold=10:vsbmc=1:search_param=20" > > -codec:v libx265 -x265-params "crf=20:qcomp=0.60" -codec:a copy -codec:s > copy minterpolate.mkv Those are not macroblock errors. They are typical optical flow errors. Motion interpolation is never perfect , there are always some types artifacts, occlusions, edge morphing There are several other methods and algorithms you can use outside of FFmpeg, some are GPU accelerated. e.g. svpflow, mvtools2, DAIN, twixtor, resolve. For artifacts around frame edges, letterbox edges usually some form of padding is used. I don't think ffmpeg minterpolate has those. -- Sent from: http://ffmpeg-users.933282.n4.nabble.com/ ___ 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] minterpolate ...for Paul
On 01/28/2021 02:05 AM, Carl Eugen Hoyos wrote:
Am 28.01.2021 um 07:26 schrieb Mark Filipak (ffmpeg) :
I'm seeing problems with minterpolate that manifest as occasional visual errors
in particular areas.
Command line, complete, uncut console output and an input file missing.
Carl Eugen
In the video,
Look at the behavior of the dots on the gate behind the police here: 0:5.422 to
0:10.127.
Look especially at the top of roof of the building here: 0:12.012 to 0:12.179, for apparent
macroblock errors.
Here's the video:
https://www.dropbox.com/t/8sKE0jEguUxQgPjD
Here's the command line:
ffmpeg -i "source=24FPS.mkv" -map 0 -filter_complex
"minterpolate=fps=6/1001:mi_mode=mci:mc_mode=obmc:scd=fdiff:scd_threshold=10:vsbmc=1:search_param=20"
-codec:v libx265 -x265-params "crf=20:qcomp=0.60" -codec:a copy -codec:s copy minterpolate.mkv
Here's the report:
ffmpeg started on 2021-01-27 at 19:04:32
Report written to "ffmpeg-20210127-190432.log"
Log level: 32
Command line:
ffmpeg -i "source=24FPS.mkv" -map 0 -filter_complex
"minterpolate=fps=6/1001:mi_mode=mci:mc_mode=obmc:scd=fdiff:scd_threshold=10:vsbmc=1:search_param=20"
-codec:v libx265 -x265-params "crf=20:qcomp=0.60" -codec:a copy -codec:s copy minterpolate.mkv
ffmpeg version N-100851-g9f38fac053 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. 64.100 / 56. 64.100
libavcodec 58.119.100 / 58.119.100
libavformat58. 65.101 / 58. 65.101
libavdevice58. 11.103 / 58. 11.103
libavfilter 7.100.100 / 7.100.100
libswscale 5. 8.100 / 5. 8.100
libswresample 3. 8.100 / 3. 8.100
libpostproc55. 8.100 / 55. 8.100
[matroska,webm @ 0224d68d6500] Could not find codec parameters for stream 3 (Subtitle:
hdmv_pgs_subtitle (pgssub)): unspecified size
Consider increasing the value for the 'analyzeduration' (0) and 'probesize'
(500) options
Input #0, matroska,webm, from 'source=24FPS.mkv':
Metadata:
encoder : libebml v1.4.0 + libmatroska v1.6.2
creation_time : 2021-01-23T03:12:17.00Z
Duration: 00:00:20.11, start: 0.00, bitrate: 26228 kb/s
Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9],
23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
Metadata:
BPS-eng : 24046529
DURATION-eng: 00:00:20.02000
NUMBER_OF_FRAMES-eng: 480
NUMBER_OF_BYTES-eng: 60176441
_STATISTICS_WRITING_APP-eng: mkvmerge v51.0.0 ('I Wish') 64-bit
_STATISTICS_WRITING_DATE_UTC-eng: 2021-01-23 03:12:17
_STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Stream #0:1(eng): Audio: dts (DTS-HD MA), 48000 Hz, stereo, s32p (24 bit)
(default)
Metadata:
BPS-eng : 2085565
DURATION-eng: 00:00:20.09600
NUMBER_OF_FRAMES-eng: 1884
NUMBER_OF_BYTES-eng: 5238940
_STATISTICS_WRITING_APP-eng: mkvmerge v51.0.0 ('I Wish') 64-bit
_STATISTICS_WRITING_DATE_UTC-eng: 2021-01-23 03:12:17
_STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Stream #0:2(eng): Audio: ac3, 48000 Hz, stereo, fltp, 192 kb/s
Metadata:
BPS-eng : 192000
DURATION-eng: 00:00:20.09600
NUMBER_OF_FRAMES-eng: 628
NUMBER_OF_BYTES-eng: 482304
_STATISTICS_WRITING_APP-eng: mkvmerge v51.0.0 ('I Wish') 64-bit
_STATISTICS_WRITING_DATE_UTC-eng: 2021-01-23 03:12:17
_STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Stream #0:3(eng): Subtitle: hdmv_pgs_subtitle
Metadata:
BPS-eng : 0
DURATION-eng: 00:00:00.0
NUMBER_OF_FRAMES-eng: 0
NUMBER_OF_BYTES-eng: 0
_STATISTICS_WRITING_APP-eng: mkvmerge v51.0.0 ('I Wish') 64-bit
_STATISTICS_WRITING_DATE_UTC-eng: 2021-01-23 03:12:17
_STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Re: [FFmpeg-user] minterpolate ...for Paul
> Am 28.01.2021 um 07:26 schrieb Mark Filipak (ffmpeg) : > > I'm seeing problems with minterpolate that manifest as occasional visual > errors in particular areas. Command line, complete, uncut console output and an input file missing. Carl Eugen ___ 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".
