Search results

What did the unstable image look like? I don't know if the manual exposure control is at the same address. We need someone with Type B unit, add has a serial port, to test this.

I keep find things the developers did wrong, or didn't care. H264 has two common color spaces, Rec709 broadcast range, and Rec709 full range. A decade ago (where this tech originates) many developers didn't set the flag to say which (like on Reels.) The assumption with no flag for media...

Version 5.6 attached This is the first version with both manual white balance and exposure. While the code changes for manual exposure are small, there a lot other changes in this build. With each version I change the boot screen and shutdown screen JPGs. There are the same image, yet they...

A benefit of running a manual exposure, there is now lower noise. My bit-rate control is going to highest Qp limit (19), and staying there, as the images are cleaner.

Feedback needed. I have found how to set the exposure to full manual, and you only need a working serial port. From the command prompt > ae set <ISO> <exposure time in µs> 0 e.g. > ae set 50 8191 0 ISO (in hex) is 32 to 640 (50 to 1600) - the auto exposure does increase ISO Exposure (in...

Firmware V5.5 attached This new firmware includes a grey frame detector to stop the capture automatically when the file is run out at the end. While I haven't had it fail. I do have the sprocket hole visible, as the detector is using the luma minimum to maximum in the frame, a low...

Version 5.4 attached. I was able to find a way to stop the motors in the event of encoder crash. While running at 50Mb/s has its risks, now at least you only have to wind back 5-6 frames, restart the unit, and continue. Some code has been moved to create more coding space, plus some work in...

No progress report. Does anyone know how to control the motors? I would like to have a control to disable them. FUN_001069d8(0, 0x4000001, 1, 0); Seems to be a call to shutdown the unit, but when I use it it gets into a loop before the motors are switched off. I expect there is another...

This is a more robust design for alignment for sure. Sorry to here about the broken sensor clip. I'm surprised mine stills works after so many removals, and my thread on the original lens mount is toast. I'm thinking I purchasing a second unit, but I would like to make show it is not type...

Version 5.3 attached. Just bit-rate stability, last version would lower the Qp to a limit of 16, but for some reels this would crash. This build uses 19 at the lowest Qp value, no other code changes. Scanned for hours on this setting. Bit-rate averaging 48Mb/s. I was hoping to get 80Mb/s...

Left is completely stock, with original auto white balance, and yes is happens to get the WB pretty good for this segment, but it all over the place through the video. The fixed/locked WB is a tad too blue, but is easy to fix in post. Here is a short version at 4K, as youtube preserves more at...

Version 5.2 Attached. The bit-rate now averages around 55Mb/s, and gentler version of the new rate control. At 80Mb/s there was still a few capture failures, so still some work to do. This build also adds 18fps as the default. At address 0x1ef984 use 0x60EA for 20fps and 0xF0D2 for 18Hz...

I just completed a 2GB capture (3+ minutes of footage) at 82Mb/s (10MB/s). This is using a prototype of the rate control I'm working on. Here is my new console output. Every two frames the Qp is lowered by one. If the bitrate is stressing buffers, the Qp is increased by 2 or 4, depending on...

@ThePhage Thank you for the nice feedback. I have never done anything like this before, any firmware reverse engineering. I've never worked with MIPS code, or Novatek SoC. My experience is as a C developer in camera development and video compression, so normal "forward" engineering. So I do...

I'm using a SanDisc Extreme Pro, rated to 100MB/s, the scanning is only using ~0.5MB/s. It is an internal limitation to the way the buffering is done (I'm guessing.) This is old dashcam tech, not designed for quality. Reels was originally putting out only 8Mb/s (1MB/s at playback speed, encode...

Here is another post to document all my firmware changes to date. Address map of changes to Type-C Reels firmware (should help in supporting other types) 0x13a2f0 - I'm hooking a function call to 0x13b4b0 that set up the input buffer address (either the read or write location) Hook code is...

Attached in V5.0 firmware. Locked quantization: QP25 Locked white balance: RGB weights 1.75, 1.0, 1.0 Pipeline resolution: 1600x1200 (to use all of this you need to replace the lens) Encode resolution: 1600x1200 I moving the seconds input buffer any to just after the encoding working space...

I went through a lot of lenses. It has to be a macro lens, and they are rare (or at least poorly described.) Also with any lens you will need a spacer to move the lens further away from the sensor to focus. Optically a 12mm lens would be 12mm from the sensor to focus at infinity, here we need to...

3D printed the lens offset. Attached is more model for the 3D print. Now my frames in focus and not skewed. There is even space between the lens, and the open film loading door. V4.2 (Type C) still occasional saw a buffer collision between the compression data, and the second input frame...

V4.1 (Type C) I was incorrectly running QP23, which failed on some scenes, so this is running QP28.