#MAGIC LANTERN CANON 100D VIMEO SERIAL NUMBERS#

Question: What's wrong with address #2020202 and it's fixed size of 514x514 and why is it overlapping almost all edmac channels? Switching to playback mode and back fixes the issue. This causes also the artifacts and happens only in LV / MV mode.

Check this screenshot and find a way to solve the issue.

Check memory management vram stuff or whatever causes the ML menu having artifacts (see screenshot from pull request listed above).

You can only chose one of the different settings but do not have an option to disable it. Another option would be to override the CFn setting with a property but Canon hasn't a simple option in its menu to disable the 'Q' button.

Q/SET button handling is dirty hacked atm.

Nothing really hard to do - just time consuming as I wasn't able to fix it quickly by double checking stubs. The stubs should be fine though but it may be a simple copy & paste error. Hint: I might have made a typo or whatever while porting it. The task_dispatch_hok stub is responsible for the 'C' rev not being able to bring up ML menu.

Use at least the parts modifying task_dispatch_hook stub (preferrably we want to get the PR used fully and not only parts of it) from.

Rebase 100D from the new unified branch and also create a new pull request for 100D afterwards. This situation makes life just more difficult in terms of porting, trying out pull request and so on.

Hopefully get 70D merged into unified branch as 100D / SL1 uses 70D's branch as base (we need this for revision handling).

#MAGIC LANTERN CANON 100D VIMEO SERIAL NUMBERS#

We got 3 known firmware revisions called A & B & C (hopefully there aren't more).Ĭamera serial numbers or sticker labels won't help you in determining the firmware revision. Then play it with VLC Player or whatever player you use and you will notice the hick-up jumps appearing at random locations in the clip.You'll fail with a simple 'make zip' if that's all you do to get the C revision running. Then open it with the latest version of MLV Producer and convert it into H.264. Pretty busy at the moment.įor those who wish to try to reproduce this issue, may be on the latest Experimental build, just dial in the settings from 1) B above and shoot a clip until recording stops. Unfortunately, these hick-ups occur also in earlier builds, I remember observing them last winter at high resolutions, and also in the later builds from Oct. They occur at random locations in the clip, so I wouldn't say that they appear at some periodic time intervals of 2s or similar.

I also get the frame jumps that Danne observed but I noticed them much later when I tried to play the clips. I am not so good at pixel peeping.Ģ) Unfortunately, despite the high image quality, the videos did not come out 100% OK. If there are any, MLV_dump seems to kill them all, so does MLV Producer too. I never noticed focus pixels on the videos shot in those two modes. Frame grab image quality in both modes was fantastic. 11 bit lossless at 5x magnification (about 150 to 250 frames possible in that mode, dependent on the fine detail in the scene).

RAW_rec module at the 2520x1080 resolution, 8. MLV_rec module at the 2496x1080 resolution, 10 bit and sound at 5x magnification (about 83 frames possible in that mode) andī. Experimental build for the 100D to shoot a few clips from my window on the 18-th floor. Here is what I did:ġ) I used the 27-th Sept.

I would like to confirm Danne's observations on the quite annoying frame jumps.

Magic lantern canon 100d vimeo