Question / Help Best way to remote into OBS Studio on Streaming PC? (no monitor or kb/m)

APerfidiousDane

APerfidiousDane

New Member
I have a workstation that I use to stream via NDI and if I keep the Remote Desktop connection open the stream will be choppy (basically mimics what I see on RDC). The OBS frames are dipped into the 20's or lower sometimes. However if I start the stream and close the RDC the stream runs fine. My workstation does not have its own monitor or kb/m. It's accessible and a possibility but I'd prefer to not mess with it if at all possible.

I was hoping to be able to keep the RDC open so that I could see dropped frames or any other issues that may arise but currently it doesn't seem likely. Is there any decent alternative out there?

https://gist.github.com/anonymous/e162fde2d67465e7fb8af3641e9f9282
 
Last edited:
Perhaps use another remoting protocol like Ultra-/Real-VNC? Usually RDP is more performant, but they may hook differently enough to not cause the same slowdown..
 
I'll check out using another type of remote connection. I was hoping to keep it as simple as possible with things included in windows or OBS plugins but if I need to try something else then so be it. Sadly remote is for classic and websocket just doesn't seem to be there for what I need.

I actually wanted to use Synergy or Mouse without borders but from what I can tell they "extend" the desktop to make it seem like the monitors on other systems are part of your default setup. I think they're an alternative to KM but not KVM. I'll look into it more but I didn't think they were as useful for a headless, for lack of a better work, type setup.

Thanks for the help. I'm definitely still on the hunt myself to see what I can find. Whatever I settle on, if it works, will get posted here for sure.

It just seems odd to me that OBS reacts that much differently simply because of a remote connection and that it performs normally once it's closed. I would expect that behavior if I were trying to stream over a remote connection
 
Last edited:
The log isn't showing me much useful, but I expected that (which is why I didn't ask one). It's just that you're running a graphics based application over Microsoft's RDP and there's a hook somewhere OBS really isn't happy about.

In any case, I hope this gets resolved (or worked around) because I was toying with a similar idea myself...
 
Code: 
12:05:05.334: Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 27411 (79.6%)

Your integrated GPU over RDP is not capable of keeping up. The server needs a proper GPU.
 
Fenrir said:
Code: 
12:05:05.334: Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 27411 (79.6%)

Your integrated GPU over RDP is not capable of keeping up. The server needs a proper GPU.
Click to expand...
But he mentions he gets a smooth stream if he closes the RDP session.
 
Can confirm a GPU makes this much better however over remote connection the end result of the stream still looks like it could be improved. Much better numbers however.

With a 3gb 1060 the frames output and drawn are much better at:

21:57:41.287: Output 'simple_stream': Total frames output: 37695
21:57:41.287: Output 'simple_stream': Total drawn frames: 37801

vs.

12:05:05.334: Output 'simple_stream': Total frames output: 34327
12:05:05.334: Output 'simple_stream': Total drawn frames: 7037 (34448 attempted)
12:05:05.334: Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 27411 (79.6%)

Guess I'll just have to remote in, start, then close the remote connection for now.

Just wanted to update in case anybody else came across this in the future.
 
You must log in or register to reply here.
Back
Top