Jump to content

Alpicat

Members
  • Posts

    97
  • Joined

  • Last visited

Posts posted by Alpicat

  1. 1 hour ago, tupp said:

    @Alpicat

    Thanks for all the updates and videos!

    At some point, I hope that someone will create a simple tutorial demonstrating how to configure the EOSM with ML to enable these capabilities.

    Thanks! Hope I can do a tutorial someday. Right now the SD overclock hack is simple enough to use, at least compared to the next phase of development that is being carried out to increase the resolution beyond 2520x1080, which is an extremely complex process.

    We're hoping it will be possible to overclock the SD card interface even further at some point. With the current overclock hack the write interface runs at 160 mhz (up from 100 mhz natively used by Canon). If the developers find a way of getting the frequency up to 208 mhz (the max UHS-I cards can achieve), then the camera's write speed could increase up to 80mb/s apparently (as opposed to 55mb/s with the current hack). That would make 2520x1320 recording feasible, possibly even 3k recording. 

    In fact I just saw that a new build has been posted enabling 4k recording for the EOS M and 100D. Will test tomorrow but doubt it'll be possible to record longer than a few frames! 

    Here's another really quick test recording 2520x1320 and 2336x1314:

     

    @PannySVHS that looks very interesting and would be great if someone could look into reviving that hack. The colours look amazing, must be thanks to that CCD sensor! Unfortunately I have no coding knowledge so wouldn't know how to help. 

    Magic Lantern development on the EOS M has progressed quickly since this thread started and now in crop mode it's become a 16mm camera (thanks to an increase in resolution capabilities) - so the title of this thread is slightly out of date. Maybe I should start a new thread! Of course it's still possible to shoot super 8 at 720p without using any of the experimental builds.

  2. The 700D, 100D and EOS M are now able to shoot around 2520x1320 in crop mode (previously 1080 was the max vertical resolution). 3k is also possible although liveview doesn't really work at that resolution.

    Record times are very short as it's only possible to shoot in 14 bit lossless for now. Here's my first successful test with the EOS M recording at 2520x1320 and 2336x1314:

     

  3. Looks like the magic lantern developers are getting close to 3k raw video recording on the 100D and 700D. I'll hopefully be able to start investigating the EOS M too as that's a similar camera. One issue at the moment is that 10 and 12 bit lossless are unsupported at this resolution, so record times are very short, and it's all extremely experimental at the moment.

    Here's the link to the 100D thread re: this topic: https://www.magiclantern.fm/forum/index.php?topic=16040.msg202627#msg202627

     

  4. @tupp the lossless bitrate menu settings seem to keep changing with each build I install - sometimes I see 10 bit lossless in the menu, and other times 11 bit. I don't know why but in any case I've never been able to see a difference. 

    Danne's newest test builds which bypass the overclock tests are meant for 95mb/s Sandisk Extreme Pro cards which is what most people seem to be using. It's possible it works on other brand cards but I don't know.

    Thanks for talking to the card manufacturers, sounds like a great idea! What would be nice is if they could increase the write speeds for UHS-I SD cards (of course there's UHS-II, but that's no good on an EOS camera) - I'll write to Sandisk. I wonder if it's the card that's being overclocked or the camera's internal card read/write interface? 

    Yes in that video there was just the open sky in the background which was blown out. But using Juan Melara's cdng grading technique the highlight rolloff looks more pleasant (see here: http://juanmelara.com.au/blog/a-better-way-to-grade-ursa-mini-cinemadngs ) 

    My card already came formatted to exfat since it's 64gb size (I think the 32gb ones are fat32). When I put ML in this card I just copied pasted the files on there after formatting the card in camera I think, didn't do anything special. You can format the card to fat32 but I haven't seen any improvements in max write speeds when doing so. 

     

     

  5. @tupp thanks for posting that video - All-I frames video looks like a great option when recording with the full sensor!

    As for 1800x1030 resolution (without the sd card hack), with 12 bit lossless you can record for a long time if there's not too much contrast or highlights in a frame. 10 bit lossless is continuous

    There's some slow progress being made with the sd card hack, it's now possible to use it without having to run tests (which took around 3 minutes every time the camera was turned on), so it's quick to start up now. However that build only works with certain fast cards, and it's still not safe to use. If you try that build with an unsupported card, I don't know what would happen to it.

    Below is my latest test, this time with people! I'm using a Sandisk extreme pro 95mb/s 64gb card I'm still getting a max of 55mb/s write speed. At 2520x1080 resolution in 12 bit lossless, recording runs for quite a while unless there's a lot of highlights and contrast in a frame. 10 bit lossless is usually completely continuous. I shot this when it was 26 degrees celcius outside, but the camera worked - it didn't go above 42 degrees C.

    Also I've now bought a Canon efs 10-18mm lens. Waiting to get a viltrox 0.71x speedbooster when it's released. That speedbooster combined with this lens at 2.5k resolution in crop mode will result in a field of view of 24mm (35mm full frame equivalent). That's wide enough for me and will make crop mode totally usable.... and that lens has IS which works nicely.

     

     

  6. 41 minutes ago, DaveAltizer said:

    It looks fairly well contained though. Im going to make a video with the one I get and start bugging Metabones to make one. I hope they do. 

    I wrote to Metabones and Viltrox about this - Metabones said they have an ef-m speedbooster in their plans but couldn't discuss any further details. Viltrox said they're planning to release one in a few months. 

  7. 12 hours ago, byuri734 said:

    Great. Any application of this for sound recording as well? My understanding is that sound does not work with lossless compressed, right? Perhaps with higher speeds one can record uncompressed with sound.

    I think someone posted a build with the mlv_lite module able to record sound a while back even before the hack was available. It's in the magic lantern forum somewhere. I'm sure it should be possible.

  8. 13 hours ago, capitanazo said:

    so will never be able to record on non crop mode more resolution than 720p on the eos m?

    Hard to say, depends on whether someone is willing to put in time and effort to enable 1080p non crop on the eosm. If you're interested and want to help out with the development, there's a discussion about this on the magic lantern forum: https://www.magiclantern.fm/forum/index.php?topic=16608.0

    13 hours ago, capitanazo said:

    and what about the 700d cant handle 1920x1080x24p 10bit on non crop mode with the uhs-i hack?

    None of the digic 5 cameras can shoot 1920x1080 in non crop mode, I think only the 5D mk III can do that. Here's the magic lantern raw calculator which gives you info on the different camera resolutions: http://rawcalculator.bitballoon.com/calculator_desktop

     

     

  9. 4 hours ago, capitanazo said:

    Guys i have a question.

    with the new uhs-i hack, you can record with 14-12-10bit in with sound and without crop mode?

    get an eos m1 plus a focal reducer would be a cheapest fullframe killer solution!

    The hack doesn't change the usability of the camera - you can use it the same way as without the hack. You can shoot without crop mode with the hack enabled, although it's probably not worth it?

    You can shoot all bitrates in raw with sound, but not with lossless raw since that uses the mlv_lite module. However I think someone managed to enable sound recording with the mlv_lite module - worth checking on the magic lantern forum.

    In non crop mode the EOS M can only record up to 720p raw (with a lot of aliasing and moire). Using 3x3 pixel binning mode (also non crop) it's still 720p max but at least there's slightly less moire. Regular h.264 is 1080p in non crop mode (with or without the bitrate hack). There's a discussion about that camera here: https://www.eoshd.com/comments/topic/26577-is-the-eos-m-the-digital-super-8-camera/

    I posted a video I've done with the EOS M + SD card overclocking on that thread, but reposting it here since that hack is relevant to a number of other Canon DSLRs. Works the same way on the 100D, 700D, 650D and others:

     

     

  10. I've uploaded another video with the SD card hack:

     

    @tupp It takes about 3 or 4 minutes to do the two tests before the sd overclock is ready to use, and then the camera runs as normal. You should be able to shoot 1920x1080 in 5x zoom mode without overclocking in 10 bit lossless - you won't get much record time but it's feasible. I can already get nearly continuous shooting in 1800x1030 12 bit lossless movie crop mode.

    I did notice it isn't possible to shoot video without the "release shutter without lens" enabled, don't know if it would be possible to get around that with Magic Lantern.

    Also, unsure if I mentioned that Viltrox are planning to do a 0.71x focal reducer for EF-M mount - they told me it should be out in the summer. I don't have a bmpcc speedbooster any longer so this should be a cheaper alternative, with the advantage of electronic contacts for EF lenses.

  11. Here is my first test filming 2520x1080, 12 bit lossless on the EOS M with the sd card hack, this shot is 2 minutes long using the stock zoom lens and a sandisk extreme pro card. Processed via MLV App and Resolve:

    Currently you need to perform an overclocking test and then a benchmark test for your SD card after each time the camera is turned off, so it's a bit cumbersome.

    Here's a still - a cdng processed through photoshop, different colour temperature than in the video:

    M06-1203_002603.thumb.png.b771bd91cca670e33c9937a7c987fc49.png

  12. On 25/04/2018 at 10:01 PM, Matt James Smith ? said:

    Is anyone else getting pink in blown highlights when shooting RAW on EOSM?

    The EOS M doesn't handle blown highlights very well in raw and you do sometimes get a flat pink (or pure white) colour in the blown out areas, and it's easy to get with harsh clipping sometimes with colourful moire appearing at the edges of the blown out areas. MlRAWviewer might make the problem worse - worth trying another program like MLV App to see if its still an issue? The way to get rid of the pink and hopefully bring back some information is clicking 'highlight recovery' in Resolve, but I'm not sure this necessarily works in every single case. If you want to go slightly further with highlight recovery, look at Juan Melara's tutorial on grading cdngs (for Blackmagic cameras but works for magic lantern raw):

     

    On 01/05/2018 at 6:59 AM, tupp said:

    Here are a few seconds (30MB MOV file) shot on the EOSM with the more recent ALL-I hack enabled and with bitrate boosted 1.5x:

    Great work though it's a shame about the moire. I guess this must be 720p mode because when shooting 1080p mp4's (with or without bitrate hack) I'm pretty certain you wouldn't get so much moire?

    Today I've tried the SD card overclock hack. It works and will post footage here soon.

  13. @ntblowz @Timotheus I emailed Viltrox last week and they mentioned they're going to release a speedbooster for eosm in a few months - although I don't know when they'll announce that officially. Metabones previously also told me they were looking into designing one but were unable to discuss any details at all. Looks like you had your speedbooster modified to fit the M50 with electronic contacts? It looks great!

    Personally I look forward to using a speedbooster with the original eos m with magic lantern, especially now that it can do continuous raw recording at 2.5k resolution in crop mode with the sd card hack.

  14. 8 hours ago, webrunner5 said:

    That is how stuff looked years ago, and we dreamed to be able to shot it like it is now! Crazy.

    That's true  - particularly in the examples above where grain has been added in post, but sometimes that look can be nice! If you want a modern and sharp but still pleasant looking image - with the new SD card overclock module the EOS M can record 2520x1072 raw continuously (using a 3.33x crop from 35mm full frame / approx 16mm size). The module is still very experimental so just waiting a bit longer until hopefully it will be easier to use!

    4 hours ago, tupp said:

    @dfort on the ML forums has directed me on how to get a build with ALL-I working, and I have already installed it and enabled ALL-I and set the bitrate to 1.5x.  Testing soon, and if I don't get any glitches, I will try to gradually boost the bitrate until the video breaks.  Will posts the test results as soon as I am able.

    That's incredible, thanks so much for doing this and look forward to hearing more about your results! 

    @Nikkor  There are no pink dots when recording in lossless 10 or 12 bit raw, but they do still appear in all the other raw formats. In any case this isn't an issue any longer as modern mlv transcoding programs such as MLV App use a focus pixel map to automatically get rid of all the dots (without requiring chroma smoothing), so you won't even know they were ever there.

    However, the EOS M still can't do 1080p when shooting full sensor raw, it stays at 720p and therefore there's a huge amount of moire. They were looking to find a way around that issue but that didn't seem to go anywhere. Here's the thread about that: https://www.magiclantern.fm/forum/index.php?topic=16608.0   If you're recording full sensor, it's best to shoot regular h264 with the bitrate hack which is 1080p. The moire is still there but it's a bit more controllable. I'm able to set the h264 bitrate at 3x and with a Sandisk 95mb/s it seems stable.

     

     

  15. @Matt Kieley thanks for posting your videos and the three others above, all really good. I never realised video on the EOS M could look this great without using crop mode, shows how useful the h264 bitrate hack is! When shooting raw without crop the amount of moire is extremely bad, and I'd assumed it was exactly the same with h264 video but that's definitely not the case, it's much more usable. 

    I like this one from Ryan Moorman with the 4:3 aspect ratio:

     

  16. 18 hours ago, mercer said:

    I had the 14-42mm, first version, last year during the second time I briefly had a Pocket cam.

    The lumix 14-42mm mark II was my first lens with the BMPCC, which I used briefly before switching to a speedbooster. The stabilisation worked fine for me too, though there was no way of turning it off as there was no OIS switch on the lens itself. When panning the motion could get a bit jerky, depending on the way you panned.

    Here's a video I made with it (also using an Olympus 9mm f8 toy lens for wide shots), prores, with some post stabilisation:

    And this one exclusively with the 14-42mm:

     

  17. Thanks, that's good to hear. Hopefully this adapter will appear soon. Would be amazing to use the BMPCC speedbooster, which in this case would provide an equivalent crop factor of 1.93x.  Could be risky though as the EOS M has a mechanical shutter which might hit the back of that speedbooster but I suppose it's possible to shoot video without firing the shutter.

  18. On 14/03/2018 at 10:40 PM, tupp said:

    I also was under the impression that "movie crop mode" could be super16 in size.

    We're getting close to this capability on the EOS M. As mentioned in the main EOSHD magic lantern video thread, the magic lantern people found a way to hack the SD card writing speed on Canon cameras, which on the EOS M would mean being able to shoot at max 2520x1072 continuously in 12 bit lossless raw in 5x zoom mode (2.35:1 aspect ratio), as opposed to just 5 seconds max recording time. The crop factor at this resolution is 3.33x which is between 16mm and super16. With a speed booster, the crop factor would get pretty close to micro 4/3. 

    Someone has already successfully used this SD card hack on their EOS M, although for now it remains very experimental and possibly dangerous for the SD card - see his forum post here: https://www.magiclantern.fm/forum/index.php?topic=12862.msg199939#msg199939  and his video shot at 2.5k below

     

  19. On 15/03/2018 at 6:15 PM, tupp said:

    ML has not been able to get higher raw resolutions from the full sensor, but I am not sure that is due to the EOSM lacking "power."  I assume that this current limitation doesn't involve the EOSM's SD card controller bottleneck, because the EOSM can obviously record full-HD+ resolutions at higher bit depths with crop modes.  So, there might be a way to get raw and "near-full-HD" without a crop.

    I don't think they've been able to work out how to get higher resolutions than 720 vertical pixels to work properly when using the full aps-c sensor, due to the way the EOS M is designed, although they were trying find a way around that and they started having some success... but the video files so far resulted in a lot of corrupt frames. Here's the discussion about it: https://www.magiclantern.fm/forum/index.php?topic=16608.0  

    On 22/03/2018 at 6:31 PM, byuri734 said:

    MLV App reads the files with AWB as 6000k always. It is strange that it can read manual white balance properly. Do you know any app that can convert eos m files and read AWB properly? Also: the MLV app cannot convert to cinema dng in my mac (high sierra), only ProRes 4444. Do you know anything about this bug?

    Perhaps MLVFS might be able to convert the files and read AWB properly? I believe it should now be able to work with lossless mlv files, however I don't know where to get the latest version of the program! With MLV App on Windows I can convert the MLVs to cdng without any issues (with the option to export uncompressed or lossless). Maybe try a previous build of the program to see if it works?

  20. 11 hours ago, tupp said:

    I thought that the 3x crop is equivalent to super16 while 5x is equivalent to super8.

    I also was under the impression that "movie crop mode" could be super16 in size.

    The two 1x1 crop modes I mentioned in my post above are the only ones available on the EOS M. There are no other crop mode. The 5x zoom mode or 3x crop (movie crop mode) are actually misleading labels, since they both do exactly the same thing (both record in 1x1 sensor crop mode - i.e. with 1:1 pixel interpolation). There's no difference between them apart from the max resolution you're allowed to record at. In fact those names only relate to how liveview previews the image for you. 

    I think part of the confusion in crop numbers comes from the fact that the magic lantern menu always states crop factor in relation to 35mm full frame (i.e. same sensor size as Canon 5D), no matter which camera.... 

    On the other hand, the "5x zoom mode" (a label that comes from the Canon EOS ecosystem) is in relation to the sensor size of that particular camera (in this case, the EOS M has an 1.6x crop aps-c sensor). So the real liveview crop factor when using 5x zoom mode on EOS M is actually 5 x 1.6 = 8x zoom, which is why liveview looks so zoomed in when selecting this mode. But as mentioned above, that's just the preview and it doesn't relate to what's being recorded.

    Do RJ do a focal reducer for the EOS M mount directly? I'd definitely be interested in getting one.

  21. 5 minutes ago, tupp said:

    Thanks for the confirmation on the 3x crop.  I wonder what resolutions are available at that crop and whether or not I would have to deal with focus pixels.

    There are two options when filming in crop mode (also called 1x1 crop mode to avoid confusion): 

    1) There's "movie crop mode" (selectable from the magic lantern menu), which I keep referring to in my previous posts on this thread (see my "Destination Docklands" video on previous page for a demonstration of this mode). The max res is 1800x1024. There are no focus pixels if you shoot in 10 or 12 bit lossless raw.  This is my favourite mode as it gives you pretty much the proper framing in liveview with a realtime preview, and the record times are generally reasonable at that resolution.

    2) There's 5x zoom mode (selectable by pressing zoom twice on Canon's liveview touchscreen). This allows you to shoot at a higher max resolution of 2520x1080. In 10 bit lossless raw you get around 3 seconds of record time at this resolution, so it's not so convenient for most uses. Also liveview is zoomed in a fair amount, so the framing isn't right - though at least it's realtime.

     @Matt Kieley mentions there's a 3x crop + the 1.6x crop (from the aps-c sensor). That's correct and adds up to a 4.8x crop in comparison to 35mm full frame (i.e. 3 x 1.6 = 4.8). That applies to both crop modes mentioned above, but the exact crop factor will actually depend on the resolution you're shooting at, because 1x1 crop mode uses 1x1 pixel interpolation (there is no pixel binning). With movie crop mode at 1800x1024 resolution, the crop from 35mm full frame is 4.66x. With 5x zoom mode at 2520x1080 the crop is 3.33x 

    14 hours ago, tupp said:

    am fairly sure that there is a 3x crop mode in Magic Lantern

    I've just checked and there is indeed a 3x3 "crop mode". This is completely different to the 1x1 crop modes mentioned above! The "3x3" refers to the fact that the camera is doing 3x3 pixel binning.

    3x3 crop mode allows you to shoot with the whole aps-c sensor width. To activate, you have to enable crop_rec module under the modules menu (using the experimental firmware). In the Canon menu you need to switch to 720p 50/60 fps recording. Then you can activate it in the magic lantern menu by selecting "crop mode".

    However, the video quality isn't very good. The difference between this 3x3 mode and the regular full aps-c recording mode (which apparently uses 3x5 pixel binning) seems marginal. I think there's slightly less moire. The max resolution is 1736x688 which gives you a 2.5:1 aspect ratio. The focus dots do make a comeback, but they can be removed with MLVapp. 

  22. On 10/3/2018 at 8:38 PM, tupp said:

    Can you post your Fotodiox contact info?  I would like to "second" your proposal for such an adapter.

    I posted a comment on one of their youtube videos where they demonstrate the adapter: https://www.youtube.com/watch?v=GPseT8Ok3EA&lc=

     

    On 10/3/2018 at 8:38 PM, tupp said:

    By the way, much of this thread involves shooting with a "Super-8m" crop on the EOSM.  I would like to enjoy the same HD resolution and raw benefits, but shoot with a Super-16 crop.  Would that be the equivalent of the 3x crop?  If so, can I shoot that crop on the EOSM with full HD, raw, 24p at 10-bit?

    I think the only way to get close to a 3x crop (which is approx Super 16 size) is to increase the horizontal resolution to 2.5k (using 5x zoom mode). However at that resolution you only get about 3 seconds record time, and the vertical res is limited to 1080. 

    The resolution I like to use with movie crop mode (1800x1024) gives you 4.66x crop which is a bit larger than super 8. It's closer to 1/1.7", same as the Pentax Q-S1 sensor.

    I actually emailed the metabones sales team last week about their plans to make a speed booster for the EOS M mount (since it would be useful for the Canon M50 too), and they say they plan to do it but can't provide further info at this stage. If they do make it, that would be one way of getting super 16mm field of view on the EOS M!

    On 11/3/2018 at 2:55 PM, byuri734 said:

    I got it to work and now I have the AWB working in camera and the Mac's MLV App reads it properly. How do you deal with exposure, any tips? Especially, how do you set zebras, 90%, 80%, etc..

    Nice to hear MLV App reads the white balance properly for you. Did you change any settings in the program? On the PC version it always defaults to 6000k.

    With exposure I have the zebras set to LumaFast, over 99% which I think is the default - apart from that I judge exposure by eye. As long as I'm not blowing out highlights with this zebra setting, the image seems fine. In the Destination Docklands video I posted above, you can see instances of blown out highlights with harsh clipping where I shoot directly at the sun or backlit clouds (visible on the cover image). I could see the zebras in liveview when shooting that shot but it was impossible to avoid. 

×
×
  • Create New...