Sorry ; It's Qp.what is kp?
Try v7.7. I'm use a Type C, and this happens on 10% or less of captures.
Regards
JM
Sorry ; It's Qp.what is kp?
Try v7.7. I'm use a Type C, and this happens on 10% or less of captures.
I looked around similar offsets to the range of buffers we saw in the ipl getimepath 0 results, and I found 16 buffers with live data, a few before the starting buffer shown in the 656x480 P2 pipeline, and several after. I tried filling all of them but still have a flicker. I'm not going to dwell on that issue though---pretty neat to have a histogram regardless, thanks to @0dan0 !Maybe not addressing all six frame buffers correctly.
Qp can't affect this, as this is a encoder value that is ramps too, the first frames are always encoded at QP 25 (or similar). The jitter starts immediately, well before any Qp change is applied. Is just the randomness of these units. I do have some leads on detecting this failure, but adding type D support is taking priority.Sorry ; It's Qp.
Regards
JM
@ThePhage could you also include the 3D printable files in the user manual link? I know there's the camera standoff mod, the lens caps, and a film visibility reducer thing.Awesome! And that’s actually really valuable information for the community here!
mem r 0x80dbf440 0x80 dump addr=80dbf440 length=00000080 to console:
80DBF440 : 802CCBB8 802CCB20 00000790 00000434 ..,. .,.....4..
80DBF450 : 00000790 00000434 00000790 00000434 ....4.......4..
80DBF460 : 00000740 00000408 00000740 00000408 @.......@......
80DBF470 : 00000740 00000408 00000700 000003E4 @..............
80DBF480 : 00000700 000003E4 00000700 000003E4 ...............
80DBF490 : 000006C0 000003C0 000006C0 000003C0 ...............
80DBF4A0 : 000006C0 000003C0 00000680 000003A0 ...............
80DBF4B0 : 00000680 000003A0 00000680 000003A0 ...............
| Modes | Width | Height | Ratio | Aspect |
|---|---|---|---|---|
| 0, 1, 2 | 1936 (0x790) | 1076 (0x434) | 1.80 | 16:9 |
| 3, 4, 5 | 1856 (0x740) | 1032 (0x408) | 1.80 | 16:9 |
| 6, 7, 8 | 1792 (0x700) | 996 (0x3E4) | 1.80 | 16:9 |
| 9, 10, 11 | 1728 (0x6C0) | 960 (0x3C0) | 1.80 | 16:9 |
| 12, 13, 14 | 1664 (0x680) | 928 (0x3A0) | 1.79 | 16:9 |
Do you have any tips on focusing the lens? On my 1st unit the metal 7mm adapter took dozens of tries to thread in, and then it still only threaded about halfway in. With the spacer/model set provided, I cannot get it to focus with the 12mm nor the 16mm lens (from the USA source). I have to lift the piece way up to get any sense of focus. E.g. the yellow part is the spacing gap I have from screwing in and the red bars are the approximate height I have to lift the camera board to get focusing. (I also need to upgrade firmware from five or so months ago's version.)
View attachment 26580
Has anyone tried swapping the camera mount for one of these? Might be easier than having the extra lens ring extension?
Amazon.com : Arducam M12 Mount Lens Holder Set, 8 Styles : Electronics
Amazon.com : Arducam M12 Mount Lens Holder Set, 8 Styles : Electronicswww.amazon.com
View attachment 26581
Lastly, a suggestion on the camera mounts, on my unit the camera bracket rubs the standoff bracket piece it mounts to. Mainly from the box-and-ears shape for clearance is overhung by the dovetail joint receptacle on that piece. If you make another revision, it would be good to make that cut through all parts, not just the thin plate part.
View attachment 26582
That's your photo and lens!A generic 12mm M12 will not work, not any 16mm lenses that I have found. That lens has a different font, and hole not present on any of my AZURE-1228MAC lenses.
| Azure Photonics AZURE-1228MAC 2/3" 12mm F2.8 Fixed Iris M12 (S-Mount) Lens, 10 Megapixel Rated, Near Field (100-500mm W.D.) |
| Azure Photonics AZURE-1622MAC 2/3" 16mm F2.2 Fixed Iris M12 (S-Mount) Lens, 10 Megapixel Rated, Near Field (100-500mm W.D.) |