 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have a wonderful picture of bark that I'd like to use as a texture
in a scene... yet I couldn't find any way to do this. Is there any way
to make a JPEG a texture in POV-Ray (or any other picture format for
that matter)? If not, is there any other way that I could make a
semi-convincing bark texture?
-Thanks in advance!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ross Taylor wrote:
>
> I have a wonderful picture of bark that I'd like to use as a texture
> in a scene... yet I couldn't find any way to do this. Is there any way
> to make a JPEG a texture in POV-Ray (or any other picture format for
> that matter)? If not, is there any other way that I could make a
> semi-convincing bark texture?
>
> -Thanks in advance!
The official version of POV-Ray has no support for the jpg format. You
could however convert the jpg image into something lile a .tga image
file then use the image map pigment feature to apply your bark image
as a texture. I have had reasonable success using this method.
example -
pigment {
image_map { tga "bark.tga" interpolate 2 }
}
--
Ken Tyler - 1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wouldn't it be great if POV could at least read in JPEG?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
["TonyB" <ben### [at] panama phoenixnet>]
| Wouldn't it be great if POV could at least read in JPEG?
Well, libjpeg is fairly easy to interface so adding JPEG support
should be trivial, however: jpeg is lossy, and artifacts like that
can really disturb an otherwise good scene. JPEG should only be used
for the final image, not for textures.
Besides, you'd only save disk space, not ram, and disk is cheap.
--
A penny for your thoughts.
Mine are more expensive.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bjørn Vaggen Konestabo" wrote:
>
> ["TonyB" <ben### [at] panamaphoenixnet>]
> | Wouldn't it be great if POV could at least read in JPEG?
>
> Well, libjpeg is fairly easy to interface so adding JPEG support
> should be trivial, however: jpeg is lossy, and artifacts like that
> can really disturb an otherwise good scene. JPEG should only be used
> for the final image, not for textures.
For those cases where you have an image in jpeg and no other form,
converting it to a non-lossy format like TGA doesn't restore what was
lost. So Ross' situation is one example of where it might be useful for
textures.
-Mark Gordon
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Seeing as you have Win98, (english version, if that matters) you might also have
a viewer program called kodakimg. Start/Run... kodakimg and open the jpg
then File/Save as... Bmp for use in POV-Ray as a 'sys' file. I haven't done
anything with the sys type for a long time so maybe it's working well now
(sounds ominous, huh).
Bob
"Ross Taylor" <rta### [at] kearnet> wrote in message
news:3878BC1B.3A912449@kear.net...
> I have a wonderful picture of bark that I'd like to use as a texture
> in a scene... yet I couldn't find any way to do this. Is there any way
> to make a JPEG a texture in POV-Ray (or any other picture format for
> that matter)? If not, is there any other way that I could make a
> semi-convincing bark texture?
>
>
>
> -Thanks in advance!
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
omniVERSE wrote:
> Seeing as you have Win98, (english version, if that matters) you might also have
> a viewer program called kodakimg. Start/Run... kodakimg and open the jpg
> then File/Save as... Bmp for use in POV-Ray as a 'sys' file. I haven't done
> anything with the sys type for a long time so maybe it's working well now
> (sounds ominous, huh).
>
> Bob
>
> "Ross Taylor" <rta### [at] kearnet> wrote in message
> news:3878BC1B.3A912449@kear.net...
> > I have a wonderful picture of bark that I'd like to use as a texture
> > in a scene... yet I couldn't find any way to do this. Is there any way
> > to make a JPEG a texture in POV-Ray (or any other picture format for
> > that matter)? If not, is there any other way that I could make a
> > semi-convincing bark texture?
> >
> >
> >
> > -Thanks in advance!
> >
nah...
Just install Gimp and use that to convert stuff to PNG files. At least you get
compression as good or better than a .ZIPped BMP, plus it's cross-platform.
--
"My new computer's got the clocks, it rocks
But it was obsolete before I opened the box" - W.A.Y.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>For those cases where you have an image in jpeg and no other form,
>converting it to a non-lossy format like TGA doesn't restore what was
>lost. So Ross' situation is one example of where it might be useful for
>textures.
Exactly my point. Most of the textures on the 'net are JPEG (AFAIK), so you
could just download them and use them directly, and programs like 3DS2POV
wouldn't have to convert the textures to other formats for you, making the
conversion faster and easier.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ross Taylor wrote:
> I have a wonderful picture of bark that I'd like to use as a texture
> in a scene... yet I couldn't find any way to do this. Is there any way
> to make a JPEG a texture in POV-Ray (or any other picture format for
> that matter)? If not, is there any other way that I could make a
> semi-convincing bark texture?
You have to covert from jpeg to a supported format like targa.
Then it works but is not a heightfield. I gather one needs magapov for
that.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
TonyB wrote:
> >For those cases where you have an image in jpeg and no other form,
> >converting it to a non-lossy format like TGA doesn't restore what was
> >lost. So Ross' situation is one example of where it might be useful for
> >textures.
>
> Exactly my point. Most of the textures on the 'net are JPEG (AFAIK), so you
> could just download them and use them directly, and programs like 3DS2POV
> wouldn't have to convert the textures to other formats for you, making the
> conversion faster and easier.
Lets not run down jpeg without qualifications. Depending on the image and
how it was saved the loss might not be noticable.
In other words, don't throw away what might be useful until you have tried
it.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Matt Giwer wrote:
>
> TonyB wrote:
>
> > >For those cases where you have an image in jpeg and no other form,
> > >converting it to a non-lossy format like TGA doesn't restore what was
> > >lost. So Ross' situation is one example of where it might be useful for
> > >textures.
> >
> > Exactly my point. Most of the textures on the 'net are JPEG (AFAIK), so you
> > could just download them and use them directly, and programs like 3DS2POV
> > wouldn't have to convert the textures to other formats for you, making the
> > conversion faster and easier.
>
> Lets not run down jpeg without qualifications. Depending on the image and
> how it was saved the loss might not be noticable.
>
> In other words, don't throw away what might be useful until you have tried
> it.
Exactely my pointelly . or something.
Well, the new JPEG2000 standard look really promising, and also supports
lossless(!) compression. just a side point, I know, I know, but it would
still be a very nice thing to have that support in POV (output to jpeg
lossless, input from any jpeg) (no, I don't want lossy compression out
of POV, that would also increase the amount of beginner level questions
about why the image looks so bad (aso aso))
Well. there was a link in /. this month, didn't bookmark it though....
--
//Spider -- [ spider@bahnhof.se ]-[ http://darkmere.wanfear.com/ ]
And the devil in black dress watches over
My guardian angel walks away
Life is short and love is always over in the morning
Black wind come carry me far away
--"Sisters of Mercy" -- "Temple Of Love"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Spider wrote:
> Matt Giwer wrote:
> > Lets not run down jpeg without qualifications. Depending on the image and
> > how it was saved the loss might not be noticable.
> >
> > In other words, don't throw away what might be useful until you have tried
> > it.
>
> Exactely my pointelly . or something.
> Well, the new JPEG2000 standard look really promising, and also supports
> lossless(!) compression. just a side point, I know, I know, but it would
> still be a very nice thing to have that support in POV (output to jpeg
> lossless, input from any jpeg) (no, I don't want lossy compression out
> of POV, that would also increase the amount of beginner level questions
> about why the image looks so bad (aso aso))
>
> Well. there was a link in /. this month, didn't bookmark it though....
The bad news is that in 1996 (95?) when I wrote my quick and dirty HTML guide I
mentioned that fractal compression was coming to browsers.
I'll believe it when I see it.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
[On Wed, 12 Jan 2000 21:25:22 -0500, Matt Giwer <jul### [at] ijnet>]
| The bad news is that in 1996 (95?) when I wrote my quick and dirty
| HTML guide I mentioned that fractal compression was coming to browsers.
| I'll believe it when I see it.
There's a big difference here. No successful fractal compression
algoithm exist. There surely is a great potential here, but no
algorithm for effectively turning an image into a set of fractal
functions.
JPEG2000 however uses well known algorithms, and an implementation
already exists. It's written in Java, so you could have
JPEG2000 images in your browser today.
http://ltswww.epfl.ch/~neximage/decoder/index.html
--
A penny for your thoughts.
Mine are more expensive.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Matt Giwer wrote:
>
>
> The bad news is that in 1996 (95?) when I wrote my quick and dirty HTML guide I
> mentioned that fractal compression was coming to browsers.
>
> I'll believe it when I see it.
Yeah.. I was one of those who hooked to the .fif compression program
when it came, really impressive.. then I lost the writer/viewer (not
public thing) and ignored it, I know there was a plugin for NS 3.0 and
.fif, buit it never got much spread...
--
//Spider -- [ spider@bahnhof.se ]-[ http://darkmere.wanfear.com/ ]
And the devil in black dress watches over
My guardian angel walks away
Life is short and love is always over in the morning
Black wind come carry me far away
--"Sisters of Mercy" -- "Temple Of Love"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> There's a big difference here. No successful fractal compression
> algoithm exist. There surely is a great potential here, but no
> algorithm for effectively turning an image into a set of fractal
> functions.
There are.
Do a web search for the .fif format, Fractal Image Format I belive it
is. Graphic Workshop could/can read it, and it was great for photos, but
I've lost all references to it over the years.
--
//Spider -- [ spider@bahnhof.se ]-[ http://darkmere.wanfear.com/ ]
And the devil in black dress watches over
My guardian angel walks away
Life is short and love is always over in the morning
Black wind come carry me far away
--"Sisters of Mercy" -- "Temple Of Love"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wasn't it Spider who wrote:
>> There's a big difference here. No successful fractal compression
>> algoithm exist. There surely is a great potential here, but no
>> algorithm for effectively turning an image into a set of fractal
>> functions.
>
>There are.
>Do a web search for the .fif format, Fractal Image Format I belive it
>is. Graphic Workshop could/can read it, and it was great for photos, but
>I've lost all references to it over the years.
There is a shareware program, Fractal Imager, at http://www.iterated.com
that can encode and decode FIF format files.
Some drawbacks with fractal image compression are:
The algorithms are patented, and the owners of the patents are not
making them freely available. In particular, they've only made the
algorithms available on a small number of operating systems.
The time taken to encode a file is quite noticeable - as much as 68
seconds for an 800x600 image on my 500MHz machine, and probably quite a
bit longer on the machines that were commonly available on 1995.
--
Mike Williams + #
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Spider wrote:
> Matt Giwer wrote:
> > The bad news is that in 1996 (95?) when I wrote my quick and dirty HTML guide
I
> > mentioned that fractal compression was coming to browsers.
> >
> > I'll believe it when I see it.
> Yeah.. I was one of those who hooked to the .fif compression program
> when it came, really impressive.. then I lost the writer/viewer (not
> public thing) and ignored it, I know there was a plugin for NS 3.0 and
> .fif, buit it never got much spread...
I checked. It was 94.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bjørn Vaggen Konestabo" wrote:
> [On Wed, 12 Jan 2000 21:25:22 -0500, Matt Giwer <jul### [at] ijnet>]
> | The bad news is that in 1996 (95?) when I wrote my quick and dirty
> | HTML guide I mentioned that fractal compression was coming to browsers.
> | I'll believe it when I see it.
>
> There's a big difference here. No successful fractal compression
> algoithm exist. There surely is a great potential here, but no
> algorithm for effectively turning an image into a set of fractal
> functions.
As I saw it, the problem was the decompression routine was free. The
compression routine was hardware only at about $300 or so. Out of my interest
and league for a one function card.
> JPEG2000 however uses well known algorithms, and an implementation
> already exists. It's written in Java, so you could have
> JPEG2000 images in your browser today.
In fact a quick look says I have such a plugin on Netscape but I don't
remember ever coming across such a file -- nor do I remember ever installing
such a thing so it likely came with.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Most likely not. can't find a thing about it in the plugin
report on my machine. I also went to the Netscape Plugin
Finder page but found no reference.
Matt Giwer wrote:
> In fact a quick look says I have such a plugin on Netscape but I don't
> remember ever coming across such a file -- nor do I remember ever installing
> such a thing so it likely came with.
--
Mr. Art
"Often the appearance of reality is more important
than the reality of the appearance."
Bill DeWitt 2000
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
[On Wed, 12 Jan 2000 23:00:14 +0000, Mike Williams <mik### [at] nospamplease>]
| The time taken to encode a file is quite noticeable - as much as 68
| seconds for an 800x600 image on my 500MHz machine, and probably quite a
| bit longer on the machines that were commonly available on 1995.
On top of that, it doesn't do a much better job than good old jpeg,
and I suspect jpeg2000 would be superior.
--
A penny for your thoughts.
Mine are more expensive.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Williams wrote:
>
> Wasn't it Spider who wrote:
> >> There's a big difference here. No successful fractal compression
> >> algoithm exist. There surely is a great potential here, but no
> >> algorithm for effectively turning an image into a set of fractal
> >> functions.
> >
> >There are.
> >Do a web search for the .fif format, Fractal Image Format I belive it
> >is. Graphic Workshop could/can read it, and it was great for photos, but
> >I've lost all references to it over the years.
>
> There is a shareware program, Fractal Imager, at http://www.iterated.com
> that can encode and decode FIF format files.
Ahh. I knew it was there somewhere.
> Some drawbacks with fractal image compression are:
>
> The algorithms are patented, and the owners of the patents are not
> making them freely available. In particular, they've only made the
> algorithms available on a small number of operating systems.
I think I mentioned this in the other post, and I agree, it is a bad
thing. But there is such a thing as successful fractal compression :p
The lack of support(platforms), and the somewhat bothersome interface(at
least IMO back then) is also a drawback.
> The time taken to encode a file is quite noticeable - as much as 68
> seconds for an 800x600 image on my 500MHz machine, and probably quite a
> bit longer on the machines that were commonly available on 1995.
Yes... it was time consuming, but then I thought the quality was quite
remarkable, and filesizes in comparsion were quite small as well.
I ran it on a 486 DX2 - 66, as far as I can remember.. It was a mess..
but it ran :)
--
//Spider -- [ spider@bahnhof.se ]-[ http://darkmere.wanfear.com/ ]
And the devil in black dress watches over
My guardian angel walks away
Life is short and love is always over in the morning
Black wind come carry me far away
--"Sisters of Mercy" -- "Temple Of Love"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
