Could you actually be more specific, what would be needed for 16bit support? I was naively thinking to just a binary copy from source pixel to target for starters.
2016-02-25 22:40 GMT+01:00 F.Sluiter <fslui...@gmail.com>: > It would also be relatively easy to implement anti-aliasing (probably in > version 2). > > 2016-02-25 22:38 GMT+01:00 Paul B Mahol <one...@gmail.com>: > >> On 2/25/16, F.Sluiter <fslui...@gmail.com> wrote: >> > If it doesn exist I would like to develop a new filter and would like to >> > check if nobody is already working on it or that it exists under a >> > different name. >> > >> > I have been researching the following usecase: >> > >> > Similar tot the displace filter, I would need a filter to remap pixels >> (the >> > difference being that displace displaces the pixels relative to where it >> > was, remap would specify where the target pixel originates from): >> > >> > Description: Remap pixels as indicated by second and third input stream. >> > >> > It takes three input streams and outputs one stream, the first input is >> the >> > source, and second and third input are targetmaps. The second and third >> > input specifies the x.y coordinate where the pixel in the target stream >> > originates from. Note that once generated, remap files can be reused >> over >> > and over again. Source and target do not have to have the same size. >> > The effect I am trying to achieve is hard to compute with the relative >> > "displace", and a lot more straightforward with "remap". >> >> With 16bit support too? Go ahead, nice idea :-) >> >> I'm interested in motion estimation/interpolation/compensation filters >> too. >> _______________________________________________ >> ffmpeg-devel mailing list >> ffmpeg-devel@ffmpeg.org >> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel >> > > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
