-
Notifications
You must be signed in to change notification settings - Fork 74
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
provide option to select pattern on no video #55
Comments
That is easier to do, I'm pondering about adding a loader later to get any On Mon, Jun 8, 2015 at 6:35 PM, Dave Rice [email protected] wrote:
|
I made some progress at replicated your color bars in v210 but got stuck at padding the line to a multiple of 128. At any rate IMHO simply getting black instead of the color bars is the greater need. I am happy to test. |
And leave the black frame for 10bit for now. Bug-Id: #55
It works for me. Also could also set a new github release? |
Let me shuffle some commits, I'm in the middle of adding support of vanc data now that eventually I have access to content using it. And I have another toy you will like a lot brewing, but probably I'll need your help (more on private email). |
During the recording of files on unstable analog sources, bmdcapture will insert a pattern if there is no video (since 5a844f9). In 8 bit it is a color bar pattern and in 10 bit it is uyvy422 data rendered in v210 so a green/purple partial frame pattern. When working with unstable analog sources there are times when no frame data is received in the middle of a recording and the pattern is used. I propose that the pattern be selectable with color bars as default but including an option for black. I think an inserted occasional black frame would be less distracting to the current way bmdcapture handles unstable signals. I'm attaching two examples of the current state.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/21006611-provide-option-to-select-pattern-on-no-video?utm_campaign=plugin&utm_content=tracker%2F256764&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F256764&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: