That said results will vary considerably with subject matter and areas selected for preservation and deletion, on that topic it is likely we will make more than one attempt at it until we get a desired result, that means we need the "resize" operation to be as fast as technically possible, at the moment it is not, currently I am seeing the process is single threaded, at most using 52% of a dual core CPU and I would imagine maxing at around 26% of a quad core cpu, the extra 1 or 2% usage being some ancillary operation that only uses a small amount of CPU but is multi-core aware maybe file I/O? I think the developers should next look into multi-threading the resize operation and once it had been broken down into multithread freindly units they could look into GPU acceleration as well since most modern computers have able GPU's just sitting there almost idle, maximising the use of available processing ability will make the program far more usable especially when processing photos greater than 8 megapixels IMHO.īearing in mind that inteligence is a relative measurement, this does what it says on the tin so to speak, obviously it cannot beat the eye and human inteligence in deciding how to morph or cut the regions but it does what it does faster than human mind can get any graphics package to do it manually with conventional select and resize selection or other conventional tools including redraw with a brush. Bearing in mind that inteligence is a relative measurement, this does what it says on the tin so to speak, obviously it cannot beat the eye and human inteligence in deciding how to morph or cut the regions but it does what it does faster than human mind can get any graphics package to do it manually with conventional select and resize selection or other conventional tools including redraw with a brush.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |