This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[BUG] Hybrid cannot differentiate between image sequences in a directory
#1
When the input source is an image sequence, and multiple image sequences exist in the same directory, Hybrid cannot differentiate between the image sequences complaining that the reading of input images goes beyond the end frame.  Applies to Hybrid released March 9, 2025

Reproduction:

1) Create multiple sequences of image files with the same name with frame number ascending by 1's.  
2) Put all the image sequences in the same directory.
3) Set input source to image sequence in the base tab.
4) Select the start and end frames for the specified image sequence.
5) Encode using your preferred settings.

Hybrid crashes with error that it read beyond the last frame of the sequence.

6) In the file directory, delete all image files that do not belong to the image sequence chosen as the input source.
7) Repeat steps 3 thru 5.

Notice Hybrid encodes normally.
Reply
#2
Quote:1) Create multiple sequences of image files with the same name with frame number ascending by 1's.
2) Put all the image sequences in the same directory.
Wouldn't one overwrite the other?
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
No.  Each image sequence would have a different base name.  For example:

image seequence 1:

image_0001.png
image_0002.png
image_0003.png
...
image_1000.png


image sequence 2:

pic_0001.png
pic_0002.png
pic_0003.png
...
pic_1000.png


The issue is Hybrid does not distinguish between image sequence "image_" and image sequence "pic_".  It thinks they are the same sequence, then complains when the file name changes during the read portion of encoding.
Reply
#4
Oh, okay. Will look at it later.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#5
I should add - this also applies to situations where an individual sequence numbering is interrupted, but not used.

for example, you have the following image sequence:

image_0001.png
image_0002.png
image_0003.png
...
image_1000.png

but image_0500.png through image_0700.png are missing, and you want to encode frames 0001 through 0400.  Hybrid complains the image sequence is bad even though the missing frames are outside the range being used as input.
Reply
#6
Uploaded a new dev version.
Let me know whether it fixes the problem for you.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)