Package Details: vapoursynth-plugin-scenechange 0.2.0_2-8

Git Clone URL: https://aur.archlinux.org/vapoursynth-plugin-scenechange.git (read-only, click to copy)
Package Base: vapoursynth-plugin-scenechange
Description: Plugin for Vapoursynth: scenechange
Upstream URL: http://forum.doom9.org/showthread.php?t=166769
Keywords: vapoursynth
Licenses: LGPL2.1
Submitter: sl1pkn07
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 4
Popularity: 0.000000
First Submitted: 2013-01-07 21:18
Last Updated: 2019-03-15 23:56

Latest Comments

« First ‹ Previous 1 2

jose1711 commented on 2015-07-14 08:36

a failure occurred in build()

alucryd commented on 2014-02-13 10:14

Well, fortunately you don't need tons of filters when you work with clean sources, and as far as animation goes, I'm happy just having a deband filter and a temporal denoiser :P

sl1pkn07 commented on 2014-02-13 10:11

The Avisynth's shadow is still very big...

jackoneill commented on 2014-02-13 09:57

"Finally, if I find I can fully replace Avisynth on Windows with Vapoursynth on Linux, I'll push vapoursynth to [community] along with the stable plugins"

Fully? Probably not for a while. There are still lots of Avisynth plugins with no VapourSynth equivalent.

alucryd commented on 2014-02-12 13:32

Hmm, I wasn't aware a CUDA fork existed. Even if the patches end up upstream, I assume a CUDA enabled build won't work on hadware other than NVIDIA, so imho you should name that one vapoursynth-cuda and keep plugin in the name for the plugins then.

alucryd commented on 2014-02-12 13:30

Hmm, I wasn't aware a CUDA fork existed. Even if the patches end up upstream, I assume a CUDA enabled build won't work on hadware other than NVIDIA, so we better keep plugin in the name then.

sl1pkn07 commented on 2014-02-12 12:54

oki.

BTW, I had plan (when finished) upload vapoursynth package build with CUDA support (fork by Adub in doom9.org), this is not a plugin, is a replace normal vapoursynth. with what name should be uploaded?

greetings

alucryd commented on 2014-02-12 12:12

Hey, since there were no signs of Chikuzen hosting this anywhere, I've created 2 repos to host the Scene Change and Temporal Soften 2 plugins source code, and added proper build scripts (a modified version of those found in the Generic Filters), and made them use system VapourSynth.h instead of the one provided. Mind that I'm not pursuing development of the plugins, I just wanted a better place to host them. You can create a new package for temporalsoften2 since that one is at version 0.1.1, not 0.2.0.

I will add a provides=('vapoursynth-ffms2') in ffms2 from [community] and symlink the lib to '/usr/lib/vapoursynth' the next time I update it, so you can remove the corresponding package from AUR (I'll tell you when it's done), a package with just a symlink is kinda pointless. You should do the same in ffms2-git as well.

Finally, if I find I can fully replace Avisynth on Windows with Vapoursynth on Linux, I'll push vapoursynth to [community] along with the stable plugins, and name them vapoursynth-${plug}, we can lose the plugin bit, they are obviously plugins.

Repos (with tagged releases):
https://github.com/alucryd/vapoursynth-scenechange
https://github.com/alucryd/vapoursynth-temporalsoften2

New PKGBUILDs (you can lose the git part):
https://github.com/alucryd/aur-alucryd/tree/master/personal/vapoursynth-scenechange-git
https://github.com/alucryd/aur-alucryd/tree/master/personal/vapoursynth-temporalsoften2-git