Search results

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...

Crazy progress continues V7.4 @sheider " feature requests: ... a user-controllable exposure lock toggle." As I have a short film project this weekend, where I will be developing and scanning about 10 rolls of Ektachrome, and I too thought an exposure lock could be very helpful. The current...

The Picture controls in menus are the same. Green tint is also still using left and right arrows, can be done at any time (like before.) However the up/down and +/- are no longer overloaded with two meanings. Setting fps, ev, and qp min, can only be done during capture.

Here is v7.3, after only a day or so. This adds Qp level control, allow you to set the minimum Qp the device will try for. Previously this was fixed at 20, but this may have caused some jitter drift (unconfirmed) on some units. During capture there is a new settings controls which should be...

Type A, B & C are for slight hardware differences, not for bitrate benefits (same for all.)

This seems to be the same hardware. Type C or B will likely work.

Restore original Type B firmware, and return that unit as it seems just broken. Likely not a firmware issue as no one else has reported this, and others do have EU models. However, if it is another variation of the hardware, someone would need to have extracted the firmware before the update...

Does it say "V2.0" on the back, or only in the About screen? If the back looks like this: it will be pretty safe to try either Type C (first) or Type B, the two most common "REELS" units. If the display is weird using C, try Type B. However, if you rear ID plate looks different, maybe...

Anyone else seeing the jitter appear after the capture started correctly? I have never seen that, so I would like to see examples to understand if there is drift on some units and not others.