Currently, we are not supporting VMAF in Windows, since it's not generating library files. We can try using MSYS/MinGW64 to add support for Windows in future.
On Mon, Apr 23, 2018 at 7:45 PM, Glenn Odagawa <flipflops2...@zoho.com> wrote: > GOOD QUESTION! > > > > > > > Glenn S. Odagawa & Quilo > Chicago, IL > +1 (773) 747-7546 > www.TheLayeredMix.co.nf-Website hosted on Norfolk Island > > -----Original Message----- From: Mario *LigH* Rohkrämer > Sent: Monday, April 23, 2018 7:55 AM > To: Development for x265 > Subject: Re: [x265] [PATCH] Add VMAF suppport to report per frame and > aggregate VMAF score > > > Mario Rohkrämer schrieb am 12.04.2018 um 18:25: > >> Am 12.04.2018, 13:13 Uhr, schrieb <induma...@multicorewareinc.com>: >> >> +.. Note:: >>> + >>> + When setting ENABLE_LIBVMAF cmake option to ON, it is recommended to >>> + also set ENABLE_SHARED to OFF to prevent build problems. >>> + We only need the static library from these builds. >>> + >>> + Binaries build with windows will not have VMAF support. >>> >> >> >> Can you explain why support for Windows builds is not (yet?) possible? >> >> I do remember that MABS is able to compile ffmpeg including VMAF, and >> also I do remember that it compiled only for x86-64 architecture due to >> some specific EMMS intrinsics. But, of course, MABS pulls the whole libvmaf >> source to do so. You will probably not want to require that. But it might >> not be too hard in MSYS/MinGW64 if an experienced user does it manually? >> > > > Still curious... > _______________________________________________ > x265-devel mailing list > x265-devel@videolan.org > https://mailman.videolan.org/listinfo/x265-devel > > _______________________________________________ > x265-devel mailing list > x265-devel@videolan.org > https://mailman.videolan.org/listinfo/x265-devel >
_______________________________________________ x265-devel mailing list x265-devel@videolan.org https://mailman.videolan.org/listinfo/x265-devel
