Jump to content

Alpicat

Members
  • Posts

    97
  • Joined

  • Last visited

Posts posted by Alpicat

  1. 3 minutes ago, matthere said:

    @Alpicat Had the invite, but had other stuff on.. Have BM said when we might get our cameras?

    They haven't said anything unfortunately, they just showed the films. One person who ordered from cvp really early on told me he hasn't had any updates from them at all, which sounds a bit worrying. I personally haven't ordered yet, will only get it in the new year if I need it for work. 

  2. 2 hours ago, mercer said:

    Don’t you just have to unscrew the back guard/fin and remove it?

    I have the ef-s 17-55mm and you can just pull the back part off with your fingers, no need to unscrew anything. You do need to use some force but it seems safe to do - I think it's different to newer ef-s lenses where you do have to use a hacksaw. With that part removed, it should be fine to use on a speedbooster. The focus ring on this lens has soft stops, it's nice to use - with a slightly longer focus throw than the Tamron or Sigma equivalents. The stabilisation is only 3 stops but it's very smooth for video - it doesn't jump around abruptly like some Tamron lenses or Lumix lenses seem to do when panning. The build quality isn't that great unfortunately, it feels a bit fragile considering how much it weighs.

  3. I'd never buy this camera but for certain small jobs where I'm shooting myself and don't have a camera team I may consider renting it for its auto focus capabilities, should be cheap enough to rent hopefully. I'm wondering if the DPAF will be as effective with continuous video autofocus when using adapted EF or EF-S lenses as it will be with native RF lenses - will be interesting to test this out. 

    @hijodeibn it could be a while before we see a speedbooster, judging by how long it's taking Metabones and Viltrox to release one for EF-M mount, which both companies have been planning to make for a really long time. It just takes time to design and manufacture stuff. Hopefully the EOS R will generate more interest and they'll be quicker! Although again, I'm wondering how effective video autofocus will be with an adapter.

  4. @Brian Williams with MLVFS I think there might be an option to remove focus pixels in the same way that MLV App does (with a focus pixel map) but don't remember what the option was called. Chroma smoothing supposedly does degrade image quality slightly - but probably not noticeable most of the time.

    @mercer I've tried converting mlvs to prores (using the LogC curve) on MLV App, and I agree the results are great! Interestingly with the EOS M I found that when I exported some shots to prores, it got rid of aliaising and moire, which remained an issue when exporting to cdng... but in some other cases where there was a different type of aliaising it didn't make a difference and possibly the cdngs were better!

    There haven't been updates for the bitrate hack that I know of. We were extremely lucky that the magic lantern forum members did so much work with the EOS M these last few months. It's gone a bit quiet now and will probably be a while before we see any new updates for that camera, but that's ok. Now I'm just waiting for Viltrox to release their EF-M speedbooster so I can turn my EOS M into a 'full-frame' camera using the mv1080p mode! 

    I think the 70D also benefits from SD card overclocking but don't know if that camera can record lossless raw yet.

     

  5. @Brian Williams I'm using Windows and was also getting corrupt files with MLVFS. I don't think it's compatible with lossless raw files, but need to check if there's an updated version. The patterns you were seeing are the focus pixels? 

    MLV App works fine for me and it gets rid of focus pixels automatically without using chroma smoothing, but would be interesting to see if MLVFS produces different results at all with the exported DNGs (in terms of colour and image quality). 

  6. @tupp @youshouldtry11  thanks for this, had never heard of the cameflex mount!

    Shooting in raw is stable even with the SD overclock hack - I rarely had problems with corrupt footage, unless it's an extremely experimental build. The only issue with the SD hack is activating it, which can be a bit risky, but after activation, the camera is fine to use as normal.

    If you want to avoid the SD card hack and want to use s8 or s16 lenses, just download the latest 4k lossless experimental build from the magic lantern website, select "movie crop mode" in 10 or 12 bit lossless raw up to 1800x1030 resolution (4.66x crop). That mode is nice to use as it gives you a properly framed liveview, and should give you fairly continuous recording times.  Of course you can also select lower resolutions whilst in movie crop mode if you want a bigger crop or a different aspect ratio. 

     

  7. @youshouldtry11 c-mount is a screw thread type mount and I don't see any screw here. I'm unsure what makes you think the above is c-mount, to me it looks like it doesn't have a mount - perhaps it's been physically removed. I sold my schneider lens last month as I wasn't using it, however below are some photos of it with c-mount:

    https://thumbs.worthpoint.com/zoom/images3/1/0915/23/schneider-kreuznach-optivaron-66mm-1_1_ba20e52d51029e2677ec30cad36cabc4.jpg

    https://www.picclickimg.com/d/w1600/pict/263721207841_/Schneider-Kreuznach-Beaulieu-Optivaron-18-6-66-C-Mount-Zoom.jpg

  8. @youshouldtry11 The lens is pretty small, but heavy as it's metal - feels front heavy on the eos m. It's a c-mount lens -I think this is the adapter that works best to make it work parfocally, though haven't personally tried it: https://fotodioxpro.com/products/c-eosm   

    Don't know what mount the lens in your photo has - it doesn't look like it has any mount at all, maybe it was unscrewed or removed, or it's a custom built one?

  9. @youshouldtry11 if you plan to use super 8 lenses, you're best off using "movie crop mode" and cropping to 4:3 aspect ratio in post to get rid of most of the vignetting. Movie crop mode in h.264 (1920x1080 resolution) is similar or same to the field of view you get with movie crop mode in raw (1080x1030 resolution). This is a 4.66x crop from full frame - which is larger than super 8, but cropping to 4:3 aspect ratio will get rid of most of the vignetting.  Below are tests I did with the eos m and schneider 6-66mm f1.8 which I had posted here a few pages back. I shot this in raw at 1800x1024 in movie crop mode. 

    For this lens I think the fotodiox adapter is the best one that will give you parfocal lens performance, from what I heard. It's tough to find an adapter that works as they all seem to be really different.

    If you want to use super 16mm lenses and shoot raw, there's also the option of using 5x zoom mode with a max stable resolution of 2520x1080 (3.33x crop from full frame), this is close to 16mm (rather than s16). However, it isn't possible to shoot this resolution with regular h.264 video. 

     

     

  10. Thanks @tupp. I guess this update makes the title of this thread slightly out of date now!

    Here's the build I used: https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Jul03.EOSM202_mv1080p.zip   With this build you're stuck with shooting full sensor only (3x3 pixel binning), you can't switch to 5x zoom mode. They may have partially fixed that in the newest build but unsure if you can then access the full sensor height, I'll need to test. See here: https://www.magiclantern.fm/forum/index.php?topic=19300.msg204564#msg204564  

    I shot that footage at iso 100 and iso 400, f3.5 and above. I later noticed that if I export to prores on MLVapp I get less noise in the shadows that exporting to cdng (which can look really excessive if you push up the shadows). However I don't know if I tested this fairly and will have to experiment further. The above video is cdng.

    Right now the main issue is liveview preview is streched vertically 1.6x (preview looks like you have an anamorphic lens attached) and you can only see the top half of the image. It's still usable though and half-pressing the shutter gives you a low fps / pixelated preview of the whole frame.

    The moire/aliaising can get fairly bad depending on what you're filming, and can become very obvious if cropping in on an image. I guess it's now the same amount as you get with all the other aps-c Canon DSLRs, or it's similar to the bmpcc. Exporting to prores rather than cdng on mlvapp can sometimes reduce the amount of moire - I need to test this further though.

  11. @mercer thanks! I do need to make a short film and should watch Rear Window, can't believe I haven't seen that yet! 

    Yes I'm using Juan Melara's method on resolve, at least for clips where any highlights are blown out otherwise it's not needed. It's the easiest way to get highlight rolloff to look ok - I have it all set up on resolve so it only takes a click and minor exposure / colour balance adjustments after that. 

  12. Thanks! It will certainly be slightly similar to the 5D once the speed booster is available! At the moment, the resolutions I've mentioned above require the use of highly experimental builds that aren't even available in the experimental downloads page yet. It's a bit of a hassle getting the different modes to run, however progress is being made pretty quickly. 

  13. Here's my first quick test with mv1080 full sensor recording on the eos m (1736x1120), no crop and continuous recording in 14 bit lossless raw. I'm happy with the image quality and moire isn't too bad. I think youtube softens the image slightly, so have uploaded at 1440p which hopefully looks a bit better:

     

    @webrunner5 In crop mode at 2520x1080 or 2520x1386 the ef-m 15-45mm lens is 50-150mm full frame equivalent (3.33x crop). With a 0.71x speed booster that will be a 2.36x crop - so using an ef-s 10-18mm (modified to fit speed booster), that would result in 24-43mm full frame equivalent. The ef-m 15-45mm won't work with the speed booster.

    The river thames video I shot at 2224x1200, which has a crop factor of 3.75x, so the 15-45mm lens was 56-170mm equivalent there. The crop factor changes depending the resolution selected - values can be calculated here: http://rawcalculator.bitballoon.com/calculator_desktop

  14. Have tested it and it's working fully. The preview is stretched vertically 1.6x for now - as if there were an anamorphic lens attached, but other than that it's fine. I never thought they would manage to do this! 

    Also, seperately, here's the most extensive test I've done so far with the new crop rec 2.5k mode (max 2520x1386) on the eos m. I recorded at 2224x1200 to get usable record times of around 10 - 20 seconds per clip. It was a very warm day so the camera got pretty hot!

     

  15. On 6/30/2018 at 5:26 PM, mercer said:

    Does the eos-m have anamorphic mode in ML? If so, I thought that could be fun to mess around with.

    A lot of progress has been made on the EOS M in the last two days and it looks like they've been able to make the camera shoot in mv1080 mode using the full aps-c sensor (no crop) for the first time ever (as opposed to the mv720 mode that the camera was always stuck in). This means that the EOS M will now be as capable as the other digic 5 cameras.... so what I said before about anamorphic shooting changes completely - this will now be a great camera for anamorphic as it can record max 1736x1120 (3:2 aspect ratio) which I think uses the whole sensor height and width. Will do my first test soon - liveview preview isn't working fully yet though. Can't wait for the Viltrox speed booster to be released soon and shoot full frame raw video with this £100 camera!

    Here's the forum post and first footage: https://www.magiclantern.fm/forum/index.php?topic=9741.msg203530#msg203530

     

  16. 2 hours ago, mercer said:

    when I update a build, do I just load a new build onto an SD card and then run the firmware update? Or do I have to bring it back to the regular Canon firmware and then do it?

    To update a build all you do is delete the ML folder, autoexec.bin file and ML-Setup.fir file from your SD card, and replace these deleted items with the new ML files that you've downloaded. You don't need to run any firmware update - that's only the case if you're using a new SD card which hasn't had Magic Lantern installed before. 

    If you're planning to shoot lossless raw using the experimental 4k crop rec build, it's worth using MLV App to convert the mlv files to cdng: https://ilia3101.github.io/MLV-App/   not all of the other programs are compatible with lossless compression.

  17. @mercer the MLV Lite module is nearly able to do all the things the regular raw module does (including sound recording), and it uses less processing power, so I think there's a discussion going on about getting rid of the regular raw module and making MLV Lite the standard one. There  isn't much difference between the two modules in terms of what they're like to use.

    The EOS M is only worth using in crop mode, and the current resolution options means it's not great at all for anamorphic filming. The max available resolution till very recently was 2520x1080 (2.33:1 aspect ratio). At this resolution recording is continuous at 10 bit lossless, and nearly continuous at 12 bit lossless. Crop is 3.33x from full frame (which will be 2.36x crop with the upcoming speed booster).

    Now it's also possible to shoot up to 2520x1384 (16:9) at 24fps. However when you increase the vertical resolution beyond 1080, the lowest bitrate setting you can select is 14 bit lossless, which limits record times to about 2 seconds only! However, as I'm sure you know with Magic Lantern you can select any resolution lower than the maximum and any aspect ratio you like, to get better record times. For example, with 2224x1200 in 14 bit lossless I currently get 10-15 seconds record time.

    The exciting news is that the SD card overclock hack is being developed even further to increase the clock frequency from 160mhz up to the UHS-I maximum of 208mhz. When (and if) that happens then 80mb/s write speed should be possible on the EOS M and other digic 5 cameras (as opposed to 55mb/s write speed that the current hack allows). This should enable continuous recording at 2520x1384.  

  18. 2 minutes ago, mercer said:

    @Alpicat looks good, I dig the music too. Have you thought about buying a 5D3?

    Thanks, glad you like it! I can't afford a new camera at the moment unfortunately - but that might change next year. The full frame look is really nice!

    For now I'm happy with the EOS M, I don't really need anything else. It's quite a capable camera - at 2.5k resolution I think I prefer its image quality slightly over the BMPCC I used to own. When Viltrox's speed booster comes out next month, it'll even be possible to shoot wide angle with EF lenses. 

    The 50D was really nice in crop mode even if liveview was only in greyscale (it could do 2000x1080 in 10 or 12 bit raw continuously). Unfortunately when shooting with the full sensor it was fairly weak - looking at footage now I realise just how much moire there is, and also at higher ISOs fixed pattern noise was bad. Its biggest issue was battery life which seemed even shorter than on the BMPCC - the EOS M battery goes on forever in comparison!

  19. @tupp very interesting videos, thanks for sharing! If it were simply possible to swap out the UHS-I SD card interface inside the EOS M for a UHS-II one, that would make higher resolution recording feasible. But I imagine the amount of coding required to make it work might make it very difficult. 

    In any case I doubt you'd be able to sell and make any money from a hardware hack like this - unless you get permission from Canon!

    I spoke to a Canon rep at the media production show in London recently where they were showing off their cinema EOS cameras, and he was aware of the EOS M 2.5k hack and seemed totally positive about it even saying he'd like to try it himself. I showed him the hack in operation. He also said he hoped that magic lantern would be available for the M50 one day! 

  20. 12 hours ago, PannySVHS said:

    @Alpicat, three of them ccd sensors even, yeah! global shutter included! Unfortunately only a few enthusiasts on this forum are interested in my thread above , which I find astonishing. I love this eos m super 8 thread though! Still, a bit disappointed. Well, no biggie. cheers :)

    It would be amazing to get the dvx100 hack working. It looks like they were connecting a laptop to the camera and running it from there? I just wouldn't have a clue how to do it!

    Here's 4k filming with the EOS M at 9fps (4096x2552), it's only possible to shoot 5 frames at a time though. At this resolution, the crop factor becomes 2x (micro four thirds). I don't think it'll ever be feasible to get this to work at 24fps. Even with the extended SD overclock hack writing at 80mb/s, it would only be possible to record a second or two, the data rate is just too high. Don't know if it would be possible to hack this camera with an external recorder and increase the write speed that way, but that's just too much work!

     

×
×
  • Create New...