The code can go to 400 in preview, but this might be bug. Use the histogram to judge the exposure.
Hacking the Kodak Reels 8mm Film Digitizer (New Thread)
- Thread starter Mac84
- Start date
fantastic!!
Ok, so to get 25-27 Mbps, I just set it to the lowest possible number - 15 for example - and let the also do the rest, correct?
Ok, so to get 25-27 Mbps, I just set it to the lowest possible number - 15 for example - and let the also do the rest, correct?
But I noticing, V7.6 doesn't want to go below Qp 20. Looking into that. It is Type A bug, only.
I got Type A running at Qp 16 again, outputting 45Mbs. Updating builds now.
Switching back to ISO 50 seems to be improving encoding by cutting down noise, which usually gets in the way of encoders. In the next update, hitting 45 Mbits sustained might not happen, but landing around 28–30 Mbits would still be fine. After that, Topaz can help enhance the image and fill in any gaps with some grain.
v7.6.1
Bug fixes only.
- Qp rate control below 20 was fixed on Type A & C (B was okay)
- Now supports up to 400 ISO during encoding (not sure if this is a good thing, but try it.)
Bug fixes only.
- Qp rate control below 20 was fixed on Type A & C (B was okay)
- Now supports up to 400 ISO during encoding (not sure if this is a good thing, but try it.)
Thanks @0dan0, I can confirm that at on my Type C scanner, the ISO value does 400 ISO during film scanning and also reported up to 800 ISO when I put my finger between the light and the lens (blacking out the sensor). Also, the encoder is showing as running at Qp 16 (when set to 15). Thanks for the ongoing updates/improvements!
Now for something completely different.
Here is the github repo for all my C code extensions, and some the scripts I use.
github.com
You can see how the histogram and the fonts are rendered, and the crude exposure and manual white balance logic. This is only the tip of the iceberg for the firmware changes, but it where most of the recent extensions are happening. Zero documentation, but I figured a git repo will help us track any future changes.
Here is the github repo for all my C code extensions, and some the scripts I use.
GitHub - 0dan0/4reels: hacks for the K. Reels scanner
hacks for the K. Reels scanner. Contribute to 0dan0/4reels development by creating an account on GitHub.
github.com
You can see how the histogram and the fonts are rendered, and the crude exposure and manual white balance logic. This is only the tip of the iceberg for the firmware changes, but it where most of the recent extensions are happening. Zero documentation, but I figured a git repo will help us track any future changes.
The Qp (Quantization Parameter) level that you set (15) and see being achieved (16) is quite good (essentially the highest quality compression you can achieve on this hardware with this current custom firmware, and WAY better than what you could achieve with the stock firmware).
Qp can be thought of as a setting that dictates how much compression is being applied, where a higher number equals more compression. The bitrate of your video is probably somewhere between 30 and 40 Mbps, but you would need to open the file in some software to determine that (or do the math yourself based on filesize and duration).
Last edited: