ConfigFile doesn't distinguish between non-existent keys and keys with
an empty (string) value; therefore we default to treating an empty
SavePath as default save path (and warn the user when setting an empty
SavePath)
Recording is now always enabled (unless previewing)
This changes the semantics of SaveToFile from "disable all file output
when disabled" to "automatically save stream to file when enabled",
which allows the "Start Recording" button to be enabled even when
SaveToFile is disabled.
Having the "Start Recording" button enabled now depends on having a
non-empty SavePath
Now able to Switch between different Scene collections.
All Scene ".Xconfig" files now stored in the "sceneCollection" folder.
Changed "GetApplicationName()" added "Profile: SceneCollection: " to the beginning of the app name.
Added "Scene Collection" Combo Box in Settings General
Can add/rename/remove new scenes collections in settings general.
Can add/rename/remove new scene collections while streaming.
Can change scenes Collections while streaming.
I can't help but wonder if this is causing some issues with frame
duplication, I suddenly realized the code wasn't particularly thread
safe so I threw this in as a precaution.
This should finally fix the out-of-sync issues with hardware encoders.
The data was not always properly being interleaved, and this should fix
the issue (again). (The previous time I attempted this it didn't quite
work out as I had wanted)
BufferSize settings in the config files will be ignored as long as
the checkbox is unchecked (UseBufferSize is unset or 0), to make
the contents of the settings dialog reflect actual encoder behavior
If a volume control was muted, the hidden 'unmute volume' value was not
saved to the configuration, meaning that if you exit while muted then
restart, it would unmute to 100% each time, causing annoyance for some
users.
This button was originally added as a convenience feature for users who
liked to stream certain windowed games (especially retro games) at a 1:1
pixel ratio without having to constantly fiddle with the settings or
figure out exactly what the window client rectangle size was for the
target.
However, some less knowledgable users would press this button without
knowing specifically what it does, causing some support issues. I've
readded the button, but with a big warning box that will pop up warn the
user and ask for confirmation.
However, this problem will have to be solved better in the rewrite.
Having this in the software capture sources is not an adequate way of
dealing with the problem. There needs to be some way to save custom
resolutions in the rewrite so you can easily switch between them. There
also needs to be a way to copy the resolution of a window or window
client rectangle, and it really shouldn't be in the window capture
source properties I think.
Caused us no end of pain. Users clicked it so much that it made us all
snap. Now, if a user really, REALLY wants to use it, they'll have to
manually set the ini file variable in their profile ini, under [Audio],
InputDevicesForDesktopSound=1
- Add an option in game capture to use SetWindowsHookEx instead of
CreateRemoteThread to inject the library.
- Add logging of what process game capture is trying to capture.
- Rename "audio time offset" where it was used to "audio sync offset"
- Adde logging for audio sync offsets
- Update version to 0.62b test 1
