search

dotnet / iot

This repo includes .NET Core implementations for various IoT boards, chips, displays and PCBs.
MIT License
2.14k stars 577 forks source link

Request a way to keep the camera open in VideoDevice #1093

Closed HumJ0218 closed 3 years ago

HumJ0218 commented 4 years ago

There are many cameras that grab pictures immediately after initialization, and there will be an unstable picture situation, ex. a full-green or black frame.

How about adding a method to keep the camera open. So users can make a delay before capture a image to avoid the green frame?

@ZhangGaoxing

krwq commented 4 years ago

I wouldn't mind if camera stayed open for whole lifetime of the class

P.S. I couldn't not notice your description "What the hell is HUB75E?" - HUB75 is LedMatrix driver, My guess is that E refers to number of connected pins, in many cases E stays disconnected - i.e. in our implementation we have a setting to pick between 64/32 row matrix, in case of 32 the E is disconnected.

HumJ0218 commented 4 years ago

@krwq Thank you for your explanation. My understanding is that the ABCDE five lines are inputs from a 5-32 decoder to select the current pixel line. I have this doubt because I bought a 128x64 RGB LED screen with a label HUB75 besides interface and only have ABC three lines to select 32 pixel lines as line selector. After some research I found that these three lines are inputs of a group of shift registers. The outputs lead the pixel lines.

My question is whether there are multiple HUB75 implementations, and they are not compatible with each other.

krwq commented 4 years ago

I'm not sure - I suspect people implement everything specially for their devices and once they get it to work they just don't care about making it compatible with other versions (unless they have both). Basically better to stick to stuff which has specification which can be read in one way - HUB75 is probably one of the worst documented protocols IMO (I've spent hours on it already)

Ellerbach commented 3 years ago

@HumJ0218 , did you have a chance to look at the PR #1163? This should solve your issue. Please let us know so we can work on the PR and merge it. Let me know if you need any help.

HumJ0218 commented 3 years ago

@Ellerbach OK. I'll try it on weekend

Ellerbach commented 3 years ago

[Triage] Regarding the request and the PR #1163, this seems to be addressed.