Log in

View Full Version : avisynth syntax file for VIM


Randall
1st December 2005, 16:55
I have taken it upon myself to write a syntax file for VIM for the avisynth scripts. If you edit your avisynth scripts using VI, VIM, or GVIM, then feel free to download my syntax file, which you can find here. http://www.vim.org/scripts/script.php?script_id=1418 Instructions for installation are found on that page. I have tried to include every plugin/filter for avisynth known to man, but there are new ones coming out all of the time, so I will be updating accordingly. I find that my AVS scripts are much easier to read now, and I hope that you find this useful for your encodings. Enjoy.

iradic
1st December 2005, 21:23
thanks

Fizick
2nd December 2005, 14:57
Recently we created Avisynth syntax file also for Colorer-take5 plugin for FAR Manager text editor (console).
IMHO, we must add this info to some sticky thread.

Mug Funky
2nd December 2005, 15:06
cool. i like coloured scripts - that way you've got a better idea something's going to work before you crash some poor media player with a buggy script.

it's too bad nobody's developing virtualdubmod anymore, as the f5 key is a real godsend there (save+reload script to the current frame. good for minor adjustments).

Randall
2nd December 2005, 17:30
no problem guys. glad to see that my effort was appreciated :-)

Wilbert
2nd December 2005, 17:44
it's too bad nobody's developing virtualdubmod anymore, as the f5 key is a real godsend there (save+reload script to the current frame. good for minor adjustments).
I agree :) You know about latest VDub and the F2 key?

@Fizick,

http://bag.hotmail.ru/colorer/avscolorer.dhtml

gives 404.

tsp
2nd December 2005, 17:51
I agree :) You know about latest VDub and the F2 key?

It's buged when using avisynth. It doesn't close the file/script first (or whatever happends) so the memory is not freed. This is with version 1.6.11.

Fizick
2nd December 2005, 18:26
Wilbert,
Oops.
Link are fixed now.

Richard Berg
2nd December 2005, 21:37
It's buged when using avisynth. It doesn't close the file/script first (or whatever happends) so the memory is not freed. This is with version 1.6.11.
I've found this too. Is Avery aware?

tsp
2nd December 2005, 21:57
I posted a thread about it in the Unofficial VirtualDub Support Forums (http://forums.virtualdub.org/index.php?act=ST&f=15&t=11178&) so he will see it.

tsp
4th December 2005, 00:45
hmm seems that virtualdub first open the file before closing the old file so that caused fft3dgpu to fail (out of videomemory). Also fft3dfilter 1.8.4 is leaking about 8 MB every time the file is reopened. That combined with the reg key handle (http://sourceforge.net/tracker/index.php?func=detail&aid=1369416&group_id=57023&atid=482673) that are never closed looked a little suspicious.
So no bug in virtualdub.

Fizick
4th December 2005, 01:49
tsp,
it is offtopic here.
Dot not scare users in Avisynth usage forum :)

Randall
5th December 2005, 20:42
*UPDATE* Added syntax support for the BlendBob() function

Let me know if you guys add any of your own filters or functions that are not in the syntax list, and I will be sure to update the script.