![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
#1 When I render a post processed animation, the frames of the
animation do not get post processed. Instead, every frame is written to
a file called *PP.* so I get only the last frame. This is obviously
wrong. How do I turn this feature off?
#2 There is mention in the HTML docs (at the end of the convolution
matrix) of a blur matrix. Yet I can find no other references, anywhere
in the docs. May I have a example, and usage for this feature, if it
exists?
And thanks, Nathan, good job on .5.
--
H.E. Day
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <39217ACA.9C5D0A4D@heday.freeservers.com>, "H.E. Day"
<The### [at] heday freeservers com> wrote:
> #2 There is mention in the HTML docs (at the end of the convolution
> matrix) of a blur matrix. Yet I can find no other references, anywhere
> in the docs. May I have a example, and usage for this feature, if it
> exists?
The blur matrix *is* the convolution matrix, I just called it a
different thing earlier in development.
--
Christopher James Huff - Personal e-mail: chr### [at] yahoo com
TAG(Technical Assistance Group) e-mail: chr### [at] tag povray org
Personal Web page: http://chrishuff.dhs.org/
TAG Web page: http://tag.povray.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>
> #1 When I render a post processed animation, the frames of the
> animation do not get post processed. Instead, every frame is written to
> a file called *PP.* so I get only the last frame. This is obviously
> wrong. How do I turn this feature off?
PP for post-processing I suppose. I noticied a similar problem than
yours.
This process seems to keep the non-processed image intact and to create
a new image -based on it- renamed with 8 letters including PP. This mean
I have to use a very short name, max 6 letters.
I suppose that if you have an animation of "Final_Frame=999", your name
should be of 3 letters max. At the end of the calculation of the frames,
you'll have a serial of frame with 6 caracters and another serial with
those same caracters and ending by "PP", also 8 caraters.
Well, I hope I'm clear enough, my english is quite poor!
Another solution could be to rename each frame ending by "PP" with an
external program. But I don't know how to.
Anyone knows better?
Hoping this can help.
DEPerere
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
H.E. Day <The### [at] heday freeservers com> wrote ...
> #1 When I render a post processed animation, the frames of the
> animation do not get post processed. Instead, every frame is written to
> a file called *PP.* so I get only the last frame. This is obviously
> wrong. How do I turn this feature off?
global_settings{
post_process{overwrite_file}
}
-Nathan
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
DEPerere <per### [at] infomaniak ch> wrote...
>
> This process seems to keep the non-processed image intact and to create
> a new image -based on it- renamed with 8 letters including PP. This mean
> I have to use a very short name, max 6 letters.
>
> I suppose that if you have an animation of "Final_Frame=999", your name
> should be of 3 letters max. At the end of the calculation of the frames,
> you'll have a serial of frame with 6 caracters and another serial with
> those same caracters and ending by "PP", also 8 caraters.
>
> Well, I hope I'm clear enough, my english is quite poor!
What you are saying is clear. I hadn't thought of the truncation that
occurs because of the 8 character limit in relation to animation files. Any
suggestions? Could we forget about the 8-character limit (and simply append
the "_PP" without truncating), or would that cause big problems for DOS? Is
there a better solution?
-Nathan
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
If something in DOS doesn't like the non-8.3 file name it doesn't "pass go",
at least nothing I've ever seen has any recognition of a file like
foobar~1.tga, so it can cause trouble.
Windows version would be fine like that though ;-) if you could surpass the
naming limit in POV.
Bob
"Nathan Kopp" <Nat### [at] Kopp com> wrote in message
news:3921f499$1@news.povray.org...
|
| DEPerere <per### [at] infomaniak ch> wrote...
| >
| > I suppose that if you have an animation of "Final_Frame=999", your name
| > should be of 3 letters max. At the end of the calculation of the frames,
| > you'll have a serial of frame with 6 characters and another serial with
| > those same characters and ending by "PP", also 8 characters.
|
| I hadn't thought of the truncation that
| occurs because of the 8 character limit in relation to animation files. Any
| suggestions? Could we forget about the 8-character limit (and simply append
| the "_PP" without truncating), or would that cause big problems for DOS? Is
| there a better solution?
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Tue, 16 May 2000 21:21:08 -0400, "Nathan Kopp" <Nat### [at] Kopp com>
wrote:
> Is there a better solution?
What about outputing animation frames to an "archive file" of some
type (ie ZIP file)? If you went this route, then there would only be
one file for all the frames, and its name would be easier to deal
with. The individual frames inside the archive could then have a pure
numerical sequence for their names. Something like 00000001.TGA could
be the first file name inside the archive, and 00000002.TGA could be
the second, and so on.
In case there is some objection to the compression of ZIP files,
remember that there is also provision for non-compressed ZIP files as
well. Of course, we could always use some other archive format. I just
mentioned this as an example case. If I'm not mistaken, DTA will work
with ZIP archives, for whatever that's worth.
Later,
Glen Berry
( Remove the "7" from 7no### [at] ezwv com to email me. )
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> global_settings{
> post_process{overwrite_file}
> }
Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you.
I mean it.
--
H.E. Day
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Glen Berry <7no### [at] ezwv com> writes:
>
> What about outputing animation frames to an "archive file" of some
> type (ie ZIP file)? If you went this route, then there would only be
> one file for all the frames, and its name would be easier to deal
> with. The individual frames inside the archive could then have a pure
> numerical sequence for their names. Something like 00000001.TGA could
> be the first file name inside the archive, and 00000002.TGA could be
> the second, and so on.
>
> In case there is some objection to the compression of ZIP files,
For compression I suggest using zlib. This is the same as gzip and it
has the advantage that zlib is already included in POV-Ray.
Thomas
--
http://thomas.willhalm.de/ (includes pgp key)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Nathan Kopp <Nat### [at] kopp com> wrote:
: What you are saying is clear. I hadn't thought of the truncation that
: occurs because of the 8 character limit in relation to animation files. Any
: suggestions? Could we forget about the 8-character limit (and simply append
: the "_PP" without truncating), or would that cause big problems for DOS? Is
: there a better solution?
Why do every platform have to suffer from the limitation of just one
platform? Why do Unix, Win9x, NT, Mac and any other platform have to use
a limited version which is intended to one platform: DOS?
I would suggest some #ifdef's in the povray source code. If we are NOT
compiling for DOS, then just use as long file names as needed. If we are
compiling for DOS, then truncate and don't care about the consecuences.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |