Hi -
On Mon, 13 Jun 2005, Steve Tell wrote:
> > between RC1 and now yuvdenoise has undergone some major changes...
>
> It looked like it had already undergone major surgery since 1.6.2 - but
> then I guess everything has too.
Yes, between the last released version and RC1 there was the first
rewrite. Then between RC1 and the present time there was another
rewrite/major-revision.
> It does seem like the yuvdenoise manpage has been left in the dust. Is
:)
> anyone's sense that yuvdenoise has stabilized again to the point where its
> worth fixing the manpage? I assume the patch would be welcome if I were
The author of yuvdenoise was going to do that when the supply of
free time increased. But if someone else were to help out I'm
sure he'd appreciate it <grin>
> Any hints on where to look for replacements for the various options no
> longer present in yuvdenoise when reworking old scripts?
> So far I found that "y4mshift -b" appears to replace the old "yuvdenoise
> -b" option.
Yes, the bordering option has effectively been moved to y4mshift.
As it turns out that's a pretty good place for it since analog->digital
capture cards often don't center the useful 704 samples of a 720 sample
frame.
I forget what most of the other options were to yuvdenoise. The
sharpening (-S) is better performed by 'y4munsharp' now but that's
the only option that comes to mind.
> I already had a CVS tree, and have been using CVS y4mspatialfilter.
> But hadn't seen much noise about worthwhile changes in there, so hadn't
> updated in a while.
Oh, we're a pretty quiet bunch as a general rule :) Don't make a
lot of noise when stuff's checked in to cvs.
> Anyway, the CVS yuvdenoise does work for me.
Super!
> Given that these are "release candidates", is there a release-bound freeze
> of some kind in place?
The goal was to let things settle down and get the bugs fixed. So
it'd probably be a good idea to hold off on new features.
> porting them forward from 1.6.2 to RC? or CVS, and was wondering if I
Against CVS would be the best choice since cvs has diverged quite
a bit from the RC1 tarball.
> should offer them up for review and possible inclusion now, or wait until
> after a release for the next cycle.
Hmmm, don't hold your breath unless blue is one of your favorite
colors? :-) Things move very slowly these days - seems there
aren't many _active_ developers remaining (maybe everyone's just
searching for new suppliers of "free time" :)).
Go ahead and create the patches and post 'em - if they're not too
likely to cause breakage they can probably be slipped in to cvs for
when the next RC is created.
Cheers,
Steven Schultz
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Mjpeg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
