You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if GetMediaInputStatus is run on a media source (specifically an ffmpeg source) the duration will come back unknown if the media is not playing. This makes it hard for apps to reason about how long a media source will play. An ffmpeg source can play remote sources and streams, but I am wagering the vast majority of media sources are playing local files off the hard drive.
It would be nice if when an the media input status is requested for an unloaded ffmpeg source playing a local file, instead of replying with an unknown duration it instead would use ffprobe to retrieve the duration.
Requested Feature Usage Scenario
My app allows users to schedule various actions around sounds, media, and events. But it's very hard to display to them the duration of media sources since getting the duration of a media source is unreliable. In reality I can do things like check if the OBS is running on the same computer as my app and run ffprobe myself, and even very quickly force OBS to load the media to test it's duration on a remote machine. But all of this is less desirable than just having OBS run ffprobe itself on the media file and report it over the websocket.
The text was updated successfully, but these errors were encountered:
Feature Request Type
RPC Request
Feature Request Type (Other)
No response
Requested Feature
Currently if GetMediaInputStatus is run on a media source (specifically an ffmpeg source) the duration will come back unknown if the media is not playing. This makes it hard for apps to reason about how long a media source will play. An ffmpeg source can play remote sources and streams, but I am wagering the vast majority of media sources are playing local files off the hard drive.
It would be nice if when an the media input status is requested for an unloaded ffmpeg source playing a local file, instead of replying with an unknown duration it instead would use ffprobe to retrieve the duration.
Requested Feature Usage Scenario
My app allows users to schedule various actions around sounds, media, and events. But it's very hard to display to them the duration of media sources since getting the duration of a media source is unreliable. In reality I can do things like check if the OBS is running on the same computer as my app and run ffprobe myself, and even very quickly force OBS to load the media to test it's duration on a remote machine. But all of this is less desirable than just having OBS run ffprobe itself on the media file and report it over the websocket.
The text was updated successfully, but these errors were encountered: