Personal View site logo
Make sure to join PV on Telegram or Facebook! Perfect to keep up with community on your smartphone.
Please, support PV!
It allows to keep PV going, with more focus towards AI, but keeping be one of the few truly independent places.
Official Nikon Hacks, D7000, D7100, D3100, D3200, D5100, V1, V2, J1, D4, D800 and Nikon Tool
  • 336 Replies sorted by
  • @swfree

    I hate to burst your bubble, but: www.youtube.com/watch?v=iwDYKENnUis

    In the video, I'm using the aperture ring on an AF35/2 lens. When custom setting F6/aperture ring is set to "off", the aperture can be adjusted with the aperture ring on a lens that has cpu. This works even during live view and video. On a lens with an aperture ring and no cpu, this is the default regardless of the setting.

    The actuator (the 4.1 arm in Nikon tech parlance) may be software locked, but it is not hardware locked. This is an important distinction to make, since we are talking about software hacks here. So yes, it is very likely that aperture control during live view or video can be enabled with a hack.

    In closing, thanks for all the hard work of the people who are attempting this hack, and please disregard the nay-sayers like swfree, who think it can't be done.

    -Micah

  • There are tables the refer to the jpg's, not all are table driven. For the D5100:

    JpgTableTypeA(0x054258, 0x054260);
    JpgTableTypeA(0x055de4, 0x055EEC);
    JpgTableTypeA(0x2A5898, 0x2A59F8);
    JpgTableTypeA(0x2a66D8, 0x2A6770);
    JpgTableTypeA(0x7c5a34, 0x7c6254);
    JpgTableTypeB(0x38e7b0, 0x38e8d0);
    JpgTableTypeC(0x38e8d0, 0x38E998);
    JpgTableTypeD(0x392F90, 0x393320);
    

    were:

    JpgTableTypeA is 8 byte block, {pointer, length}
    JpgTableTypeB is 12 byte block, {dummy, pointer, length}
    JpgTableTypeC is 20 byte block, {dummy, pointer, length, dummy, dummy}
    JpgTableTypeD is 16 byte block, {pointer, length, dummy, dummy}
    

    And then there are some left over jpegs:

    MakeJpeg(0x8A6B4B, 0x22FE);
    MakeJpeg(0x8A8E49, 0x2661);
    MakeJpeg(0x8AB4AA, 0x2C66);
    MakeJpeg(0x8B0FD7, 0xE6C);
    MakeJpeg(0x8B1E43, 0x1680);
    MakeJpeg(0x8B34C3, 0x181C);
    MakeJpeg(0x8B4CDF, 0xDB2);  
    MakeJpeg(0x8B5A91, 4280);
    MakeJpeg(0x8BEAAD, 0xECB);
    MakeJpeg(0x8BF978, 0x155F);
    MakeJpeg(0x8C0ED7, 0xFEC);
    MakeJpeg(0x8C1EC3, 0x1103);
    MakeJpeg(0x8C2FC6, 0x10dE);
    MakeJpeg(0x8C53FF, 5049);
    MakeJpeg(0x8C8235, 0xCF4);
    MakeJpeg(0x8E7930, 0xE44);
    MakeJpeg(0x8E8774, 0x162E);
    MakeJpeg(0x8E9DA2, 5801);
    MakeJpeg(0x8EB44B, 3224);
    MakeJpeg(0x8EC0E3, 0x122E);
    MakeJpeg(0x8ED311, 4820);
    MakeJpeg(0x8EE5E5, 0x12E7);
    MakeJpeg(0x8EF8CC, 4451);
    MakeJpeg(0x8F0A2F, 6335);
    MakeJpeg(0x8F22EE, 4733);
    MakeJpeg(0x8F356B, 0xE7D);
    MakeJpeg(0x8F43E8, 6595 );
    MakeJpeg(0x8F5DAB, 0x1E7C);
    MakeJpeg(0x8F7C27, 0xFBC);
    MakeJpeg(0x8F8BE3, 5284 );
    MakeJpeg(0x8FFDD9, 0xF07);
    MakeJpeg(0x900CE0, 0x16E0);
    MakeJpeg(0x9023C0, 0x100C);
    MakeJpeg(0x9033CC, 5772 );
    MakeJpeg(0x904A58, 0x117F);
    MakeJpeg(0x905BD7, 0xB8B);
    MakeJpeg(0x906762, 0xC03);
    MakeJpeg(0x907365, 0x1994);
    

    The addresses are all memory space, not file space references

  • @Vitaliy_Kiselev

    I'm just started digging into nikon's firmware, so it's 'a little bit of this, a little bit of that' - though I do have previous experience with embedded RE, so I know some tricks, but right now I'm just working out some very basic "vectors of development", so to say.

  • @scev0la

    How about sharing your info here?

    you're storing into JPEG 1 extra byte at the very end of the file that does not belong there.

    And? Right now tool is suitable for viewing only, so this small bug does not cause any problems.

  • @Vitaliy_Kiselev, Directory inside do exist (in fact, there's a lot of them), and btw you're storing into JPEG 1 extra byte at the very end of the file that does not belong there.

  • @scev0la

    It uses special algorithm for extracting JPEG files. No directory inside exist.

  • Vitaly, I have a question regarding your ntool.exe: How exactly do you find all those JPEG files? Simply by searching for JPEG signature, like "FF D8 FF E0 00 10 4A 46 49 46 00" ? Or you happened to find some kind of a "master directory" inside firmware? I've found some, but it does not contains all the JPEGs that are inside..

  • Dear Nikonian friends. I have tried in vain to find the D200_IMAGE_ADJ_01_25_06 (or newer) software and needs it really bad to refrech my old D200 from tuck pixels. Is there anyone here that actually got hold of the file and care to share it with me? I would be very grateful and happy if someone could help me with this! Please respond to marc.de.legion(at)gmail.com Best regards from a fellow Nikonian in Norway. /// Marc

  • @micah

    you are wrong again.

    the D800 is mechanically a complete different camera. they built it with a dedicated aperture drive motor.

    on the D7000, the aperture wheel in live view mode does NOT control the aperture in real time, it is just changing the aperture value on the screen which has to be enabled by turning the live view off so the mirror comes down, and turning live view back on, so the mirror mechanism will CHANGE and hold the aperture in position you have set in live view. as soon the mirror is up, the aperture can not be changed anymore.

    only the value on the live view screen is changing.

    not the actual aperture.

    you have to disable and enable the live view to use the set aperture

    also , aperture preview does only work when live view is not enabled. means the mirror has to be down for it to work. the aperture is set by the mirror mechanism as first step before the mirror even moves. the aperture preview stops right there, before it even actuates the mirror.
    the d7000 has 3 motors, 2 motors in the shutter mechanism, one for the mirror mechanism and aperture, one for the shutter curtain only. and a slow, quite noisy AF motor that is used to drive the focus on on older lenses without AF motor.

    i took a broken d7000 apart, and be assured, there is mechanically no way that the aperture could be changed dynamically in live view. you would need a complete different mechanism or in this case the new D800 which was made with video in mind, and being able to set aperture in live view

  • @Georgester - nothing yet for the D5100, the tool is at this point only for experimentation.

  • Sorry for my question, but I have Nikon d5100 and what can this tool add into functions of my camera,заранее спасибо.

  • @swfree, about the aperture arm: not true that they are hard interconnected mechanically. see: aperture preview.

    New D800 has "stepless" smooth aperture adjustment. It doesn't appear to be truly stepless, but it does change smoothly. Even the ability to change not smoothly would be an improvement.

    Oh, and as further proof that the mechanisms aren't connected, you can adjust aperture with lenses with aperture rings that lack cpus on the D7000 during video. This means that the aperture arm has the ability to move around, even when the mirror is up. (it has to move to allow the aperture pin on the lens to move)

  • How long will it take for a hack?

    We are hunting for small clues, in our spare time, for the fun of it. As far as I can tell Vitaliy has his hands full on the GHx work.

    Why is it not being doing here?

    This site seems very focused around the good work being done on the GHx hacks. We didn't want to distract from that, or have the established community questioning the progress, when we are much further behind in the understanding curve, of how our firmware works.

    I really like Stuge's post above, we are not lacking it idea's that we can't already do. Once we have cracked open the Rubik cube, and start getting some win's then we can talk about what other people would like. But honestly, until that point in time, I couldn't give a hoot what other would like done. Help sure, and by help I don't mean ask how you can help. Just out right help or don't help.

    So yes, 2-3 years sounds about what to expect. Aka, buy the camera you want to do what you want now, and if somebody works out how to give you more for free at some time in the future, then that's awesome, but base your actions on what is currently available, as there is no promise that anything will be done.

  • 2 maybe 3 more years. i say check back 2015, or try to learn writing your own firmware. nikon firmware has clearly no priority right now, and i guess it could get quite expensive. when you write custom firmware, you gonna brick several cameras in the progress from trying to get just the basics to work.

    maybe you could donate a camera or two

  • my comment is not abount naggin but to have the idea of timeframe. So I wondered if anyone had any clue as to how long it may take for thing to happen.Otherwise I can buy another camera with 60fps.

  • @osmar92 When you create it.

    To everyone who is posting comments asking for things they want:

    Please consider that you are only creating noise on the internet, and you make it more difficult for people who are actually competent to collaborate to do so. If you can not be constructive at this time, then please just wait until there is some announcement.

    Don't worry, if you are interested in something and you keep an eye on the relevant sites then you will not miss it if and when it happens. Please spend your time meanwhile doing something productive instead of nagging for your most desired feature.

    Many thanks!

    Personally, I will look at how to up the video length limit on my D3100, because it's a silly arbitrary limitation, and because it makes it impossible to use the camera e.g. for recording a conference presentation, lecture or any stage event, which it would otherwise be able to do just fine in many conditions. Like anyone else who is halfway competent I don't have free time for this at all, so it can take a long time and it may never get done at all. See above. Get excited when something is finished, get working on your own until such time. If you can't help, then simply wait. It is really irrelevant how many millions of people are unhappy with the products they have bought. If they can organize they need to take it up with the producer, not with individuals doing technology research for fun.

    Many thanks to Simeon, Vitaliy and others who share their work.

  • Any idea when we will get a hold of 60fps in d5100 or any hack for that matter?

  • rename nef to raw, problem solved

  • Shame you're too busy.

    I'm looking for a longer Exposure Delay (currently 1-2s) and introduction of "proper" RAW. Rather than the bastardised Nikon NEF format. :)

  • @xztraz

    Personally, I am too busy now with Panasonic cameras.

  • Any updates?

  • Lpowell, this is true, nikon took its time, even though ive never really needed a feature like that because im using manual lenses with aperture ring on the d7000 like the quite awesome fully manual Rokinon/Samyang/Walimex Pro AE 35 mm 1:1,4 http://www.amazon.com/Rokinon-Angle-Nikon-Automatic-RK35MAF-N/dp/B004X1SFTA/ref=sr_1_1?ie=UTF8&qid=1326481509&sr=8-1 i say if you want live view aperture control , the chances that you are a dslr film maker are good, so you dont really need auto focus, but a nice, smooth and long manual focus for your follow focus setup. just get manual lenses

  • @el_guero In Aperture Priority Live View mode on the Nikon D7000 and D5100, you can turn the dial and the aperture setting on the LCD will change. However, the lens aperture will not actually be changed until you leave Live View mode or snap a photo. This is a long-known pitfall of Nikon's Live View mode and it's good to hear that it has finally been fixed with the D4.

  • @swfree I really don't think that's a physical limitation because while on aperture priority mode, on live view you can record video and also change the aperture value, if it was in did a physical limitation as you suggest that wouldn't be possible at all.

This topic is closed.
← All Discussions