Messages

Very interesting!

Those cards do not seem too expensive, about 20€ from Amazon delivered around here, plus another 10€ more for an adapter to Compact Flash. Did you try that card with a CF adapter, by the way?

Reading your post, I understand that Windows is only needed in case someone bricks the card, and any other procedure can be performed from a Linux box; is that correct?

Many thanks!

Perhaps not exactly what you need, but "aperture bracketing" seems quite similar: http://www.magiclantern.fm/forum/index.php?topic=3045

You might want to contact with member 0xAF in this forum: if I remember correctly, he already worked on JTAG with the 400D.

AFAIK, Canon cameras can only act as a USB slaves, not USB masters; does not seem possible to me (but I would be glad to be proven wrong).

I just googled "canon e-ttl protocol" and found several promising results.

Canon's image stabilization works on the lens. If I am not mistaken, all communications between camera and lens are just "switch IS on" / "switch IS off" messages. Thus, this feature seems impossible on Canon hardware.

AFAIK, "read" physically implies "reset", in current sensor technology.

All even lines must have the same ISO, and all odd lines must have the same ISO.

I guess there is new code in WiringPi, that uses integer division / module functions; so the .o file now contains references to __aeabi_* functions, and the linker has trouble resolving them.
Could you post here the whole Makefile that produces the error, please?

What do you mean? How can I properly configure my wrapper? I thought the wrapper doesn't do anything but point to a function in an object file.
And also I thought if the object file contains extra functions that I don't link then it doesn't affect my program.

If I am not mistaken, your .o file contains references to some external functions (__aeabi_idiv, __aeabi_divmod), and the message means your linker has trouble resolving those references. It seems to be able to find those functions at "/lib/arm-linux-gnueabihf/libgcc_s.so.1", however; but then it fails when adding them. Could you post more info here about that wrapper, please?

