SimpleResize YV12

[sapient]

Hi...

I show that the gordian knot beta comes with a YV12 supporting version of simpleresize... Is it a stable release? There is no readme and trbarry doesn't have it at his homepage...

sapient

[trbarry]

sapient -

It all should be at the usual places:

www.trbarry.com/Readme_SimpleResize.txt and
www.trbarry.com/SimpleResize.zip (source,bin, & readme)

- Tom

edit: I see the stupid reame file was updated for Avisynth 2.5 support but still says YUY2 only. That is false, the Avisynth 2.5 version does work in YV12 mode, except for InterlacedResize.

[DDogg]

Tom, as you know, I use InterLacedResize function within SimpleResize for resizing DV. It seems to work great. The few times you have mentioned InterLacedResize it seemed like you had some reservations about it, but maybe that was just when used before FieldDeinterlace().

I just wanted to ask for some clarification. Do you see any technical downside using it for straight resizing on pure interlace versus the more conventional splitting of fields and all that rigamarole that gives me heartburn?

As for using it before FieldDeinterlace(), I can understand there might be a byproduct for FieldDeinterlace as it does not get all the original information, but it seems to work for me just fine in the few quick tests I did (DV)and is very fast. Any more comments on that and what problems should I look for more closely if doing this?

[bb]

Originally posted by trbarry
edit: I see the stupid reame file was updated for Avisynth 2.5 support but still says YUY2 only. That is false, the Avisynth 2.5 version does work in YV12 mode, except for InterlacedResize.
Do I understand correctly: In your AviSynth 2.5 version InterlacedResize works in YUV2 colorspace, but not in YV12?

bb

[trbarry]

I just wanted to ask for some clarification. Do you see any technical downside using it for straight resizing on pure interlace versus the more conventional splitting of fields and all that rigamarole that gives me heartburn?

DDogg -

The only downside of InterlacedResize vs SimpleResize is that InterlacedResize has to work only with the data from one field at a time. This means the vertical resize results are not quite as precise because it is interpolating from data values (sample points) that are twice as far apart as they would be if you could use all the lines. However this will still probably be slightly more accurate (and faster) than separating the fields and separately resizing them.

The only real justifcation for using InterlacedResize before deinterlacing (instead of SimpleResize after) is when you are significantly downsizing. In this case the slower deinterlace step may run a bit faster because it is operating on smaller frames. But except for that speedup I'd deinterlace first and resize later. BTW, in one of the other threads where we discussed this I'd forgotten about the speedup effect, so take my comments there accordingly.

- Tom

[trbarry]

Do I understand correctly: In your AviSynth 2.5 version InterlacedResize works in YUV2 colorspace, but not in YV12?

bb -

Yikes! I had to go look at the code for that one. But yes, you are correct.

The rest of the functions, SimpleResize, WarpedResize, etc., should work in Avisynth 2.5 in both the YUY2 and YV12 color spaces.

I don't anticipate any major problem with implementing support for InterlacedResize in YV12. It's just the math is different because of the strange way YV12 stores chroma data when interlaced. So it takes some thought first and I got side tracked before I finished that.

- Tom

[DVD__GR]

trbarry I would kindly request sometime when you have the
time to give us a link with all your avisynth work together,or
to setup a litlle bit your site to be able to browse your work.
thanks in advance:)

[trbarry]

Sorry, it's been many years since I really maintained my web page. I think I last changed service providers about 6 years ago and haven't changed anything much since. ;)

Generally for any of my Avisynth filters there are 2 files, case sensitive. So if the name of my filter was SimpleResize() then you can probably find:

www.trbarry.com/Readme_SimpleResize.txt and
www.trbarry.com/SimpleResize.zip , etc.

A quick list of my Readme files shows:

www.trbarry.com/Readme_BT709ToBT601.txt
www.trbarry.com/Readme_DctFilter.txt
www.trbarry.com/Readme_FillMargins.txt
www.trbarry.com/Readme_GreedyHMA.txt
www.trbarry.com/Readme_SimpleResize.txt
www.trbarry.com/Readme_STMedianFilter.txt
www.trbarry.com/Readme_TomsMoComp.txt
www.trbarry.com/Readme_UnDot.txt
www.trbarry.com/Readme_UnFilter.txt
www.trbarry.com/Readme_YV12InterlacedReduceBy2.txt

and the zips, plus a couple (all should have source, dll, readme):

www.trbarry.com/BT709ToBT601.zip
www.trbarry.com/DctFilter.zip
www.trbarry.com/DVD2AVIT3.zip (save-oe version w/HDTV bug fixes)
www.trbarry.com/FillMargins.zip
www.trbarry.com/GreedyHMA.zip
www.trbarry.com/MPEG2DEC2.zip (YUY2, Avisynth 2.0x, P4 support)
www.trbarry.com/MPEG2DEC3.zip (YV12, Marc FD's with HDTV bug fix)
www.trbarry.com/SimpleResize.zip
www.trbarry.com/STMedianFilter.zip
www.trbarry.com/TomsMoComp.zip
www.trbarry.com/TomsMoComp_Faster_DLL.zip (for DScaler 4.x only)
www.trbarry.com/UnDot.zip
www.trbarry.com/UnFilter.zip
www.trbarry.com/YV12InterlacedReduceBy2.zip

and a screen cap from my latest attempt to make up-converts:

www.trbarry.com/Star_Wars_RoJ.jpg

- Tom

[DDogg]

Tom, I now understand InterlacedResize does not support RGB32 (Wah), but the statement InterlacedResize(480,480) throws the "must be divisible by 2" error instead of a colorspace warning on 720x480 DV source served as RGB32. Not a biggy but it might confuse people like me :)

Before I get glommed on, the reason my DV is RGB32 is because I was serving via the Vegas/Premiere/MSP7 frameserver that just came out and outputs in RGB32. I can of course use the ConvertToYUV2 (which cured my interlaced resize problem) but I thought you may have been interested in the "by 2" error throwing because of RGB32 Colorspace.

OT:
This FS is cool and allows me to serve directly from the time-line, though avisynth, and into AVI2SVCD (subset of DVD2SVCD), or to other vid software. Yeah, no more intermediate renders! Oh, and Tom - Vegas 4.0B supports HD and 24p now :)

[trbarry]

DDogg -

Thanks for the alert. I probably just copied a section of code when I added that check and didn't rememeber to add the message.

I'll fix that.

And yeah, I've heard good things about Vegas & HD.

- Tom