VSFilterMod

[z0rc]

https://code.google.com/p/vsfiltermod/

Continuation of VSFilter. New features, x64 builds and minor bugfixes. Detailed information on wiki.

If you have any bugreports, suggestions or feature requests, then fill a ticket on project's site.

[b66pak]

thanks...
_

[tetsuo55]

Hello z0rc,

First of i think its great news that someone has stepped up to work on vsfilter.

I am the project manager for MPC-HC.
We have been looking for vsfilter devs for a very long time.

Maybe you have tried to contact us without any response, if so then i appologise for that, we are having problems with contact through sourceforge.

We currently have 2 volunteers who are working on vsfilter behind the scenes, and we have some big plans for it.

I would formally like to invite you to join team mpc-hc and work on the subtitle renderer as part of the team.

[jiifurusu]

I am the current lead developer of Aegisub, and has also done some development on VSFilter, mostly in 2008 where I introduced several extensions, in addition to fixing a number of rendering bugs.

Edit: For a more detailed opinion, please see this blog post: http://blog.aegisub.org/2010/02/old-and-present-vsfilter.html

I recommend staying away from the extensions introduced in this third fork of VSFilter. (Third: The two other are Guliverkli2 and MPC-HC.) I would also highly recommend not using the extensions I made to VSFilter in 2008, despite them being in both Guliverkli2 and MPC-HC.
Aegisub will never support the extensions made in VSFilterMod.

I personally regret making feature additions to VSFilter myself in 2008, and in fact did it soon after releasing them. They were never meant to be used in subtitles distributed, though I should have seen that happening. The ASS format reached its essentially final form in 2004, and should ideally not have changed since then.

So I beg: Please do not use the extensions.


The ASS format is bad in many ways, and the way to make it better is not to smack more mud on the already huge ball it is. The only solution is to create a new format from scratch, with proper specifications and have the community involved in the development, of course.

[sneaker_ger]

While we're at it: kumaji status?

[roozhou]

@jfs
Even the "bad" ASS format is not fully supported by VSFilter. Many useful features are still missing, e.g. [Graphics] section and picture event. Subtitlers have to use inefficient drawing commands to "draw" logos.

[jiifurusu]

roozhou:
I consider the ASS format to be defined by what VSFilter supported and rendered in 2004, not any document, that's simply how things ended up. Extending things won't make anything any better, because a large base of users won't be able to view the effects, picture or whatever the extensions specify.
I hope you can agree with me that subtitles need to be rendered exactly the same regardless of who is viewing them and on what system they are displayed. Just things such as difference in text size and line wrapping can have a major effect on readability, and is in fact one of the failings of most simple, unstyled text formats. (For that purpose, boldface and italics don't really count as styling, by the way.) Any kinds of extensions to a format not supported by and agreed on by every renderer, and supported by the great majority of viewers' software, breaks that assumption.
The real argument here is: Do not use those extensions, because you cannot be sure your viewers will see what you intended for them to see.


As for Kumaji... well I did make a commit a short time ago, but it was really just things I had had sitting for a long time :( Aegisub takes up too much of my time.

[[ReX]]

It would be nice if you could make it not crash while being loaded along with the video in Subtitle Workshop using Windows 7.

That doesn't happen when using VSFilter 2.33 :confused:, but the subs look ugly when using that version.

I'm not sure what's the cause, but if you could take a look at it, I'm willing to help.

[roozhou]

roozhou:
I consider the ASS format to be defined by what VSFilter supported and rendered in 2004, not any document, that's simply how things ended up.
Of course we need a document, and it is already there. How do you define "what VSFilter supported and rendered in 2004"? And VSFilter being windows-only makes things even worse.


I hope you can agree with me that subtitles need to be rendered exactly the same regardless of who is viewing them and on what system they are displayed.
Totally agreed, and I hope it will be bit-exact. We need a well-documented spec plus a full-featured, open-source and cross-platform reference subtitle renderer instead of a buggy windows-only software. Many SAP and LCD-TV manufacturers in China are trying to support ASS subtitles in their hardware. They don't need de factor standard because they cannot magically port VSFilter(full of MFC and GDI craps) to their chips.

[Vitaliy Gorbatenko]

Are there any plans to improve VSFilterMod? In particular, increase the speed of rendering subtitles with CUDA / DirectX? The current versions can not cope with a portrayal of the subtitles in 1080p video. I know that the MOD version is not for softsubs, but it though not much, but faster than normal.

[Katie Boundary]

Proper documentation for at least ONE of these filters would be nice.

[kedautinh12]

I found new improve of vsfiltermod
https://github.com/sorayuki/VSFilterMod/releases

[Selur]

Problem with that version seems to be that it does not work with Avisynth+ 3.5.1.
It doesn't crash, but it simple doesn't do anything, when using Avisynth MT 2.6 everything works fine.
(Sadly the issue tracker is disabled there, thus no clue where to report the issue.)

Cu Selur

[tormento]

Problem with that version seems to be that it does not work with Avisynth+ 3.5.1.
Perhaps because it's a VS filter? :confused:

[kedautinh12]

Problem with that version seems to be that it does not work with Avisynth+ 3.5.1.
It doesn't crash, but it simple doesn't do anything, when using Avisynth MT 2.6 everything works fine.
(Sadly the issue tracker is disabled there, thus no clue where to report the issue.)

Cu Selur
I use normally with this ver

https://github.com/sorayuki/VSFilterMod/releases

[Reel.Deel]

Problem with that version seems to be that it does not work with Avisynth+ 3.5.1.
It doesn't crash, but it simple doesn't do anything, when using Avisynth MT 2.6 everything works fine.
(Sadly the issue tracker is disabled there, thus no clue where to report the issue.)

Cu Selur


https://github.com/sorayuki/VSFilterMod/releases this version with Avisynth+ 3.5.1 works fine for me. I did notice that if you feed it a colorspace that is not supported the filter will simply not render any subtitles. No error message, just your original clip with w/o subtitles is returned.

Perhaps because it's a VS filter? :confused:

It's a dual-interface filter, supports AviSynth and VapourSynth.

[kedautinh12]

New fork of vsfiltermod
https://github.com/Masaiki/VSFilterMod

[kedautinh12]

VSfilterMod r5.2.7b (Vmoe mod)
https://github.com/computerfan/VSFilterMod/releases

[Katie Boundary]

No VobSub? No VSrip? This is just one tiny part of a package. Where's the rest of the package?

[kedautinh12]

VSfilterMod r5.2.7b (Vmoe mod)
Update for AviSynth+ (thank Asd-g)
Update the AviSynth headers
Add YUV420P10 and YUV420P16 support (ported from the VapourSynth version)
Set MT mode
Add parameter accurate (TextSubMod/VobSub/MaskSubMod)
https://github.com/kedaitinh12/VSFilterMod/releases/tag/r5.2.7-beta