Selur's Little Message Board

Selur's Little Message Board > Hybrid - Support > Problems & Questions > Color>Basic>Smooth Level ERROR
Full Version: Color>Basic>Smooth Level ERROR
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2

NoahLoot

19.06.2026, 07:28
Hello,

Since the installation of hybrid 2026.06.18.1  i get the following error to see when Smooth Level collor correction is enabled.

[Image: smooth-color-error.png]

Code:
2026-06-19 07:20:18.185 Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll is using API3 which is deprecated and will be removed shortly. 2026-06-19 07:20:37.801 Script was successfully evaluated. Output video info: Frames: 3110 | Time: 0:51:50.000 | Size: 3840x1080 | FPS: 1/1 = 1 | Format: YUV420P8 2026-06-19 07:20:37.840 Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll is using API3 which is deprecated and will be removed shortly. 2026-06-19 07:21:26.013 [VSE Server]: incoming connection [VSE Server]: ConnectedState [VSE Server]: socket is ready to be read [VSE Server]: connection open: true [VSE Server]: connection readable: true [VSE Server] - Message received: changeTo ### E:\TEMP\FRINGE\tempPreviewVapoursynthFile07_21_25_995.vpy ### 2026-06-19 07:21:26.020 Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll is using API3 which is deprecated and will be removed shortly. 2026-06-19 07:21:26.422 Script was successfully evaluated. Output video info: Frames: 3110 | Time: 0:51:50.000 | Size: 3840x1080 | FPS: 1/1 = 1 | Format: YUV420P8 2026-06-19 07:21:26.529 Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll is using API3 which is deprecated and will be removed shortly. 2026-06-19 07:21:39.003 [VSE Server]: socket is ready to be read [VSE Server]: connection open: true [VSE Server]: connection readable: true [VSE Server] - Message received: changeTo ### E:\TEMP\FRINGE\tempPreviewVapoursynthFile07_21_38_985.vpy ### 2026-06-19 07:21:39.017 Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll is using API3 which is deprecated and will be removed shortly. 2026-06-19 07:21:39.435 Script was successfully evaluated. Output video info: Frames: 3110 | Time: 0:51:50.000 | Size: 3840x1080 | FPS: 1/1 = 1 | Format: YUV420P8 2026-06-19 07:21:39.559 Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll is using API3 which is deprecated and will be removed shortly. 2026-06-19 07:21:49.086 [VSE Server]: socket is ready to be read [VSE Server]: connection open: true [VSE Server]: connection readable: true [VSE Server] - Message received: changeTo ### E:\TEMP\FRINGE\tempPreviewVapoursynthFile07_21_49_069.vpy ### 2026-06-19 07:21:49.098 Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll is using API3 which is deprecated and will be removed shortly. 2026-06-19 07:21:49.488 Script was successfully evaluated. Output video info: Frames: 3110 | Time: 0:51:50.000 | Size: 3840x1080 | FPS: 1/1 = 1 | Format: YUV420P8 2026-06-19 07:21:49.602 Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll is using API3 which is deprecated and will be removed shortly. 2026-06-19 07:22:02.134 [VSE Server]: socket is ready to be read [VSE Server]: connection open: true [VSE Server]: connection readable: true [VSE Server] - Message received: changeTo ### E:\TEMP\FRINGE\tempPreviewVapoursynthFile07_22_02_127.vpy ### 2026-06-19 07:22:02.155 Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll is using API3 which is deprecated and will be removed shortly. 2026-06-19 07:22:02.572 Script was successfully evaluated. Output video info: Frames: 3110 | Time: 0:51:50.000 | Size: 3840x1080 | FPS: 1/1 = 1 | Format: YUV420P8 2026-06-19 07:22:02.718 Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll is using API3 which is deprecated and will be removed shortly. 2026-06-19 07:22:20.084 [VSE Server]: socket is ready to be read [VSE Server]: connection open: true [VSE Server]: connection readable: true [VSE Server] - Message received: changeTo ### E:\TEMP\FRINGE\tempPreviewVapoursynthFile07_22_20_072.vpy ### 2026-06-19 07:22:20.102 Plugin C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll is using API3 which is deprecated and will be removed shortly. 2026-06-19 07:22:20.535 Failed to evaluate the script: Python exception: No attribute with the name f3kdb exists. Did you mistype a plugin namespace or forget to install a plugin? Traceback (most recent call last): File "vapoursynth.pyx", line 3623, in vapoursynth._vpy_evaluate File "vapoursynth.pyx", line 3624, in vapoursynth._vpy_evaluate File "E:\TEMP\FRINGE\tempPreviewVapoursynthFile07_22_20_072.vpy", line 54, in clip = color.SmoothLevels(clip, input_low=16, input_high=235, output_low=16, output_high=235, gamma=1.00, chroma=50, limiter=0, Lmode=3, BrightSTR=100, Ecenter=128, protect=-1, Ecurve=1, Smode=0, Mfactor=2, RGmode=12, useDB=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Program Files\Hybrid\64bit\vsscripts\color.py", line 317, in SmoothLevels deband_func = core.vszip.Deband if hasattr(core, 'vszip') else core.neo_f3kdb.Deband if hasattr(core, 'neo_f3kdb') else core.f3kdb.Deband ^^^^^^^^^^ File "vapoursynth.pyx", line 3117, in vapoursynth._CoreProxy.__getattr__ File "vapoursynth.pyx", line 2933, in vapoursynth.Core.__getattr__ AttributeError: No attribute with the name f3kdb exists. Did you mistype a plugin namespace or forget to install a plugin?

This is what the Log reports.



I hope "smooth level" is still supported..

Thank you in advance,

Selur

19.06.2026, 13:59
Yeah, I just adjusted tons of scripts to support newer filters, and I made some mistakes. Smile
Uploaded a new dev, let me know whether that fixes the problem for you.

Cu Selur

NoahLoot

19.06.2026, 16:27
(19.06.2026, 13:59)Selur Wrote: [ -> ]Yeah, I just adjusted tons of scripts to support newer filters, and I made some mistakes. Smile

Ah.. i thought as much..  
Iam glad the filter is still supported though 👍🏽.  


(19.06.2026, 13:59)Selur Wrote: [ -> ]Uploaded a new dev, let me know whether that fixes the problem for you.

Cu Selur

SPLENDID 😉👌🏽

One other thing...

I did a fresh install of hybrid (dev/experimental).  
And for some reason hybrid still doesn't create an hybrid log in my output folder.. 

Output folder is the same as my Destination folder... may that be the reason.. ?
But then again, in the past that wasn't an issue, and hybrid did created the log anyway regardless of path logic.

Anyway, the previous install of hybrid was the latest "stable" version, and it didn't created any logs either ..  
Even though the option "Create Debug File" is toggled on always .

Also, when i refresh the hybrid install... will it keep using the old VapourSynth folder flawless !?
Or do i have to move over that huge torch addon pack everytime i update hybrid ?

At the moment iam using torch VapoursynthR77_torch_2026.06.16 + Hybrid_dev_2026.06.18-193220 🙂


Thank you , come again  Big Grin

Selur

19.06.2026, 16:35
Quote: Even though the option "Create Debug File" is toggled on always .
Don't do that, especially newer versions while create increasingly large files, which will slow down everything.

Quote: Output folder is the same as my Destination folder... may that be the reason.. ?
Maybe, I don't use the option, but when loading a new file, which temporarily would clear the output folder, could break the debug processing.


Cu Selur

NoahLoot

19.06.2026, 16:46
(19.06.2026, 16:35)Selur Wrote: [ -> ]
Quote: Even though the option "Create Debug File" is toggled on always .
Don't do that, especially newer versions while create increasingly large files, which will slow down everything.

I meant, atm the toggle is alway's on to figure out why it doesn't create an log!?
When everything works just fine, it's always disabled by me hands.  That's what i meant to say.

Regarding this issue, in the meanwhile i gave special permissions to the user of my current windows 11 25h2 account..  
ie: write/modify = enabled..  But that doesn't seem to remedy the problem either !!

i also disabled windef temporarely to check and see if that is preventing hybrid from creating an debug..
That doesn't seem to have any affect either !

So.. i wonder... is the debug file created in another folder other than the output folder ?


(19.06.2026, 16:35)Selur Wrote: [ -> ]
Quote:Output folder is the same as my Destination folder... may that be the reason.. ?
Maybe, I don't use the option, but when loading a new file, which temporarily would clear the output folder, could break the debug processing.


Cu Selur

I will change folder paths manual to check and see if that resolves anything.
Right after its done processing the current job  Big Grin 


Tbh, the latest stable install of hybrid didn't created an debug file either.. or atleas i haven't found it at the usual place..



Thanks anyway,

Selur

19.06.2026, 16:49
Best set a fixed folder for the debug output (same for temp) and set it somewhere out of the normal windows folders.

NoahLoot

19.06.2026, 16:55
(19.06.2026, 16:49)Selur Wrote: [ -> ]Best set a fixed folder for the debug output (same for temp) and set it somewhere out of the normal windows folders.

I will try that , thank.

Just an fyi.. i never use my system partition as storage / workspace for video editing..
For that i use an sepperate nvme m.2 ssd storage.

Also, i've checked in Windows explorer and searched for *debug files at the usual places to see if any debug files would popup..
And , explorer did find debug files... But did not found the one that matters Big Grin .. 

Meaning, hybrid most likely isn't creating any debug files at all even though its toggled on !!

ps: waiting for google drive to DL the new dev and trying it out. ie: DL limit 🥴!
As soon i've installed the new dev , i'll report back.

thanks,

Selur

19.06.2026, 17:06
Quote: Meaning, hybrid most likely isn't creating any debug files at all even though its toggled on !!
If Debug output once doesn't have a folder it will not look again unless its toggled of and on again.

NoahLoot

19.06.2026, 17:14
(19.06.2026, 17:06)Selur Wrote: [ -> ]
Quote: Meaning, hybrid most likely isn't creating any debug files at all even though its toggled on !!
If Debug output once doesn't have a folder it will not look again unless its toggled of and on again.

Ah.. weird..

So if i understand correct..  It won't search & look again, even after an hybrid restart ?

That makes sense.. 

But i have thought about that too, and used the toggle switch and then restarted hybrid..  Outcome, still no debug file  Huh


I'll keep you posted..

tanks

Selur

19.06.2026, 17:27
Quote: I guess your finding is related to the debug situation .. ?
No it will look after a restart, but then the output folder is again empty,... so it will break again.

=> set a dedicated folder for the debug output if you want to adjust the output folder to the input folder.

Cu Selur
Pages: 1 2
Selur's Little Message Board > Hybrid - Support > Problems & Questions > Color>Basic>Smooth Level ERROR