Search results

@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:

What was your average bit-rate?

It is not falsing triggering the auto stop, unless you have about 40 frames of completely clear. This is just the limitations of the hardware running at higher bitrate.

It is not a hard number, as it also depends on the grain and detail in your footage, and the rate of change in the footage. The original firmware would have averaged a Qp around 35. This is not a firmware bug, we simply running the compression beyond the design spec. For the highest quality...

This is the risk you take when using a Qp below 22. Unit will randomly crash with the highest bitrates. This is way I added the Qp control, for max quality, you might have to rescan more, for a longer reels that you want to work reliability use a higher Qp.

Share examples? I do this all the time, not seeing it.

Now for something completely different. Here is the github repo for all my C code extensions, and some the scripts I use. https://github.com/0dan0/4reels 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...

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

I got Type A running at Qp 16 again, outputting 45Mbs. Updating builds now.