Messages

[not]

The EOSM and EOSM2 work the same when it comes to starting the camera with the play button. They start up in playback mode which is not LiveView.

I've been busy on other projects so I haven't been able to look into it but the problems with the new DryOS task hooks that are causing problems on the 100D are likely a problem on the EOSM2 because these cameras are very similar. I'll follow the "fix" on the 100D when it is ready.

In the meantime you might look into doing a firmware dump and running it in QEMU. Yeah, I know it is a challenge. Just start here, take it a step at a time and follow what was already posted. Note that compiling ML and getting QEMU up and running is much easier these days.

Oh, derp. I see now you have to hold down the play button for 1+ seconds to get it to start in playback mode--a momentary press won't cut it. That's probably even in the manual for the camera which I probably ought to read.

Was that what a1ex was talking about then--a way to start up the camera in a screen other than LV and launch ML from that screen? Or can ML not run from Playback mode either? Maybe he was just referring to running it within QEMU. Sorry if those are dumb questions.

I'll take your last paragraph as a stretch goal and see how far I can get.

In hopes of trying to contribute something I spent the last hour seeing if there was some way of getting the M2 to power on to any other screen other than LV, and unfortunately I wasn't able to find one. I know with my PowerShot S95 I can press the Play button when the camera is off and it powers on and goes directly to playback mode. But with the M2, none of the buttons appear functional until the Power button is pressed, and that directly goes to LV mode, no matter what settings I tried in the menus. Does the original M have the same limitation?

@bookemdano -- are you able to use Mercurial (command line or through a GUI like SourceTree) and compile ML? That would be the best way to test, once the camera boot flag is enabled of course. So while we're waiting for that, take the time to set up a testing/development environment. It isn't that hard. I've got a few tutorials on how to get something up quickly on Mac or Windows. If you're on Linux you don't need a tutorial.

First of all, sorry for the delay in response. I posted my earlier message and then promptly left on a two week vacation. I'm back now and followed your very thorough OS X tutorial. I just successfully compiled the Oct 1 nightly for the 6D, although I haven't tried actually running it on my 6D yet (guess I should do that before I deem it successful). But I think I'm ready to go for when you've got something ready to test.

I used the M2 on my trip and I'm really impressed with how much camera Canon packed into such a tiny body. I was prepared for the slow-ish focus--it's not a big deal to me. My only real gripe is that it chewed through the wimpy LP-E12 batteries like candy. I think I'm going to pick up a generic ACK-E12 AC adapter for when I test ML on it. I'm still glad to not have to hassle with the E17 and the "feature" Canon added that makes using generic batteries as annoying as possible.

So... any progress lately? I know each body's ML port is like a crying puppy badly needing love and there aren't enough devs here to tend to them all. And the M2 would definitely be the runt of the litter given how few of them were sold.  So no worries if you're prioritizing something else that will benefit more people. But by all means, if there is anything I can do to assist, let me know. I don't have much knowledge about ML development but I'm pretty decent at (eventually) figuring stuff out with some google-fu, asking dumb questions and good old trial and error.

As someone who just bought an M2 I'm really pulling for you dfort. I specifically chose the M2 over the M3 and newer cameras because like the M it runs DryOS and is therefore capable of running ML. Plus it uses the uber-cheap LP-E12 batteries and there's no stupid hassle with using third party batteries/chargers. I chose it over the M because of the faster focusing speed & more focusing points, the lighter/smaller body and the built-in WiFi (since none of the Ms can do tethered shooting over USB, WiFi control is better than nothing at all and is a possible avenue for future innovation).

I am not well-versed enough in coding to assist with the actual porting, but I have a fairly high risk tolerance and a mind for diagnostics. So when it comes time to put an alpha through its paces, sign me up. The M2 is not my main camera, and they can be had somewhat cheaply on ebay so if I brick it, it's not the end of the world.

I'm heartened to hear A1ex's comments that this should be a fairly straightforward port. And dfort I've seen enough of your other contributions here to know that you've got what it takes to do this. So I guess I just want to give you simultaneous pat on the back/shove to keep going. The M2 is the best Canon mirrorless model capable of running ML, so it deserves to run ML

