I concur with your goal to focus on improving image quality before pursuing "convenience" features. That said, a lot of questions / complaints could be avoided if the stock features that no longer work as a result of the firmware mods would be hidden / disabled in the UI. Video playback is one example; I believe that on-device SD card formatting is another.
Modding the Kodak Reels 8mm Film Digitizer (Firmware Hack)
- Thread starter Mac84
- Start date
I wish you luck with the 16mm macro lens... IMHO, the ultimate "practical" goal would be to determine a lens / spacing combo that maximizes image capture quality while eliminating the need to cut the case or otherwise void the manufacturer's warranty.
I really want to upgrade the stock lens, but I'm equally reluctant to cut into the case, voiding the unit's 1-year warranty. (I'm scheduled to receive my new unit tomorrow.)
It has an AGC, just not as fast as the stock FW. It is has limits to prevent too much gain lift black too much into grey. The speed of the ACG could be a control, but you will find there is not perfect setting.
Unfortunately change anything in the UI is likely much more work than quality enhancement. All changes are through educated guesses at best, modifying the binary of the firmware, there is no source code to work from. The only UI elements I've successful changed is the boot JPEG, and one word, in one language only.
It is very unlikely that there is a macro lens, with sufficient quality, and doesn't require a different mounting position. I've tried a dozen lenses, only one is good so far (with a mount move.)
What timing 
Great find on the US supplier lens. I'd looked several times and never found one with all the right specs it seems. That's definitely more palatable than the shipping from the UK or the 50% tax from China. The IR question came about because the Chinese seller offered both versions of the lens.
Could you explain how the 5mm spacer need came about? I see you said it had something to do with how far the lens needs to be from the sensor, but I was lost after that.
Great find on the US supplier lens. I'd looked several times and never found one with all the right specs it seems. That's definitely more palatable than the shipping from the UK or the 50% tax from China. The IR question came about because the Chinese seller offered both versions of the lens.Could you explain how the 5mm spacer need came about? I see you said it had something to do with how far the lens needs to be from the sensor, but I was lost after that.
Use a 7mm spacer, it will require less device modifications.
Extension ring: https://www.m12lenses.com/7mm-Metal-Extension-Ring-for-M12-Mount-p/pt-erm12-700m.htm
Extension ring: https://www.m12lenses.com/7mm-Metal-Extension-Ring-for-M12-Mount-p/pt-erm12-700m.htm
@larryc39 When you install your replacement lens and spacer, would you be willing to document and share the process (preferably with photos) for those of us who are a bit nervous about damaging our units?What timing
Could you explain how the 5mm spacer need came about? I see you said it had something to do with how far the lens needs to be from the sensor, but I was lost after that.
Enough enhancement already to release 7.0.
- Added auto exposure back into preview
- Added ISO 50 back to the exposure range
- Added Tint -2.0 is now true B&W
Let me know if you seeing much jitter in 7.0, as the preview auto exposure was originally disabled to reduce jitter. Now the preview auto exposure biases to a short shutter, hopefully to achieve the same jitter reduction. I'm not seeing any jitter my brief testing.
Last edited:
Bummer! I still like the hack idea you proposed way back in February in post #317 of "frame control for 18 or 24, would be nice (20 is weird)". I agree that 20 is weird. Actually, I would prefer 16 fps for my regular 8mm film, to match the original filming speed. However, I can certainly deal with a hardcoded value of 18 (using ffmpeg after encoding to manually convert from 18 fps to 16) if you are unable to add frame control to the UI without access to the fw source code.
Setting 16fps in your own firmware is straightforward.
Type A/B - offset 0x1fe974
Type C - offset 0x1fe984
0xD2F0 is 54000. 54000 / 3000 = 18fps
For 16fps, 16 * 3000 = 48000 in hex 0xBB80
So change the four characters with the .rbn file to 80 BB (little endian), run the NtkTool Pack Firmware option, and the firmware will now encode 16fps files.
I'm trying out a new version of #7. The first set is from a black and white film, where everything is at 0 and only the white balance changes.
The second set is a color film and like the first set, everything is at 0 and only the white balance changes.
It is firmware version "C".
The second set is a color film and like the first set, everything is at 0 and only the white balance changes.
It is firmware version "C".
I could bias the the white balance, so 0 is closer to normal. T
// Plus +2.0 to -2.0
if(*whitebal == LVL_P20) { r = 0x1C0; g = 0x100; b = 0x100; } //1.75,1,1
if(*whitebal == LVL_P15) { r = 0x180; g = 0x100; b = 0x100; }
if(*whitebal == LVL_P10) { r = 0x140; g = 0x100; b = 0x100; }
if(*whitebal == LVL_P05) { r = 0x120; g = 0x100; b = 0x100; }
if(*whitebal == LVL_000) { r = 0x100; g = 0x100; b = 0x100; } //1,1,1
if(*whitebal == LVL_N05) { r = 0x100; g = 0x100; b = 0x120; }
if(*whitebal == LVL_N10) { r = 0x100; g = 0x100; b = 0x140; }
if(*whitebal == LVL_N15) { r = 0x100; g = 0x100; b = 0x180; }
if(*whitebal == LVL_N20) { r = 0x100; g = 0x100; b = 0x1c0; } //1,1,1.75
So currently WB of 0 has unity RGB gains (the reason it is as it is.)
Reasons to add bias. The sensor doesn't seem to be very red sensitive, and the back light is very blue. Will address in the next release
// Plus +2.0 to -2.0
if(*whitebal == LVL_P20) { r = 0x1C0; g = 0x100; b = 0x100; } //1.75,1,1
if(*whitebal == LVL_P15) { r = 0x180; g = 0x100; b = 0x100; }
if(*whitebal == LVL_P10) { r = 0x140; g = 0x100; b = 0x100; }
if(*whitebal == LVL_P05) { r = 0x120; g = 0x100; b = 0x100; }
if(*whitebal == LVL_000) { r = 0x100; g = 0x100; b = 0x100; } //1,1,1
if(*whitebal == LVL_N05) { r = 0x100; g = 0x100; b = 0x120; }
if(*whitebal == LVL_N10) { r = 0x100; g = 0x100; b = 0x140; }
if(*whitebal == LVL_N15) { r = 0x100; g = 0x100; b = 0x180; }
if(*whitebal == LVL_N20) { r = 0x100; g = 0x100; b = 0x1c0; } //1,1,1.75
So currently WB of 0 has unity RGB gains (the reason it is as it is.)
Reasons to add bias. The sensor doesn't seem to be very red sensitive, and the back light is very blue. Will address in the next release
Beta v7.1 for Type B. Please test if I broken anything.
Changes:
Exposure: Went back to ISO 100-400, as was seeing more exposure stepping with ISO 50.
White balance: 0 is now normalized to color of the backlight.
FPS: is now selectable between 16, 18 and 24fps. Long hold on up or down, arrows to increase or decrease the frame rate. You will be remembered, and can be changed during capture, as the value is only unused as the capture is stopped.
I will do Type A & C soon after positive feedback on the Type B build.
Selectable Frame Rate: Outstanding!!!!!!!! Can't wait to get cracking with my C model, but will gladly wait.
"Official" V7.1 for Types A,B & C
Please test if I've broken anything (more, other 64GB+ support and Playback).
Changes:
Exposure: Went back to ISO 100-400, as was seeing more exposure stepping with ISO 50.
White balance: 0 is now normalized to color of the backlight.
FPS: is now selectable between 16, 18 and 24fps. Long hold on up or down, arrows to increase or decrease the frame rate. You will be remembered, and can be changed during capture, as the value is only unused as the capture is stopped.
updated with v7.1.1 (fixing the fps issues)
Please test if I've broken anything (more, other 64GB+ support and Playback).
Changes:
Exposure: Went back to ISO 100-400, as was seeing more exposure stepping with ISO 50.
White balance: 0 is now normalized to color of the backlight.
FPS: is now selectable between 16, 18 and 24fps. Long hold on up or down, arrows to increase or decrease the frame rate. You will be remembered, and can be changed during capture, as the value is only unused as the capture is stopped.
updated with v7.1.1 (fixing the fps issues)
Last edited:
@0dan0
I just ran V7.0 on Type C without issue.
Can you give me a quick refresh on settings ... is this correct?
WB: 0.0
Sharp: -1
Tint: 0.0
Frame adjust/zoom: whatever
Just flashed Type C to 7.1, gonna do a 50' reel now.
Ordered my lens!
Thank you so much for all this work!
I did new tests and the color matches in my opinion. The speed is worse. With 16 set the real speed is 5.333. With 18 it is 6 and with 24 it is 8. It looks like you need to multiply by 3.
Hopefully this will help you. I really admire your knowledge and selfless help for those of us who can't do this. Many thanks.
Hopefully this will help you. I really admire your knowledge and selfless help for those of us who can't do this. Many thanks.
Last edited: