jcm

Just tried to play and experienced this. Got a trace, attached. Looks like it could be audio-related. Not sure why the stacks are so large in SS14 on macOS. ```...

Couple misc changes: - Fixed the reaction effects property issue - We were checking if the received buffers differed from the configured format by checking the video range; it seemed...

Sidebar that I just thought of; now that the scaffolding is in place to store computed properties in an AVCaptureDeviceFormat+Comparable category, The format's list description (given by `[OBSAVCapture descriptionFromFormat:]` presently)...

Some submodules went weird on the latest commit, and in the process of fixing it I went ahead and rebased and squashed the commits.

The only difference from there to the current state is the decimal formatting. Here is the current state of the list format for the devices I have available:

In the third screenshot, yes, each of those is its own frame rate range on the format where the range represents one discrete value (min and max are equal). I...

Rebased, and also changed `AVCaptureDeviceFormat+OBSListable.m`'s `- (NSString *)obsPropertyListDescription` to more gracefully handle bad values. I chose to just not include string values if they are invalid, unspecified, or unknown. So...

Per discussion out-of-band, we needed to add an internal representation for the value of device formats separate from their human-readable descriptions. This is so that we can freely change the...

Revised to add a trivial base64 mask / hash for the internal value used by OBS to identify device formats. Leaving this value human-readable risked the impression that this value...

Just wanted to note that there are still two "changes requested" flags on this, but both of these were resolved a few weeks back, so should be given another pass.