The optimizations sound good, I have yet to repeat a test with the current version (last time I tested was with an early self-compiled 28'ish build).īut closing this based solely on a straw man? I think everyone here would agree that reloading a full image source every frame is not a common scenario, I don't know who you are telling this.īy OPs screenshot the scenario here apparently is an image file that displays a game score. There have been optimizations (see flaeri's comment), but this really isn't what the image source is meant to be used or will be optimized for. So investing the time and adding the complexity wouldn't be "just for this", it would be to turn the image source for many common scenarios from "unusable" to "useful" (at least for people who care about frame drops).Īs mentioned in this thread already, if you're hammering OBS to reload a full image source every frame, degraded performance is to be expected (also for reference, this is by no means a common scenario). Right now what I do is to avoid using image sources like the plague and use browser sources with a simple html that loads the image instead. I was really wondering why this happens, but if I understand your comment right then this is done on the main thread and with a 60 FPS recording/stream will always make OBS drop frames as soon as it takes longer than 16.66 ms (and usually less, since OBS also got other stuff to render in the same time frame). Changing the underlying image file, triggering an automatic reload of the image source.Hiding and Showing the image with "Unload image when not showing" enabled.Adding the image source and therefore loading an image the first time regardless of its options and file watch features."Loading" here includes all of these scenarios: I use a very large image there to increase the probability of the issue occurring, but even loading a 1080p BMP image from a fast SSD (which shouldn't be something uncommon or extreme for a 1080p stream/recording) will cause frame drops. I use it for my reproduction scenario in #6673 because I needed something that is part of OBS base functionality and performs extremely bad (in contrast to OBS otherwise usually performing great). Both the option "Unload image when not showing" and the fact that it has a file watch and automatically refreshes when the underlying image changed are unusable if I don't want frame drops (and I really want to avoid them, since they can cause other issues like A/V desyncs). I'm not sure it's worth the complexity to add threaded loading for image sources just for Unfortunately it doesn't get better with BMP.įor me the image source really is only usable in one single scenario right now: a static image is loaded at the beginning and then never unloaded. PNGs are quite slow to decompress relatively speaking, for frequently updated files try using uncompressed PNG or another raw format like BMP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |