FB-FB(1)

πŸ“¦
version 7.44.0 Β· 2 versions
, in nixpkgs unstable

πŸ’… fb-fb(1) β€” the BRL-CAD manual page, bestie edition πŸŽ€

okay so you opened the fb-fb(1) page from the BRL-CAD manual set and you want the tea. buckle up, because this little icon copies one framebuffer onto another and it ate. πŸ¦‹


✨ NAME ✨

fb-fb β€” copy a framebuffer image to another framebuffer. that's it. that's the whole gig. πŸ’–


🌸 SYNOPSIS 🌸

fb-fb [-v] [-F _output_framebuffer_] _input_framebuffer_
fb-fb [-v] _input_framebuffer_ [_output_framebuffer_]

🫢 DESCRIPTION 🫢

okay so here's the vibe: fb-fb copies the entire image from input_framebuffer over to an output framebuffer, and it does it by reading and writing in blocks of scanlines. lowkey efficient. the output size is taken straight from the input framebuffer β€” no guessing, no drama, it just matches. ✨

now, the output device? you've got two ways to name it, and you have to pick one:

  • with the -F option, or
  • as a second positional argument
but not both, bestie. -F and the positional output argument are mutually exclusive. pick a lane. πŸ’€

if you don't give an output at all, the default framebuffer gets used (typically set by the FB_FILE environment variable). and same energy for the input β€” the same conventions apply if you omit it, though ngl an input framebuffer is normally required. 😭


πŸ’… OPTIONS πŸ’…

  • -v β€” verbose mode, the main character setting. prints the input and output device names, the detected width and height, and per-block progress β€” all to standard error. no cap, it's giving "narrator". πŸ”₯
  • -F output_framebuffer β€” specify the output framebuffer device. mutually exclusive with the positional output argument (yeah, we said it already, but it's that kind of rule). πŸŽ€
  • -h, -? β€” print a usage message and exit. classic. iconic. we stan a polite exit. πŸ‘‘

🌈 EXAMPLES 🌈

Example 1. Snapshot a live framebuffer into a file 🌸

fb-fb /dev/X /dev/mem
fb-pix /dev/mem > snapshot.pix

so what's happening here: you copy whatever is currently displayed on the X11 framebuffer into the in-memory framebuffer, then you save it to a pix(5) file with fb-pix(1). πŸ¦‹

and the why? this captures a render produced by rt(1) without re-running the raytrace. literally saving you so much time. obsessed. πŸ’–


⭐ SEE ALSO ⭐

brlcad(1), fb-pix(1), fb-png(1), fb-bw(1), pix-fb(1) β€” go read these too, they're all in the group chat. 🫢


🧚 AUTHOR 🧚

BRL-CAD Team β€” the ones who built it. πŸ’œ


This software is Copyright (c) 1991-2026 by the United States Government as represented by U.S. Army Research Laboratory. periodt. πŸŽ€


πŸ™ˆ BUG REPORTS πŸ™ˆ

Reports of bugs or problems should be submitted via electronic mail to devs@brlcad.org. found a bug? don't be shy, tell them β€” they want to know, fr fr. πŸ’Œ


πŸ’€ reminder before you dip: -F or the positional output arg. not both. that's the one thing that'll get you.

alright bestie, that's the whole page 🫢 this came to you from BRL-CAD (FB-FB(1)) β€” mwah, catch you on the next manpage. πŸ’–βœ¨πŸŒΈ

πŸ“¦ where this page comes from