New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dzsave support #54
Comments
ruby-vips is based on vips7. dzsave is part of vips8 and so you can't I don't know what the best solution to your problem would be. Does system "vips dzsave #{filename_of_full_res_image} #{name_of_desired_deepzoom_image} #{dzsave_options}" But I don't know carrierwave well enough to know where to add this, or dzsave takes about 2 - 3s for a 10,000 x 10,000 pixel RGB image, so it A simpler solution would be to run that command yourself as part of |
There's an experimental ruby-vips8 binding with dzsave support here: https://github.com/jcupitt/ruby-vips8 It has the serious problem that it must force a GC before each call to libvips :-( so still not quite production-ready. |
ruby-vips has now been bumped to 1.0 and an API break. The new API supports dzsave, so you should be all set. |
I understand libvips8 will automate integration of new and updated features, however advice on implementation or, better still, an example for dzsave within a rails app (using CarrierWave) would be greatly appreciated.
Or if not, flag it for addition to the CarrierWave-Vips gem.
The text was updated successfully, but these errors were encountered: