Selur's Little Message Board

Almost everytime I upgrade to a new dev version, when I load a Vapoursynth preset, I have a ton of annoying warning popups appearing. It's repeating when adding to queue too.

Maybe that's because things are being removed from version to version.

Load and Save your preset. Then restart and the issue should be gone.
If not, read the sticky, share details,...

It doesn't work.

- Hybrid 2024.11.23.1, Windows 10 64-Bit

- Currently, there are three error popups, cycling and repeating many times (I think not found lines can change between Hybrid versions) :

Found not field : vsCustomVSGANFilter
Found not field : vsCustomGRLIRFilter
Found not field : vsCustomSAFAmlrt

- To reproduce : load any video, then, apply a Vapoursynth preset saved with an older Hybrid version (here is a link of the buggy preset Drive)

It is strange that loading and re-saving the model does not fix the problem, since those elements should not be there if the torch addon is not there.
Your json does contain them and tons of other values that should not be there.
Using dev 2024.21.1 I put your model inside the profiles/scripts/vapoursynth folder and loaded it without any popups.
=> can't reproduce

Also try:
1. loading the preset (clicking all the errors away)
2. resetting the Vapoursynth filter order
3. re-saving the preset.
=> if you can reproduce your problem with 2024.21.1 create a debug output like the sticky states.



Cu Selur

Your method of resetting filter order queue then resaving the .json works. I can reload it without issues.

As you can see, this method removes things that should not be there :



Here is the Debug output created after adding to queue : DebugOutput

No need for a debug output if that method works.
Also, like I mentioned, I can't reproduce the problem at all with the 2024.11.21 dev version.

Cu Selur

I had this problem since I start using Hybrid, like maybe in August.
As soon as I update, my old presets won't load without popups issues.

Maybe what you can do is install a fresh old Hybrid dev version (like say from a month ago), create a VS preset, then update Hybrid with last dev above it, and load the preset (if you want to do it, because it means uninstalling what you have).

Quote:I had this problem since I start using Hybrid, like maybe in August.

And since no one reported it, it didn't get fixed. It should be fixed in the latest dev, but it is always advised to resave presets&co after an update. Also if the changelog mentions that resetting all presets&co is necessary, it usually is.

Cu Selur

Quote:And since no one reported it, it didn't get fixed. It should be fixed in the latest dev, but it is always advised to resave presets&co after an update. Also if the changelog mentions that resetting all presets&co is necessary, it usually is.

Alright, I'll keep that in mind.