fraps links

http://spazzarama.com/2009/02/07/screencapture-with-direct3d/

http://stackoverflow.com/questions/5069104/fastest-method-of-screen-capturing

also that one guy’s “instrumenting” library.

http://stackoverflow.com/questions/5069104/fastest-method-of-screen-capturing [stretchrect, also memcpy link…

http://stackoverflow.com/questions/4120108/how-to-save-backbuffer-to-file-in-directx-10/4286971#4286971 dx10

windows vista/7 32 bit program sees files 64 bit doesn’t

http://www.techsupportalert.com/content/how-windows7-vista64-support-32bit-applications.htm

http://www.techsupportalert.com/content/32-bit-and-64-bit-explained.htm mentions the different cmd.exe’s which might make a difference

http://stackoverflow.com/questions/3219255/why-do-files-get-placed-c-users-usernameappdata-local-virtualstore-program-fi really explains it though

how to convert rgb/rgb32 to i420

libvidcap has methods like “vidcap_rgb32_to_i420″ in its source.
swscale also does it with optimized MMX instructions :) (for sure if compiled with –enable-gpl not sure about otherwise)

The naive way works! sweet!

https://github.com/rdp/screen-capture-recorder-to-video-windows-free/commit/465decb20d89bb7e26f8a4e16c27a0e26490cbf8 (note: I changed it later see comments)

(non optimized, ping me with questions)

vlc woe

avcodec warning: almost fed libavcodec with two frames with the same PTS (501148507337)
avcodec warning: almost fed libavcodec with two frames with the same PTS (501148540670)
avcodec warning: almost fed libavcodec with two frames with the same PTS (501148574003)
avcodec warning: almost fed libavcodec with two frames with the same PTS (501148607337)
avcodec warning: almost fed libavcodec with two frames with the same PTS (501148640670)
avcodec warning: almost fed libavcodec with two frames with the same PTS (501148674003)
stream_out_transcode debug: drift is too high, resetting master sync
access_output_udp debug: packet has been sent too late (9962071)

 

 

 

with my directshow capture device…I think this may mean “VLC’s sync timing code is buggy” 

Meant I was introducing a little bit of “timestamp creep” on my packets by sleeping too long then stamping them.  So basically I was giving it some extra time in there.

https://github.com/rdp/screen-capture-recorder-to-video-windows-free/commit/b255b214081a553ef9e0953dea36e84d562755d7

–live-caching=3000 seemed to help