Vapoursynth

[asarian]

Blu-ray IDX/SUB filters (the kind extracted with BDSup2Sub, for example), is it possible to incorporate those in VS too?! That would be sweet, as I like my subs (like for Japanese material) to be unmodified.

EDIT: Looking for something like SupTitle.

[jackoneill]

Originally Posted by asarian

Blu-ray IDX/SUB filters (the kind extracted with BDSup2Sub, for example), is it possible to incorporate those in VS too?! That would be sweet, as I like my subs (like for Japanese material) to be unmodified.

EDIT: Looking for something like SupTitle.

I think there is no such filter for VapourSynth (yet?), but you can do it with mpv:

mpv video.mov --sub-file subtitles.idx --vf vapoursynth=script.py --ovc libx264 --oac libvorbis -o output.mkv

It will filter video.mov using script.py, then it will render the subtitles and encode the result with x264.

[asarian]

^^ Brilliant! Thank you!

[Myrsloik]

R32 has been released. Full changelog in the first post. The release has fixes not in the RC.

The usual blog post.

Mostly bug fixes, one of them important since it fixes caches not always being properly added since the nfMakeLinear addition in R30.

And interlaced resizing. Because the world is a horrible place.

[asarian]

Thank you!!

[asarian]

Hmm, how do I tackle this one?

vid = core.avisource.AVISource ("f:/jobs/test.avi")

Script evaluation failed:
Python exception: AVISource: couldn't locate a decompressor for fourcc DX50
Traceback (most recent call last):
  File "src\cython\vapoursynth.pyx", line 1491, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:26897)
  File "f:\jobs\test.vpy", line 7, in <module>
    vid = core.avisource.AVISource ("f:/jobs/test.avi")
  File "src\cython\vapoursynth.pyx", line 1383, in vapoursynth.Function.__call__ (src\cython\vapoursynth.c:25204)
vapoursynth.Error: AVISource: couldn't locate a decompressor for fourcc DX50

[stax76]

install either

DivX, XviD or ffdshow VFW decomressor

or use ffms2 or l-smash-works

[LigH]

Do you have a VfW decoder for DivX 5+ installed? (Assuming that AVISource requires installed VfW codecs as decoder...)

[stax76]

Originally Posted by LigH

Do you have a VfW decoder for DivX 5+ installed? (Assuming that AVISource requires installed VfW codecs as decoder...)

vs AVISource uses VFW like avs AVISource so vs AVISource can open avs for instance to use avs DGSource.

[asarian]

Originally Posted by stax76

install either

DivX or ffdshow VFW decomressor

or use ffms2 or l-smash-works

About the latter, 'core.lsmas.LWLibavSource' made the process crash immediately. I'll try ffms2, and I'll look into getting the other 2 to work with VS. Thanks!

Darn AVI! I hate that format!

[asarian]

'vid = core.ffms2.Source' can't make head or tails out of it either. It just keeps blabbing about needing to crop (and even when I do, it makes no difference):

Python exception: Crop: cropped area needs to have mod 2 height offset
Traceback (most recent call last):
  File "src\cython\vapoursynth.pyx", line 1491, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:26897)
  File "F:\jobs\test.vpy", line 9, in <module>
    vid = core.std.CropRel (clip=vid, left=0, right=0, top=1, bottom=0)
  File "src\cython\vapoursynth.pyx", line 1383, in vapoursynth.Function.__call__ (src\cython\vapoursynth.c:25204)
vapoursynth.Error: Crop: cropped area needs to have mod 2 height offset

[sneaker_ger]

"mod 2" means you can only achieve even numbers of pixel dimension. You cannot crop just one pixel away, you have to crop away 2 or 4 or 6 or 8 etc. This depends on the colorspace. For progressive YUV 4:2:0 you need to use mod 2.

[asarian]

Originally Posted by sneaker_ger

"mod 2" means you can only achieve even numbers of pixel dimension. You cannot crop just one pixel away, you have to crop away 2 or 4 or 6 or 8 etc. This depends on the colorspace. For progressive YUV 4:2:0 you need to use mod 2.

The AVI in question has a height of 225; so cropping per 2 is going to prove difficult; but I can add a border first. Thx.

EDIT: Yeah, AddBorders isn't going to work either, for the same reason. Sigh.

[LigH]

Must be quite a *censored* who produced such videos ... I wonder if you have a chance to ask the codec to return RGB24 or RGB32 (with their respective ffmpeg style format strings).
__

Different question:

Does anyone provide binaries of plugins ported by VFR-maniac, but only linked as source repos on the plugins list (FFT3DFilter, ReduceFlicker, TNLMeans without OpenCL)?

[asarian]

Originally Posted by LigH

Must be quite a *censored* who produced such videos ...

I'll say.

This is totally silly. I can resize it first, but then I can't deblock it properly any more. Arghh.

[asarian]

Originally Posted by asarian

I'll say.

This is totally silly. I can resize it first, but then I can't deblock it properly any more. Arghh.

On that note, could I use some sort of Overlay() in VS? (So as to crop things later) Didn't find an Overlay() function in VS, but I'm sure it supports something similar.

[LigH]

I remember that in AviSynth, you could resize a clip rectangle, optionally. Not sure if VapourSynth supports this syntax too.

[asarian]

Originally Posted by LigH

I remember that in AviSynth, you could resize a clip rectangle, optionally. Not sure if VapourSynth supports this syntax too.

I had to fall back to AviSynth, for the moment, and do the OverLay() trick: not particularly elegant, but it works. I simply start with a static 400x240 background image, and overlay the oddly coded 400x225 vid over it (at x=0, y=0), and then crop -16 from the bottom, when all deblocking/denoising etc is done.

Really would love to see Overlay() in VS too, one day.

[feisty2]

Originally Posted by asarian

I had to fall back to AviSynth, for the moment, and do the OverLay() trick: not particularly elegant, but it works. I simply start with a static 400x240 background image, and overlay the oddly coded 400x225 vid over it (at x=0, y=0), and then crop -16 from the bottom, when all deblocking/denoising etc is done.

Really would love to see Overlay() in VS too, one day.

Overlay is lame sh*t, the fancy way to do such thing is doing it under gray color space, 3 gray clips, one for each plane

[asarian]

^^ Maybe you should have told me that 4 posts ago?! Anyway, 'quick and dirty' works for me.