2 ms·
Very impressive, kudos. I'd like screenshots rather than PSNR and SSIM because those don't translate into human perception of a good encode. The only grip I ha
by mratsim 8y ago
Very impressive, kudos. I'd like screenshots rather than PSNR and SSIM because those don't translate into human perception of a good encode.
The only grip I have is the 13k lines of C + intrinsics.
- danmg 8y agoThat's most DSP code. Take a look at FFTW or SOKit.
- lieff 8y agoI've add screenshot of first intra frame and x264.264 to compare in players.
- vardump 8y ago> The only grip I have is the 13k lines of C + intrinsics. How are you supposed to get acceptable performance without intrinsics?
- userbinator 8y agoEspecially if it's meant to be an educational and in any case non-realtime encoder, intrinsics are not really necessary and make the code less portable. I also wonder how much the compiler can do autovectorisation on code like this --- it's pretty much exactly the type of code that autovectorisation is intended for. Edit: I noticed in the benchmark that it compressed the 10s foreman.cif (demo video) in half a second, so it's already 20x faster than realtime on that small resolution.
- lieff 8y agoIt's also single core comparison. Multi-threaded encoding is supported too: with 4 threads I get 0,190s for minih264 and 0,135s for x264.