Feature Request: Support the OBS Source Profiler #1306
Description
Feature Request Type
RPC Request
Feature Request Type (Other)
No response
Requested Feature
In v31, OBS added the Source Profiler, a way to get information about resource utilization on a per-source basis. Currently, this information is not directly exposed by OBS, and the only way I am aware of to access it is Exeldro's source profiler plugin. The plugin is great, but only provides the profiling information in human-readable form. obs-websocket should also make this information available via the websocket interface
Requested Feature Usage Scenario
obs-websocket already provides the ability to retrieve general performance information from OBS (e.g. counters for render lag, encoding overload, and frame drops); some people already gather (and usually graph) this information to assist in understanding their stream's performance over time, and identify changes to their stream that might have unanticipated performance impacts. Exeldro's plugin, while great, is better suited towards identifying the source [sic] of acute performance issues, rather than allowing performance to be tracked over time to identify longer term trends and behaviors.
(FWIW, I have a working telegraf plugin for gathering OBS stats that I'm working on putting in a release-able state, so there will be at least one way to make use of this information/feature at some point in the not-so-distant future.)