Modding the Kodak Reels 8mm Film Digitizer (Firmware Hack)

[fishgee]

Hey all, just picked up a used Kodak Reels sn: D3024148BKxxxx which should be a Type B firmware.

Before flashing the 1440p mod I had a question on what the typical file size for the common regular 8 reels at the new resolution and bitrate, e.g. 50 ft, 100 ft and 200 ft?

Thanks in advance.

I'm using the 5.8 version right now, and the file sizes for 3" - 50 foot reels is coming in just under 700MB per reel. I realize the B firmware isn't available in version 5.8 (yet ;-) ), but it should give you some indication of what to expect.

 

[NotaNumber]

I'm using the 5.8 version right now, and the file sizes for 3" - 50 foot reels is coming in just under 700K per reel. I realize the B firmware isn't available in version 5.8 (yet ;-) ), but it should give you some indication of what to expect.

Thanks for the info. Maybe I'll bite the bullet and flash the B firmware or may be wait for the type B v5.x.

I have to order some leader and splicing tapes anyway.

Edit: I couldn't wait. The firmware loaded and files as scanned with the modded settings. Playback and thumbnails on the scanner show green and magenta patches but playback of the files on my PC are "normal".

Attached are mediinfo screenshots on files scanned with original vs version B firmware.

I am curious about the encoded time and date. The date appears fixed and the time perhaps random. Does the date have any relationship to the original firmware version?

 

[0dan0]

Hi folks,

I'm still around and need to revisit more Reelz hacking. I finished scanning all my families 8mm and Super8 from the 60s and 70s, about 4 hours run time, so that took a while. So I needed new sources to continue this hacking hobby. So I'm now shooting my own modern 100D Ektachrome, using a Super8 camera from the 70s. Also can now do film development at home, so other that film and development chemicals, I can shoot, develop and scan in about 3 hours. I did find the fixed WB was wrong for modern film, and my development look, so I need to add a user control for WB Auto and manual.

I'm very slow hacking Type A and B units, now with fixed WB, not much else yet. Having units at different stages helps for progress comparisons.

Shot this film yesterday:

 

[domb84]

Hi folks,

I'm still around and need to revisit more Reelz hacking. I finished scanning all my families 8mm and Super8 from the 60s and 70s, about 4 hours run time, so that took a while. So I needed new sources to continue this hacking hobby. So I'm now shooting my own modern 100D Ektachrome, using a Super8 camera from the 70s. Also can now do film development at home, so other that film and development chemicals, I can shoot, develop and scan in about 3 hours. I did find the fixed WB was wrong for modern film, and my development look, so I need to add a user control for WB Auto and manual.

I'm very slow hacking Type A and B units, now with fixed WB, not much else yet. Having units at different stages helps for progress comparisons.

Shot this film yesterday:

I should have a bit of time this week to look at the M127 firmware again and seeing if I can get a modded one booting. Do you know if any of the fixes you've applied would work on the one I uploaded? i.e. are there any matching code across the firmwares? Perhaps you have a list of hex codes that you modified I can check against?

 

[ThePhage]

Hi folks,

I'm still around and need to revisit more Reelz hacking. I finished scanning all my families 8mm and Super8 from the 60s and 70s, about 4 hours run time, so that took a while. So I needed new sources to continue this hacking hobby. So I'm now shooting my own modern 100D Ektachrome, using a Super8 camera from the 70s. Also can now do film development at home, so other that film and development chemicals, I can shoot, develop and scan in about 3 hours. I did find the fixed WB was wrong for modern film, and my development look, so I need to add a user control for WB Auto and manual.

I'm very slow hacking Type A and B units, now with fixed WB, not much else yet. Having units at different stages helps for progress comparisons.

Shot this film yesterday:

Fun to read and see what you've been up to over these recent months. I love the clarity in your fresh footage, especially with the new lens. Looking forward to whatever advancements you and the community can make with regard to user-adjustable settings. I wonder if the frame rate (16, 18, 24) is something that you would consider for that too. Plenty of old 8mm footage out there in need of scanning with this machine.

While it's a trivial task to adjust the playback frame rate after capture, it would be nice to have the original mp4 files reflect the correct frame rate from the beginning (like the full range flag).

Anyways, thanks for the update!

 

[0dan0]

I'm sure somewhere there is an fopen(), fread() and fwrite(), to open a config file with user controllable parameters, rather than flashing builds custom parameters. But this I have not yet found. Once I have that, then I could build a small UI (if I find the button events) to set fps, white balance, etc. Taking priority is catching Type A and B up, and maybe more importantly (but harder), working out a fix for the top and bottom frame jitter issues.

 

[Gewendell]

I'm sure somewhere there is an fopen(), fread() and fwrite(), to open a config file with user controllable parameters, rather than flashing builds custom parameters. But this I have not yet found. Once I have that, then I could build a small UI (if I find the button events) to set fps, white balance, etc. Taking priority is catching Type A and B up, and maybe more importantly (but harder), working out a fix for the top and bottom frame jitter issues.

Long time lurker, first time poster. 0dan0 & Mac84, do either of you have Venmo or other way for us to throw you some cash for your troubles? I'm on a Model "A" and cannot WAIT to utilize your updates. If a little USD$ thrown your way by the community (assuming this is allowed in this space to even suggest), I'd HAPPILY contribute for your efforts in the community's behalf. Seriously, the least we can do. Would also pay for a step-by-step guide/video for the lens swap. (and I'm sure I'm not the only one). Thank you all for your posts and for pushing the envelope for this humble scanner!!

 

[CineMark]

Hi, I'd like to report that I just bought a Reels from Amazon. The serial number is: k3124148bk01699 which was reported by the website as serial not found, and needing firmware B. However, when I loaded that, I got the electric fireplace screen show on my Reels. I then proceeded to load the C firmware on the unit, and it booted on as original. I'm now running a film through and will report back with any issues.

 

[0dan0]

Help is a video of my progress so far, and request for technical help at the end.

@Gewendell money will not help, I just the find enough time, and I'm looking for new leads to fix the remaining issues.

If some with a Type C Reels unit, could test all the versions I've posted, to see when the chroma artifact was introduced (or if it was there all the time.) If you have a stock lens, zoom all the way out, as this will emulate Ideas so far. 1) there is a chance is the increased bit-rate is on for Luma, and I'm starving chroma compression 2) As I used larger image buffering, maybe I'm stomping on some memory that is used for UV chroma compression (I would think it was be worse if that was the case.)