Messages

Thanks.
I uploaded it at 2560x1090, but youtube has new "feature" that it won't allow to pick higher resolution than what your screen has. I have 1920x1200 screen and cannot pick 4k anywhere on YT, very rarely it allows me to pick 1440p.
Other possibility is that higher the resolution, longer time it takes to generate video.
And also YT might consider wide aspect ratio as unsupported and allow only FullHD (since it has 1090 lines).
I don't know what it is, but it is uploaded in same way as previous video and my friend with bigger monitor confirmed,  that there is 1440p.

As for extended cut, here is longest shot i did, 36 seconds (i didn't needed longer so i stopped it, camera could continue to at least 4GB limit, this was 1.7 GB) 

I did another one, other than a bit cumbersome hack activation everything went smoothly.

Managed to catch International Space Station crossing the Sun.

You can catch your own using this website 
https://transit-finder.com/

It is part of this dfort's build: https://bitbucket.org/daniel_fort/magic-lantern/downloads/crop_rec_4k_mlv_lite_snd.2018Apr03.EOSM202.zip
But be advised, it might be dangerous to your card and/or camera.

Compared to 35 mm camera, crop is 3.4. I have Canon 15-45 and most of the time i used it at 15 mm so it results into 51 mm.

Standard Canon 50/1.8
Maybe it was too dark around and also it was pointed to a blank wall.
EDIT: Also it started in MF mode. but after a while it asked to be switched to AF mode, so i did.

Oh, sorry about that.
stubtest.log
http://s000.tinyupload.com/index.php?file_id=10482695454607144959
luatest.log
http://s000.tinyupload.com/index.php?file_id=58857871548474538660

Downloaded and tested.
https://nofile.io/f/VvAw5pfpa6N/STUBTEST.LOG
https://nofile.io/f/wcCbSQFCTc3/LUATEST.LOG

I have your magiclantern-Nightly.2018Apr10.550D110.zip build and it behaves as mk1174 describes. To be honest i don't remember the last time i used photo mode, so i don't  even remember how it should behave, it displays "screan cleaning" then goes blank and requires either pressing Disp or Live View button (If mk1174 didn't pointed out as a problem, i wouldn't even considered it to be one).

Thank you for the build, going to test it.

I've updated firmware to 1.1.0 and wanted to try 10 12 bit depth build, but it seems that there is none. Several week ago someone tried it though, i think @dfort had one?

Yes,  most of the time, thanks to ML developers, in this case specifically @a1ex and you.

That looks very promising and interesting.

As instructed I did some extensive tests of sd_uhs module and:
First of all, thank you guys, this really extends usability of my EOS M far beyond of my expectations.
I've been using two cards, SD Sandisk Extreme 16 GB and uSD Sandisk Extreme 32 GB.
I've recorded over 30 GB of data during 4 hours, cards are OK, camera is OK, Data are OK (I'm using 3rd April dforts build for EOS M and crop rec build for EOS M from 10th of March).
I shot at 2520x1072 with fps override to 24 fps (HighTV) in 12-bit lossless. Resulting Bandwidth around 55 MB/s.
In most of scenes recording could be continuous, but in some settings I've got only around 3-10 seconds, didn't found reason for this (other than maybe complexity of the scene or temperature of the processor).
Also I don't know how it is supposed to behave but in my case it was: new ML installation enable SD hack, benchmark:

Code Select Expand

