bino-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bino-list] Hi & Bino blurs my OU footage on interlaced output.


From: gl
Subject: [Bino-list] Hi & Bino blurs my OU footage on interlaced output.
Date: Mon, 06 Jan 2014 17:33:46 +0000
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0

(my first msg never showed up, I assume the large image triggered moderation - here's a copy with an external link to the image):
--

Hi guys,

I'm gl (aka gl.tter). I'm a programmer who's been working on a stereo video editing plugin for a few years (http://gl.tter.org/LumaChroma3D, though that's out-of-date).

I tried Bino recently after I changed from my Zalman M215W to an LG D2343P (both passive interlaced 1080p screens) and couldn't use the Zalman Edition Stereoscopic Player anymore. Great to have a free stereo player.

First thing I noticed though is that it blurs my Over/Under squeezed (half-height) 1080p footage on 1080p passive displays, on all Quality levels, when it shouldn't.

Specifically, my footage is a perfect match for 1080p passives, ie. Over/Under (Top/Bottom) 1920x1080 w. half-height views (1920x540). Each view has the same number of rows as the display, so the images should not be resized/resampled or filtered in any way, but directly interlaced as-is.

I've prepared a test, a B&W 2x2 checkboard video @ 1080p:http://gl.tter.org/_TEMP/Checkerboard2x2(1080p).mk3d . You do not need a passive display to see the problem, any 1080p screen is fine:

If you show this using Input: "Top/Bottom, half-height", "Output Even/Odd rows" on a 1080p screen you get this:

http://gl.tter.org/_TEMP/BinoBlurTest.gif  (animated GIF)

'Correct' is what should happen - just interlacing, no filtering. You can see how Bino blurs the image vertically at all Quality settings.

It looks like a classic vertical half-pixel shift (sampled with bilinear), or maybe it's interpolation from scaling, or deliberate AA - but in this special case, where the row resolutions match exactly, none of those should happen.

Also, I understand that Q3/Q4 apply additional filtering. For 'squeezed' views that also makes no sense, as the squeezing is already filtered.

I haven't looked at the source code yet as I'm pretty busy, maybe you can check it out?
--
gl







reply via email to

[Prev in Thread] Current Thread [Next in Thread]