You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CaptureDevice.StartRecordingAsync calls a StspMediaSinkProxy method 'InitializeAsync' with parameters in the wrong order.
As presented, line is: var mfExtension = await mediaSink.InitializeAsync(encodingProfile.Audio, encodingProfile.Video);
Should be: var mfExtension = await mediaSink.InitializeAsync(encodingProfile.Video, encodingProfile.Audio);
To Reproduce
Code actually works as presented, but I think it takes longer to Initialize.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
This is just a typo in the header file. The implementation and callers all use Video/Audio. But the prototype in the header has them swapped. The code is actually correct, which is why it works as presented. I'll fix the header.
* IoT-GPIO: Remember event token so we can unsubscribe later #1247
* SimpleCommunication: Fix typo in parameter ordering (code worked, but names were backward) #1294
* WiFiDirect: Fix build #1319
* Delete obsolete samples templates
Which sample are you reporting a bug in?
SimpleCommunications
Describe the bug
Problem with line of code in CaptureDevice,cs.
CaptureDevice.StartRecordingAsync calls a StspMediaSinkProxy method 'InitializeAsync' with parameters in the wrong order.
As presented, line is: var mfExtension = await mediaSink.InitializeAsync(encodingProfile.Audio, encodingProfile.Video);
Should be: var mfExtension = await mediaSink.InitializeAsync(encodingProfile.Video, encodingProfile.Audio);
To Reproduce
Code actually works as presented, but I think it takes longer to Initialize.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Configuration
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: