![](/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) |
I am using MainActor to compile my images into an animation. I had to
try to submit (THE SAME!!) entry about 7 times before it would be
accepted by IRTC.
My entry was being rejected for failing the "mpeg_stat -verify -quiet"
test. Using little but intuition, I changed some settings in MainActor
to eliminate all audio data from the file. This recompiled animation
worked.
Just some advice for anyone who has trouble getting IRTC to accept
MainActor-compiled animations.......
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) |
Greg M. Johnson wrote:
>
> I am using MainActor to compile my images into an animation. I had to
> try to submit (THE SAME!!) entry about 7 times before it would be
> accepted by IRTC.
>
> My entry was being rejected for failing the "mpeg_stat -verify -quiet"
> test. Using little but intuition, I changed some settings in
> MainActor to eliminate all audio data from the file. This recompiled
> animation worked.
>
> Just some advice for anyone who has trouble getting IRTC to accept
> MainActor-compiled animations.......
Some kind soul who meant well sent me his copy of MainActor; after
using it a few times on the last round of the IRTC, I noticed
artifacting that wasn't present in the output of CMPEG (ie, CMPEG was
producing better-quality work). I went back to using CMPEG.
Regards,
John
--
ICQ: 46085459
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) |
John VanSickle <van### [at] erols com> wrote:
: Some kind soul who meant well sent me his copy of MainActor; after
: using it a few times on the last round of the IRTC, I noticed
: artifacting that wasn't present in the output of CMPEG (ie, CMPEG was
: producing better-quality work). I went back to using CMPEG.
I think that the amount of artifacts depends on the quality setting of the
frames, the type of the frames (I, P or B) and the amount and ordering of them.
This also affects file size.
Cmpeg is very good because you can easyly change these things.
With the default settings of cmpeg (IBBPBBPBB or something like that), my
entry was too big (about 6 Megs). I tried lots of settings until I found
one that gave me lots of compression without too many artifacts (the frames
were in the order IBPBPBPBPBPBPBPBPB if I remember right).
--
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) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Nieminen Juha wrote:
> I think that the amount of artifacts depends on the quality setting of the
> frames, the type of the frames (I, P or B) and the amount and ordering of them.
> This also affects file size.
> Cmpeg is very good because you can easyly change these things.
> With the default settings of cmpeg (IBBPBBPBB or something like that), my
> entry was too big (about 6 Megs). I tried lots of settings until I found
> one that gave me lots of compression without too many artifacts (the frames
> were in the order IBPBPBPBPBPBPBPBPB if I remember right).
I haven't dug into those settings yet. I just started using one of the examples
that I liked. But as noted elsewhere from no AA to the usual default AA the file
size dropped from 4M to 3M almost. And there was a much smoother motion as a
result. It appears the more AA the less CMPEG has to deal with in assembling the
frames.
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) |
Nieminen Juha wrote in message <388308d3@news.povray.org>...
> I think that the amount of artifacts depends on the quality setting of
the
>frames, the type of the frames (I, P or B) and the amount and ordering of
them.
>This also affects file size.
> Cmpeg is very good because you can easyly change these things.
> With the default settings of cmpeg (IBBPBBPBB or something like that), my
>entry was too big (about 6 Megs). I tried lots of settings until I found
>one that gave me lots of compression without too many artifacts (the frames
>were in the order IBPBPBPBPBPBPBPBPB if I remember right).
In general, "I" frames give you the best quality, but by far the least
compression. "P" frames give you good compression and good quality, while
"B" frames give enormous compression at the lowest quality. I used the
pattern "IPPIPPIPPIPPIPPI" for my robot, giving good quality and 80:1
compression. The pattern "IBBBBBBBBBBBBBBB" gave 312:1 compression, but a
quality that the generous would describe as "horrendous".
Mark
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) |
Hi Greg!
I was thinking of using main actor too. But with Sander's CMPEG shell,
CMPEG becomes handy.
But thanks for the advice though.
Karl
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |