Soroush

I was able to reproduce the bug. I modified your code a little and here is the reproduction code: ``` class Program { private static Device device; private static VideoStream...

I will take a look into this. Can you try an older version to see if the problem is there as well or just newly introduced again?

Thanks sumitta, let me take a look at this, I will get back to you asap.

Unfortunately I couldn't reproduce the issue. Tried compiling as both 32 and 64bit and tested with two devices. (Kinect, Asus Xtion) I am going to try it on an other...

Unfortunately as I cant reproduce the bug, I cant debug it either. I ask you guys to try to debug it if you had the time and encountered this bug....

I checked this issue again using the latest release of the library and it wasn't there. But then again I never had this error. So it might be a Kinect...

usually, it's a timing problem. Change the color format to `A8R8G8B8` and try again; otherwise, play with other variables; get the current timing and compare it with the one you...

these files might be useful as an example for grid management (mosaic v2) set of APIs: https://github.com/falahati/HeliosDisplayManagement/tree/master/HeliosDisplayManagement.Shared/NVIDIA otherwise, I have no new input here; the driver can reject a timing...

There is six types of display in NVAPI: 1. `DisplayDevice`: Represents a physical display, your own monitor 2. `Display`: A logical connected display 3. `UnattachedDisplay`: A logical disconnected display 2....

for I2C you need to read DDC documentations. I am not overly familiar with the specifics. isn't `00 FF FF FF` the initial bytes to a valid EDID? well, mine...