Search results

D-type has only 5% of the features ported. The resolution change has no benefit without the in-pinning resolution fixes, not yet ported. Only has 18fps, and lock white balance, AFAIK. No increase bit-rate. Need a few more weeks.

Seem I posted a slight different build. This will match the Type C, I help me with the next steps. I could use the shell to confirm expo control addresses, that should work for you too.

Attached is an example of print added to the beginning of New Capture Res. This should be the first entry point. It will crash after the print outs. As the sensor pixel pitch has changed, it does make some sense scanning resolution has changed, my code it likely not expecting it. When use...

Anywhere you can add 34 80 04 3C 18 03 02 0C F0 B0 84 24 F0 B0 points to the string at 33B0F0. Value in a1 goes to the first %d, a2 the second %d, and so on. Add you own string messages as needed. The first area to investigate, are the calls to setting resolution.

To be this wide, this is either downgraded the lens (even wider) or they have following this development and a planing a future lens swap.

That is weirdly wide for a stock lens and unmodified firmware.

I think so. hist.c should not be called before the new New Preview Res code

AR0330 2.2um pixels OS04D 2.0um pixels I'm assuming the same lens. Please do a full overscan, need to see the sprockets. The smaller pixels will slight help the original lens, increasing your scan resolution 10%. New 12mm lens will still be a better setup.

From at 2019 to 2025 board date. I think I will have to get a type D unit, both to work the port, and test the quality. What you can do, is add prints to the code, to find where it is stopping. Type D: fileid:0 <- last message??? Type C: The last five lines is from my code. Code at...

That's annoying, crash or looping error messages would have been easier for next steps. hist.c code will not run without the support from the other functions starting at 0x338f80. Some good news, and some bad news. From Type D > ERR:ChgMode_OS04D10() ChgMode_OS04D10 to 1... From Type C >...

@videodoctor For your initial testing only This build will very likely crash, and/or dump a lot of error messages. I've ported anything I could, but with no way to verify, now up to you. I need to see the complete shell output from your unit. Start from "Hello, World!" There might a lot of...

The offset looks about right, but I'm away from my computer, so I can't compare, but clearly the auto exposure function has changed significantly from the earlier models. I have been patching a lot of things for type D. The AE hook was one of the last things to do. I will have something to...

There are a lot of error messages I had suppressed with a NOP over the print console call. I don't remember if this is one of them. For any string message to find where is it called from: search on "UIFlowWndMovie_OnTimer" found at offset 0x32ef2c This address will be in stored in a0 or...

The code dev stuff could scare some away, but I always ported my findings in the main thread, just in case someone can learn from it. Opps! I made a typo Try this: mem w 80ddc670 30 You do not need the motor stop patch code yet, as that is hook to the encode crash, which only happens once you...

For recent US purchasers from Amazon, what serial numbers are you getting? H2825, D2825 or something else?

Yes, you can make Linux versions, I could potential use that too. Here is the source, I should forked the original and offered patches.

Classic 8mm is 16fps. Most Super8 is 18fps. Best not to mix as video files do support changing frame rates. If you have to mix, then use a 24.0Hz timeline, both 16 and 18fps will look okay within 24fps file. Very minimal contrast controls. If it going to youtube I export at 2160p (4K)...

You will need both hist.c and manwb.c built. But I expect there are a lot other things to fix first. You should be using all the same hooks as the earlier models, otherwise it will be more difficult to maintain. Use the differences before C original and C now, and make the needed changes to...

I updated my type-D firmware with the above code changes. This has not merge in your other patches. So you should just grab bytes from 338f28 - 340008. Repo is up to date. Note: the code from 338f28 - 33b200 still will need some Type D support. Like this motor shutdown code: If has...

Reel type must be at 0x80340000 Looking at D.BIN (very helpful) the Type D NVM is at 0x80E0ADA4, not what you had suggested. This is matches the data I expected to find for brightness, sharpness and tint, all set to defaults at zero. In memory look for 04 00 00 00 04 00 00 00 04 00 00 00...