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

Switching from Win8 Desktop Duplication to WinAPI as capture source doesn't work #37

Closed
alexdie opened this issue May 17, 2016 · 5 comments

Comments

@alexdie
Copy link

alexdie commented May 17, 2016

When switching capture sources from desktop duplication to WinAPI while Lightpack is running the setting isn't applied and lightpack needs to be restarted in order to apply the setting.

@alexdie alexdie changed the title Switching from Win8 Desktop Duplication to WinAPI as capture source r Switching from Win8 Desktop Duplication to WinAPI as capture source doesn't work May 17, 2016
@psieg
Copy link
Owner

psieg commented May 18, 2016

Hi,

unfortunately I can't reproduce the problem. Can you give more details (how do you know which grabbing is active?) or provide a log file?

Best

@alexdie
Copy link
Author

alexdie commented May 18, 2016

I discovered this behaviour (or thought I did) while gathering information for #38 .

I have issues while using Win8 Desktop Duplication and no issues when using WinAPI capturing. However, switching from Win8 Desktop Duplication to WinAPI while Lightpack is running doesn't alleviate the issues, I need to restart Lightpack. That is why I - maybe wrongly - assumed the capture source wasn't switched properly.

Where are the log files for Lightpack located?

@psieg
Copy link
Owner

psieg commented May 18, 2016

The logs are at C:\Users\You\Prismatik\logs\ I didn't have time to reproduce #38 yet

@alexdie
Copy link
Author

alexdie commented May 18, 2016

Prismatik.1.txt
Prismatik.0.txt

In the .1. log I started Lightpack in Win8 Desktop Duplication mode and started Dota 2. I then switched to WinAPI capturing. The fps issues are still present. I quit Lightpack and restart it, starting the .0. log. Everything is back to normal performance.

@psieg
Copy link
Owner

psieg commented May 26, 2016

According to the logs, the grabber switch is done as expected. This is I believe indeed just a "shadow" of #38, but not a bug in itself, as switching seems to work.

@psieg psieg closed this as completed May 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants