Overscale screenshots?

[Tampa]

This might be a windows limitation, but I'd like to take screenshots at 2x or 4x resolution for particularly large code bases. I tried changing the window size, but it unfortunately seems limited to that maximum screen resolution on windows, so that approach didn't work. An option to save screenshots at higher scales would be nice :)

Have not tried on linux yet.

[bitpaint]

Hey, i used to create big screenshoots from ppm files.

If i remember correctly i was piping the render in 4k to a ppm file, then extract single image with ffmpeg.
https://github.com/bitpaint/bitcoin-gources/tree/main/gource/art/4k

I did that on a 1080p sceeen.
I can't remember exactly but i think this was the way i used to do it, but i used to do it.

Alternatively i'm working on a UI for Gource that will allow you to do this kind of stuff, but it's still under progress.

[bitpaint]

Try this:

gource --viewport 7680x4320 --stop-at-time 10 --output-ppm-stream - | ffmpeg -f image2pipe -vcodec ppm -i - output%03d.png

1. gource:
   This is the command that runs Gource, the software that generates an animated visualization of a repository's version control history.

2. --viewport 7680x4320:
   --viewport: Specifies the resolution (the "viewport size") for the Gource window.

7680x4320: This sets the resolution to 8K (7680 pixels wide by 4320 pixels tall). This ensures that the visual output from Gource is rendered at a very high resolution.

3. --stop-at-time 10:
   --stop-at-time: This option specifies the point in time after which Gource will stop the animation.

10: This tells Gource to stop the animation 10 seconds into the run.

4. --output-ppm-stream -:
   --output-ppm-stream: This tells Gource to output the generated animation frames as a PPM (Portable PixMap) image stream. A stream is a continuous flow of image data that can be processed by another program.

-: This symbol means the output will be sent to standard output (stdout), so it is passed along to the next part of the command (in this case, ffmpeg).

5. | (Pipe):
   The pipe symbol | is used to pass the output from Gource directly into ffmpeg for further processing. This means Gource sends the frame data to ffmpeg in real-time.

6. ffmpeg:
   ffmpeg is a popular command-line tool used to handle multimedia files, such as videos and images. In this case, it's being used to convert the image stream from Gource into an image file format (PNG).

7. -f image2pipe:
   -f: This option tells ffmpeg to specify the input format.

image2pipe: This indicates that the input is a stream of images (as opposed to a regular file), and ffmpeg should treat it as such.

8. -vcodec ppm:
   -vcodec: This option specifies the video codec (in this case, it's not actually a video, but an image stream).

ppm: This tells ffmpeg to expect the PPM format (Portable PixMap) from the input stream.

9. -i -:
   -i: This option specifies the input for ffmpeg.

-: The - tells ffmpeg to use the data coming from the standard input (stdout), which is the image stream from Gource.

10. -update 1:
    -update: This option tells ffmpeg to overwrite the output file each time a new frame is received.

1: This ensures that only one frame is saved at a time, effectively creating a single snapshot from the stream.

11. output.png:
    This specifies the output file where ffmpeg will save the image. In this case, the output will be saved as output.png.

[Tampa]

This works, but I only really want an image once the entire log has been processed as a kind of code overview. ffmpeg refuses to overwrite the same file with image2pipe and so it has to generate every frame to png, which will take days to finish and fill up my disk. I tried skipping ahead in gource, but that just omits things. I need something that writes the output to a dummy I can then take a "snapshot" of once gource has ran through the whole git log.

[bitpaint]

You can use: spd 0.00001 to make the viz faster... exit when you are happy or wait for it to finish.
it will output the last frame as a png. we dont write the ppm file but instead pipe it to memory.
There is some things we can't change for now but this does work on my laptop for a large repo, i get a 4k screenshoot in under 5minute.
8k takes longer but does work.

I guess that's the best we can do for now.
Another way would be to emulate a bigger screen and use the screenshoot build-in function in gource ... i guess. (never done that)

Try this one:
(press Esc to stop early otherwise it could take some minutes for it to "stabilize" and auto-close, but it does work.)

4K
gource -s 0.00001 --viewport 3840x2160 --stop-at-end --hide users,filenames,dirnames --output-ppm-stream - | ffmpeg -y -f image2pipe -vcodec ppm -i - -update 1 last_frame.png

8K
gource -s 0.00001 --viewport 7680x4320 --stop-at-end --hide users,filenames,dirnames --output-ppm-stream - | ffmpeg -y -f image2pipe -vcodec ppm -i - -update 1 last_frame.png