What you are seeing is most likely an artifact caused by extreme photo processing. Both GIF and JPG image storage is subject to such errors and can produce images of things and actions that never were there in the first place. Truthers put much stock in subjective interpretation of such artifacts, calling them "anomolies." Photo processing experts (of which I am one) call it absolute nonsense.
It's a lot like a portrait painter, creating a crude pencil sketch from a snapshot he saw 10 years ago and saying, "Here's what happened, and my drawing proves all other observers and photos are wrong!"
It takes a discerning eye to see, but if you follow the prompts supplied and watch it over and over, you'll get there.Whatever "wave propagation" that femr2 wants me to see, I simply cannot see.
Went back to one, now back up to two. Oh well, you have the video links.femr2, If you have only heard from 2 people that your gifs are a mess, add me to the list.
I very much doubt MT uses the same tools that I do, increasing the likelyhood that you have a local problem.Every gif you or Major_Tom ever post does not appear like you think it does on Firefox or Safari (Mac) or Safari (PC).
It's just colour range enhancement to highlight behaviour which is already there.What you are seeing is most likely an artifact caused by extreme photo processing.
JPEG is lossy, GIF is not. Your statement makes little sense.Both GIF and JPG image storage is subject to such errors and can produce images of things and actions that never were there in the first place.
Try reading the discussion before commenting.Truthers put much stock in subjective interpretation of such artifacts, calling them "anomolies."
A *photo processing expert* (interesting choice of word triplet. giggle) would not suggest similar artefact behaviour between GIF and JPEG formats. Two entirely different beasts.Photo processing experts (of which I am one) call it absolute nonsense.
.
I very much doubt MT uses the same tools that I do
Sherman Bay's statement makes perfect sense. Unless your original video was itself a GIF, you had to convert from some other format to GIF. That conversion introduced at least the first of these kinds of compression error:It's just colour range enhancement to highlight behaviour which is already there.What you are seeing is most likely an artifact caused by extreme photo processing.
JPEG is lossy, GIF is not. Your statement makes little sense.Both GIF and JPG image storage is subject to such errors and can produce images of things and actions that never were there in the first place.
Sherman Bay demonstrated considerably greater understanding of processing artifacts than you did in your reply to him.A *photo processing expert* (interesting choice of word triplet. giggle) would not suggest similar artefact behaviour between GIF and JPEG formats. Two entirely different beasts.Photo processing experts (of which I am one) call it absolute nonsense.
No, change in reflectivity state is the means by which the behaviour being highlighted becomes visible, but *what it is* is the CAUSE of that state change, which is a disturbance/a flexure (as Ryan put it)/a distortion...of the facade.
You now know that belief to be inaccurate.
What caused the failure?My *theory*, as you put it, in relation to my video that beachnut so lovingly highlighted, is that it shows visual evidence supporting the notion of propogation of failure from low down in the building beneath the East penthouse propogating up to said penthouse, then showing the effect upon the facade as the penthouse and surrounding structure descends through the building...as I have stated many times.
And you think that is bizarre ? I see
The prefix is *non*, not *none*.
Are you suggesting that the behaviour I have described did not occur ?
Are you suggesting I am engaging in discussion of a fake occurance ?
No, change in reflectivity state is the means by which the behaviour being highlighted becomes visible, but *what it is* is the CAUSE of that state change, which is a disturbance/a flexure (as Ryan put it)/a distortion...of the facade.
Downsampling of colour range, sure. Doesn't really introduce much in the way of artefacts of the kind he was hinting at.Sherman Bay's statement makes perfect sense. Unless your original video was itself a GIF, you had to convert from some other format to GIF. That conversion introduced at least the first of these kinds of compression error:
[*]GIF cannot represent more than 256 colors per image, so any conversion from natural-color video formats to GIF involves lossy compression of color.
[*]If you changed the pixel resolution at any stage of your conversion to GIF, then that conversion introduced additional loss of information.
I use lossless compression at all times (HuffYUV). See note above about how silly the suggestion is otherwise.Both of those losses come on top of whatever lossy compression may have been used to create your source materials.
I beg to differ.Sherman Bay demonstrated considerably greater understanding of processing artifacts than you did in your reply to him.
Quite revealing, isn't itI'm a bit confused.
femr2 is showing the visual effects of the collapse progression as NIST describes it and people are arguing about it.
![]()
Took quite an effort to find it, though I don't think *expect* would be quite right.Should we not expect visual distortion in the buildings exterior facade?
Don't recall that at all. The video has been online since 4 August 2009.In fact, I think I asked him about doing this view over a year ago.
All this because apparently Sunlight reflects off of glass.
I'm a bit confused.
femr2 is showing the visual effects of the collapse progression as NIST describes it and people are arguing about it. Should we not expect visual distortion in the buildings exterior facade? Looks basically how I would imaged it to look. In fact, I think I asked him about doing this view over a year ago.
![]()
He seems to be confirming what NIST says. Until he does otherwise I'm taking it as such. Simple really.Who's arguing? Just wantinhg to know what he thinks the CAUSE was. When he stops dancing any blowing his own trumpet about the special tools he uses perhaps he can tell us what the CAUSE was.
I'm a bit confused.
femr2 is showing the visual effects of the collapse progression as NIST describes it and people are arguing about it. Should we not expect visual distortion in the buildings exterior facade? Looks basically how I would imagined it to look. In fact, I think I asked him about doing this view over a year ago.
![]()
Crack on. lol.
The majority on this site dont visit this sub forum. They actively wanted this **** moved away. Thats point one!
The majority of the planet don't visit this site or any other ct site. They have no need. Thats point two!
Why am I here? Laughs and giggles. It started with the 'truthers' but I am beginning to see a steady stream of 'none truthers' or 'debunkers' warranting laughs and giggles. Not out of them being 'wrong' or 'uneducated' but purely out of them 'argueing over pinnoccio'. lol.
Crack an Newton. Or ya could just refer all the nutjobs to gravy's site. Simple. Job done for ya long ago. Engineer or not..........still discussing pinnoccio the kids to no end.................as shown below:-
I could use my techy knowledge and experience with explosives and demolitions to **** on anyone here. lol. Alas I realised it would be to no avail long ago. One day you will too. lol.
But hey Engineer.........crack on, femr2 is listening to ya. lol.
The last gif you posted shows the building literally splitting in two. I can't get a screencap, 'cause I can't pause a gif. Seems odd that the same thing would happen on both Mac and PC and with different browsers. Maybe I'm having a lucid dream or hallucination.femr2 said:I very much doubt MT uses the same tools that I do, increasing the likelyhood that you have a local problem.Every gif you or Major_Tom ever post does not appear like you think it does on Firefox or Safari (Mac) or Safari (PC).
I'll keep an eye on it.