Running OBS (any variant) causes steamvr to lose tracking?

[Miss Stabby]

Since i got the index i have been having some minor tracking outages for a few seconds at a time. I mostly ignored them as they were far and wide inbetween them.
Also for the past months i used OBS to stream my VR onto twitch.
Though a few weeks ago i noticed steamvr gotten problematically bad with steamvr's tracking failing for several seconds only to return for 1 or 2 seconds before losing position again.

First i thought it might've been the USB controller or some other driver. However after switching things around, reinstalling all drivers and varying some other settings i managed to track the problem to OBS running in the background causing steamvr to lose sight of the lighthouses.
When i close down OBS i can play vr decently (though far from the flawless results i had with the vive)

The problem though is that i would like to keep streaming vr games on twitch, and now i can not.

My current setup:
Win 10 x64
I7 5960x
Asus X99E-WS
EVGA Nvidia 980Ti
32GB DDR4
M.2 Samsung Evo 970 ssd
Index VR HMD (retail, 1st wave)
Knuckles (EV3) controllers
HTC Vive (pre) lighthouses (running in a wired sync config)
SteamVR 1.8.14 (tried both beta and non-beta both suffer the same outages)
OpenVR Advanced Settings 3.2

When i open the steamvr console there is a loop that keeps showing up between the tracking working and failing again:

 Wed Oct 23 2019 22:11:59.769 - lighthouse: Saved LighthouseDB rev 95091 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.json
Wed Oct 23 2019 22:12:00.767 - lighthouse: LHR-DA7729DD: Triggered keepalive (failed)
Wed Oct 23 2019 22:12:00.873 - lighthouse: LHR-DA7729DD: Triggered keepalive (succeeded)
Wed Oct 23 2019 22:12:01.757 - lighthouse: LHR-DA7729DD: Packet received after 1.000s, keepalive (9/1)
Wed Oct 23 2019 22:12:05.437 - lighthouse: LHR-DA7729DD: Triggered keepalive (failed)
Wed Oct 23 2019 22:12:05.539 - lighthouse: LHR-DA7729DD: Triggered keepalive (succeeded)
Wed Oct 23 2019 22:12:06.426 - lighthouse: LHR-DA7729DD: Packet received after 1.001s, keepalive (9/1)
Wed Oct 23 2019 22:12:07.315 - lighthouse: LHR-DA7729DD: Triggered keepalive (failed)
Wed Oct 23 2019 22:12:07.419 - lighthouse: LHR-DA7729DD: Triggered keepalive (succeeded)
Wed Oct 23 2019 22:12:08.306 - lighthouse: LHR-DA7729DD: Packet received after 1.001s, keepalive (9/1)
Wed Oct 23 2019 22:12:16.177 - lighthouse: LHR-DA7729DD: Triggered keepalive (failed)
Wed Oct 23 2019 22:12:18.183 - lighthouse: LHR-DA7729DD H: Resetting tracking: no optical samples for 2045ms
Wed Oct 23 2019 22:12:18.183 - lighthouse: LHR-DA7729DD H: Dropped 5470 back-facing hits during the previous tracking session
Wed Oct 23 2019 22:12:18.183 - lighthouse: Stopped tracking with universe 1562657760
Wed Oct 23 2019 22:12:21.263 - lighthouse: LHR-DA7729DD: Triggered keepalive (succeeded)
Wed Oct 23 2019 22:12:22.167 - lighthouse: LHR-DA7729DD: Packet received after 6.002s, keepalive (8/1)
Wed Oct 23 2019 22:12:22.167 - lighthouse: LHR-DA7729DD H: tdm sync lost
Wed Oct 23 2019 22:12:22.175 - lighthouse: LHR-DA7729DD H: tdm sync acquired
Wed Oct 23 2019 22:12:23.285 - lighthouse: LHR-DA7729DD H: No optical frames in past 5 seconds
Wed Oct 23 2019 22:12:23.595 - lighthouse: LHR-DA7729DD: Triggered keepalive (failed)
Wed Oct 23 2019 22:12:23.697 - lighthouse: LHR-DA7729DD: Triggered keepalive (succeeded)
Wed Oct 23 2019 22:12:24.585 - lighthouse: LHR-DA7729DD: Packet received after 1.000s, keepalive (9/1)
Wed Oct 23 2019 22:12:27.616 - lighthouse: LHR-DA7729DD H: ----- BOOTSTRAPPED base E18D46FA (immediate) distance 1.53m velocity 0.01m/s base pitch ~65.8 deg roll ~-3.1 deg -----
Wed Oct 23 2019 22:12:28.285 - lighthouse: LHR-DA7729DD H: Optical frames received again...
Wed Oct 23 2019 22:12:29.282 - lighthouse: LHR-DA7729DD H: ----- CALIBRATED base E18D46FA at pitch 64.89 deg roll -2.07 deg -----
Wed Oct 23 2019 22:12:29.282 - lighthouse: Updating tilt for E18D46FA:  Old= 64.94, -1.97, 2.2621e-06 <- 0.09 deg -> new= 64.89, -2.07, 4.57759e-06   result=64.89, -2.07, 4.57759e-06
Wed Oct 23 2019 22:12:29.282 - lighthouse: Best tilt from LHR-DA7729DD for base E18D46FA pitch 64.89 roll -2.07 score 2.98
Wed Oct 23 2019 22:12:29.282 - lighthouse: BootstrapFinished setting tilt base to E18D46FA
Wed Oct 23 2019 22:12:29.282 - lighthouse: Selected existing universe 1562657760 (E18D46FA is primary)
Wed Oct 23 2019 22:12:29.282 - lighthouse: Setting universe tilt from E18D46FA via transform to global: pitch 64.89 deg roll -2.07 deg
Wed Oct 23 2019 22:12:29.290 - lighthouse: Saved LighthouseDB rev 95092 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.json

After this the same log keeps repeating with tracking coming back and failing straight away repeatedly.

[bendotcom]

I would guess that OBS is opening a camera (maybe even the one in the HMD) and causing extra USB traffic that is causing tracking related USB traffic to be de-prioritized by Windows.

[BOLL]

I'm far from an expert on this, but I would try a few things:

1. Re-seat the sync cable
   
2. Try the optical sync, might have to move a station because I guess you are using the cable for a reason
   
3. Re-seat power cables, maybe one is border-line disconnected and is giving a fluttering power delivery due to vibrations
   
4. See if it acts the same with just one base station turned on, either one in turn. I think that means it should be in mode B if my memory serves, not sure as I've ever only run 1 base by mistake.
   
5. Remove that full body mirror you just installed on a wardrobe door... oh wait, maybe that was me!

[BOLL]

Oh yeah, as Ben mentioned, USB things can go crazy. I had an ElGato Camlink connected which after a Windows update would cause one core to be saturated by kernel load, completely lagging my system.

How I found that out was to create a second scene collection in OBS, this will unload your previous sources including capture devices, restart the application with the empty collection and see if the problem still persist.

[Miss Stabby]

already looked into the camera being a issue, currently i have disabled the camera on a system level (device manager > index camera > disable this device) and in steamvr disabled the camera
It doesnt show up as a available source in OBS but it still gives me the tracking issues, forgot to mention this in my first post