hi all, i want to share my way to use libjpeg loading options. here my addition to source https://github.com/Itseez/opencv/pull...
by this change i can set "scale_denom" parameter and load jpeg images scaled 1/2 - 1/4 - 1/8
also i wonder if it worth to merge to opencv library after revised by opencv gurus here. any comment is welcome
new feature added to cv::imread as documented
example usage:
cv::Mat img = cv::imread( "lena.jpg", IMREAD_REDUCED_COLOR_2 ) // loads image reduced 1/2
cv::Mat img = cv::imread( "lena.jpg", IMREAD_REDUCED_GRAYSCALE_8 ) // loads img reduced 1/8 grayscale
this will put you into vi (oh, shucks, yes, that infamous editor). you'll see a list of commits like:
pick 0a2a522 com_1
pick 087f4cb com_2
pick 05724ed com_3
change all but the 1st 'pick'(or the one you want to keep) to 'stash' (or 's'). . you probably need the 'insert' key to toggle insert mode
press 'escape' to toggle edit/command mode
this was only the 1st vi run, it will be followed by a second, where you're supposed to select/comment out/change the final commit message. comment out('#') anything unneeded, until left with a single line (in yellow)
[escape], ':w' , ':q'
;
@berak i did something but i don't know i am on the rigth way or not. on my fork like https://github.com/sturkmen72/opencv/... but how to update https://github.com/Itseez/opencv/pull...
ah, so that's a new branch now: "imread_reduced" , while the old pr was "patch-1" ?
you could try to overwrite the old "patch-1" branch with your new content (it will still be named "patch-1":
git checkout imread_reduced
git push -f origin patch-1
(push -f for "forced")
alternatively, you could just close the "patch-1" pr, and make a pull-request for "imread_reduced" (and maybe make a comment)
anyway, cool thing, you're close to getting it in ;)
i am trying to improve imread_reduced. my goal is by this change, to compute scale_denom value in load process. to explain it lets look example usage:
int onLoad( int width, int height )
{
int scale = 1;
if( width > 320 )
scale = width / 320;
return scale;
}
int main( int argc, char** argv )
{
Mat jpegimage = imread_reduced("fruits.jpg", IMREAD_COLOR, 0 , onLoad ); // onLoad is new ! by this way we can compute scale_denom inside process.
imshow("jpegimage",jpegimage);
waitKey();
return 0;
}
you can see implementing code here . @berak what is your opinion about it.
Asked: 2015-06-24 19:13:44 -0600
Seen: 872 times
Last updated: Nov 16 '15
i see 2 problems with that approach:
(major:) a global variable is used to store the scale factor. now, you can never be sure, in what state it is, also, which other part of the codebase has tried to set it before, so you will have to set it every time you try to imread() something. (you might not even know, what's in the filename)
(minor:) your cvSetJpegScale() function is hidden in the deprecated c-api. [in my case, i mostly try to avoid including any of those headers]
@berak thank you for your valuable critique. i changed something. your comments are very welcome
yea, i've seen, that you're trying to move it into an additional param for imread()
but this again has the drawback, that the interfaces will have to change, which breaks binary compatibility (which does not go well with the opencv devs)
also, the param is only valid for jpg images
(again, your effort there is highly appreciated, please don't take this all too negative !!)
@berak did you delete your last comment. i saw it but did not read
well, yes, - temporarily(sorry for confusion) ;) using the imread flags for this seems to be the best idea so far, imho.
(then i was not sure, if the size/allocation would work, but atm, it seems so.)
do you think, there's a way to get rid of the global var and the setter function ?
@berak it is easy to get rid of the global var and the setter function, then BaseImageDecoder class need a new method to set scale_denom value.
@StevenPuttemans Can i get your opinion
@sturkmen, I think @berak somewhat pointed all the critical problems out. But maybe adding an overload function on the imread operation is a better way? This ensures that binary compatibility is not broken.