(13.01.2024, 23:32)Selur Wrote: [ -> ]No, that was a typo 'now' -> 'not'.
Cu Selur
Ah i see... Happens to the best of us Sir Selur
So, i asume nothing can be done to cure the TRT issue of FemaSR atm ?
Pitty, it's crucial to speed up the process considerable
cheers,
TD
(14.01.2024, 14:37)Selur Wrote: [ -> ]Aside from asking HolyWu to look into (https://github.com/HolyWu/vs-femasr/issues/6) or writing your own port: No
First of , that's quite an long log you've posted Holy Moly Sacrimony
!
Second, the resizer hardly utilize half of the vram in my experience.. that doesn't fly .. yet i have had out of memory warnings aswell , even though my gpu had like 60 - 70% unused vram left
And yes, i wos thinking in the line of using an ported version of femaSR if there's any floating the net ...
cheers,
TD
Quote:And yes, i wos thinking in the line of using an ported version of femaSR if there's any floating the net ...
afaik.
https://github.com/HolyWu/vs-femasr is the only way to use FeMaSR in Vapoursynth.
Cu Selur
(14.01.2024, 14:46)Selur Wrote: [ -> ]Quote:And yes, i wos thinking in the line of using an ported version of femaSR if there's any floating the net ...
afaik. https://github.com/HolyWu/vs-femasr is the only way to use FeMaSR in Vapoursynth.
Cu Selur
I have checked that page, thanks nonetheless..
What about Avisynth / avisynth+ possibilities ?
I guess, vapoursynth is superior to avisynth in terms of multithreading / cache / memory .etc .. But beside that ...
cheers,
TD
Quote:What about Avisynth / avisynth+ possibilities ?
In theory everything is possible.
(14.01.2024, 15:58)Selur Wrote: [ -> ]Quote:What about Avisynth / avisynth+ possibilities ?
In theory everything is possible.
"The Theory of Everything" → One To Watch
Cheers,
TD
Quote:I render twice since I tried to use Filter Queue to do everything once but a few errors have appeared...?
Not sharing how to reproduce the problem, won't get it fixed.