Open D1yt opened 5 years ago
It depends if the sources in the scene are async or not. For sources that are not async like scenes and groups the replay source renders the source. For async sources it just captures the frames.
So there is no way to "fix" this behaviour because it's "intentional"
Am Fr., 8. März 2019 um 06:49 Uhr schrieb Exeldro <notifications@github.com
:
It depends if the sources in the scene are async or not. For sources that are not async like scenes and groups the replay source renders the source. For async sources it just captures the frames.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/exeldro/obs-replay-source/issues/2#issuecomment-470813847, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ8KjU78dnVWmrjCTRTQlzlMR1imbqBLks5vUfoFgaJpZM4bkRRs .
When you want the replay to track a whole scene or group with several sources (all of them blank) OBS uses RAM proportional to the number of sources. This can be bypassed by using the same replay filter for all of these sources.