5 hours ago
I was able to reproduce your problem.
I installed VapoursynthR76_torch_2026.05.25.7z with R76 (shit!)
With the debugger I discovered that the filter is blocked by this piece of code
Inside the function RefImageReader2.get_clip_ref_list() in colormnet2_utils.py
There is nothing of special here, and in R74 (and older versions) this code is working perfectly and run in less than 1 second.
They're probably starting to use Artificial "Dementia" (stochastic code generators that seem to work), that introduced some kind of deadlock.
My suggestion: revert to R74 and stop to update VapourSynth for at least 10 years (when people will probably have forgotten about the existence of API3/API4).
There is nothing that I can do to solve this kind of VapourSynth's bug.
Dan
I installed VapoursynthR76_torch_2026.05.25.7z with R76 (shit!)
With the debugger I discovered that the filter is blocked by this piece of code
for i in range(0, self.clip_buffer_size):
frame = clip_sc.get_frame(i) <-- blocking code with i > 100
if frame.props['_SceneChangePrev'] == 1:
self.ref_num_list.append(start_frame + i)
self.num_ref_imgs += 1Inside the function RefImageReader2.get_clip_ref_list() in colormnet2_utils.py
There is nothing of special here, and in R74 (and older versions) this code is working perfectly and run in less than 1 second.
They're probably starting to use Artificial "Dementia" (stochastic code generators that seem to work), that introduced some kind of deadlock.
My suggestion: revert to R74 and stop to update VapourSynth for at least 10 years (when people will probably have forgotten about the existence of API3/API4).
There is nothing that I can do to solve this kind of VapourSynth's bug.
Dan

