Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Ulf Zibis
Am 19.07.19 um 15:58 schrieb Stéphane Chauveau: > > You don't get it. The problem is not that you need a better formula. > The problem is that some values such as  10.2 cannot be exactly > represented using floating point values. > > For example, let's consider a few examples using the printf

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Ulf Zibis
Am 19.07.19 um 15:51 schrieb Paul B Mahol: > Really hard to guess something when there is missing information in chain. Hm, which information is missing in my chain from Fri, 19 Jul 2019 01:21:54 +0300 (EEST) -Ulf ___ ffmpeg-user mailing list

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Paul B Mahol
On 7/19/19, Ulf Zibis wrote: > > Am 19.07.19 um 11:33 schrieb Ulf Zibis: >> >> [.] >> >> For the 1st catched frame there is "next_dts_time:10.24" and >> "next_pts_time:10.16". So how can I be sure, that this is the >> corresponding frame to the output of my filter? : >>

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Stéphane Chauveau
On 7/19/19 3:16 PM, Ulf Zibis wrote: Using eq() on floating points is indeed a bad idea because of floating point rounding. In the code of the select filter I've found: #define TS2D(ts) ((ts) == AV_NOPTS_VALUE ? NAN : (double)(ts))     select->var_values[VAR_T  ] = TS2D(frame->pts) *

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Ulf Zibis
Am 19.07.19 um 13:28 schrieb Moritz Barsnick: > On Fri, Jul 19, 2019 at 13:24:58 +0200, Ulf Zibis wrote: >> frames but I meant a random collection such as: >> >> "select='eq(t\,10.16\,10.2\,10.24\,15.16\,100.5)'" > Ah, sorry. A list operator. No, no such support. So what would you  think on ..

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Ulf Zibis
Am 19.07.19 um 11:22 schrieb Stéphane Chauveau: > On 7/19/19 9:18 AM, Moritz Barsnick wrote: >> On Fri, Jul 19, 2019 at 00:21:53 +0200, Ulf Zibis wrote: >>> ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf >>>

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Moritz Barsnick
On Fri, Jul 19, 2019 at 13:24:58 +0200, Ulf Zibis wrote: > frames but I meant a random collection such as: > > "select='eq(t\,10.16\,10.2\,10.24\,15.16\,100.5)'" Ah, sorry. A list operator. No, no such support. Moritz ___ ffmpeg-user mailing list

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Ulf Zibis
Am 19.07.19 um 13:03 schrieb Moritz Barsnick: > On Fri, Jul 19, 2019 at 12:11:15 +0200, Ulf Zibis wrote: >> Wouldn't it be comfortable to allow a syntax like >> "select='eq(t\,10.16\,10.2\,10.24)'" to select a collection of frames? > That's what Stephance suggested: > >> So my advice is to add a

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Nicolas George
Moritz Barsnick (12019-07-19): > I'm not sure whether expressions actually work with string values, > though. The expression parser is very limited and hard to extend. Furthermore, its API is very inconvenient. If somebody were to rewrite it from scratch, it would be a great progress. (But do not

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Moritz Barsnick
On Fri, Jul 19, 2019 at 12:11:15 +0200, Ulf Zibis wrote: > Wouldn't it be comfortable to allow a syntax like > "select='eq(t\,10.16\,10.2\,10.24)'" to select a collection of frames? That's what Stephance suggested: > So my advice is to add a 3rd digit to your time values and to replace, for >

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Ulf Zibis
Am 19.07.19 um 00:21 schrieb Ulf Zibis: > Hi, > > my command is: > ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf >

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Ulf Zibis
Am 19.07.19 um 11:22 schrieb Stéphane Chauveau: > On 7/19/19 9:18 AM, Moritz Barsnick wrote: >> On Fri, Jul 19, 2019 at 00:21:53 +0200, Ulf Zibis wrote: >>> ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf >>>

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Ulf Zibis
Am 19.07.19 um 09:18 schrieb Moritz Barsnick: > On Fri, Jul 19, 2019 at 00:21:53 +0200, Ulf Zibis wrote: >> ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf >>

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Ulf Zibis
Am 19.07.19 um 08:30 schrieb Carl Eugen Hoyos: > Am Fr., 19. Juli 2019 um 00:22 Uhr schrieb Ulf Zibis : > >> my command is: >> ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 > If you want support on this mailing list, do not use -v warning > and post the command line together with the

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Stéphane Chauveau
On 7/19/19 9:18 AM, Moritz Barsnick wrote: On Fri, Jul 19, 2019 at 00:21:53 +0200, Ulf Zibis wrote: ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Moritz Barsnick
On Fri, Jul 19, 2019 at 00:21:53 +0200, Ulf Zibis wrote: > ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf >

Re: [FFmpeg-user] missing a selected frame

2019-07-19 Thread Carl Eugen Hoyos
Am Fr., 19. Juli 2019 um 00:22 Uhr schrieb Ulf Zibis : > my command is: > ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 If you want support on this mailing list, do not use -v warning and post the command line together with the complete, uncut console output. In this case, you may want to

[FFmpeg-user] missing a selected frame

2019-07-18 Thread Ulf Zibis
Hi, my command is: ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf select='eq(t\,10.16)+eq(t\,10.2)+eq(t\,10.24)+eq(t\,10.28)+eq(t\,10.32)+eq(t\,10.36)+eq(t\,10.4)+eq(t\,10.44)+eq(t\,17.52)+eq(t\,47.96)+eq(t\,49.08)+eq(t\,49.2)+eq(t\,55.72)+eq(t\,83.0)' -q 5 -c:a copy -vsync vfr