[Cin] Updated filetiff patch

Phyllis Smith phylsmith2017 at gmail.com
Thu Mar 19 20:34:28 CET 2020


Andrew,
Trying to keep up with you but expect that I have already lost track and
will miss some email.  (My advice, be sure to get some exercise and do not
spend all of your time on the computer; GG took a solo 1.5 hour bike ride
yesterday).

Anyway, from March 15, I could not reproduce this "0 frames".  Which format
did you use for the render?  My test below your output is from ffmpeg and
then tiff and testing for exr and jpeg sequence also showed 1 frame.  In my
render menu, I specifically selected "One frame" and I tested using a x.mov
and a x.png file.  Any suggestions for me to reproduce ?

Also, a bit of nipicking (?) but Cinelerra doesn' show single-frame
> rendering correctly in stats:
>
> *** rendered 0 frames* in 14.170 secs, 0.000 fps
> *Render::render_single*: Session finished.
> ** rendered 355 frames in 249.619 secs, 1.422 fps
> Render::render_single: Session finished.
> ** rendered 0 frames in 3.640 secs, 0.000 fps
>
> Shouldn't it be 1 frame, at least?
>
> *Render::render_single*: Session finished.
*** rendered 1 frames *in 0.121 secs, 8.264 fps
[Detaching after vfork from child process 163845]
*Render::render_single:* Session finished.
*** rendered 1 frames *in 0.079 secs, 12.658 fps
[Detaching after vfork from child process 164058]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20200319/cfa9f907/attachment.html>


More information about the Cin mailing list