On Sat, Aug 25, 2018 at 03:30:48PM +0200, Marton Balint wrote:
>
>
> On Sat, 25 Aug 2018, Michael Niedermayer wrote:
>
> >On Fri, Aug 24, 2018 at 04:33:18PM -0300, James Almer wrote:
> >>On 8/24/2018 3:56 PM, Devin Heitmueller wrote:
> >>>Create a new av_get_frame_filename3() API which is just l
On 8/25/2018 10:30 AM, Marton Balint wrote:
>
>
> On Sat, 25 Aug 2018, Michael Niedermayer wrote:
>
>> On Fri, Aug 24, 2018 at 04:33:18PM -0300, James Almer wrote:
>>> On 8/24/2018 3:56 PM, Devin Heitmueller wrote:
Create a new av_get_frame_filename3() API which is just like the
previo
On Sat, 25 Aug 2018, Michael Niedermayer wrote:
On Fri, Aug 24, 2018 at 04:33:18PM -0300, James Almer wrote:
On 8/24/2018 3:56 PM, Devin Heitmueller wrote:
Create a new av_get_frame_filename3() API which is just like the
previous version but accepts a 64-bit integer for the "number"
argument
On Fri, Aug 24, 2018 at 04:33:18PM -0300, James Almer wrote:
> On 8/24/2018 3:56 PM, Devin Heitmueller wrote:
> > Create a new av_get_frame_filename3() API which is just like the
> > previous version but accepts a 64-bit integer for the "number"
> > argument. This is useful in cases where you want
On 8/24/2018 3:56 PM, Devin Heitmueller wrote:
> Create a new av_get_frame_filename3() API which is just like the
> previous version but accepts a 64-bit integer for the "number"
> argument. This is useful in cases where you want to put the
> original PTS into the filename (which can be larger tha
Create a new av_get_frame_filename3() API which is just like the
previous version but accepts a 64-bit integer for the "number"
argument. This is useful in cases where you want to put the
original PTS into the filename (which can be larger than 32-bits).
Tested with:
./ffmpeg -copyts -vsync 0 -i
