arn't a couple of presets good enough to help people without the technical
knowlege ?
On Sat, Oct 19, 2013 at 1:28 AM, Tobias Ellinghaus wrote:
> Am Freitag, 18. Oktober 2013, 13:57:52 schrieb jeremy rosen:
> > my guess is it's a badly worded
> >
> > "optimized for digital painting"
> > "opti
Am Freitag, 18. Oktober 2013, 13:57:52 schrieb jeremy rosen:
> my guess is it's a badly worded
>
> "optimized for digital painting"
> "optimized for photo"
> "optimized for graph and schematics"
>
> but because portraits and other photo with large surface compress better
> with the digital painti
Sounds good to me, I'll add it to my TODO list for the next iteration of
the module.
On Fri, Oct 18, 2013 at 1:57 PM, jeremy rosen wrote:
> my guess is it's a badly worded
>
> "optimized for digital painting"
> "optimized for photo"
> "optimized for graph and schematics"
>
> but because portrai
my guess is it's a badly worded
"optimized for digital painting"
"optimized for photo"
"optimized for graph and schematics"
but because portraits and other photo with large surface compress better
with the digital painting preset, there is this confusion..
frop a UI point of view here are a few
are there any docs about what this actually does? if we don't find out i
would vote for removing the meaningless explanation altogether :)
On Fri, Oct 18, 2013 at 12:00 PM, Dimitrios Psychogios <
dpsychog...@gmail.com> wrote:
> These come directly from encode.h (
> https://code.google.com/p/webm
These come directly from encode.h (
https://code.google.com/p/webm/source/browse/src/webp/encode.h?repo=libwebp).
Look at enums: WebPPreset and WebPImageHint. The alternative would be to
use the Default hint and expose all the encoder options in the UI which
would make the module too complicated
yeah, this sounds like "what compression algorithm should we use" so we
need to know a bit more about there different best/wrors case compression
to give better advice to our audience.
On Fri, Oct 18, 2013 at 10:54 AM, johannes hanika wrote:
> right. sounds like overly simplified technical ter
right. sounds like overly simplified technical terms, probably written for
a non-image processing audience somewhere in a webdesign doc.. i think
these should be changed to something darktable folks would understand
(wavelet compression? color quantization biased to support more shades of
blue? the
Hi,
There's a string in the WebP module that I find a bit confusing (taken
from the generated sv.po):
#: ../src/imageio/format/webp.c:281
msgid ""
"image characteristics hint for the underlying encoder.\n"
"picture : digital picture, like portrait, inner shot\n"
"photo
