On Wed, Jul 10, 2024 at 11:18 PM Mark Filipak <markfilipak.i...@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> _______________________________________________ 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".
