On Thursday, August 21, 2008, at 06:41AM, "Carl Rohumaa" <[EMAIL PROTECTED]> wrote: >Just trying out some camera settings for a live video patch I am >working on and notice that even if I check the de-interlace fields box >in the video input patch it will not de-interlace an HDV 1080i input. >SD is fine. Is this expected? Sorry if this has been asked a million >times. > >Ok it is true that it seems to de-interlace a bit and is worse without >but still has a significant interlacing on all the movement. > >BTW Is thread h--i__j--a+++c---k++i--n--g allowed on the list? ;-))) > >C > I took the liberty to edit your last posting. The h-i. Jack. (hereafter referred to as t "h"-word.) is likely to be picked up by any number of 'patriot' governmental agencies. So while "h"-wording of threads is technically impossible to dis-allow--it certainly is not condoned.
I also consider the "B" word as highly offensive. That would be "B_U_G." I have noticed over 60 occurrences of this vulgar, vicious word on this very list. "BUGS" is a four-letter word in anyone's book. While someone might point out that 'b-u-g' is a three letter word--they never travel alone. Once one is found, there are most definitely others lurking in the background. When one's technical implementation imprecisely matches one's problem-space (both real or imagined), one should identify it formally and rigorously and not resort to cavalierly tossing around the obscene and highly profane "B" word. My advice is manifold. First, become a soft architect. They can easily pawn off slight inaccuracies in their design as boring implementation details and in some rare instances have the programmer shot. But good coders are hard to find-- they're all selling pencils on some busy urban street-corner--cursing the open-source movement under their breath. But if you have to actually be unfortunate enough to be responsible for getting all the bits in the right places at the right time--i.e. a coder/programmer/designer--SOFTWARE ENGINEER--then my advice would be--don't put b-u-g-s in your code. I'm sorry for stating the painfully obvious, but maybe it never occurred to other beginning IT hackers. Just don't do it. These are not a desireable language feature. Once you use them you'll then have to waste even more time learning to use a de-louser. Once you admit to being adept at de-"B"-ing then any number of people will actually expect you to fix their code. I give some similar advice to golfers. Don't hit your golf ball into the bunker (sand trap). I don't understand this. Even players on the PGA Tour, (even TW sometimes condescends to visit a trap--I guess he needs the practice) , players who should know better, insist on hitting their balls into sand traps. Why would they do this? Sorry to be off topic. If you insist on populating your source code with b's at least have the decency to place these into a plug-in so that others might not have to see the offending code, besides they'll run quicker and maybe no-one will notice. De-interacing 1080i--that sounds like a boring, technical detail. I'm a film director. --aram _______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
