27.10.2020, 21:11
Image sequence support was added mainly to support the output of 3D rendering tools, there image sequences make sense since it might take quite a while to calculate just a single image of a render sequence. (that sadly has not really changed, especially if you need to visualize new developed rendering&co methods)
If video import and export would usually take minutes per frame Hybrid would probably just support image sequences.
Hybrid does not support DVD output since:
a. I have no clue how to properly calculate the overheads for vob files
b. I don't know any really good open source MPEG-2 encoder (only free cross-platform MPEG-2 encoder I'm aware of is the one in FFmpeg, I had hope for x262, but that one turned into a dead project)
c. I haven't created DVDs since before I started writing Hybrid.
d. my knowledge about DVD structures (especially menu structures) is really minimal
---
Also calling something like:
seems to be easy enough that folks can do it themselves.
Cu Selur
If video import and export would usually take minutes per frame Hybrid would probably just support image sequences.
Hybrid does not support DVD output since:
a. I have no clue how to properly calculate the overheads for vob files
b. I don't know any really good open source MPEG-2 encoder (only free cross-platform MPEG-2 encoder I'm aware of is the one in FFmpeg, I had hope for x262, but that one turned into a dead project)
c. I haven't created DVDs since before I started writing Hybrid.
d. my knowledge about DVD structures (especially menu structures) is really minimal
---
Also calling something like:
ffmpeg -i "path to video" -f image2 -vcodec png "E:\Output\%06d.png"Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.