OT-OT:
i can recommend NodeMCU (http://en.wikipedia.org/wiki/NodeMCU)
the processor is the same chip as the wifi chip, so you have a small footprint.
see e.g. http://i.imgur.com/FY98xHX.jpg

programming language is LUA or C if you want to program the ESP directly.

why i like it?
the module is $3 on ebay

Just whoa!!! You have opened a whole new world to me; many thanks, but my wife is going to hate you now.

AFAIK:

Those symbols are the functions for the integer division and integer modulus. You cannot just remove them from the .o file, because some code in that file needs those functions; unless such code can be easily removed from wiringPi, you have to either statically link those functions into your .o file, or tell your wrapper how to search those symbols at libgcc. In my humble opinion, it looks like your wrapper is not properly configured.

We are requesting that options for zoom and focus compatibility be added. Sony has full compatibility for a slew of their cameras. Why should Canon compatibility be limited to burst photography? Thank you in advance for your time and effort to close the gap with other competitors. We would like to stay with Canon for our video needs. If the goal really is making "the ultimate open source camera", I would think this is an issue worth researching.

Just out of curiosity (I am not a ML developer): you are requesting to add "zoom and focus compatibility"; if I understood your product, what you need is a mechanism to control focus and zoom from a device external to the camera, is it that? Now, considering that Canon zoom lenses do not have a motor to drive the zoom, how do you expect any software to be able to control it? Or did I miss something?

Others who tried something similar (using a 400D and 400plus) faced the same problems: looks like the camera caches the content of the card, and thus external modifications remain unnoticed. As far as I know, they did not manage to find a way around this issue.

Recent Canon cameras have specific menu entries to control some functions from the Eye-Fi cards, so it seems there is a protocol to talk to the card from the camera; perhaps there is a way here...

Do you really want ML to switch MLU on and off automatically? Personally, I would find that really annoying.

AFAIK, Canon's IS is fully implemented inside the lens, and all that the camera can do is switch it on or off; but I would love to be proven wrong.

Hello!!!
I Love the ML for the 5d  mIII and I have a question !

Is it possible that someone can incorporate a shutter lag setting ? 
I want the shutter to lag but not the flash firing
In other words I want the flash to go off when pressing the button, before the shutter by some milli seconds.
Maybe make it set-able by miliseconds?
Would help a lot !

May I ask why?
Just curious to know when can that be useful, thanks.

AFAIK, reading the sensor also destroys its contents...

Just for your reference, we have a "long exposure calculator" for the 400D (https://code.google.com/p/400plus/wiki/UserGuide#Long_Exposure_Calculator):

The long exposure calculator is a tool created to help the photographer quickly determine the exposure time required by a particular scene. The idea behind the long exposure calculator is that you can quickly measure a scene using a high ISO and a large aperture, then lower the ISO value and reduce the aperture, but increase the exposure time accordingly.

For example, let's suppose we want to photograph a night scene; we decide to use the lowest possible sensitivity (ISO100), to avoid noise, and a relatively closed aperture (f/8), to get the depth of field we need. Using those parameters, the exposure time needed may easily overpass 30 seconds, and thus we cannot use the camera to make a reliable measurement.

But we can temporarily select a high sensitivity and large aperture (ISO1600 and f/2.8, for example), measure the scene, and determine we would need a 15-second exposure with those parameters. Then we enter the long exposure calculator, lower the ISO value to 100, and close the diaphragm to f/8; the Ev indicator will display a value if -9, meaning that with the current parameters the exposure is 9 stops below the measured value. We can now increase the exposition time until the Ev indicator goes back to 0, meaning the current parameters would result in the same exposure than we had at the beginning; in our case, that means raising the exposure time from 15 seconds to 32 minutes. Finally, just press "Apply" to configure the camera with these parameters, and launch the long exposure script.

Notice: The Ev field in this calculator cannot display values smaller than -15EV or larger than +15EV.

Tip: If you plan to use a ND filter, you can measure the scene without the ND; then enter the long exposure calculator and adjust the exposure to get an Ev result inverse to the value of the ND filter. For example, assuming we have an ND8 filter (8 steps of light reduction): if the camera measures 1/120s f/4.0 ISO1600 without the filter, then select 2' f/8.0 ISO100 to achieve a Ev of +8.

So you basically want a method to cheat, and transform a processed image to pose as if it had been created directly by the camera...?

I would guess that the shutter switch at the battery grip is connected in parallel with the shutter switch at the camera; then, that voltage drop you are measuring is probably just the input pin going down, and the only method to make it go down is to physically actuate on the shutter switch. I do not see any reason for Canon to implement an output pin there.

I do not think the camera can act as a host controller, as it lacks the hardware needed, but I may be mistaken; in that case, the problem is not to write a file manager, but to be able to control the hard drive from the camera.

Fully aware of dual ISO etc and a user.

Just thought some may enjoy reading this article.

I'm not 'requesting' anything!

Cheers

Well, I did enjoy reading the article (just skimmed through it ); thanks.

That paper deals with image registration (alignment) and bracketing strategies. The first part is not very interesting to me, as it concerns mostly to the post-processing phase. But the part about bracketing strategies could be relevant.

They have studied the best approach to capture a HDR sequence of images under a time constraint: how many exposures should be taken, and how long should they be, when there is a maximum time allowed to capture all the sequence. Under normal conditions, the traditional burst of 3 to 9 exposures, with 1EV separation between exposures, can be enough; but for low-light situations, where longer exposures are required, the total time needed to capture a scene can be a problem.

Instead of using a 1EV separation between exposures, they propose using a Fibonacci sequence; for example, instead of 1s, 2s, 4s, 8s (15s total), the propose using 1s, 2s, 3s, 6s (12s total).

hi guy,

i got an idea.
what about modifying the dual-iso module, to instate of getting two separate ISOs to get different crop locations on the sensor.

in fullHD the Pictures would have an eye-distance of about an inch (in reality it is 6,5cm, i know). that could appear as a non overdone little 3D Stereo effect.

i´am just thinking. what´s about you?

best regards.
Rudi

Take a photograph, open it in your favorite image editor, and split it in two; that makes your "different crop locations on the sensor". Now try to make a 3D image, out of those two images, and tell us the result (hint: you can't).

[de]

I guess that what the OP is asking for is not the "tilt-shift effect" (tilting the focus plane to match the scene, and create a greater depth of field) but the "tilt-shift deeffect" (tilting the focus plane against the scene, and create a shorter depth of field). IMHO, such "effects" belong to the post-processing phase, and are out-of-scope for ML.

I am going to make a movie soon(ish) and having a port for the 350D would save me quite a bit of money since I can get a 350D for free.

The 350D cannot do LiveView or record video; it is a limitation of the hardware.

How much for a working port?

More than the cost of a new camera, I guess...