[FFmpeg-user] forced-idr -- 3 more tired

[Mark Filipak]

On 11/07/2024 00.11, Gyan Doshi wrote:
> 
> 
> On 2024-07-11 03:09 am, Paul B Mahol wrote:
>> On Wed, Jul 10, 2024 at 11:18 PM Mark Filipak<markfilipak.imdb at gmail.com>
>> wrote:
>>
>>> On 10/07/2024 13.51, Will Boba wrote:
>>>> On 7/10/24 10:26, Mark Filipak wrote:
>>>>> Three more tried.
>>>>>
>>>>> ffmpeg -forced-idr 1 -i ... -c:v libx264 -an -sn -start_at_zero
>>> -muxdelay 0 ...
>>>>> [in#0 @ 0000000000542d00] Error opening input: Invalid data found when
>>> processing input
>>>>> ffmpeg -i ... -forced-idr 1 -c:v libx264 -an -sn -start_at_zero
>>> -muxdelay 0 ...
>>>>> [in#0 @ 0000000000542d00] Error opening input: Invalid data found when
>>> processing input
>>>>> ffmpeg -i ... -c:v libx264 -an -sn -start_at_zero -muxdelay 0
>>> -forced-idr 1 ...
>>>>> [in#0 @ 0000000000542d00] Error opening input: Invalid data found when
>>> processing input
>>>> This option belongs to libx264, not to FFmpeg.
>>>>
>>>> Try this:
>>>>
>>>> "-x264opts forced-idr"
>>>>
>>>> ---
>>>> Will
>>> Thank you, Will. Yes, I did try that:
>>>
>>>
>> Try instead this one:
>>
>> ffmpeg -i <input> -c:v libx264 -forced-idr 1 -an -sn -start_at_zero
>> -muxdelay 0 <output>
> 
> The error msg is
> 
> "Error opening input: Invalid data found when processing input" The input isn't recognized. Changing 
> output options won't make any difference. Regards, Gyan

The error message is false, Gyan. There appears to be 3 things going on:
1, '-filter_complex:v select' is getting timestamps that are 12 seconds in error,
2, '-filter_complex:a aselect' is interfering with timing during processing by another 24 seconds, 
even when '-an' is included, and
3, '-copyts -start_at_zero' is failing.

There's something about this Criterion disc that gives FFmpeg indigestion.

I'm investigating and will publish a report.

--Mark.