On Thu, Feb 11, 2021 at 11:15 PM Mark Thompson <s...@jkqxz.net> wrote:
> On 10/02/2021 23:53, Paul B Mahol wrote: > > On Wed, Feb 10, 2021 at 11:08 PM Mark Thompson <s...@jkqxz.net> wrote: > > > >> On 10/02/2021 17:16, Christopher Degawa wrote: > >>> From: Christopher Degawa <christopher.deg...@intel.com> > >>> > >>> Equivalent to the --lp option for SvtAv1EncApp, and is the only way > >>> to control how much cpu power svt-av1 uses for now > >>> > >>> Not using thread_count as it would be preferable to reserve that until > >>> svt-av1 properly implements a threads option > >> > >> Then what does it actually do? The description below about the number > of > >> logical threads to run sounds pretty much exactly like what the threads > >> option does. > >> > >> > > Threads option is limited to filters that do filtering by calling > > execute(), internal threading code of libavfilter. > > This would be from AVCodecContext.thread_count, not anything in > libavfilter. > > Yes, but it is same .execute thing. But I agree with rest of your views. > - Mark > _______________________________________________ > 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". _______________________________________________ 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".
