 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi all.
I went crazy with the code because with "ONCE" activated I kept seeing GIF
images strechted and repeated 4 times.
The same images, which I hadn't saved recently, were regular.
Then I understand, now Irfanview has the INTERLACED option by default, but this
is not recognized and the decoding of the image is wrong.
Regards
G.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 03/03/2020 à 07:04, GioSeregni a écrit :
> Hi all.
> I went crazy with the code because with "ONCE" activated I kept seeing GIF
> images strechted and repeated 4 times.
> The same images, which I hadn't saved recently, were regular.
> Then I understand, now Irfanview has the INTERLACED option by default, but this
> is not recognized and the decoding of the image is wrong.
> Regards
> G.
>
>
Well, the problem should be handled in povray,
since FS#314, but seems the correction did not make it in the official
code. (not the 3.7 stable anyway)
But it is already fixed on the official master.
For the curious, in source/base/image/gif.cpp, the check for interlaced
gif should look at buffer[8] and not buffer[9] (for & 0x40)
Now, you won't be happy with the correction either, because interlaced
gif are not supported but you will get an interruption at parse time
instead of rendering (so it will save you time).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le_Forgeron <jgr### [at] free fr> wrote:
> Le 03/03/2020 à 07:04, GioSeregni a écrit :
> > Hi all.
> > I went crazy with the code because with "ONCE" activated I kept seeing GIF
> > images strechted and repeated 4 times.
> > The same images, which I hadn't saved recently, were regular.
> > Then I understand, now Irfanview has the INTERLACED option by default, but this
> > is not recognized and the decoding of the image is wrong.
> > Regards
> > G.
> >
> >
>
> Well, the problem should be handled in povray,
> since FS#314, but seems the correction did not make it in the official
> code. (not the 3.7 stable anyway)
>
> But it is already fixed on the official master.
>
> For the curious, in source/base/image/gif.cpp, the check for interlaced
> gif should look at buffer[8] and not buffer[9] (for & 0x40)
>
> Now, you won't be happy with the correction either, because interlaced
> gif are not supported but you will get an interruption at parse time
> instead of rendering (so it will save you time).
Thanks for your kind reply, it's ok, in my opinion the problem arises if the
user doesn't know it, because if he thinks it's his code's fault he can work
hours without finding a solution.Best Regards and thanks again!
G.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
