Search results

Thank you, these are helpful. I wanted to see if the frame cadence was different when there is jitter. These two show the same cadence as good captures. So detecting cadence alone will not be sufficient. I have added a crude frame buffer difference test the seems to work, now I have to see if...

Hmmm.. not quite how it works. While there is some disagreement on the resolution resolved for CFA Bayer sensor, it is not half as you theorized, and we aren't get 4:4:4 color from H264 (there would be very little benefit). The sensor has a photo readout mode (not used) and a video read-out...

Yes, that is a type D. The exposure flicking is one of the many problems the firmware hacks help address (and hopefully/eventually for type D too.)

v7.7 is getting close to all the features I would want for MP4 encoding film scanner. The main remaining fix is to either prevent or at least detect the jitter, so that scanning hours aren't wasted. For this I will need your help. This v7.7.1 build only add a hidden debug feature, if not...

Version 7.7 for Type A, B and C (and stock FW recovery for D users.) So nothing for Type D yet, at least now unit can be recovered if the wrong firmware is installed. New to v7.7 - stats and controllable field are written off the video image (bottom right corner.) - there is now an ISO Max...

@WowIndescribable H2324148BKxxxxx is a type C, so you have no need to wait. While the firmware hacks are is still changing, but the quality improvements are slowing. If you can swap the lens, with any recent firmware, you will be good.

At least now Type D users can now be unbricked. The changes in the new firmware are more extensive that any other model. Function addresses have moved, so this might take a while.

While we are waiting for an original image for the new type D unit, progress continues. Currently all my text and histogram rendering using the preview video buffers, the YUV data that contains the lower resolution of the film-scan for display. This is a very useful buffer as I used it for my...

@SkipBurg hold off on updates for an D2825 units, that one I'm uncertain about.

If you look at my list you can see that that is clearly a type-C unit, as others had the same serial number style. The worrying serial is H2825xxx. Scan first for sure, but you will likely want scan again to get the quality benefits.

This suggests the unit is crashing, it is not the buttons aren't working. Return it. The manufacture can easily refurb the units, and would have this issue if A) they didn't do a sloppy design, and B) they would provide users installable firmware.

@Mac84 Yep, that is a type C. @JKCalhoun and @Grandson (if you still have your scanner), I now believe there has been a new hardware release, which we don't have the baseline firmware. This is likely fixable. The easiest approach, if @Mac84 or myself, or someone willing to add a serial port...

Here is v7.6.2, this has two bug fixes. First that the reframing wouldn't work immediately after the update, and the second that reframing was bizarre after capturing, if you used the arrow navigation controls. These both had the same root cause. All the code changes are on...

Based on the posts on this forum, and those that shared serial numbers, it seems there is a fourth hardware configuration and therefore a Type D firmware needed. We have seen two units on this forum with H2825xx serials, that will not support button presses after update, but the LCD driver...

Do the buttons work with type A or C? If this is a new configuration, it would nice to see what it shares with other configurations.

This might be a new limitation. It seems it was broken in V7.4 (v7.3 is okay). So two steps forward, one step back. In three weeks no one else has reported it, as we general frame, then capture, not capture then frame. It is a bug, and worth looking into.

Video is blank here. I only hear the audio. I was able to download to see it.

33K is a tad low for Qp 16. But for stock lens at 16 or 18fps it could be okay.

I don't understand this one. Can you video what is happening?

I expect your new lens might be pointing to far to one side. When you are reframing to centering, might be using some out-of-range values. During preview share these numbers: