https://bugzilla.wikimedia.org/show_bug.cgi?id=32721
--- Comment #23 from John Cupitt <[email protected]> --- (In reply to comment #22) > Anything left here to do, or can this ticket be closed as FIXED? I'm the vips maintainer. As it stands, the VipsScalar plugin will cause a lot of disc traffic. Should fixing that happen in a new bug? If yes, then this can be closed. VipsScalar currently works by running a series of separate vips commands. Looking at the source here: https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VipsScaler.git;a=blob;f=VipsScaler_body.php;h=69f31b108d99849c36fd92591f135bfbfca69d02;hb=HEAD makeCommands() will typically run something like: # unpack png file to a huge disc temp vips im_png2vips huge.png t1.v # block shrink by large integer factor vips im_shrink t1.v t2.v xx xx # bilinear resize to final exact dimensions vips im_resize_linear t2.v t3.v xxxx yyyy # sharpen slightly to counteract softening effect of bilinear vips im_convf t3.v t4.v sharpen_matrix # any 90-degree rotation required vips im_rotxx t4.v final.jpg Instead, it should simply run vipsthumbnail: vipsthumbnail huge.png -o final.jpg --size required-output-size-in-pixels --interpolator bicubic This requires the latest stable version of vips which is not yet in Debian and must be built from source. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
