AvxSynth: a Linux port of AviSynth

[qyot27]

On the System Setup page on Github, both FFmpeg and FFMS2 have full checkinstall commands. And while the instructions there are geared toward the release tarballs and therefore have simple version numbers to parse, AvxSynth itself is left with a plain sudo make install.

The below is the checkinstall line I've been using for AvxSynth:

sudo checkinstall --pkgname=avxsynth --pkgversion="1:$(grep "Version" avxsynth.pc | \
    cut -f2 -d " ")+$(git rev-list HEAD | wc -l)-$(git rev-list HEAD -n 1 | cut -c 1-7)-$(date +%Y%m%d)" \
    --backup=no --deldoc=yes --fstrans=no --default

which results in:

$ sudo apt-cache show avxsynth
Package: avxsynth
Status: install ok installed
Priority: extra
Section: checkinstall
Installed-Size: 11356
Architecture: i386
Version: 1:4.0+137-b2eb3c3-20120625-1
Provides: avxsynth
Description: Package created with checkinstall 1.6.2

[Adub]

Hmm, that's a useful command you got there qyot27. I'll probably steal it once I get my new i7 Ubuntu rig up.

[sl1pkn07]

@qyot27: ubuntu?

to build package in ubuntu/debian: "dpkg-buildpackage -b" in avxsynt folder.. avxsynth have all to build package without checkinstall

[qyot27]

I know about the buildpackage support, but I can't be bothered to use it. The only users who should really care about making repository-safe packages are those maintaining a repo, not the casual user that just wants it logged in the package manager.

It still doesn't change the fact that if it were so important to use the 'Debian way' to build the package (which it really isn't, aside from repo maintainers), then it still doesn't explain why it's not given as the final step on the installation page, with make install used instead. And considering said installation page assumes the use of an Ubuntu system (as that's the distro AvxSynth development is targeted to anyway), either packaging method would be valid and superior to a plain make install.

[sl1pkn07]

is it more difficult:

dpkg-buildpackage
cd ..
sudo dpkg -i libavxsynth* avxedit*

instead of:

autoreconf -i
./configure
make

sudo checkinstall --pkgname=avxsynth --pkgversion="1:$(grep "Version" avxsynth.pc | \
    cut -f2 -d " ")+$(git rev-list HEAD | wc -l)-$(git rev-list HEAD -n 1 | cut -c 1-7)-$(date +%Y%m%d)" \
    --backup=no --deldoc=yes --fstrans=no --default

?

Use checkinstall instead of make install, because if you use make install, when deleting sources you may need to uninstall 2 method:

Rebuild sources and make uninstall (in the same prefix) or delete files installed one by one.

Using checkinstall (and dpkg-buildpackage) is easier than removing/updating the build using the system package updater. (apt-get, dpkg, packagekit,synaptic, etc)

[StainlessS]

I like the IDEA of LINUX, and the demise of MS, but really, not gonna happen any time soon.
If only Linux could differentiate between eg a word processor program and some other.
Under Windows, you might have a program called eg Office stuff, under Linux
it will almost certainly be called giraffe or duck billed or whatever..

I hate Windows, and Linux, but not in equal measure.

[sl1pkn07]

openoffice, libreoffice calligra.....

[StainlessS]

Can you suggest a solution for those unfortunate giraffe fixated users amongst us.

[Guest]

Let's stay on topic, guys.

[sl1pkn07]

oh. sorry (the offtopic). giraffe is a circuit simulator?

ktechlab?

[sl1pkn07]

okidoki

[StainlessS]

sl1pkn07, Open source?
Maybe like Spice. Nice Spice simulator would be well good.

[e1897876]

Hello,

Does someone know if it is somehow possible to get the following AviSynth script working with AvxSynth (or which lines will work at least)? The functions (.avsi) used here are attached. I think, the video source could be modified as ffdshow tryouts doesn't exist under Linux.

setmtmode(5,0)
SetMemoryMax(512)
video=ffdshow_source().changefps(ffdshow_source(), linear=true)
A=video
setmtmode(2)
SetMemoryMax(712)
B=a.SPresso_JD()
C=a.SeeSaw_JD(B).LimitedSharpenFaster_JD(strength = 11)
return C
GetMTMode(false) > 0 ? distributor() : last

The other way round would be OK, too: will
- RemoveGrain-1.0
- masktools-v2.0a35
- mvtools-v2.5.11.3
- VariableBlur040
- warpsharppackage_25_dll_20031103
somehow be available with AvxSynth? That would be great!

If that should be a dead end, has someone an idea which combination of ported filters (Built-in-Functions) would offer similar functionality?

Thanks for helping and regards.

[e1897876]

Really guys, no ideas?

[sl1pkn07]

Originally Posted by e1897876

The other way round would be OK, too: will
- RemoveGrain-1.0
- masktools-v2.0a35
- mvtools-v2.5.11.3
- VariableBlur040
- warpsharppackage_25_dll_20031103
somehow be available with AvxSynth? That would be great!

only exist port for Removegrain and masktools, but don't work

to load video use ffmpegsource instead ffdshow (only windows)

all "set" modes don't exist in avxsynth

[e1897876]

OK for now, thanks for those hints.

[btb]

AvxSynth working on OSX, for anyone interested

https://github.com/avxsynth/avxsynth/issues/83

[videophool]

Originally Posted by btb

AvxSynth working on OSX, for anyone interested

https://github.com/avxsynth/avxsynth/issues/83

Excellent contribution. Thanks.

[Adub]

Hmm, I'm currently doing some research on the innards of AvxSynth, specifically the Cache and InternalCache mechanisms. Is there any documentation anywhere about their internal use for the built in functions? Is the Cache used by default throughout the full filter chain, or is it a more pick and choose situation per filter?

For context, I'm going to start work on porting some of the built in functions to CUDA (specifically the ones with disabled MMX and SSE) for some academic research, and if I can modify the internal cache in such a way so that I can keep the frame data on the GPU as long as possible, the greatest performance gains will be achieved. Otherwise if we are sending the frames back and forth across the bus, we lose a lot of speed due to the extra transmission overhead.

[mandarinka]

If you care about unix environments, Vapoursynth is probably much more viable project to contribute to: http://forum.doom9.org/showthread.php?t=165771