===================
2018/04/06 22:29:28
===================
Before the hack: r:37MB/s w:34MB/s  W:32MB/s R:37MB/s  :)  [best 34MB/s]
SDR50 @ 96MHz  : r:37MB/s w:32MB/s  W:33MB/s R:37MB/s  meh [best 34MB/s]
SDR50 @ 96MHz  : r:37MB/s w:19MB/s  W:33MB/s R:38MB/s  meh [best 34MB/s]
SDR50 @ 80MHz  : r:32MB/s w:30MB/s  W:28MB/s R:32MB/s  meh [best 34MB/s]
SDR50 @ 80MHz  : r:36MB/s w:34MB/s  W:35MB/s R:37MB/s  :)  [best 34MB/s]
SDR50 @ 120MHz : r:54MB/s w:52MB/s  W:52MB/s R:55MB/s  :)  [best 52MB/s]
SDR50 @ 120MHz : r:54MB/s w:50MB/s  W:52MB/s R:55MB/s  meh [best 52MB/s]
SDR104 @ 96MHz : r:44MB/s w:42MB/s  W:42MB/s R:44MB/s  meh [best 52MB/s]
SDR104 @ 96MHz : r:44MB/s w:41MB/s  W:42MB/s R:44MB/s  meh [best 52MB/s]
SDR104 @ 80MHz : r:37MB/s w:35MB/s  W:36MB/s R:37MB/s  meh [best 52MB/s]
SDR104 @ 80MHz : r:37MB/s w:35MB/s  W:35MB/s R:37MB/s  meh [best 52MB/s]
SDR104 @ 120MHz: r:55MB/s w:53MB/s  W:52MB/s R:55MB/s  :)  [best 53MB/s]
SDR104 @ 120MHz: r:54MB/s w:51MB/s  W:50MB/s R:55MB/s  meh [best 53MB/s]
SDR104 @ 132MHz: r:51MB/s w:48MB/s  W:48MB/s R:51MB/s  meh [best 53MB/s]
SDR104 @ 132MHz: r:50MB/s w:48MB/s  W:48MB/s R:51MB/s  meh [best 53MB/s]
SDR104 @ 160MHz: r:72MB/s w:70MB/s  W:67MB/s R:73MB/s  :)  [best 70MB/s]
SDR104 @ 160MHz: r:72MB/s w:68MB/s  W:64MB/s R:73MB/s  meh [best 70MB/s]

Done.
Please run THOROUGH tests before using!!!
Then I could record videos with high bitrate. Once i switched camera off and on again memory patch wasn't (obviously) applied, so i tried to enable SD hack again, but i've got this:

Code Select Expand

===================
2018/04/10 08:29:10
===================
Before the hack: malloc error
[best 66MB/s]
SDR50 @ 96MHz  : malloc error
[best 66MB/s]
SDR50 @ 96MHz  : malloc error
[best 66MB/s]
SDR50 @ 80MHz  : malloc error
[best 66MB/s]
SDR50 @ 80MHz  : malloc error
[best 66MB/s]
SDR50 @ 120MHz : malloc error
[best 66MB/s]
SDR50 @ 120MHz : malloc error
[best 66MB/s]
SDR104 @ 96MHz : malloc error
[best 66MB/s]
SDR104 @ 96MHz : malloc error
[best 66MB/s]
SDR104 @ 80MHz : malloc error
[best 66MB/s]
SDR104 @ 80MHz : malloc error
[best 66MB/s]
SDR104 @ 120MHz: malloc error
[best 66MB/s]
SDR104 @ 120MHz: malloc error
[best 66MB/s]
SDR104 @ 132MHz: malloc error
[best 66MB/s]
SDR104 @ 132MHz: malloc error
[best 66MB/s]
SDR104 @ 160MHz: malloc error
[best 66MB/s]
SDR104 @ 160MHz: malloc error
[best 66MB/s]

Done.
Please run THOROUGH tests before using!!!
Strangely enough, after this memory patch have been applied and i could continue recording with high bitrate.
I wanted to ask if is it possible to streamline usage of the hack (like add menu "apply saved SD clock values", or to avoid opening console), but since you retracted the module, i don't know whether you intend to explore this more. (And as far as i'm concerned i'm not giving this module back )

If you are interested in result, i posted it on youtube

