-
-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Camera has green tint and runs with big delay/lag #72
Comments
Hi, there, I have the same issue, I am using surface book as well, have you fixed it? I think the problem might because of the infrared sensor? |
have the same issue when using an app, it seems there's some conflict with some programs , when i use a new install win 10 system on the same machine , there is no this issue |
Having the same issue, using surface pro 4, even after i reinstall win10. |
I still have yet to find a solution to this issue, so I figured I'd maybe give this a bump. The video library that's been made available from the Processing Foundation doesn't appear to be functioning with my surface pro's webcams as well. I run Windows 10 on a Surface Pro (2017 model). I can only view the rear-facing camera and it is dark and green tinted. I have no access to the front camera at all. The frame rate is incredibly low as well. I have found a solution that does not use the video library, but it doesn't really seem like the most useful for experimental use of digital cameras. Plus it utilizes a DirectShow library, which is not open-source. Doesn't solve the issue for the long term. |
How rubbish is this surface pro 4 green colour tint lag, lagging issue... My usual surface pro 4 camera app works absolutely fine but Zoom (zoom.us) conferencing app come out green and really laggy - like ~1 FPS. I tried installing a firmware update as advised here: https://answers.microsoft.com/en-us/surface/forum/all/microsoft-surface-pro-4-camera-green-tintlag/f8b59b09-18ec-478a-9225-4ac95a5e39fc Basically advises installing Microsoft's (25/7/2018) firmware update: (SurfacePro4_Win10_16299_1803001_0.msi) https://www.microsoft.com/en-gb/download/details.aspx?id=49498 This didn't work for me. Although it did bring up this error when trying to view the front facing camera through the native camera app 0xA00F4271(0xC00D3704) which I had to fix previously so for a moment I thought I'd done backwards but then it seemed to work and went away without making any changes that I recollect (computer restart or software/firmware installation anyway) Next step for me is to get in touch with Microsoft Support unless anyone else has found a solution? Zoom app front camera feed (rear camera is the same) |
hello peedubs, i have also meet this issue long ago , and following is my resolution. please update your system to the latest , and check your regedit. if you find the EnableFrameServerMode , please remove it and have a try |
I have the same issue on surface pro 6(windows 10 1809). |
The above registry setting worked to fix my issue! Thanks! I fought and fought with this problem. Camera worked fine in the camera app and the skype for business video, but had a very dark green tint/hue to zoom video and 8x8 video. |
What registry setting are you referring to?? This is making me crazy!! |
Please tell me what I need to do as if you are talking to 5 year old. I have looked where I thought were the obvious places but have no clue what to do now. |
Are you having this issue with the surface?
Adrian Young
612-343-8169
ag.young@mac.com
… On May 13, 2020, at 5:14 PM, aj40something ***@***.***> wrote:
What registry setting are you referring to?? This is making me crazy!!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Yes, most frustrating!
On Wed, May 13, 2020, 6:05 PM greentintgone <notifications@github.com>
wrote:
… Are you having this issue with the surface?
Adrian Young
612-343-8169
***@***.***
> On May 13, 2020, at 5:14 PM, aj40something ***@***.***>
wrote:
>
>
> What registry setting are you referring to?? This is making me crazy!!
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#72 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APSKGNKKTFRRWROCVTRPX4TRRMRURANCNFSM4DN53QUQ>
.
|
Ok.
Launch RegEdit
Once you’re in the registry editor go to these folders. They will show up on the left side.
[HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Windows Media Foundation\Platform]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\Platform]
** In both of these folders above delete the sword that shows up titled enableframeswrvermode.
DWORD under both keys titled : EnableFrameServerMode with value set to 0 needs to be deleted
Adrian Young
612-343-8169
ag.young@mac.com
… On May 13, 2020, at 5:14 PM, aj40something ***@***.***> wrote:
What registry setting are you referring to?? This is making me crazy!!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Thank you! Looks like it worked!!
On Wed, May 13, 2020 at 8:59 PM greentintgone <notifications@github.com>
wrote:
… Ok.
Launch RegEdit
Once you’re in the registry editor go to these folders. They will show up
on the left side.
[HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Windows Media
Foundation\Platform]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\Platform]
** In both of these folders above delete the sword that shows up titled
enableframeswrvermode.
DWORD under both keys titled : EnableFrameServerMode with value set to 0
needs to be deleted
Adrian Young
612-343-8169
***@***.***
> On May 13, 2020, at 5:14 PM, aj40something ***@***.***>
wrote:
>
>
> What registry setting are you referring to?? This is making me crazy!!
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#72 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APSKGNNLROKFA63HOG7RGX3RRNGBNANCNFSM4DN53QUQ>
.
|
Hello all, I went to the Registry Editor app and searched for the mentioned sword on both folders, but I didn't find them. Am I doing something wrong? My problem is that my video captured in real time in the Processing 3 program is also green tinted and very, very slow. If anyone knows what to do and doesn't mind sharing I would appreciate it very much. |
I made an account to say that this was my issue. Microsoft help desk told me to make it and never said to delete it after my camera worked again! Thanks!! |
Hi guys, I have the same problem in Processing 4. The video captured is green-tinted and has large delays. I tried to create a EnableFrameServerMode in regedit, but it doesn't work for me. If anyone knows what to do, please share the solution I would appreciate it very much. |
Thank you YuxuanLing, running the registry as administrator and deleting the two dwords did the trick. It is incredible how shitty the service at Microsoft is. I use MS's skype and a MS surface comp. |
Hi, I have the same issue here. I tried going into the suggested registry locations, but there weren't the mentioned files. |
Try installing the latest GStreamer library on your system, so the video processing library will use this version instead of the older 1.20.x version. I installed GStreamer 1.24.6 on my Surface Pro, and it works. |
Do you mean this? https://gstreamer.freedesktop.org/download/#windows |
Yes. I installed MSVC 64bit 1.24.6 runtime and development. |
When I try to display an image from my camera it gets displayed with a green tint to it. It should also run at 30 fps but it runs really laggy. It's also got a big delay.
OS: Windows 10
I'm having this problem on a Surface Book and I've heard of many other surface users who have the same problem. Someone suggested, that the green tint could be from the depth data from the camera.
Greetings
TheCodec
The text was updated successfully, but these errors were encountered: