Closed GoogleCodeExporter closed 9 years ago
Original comment by ya...@google.com
on 3 Dec 2013 at 5:09
Hi Dominic,
The current VP9 top of tree code gave segfault while encoding with --tune=ssim.
You mentioned it worked a week ago. I reset to commit: Merge "Correct a couple
of typos" (ee1e4e645acd0e997040281eb4b59ff7d20a860e). But it didn't work. I got
the following error:
$ ./vpxenc --codec=vp9 -o test.webm test.I420 --limit=20 -p 2 --best
--cpu-used=0 --target-bitrate=2000 --auto-alt-ref=1 --minsection-pct=10
--maxsection-pct=2000 --lag-in-frames=25 --kf-min-dist=0 --kf-max-dist=99999
--static-thresh=0 --min-q=0 --max-q=63 --arnr-maxframes=7 --arnr-strength=5
--arnr-type=3 --i420 -w 1280 -h 720 --tune=ssim
Pass 1/2 frame 20/21 3192B 1276b/f 38304b/s 5148898 us (3.88 fps)
Pass 2/2 frame 20/0 0B 5160938 us 3.88 fps [ETA unknown] vpxenc:
../libvpx/vp9/common/vp9_reconintra.c:382: vp9_predict_intra_block: Assertion
`bwl >= 0' failed.
Aborted (core dumped)
It seems this problem existed for quite some time.
Yunqing
Original comment by yunqingw...@google.com
on 3 Dec 2013 at 10:51
Tuning for SSIM is not properly implemented for vp9 yet, propose to temporarily
disable the option here:
https://gerrit.chromium.org/gerrit/#/c/67993/
Original comment by ya...@google.com
on 4 Dec 2013 at 8:42
Hi Yunqing,
that's true, I was sure I had it working once... not so sure any more. I
only recently decided to evaluate compression performance for SSIM tuning
in detail. I was just curious because recently a commit arrived in the
master branch allowing to activate Adaptive Quantizers for the Segment IDs,
which to my mind carries the possibility of bringing SSIM performance of
VP9 to a new level. So thats why I wanted to set tune=SSIM, just for fair
evaluation. In my old test, I probably did not set tune=SSIM because they
were focused on PSNR performance, but I evaluted SSIM anyhow, so maybe
that's where I got the impression that SSIM for VP9 works.
On the ICIP2013 VP9 workshop in Melbourne, a lot of SSIM values for VP9
were presented, I just wonder, where the rate points NOT calculated with
tune=SSIM? That's going to be VERY interesting, seeing VP9 perform with
some SSIM optimizer logic!
Thanks to Yaowu for proposing to disable this command line option for now,
otherwise it would be quite confusing.
Original comment by dominic....@gmail.com
on 5 Dec 2013 at 12:21
Original comment by ya...@google.com
on 12 Dec 2013 at 5:52
Original issue reported on code.google.com by
dominic....@gmail.com
on 27 Nov 2013 at 9:40Attachments: