[x265] My bug reports for rev. ~400-450
JMK
three4teen16 at coldmail.nu
Tue Oct 22 18:45:57 CEST 2013
--- shazeb at multicorewareinc.com wrote:
> From: Shazeb Khan <shazeb at multicorewareinc.com>
> To: Development for x265 <x265-devel at videolan.org>
> Subject: Re: [x265] My bug reports for rev. ~400-450
> Date: Tue, 22 Oct 2013 16:22:57 +0530
> Hi Mario,
> We were also observing the crash which you raised concern about,
> but it was fixed in a recent commit:
> 'Adapting weightp primitive for pixel input'.
> I hope you were running on a build prior to this commit.
> I however tried to reproduce the case you reported, by:
> 1) converting Sintel_trailer video to 640x272 y4m
>(in order to match your input)
> 2) and encoding with the parameters you provided :
> x265.exe sintel_trailer_2k_272p24.y4m -o
> sintel_trailer_360.hevc -F3 -q 12 -b 3 --b-adapt 2 --bframe-bias 30
> --weightp --ref 3 -i 240 --no-psnr --ssim --rdpenalty 1 --csv
> sintel_trailer_360.csv
> and did not observe any crash on VC11-x86_64 build.
For the notes, the maintainer of the buildbot @ http://x265.cc/ said the commit 4066e6e could be compiled successfully only through vc11 x86-64.
Which makes me ask: GCC can be used on various operating systems, including Windows,
whereas MSVC works under Windows only,
so what is the point of using it in the X265 Project?????
_____________________________________________________________
ps. Do you like my email address? Get yourself a coldmail.nu address too
http://www.coldmail.nu (it's free!)
More information about the x265-devel
mailing list