[Octave-bug-tracker] [bug #63560] [octave forge] (image) imresize gives inaccurate result

[Hartmut]

Follow-up Comment #12, bug #63560 (project octave):

Our current Octave repo code does exactly this! It has a big loop (that runs
twice), and does first the processing of one image axis, using a first scaling
factor and a first interpolation kernel, and afterwards the the processing of
the second image axis. So all that you wish in comment #11 has already been
taken care of in our current implementation :)

It would probably help if you used our patched imresize implementation (using
the latest patch, currently V3) on a handful of real images, and thoroughly
look at the results if something unexpected happens to them. If you observe no
obvious side-effects, I am now confident enough to do the right think in the
patch, that we could probably push it afterwards.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63560>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/