User contributions for 146.199.0.169

17 June 2019

• 21:3621:36, 17 June 2019 diff hist +633 Chlorodifluoromethane →Price history and availability: absolute crawling code horror, but hopefully it'll work
• 21:1321:13, 17 June 2019 diff hist +9 Chlorodifluoromethane →Price history and availability: also, they determined the remaining stockpile was 22700 to 45400 tonnes (which I expect means roughly 50 to 100 million pounds?)... when? The stockpile will vary over time. The cited articles are from 2013, so it's certainly not up-to-date data. Plus I'm definitely going to have to convert that table to metric, ain't I... mixing units like that is just silly, especially as all the rest of the article is metric / SI.
• 21:1121:11, 17 June 2019 diff hist −18 Chlorodifluoromethane →Price history and availability: The symbol for "metric ton" (or properly: tonne) is, er... "t". And it shouldn't need subtitling like that, as it's a standard SI unit. If the reader understood the units in the lengthy table a couple of screens further up, or the enthalpy diagram, they'll know what "t" means.
• 21:0921:09, 17 June 2019 diff hist −2,187 Talk:Chlorodifluoromethane →Any reason for "MT"?: don't know why this doubleposted
• 21:0821:08, 17 June 2019 diff hist +2,187 Talk:Chlorodifluoromethane →Any reason for "MT"?: new section
• 21:0721:07, 17 June 2019 diff hist +2,187 Talk:Chlorodifluoromethane →Any reason for "MT"?: new section
• 20:5720:57, 17 June 2019 diff hist +264 Talk:Chlorodifluoromethane →Cans of HFC 22 for use in air guns are NOT Chlorodifluoromethane!

3 June 2019

• 15:3115:31, 3 June 2019 diff hist +4 Framework (office suite) This whole lede is a horrendous, possibly machine-translated mess, but calling the IBM-compatible the "PC 8086" is possibly the most egregious error of the lot, so I'ma start by fixing that.

19 May 2019

• 17:0617:06, 19 May 2019 diff hist +226 Talk:MC68340 →Is this...: new section

18 May 2019

• 14:1514:15, 18 May 2019 diff hist +317 Interlaced video →Interlace and computers: bla bla bla, more twiddles
• 14:1014:10, 18 May 2019 diff hist +1,557 Interlaced video →History: Some style/grammar tweaks, correcting own typos; AFAIK, South America in general has been slow in adopting digital / HD TV, so it's still correct to say that Brazil "uses" NTSC/50, but if that's out of date, please adjust it. Etcetera, so on, and so forth.
• 13:3813:38, 18 May 2019 diff hist +4 Interlaced video →Interline twitter: ah, I accidentally a word
• 13:3213:32, 18 May 2019 diff hist +3,499 Interlaced video →History: God, what a mess. NTSC refers *colour encoding* first bolted on to US 525-line monochrome TV standard; ditto PAL and SECAM, for (mostly) 625-line. There's no particular magic or special designation for the monochrome systems themselves other than the linecount. Also, why concentrate on the ][gs alone? 262/313p was v.common. The CGA DID support composite colour modulation, w/an encoder on the card for TVs/cheap monitors; RGB screens were costlier! VGA / Mac-II hi-res were both 1987.
• 12:4212:42, 18 May 2019 diff hist +141 Interlaced video →History: (however, ISO standards are basically impossible to cite due to paywalls, and I can't find the actual page I was reading - on Google books - in my browser history) ... Also quick sidenote that "405-line" TV wouldn't be "405i" in the modern age, same as how we don't count the full 1125 lines of a 1080i/1080p HDTV scan.
• 12:3812:38, 18 May 2019 diff hist +49 Interlaced video →History: ISO documents including research and analysis show that 50Hz is about the bare minimum, at a population-mean (ie 50th %ile) level, though that doesn't account for phosphor afterglow etc. If you make it larger, brighter, and want to ensure much more of the population perceive a non-flickering image, you have to go higher; 90th %ile at 300cd is just over 80Hz, and 95th %ile at higher illuminances is closer to 90. Hence the ultimate VESA standard of 85Hz for true flicker-free monitors
• 12:3312:33, 18 May 2019 diff hist +312 Interlaced video →Deinterlacing: I wouldn't be surprised to find that a monitor that can understand 8514/A and 1080p also displays 1080i without trouble, particularly as it scans at basically the same rate as 720p which is also widely supported, especially if the screen has HDMI (or DVI) input. What's actually missing in the main is "15kHz" capability, which excludes you from plugging a non-upscaling DVD player (or VHS, TV tuner) directly into a monitor. And of course "software video players" cover all those
• 12:2612:26, 18 May 2019 diff hist +5 Interlaced video →Deinterlacing: Hm. Turns out there is no "XGA" article, which is a bit of a hole in the wiki record, and it redirects rather uselessly to (the top of) a huge list of display resolutions instead of to the progenitor adaptor. Fixing that. Note that said article -does- include mention of (weird!) text modes unique to the 8514/XGA which use the interlaced hi-rez mode as their basis, but I strongly doubt any of them were ever used in anger, vs much more common XGA-graphics & VGA-based text modes
• 12:2212:22, 18 May 2019 diff hist +1,446 Talk:IBM 8514 →Title...?: new section
• 12:1412:14, 18 May 2019 diff hist +13 Display resolution standards →1024{{resx}}768 (XGA): If we're talking about the "8514", that's a monitor, and it has only one new "mode" - 1024x768 interlaced, at whatever colours it's provided with. The graphics *card* is the 8514/A, which has various colour modes, sub-resolutions, etc - and could be connected to several different monitors besides the 8514 itself, from day one. Petty, maybe, but if we're not going to get the fine detail correct, what's the point of bothering with an encyclopaedia in the first place?
• 12:1012:10, 18 May 2019 diff hist +1,578 Talk:Display resolution standards →How many colors can be displayed simultaneously in SXGA?
• 12:0112:01, 18 May 2019 diff hist +1,418 Talk:Display resolution standards →WTH
• 11:5211:52, 18 May 2019 diff hist −6 Interlaced video →Deinterlacing: I'm not aware of any interlaced text-only display modes, care to name some? And certainly any textmode supported by a modern display will be progressive. Text requires quite a lot less vertical resolution than horizontal to look decent, so textmode and early graphics modes based on them tended to have tall pixels (= greater H than V rez), including progressive versions of TV modes (e.g. CGA 640x200). Interlacing was used for early hi-rez square-pixel graphics modes like XGA.
• 11:4911:49, 18 May 2019 diff hist +574 Interlaced video →Interline twitter: OK, can't really source this cuz I'm reaching back quite a way, so O.R. it if you must... but waybackwhen I made title/menu screens for homebrew VCDs (which displayed a full 704x576, vs the video's 1/4 rez), the best way to get a sharp-looking image without shimmering text was to create it at full rez then apply a 1px vertical motion blur - NOT just linedouble (=obviously blocky but STILL shimmered!) - a technique based on what I'd read was generally used by TV studios...
• 11:3811:38, 18 May 2019 diff hist +236 Interlaced video →Interline twitter: Why 30Hz going to 15Hz? That's some extremely old, specialist technology you're considering there, probably an early 80s CAD system using a purpose-built long-persistence phosphor CRT which wouldn't show the flicker anyway (but be hopeless for any kind of fast motion). To be completely fair I should have edited this to the 87Hz / 43.5Hz common to early 'laced SVGA/XGA/SXGA displays, but 60/30 is probably more familiar and understandable in the world of 2019.

15 May 2019

• 00:1600:16, 15 May 2019 diff hist −15 Transistor–transistor logic →History: Removing an utterly petty "when?" tag. 7400s are still being sold *now*, and it's likely they will *never* go out of production in one form or another, as they are so fundamentally useful for an endless array of rudimentary electronic tasks, same as they have been for over 55 years so far. I've put a "(2019)" marker in pretty much as a courtesy, but, honestly? If 7400s stop being sold whilst WP exists, you can feel free to phone me and blow a raspberry down the line.

7 May 2019

• 16:2216:22, 7 May 2019 diff hist +29 I386 The specs for the "386" are those for the "DX", a designation that was retroactively applied to the original all-32-bit chip when the SX came along. If you're going to include both data/address bus widths then it would be sensible to define which apply to which version of the chip. Also, editing the address width to "32/24" but not the data width to "32/16"? Come on, that's just sloppy.
• 16:1816:18, 7 May 2019 diff hist +35 I386 Bit of an odd caption which seems to essentially just copy the image filename, not really meaning much to anyone not intimately familiar with CPU chip collecting and mostly reiterating what can be seen in the picture itself. Hopefully this is a more useful replacement.
• 01:0201:02, 7 May 2019 diff hist +28 Hold-And-Modify →Hold-And-Modify mode: figured I should probably look it up properly
• 00:5200:52, 7 May 2019 diff hist +4,128 Talk:Hold-And-Modify →Animating HAM images
• 00:2200:22, 7 May 2019 diff hist +2,171 Talk:Hold-And-Modify →Sprites vs HAM: new section
• 00:0600:06, 7 May 2019 diff hist +1,996 Talk:Hold-And-Modify →Rewrite the description of HAM

6 May 2019

• 23:4823:48, 6 May 2019 diff hist +3,827 Talk:Hold-And-Modify →Rewrite the description of HAM
• 23:2423:24, 6 May 2019 diff hist +1,464 Talk:Hold-And-Modify →picture showing clearly the artifacts that might happen with this format?
• 23:1823:18, 6 May 2019 diff hist +2,008 Talk:Hold-And-Modify →Sliced HAM (SHAM or SHM)
• 23:0123:01, 6 May 2019 diff hist +36 Hold-And-Modify →Limitations: of course VHS doesn't have hard edged chroma pixels, it's more the number of times you can produce a full range switch from black to white and back again, with the inherent filtering making that transition very smooth and blurry. It didn't look as crappy as you'd expect because smaller changes to the signal could be managed more quickly, increasing the effective resolution for more subtly shaded material - just the same as with HAM...
• 22:5822:58, 6 May 2019 diff hist +48 Hold-And-Modify →Limitations: What's the point of including a MHz figure for VHS when there's no comparitive frequency for the Amiga modes (whose pixel clocks, fwiw, would have to be halved to equate to analogue video bandwidth)? Replacing it with an explanatory note of video line pixel equivalents (80 is still pretty low). Also, OCS/ECS (for which a "704" pixel limit is relevant - AGA can run HAM at much higher resolutions) can't used HAM in hi-rez... 352-ish horizontal pixels is where they cap out.
• 22:5322:53, 6 May 2019 diff hist +11 Hold-And-Modify →Usage: huh, I thought "High color" had been reused for a type of modern HDR / Deep Color mode and would thus cause disambiguation issues. Turns out, no...
• 22:5222:52, 6 May 2019 diff hist +655 Hold-And-Modify →Usage: The planar thing is an interesting historic side note, but hardly relevant to the usefulness of HAM. As demonstrated by the existence of both planar and chunky 8bpp modes on the PC VGA, with the same resolution limits and memory use as each other, it's simply a different way of interleaving the video data that's useful for simplifying the decoding of non-byte-aligned (e.g. 5bpp / 32-color) pixels. It means nothing for actual bandwidth - HAM8 would work just the same if it was chunky.
• 22:3722:37, 6 May 2019 diff hist +58 Hold-And-Modify →Hold-And-Modify mode
• 22:3622:36, 6 May 2019 diff hist −6 Hold-And-Modify →Hold-And-Modify mode: on the subject of consistency, made a slight slip on the basis of "component" vs "channel" (the difference is pretty subtle, TBF, and not really worth expanding on here)
• 22:3322:33, 6 May 2019 diff hist +2,092 Hold-And-Modify →Hold-And-Modify mode: Jeez, was this section last updated by a 9-year-old? The ideas were mostly (though not entirely) sound, but the writing was outright juvenile and not at all encyclopaedic. Have thus given it a wholescale rewrite, with some correction of erroneous info (NTSC =/= an HSV system, it's merely simpler to convert to from it), adding missing details, making things more consistent (pick HSV or HSL, don't switch between them randomly - they're two names for the same thing), etc.