I did some tests using experimental sh_uhs.mod module and this is the result.
(more information about module https://www.magiclantern.fm/forum/index.php?topic=12862.0)

This is just amazing 
5 years old camera that i bought for $150 can do continuous 2.5K (2520x1072 - 2.35:1)@24 fps video in 12-bit compressed RAW (~56MB/s), wow, just wow 

Sandisk Extreme (microSD, not even Pro) results (in replay mode)

Code Select Expand

===================
2018/04/06 22:29:28
===================
Before the hack: r:37MB/s w:34MB/s  W:32MB/s R:37MB/s  :)  [best 34MB/s]
SDR50 @ 96MHz  : r:37MB/s w:32MB/s  W:33MB/s R:37MB/s  meh [best 34MB/s]
SDR50 @ 96MHz  : r:37MB/s w:19MB/s  W:33MB/s R:38MB/s  meh [best 34MB/s]
SDR50 @ 80MHz  : r:32MB/s w:30MB/s  W:28MB/s R:32MB/s  meh [best 34MB/s]
SDR50 @ 80MHz  : r:36MB/s w:34MB/s  W:35MB/s R:37MB/s  :)  [best 34MB/s]
SDR50 @ 120MHz : r:54MB/s w:52MB/s  W:52MB/s R:55MB/s  :)  [best 52MB/s]
SDR50 @ 120MHz : r:54MB/s w:50MB/s  W:52MB/s R:55MB/s  meh [best 52MB/s]
SDR104 @ 96MHz : r:44MB/s w:42MB/s  W:42MB/s R:44MB/s  meh [best 52MB/s]
SDR104 @ 96MHz : r:44MB/s w:41MB/s  W:42MB/s R:44MB/s  meh [best 52MB/s]
SDR104 @ 80MHz : r:37MB/s w:35MB/s  W:36MB/s R:37MB/s  meh [best 52MB/s]
SDR104 @ 80MHz : r:37MB/s w:35MB/s  W:35MB/s R:37MB/s  meh [best 52MB/s]
SDR104 @ 120MHz: r:55MB/s w:53MB/s  W:52MB/s R:55MB/s  :)  [best 53MB/s]
SDR104 @ 120MHz: r:54MB/s w:51MB/s  W:50MB/s R:55MB/s  meh [best 53MB/s]
SDR104 @ 132MHz: r:51MB/s w:48MB/s  W:48MB/s R:51MB/s  meh [best 53MB/s]
SDR104 @ 132MHz: r:50MB/s w:48MB/s  W:48MB/s R:51MB/s  meh [best 53MB/s]
SDR104 @ 160MHz: r:72MB/s w:70MB/s  W:67MB/s R:73MB/s  :)  [best 70MB/s]
SDR104 @ 160MHz: r:72MB/s w:68MB/s  W:64MB/s R:73MB/s  meh [best 70MB/s]

Done.
Please run THOROUGH tests before using!!!

Oh, WOW, this is amazing .

On EOS M 2.02 somehow i max out at ~45mb/s,  two different Sandisk Extreme Pro cards, two different builds (second is dfort's build from yesterday).
@dfort have you got some special edition cards? Better stickers or something?

I should probably update it but it would be nice to get some feedback.

Sorry, i've tested it while ago, but forgot to write what i found (in short, it didn't work for me, but other builds also so i presumed error on my side).
(everything is about videos in 10-bit colors)
But i gave it a go again today and results are ....strange.
First video is always OK whatever resolution, framerate or aspect ratio is, but in next videos every even frame is shifted. Only switching the camera off and battery removal resets it, so next first video will be fine, and following are shifted again.



gif free upload

Nevertherless, since now i know this, it greatly extends usability of this ol'hag for me, so thank you for the build .

I did find a bug on the EOSM that I couldn't resolve. When in zoom mode at maximum 2520x1080 resolution if you set the FPS override to "Optimize for Exact FPS" or "Low Jello, 180d" the right side of the image gets chopped off and glitches appear every few frames. Basically, a black bar on the left of the frame that can be seen on the LiveView screen if the Preview is set to Auto or Framing.

This bug, altough in my case it's on the right side (as a1ex), is there for at least 9 months, i have it in my test from April ( https://youtu.be/FyfRVbYHYh8 ). Strangely enough, it disappeared when fps was set to 15 fps (https://youtu.be/Wvs2KDwk0M8). With build from December the 19th it's not true any more, and stripe is there to stay (only in exact fps mode though).
I will test your new build tomorrow.

... This camera works best in Movie crop mode (a.k.a. mv1080crop or CROP_MODE_HACK). In fact that's the only mode where the camera will record in 23.976 fps without having to use the FPS override option. ...

