You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No matter how I modify the timestep, the frame generated by demo_2x.py is always 0.5. Even when I change the timestep parameter in the inference function in Trainer_x4k.py, the generated frame is always 0.5 with no changes at all.
The text was updated successfully, but these errors were encountered:
This is because the provided checkpoints are trained in a fixed-timestep manner. Following most current VFI work, we use vimeo_triplet (input: t=0,1; target: t=0.5) as the pre-training dataset. Moreover, when fine-tuning on X-Train, we also use t=0.5 as the prediction target. So if you are looking for the results of other timesteps, I would recommend the following two solutions:
Try other excellent works which are trained on more arbitrary timestep datasets, like vimeo_septuplet containing 7 consecutive frames. i.e. EMA-VFI-t, RIFE_m.
No matter how I modify the
timestep
, the frame generated bydemo_2x.py
is always 0.5. Even when I change thetimestep
parameter in theinference
function inTrainer_x4k.py
, the generated frame is always 0.5 with no changes at all.The text was updated successfully, but these errors were encountered: