Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Very nice tip, mainly the part about when something happens you can rewind it.

What about hard disk space? How you handle it?



The space requirements can be very low capturing something like writing code, where only 1% of the screen might change second-to-second.

"ffmpeg -f gdigrab -i desktop -c:v libx264 -preset medium -fps_mode vfr -crf 0 -an -vf mpdecimate capture.ts" (Windows, -f x11grab -i $DISPLAY for Linux on X11) produces a lossless video that averages 102 MiB/hour for me (1920x1080 @ <= 60fps). That's about two cents a day at current disk prices, and easy to upload as a private YouTube video if you don't want to lug the files around.

If you don't like the CPU hit, use -preset ultrafast to record the capture using less processing power but giving a larger file, and then re-encode that file later using -preset slower. There's no quality loss if you used lossless mode (-crf 0), and for content like this the savings are especially large (reducing to around one-quarter ultrafast size, in my experience).


Wow, I did not know that. Awesome!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: