-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VS2012 project with 3 new features #44
base: master
Are you sure you want to change the base?
Conversation
Solution and projects files were modified to make them compilabe without installing the Windows SDKs's DirectShow sample. Lib and Includes paths were modified too.
Modifications regarding the default Git settings.
ffmpeg update to 2014-06-09
Codec is replaced with x264rgb and there is an option to switch crf value between 0 (lossless) and 1 (very good quality).
x64 solution modification
Add a new Windows event hook to capture the foreground window changed event, in order to be able to capture the window which is currently in the foreground at any given time.
Paths were fixed to reflect the new locations.
You can use the Ctrl+Alt+W keystroke to fix and release the window handle of the recorded window. When you start recording, it is in the released state, so you can switch between the windows and the SCR will capture the foreground window. When you click Ctrl+Alt+W it will store the window handle, so if you switch the foreground window to another one, it will still record the previous window.
Refactored and reworked the rectangle handling of desktop, window and bounding box objects. It also made the capture of the small windows faster and resolved the "trailing" issue when a single window was recorded which was smaller than the video resolution and it was moved around.
In window capture mode the mouse disappeared. There was an error in the AddMouse function.
New feature: when you hit Ctrl+Alt+W the active window will have a green (released) or blue (freezed) border around it. When you hit Ctrl+Alt+B, you will see where the bounding box (capture area of the screen) is.
In window mode there was a small misalignment between the bounding box and the real capture area. Now it is correctly show where the recording will take place.
Removed some user-specific files
Remove batch files from Release and Debug folders
Merge x86 and x64 solutions into one.
Delete screen-capture-recorder.dll
Update to the gitignore file
Modified the .gitignore file to include some files which are needed for compilation and testing.
Updated readme and installer files to 0.13.0
Replaced x64 ffmpeg (2014-06-09) with x86 (2014-08-24), because it caused problems on 32-bit systems.
ChangeLog update
I will definitely look at this once I get back into "open source" mode here...possibly 2 months or so, sorry about that! |
The position of the mouse cursor was off in certain recording modes
Added new options for foreground window only recording (enable/disable, capture mouse cursor and some description of the keystrokes)
I fixed a problem with the mouse capture and extended the configuration utility with the new options. |
OK do you know exactly which commit did those two thing? On Fri, Oct 31, 2014 at 1:24 PM, Andras Fuchs notifications@github.com
|
Yes, you can see them next to the list of commits just above my previous comment. Mouse cursor: New options in the config utility: |
In the configuration utility we have the resizable window to select the area to be recorded. This window now shows the resolution of itself in the middle.
And added a small extra function to the configuration utility to show the size of the area selection transparent window. Commit: |
nice...now to find the time to integrate them... On Sat, Nov 1, 2014 at 2:19 AM, Andras Fuchs notifications@github.com
|
Hi!
I've made a fork from your project to help you with the work.
I needed to convert the project to the Visual Studio 2012, and I also needed to change some include and lib paths to make my copy complilable.
As you can see those changes are separated to different commits, I hope it will help you to separate them from the new feature implementations.
What do you think?
Update 2014-08-19:
I've made some new features today: