-
Notifications
You must be signed in to change notification settings - Fork 94
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
10bit dynamic range #45
Comments
Is the mode limited to 320x240? |
I've only tried 640x480, which works. |
@cdoty What settings were you using to get < 1fps? |
Suggest opening another issue for frame rates. I don't know how accurate these values are in terms of the actual resultant frame rate, but for VGA I currently have: ... Note that the type of fps has to change. In the kernel module, I had to modify gspca.h/c and include fixed values for numerator/denominator also. |
Can anyone confirm if 10bit works for them? |
Thanks for those entries @mattipee -- I hope to try 10-bit in the next few days -- if / when I do, I'll report back. |
I don't know what downstream support you'll have for 10-bit, but 8-bit conversion is as simple as dropping every 5th byte - you might test by checking for non-null before you drop. Alternatively, 10-bit to 16bit is relatively easy too, you can left-align the relevant bits from the 5th byte and pad with 0s to create each low-byte. You may already appreciate all of that, but I expect you'll need to implement one or the other. Good luck, @bakercp. Here's a snippet for reference:
You could also use:
But note that (from memory), the 10 bits are right aligned. |
...with the most important change of course being from:
to:
|
Hi, this might be of interest.
I've been playing with the ov534 linux kernel module to add gamma, framerates <1fps, etc, and used your register initialisation routines to get raw output working.
By setting DSP_Ctrl4[0], video format to RAW10 and framesize to 0x017700, I've managed to capture 10bit raw.
Four pixels every five bytes, with the lsb's packed into the fifth byte:
11111111 22222222 33333333 44444444 44332211
The text was updated successfully, but these errors were encountered: