Skip to content
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

MediaCapture with GPU based IBasicVideoEffect issue still there #446

Closed
ratishphilip opened this issue Oct 28, 2016 · 20 comments
Closed

MediaCapture with GPU based IBasicVideoEffect issue still there #446

ratishphilip opened this issue Oct 28, 2016 · 20 comments

Comments

@ratishphilip
Copy link

ratishphilip commented Oct 28, 2016

@shawnhar
Hi,

This is regarding the issue reported in #350 and #397.

I am currently using a Lumia 640 with build 14951. Though this issue was fixed in an earlier build (14393), I believe it has returned again. I am still seeing the Media Capture Failed: The parameter is incorrect error message.

Also, whenever I add a new VideoEffect to the VideoPreview stream of MediaCapture, in my own sample application, the CaptureElement does not display any video (just a white screen). Removing the VideoEffect shows the preview normally. ( I have reported it here )

Could you please look into this issue?

@13thsymphony
Copy link
Member

I tried to repro the "parameter is incorrect" issue on two Lumia 950's with 14959, and they both worked.

@ratishphilip
Copy link
Author

@13thsymphony

It is happening on my Lumia 640 with 14951. Are any of the features in Win2d not supported in Lumia 640?

@13thsymphony
Copy link
Member

The previous issue (#350, #397) repro'ed on both the 640 and 950. We still need to investigate what you're seeing, but this suggests it is a new issue.

@ratishphilip
Copy link
Author

As I have elaborated here, if I comment this line in my code, the preview works

var effect = await _mediaCapture.AddVideoEffectAsync(
                new VideoEffectDefinition(typeof(TheEffect).FullName),
                                            MediaStreamType.VideoPreview);

@ratishphilip
Copy link
Author

If I add a IBasicVideoEffect to the VideoPreview, all I see is a white screen.

@13thsymphony
Copy link
Member

Can you try the camera effect demo in the Win2D Example Gallery?

@ratishphilip
Copy link
Author

Yes I did. That's when I am getting the Media Capture Failed: The parameter is incorrect error message.

@ratishphilip
Copy link
Author

Upon debugging I am getting a MediaCapture Failed event after this line

await mediaCapture.AddVideoEffectAsync(new VideoEffectDefinition(typeName, effectPropertySet),
                MediaStreamType.VideoPreview);

win2d_example_error

@ratishphilip
Copy link
Author

@shawnhar @13thsymphony
I updated my Lumia 640 to 14955 yesterday.
I am still seeing the same error.

@13thsymphony
Copy link
Member

I was finally able to get my hands on a Lumia 640 and upgrade the OS to 14955, and this does indeed repro. This appears to be another regression in the underlying OS; we are investigating more.

@ratishphilip
Copy link
Author

@13thsymphony
Thank you. Hope a solution is found soon.

@13thsymphony
Copy link
Member

13thsymphony commented Nov 2, 2016

@ratishphilip
This definitely is a similar (if not identical) regression in the OS as #397. We're working with the platform team to get it fixed.

For my reference, this is internal bug 9637471

@ratishphilip
Copy link
Author

Does this error happen on devices older than Lumia 640? (Like Lumia 550)?

@13thsymphony
Copy link
Member

Our current hypothesis is that the issue hits devices using the Adreno 300 series of GPU (DX feature level 9_3). This includes the 550, but we haven't tried it explicitly. The Lumia 950, for example, uses a 400 series and is not affected (DX feature level 11_1).

@ratishphilip
Copy link
Author

So to effectively use all the features of Win2d and the camera, the baseline device is Lumia 950?

@ratishphilip
Copy link
Author

@shawnhar @13thsymphony
any updates on this bug?

@ratishphilip
Copy link
Author

@shawnhar @13thsymphony
any updates on this bug?
Is it fixed in 14977 build?

@shawnhar
Copy link
Member

shawnhar commented Dec 1, 2016

No, this is not fixed yet.

@shawnhar
Copy link
Member

This issue should be fixed in Windows OS builds from mid-Feb onwards.

@ratishphilip
Copy link
Author

Yes it is. Just checked on my L640.

Thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants