Topics

Just wondering/thinking out loud here: I prefer shooting through the eyepiece on my 5d, however, "in a (my) perfect world" it'd be possible to use the silent shutter feature without having to buy one of those fancy back screen eye piece things to keep the screen visible in broad daylight. I was just shooting at the beach, and I wound up shooting without silent picture because I couldn't see what I was doing, but I'd love it if I could mess around with the module.
So, bearing in mind that I am describing this merely from my superficial understanding of how the liveview function works (just by looking at the camera), my thought/question is this:
is it possible to to separate the functionality of the liveview feature into "that which enables silent picture" and "that which must move the mirror away from the eyepiece?"
And I suppose more immediately, should I be posting this instead in the "feature request" section? I mainly want to know if it's possible, but if it is, then I would certainly be pleased if someone did decide to take this upon themselves. Thanks.

[*THERE ARE THREE LINKS BELLOW THAT ARE INTEGRAL TO THE QUESTION I'M POSING*]

*THERE ARE THREE LINKS BELLOW THAT ARE INTEGRAL TO THE QUESTION I'M POSING*
I happened upon this thread http://www.magiclantern.fm/forum/index.php?topic=13982.msg134987#msg134987, and wondered: is anyone out there exploring something like this currently? Or does anyone have any insight to offer into this issue? Obviously, bearing with the motion "jello" notwithstanding, this is the bane of the low budget dslr project.
For myself, when I finally get time to devote to solidifying my setup and workflow (assuming that ever happens...), I'm the kind of person who's not looking for anything but an all in one solution, as far as is possible. I'm using a 5d3, and hopeful since seeing content like this, especially after years of accepting that I would just, you know, not film anything moving too quickly, or settle for a less than satisfactory image. Following are the relevant links I got out of the aforementioned thread.

1. Original test video by some guy (reducing/eliminating "jello" artifacts via some kind of filter): https://vimeo.com/5976527
2. Tessive's discontinued product and explanation of concept:
https://vimeo.com/46701641
3. RED's mount design incorporating filter (who can even afford to rent one of the cameras for these things anyway?): http://www.red.com/store/products/dsmc-mount-ti-canon-captive

As an afterthought, although I'm hesitant to open this can of worms lest this become the sole focus of this thread (assuming anyone reads this), I also dare to ask (bearing in mind that I'm not knowledgeable of hardware or software): in light of the video from Tessive's vimeo account explaining the phenomenon (in particular from @2:44 on wherein the guy talks about frequency response of shutter angles), is there any aspect of this that can be coded or something? Like I said, I don't understand the practical stuff, just the conceptual type stuff, and not especially well at that. Hopefully something will come of this discussion.

[*5/7: solved]

I've been messing around with my eosm today, and so far I've encountered several "problems."
Having just started using ml, I don't know yet how much of this is to do with the settings I have chosen, or what.
I'll list my settings below, first, here are the problems I've been having:

1) in expo: dual iso value changed in movie mode so that both values are changed to the same number (sometimes in photo mode, but usually with camera turn off)
2) in expo: whenever I change iso to below 200, it automatically resets to 200 (in dual iso, setting it to 400/800) *5/7: solved
3) in video mode: when recording the last few times (it was working fine earlier) video will get stuck in loop of 1-2 frames in live view, however in file manager it shows that video has been recording the whole time. *5/7/: this has not happened since, but I still don't know what caused it
4) for some reason, perhaps this is common, when I enable silent pictures two things happen: one, the left arrow on the "joystick"/d-pad/whatever triggers a photo; two: when I go to disable silent picture photos can no longer be taken normally. Does this fall under the so-called "shutter bug" issue typical to this model?
5) in photo mode: weird vertical banding/red and blue noise, doesn't show up in captured photo, screenshot below:
6) in ML settings menu: random graphics from the live view HUD will flash over the screen, sometimes I will press a button/arrow key/etc. and it will exit the menu and start recording.
7) I have also noted that even after I turn off all the modules which I understand to be connected to other values it still seems as though some of the settings in the camera are changing (I'm thinking specifically of fps and shutter values) without my having done so, which makes having reliable presets rather difficult...
8 ) Just today (5/7) I've been noticing that my color profile from between the resulting photo and live view is drastically different, very confusing.
9) it also seems as if every time I take the photos and videos I've shot off of the memory card that the camera will start behaving noticeably different. The camera has not gone through the same startup "behavior" every time. That is to say, atm when it turns on ant the scripts start loading, the image becomes choppy, whereas previously it had not done so. I don't remember any of the other changes that have happened of if they were as obvious; the main point is that the camera's performance always seems a little weird on startup after clearing the folder dcim/100canon.
10) In ML menu: sometimes when I turn the camera on and off the max resolution that the camera will constantly record at is diminished (before turning off it's stable at a higher one, then on reboot it is no longer so), despite not having changed anything. This and similar problems seem to have ways of being worked around, however, only by fiddling with the camera settings until it seems to "remember" that there's no conflict, I presume as much anyway, I have no idea what's going on. Again, this is making it incredibly impractical to even take the EOSM out to shoot aside from testing purposes, which I can't really make much headway in unless someone can help me out and tell me what I need to do to get all this dealt with.
11) info button will not always toggle between ML and Canon overlays. Just tried turning off global draw and it did not change anything... there's also this orange line at the bottom of the screen that appears to be "loading" whenever I press the INFO button, however, it doesn't actually seem to be doing anything. When I press the INFO button, it seems merely to change the direction which the orange line is going.


I had some working settings earlier today, started having the pink screen overexposure/peaking, and figured out that
I had forgotten to edit some settings in FPS override, changed that and had a decent video setting again, did some
shooting, turned camera off, then was experiencing the pink screen/overexposure again, without having changed
any settings.
Fiddled with settings to see what was going on, ultimately did not change any parameters, switched some on and off,
and then had workable live view again. Turned camera off and same problem occurred. Is this a common thing?

*****
Also had the following error while running api_test.lua: upon running the script, initially showed a number zero on the right side of the ML menu, have to manually exit ml menu before script can be seen, script runs, fails, and show this error message:

script failed:
ML/SCRIPTS/API_TEST.LUA:213: set 'shutter' failed
slack trackback:
[C]: in metamethod '__newindex'
ML/SCRIPTS/API_TEST.LUA:213: in function 'test_camera_exposure'
ML/SCRIPTS/API_TEST.LUA:638: in function 'api_tests'

Tried several times since the first error with a different sd card, the third time I got almost the same error
as the first, but with the first ml/script reading LUA:222 instead of 213. What does this mean?

*************
*EDIT—May 7th:
so I also am having some strange things happening when I push the shutter up to 32" (in photo mode)... once it had a perfectly workable image, and then after changing other settings and the shutter as well (and going back to photo mode) suddenly putting the exposure up to 32" produces some strange live view results:

This is supposed to be some lightposts on my college campus...
from what I remember the photo it produces looks nothing like it, however all of this is rather perturbing, and I could use some feedback.

Just got an eos m, going to start experimenting with that once I can devote some more time to exploring the different post production options outlined in the forum...
This may sound like a strange request, since the main trend of this forum seems to me to be trying to get improved footage out of the canon cameras (I do like nice footage as well), however, I am curious to hear if anyone has any suggestions on intentionally corrupting raw images, and stable ways to save them and/or convert them.
I've attempted to make one movie using such "glitched" footage by a very lengthy process of importing video footage as raw data into audacity, but the process only outputs a small portion of footage from the middle of the original that is even readable.
By convenient fluke the original file became corrupted when I was exporting it from final cut pro 7 (which I don't have anymore) on a computer that couldn't really handle 1080p (which I also don't have anymore, currently running a 2012 macbook pro)...
you can watch it below. An example of what I'm talking about can be seen around the 1hr and 39 minute mark:
https://www.youtube.com/watch?v=lIRdbCirjPE
there is also image stabilization from youtube.
-cheers