You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by akash-akya April 18, 2024
Does it makes sense to create VipsForeignSaveRawTarget to support streaming raw pixels in a unified way (vips_image_write_to_target(in, ".raw", target))?
I know there is already VipsForeignSaveRawFd which can be used to create similar interface, but in our case we have a unified interface to do streaming writes and this would help us to avoid creating special case to write raw pixels.
If this makes sense then I can try implementing it
The text was updated successfully, but these errors were encountered:
You can copy-paste code from something like ppmsave. I would have an abstract base class VipsForeignSaveRaw which writes to a target, then define VipsForeignSaveRawTarget, VipsForeignSaveRawFile etc. as concrete subclasses which define the parameters.
Discussed in #3940
Originally posted by akash-akya April 18, 2024
Does it makes sense to create
VipsForeignSaveRawTarget
to support streaming raw pixels in a unified way (vips_image_write_to_target(in, ".raw", target)
)?I know there is already
VipsForeignSaveRawFd
which can be used to create similar interface, but in our case we have a unified interface to do streaming writes and this would help us to avoid creating special case to write raw pixels.If this makes sense then I can try implementing it
The text was updated successfully, but these errors were encountered: