net is not exactly designed around optimization. I'm pretty sure they have implemented the option to do things on the GPU, otherwise they'd be crazy.Ģ.) There's also the overhead of the. But I suppose I do have some theories:ġ.) If they are doing software rendering of scenes then that's a pretty gigantic waste of time when everyone has a decent GPU these days. I don't know what exactly what xsplit does, I've still to this day never used it because I suppose I just don't care enough about it. I use SSE2 intrinsics whenever possible as well to further reduce CPU load as much as possible. NET BS, no wasting time with all those extra useless dependencies and overhead.
The app is written in full C++, no overhead for. I generally designed it to spend as little time on the CPU as possible, as wasting CPU time on image manipulation is a completely pointless waste of resources with a decent GPU around, which is almost always the case for anyone streaming seriously. I didn't even bother to use a software renderer or anything because it just wasn't worth the time when streaming typically requires a beefy computer anyway. I wrote it with this specific design in mind, and with optimization in mind (though there are a few places where it needs work, such as the audio engine). It's a GPU accelerated streaming application (note that this does not include encoding). I've made no secret that OBS is almost entirely GPU dependent. I'll try to settle this myself, though I don't know how long this thread will actually be alive.
0 kommentar(er)
