Talk:Framebuffer

message: Here it states: This switch is usually done during the vertical blanking interval to prevent the screen from "tearing" (i.e., half the old frame is shown, and half the new frame is shown).
This is wrong, maybe it is true on some platforms. But this line suggests that it is almost always the case ("usually"). It is not, in fact many people dislike the lag vsync introduces and on PC it is mostly disabled by default. This should be changed.  — Preceding unsigned comment added by 77.1.78.191 (talk) 11:10, 21 March 2015 (UTC)
replies: text: Usually has been changed to often. The whole paragraph starts by saying the technique may be used. Does anyone have a citation about lag and vsync? ~Kvng (talk) 19:56, 23 April 2020 (UTC)
thread_title:  Section "Page Flipping" 

message: The screen buffer article suggests there is a difference between that and a frame buffer. But it doesn't really say that, it contrasts itself with VRAM, which is odd. Worse, the provided references both clearly refer to buffers holding a full screen (in one case, ASCII data) and don't distinguish themselves.
I can imagine a difference between the two - one could buffer just a portion of the screen while the other is a full screen. However, if such a distinction exists I've failed to find any evidence of it.
If someone can offer a distinction I'm all ears, otherwise I'd like to merge the screen buffer here, leaving it as an "alternate term" definition and redirect.
Maury Markowitz (talk) 13:02, 1 October 2015 (UTC)
replies: text: There is no difference between the two. I vote to merge Screen buffer into this article. 104.228.101.152 (talk) 02:28, 19 December 2016 (UTC)
replies: text: There's a big difference between the two. A frame buffer is simply memory that contains a video frame. Depending on the application, it may be used to capture frames from a video decoder (e.g., frame synchronizers and frame grabbers), cyclically "replayed" through a video encoder to produce video, used to reformat video (e.g., frame rate conversion, image rotate/resize/crop), transmitted via communication interface (e.g., USB, Ethernet), etc. On the other hand, a screen buffer is a frame buffer (typically dual-port) which holds image data for a tightly-coupled display interface -- a specific usage case of frame buffers. Lambtron talk 16:34, 16 January 2020 (UTC)
replies: text: Assuming we can find good sourcing for your claim for how this terminology is used (I suspect things are a bit messier than you suggest out there), modern systems typically use general-purpose main memory or GPU memory for what you're calling a screen buffer. Instead of dedicated dual-port memory, DMA is used to refresh the display. At best, the distinction between Framebuffer and Screen buffer has been blurred by technological advancement so it seems appropriate now to cover them in the same article. ~Kvng (talk) 15:34, 20 January 2020 (UTC)
replies: text: Screen buffer now redirects here. ~Kvng (talk) 19:56, 23 April 2020 (UTC)
thread_title:  Is there really any difference between this and screen buffer? 

message: Hello fellow Wikipedians,
I have just modified 2 external links on Framebuffer. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Corrected formatting/usage for http://accad.osu.edu/~waynec/history/PDFs/Annals_final.pdf
*Added archive https://web.archive.org/web/20061102132148/http://www.amiga-hardware.com/showhardware.cgi?HARDID=481 to http://www.amiga-hardware.com/showhardware.cgi?HARDID=481
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 05:05, 5 October 2017 (UTC)
replies: text: http://www.amiga-hardware.com/ no longer cited. ~Kvng (talk) 19:56, 23 April 2020 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified 8 external links on Framebuffer. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20061102121333/http://www.amiga-hardware.com/showhardware.cgi?HARDID=291 to http://www.amiga-hardware.com/showhardware.cgi?HARDID=291
*Added archive https://web.archive.org/web/20070708224741/http://www.amiga-hardware.com/showhardware.cgi?HARDID=282 to http://www.amiga-hardware.com/showhardware.cgi?HARDID=282
*Added archive https://web.archive.org/web/20061102132339/http://www.amiga-hardware.com/showhardware.cgi?HARDID=503 to http://www.amiga-hardware.com/showhardware.cgi?HARDID=503
*Added archive https://web.archive.org/web/20061102132033/http://www.amiga-hardware.com/showhardware.cgi?HARDID=498 to http://www.amiga-hardware.com/showhardware.cgi?HARDID=498
*Added archive https://www.webcitation.org/65uEJ2qdI?url=https://design.osu.edu/carlson/history/PDFs/14_paint.pdf to http://accad.osu.edu/~waynec/history/PDFs/14_paint.pdf
*Added archive https://www.webcitation.org/65uEJVsGj?url=https://design.osu.edu/carlson/history/lesson15.html to http://accad.osu.edu/~waynec/history/lesson15.html
*Added archive https://www.webcitation.org/65uEKKkhe?url=https://design.osu.edu/carlson/history/PDFs/paint.pdf to http://accad.osu.edu/~waynec/history/PDFs/paint.pdf
*Added archive https://web.archive.org/web/20060211051810/http://www.acid.org/radio/arts-ep05-transcript.txt to http://www.acid.org/radio/arts-ep05-transcript.txt
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 19:42, 11 January 2018 (UTC)
replies: text: http://www.amiga-hardware.com/ no longer cited. ~Kvng (talk) 19:56, 23 April 2020 (UTC)
thread_title:  External links modified 

message: "Amiga computers, due to their special design attention to graphics performance, created in the 1980s a vast market of framebuffer based graphics cards. Noteworthy to mention was the graphics card in Amiga A2500 Unix, which was in 1991 the first computer to implement an X11 server program as a server for hosting graphical environments and the Open Look GUI graphical interface in high resolution (1024x1024 or 1024x768 at 256 colors)."
Is this really claiming that the A2500 was the first computer to run X11 in high resolution at 256 colors, or am I not understanding correctly?  That claim would be completely and utterly false on any conceivable level. 
hbent (talk) 17:17, 19 January 2018 (UTC)
thread_title:  Amiga claims 

message: Does anyone know why most of the sections of this article are unsourced? NintendoTTTEfan2005 (talk) 08:22, 14 June 2023 (UTC)
replies: text: Because it needs improvement. Some of these sections have  links. You can often find appropriate sources in these linked articles and copy them here. ~Kvng (talk) 12:39, 20 June 2023 (UTC)
thread_title:  Unsourced sections