Messages

Have you tested it out yet Apxub, and if so, did it work as intended?

Yes, it is in the FPS-override menu.

Sounds great! You have already made your choice, and I am sure it's a good one. Personally though I think the Canon m6ii has the potential of being the ultimate hybrid camera, if it hade ML-video. As a photo camera it is really excellent, best colors I've had from a digital camera, good af etc., and for its size without competition. The ef-m lenses are also very compact and it is a nice lineup. So, when you're done with your current project, in a couple of years maybe, think a bit about the m6ii.

Ok, good to know. I did try to install the focus pixel maps manually in the appimage build, but only got them to work with the 1x1 presets. Probably something I did wrong, but this build solves it anyhow. For the dng:s I did actually try a program called rawstudio (it is very fast, so processing a large quantity of dng:s for video is actually doable), but also rawtherapee just to see what it looked like, and neither one had the image stretched. But as they are photo editors, I guess not reading the stretch (if the mlvapp puts such information in the file) is what to expect.

The DNG-export works perfectly when building from source on Ubuntu 22.04, so my problem is solved by that really. The automatic import of focus pixel maps also works for all modes on the EOS M with that build, something that did not work for me at all for the "anamorphic" modes with the latest appimage. These things considered, would a new appimage for linux be possible?

For me, the 1x3 dng images are not stretched after export. Is that a known fact/problem?

Thanks!

I am using Ubuntu 22.04 by the way, latest version of the MLVapp.

Having a problem right now with exporting cinema dng:s (uncompressed, lossless and fast pass) from the mlvapp. It only exports the first frame, then it stops with the message "Disk full." and then "Disk full. Export aborted.". I have 65gb free on my computer and 250gb on my external disk where the mlv files are. I can export frame by frame to dng ok. All other formats (tiff, h265 etc) are exporting as normal. Any idea what I may be doing wrong?

Ok, that's too bad, but thanks for the quick reply! What's the lowest rolling shutter on the 700d in 1x3 mode?

Really love the crop mood and the work everyone in the magic lantern team has done to make it possible, thanks to everyone involved for that! I have used it alot and have started wondering if another mode could be added:

The downsides of the eos m as a cinema camera are well known: Aliasing in 3x3-mode and rolling shutter in 1x3-modes. I have also found 3x3 the noisiest, 1x1 second most, and 1x3 the cleanest when using high iso:s, but that is probably well known as well. Anyhow I mostly use the 1x1 2.5k crop because of reasonable rolling shutter and little aliasing, the crop is acceptable when considering the colors and overall image quality from the magic lantern eos m. For me, the rolling shutter of about 24ms still requires a stabilised lens for handheld use, to look good (every mode works well on a tripod, of course). The 2.8k mode has as much rolling shutter as the 4.4k 1x3 mode (about 29ms according to ml menu), so the 4.4k seems a better overall choice because of less noise and less crop. Now I have started to wonder if there has been any experiments with smaller crops using the 1x3 mode? Would it be possible to make a 4k or smaller crop of 1x3 to get the rolling shutter closer to 20ms? A super-16mm crop (3x) in 1x3 mode could also be interesting, if possible, with even less rolling shutter. I guess the picture would be softer, and there would be some aliasing compared to the 1:1, but maybe it would be a good compromise considering the problems of the different modes, or are there other downsides?

Tested the build now, and it is wonderful, thank you Bilal! As stated earlier, for the eos m the button customisation for changing ISO and aperture with up and down arrows from Dannes build is really the only thing missing. It is quite important for smooth use with the EOS M, as you have to click into menus to change these things otherwise. Again, thank you!

I am only using Linux, and I really like the workflow with doing all grading in the mlvapp before exporting it to a better format for editing, which makes the whole editing experience smoother. For various reasons I have started to look at alternatives to the 5d mk3 and EOS M. I tried converting some photo dng samples I downloaded from the Sigma FP, but when loading into MLVApp there were black bars, pink color etc, so I guess the FP is not supported, or do the cinema dng files work? I have also been looking for cdng-files for the original BMPCC online, with no luck, to see if that camera would work in MLVApp after converting cdng to mlv. Does anyone know if it works?

Please disregard my previous post. I had to change the function for the trash button in the canon menu. It was set to ISO and not normal , for some reason. Apologies.

I have this problem on Dannes latest build Nightly.2022Oct06.EOSM202 that when i press down to lower ISO, the Canon ISO menu shows up, and ISO doesn't change when changing it there. Pressing up to increase ISO is no problem. I did not have this problem in earlier builds. Is there a workaround for this?

In 240MHz overclock

I returned the Kingston canvas go! plus cards and bought a sandisk Extreme Pro 256gb microSDXC instead and now I get 91/86/91/86 in play mode and 75/70/75/70 in normal mode.

Yes, I tried that one, with the same results.

Tried that, but it doesn't work. 160MHz works in both SDR50 and SDR104, but that's about it.

Received the Kingston Canvas Go! Plus 256gb sd card now. Same results basically. It only works in 160MHz overclock for me, and gives benchmarks with read and write at about 59 MB/s, both in normal and play mode, so this is actually a bit worse. My Sandisk Extreme Pro 64gb works in 240MHz but the benchmarks in play mode are 92/86/69/85 and 58/70/62/70 in normal mode. I am using build Nightly.2022Oct06.EOSM202. It also says "Mercurial changeset: 8a324688dbad" in the help folder, if that is relevant. Replacing with Bilal's module changes nothing. Just to see if I have done something worng: First I used low level format on card in camera, then I put the files from Dannes build in root of card, then I ran firmware update with card in camera.

Ah sorry, didn't see your post Walter. I am away for the weekend, but I will look into that when I get back home.

Used Dannes latest build (october 06 I believe). I have the Kingston Canvas Go! plus 256gb on the way, will see what happens when that one arrives.

Tried that on both 240Mhz and 192Mhz, but did not work. I have returned the card and will try the normal SD-card size instead. It may be something with my camera as well. I only get about 79Mb/s with my sandisk extreme pro 64gb in play mode, but maybe that's normal. I have tried re-installing magic lantern on both card and camera, with the same result.

Bought the Kingston Canvas Go! Plus microSD 128gb with micro sd adapter. Unfortunately it does not seem to work with the 240mhz overclock. It works in 160mhz and then I get 59MB/s read and write in movie mode and about 69MB/s in play mode.