01.11.2021, 20:13
New placement of vsViever Auto refresh button looks great!
[GUIDE] VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS
|
01.11.2021, 20:13
New placement of vsViever Auto refresh button looks great!
01.11.2021, 21:28
ResampleHQ resizer error:
Failed to evaluate the script:
01.11.2021, 21:32
What does the Vapoursynth script look like?
Just tried with a random source and had no problem. Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
01.11.2021, 21:36
AddLogo error:
2021-11-01 21:33:57.617 (01.11.2021, 21:32)Selur Wrote: What does the Vapoursynth script look like? # Imports Seems ResampleHQ resizer gives error only when used deinterlacer. No error if i use progressive source.
I can reproduce this.
Seems like a problem with the imwri filter. [logo, alpha] = core.imwri.Read(filename="/Users/aaa/Desktop/No name.png", alpha=True) -> added a post over at doom9 in the Vapoursynth thread (https://forum.doom9.org/showthread.php?p...ost1956378) since the filter is maintained by myrsloik. --- about ResampleHQ: Try whether adding "clip = core.std.SetFieldBased(clip, 0)" before the resampleHQ line helps. -> forget that, I overlooked the line, it's already there. Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page. # making sure input color matrix is set as 709 may be a new fmtconv is needed? Will try to look at it on Wendsday after work. No time tomorrow. Going to bed now. Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
01.11.2021, 22:02
So i checked all filters for vsViewer errors. Seems all works same as before.
KNLMeansCL produce same artifacts as before. I didn't touch other KNLMeansCL settings to check if it still produce kernel panic. Also same as before i used MVTools v21. As i noticed earlier in R54 and earlier VS versions MVTools v22 and v23 produce error on render "crashed: Helper1, exitCode: 11" I didn't check MVTools v22 and v23 with R57 yet, but guess it will produce the same error. ResampleHQ resizer gives error only when used deinterlacer. No error if i use progressive source. Maybe some conflict with resize settings in Hybrid? I will send you a debug.
02.11.2021, 06:06
Strange mvtools is used in tons of scripts. -> I doubt the issue is with mvtools otherwise preview wouldn't work with a ton of the scripts.
Can't check about KNLMeansCL due to lack of gpu support in my vm. -> will look into the mvtools and resamplehq problem if you share a separate debug output for each. (got no issues on Windows, so this might be an issue with the libraries) Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
02.11.2021, 06:55
Seems no more error with MVtools-v23. (it happened when use QTGMC preset "Placebo" in Hybrid. Render started, but after some short time it stopped with error. "crashed: Helper1, exitCode: 11") Problem was reported 15th August 2020 http://forum.doom9.net/showthread.php?s=...ost1921113 and also it was reported earlier by other people few times. From that time i only used MVtools-v21. As i remember last time i tested MVtools-v23 with R53 and it give me same error. So i have no idea if problem fix was in newer Hybrid or in newer Vapoursynth version.
What does "after some short time" mean? 1min 20min 50min ?
That sounds more like a memory, heat, problem, but could also be a bug triggered on your system. Atm. I see no way to reproduce this. -> can't reproduce this here. (QTGMC Placebo doesn't seem to crash in my VM, I let it run for 30min) Also you might want to report to https://github.com/dubhater/vapoursynth-mvtools with details about your cpu&co. Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page. |
« Next Oldest | Next Newest »
|