Could you please merge this patch or merge a similar fix?
Thanks,
Mark Niebur
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
This should be fixed already on master? I checked a few hours ago and was
able to repro.
On Tue, Oct 15, 2019, 5:03 PM Paul B Mahol wrote:
> Should be fixed.
>
> On 10/16/19, Mark Niebur wrote:
> > I'm sorry for not specifying. In the case that data is not ready from
> >
} else if (!in) {
>> +if (ff_outlink_frame_wanted(ctx->outputs[0])) {
>> ff_inlink_request_frame(ctx->inputs[1]);
>> -return 0;
>> }
>> + return 0;
>> }
>> in-&
s->pts += av_rescale_q(in->nb_samples,
Thanks,
Mark
> On Oct 15, 2019, at 2:26 PM, Paul B Mahol wrote:
>
> On 10/15/19, Mark Niebur wrote:
>> Hello,
>> I'm trying to debug an issue I'm seeing where the filter "acrossfade"
>> produces a segfault. This
Would this be on master or some other branch?
> On Oct 15, 2019, at 2:26 PM, Paul B Mahol wrote:
>
> On 10/15/19, Mark Niebur wrote:
>> Hello,
>> I'm trying to debug an issue I'm seeing where the filter "acrossfade"
>> produces a segfault. This seemin
Hello,
I'm trying to debug an issue I'm seeing where the filter "acrossfade" produces
a segfault. This seemingly only happens in docker containers, and I am seeing
it when running a rather large filter chain. I'm trying to get to the bottom
of it, but it would be really helpful to understand
