View Full Version : mt_lut[] does not support [CPU] frame


color
8th March 2022, 10:25
I don't know why, but since I updated windows 10 to 11 and reinstalled avisynth+ and transfered all my plugins I started to get this Error message and I don't know why and how to fix or what I have done wrong?

Device unmatch: mt_lut[] does not support [CPU] frame

I get this with some plugins I use often, this is for an example that gives this error message:

f3kgrain(luma=64, chroma=64,mode=1, temp=50, adapt=64, sigma=1.0)
and
Grainfactory3(5,7,10)

kedautinh12
8th March 2022, 10:57
You can try some ex_ family from Dogway

f3kgrain:
https://github.com/kedaitinh12/AVSPlus-Scripts/blob/master/f3kgrain_v0.4MOD.avsi

Grainfactory3mod:
https://github.com/Dogway/Avisynth-Scripts/blob/master/MIX%20mods/GrainFactory3mod.avsi

It's request some script from Dogway to work

Extools:
https://github.com/Dogway/Avisynth-Scripts/blob/master/ExTools.avsi

ResizerPack:
https://github.com/Dogway/Avisynth-Scripts/blob/master/ResizersPack.avsi

Dogway
8th March 2022, 11:06
@kedautinh12, thanks for the free ad :P but the masktools issue should be fixed first.

@color: try to use mt_lut() calls and see where it fails.

kedautinh12
8th March 2022, 12:04
I think can use ex_lut in extools replace mt_lut :D

pinterf
8th March 2022, 12:16
Which AviSynth and masktools2 version is running.
Avsmeter64 -avsinfo lists them

color
8th March 2022, 12:25
You can try some ex_ family from Dogway

f3kgrain:
https://github.com/kedaitinh12/AVSPlus-Scripts/blob/master/f3kgrain_v0.4MOD.avsi

Grainfactory3mod:
https://github.com/Dogway/Avisynth-Scripts/blob/master/MIX%20mods/GrainFactory3mod.avsi

It's request some script from Dogway to work

Extools:
https://github.com/Dogway/Avisynth-Scripts/blob/master/ExTools.avsi

ResizerPack:
https://github.com/Dogway/Avisynth-Scripts/blob/master/ResizersPack.avsi

I will give it a try, sadly I use other scripts as well that gives the same error, so It's better to get it fixed if its possible, don't know if something changed in latest version in avisynth+ or windows 11 that made this. Or have I used wrong avisynth+?

AviSynthPlus_3.7.1_20211231-filesonly.7z 9.65 MB
AviSynthPlus_3.7.1_20211231.exe 8.45 MB <--
AviSynthPlus_3.7.1_20211231_vcredist.exe 37.1 MB
AviSynthPlus_3.7.1_20211231_vcredist_xp.exe 27.4 MB
AviSynthPlus_3.7.1_20211231_xp.exe 8.43 MB

@kedautinh12, thanks for the free ad :P but the masktools issue should be fixed first.

@color: try to use mt_lut() calls and see where it fails.

I did try only mt_lut() and it gives the same "Device unmatch: mt_lut[] does not support [CPU] frame"

I think can use ex_lut in extools replace mt_lut :D

I did try and I got problem with "U=U, V=V" that is used. I marked what does not work, I don't know how to rewrite as well:
ex_lut("x "+string(adapt)+" - abs 255 * "+string(adapt)+" 128 - abs 128 + /", U=1, V=1)

kedautinh12
8th March 2022, 12:31
Change u=1, v=1 become UV=1
If you use ex_lut need use avs+ 3.7.2 test 12
https://forum.doom9.org/showthread.php?t=181351

Btw, if you use my ver f3kgrain need 2 other script

F3KDB_sMOD:
https://github.com/kedaitinh12/AVSPlus-Scripts/blob/master/F3KDB_sMOD.avsi

Zs_RF_Shared
https://github.com/realfinder/AVS-Stuff/blob/Community/avs%202.5%20and%20up/Zs_RF_Shared.avsi

color
8th March 2022, 14:27
Change u=1, v=1 become UV=1
If you use ex_lut need use avs+ 3.7.2 test 12
https://forum.doom9.org/showthread.php?t=181351

Btw, if you use my ver f3kgrain need 2 other script

F3KDB_sMOD:
https://github.com/kedaitinh12/AVSPlus-Scripts/blob/master/F3KDB_sMOD.avsi

Zs_RF_Shared
https://github.com/realfinder/AVS-Stuff/blob/Community/avs%202.5%20and%20up/Zs_RF_Shared.avsi


Thank you. I just realized that QTMC gives the same error with mt_makediff. :/

kedautinh12
8th March 2022, 14:43
I think you can try QTGMC+
https://github.com/Dogway/Avisynth-Scripts/blob/master/MIX%20mods/QTGMC%2B.avsi

pinterf
8th March 2022, 15:04
Thank you. I just realized that QTMC gives the same error with mt_makediff. :/
Running avsmeter or avsmeter64 with avsinfo option is recommended to see what DLLs are used. Perhaps you have a very old plugin somewhere or multiple masktools2/mt_masktool dll.

color
8th March 2022, 15:38
Running avsmeter or avsmeter64 with avsinfo option is recommended to see what DLLs are used. Perhaps you have a very old plugin somewhere or multiple masktools2/mt_masktool dll.

OH!!! You are right! I am, I did have 2 masktools2 dll, :o one called "mt_masktools2", deleted that one and now it works! Thank you. I was almost pulling my hair. I don't know how it went up there. The other scripts works as they should now! :D

Thank you. :cool::rolleyes::p

pinterf
8th March 2022, 16:42
OH!!! You are right! I am, I did have 2 masktools2 dll, :o one called "mt_masktools2", deleted that one and now it works! Thank you. I was almost pulling my hair. I don't know how it went up there. The other scripts works as they should now! :D

Thank you. :cool::rolleyes::p
Great. Out of curiousity, could you upload your mt_masktools version for me, because this type of misbehaving (wrong or garbaged answer on an internal Avisynth child filter call) is handled in Avisynth+ but it seems it's not enough. Thanks.

color
8th March 2022, 16:58
Great. Out of curiousity, could you upload your mt_masktools version for me, because this type of misbehaving (wrong or garbaged answer on an internal Avisynth child filter call) is handled in Avisynth+ but it seems it's not enough. Thanks.

I have sent you the mt_masktool that gives error via PM