That wiki links to: https://github.com/vapoursynth/bestsource
about vfr: https://github.com/vapoursynth/bestsource/issues/9
Seeing that there have been changes in the last few weeks it seems like myrsloik is still working on it.
They added actions which produce builds on each change, so there are updated binaries.
=> I'll look at it, but atm. I probably wouldn't recommend using it.
(one downside: you can't create the index file in advance, there is no alternative to ffindex, so first loading might be slow)
Documentation:
Cu Selur
about vfr: https://github.com/vapoursynth/bestsource/issues/9
Seeing that there have been changes in the last few weeks it seems like myrsloik is still working on it.
They added actions which produce builds on each change, so there are updated binaries.
=> I'll look at it, but atm. I probably wouldn't recommend using it.
(one downside: you can't create the index file in advance, there is no alternative to ffindex, so first loading might be slow)
Documentation:
Quote:hwdevice: The interface to use for hardware decoding. Depends on OS and hardware. On windows d3d11va and cuda are probably the ones most likely to work. Defaults to CPU decoding. Will throw errors for formats where hardware decoding isn't possible.also does not really list what values are available for hardware decoding,.. :/
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.