Yesterday, 21:07
Quote:I believe I remember a thread somewhere that discussed why vs viewer takes so much longer to display vs the viewer that StaxRip uses, and believe it had something to do with scanning the movie and/or building some sort of model from it before the filters are applied and the preview shows.Whether index files are created depends on the source filter used.
Different source filters can be faster or slower building indexes depending on the source.
All source filters that create indexes will read through the whole file to create the index.
No clue what StaxRip uses for preview (maybe mpv?), but any meaningful speed differences are probably down to using a different or differently configured source filter.
Quote:Is there a way to change the behavior so that models are not built before display?Use a different source filter.
Quote:Is there a way to change the behavior so that models are not built before display?Interference of machine learning models only takes place if these are used and unless you use filters from the torch- or vsmlrt-add-on (or REALESRGAN) those are created since the filters are not used. vsmlrt works fine with Intel and AMD cards, only the torch-add-on uses CUDA.
Quote:What if a user only uses Hybrid for video filters, that do not leverage any cuda?Then no engine files or similar are created.
Quote:On another note, I am hoping that someday ZLUDA may help AMD gpus run CUDA based video filters.Yes, but last I checked it was nowhere near usable.Are you familiar with it at all
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.


Are you familiar with it at all