Search results

Oopps, I had the red offset wrong: Default values should be: WBAL (current defaults) 2.0 592,256,256 1.5 560,256,256 1.0 528,256,256 0.5 496,256,256 0.0 464,256,256 -0.5 464,256,288 -1.0 432,256,320 -1.5 304,256,448 -2.0 256,256,448

It will not. Only the AZURE-1228MAC 2/3" 12mm F2.8. The lenses need to be designed as a macro.

My three units.

That is the older design, use the STLs linked in https://tinkerdifferent.com/threads...-film-digitizer-firmware-hack.2897/post-42590

I would replace that unit.

1) stick with the the known lens 12mm at 2.8mm. I have three units running 2.8mm all work great. Use: https://www.rmaelectronics.com/azure-photonics-azure-1228mac/ 2) Latest 3D spacers: https://tinkerdifferent.com/threads/modding-the-kodak-reels-8mm-film-digitizer-firmware-hack.2897/post-42590...

Why did twenty people (so far) download NewNtkTools2025.zip, this is for developers to "customize firmware". I was just sharing a change to one the tools I'm using, I only expected maybe Mac84, and one other to try it. If there are more out there want to try extending the firmware, let me know...

The Picture setting still set the white balance like before, with has a maximum of 9 WB settings. Now during recording you can tweak red, green and blue, up and down as much as you like, it will remember any changes. Unfortunately I yet to implement a reset, to restore the defaults. The...

Here is v7.5. Additions: - You can customize all the RGB gains for white balance, to deal with very blue (or red) film. - The font has been increased in size for improve readability. - FPS, EV, Qp and Frame count are now only during capture. Bug fixes: - Sometimes the ISO/Shutter wasn't...

Thank you. Many people have offered donations, which I have generally ignored, as it would not be a positive motivation for me. If I felt I was being paid for this, in anyway, it wouldn't be as fun. But I have a solution. This project of reverse engineering a consumer product is in the grey...

> what are the steps to change the frame rate from 16 to 18fps, and also manipulate the auto exposure? Use the up and down arrows move the square braces between controllable settings, +/- change the settings. These are only changeable during record.

Here is v7.4.1. Just a bug fix (although important.) If the permanent memory was in the wrong state (7.4.0 wasn't initializing it), the unit could have been locked to the wrong exposure values, with no way to change it. This version will reset the locked exposure settings on firmware update...

I had wound the focus until tight, but it wasn't yet perfectly in focus, need to more threads to turn. Nothing to do with the unit type. The different slim heights is so that one if will likely work, providing useful threads on the lens to dial in the focus.

As my Type C was stock, the resolution too low for me, I just lens modified my fourth scanner. This time I found I couldn't focus, likely as the 7mm lens extender wouldn't screwing flush with the cheap plastic lens mount. This 3D print has three different slim heights given more options if...

Try my test of many short captures. If my units is 9% error rate, but your closer 50%, that is different might be setup, reel skid tension, or just a hardware difference. My unmodified type C (stock lens, no serial port), had zero jitter in the first 10 captures. To test it like in had a new...

That is correct for this version, but in the next it will be simply threshold limited.

As for jitter, I have capture 45 ~100 frame clips (long enough to see jitter.) Only 4 of the 45 had jitter, this is why it is hard to debug, with only ~9% error rate is hard too measure if an change has improved things. However three of the four bad captures, all had a weird overexposed first...

The bug is both more minor than I thought and might not be worth improving. The minimum Qp is working to limit the scanner stress. When the scanner is stressed with too much data from compression, it adjusts the Qp upward 3 or 6. This part is working. If the scanner is not stressed, it will...

You are correct, for some reason 22Mb/s is the lowest, I can get higher bit-rate, but not lower. Found the bug. 7.4.1 shortly

I've updated the Type C download (above) to have the updated folder name. Unfortunately there is nothing in the build that changes the randomness of the startup jitter. The cause is still completely unknown. As for the jitter drift relating to compression, that is still an unproven theory...