Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

A Method for Capturing Screen N frames

IP.com Disclosure Number: IPCOM000246536D
Publication Date: 2016-Jun-16
Document File: 5 page(s) / 68K

Publishing Venue

The IP.com Prior Art Database


Customers or Developers often suffer software crash or have usage problem on product such as bug or setting error. Sometimes, screen shot can not make problem clear, support people can not know what user has done before the problem occur. Video or GIF (Graphics Interchange Format ) can tell the procedure about what user did, but he has to reproduce the problem and use some screen record tool. It is tedious and sometime can not reproduce the problem easily. Our disclosure is that user just needs to click on print screen button on keyboard as usual to get screen shot, but what they can get is a video or GIF image eventually.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 65% of the total text.

Page 01 of 5

A Method for Capturing Screen N frames

This disclosure claims that

User just needs to click on print screen button on keyboard to get screen shot as usual, when they suffer the software crash. But they can get a video or GIF image which is a few time recording what user did before the problem occur.

Operation system has a daemon process to record the screen in real time into a memory cache.

User does not need to care about the daemon process, it is started with Operation system, and also don't need to click something to enter the record mode just like video record.

Daemon process would automatically make a video or GIF image after user print screen, and save it as a mp4 or gif file in file system.

Figure 1 shows the whole process of this disclosure.


Page 02 of 5

Figure 1. Flow chart of Daemon Process


Page 03 of 5

Figure 2

Figure 2 is left part of the figure 1, that shows:
1. Daemon process starts with operation system and keep running in background.

2. If user suffers software crash or has usage problem, and click on print screen button, daemon process would make a video or a gif image.

3. The video or gif image would be saved in local file system.


Page 04 of 5

Figure 3

Figure 3 is right part of the figure 1, that shows:
1. Daemon process keeps capturing screen and cache the frames in memory.

2. Daemon process would compress the frames, so memory allocation would not be huge.

3. Daemon process just keep X time frames by default, user can customize the period...