Messages

Guys, I'm sorry for being obviously dumb or something like that, but I don't understand why I can't take silent pics with exposure time longer than 16s with the nightly build from builds.magiclantern.fm (700D.114) when it seems to be possible according to this thread.

The link from @josevpn doesn't work anymore, https://bitbucket.org/Gr3g01/magic-lantern-frsp-long-expo/ is gone, and the PR is declined - because of "monkey patching"??

However, I found it here, updated it with the addresses from @hillibilli

I have a 700D.114 and there the address of capture_err_time_addr is different to the value from @josepvm:

capture_err_time_addr = 0xff1e1dd8

The address of
bulb_end_addr is the same as @josepvm posted = 0x24960

Aaaand now my first 5 minute test-exposure worked very well
This is my compiled build: https://arxius.io/f/110e49fb

My question is: if this is possible, and working, why is it not merged? To me it is more important to have a feature that works rather than it being a "clean" solution.

Also, I think that I read somewhere (this forum and it's thread's are faar to huge IMO, to figure something out the first thing I have to do is sit down for two hours and read the forum), that somebody has found a workaround for the faster-than-~300ms-problem. If so, can somebody point me in the right direction?

And maybe we can do a list of features being implemented, but not currently in the nightly builds, and features declined? Like, things for testing, funny things nobody wants, etc.
Well, maybe there already is. Sorry for being dumb and not reading it all (the overview of all threads, and also all those 40 pages of this thread), I don't have the capacity for it IMO.

PS: Just noticed the code also still is here, it's @milank's version with support for the cams with bulb dial mode - I think?

And then there's also lua_touch which I got working on my 700D with some help. Although I think some changes afterwards broke it again.
See here: https://bitbucket.org/hudson/magic-lantern/issues/2520/lua_touch-outdated-hijack_touch_cbr_ptr
It just has finger down, move and up, as far as I remember.

Not sure if this is helpful, this forum is so confusing...

@a1ex: Where is the call done? I don't understand the magic with the menus yet. (Like how they work)
One could easily change hdmi_code_array to 5, like hd seems to have, but I think that didn't work.

Code Select Expand

static void ChangeHDMIOutputSizeToVGA()
{
    hdmi_code_array[0] = 2;
    prop_request_change(PROP_HDMI_CHANGE_CODE, hdmi_code_array, 32);
}


Re:Lua touch

Electronic level thingy sounds like a really nice idea.... Is it a 3 axis gyro or what data do we have?

Yeah, I think it's really broken, I tried to compile the newest lua_touch and all the scripts just say "error". Once the calculator worked though. But on the issue on the touch pointer address thing I posted my last working build - it should still work in case you get a 700D again

Hey guys,
under the display setting there's an option "Force HDMI VGA", is it possible to also implement a "Force HDMI HD" option?
Because my 700D doesn't recognize the resolution of my computer screen (1920x1080) and only outputs VGA.
On a TV screen it's 1080i though, so it must be possible.

Thanks.
/Daniel
PS: What prevents lua_touch from getting merged? I don't see any issues on my 700D, so I'd really like it getting merged