Messages

As far as I remember EOS-M was able to use the commented fps values too:
https://bitbucket.org/nikfreak/magic-lantern/src/100D_merge_fw101/src/fps-engio.c#lines-253

Anyone time to try it with sd overclock?

lol policeman 

this will drive some nice traffic to the website once stable.

You guys better try this on spare cards cause some will burn 

good job, please continue !!!! 

errrrm a1ex, couldn't this (=you  ) be brute forced within qemu?? No? We could need some volunteers to try this on their cams  otherwise. Should be worth it.

[SDR104 @ 160MHz]

Ran a brute force (random) search for the above registers, and...

SDR104 @ 160MHz

......
Brute-forcing: press shutter halfway during the initial tests, until it starts running some more. Press shutter halfway again to stop (infinite loop).
No guarantees of success, no guarantees of safety, no guarantees of data integrity. You have been warned.

Please post logs and benchmarks.

Anyone ever been able to find or brute force 208 Mhz for SDR104 ??

It's not arrogance. It's Walter.

I assure you, I did read it, along with every other reply in this thread. I don't even know where to begin with regard to all of the questions that I have. There is too much information for me digest. If that makes me dumb, I'm cool with that...

Please read 1st post UNTIL you understand what and how to do. Do it twice, thrice... That's not dumb - that's how it works..

[it's time to move to git]

Please don't make THE decision to selfhost a repo. I personally think it's time to move to git as it seems to be more widely adopted but ofc having backups of all repos is a good idea. I am unsure if you really need to have a backup from all forks. Mine for e.g. might be skipped if 70D and 100D got merged.

Idea: I suggest merging PRs (read: not all) as much as possible either before or short after leaving bitbucket. Everyone wanting the "old" aka "nightly stable" builds might download it from ml website. This might be a chance to "force" community as well as newbies to participate on the new platform and speed things up.

A picture is worth a thousand words.
Congrats!

nice progress 

Please, accept OlRivrrat's opinion. Everyone's free to use raw recording and think about it what he/she wants. Me for e.g: i don't even use H264. So I also don't care about raw video. But hey, that's me - a photo freak.

Please return to topic.

I'm sold for both the module "fake_hss.mo" and the frsp solution 

a1ex, thanks for the detailed answer. 

Greg, as far as I understood, the SPT software could adjust the delay of the inbuilt popup flash. Correct me if wrong. Didn't see it from that point of view but this brought me to the idea how some radio trigge rmanufactures do it, too. They provide an adjustable delay option on their triggers and you can adjust it to your needs as described in X Contact Timing of SPT until vignetting is acceptable. probaly not worth the hassle but one would need to find a way to adjust the delay (property?) via ML.

You can try "leaf shutter" by changing the aperture value when capturing FRSP.

this one I didn't understand. Was reading chdk's wiki last days and then shocked seeing they could do some kind of 1/60000 flash sync speed.

- full-res LiveView (only 5D3 for now, but there is a PoC for 700D with adtg_gui); this can reach shutter speeds as fast as 1/15000, with a rolling shutter of 128ms on 5D3
- this proof of concept (use aperture to simulate a mechanical shutter, much quieter, compatible with all models, just need a couple of hours to make sure it actually works as advertised, then it will be live)

To select 1/8000 quickly, try the exposure presets feature. A Lua script can be used to sketch the half-shutter workaround, too. Disabling exposure simulation might be also helpful (yet another workaround).

To sum this up:

where's the needed code (parts) to get FRSP running with such high shutter speeds, e.g. 1/1000? I remember also some comments about achieving a neutral density effect. Some guidance, please, as well as a solution for triggering the hot shoe flash in frsp. Wanna achieve soemthing like this for cheap

Was this just an April's fool or does this one exist?

check your PM

a1ex do you know an easy way (some lines of code) to trigger the flash hot shoe within frsp?

hey welcome, this is one of the most interesting posts lately.
Your best bet is getting 80D running in QEMU and learn everthing the hard way. Guess you might need a digic 5 dump from any camera to check how it feels as well as the 80D dump to learn from. next, also a tutor. Dunno if a1ex can help or even has time or the mood to assist. Patience is a virtue. Don't disappear

...
(I figured out how to use flash with FRSP - the trick is to find a delay, specific to your camera, between triggering FRSP and triggering the flash), typically at 1:8 power. The FRSP exposure is so long (0.4s for my 6D)...

Please explain quoted part in detail!
Are you using radio triggers whch you can adjust / program a delay or do you do this with ML specific code. I am very interested in this. And I thought the shutter limit was already solved by a1ex for FRPS - at least on 5D3 !?!?!? So you could probably use more flash power. Pleas tell me I can use some kind of "tail sync hack" with frsp. I need this adjustable delay for flash trigger function

genius!

Welcome back, Walter

ok here, too but switched the job and got lots of work to do. Wife and kids stay @home.

Canon will repair it if first two digits in your camera's serial number are within the range of 00 to 22. Check the product advisory

+1 for Walter:
Write clearly. Say what you mean, and make sure it can't be misinterpreted. One suggestion from me for underclocking the main CPU would now be: DESOLDER the CPU of the 70D and solder the one from 40D into it. Good luck!