( Phyllis): When I used the ffmpeg/tiff render format, it created the toc file but it was empty even then. Also ran the CinGG version of 11/2016 and 2/2018; in both cases the toc file was either empty (the earlier ones) or just the first 4 lines. So I think it never worked right and the workaround as Andrea tested it to create the toc file manually.
Sorry to insist, but I think DPX support is very important. It would take more testing by other users. As I wrote in a previous message, some versions work for me, and even in Arch, DPX and PNG used to work for me (not anymore, now). @IgorBeg Please, can you test the rendering of a sequence of images (it only takes a few seconds), since you normally use Ubuntu 16?
I assume the ffmpeg command line creates it? I have not had the chance to try that yet. Does it?
FFmpeg creates the images with a command (muxer) that implies %05d in the name and then, thanks to the image2 command (demuxer), it reads them (without the need to create a TOC file) and creates the video. It occurs to me that CinGG presets create the images via %05d and then, instead of being read by image2, the TOC file (not the video file!) is created and can be imported into CinGG (or other program). Perhaps a version of "imagelist.sh" is implemented? In short, the difference between ffmpeg and CinGG is the creation of the TOC file. I remember that my hypothesis about the problem is the management of absolute/relative paths, since the TOC is created and works: only the links are missing. Is it possible to trace a patch that has touched the paths? If not, I'll say again that it's better to delete these presets and the related entries in the manual altogether. [ffmpeg reference: https://www.ffmpeg.org/faq.html#How-do-I-encode-single-pictures-into-movies_... https://www.ffmpeg.org/ffmpeg-formats.html#image2-2 https://www.ffmpeg.org/ffmpeg-formats.html#image2-1]