YorVeX
Member
Just wanted to say that now in February 2020 with OBS 24.0.3 I ran into exactly this issue, so it still is there.
I've been searching why I regularly keep on "missing frames due to rendering lag" and was already pulling out my hair.
I have a lot of self-coded tools and stopped them one by one to exclude them. I stopped missing frames when I closed a program that is responsible for updating a text file that is embedded as a Text source in OBS. When I then searched on Google for frames missed due to Text sources I found this thread. After reading that the Text outline caused it I fired my tool that updates the text file back up, got the missed frames again, then disable the outline for that Text source and - Ta-Dah! - no more missed frames.
The reason why it couldn't be reproduced here probably was because two other factors are important:
1. The frames are only missed when the text is re-rendered. Which happens when the text for the Text source comes from a file, the frames are missed every time that file is updated.
2. The next needs to be of significant length. For me with every character of text I add the chance of a text change producing the missed frames increases. For me it's around 259 characters that I start to miss frames. With fewer characters I can still see that the "Average time to render frame" jumps from 0.5 to 1 ms in my test seen but no frames are missed.
I will open a bug report about this now and link it here.
I've been searching why I regularly keep on "missing frames due to rendering lag" and was already pulling out my hair.
I have a lot of self-coded tools and stopped them one by one to exclude them. I stopped missing frames when I closed a program that is responsible for updating a text file that is embedded as a Text source in OBS. When I then searched on Google for frames missed due to Text sources I found this thread. After reading that the Text outline caused it I fired my tool that updates the text file back up, got the missed frames again, then disable the outline for that Text source and - Ta-Dah! - no more missed frames.
The reason why it couldn't be reproduced here probably was because two other factors are important:
1. The frames are only missed when the text is re-rendered. Which happens when the text for the Text source comes from a file, the frames are missed every time that file is updated.
2. The next needs to be of significant length. For me with every character of text I add the chance of a text change producing the missed frames increases. For me it's around 259 characters that I start to miss frames. With fewer characters I can still see that the "Average time to render frame" jumps from 0.5 to 1 ms in my test seen but no frames are missed.
I will open a bug report about this now and link it here.