And just when i thought that I understand all different modes, new wild mode appears 
I'm currently using crop_rec_4k branch, that allows using full buffer 2512? pixels horizontal resolution in 1:1 crop mode, but as pretty much in all modes on EOS M at 30 fps and as you wrote i indeed need to use FPS override to get to 24 fps (and that has it's own set of problems regarding rolling shutter and exposure time).
Can you elaborate how to record in this mv1080crop mode?
I found only this table, but i don't know how to activate it http://www.magiclantern.fm/forum/index.php?topic=5601.msg194406#msg194406
(Also I presume, that maximum resolution stays at 1872x1060?)

Tip - to post a YouTube video change the URL from https to http and enclose it in youtube tags like this:

Code Select Expand

[youtube]http://youtu.be/YcKTqGJUTls[/youtube]

Thanks, didn't know that.

I've just tested build  magiclantern-crop_rec_4k.2017Dec19.EOSM202.zip and it's amazing,  2.5K RAW video (altough with some limitations given SD card write speed).

Did some shots, in case anyone is interested you can check video here https://youtu.be/YcKTqGJUTls

I have a used sigma 10-20mm f3.5 which works good for the price paid. Of course you will also need a canon ef converter to mount the lens.

That looks fine, but it's way out of my price range (around $400 here), also with adapter it's not so light combo with EOS M anymore.

I've got c mount lenses. 25,12.5,8.5 and 6mm. i think pretty much any of them will work in crop mode. 3x or 5x crop mode. i had a 4.5mm lens and that one even worked. i broke it though. c mount lenses don't seem to focus to infinity though... at least mine don't . i haven't made any modifications to them. also they are all over the place. I've got 1",3/4", 1/2" they all close focus no problem. wide angle infinity focus seems soft to me. not terrible though. more resolution and we would be in serious territory. im still waiting for compressed raw. then we are talking better than a7sii in sharpness territory. I've got one of those too. and sometimes i prefer the 100 dollar M to it.

Could you elaborate on manufacturers of these lenses? I managed to find some from Tamron and Fujinon.

CS isn't C. The CS lenses are designed for small surveillance cameras. You can use C mount lenses on a CS mount camera with an adapter but not vice-versa.

I don't say it is, i'm saying that the only difference is in flange distance, and some sellers do not make difference between C and CS mount, hint would be size of an image circle, 1/2" being borderline size (at least i understood that from wiki).

Anyway I ordered this Tamron 8mm for 2/3" sensor http://www.tamron-usa.com/IO/IndOp/prod/23fm08l.php when it arives i'll do some tests and post results in case someone else is solving the same problem.

EDIT: mistype

Hi,
if I understood correctly, when shooting raw video, most of you are using (one way or another) crop mode in either telephoto mode (with EF-M lenses) or you are using some short focal length C-mount TV lenses. Is there a list of usable (and affordable preferably) lenses (i'm looking for sub 15mm)? Problem with C-mount is that there are two versions and most seller cannot (or don't want to) differ between them, talking about C-mount and CS-mount, same thread but different flange distance (CS 12.5 mm, C 17.5 mm) so CS is pretty much unusable since it's impossible to focus it.

What do you mean? EOS M can do mv1080 if you turn on H.264 proxy. It is rather buggy and experimental but hey.

http://www.magiclantern.fm/forum/index.php?topic=16608.msg179969#msg179969

I mean I wasn't able to replicate it, I wasn't able to get same nightly and with my version of ML although i've been able to capture whole frames, all were in pink and after correction of black and white levels it has been extremely noisy to the point of unusability. Same processing of test mlv of Koks the cat lead to excellent results, just my camera didn't deliver same input. When I asked about what build i should use, it stayed unanswered  ( http://www.magiclantern.fm/forum/index.php?topic=9741.msg183234#msg183234 ) (not complaining, just stating). I've got in bookmarks your bitbucket page, but you wrote that your version was really experimental, and also i'd have to update firmware to 2.03, and i thought since 2.02 is more mainstream, that development would go faster there.

@reddeercity
It's not like we wouldn't like new builds, but most of us are not programmers, so we do some test, and that's it. I for one would love 10-bit RAW working on 550D, but I have same problems as others, all frames are corrupted 1/3 of screen is shifted and frozen. Since this has been reported, i'm afraid that's all I can do.

(I was also hoping in mv1080 on EOS M, but all my questions in appropriate threads have been ignored, so i kinda gave up)

Well, early christmas came to mind