Re: [Gimp-developer] Problems with JPG?!

On Sun, 31 Jan 2016 22:22:55 +0000, Kevin Payne wrote:
Yes it's almost certainly the bug that won't get fixed raising it's ugly head again:

Manufacturers simply aren't going to fix their firmware, particularly
for older devices (read: are already on the market).  And it's
possible that a firmware fix wouldn't even be enough, since printers
would need more memory to buffer the entire image rather than just
reconstituting it one row of blocks at a time.  There's also the added
testing expense.  Phones and cameras don't generate progressive JPEGs,
so printer, TV, etc. manufacturers don't have any real incentive to
support them.  The manufacturers probably don't even write their own
firmware; they contract it out.

Progressive JPEGs are nice for displaying big images in browsers over
slow links (which my 1500/368 DSL qualifies as).  I admit that they're
easier for me in that context.  But given the confusion this is
causing, and that it requires non-trivial knowledge (and tools) for
people to fix after the fact, I'd argue that this should be revisited.

From: gimp-developer-list <gimp-developer-list-bounces gnome org> on behalf of Michael Schumacher <schumaml 
gmx de>
Sent: 31 January 2016 20:31
To: gimp-developer-list gnome org
Subject: Re: [Gimp-developer] Problems with JPG?!

Am 31.01.2016 um 16:29 schrieb Stefan Rohde:

I can not display images that I have prepared and saved with GIMP 2.8.14
(under Windows 10) in jpg-format on my TV or via a digital box (WD TV).

Do you have an idea or information !?

It's most likely the Progressive option in the advanced part of the JPEG
export dialog.

Robert Krawitz                                     <rlk alum mit edu>

***  MIT Engineers   A Proud Tradition  ***
Member of the League for Programming Freedom  --
Project lead for Gutenprint   --

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]