20.07.2020, 19:40
(I'm using a program that only outputs png image streams for lossless encodes, hence my recent threads.)
If you create an image stream job in Hybrid, add it to the job list, then, create a SECOND image stream job with a DIFFERENT resolution, Hybrid "remembers" the resolution from the FIRST job and "imposes" that on the second. This will then corrupt the output. (You actually don't have to create a job... this will happen if you JUST click the "Accept" button then immediately go back and select a different stream with a different resolution.)
Example: First image stream job with resolution of 1440x1080:
After adding to job list, here is now the input window for the second image stream job with a resolution of 1920x1080:
Closing and restarting Hybrid will "reset" the resolution for image streams.
Example files to reproduce this attached.
[attachment=944]
I should also mention (I normally don't like to report multiple things in one thread but this kind of goes with it):
While not a bug, when you select an image stream input for a second job, the "last Frame" button "remembers" the directory from the first job. So if you're not careful and select the last image from the FIRST job, you'll have two different directories for first frame and last frame, which really shouldn't be allowed... "last Frame" should ONLY allow an image to be selected from the SAME directory as the "1st frame".
If you create an image stream job in Hybrid, add it to the job list, then, create a SECOND image stream job with a DIFFERENT resolution, Hybrid "remembers" the resolution from the FIRST job and "imposes" that on the second. This will then corrupt the output. (You actually don't have to create a job... this will happen if you JUST click the "Accept" button then immediately go back and select a different stream with a different resolution.)
Example: First image stream job with resolution of 1440x1080:
After adding to job list, here is now the input window for the second image stream job with a resolution of 1920x1080:
Closing and restarting Hybrid will "reset" the resolution for image streams.
Example files to reproduce this attached.
[attachment=944]
I should also mention (I normally don't like to report multiple things in one thread but this kind of goes with it):
While not a bug, when you select an image stream input for a second job, the "last Frame" button "remembers" the directory from the first job. So if you're not careful and select the last image from the FIRST job, you'll have two different directories for first frame and last frame, which really shouldn't be allowed... "last Frame" should ONLY allow an image to be selected from the SAME directory as the "1st frame".