Seriously though, thank you guys for all the time you've spent so far on this endeavor. I'll enjoy my new M2 even without ML, but man I hope I get to run ML on it.

Thanks dmilligan. Unfortunately those options won't work for me (without introducing other complications) because it's impossible to keep the frame rame in sync between the projector and DSLR. I have outfitted my projector with a microswitch which can signal the DSLR to capture the next frame. But without completely replacing the motor in the projector, the slowest speed it offers is ~3FPS.

I have actually played around with RAW video prior to this and had no problem getting 24FPS continuous at 1024x768 (this is 8mm film so that is plenty of resolution for it). Figured 3FPS even at the full LV resolution would be no problem (file sizes are about 4MB each so it ought to be able to do 8 or 9FPS before exceeding the speed of the SD bus).

That's why I was wondering if maybe there are any settings in the menus that might eke out more speed. Has anyone seen higher speeds also with a 5D3 or maybe even an APS-C camera (due to smaller LV resolution)?

Any ideas? Thanks again.

in modules/silent/silent.c, in the save_mlv() function (line 234), replace the following code:
Code: [Select]
    if (is_intervalometer_running())
    {
        frame_number = get_interval_count();
    }
change it to this:
Code: [Select]
    static int current_frame_number = 0;
    frame_number = current_frame_number;
    current_frame_number++;

and then recompile silent.mo

