CogVideoX I2V: Missing guard-rail on num_frames

[tin2tin]

Describe the bug

CogVideoX I2V: There is a warning when the negative_prompt is defined, but no warning when num_frames is defined, however, the latter will cause a faulty render, so maybe a guard-rail warning should be added to a defined num_frames value.

The faulty video: https://github.com/user-attachments/assets/5d3b4dd9-c9d2-43bb-b14c-bdd34b490bab

Reproduction

Just add a defined num_frames value to the inference code.

Logs

No response

System Info

Latest beta diff, Win 11

Who can help?

@DN6 @a-r-r-o-w

[a-r-r-o-w]

I'm having a bit of trouble understanding what's wrong here, sorry. Do you mean to say that there should be a num_frames == 49 restriction here?

[tin2tin]

Well, I had a lot of faulty renders until I realized that disabling num_frames made it work. The value might have been 48.

[a-r-r-o-w]

Yes, unfortunately the I2V model doesn't support anything other than 49 frames. I missed this initially so opened a patch PR to fix. Thanks for reporting!

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread.

Please note that issues that do not follow the contributing guidelines are likely to be ignored.

[a-r-r-o-w]

Marking as closed because does not make sense to guard the value any more because of the 1.5 checkpoints that support 81 and 161 frames as well