To the POV Team:

I have a request to add JPEG as an option for rendered images.  The library
and files can be found at:

http://support.intel.com/support/performancetools/libraries/ijl/index.htm

Post a reply to this message

In article <38ad6b4e@news.povray.org> , "Mike Weber" <mik### [at] pyxiscom>
wrote:

> To the POV Team:
>
> I have a request to add JPEG as an option for rendered images.  The library
> and files can be found at:
>
> http://support.intel.com/support/performancetools/libraries/ijl/index.htm


To quote from the Intel site:

"Intel JPEG Library System Requirements

The Intel JPEG Library runs on Intel Architecture-based personal computers
running Microsoft Windows. The library integrates into an application or
library written in C or C++. The Intel JPEG Library requires the following
hardware and software:

Hardware
Intel Pentium processor-based system (a Pentium, Pentium Pro, Pentium with
MMX technology, Pentium II, or Pentium III processor-based system) 8 MBytes
RAM (32 MBytes RAM recommended)

Software
Microsoft Windows 95/98, Windows NT 4.0 or higher A C++ compiler: Intel
C/C++ Compiler version 2.4 or higher, or Microsoft Visual C++ version 4.0 or
higher"


However, there is a free JPEG library available which is cross platform. The
issue of JPEG output has previously been discussed in this newsgroups and
JPEG output is unsuitable for POV-Ray (just search a few month back to find
a thread on it). JPEG input is another issue.


        Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich wrote:
> 
> The issue of JPEG output has previously been discussed in this
> newsgroups and JPEG output is unsuitable for POV-Ray (just search a
> few month back to find a thread on it). JPEG input is another issue.

A thousand pardons, but I thought it was using JPEG output that was
okay, but that it lacked the quality needed for input.  Am I
remembering things incorrectly?

Regards,
John
-- 
ICQ: 46085459

Post a reply to this message

In article <38AD814A.5A3E5BC1@erols.com> , John VanSickle 
<van### [at] erolscom>  wrote:

>> The issue of JPEG output has previously been discussed in this
>> newsgroups and JPEG output is unsuitable for POV-Ray (just search a
>> few month back to find a thread on it). JPEG input is another issue.
>
> A thousand pardons, but I thought it was using JPEG output that was
> okay, but that it lacked the quality needed for input.  Am I
> remembering things incorrectly?

Yes, you do.


     Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

John VanSickle wrote:
> 
> A thousand pardons, but I thought it was using JPEG output that was
> okay, but that it lacked the quality needed for input.  Am I
> remembering things incorrectly?
> 

Output was considered not OK, becaus of unpredictable, lossy compression.
Input is OK, because many image maps are originally in JPEG anyway and
converting them to a non-lossy format won't help any.

Margus

Post a reply to this message

>Output was considered not OK, becaus of unpredictable, lossy compression.
>Input is OK, because many image maps are originally in JPEG anyway and
>converting them to a non-lossy format won't help any.


So when will we get it for input? I have several projects that would happily
work with JPEG. I would save a lot of HD space from having to turn textures
into PNG all the time.

Post a reply to this message

In article <38adca10@news.povray.org> , "TonyB" <ben### [at] panamac-comnet>
wrote:

> So when will we get it for input? I have several projects that would happily
> work with JPEG. I would save a lot of HD space from having to turn textures
> into PNG all the time.

As you know, the POV-Team does not give any exact details about new versions
or their release dates :-)


        Thorsten

Post a reply to this message

On Fri, 18 Feb 2000 10:50:15 -0600, "Thorsten Froehlich"
<tho### [at] trfde> wrote:

>JPEG output is unsuitable for POV-Ray (just search a few month back to find
>a thread on it). JPEG input is another issue.

Funny, it comes in pretty handy for IRTC submissions and you will also
find several "unsuitable" jpeg images here on this news server.   :)

My point is that while JPEG images are certainly compromised in
quality, there are certainly good uses for them. It would be nice if
POV-Ray could support them directly, instead of relying on external
software. This should be an option that the *user* gets to decide
whether or not to use. I'm very tired of some programmers deciding
that since *they* don't want to use a potential feature, that no one
else should have the option of using it either. This sort of thinking
only hurts the potential of POV-Ray. 

I assume I'll be flamed for saying that, but I think it needed to be
said.

Believe me, if I could handle the programming myself, I'd write a JPEG
patch personally. In fact, it has already been done by a few different
people, but it was never incorporated into the Official POV, nor did
it find it's way into SuperPatch, or Mega-POV. If anyone wants JPEG
support currently, they can always use IMP-POV. Unfortunately, it is
based on Official POV, and not Mega-POV, which is my favorite.


later,
Glen Berry

Post a reply to this message

Glen Berry wrote:

>If anyone wants JPEG
>support currently, they can always use IMP-POV.

Is JPEG compression (in IMP-POV) a post process? If so could you have both 
an uncompressed and a compressed image as output? Don't know what the gain 
of that would be though.

Ingo

-- 
Photography: http://members.home.nl/ingoogni/
Pov-Ray    : http://members.home.nl/seed7/

Post a reply to this message

> :-)


That little smiley just said a mouthful. :)

Post a reply to this message