Thanks dmilligan that works great. Can I trouble you again to ask if there is any way I can get more FPS out of this (remember I'm talking about Simple mode, not full-res)? Even holding the shutter button down halfway I get what looks like a little less than 2FPS. I'm trying to get at least 3FPS continuous, since that's the slowest rate my projector can go. Are there any settings you can think of in ML or the Canon menus that would speed it up? I'm already using an SanDisk Pro Extreme which is maxxing the 40MB/s SD bus on my 6D (I don't think the SD card is the bottleneck here, anyway).

Barring anything that can be done in the menus, in your opinion is there any further optimization that can be done to silent.mo to yield a slightly faster FPS? I'm just wondering if it's even possible or I'm bound here by some other constraint.

I should mention I haven't actually tried connecting this to my projector set up yet (which would be actuating the half-press actions via the wired remote port). But I figured that holding the shutter button halfway is going to show the max rate the camera is able to go.

Just wondering what my options are at this point. Any light you (or anyone else) can shed would be much appreciated.

Thanks again!

@dmilligan - thanks for this.

I just compiled and am testing this out on my 6D. For my purposes though I'm actually using silent.mo Simple mode because I need speed (going to try to use it to telecine some old 8mm home movies by "projecting" onto the camera sensor at a low frame rate and triggering the camera to photograph each frame of the film.

I was hoping with your addition that my pics would all be saved into a single MLV container. But when I take a bunch of silent pics it's presently saving each one to its own MLV. When I came back to this thread and re-read the first page I see now that you only implemented saving a single MLV for the intervalometer function.

How difficult would it be to enable this capability (single MLV) for silent pics taken via multiple half-presses? Any chance you could implement that? Maybe as a separate option in the settings since I guess for others it would be undesirable to have all pics from a "session" in a single MLV.

I'm sure you're not looking for more work, so I understand if this isn't something you want to do. Just thought I'd check in case it's a fairly simple change.

Thank you again!

Thanks Levas. When you say fastest shutter speeds with full-res-silent pics is 1/3 of a second are you actually talking about the shutter speed? Because I thought a1ex in the first post said the fastest shutter speed was 1/10 of a second.

And I'm actually not trying to mimic 8mm film, I'm trying to digitize pre-existing 8mm film. I know I can shoot at 18fps and set the projector to 18fps, but the projector uses an AC motor so the frame rate is not going to be precisely 18fps--thus the camera becomes unsynced and starts capturing frame transitions.

What I am trying to accomplish is the projector advances a frame, then tells the 6D to take a picture. That would allow me to achieve 1:1 frame capture (one still image for each frame of 8mm film). I can run the projector at 3fps if this silent mode can take photos at 3fps.

I was wondering what kind of realistic frame rate I could achieve with this on a 6D (assume with a fast enough SD card to get the max ~40MB/s) using a remote shutter release to do the half-press?

I'm trying to develop a technique with which to telecine my family's old 8mm home movies. I've been messing with shooting video and trying to detect and remove all the duplicate frames but that gets very complicated very quickly.

I have mounted a microswitch on the projector shutter which I could adapt to short the half-press shutter "button" on the cable remote connection. Previously I abandoned that route as I would quickly wear out the mechanical shutter on the camera (3600 frames per 50meter film adds up quickly). But I wonder if this silent module could be able to do what I want? I don't even need the full resolution of the sensor--I would be happy with 720p (crop mode?)

I also read the thread about silent mode into an MLV container as opposed to DNGs would make writes faster. Would that help me?

Normally the projector runs at 18fps but it has a slow motion function I can use to do 16, 12, 9, 6 or 3fps.

So A1ex or anyone else familiar with this function--can you tell me if this is likely to work or not? I know most everyone else is using this module for timelapse. I would be doing 1/10 second exposures (the fastest shutter speed available, right?) triggered from the projector using the cable remote and would need to capture at 3fps (or even better 6fps if possible) via simulated half-presses. I am willing to experiment, but if there's no possible way it can work please let me know so I can go back to the shoot video/remote dupe frames method.

Thank you!

The mlv_rec/mlv_sound/autoexec all come as a package. If you take one from another build it may be old or not compatible. With any card that can do at least 40MB/s you should be able to pull of 1280x720 with sound.

Thanks, 1%. I am showing more ignorance here but I thought the autoexec was the heart of TL vs. ML. So if I use the autoexec included with the mlv modules am I still using TL on my 6D? Or I guess to turn it into a practical question there is no problem using a ML autoexec with TL? Or are you saying I need to compile mlv somehow to work with your autoexec? Sorry for the pedantic question.

Its based on the data rate. Whatever you can fit into that ~40MB/s is good.

So 1024x768 should have a lower data rate than 1280x720 right?

Hi all, a bit green still with all this but am picking things up fairly quickly. I have a couple of questions I'm hoping someone might help me with. For starters I've got a 6D, already have TL running on it just fine. Picked up a couple of Sandisk Extreme Plus 32GB, which are supposedly 80 MB/s cards. In another thread, someone here claimed to get really good results with them. Anyway, here are my questions:

1. For what I'm trying to do I would *really* like to get sound recorded along with the raw video on the 6D. From a bit of research it seems this is now possible using mlv_rec.mo along with mlv_snd.mo. However, when I try to add these modules (from the ZIP in the first post here: https://secure.magiclantern.fm/forum/index.php?topic=7122.0) and enable them, when I reboot they show up as "err" and do not load. I also saw a compiled version of mlv_rec.mo on 1%'s bitbucket repo so I tried that one too, same result.

So I think I'm probably missing some crucial piece of knowledge here. I know mlv_rec works with TL on the 6D because I saw someone post about it: https://secure.magiclantern.fm/forum/index.php?topic=7122.msg96937#msg96937 but I am either not installing the correct module files or maybe I need a different build of TL? I have only tried the most recent one from 28 February.

Can someone point me in the right direction as to what I need to do to get mlv_rec and mlv_snd working with TL on my 6D. If I need to compile them, is there a "dummies" tutorial for that somewhere?

2. OK so I have no pipe dreams about what kind of continuous resolution I am going to be able to get. I know the 6D's SD controller is the limiting factor here. But I think I saw someone get 720p (1280x720 I assume) working continuously. My question is what if I choose a 4:3 aspect ratio? Should 1024x768 be possible continuous? Is it just based on the total number of pixels? So say for a given number of vertical lines (say 720) a 4:3 aspect ratio would require less write speed than a 16:9 AR? I mean this makes intuitive sense to me because there are less pixels involved. But I just wanted to make sure that I'm correct on that before I go assuming.

What about with the addition of audio (which I do not need any kind of fidelity on, if that is adjustable. I'm just recording a beep track that I need to be synchronized with the frames). With the 6D's limited SD controller should I be able to get 1024x768 raw along with audio continuously without dropping frames?

It's ok if no one knows that--I plan to experiment with it. Just wondering if others have tried to see what they could get continuous with audio.

Thanks a lot for any help/tips people can provide. And a big thanks to 1% for making this possible on the 6D.