486b95eb7b
Merge branch 'master' into add-stream-object
2019-11-19 17:08:03 +00:00
712157cd16
better support for TIFFs with many alphas
...
The premultiplied alpha can be in any position, and it checks if there
is more than one ASSOCALPHA.
See https://github.com/libvips/libvips/issues/1471
2019-11-18 16:48:34 +00:00
6b5035c160
update changelog
2019-11-15 17:30:31 +00:00
c1a027c8d7
ppm load uses streams
2019-11-14 12:57:39 +00:00
cb7bc24b2a
note in changelog
2019-11-12 18:05:17 +00:00
55024c71ce
Merge branch 'master' into add-stream-object
2019-11-12 14:08:02 +00:00
ceb2db513d
Merge branch '8.8'
2019-11-11 18:05:57 +00:00
b8ea3f8442
update cpp interface for stream variable rename
2019-11-11 09:24:45 +00:00
b65a9d7328
oop, missing ! on tiff save
...
resolution-unit metadata was not being checked correctly on tiff save,
thanks @kayarre
see https://github.com/libvips/pyvips/issues/133
2019-11-10 10:26:13 +00:00
f499cefb0e
add iiif layout to dzsave
2019-11-09 20:40:39 +00:00
edca486f19
revise buffered input
...
rad load works now
2019-11-06 16:35:19 +00:00
8eeb415b09
Merge branch 'master' into add-stream-object
2019-10-28 05:10:11 +00:00
8337e17428
add no_strip option to dzsave
...
it's sometimes useful to have pyramid tiles with ICC profiles
see https://github.com/libvips/libvips/issues/1451
2019-10-21 16:46:20 +01:00
20cb0da247
test suite passes
...
with all jpegload coming via VipsStreamInput
2019-10-11 14:03:10 +01:00
c9a7b92eeb
version bump
2019-09-17 17:16:26 +01:00
efdf33f3de
add vips_error_buffer_copy()
...
Add vips_error_buffer_copy() to fix a race in error buffer fetch.
See https://github.com/libvips/libvips/issues/1423
Thanks @dineshkannaa
2019-09-12 09:49:49 +01:00
7b2729adfa
fix up nifti load/save
...
- use double for all floating point scalar metadata, like other loaders
- remove use of stray "n" property
2019-09-09 16:06:22 +01:00
dd9eba9e26
add @format and @interpretation to rawload
2019-09-05 16:25:55 +01:00
1ee54bfa80
Merge branch '8.8'
2019-09-05 12:45:08 +01:00
06fdc95038
xres/yres params in tiffsave were in cm
...
and should have been in pixels/mm
thanks f--f
see https://github.com/libvips/libvips/issues/1421
2019-09-04 17:02:24 +01:00
da8cee048f
enable alpha in heifsave
...
Check for image alpha and enable it. There seem to be some
non-transparent tiles, curiously.
See https://github.com/libvips/libvips/issues/1411
2019-09-01 16:58:50 +01:00
75b45cc2ef
enable alpha handling in heic load
...
use RGBA decoding, when appropriate
see https://github.com/libvips/libvips/issues/1411
2019-09-01 16:37:43 +01:00
4b5b982711
merge 8.8
2019-08-31 12:29:50 +01:00
574be4380e
revert sharpen restoring the input colourspace
...
icc_export can make _RGB images, so the input can be outside the set of
supported colourspace transforms.
See 46212e92b1 (r34904985)
2019-08-31 11:29:36 +01:00
5d19bcf955
Merge branch '8.8'
2019-08-30 11:03:24 +01:00
6ea76f9632
improve data_length handling in jpg load
...
libjpeg uses unsigned ints for data length, so we must use size_t
everywhere.
2019-08-30 11:00:25 +01:00
349e76bb85
Merge branch '8.8'
2019-08-29 15:30:20 +01:00
3161de3b52
verify bands/format for coded vips images
...
WHen loading a vips image with Coding set, make sure that Bands and
BandFmt are correct.
2019-08-29 15:28:55 +01:00
9a5dca1ef8
Merge branch '8.8'
2019-08-28 10:05:12 +01:00
46212e92b1
fix default sharpen
...
sharpen with sigma 0.5 was doing nothing, since the new int precision
rules meant that we generated a point-point convolution.
This patch increases the int precision for sharpen, so we now work with
sigma down to 0.5.
Also: restore input colourspace. Previously, the output image was always
LabS (the computation space for sharpen). Now, it transforms back to the
input space. This is more in line with how other operators work.
Thanks 2h4dl for pointing this out.
See https://github.com/libvips/pyvips/issues/123
2019-08-28 09:16:40 +01:00
2f6cc1fad9
Merge branch '8.8'
2019-08-27 14:49:42 +01:00
d61a85f6c9
prevent over-pre-shrink in thumbnail
...
We could pre-shrink so much that an axis went to 0.
See https://github.com/lovell/sharp/issues/1782#issuecomment-525249430
2019-08-27 14:47:36 +01:00
d2ab993931
Merge branch '8.8'
2019-08-27 13:06:27 +01:00
5cce83a294
check image bounds for GIF load
...
It seems giflib does no checking of image dimensions at all, not even
height == 0.
2019-08-27 13:04:28 +01:00
23d0d5603d
Merge branch '8.8'
2019-08-24 17:15:45 +01:00
4691260540
better feof() handling in gif load
...
Relaxing the read error rules made looping possible .. make sure we
always stop explicitly on eof.
2019-08-24 17:14:10 +01:00
77de39320a
Merge branch '8.8'
2019-08-24 11:21:48 +01:00
038409093f
clip coding and interpretation on image read
...
They could be out of bounds enums. This used not to matter, but we use
them more now, so out of bounds values can cause coredumps.
2019-08-24 11:20:45 +01:00
1b57c6d066
Merge branch '8.8'
2019-08-23 15:43:12 +01:00
4b677fb16a
make GIF parse less strict
...
Some GIFs don't follow the standard very closely. Let them through.
See https://github.com/libvips/libvips/issues/1404
2019-08-23 15:40:48 +01:00
19a80e4efb
Merge branch '8.8'
2019-08-21 17:37:16 +01:00
b5e8e99746
fix a read-one-byte-beyond issue in jpeg load
...
libvips could harmlessly read beyond the end of a string with a crafted jpg
file
2019-08-21 17:17:54 +01:00
ed2054dbbc
revise arithmetic with const
...
there's a problem with out of bounds values, for example:
vips relational_const k2.jpg x.v equal 1000
actually finds pixels == 255, since 1000 is saturated converted to 255
before the test starts.
This patch reworks arithmetic against const values to fix this.
2019-08-21 10:35:48 +01:00
2d0c21279a
add tests
2019-08-19 16:27:44 +01:00
d80ce4bf15
fix a problem with shrinkv tail processing
...
Tail processing in shrinkv had an implicit assumption of round-down, but of
course we round to nearest. Thanks angelmixu.
see https://github.com/libvips/libvips/issues/1396
2019-08-13 11:21:01 +01:00
cdee0feb93
Merge branch '8.8'
2019-08-09 10:12:55 +01:00
aafc2c7948
add changelog note for profiles.c fix
2019-08-09 10:11:45 +01:00
988f9594f4
Merge branch '8.8'
2019-08-08 16:11:02 +01:00
ff58c67e33
add locks for pdfium load
...
We used to lock within documents, ie. we did not allow two threads to
work on the same file.
However pdfium is not threadsafe in any way, and this is not supported,
see:
https://groups.google.com/forum/#!msg/pdfium/kyIdh_J4csg/K1LvfPiHDwAJ
This patch adds locks around pdfium calls.
see:
https://github.com/libvips/libvips/issues/1380
https://github.com/libvips/libvips/issues/1275
2019-08-08 15:54:16 +01:00
7250b169d4
Merge branch '8.8'
2019-08-07 16:19:23 +01:00
John Cupitt