Modding the Kodak Reels 8mm Film Digitizer (Firmware Hack)
- Thread starter Mac84
- Start date
Still getting some anomalies, FPS, data rates and also one capture stalled, the film was moving through, but the SD card just repeated the same frame for many seconds
Movie specs - 0dan0 V7.1 on Type C ...
Also I was seeing 464x224x256 in the WB values on this. Going above 256 for the first RGB value?
Went back to 0dan0 V7.0 on Type C and got this ....
Movie specs - 0dan0 V7.1 on Type C ...
Also I was seeing 464x224x256 in the WB values on this. Going above 256 for the first RGB value?
Went back to 0dan0 V7.0 on Type C and got this ....
Seems you did get the update to work. You need to redownload v7.1
within the zip you will have 71a.
But otherwise would be hard to tell, also the file date is 10/22 not 10/21.
No (although harmless), but it is showing that the ZIP has changed.
ok, new capture on V7.1a on Type C – also I am getting consistent data failure around the 17 sec. mark. Unit continues moving film, capture continues, movie hangs at ~17 sec and repeats same frame for the rest of the movie, in my case 51 sec mark. I am using SanDisk 280mbs SDXC II U3.
Trying again for v7.1.
I did covered that the base timescale for the MP4 was hardcoded to 60000. To get the frame rate changes correct, a lot of code used 60000 directly at the assembly level. When fixing the 20fps to 18fps, all I changed was the numerator in the frame rate setting. But for 24fps, the numbers exceeded 16-bit, so I need to change the time scale.
This are all the locations I have found that I believe are timescale.
While the is unlikely to be useful information for others. It is here to keep a record. If something else breaks, one of these changes might have been wrong. I was searching for uses of 60000 in MIPS assemble code. Hoping these are all the timescales. I'm now using 20000 for the timescale (solving the 3x error you may have seen.)
Both Mac and Windows users need this fix. All working well in my testing.
I did covered that the base timescale for the MP4 was hardcoded to 60000. To get the frame rate changes correct, a lot of code used 60000 directly at the assembly level. When fixing the 20fps to 18fps, all I changed was the numerator in the frame rate setting. But for 24fps, the numbers exceeded 16-bit, so I need to change the time scale.
This are all the locations I have found that I believe are timescale.
While the is unlikely to be useful information for others. It is here to keep a record. If something else breaks, one of these changes might have been wrong. I was searching for uses of 60000 in MIPS assemble code. Hoping these are all the timescales. I'm now using 20000 for the timescale (solving the 3x error you may have seen.)
Both Mac and Windows users need this fix. All working well in my testing.
V7.1.1 working great on my Type C, no longer hangs (stalls) at 0:17, Quicktime .MP4 shows 18fps and ~22Mbit/s, picture looks very good.
Can't wait for my lens to arrive! Have boxes and boxes of old film that still needs to see the light.
Thank you @0dan0 and everyone else here making all this possible!
QuickTime info:
Sample from V7.1.1 on Type C
Stock Lens + Settings: Exp: Default WB: 0.0 Sharp: -1.0 Tint: 0.0 Frame: adjusted to a sweet spot
Can't wait for my lens to arrive! Have boxes and boxes of old film that still needs to see the light.
Thank you @0dan0 and everyone else here making all this possible!
QuickTime info:
Sample from V7.1.1 on Type C
Stock Lens + Settings: Exp: Default WB: 0.0 Sharp: -1.0 Tint: 0.0 Frame: adjusted to a sweet spot
@0dan0 I tested the 7.1.1 firmware on my Model C scanner and a 5" reel scanned really well. Really great results with my 8mm scan (50' roll, no issues so far).
I'm developing an "Operating Guide" that incorporates your latest changes that I'll post here a little later; will edit as needed to help new-comers.
I did note that a 64 GB card I had been using with Mac84's firmware did not work well with 7.1.1, but a 32 GB card worked well with no issues.
Really liking the ability to set the Frame rate, Exposure Bias, White Balance, and tint. Particularly the recent WB trim adjustment for the LED backlight has been a solid improvement for me.
To confirm, is the Menu control labeled as "Tint" now functioning as a "Saturation" control where -2 is monochrome, 0 is normal color, and +2 equals very increased color saturation?
Thank you, thank you, THANK YOU, for all of these improvements. They are sooooooo good!
I'm developing an "Operating Guide" that incorporates your latest changes that I'll post here a little later; will edit as needed to help new-comers.
I did note that a 64 GB card I had been using with Mac84's firmware did not work well with 7.1.1, but a 32 GB card worked well with no issues.
Really liking the ability to set the Frame rate, Exposure Bias, White Balance, and tint. Particularly the recent WB trim adjustment for the LED backlight has been a solid improvement for me.
To confirm, is the Menu control labeled as "Tint" now functioning as a "Saturation" control where -2 is monochrome, 0 is normal color, and +2 equals very increased color saturation?
Thank you, thank you, THANK YOU, for all of these improvements. They are sooooooo good!
Last edited:
Thank you.
Tint always acted as saturation control, but is setting went from 25% to 200% (guessing). I just made -2.0 set to 0% saturation, to make working with B&W film easier.
Yes 64GB card support is broken. Someone will have to go through all the releases to find out when that happened.
FWIW, I am able to save an MP4 file of ~4,000 frames (50-ft roll) created by fw v7.1.1 on my Type B device using the 128 GB SDXC memory card formatted as FAT32 in the attached photo. After the last frame has been scanned, I press the 'OK' button, then select 'Close', and finally turn off the unit before I eject the memory card.
Surely I'm not the only person who is able to save an MP4 on a memory card larger than 32 GB?
Attachments
Sticking to FAT32 with these units doesn't bother me one bit. That said, I believe that other folks have reported that the firmware (stock and presumably all mods created to-date) formats memory cards as exFAT when someone chooses to use that feature on the unit. That is why I suggested trying to disable that feature in the firmware and/or the UI, to avoid user questions / complaints.