[Digikam-devel] [Bug 205776] "Embedded preview loads full image size" does not only do what it says, confusing users

[Matti Rintala]

https://bugs.kde.org/show_bug.cgi?id=205776





--- Comment #24 from Matti Rintala <bitti cs tut fi>  2009-09-04 09:55:44 ---
Mikolaj,

I think you have a good point. Shooting raw requires much more CPU power and
memory than jpeg. Which means that you probably do not have an old low-end
machine. Which makes the combination "use reduced-size embedded previews"
useless for raw shooters.

I see the following user groups:

1) Jpeg-only shooter
- Does not care how raw previews work
- May have a low-end machine, so reduced-size previews are useful

2) Raw-shooter whose camera stores full-size embedded previews
- Probably wants to use those full-size previews since they show how the
picture looked like on camera's lcd. Full-size is better for focus checking.
- Using embedded previews is also faster
- Wants jpegs full-size, since CPU and memory are not a problem

3) Raw-shooter whose camera only stores small embedded previews (are there such
cameras?)
- Small embedded preview shows how picture was on camera's lcd, but is not big
enough for checking focus etc.
- Needs full-size raw-decoded previews for checking focus
- Jpegs can be full-size
- I'll have to check which cameras belong to this group

For group 1 everything works now. For group 2 (me, and I think most
raw-shooters), the problem is that full-size preview does not use embedded
preview, even if it's available. For group 3 (if such group exists) things are
more complicated: for overall preview, small embedded preview is better. For
focus checking, full-size raw-decoded preview is better.

So what if: "Load full-size previews" uses embedded preview, if it's full-size.
Otherwise it uses raw-decoded preview. Would this be enough for every user
group?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.