Mesh warp resizer needed

[Emulgator]

To spatially adjust fields of a unrepeatable flying-spot transfer coming from a disadjusted machine a mesh warp resizer like in After Effects would be handy.
I tried my luck with vcmohan's DeBarrel, it is very nice but the scan lines had been so distorted (I guess by uneven deflection coils) that I need more points to warp.
Does anybody know of a solution ? Anything besides Adobe, an avisynth filter, plugin into Sony Vegas etc.

P.S. Sorry, wrong forum. Should have been in Avisynth usage. Mods please feel free to move this thread...

[poisondeathray]

Why not Adobe ?

You pretty much need a GUI to do a free transform. I can't imagine doing it by coordinates or math...

For images, you can try grid warp for paint.net and batch process. I think gimp has one coming out or it might be out already
http://forums.getpaint.net/index.php?/topic/25327-grid-warp/

Another free option might be debugmode winmorph + wax to do the trasform with splines, but I guess it depends on exactly what type of manipulation you need

EDIT : I forgot Nuke has a free non-commercial version now. It has limitations such as limted to HD resolutions, fewer functions, but I think the free version still has the grid warp

https://www.thefoundry.co.uk/products/nuke/compare/
http://help.thefoundry.co.uk/nuke/8.0/content/user_guide/warping/warping_using_gridwarp.html

[vcmohan]

I tried my luck with vcmohan's DeBarrel, it is very nice but the scan lines had been so distorted (I guess by uneven deflection coils) that I need more points to warp.
Does anybody know of a solution ?.
My plugin Planetarium does probably what you desire. Of course I did not understand clearly your problem.
Planetarium requires a input grid and corresponding output grid coordinates specified for each intersection. This data is read from a text file by the plugin and warps the input accordingly. If the text file format is given, then a grid warper plugin can be created (by me) specifically for that format.

[Emulgator]

poisondeathray: Many thanks for your suggestions !
Unfortunately I repeatedly failed to transfer my paid Adobe CS3 license from an outdated machine to the rendering machine.
It looks like adobe do not support that license transfer anymore.
I tried to jump through their hoops, but ended up sitting on 2500€ almost lost in the bin, furious, but I shall have to try again.
GUI, yes, one will want to drag and drop the grid points rather than trying numbers, but I am willing to go through the latter.
A 5x5 grid would suffice I guess.
Ah paint.net grid warp. Beautiful. Digging into it now.
Nuke: whoa. Lets see if their non-commercial grid pops up after their hoops without paying 5000 GBP.

vcmohan: Many thanks for Planetarium, I will look into it now !
...but I have difficulties understanding the structure of the parameter list from the description.
I tried a translation, please correct me if I'm wrong.

Use:

Planetarium(clip (clip,default:none), "path\to\mapping\file" (string, default:none), ow (Output Width, int, 720..4096, default:1920), oh (OutputHeight, int, 480..4096, default:1080), type (int, default:2), level (int, 1..4, default:1))

YV12, YV16(2.6), YV24(2.6), YUY2, RGB24, RGB32

The input parameters are
the input clip, mapping data file, output frame size, type of input data, type of interpolation.

The plugin has no way to check whether the input is of type indicated in the data file.
It is the users responsibility to ensure this.

The output may exhibit strong striations due to abrupt variations of intensity.
To eliminate these variations a interpolation parameter 'level' can be used.
A level of 7 may be quite satisfactory.

-----------------------Mapping data file (.txt file)----------------------------------------

The first line has a single value that specifies the input image type.
This value is 2 for a fish eye view source aberration. (Other source aberrations ?)

The second line has 2 values:
the numbers of grid sections along width and height.

The following each of lines contain
the output x and y pixel coordinates of output frame, frame center normalised float (0.0 to 1.0) as 0.0, 0.0
the w and h values of grid sections on input frame, left bottom normalised float (0.0 to 1.0) as 0.0, 0.0
and intensity in normalised float (0.0 to 1.0).

An example (hopefully mapping 1:1....no, it won't work)

2
3, 3
-1.0, 1.0, 0.0, 1.0, 1.0
0.0, 1.0, 0.5, 1.0, 1.0
1.0, 1.0, 1.0, 1.0, 1.0
-1.0, 0.0, 0.0, 0.5, 1.0
0.0, 0.0, 0.5, 0.5, 1.0
1.0, 0.0, 1.0, 0.5, 1.0
-1.0, -1.0, 0.0, 0.0, 1.0
0.0, -1.0, 0.5, 0.0, 1.0
1.0, -1.0, 0.0, 1.0, 1.0



Using this file the Planetarium plugin performs thousands of matrix conversions and keeps the results in a look-up table.
Since these conversions are done by cpu at present, the start-up is slow.

In future using Graphic cards capabilities will be explored to speed this process up.


A 30 frame sample PAL-DV-AVI is here:
http://dvd-manufactur.de/files/FlyingSpotScanner Beam Distortion PAL-DV 30f.avi
You may call SeparateFields().Bob() and watch the right quarter of image content wagging up with uneven field and down with even fields.

[raffriff42]

Unfortunately I repeatedly failed to transfer my paid Adobe CS3 license from an outdated machine to the rendering machine.Assuming you haven't tossed out your old hardware yet, try P2V (http://forum.doom9.org/showthread.php?p=1754547#post1754547).

[Emulgator]

Good suggestion ! My old WinXP32SP3 (CPU T7600G) hardware lives on, well maintained. One more hoop though, lets see.
Still hoping for moving license, maybe I borked something networky on that new Win7U64 (CPU i7-4960X) system
which inhibits successful remote license activation the adobe way. No firewall virus software though, never had that...
While trying to give freeware elevated writing rights to any location I gradually had to take over ownership to more and more locations from system.
Once I was tired of ploughing and made that globally. I guess that locked some (invisible to me, but needed) acesses out.
Some software relying on Visual C++ Redistributables close with a silent crash and from that (BEX) crash on
every software that uses the same redistributables can no longer start up until a fresh restart has been made.
Will have to investigate further, time permitting.

[vcmohan]

@emulgator
My plugin Planetarium was developed for a specific purpose requested by a Planetarium operator. He provided me with the input-output grid spec file. It has also other values required for that use. So it will not work for you.
If you can specify the input frame size, input grid spacing vertical and horizontal, ( I am assuming that you have a evenly spaced grid) corresponding output grid coordinates ( with ref to origin may be center or left top of frame) for all the grid intersections (either in float or integer ) as a table in a text file then a plugin can be developed.

[vcmohan]

I have examined the video. As far as I could guess, the video appears to have slight jitter. Is it a transfer of VCR to digital video?
I processed with the following code and to my old eyes it looks fine.
loadPlugin ("C:\....DeJitter.dll")
directshowsource("C:\users\vcmohan\Videos\FlyingSpot.avi")
Dejitter(jmax = 10, th = 40, wsyn=16,extend=false, uselast=true)

[Emulgator]

Many thanks, vcmohan ! Yes, it is a transfer from VHS to DV.
Before it must have been flying-spot-transferred from 16mm film to
(me guessing) 1" Type C-tape or U-matic,
the scanner must have been introducing the different field warping.
You may add
SeparateFields().Bob()
to see what I mean.

[vcmohan]

While experimenting I used the following code. It appears to have corrected itself. May be excepting at one scan line affecting the number plates of the cars.
directshowsource("C:\......\FlyingSpot.avi")
turnleft()
separatefields().bob()
turnright()
Please try. My eyes are old.