Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Tullen

Pages: [1] 2 3
Camera-specific discussion / Re: Canon EOS M
« on: January 20, 2019, 05:30:12 PM »
Regarding motion blur. What shutter speed do you think is good? 1/125 or faster?

Camera-specific discussion / Re: Canon EOS M
« on: January 20, 2019, 04:16:48 PM »

Thanks for the help. Any recommendations for how to get proper exposure. Since the light falling on the moon will change as the shadow disappears.

Share Your Videos / Re: Lunar Eclipse
« on: January 20, 2019, 04:10:55 PM »
Any recommendations for capturing the super blood moon tomorrow morning?

I have a eos m, a 220mm F4.0 and a 135mm F2.8. 

Would love some recommendations for what lens to use and what crop mode to use. How to set proper exposure. Dual iso? Anything would help. Dont have that much experience with Magic Lantern yet, and almost none with shooting the moon. Unfortunately I only have one battery at the moment so that will be a problem to. Guess it will be around -10 outside.

Camera-specific discussion / Re: Canon EOS M
« on: January 20, 2019, 03:39:59 PM »

This development speed is insane and great. In current options, what would you recommend for capturing the super blood moon tomorrow morning? I have a 220mm F4.0 that I though I could use with the options with highest crop and best light handling. Or should I go for the 135mm F2.8? Dual iso I guess would be good too. Any suggestions for settings and workflow?

Camera-specific discussion / Re: Canon EOS M
« on: December 11, 2018, 11:02:17 PM »
is there any way to get the "framing" liveview work on an external display? whatever i choose for preview, it's showing "realtime" for hdmi external. by the way, i searched but i couldn't really get 1x3 crop mode, it shows at liveview and records very wide. i can provide footage does it need to be dng or are compressed formats okay? (i'm using mlv app on windows and i'm really grateful to both firmware and software developers.)

I'm also very interested in this. Anyone knows? Would be great to be able to use the monitor and get proper framing. Another option if it works would be to output full frame (without 5x) and have a frammarking on. Even though a lot of the display would not be in use its not as big of an issue on a 7" or 9" monitor.

Any ideas?

Camera-specific discussion / Re: Canon EOS M
« on: December 11, 2018, 12:32:54 AM »

When using your, the recording sometimes shuts down due to to slow memory write speed. I'm using a Sandisk Extreme Pro 128GB.

- Installed and played around a bit with Magic Lantern.
- Set canon camera to manual film mode. Set the camera to 1080p 24 fps and Pal in canon menu.
- Did a low level format of the memory card in camera.
- Removed the old ML folder from the memory card and extracted the ML folder and the .DS Store, autoexec.bin and ML-SETUP.FIR to the root of the memory card from the (ignoring the MACOSX folder). Safe eject card from memory reader.
- Went into manual fotomode and updated the firmware. When prompted restarted the camera. Set the camera to film mode (manual).
- Opened magic lantern and loaded the crop_rec, lua, mlv_lite, mlv_snd and sd_uhs modules. Restart.
- Set  sd_uhs to autorun. Restart
- Go to movie tab and enable Crop Mode 2.5k 2520x1304 and set to 12 bit in Crop Mode submenu. Set FPS override to 23.976 and optimized for exact fps. Restart
- Go to movie tab and enable RAW, set bit depth to 12 and resolution to 2560 (which sets it to 2520x1308).

If I then try to record, the recording shuts down immediately.

If I put the RAW to 12 bit lossless it can record to up to a minute before stopping. Also, if I set it to 12 bit lossless the display becomes much darker. Gets brighter when I half-press shutter button.

So maybe the sd_uhs is not enough to record in 12 bit or 12 bit lossless at this resolution? If I set the Crop Mode to 10 bit and RAW to 10 bit it also shuts down after a few frames.
Setting the Crop Mode to 10 bit and the RAW to 11...8 bit lossless it seems to record continuously, but then the image is scrambled and of course  I'm still stuck with the dark display.

I'm sure I am doing something wrong, or maybe the dark display thing is a know issue, but I did not find anything when searching this tread so maybe you or others have some tips?

Cheers and thanks for all the amazing work.

EDIT: Seems none of the clips I took work when checking in mlvapp :(. So Im probably in much more trouble than I thought about just the dark image and 10 bit. How did you go about it alpicat?

Camera-specific discussion / Re: Canon EOS M
« on: December 09, 2018, 05:42:09 PM »
I just got the same results when starting the camera and shutting it down before 2.5k script had finished running. Camera stuck at sensor cleaning, and had to pull battery. But cant reproduce it.

Share Your Videos / Re: EOS M - Full frame raw with Viltrox speed booster
« on: December 07, 2018, 11:56:56 PM »
Does it accept EF-S lenses?

Sent from my iPhone using Tapatalk

Unfortunately not Canon ef-s (maybe those are the only ones called that?). Those lenses protrude and will hit the glas. Other lenses for aps work, like my Tokina, but sadly some firmware issues with the Tamron. But yes, you will get vignetting. I can take some pictures to illustrate.

Share Your Videos / Re: EOS M - Full frame raw with Viltrox speed booster
« on: December 06, 2018, 07:02:26 PM »
I just bought what I think is the complete EOS-M setup (minus some power stuff).

The adapter mentioned here: Viltrox EF-EOS M2
VILTROX Canon EF-EOS M AF adapter mount (normal without focal reducer)

Tamron af 17-50mm f2,8 sp xr di-ii ld aspherical (if)
Tokina AT-X PRO 11-16mm 1:2.8 SD (IF) DX

VILTROX DC-70 HD 7 inch Professional ­High-definition Monitor
VILTROX L116T Led light
Viltrox VL-200 led light

G6 Plus Fyfeiyutech Gimblal.
2 x Sandisk Extreme Pro 128GB

Everything, plus the Eos m with kit lens and bag/flash, for 1430 Euros total. Exited to see what I can do with this.

Unfortunately, even with the newest firmware the Viltrox EF-EOS M2 adapter does not seem to work with the Tamron af 17-50mm.
Also, havent tested the gimbal with adapter and the lenses. Lets see if it works. Its rated for 800g but with adapter and and lenses it will probably weigh around 1200g.

Camera-specific discussion / Re: Canon EOS M
« on: November 05, 2018, 10:41:00 AM »
How much does that lens cover? would it cover 2.5k wide shot you think?

Hello all - I’m a longtime lurker, seldom a poster. I’ve been messing with using my EOSM as a Digital Super 8 camera and I’m pretty happy with the results.

For the video below I used the following setup.

6mm f/1.2 Pentax TV lens (paper shim between lens and C mount-EOSM adapter, for infinity focus)
Tiffen Digital Diffusion 5 filter (reduces moire artefacts)
EOSM with latest ML build
18fps override (exact)
5x zoom
12bit lossless RAW
4:3 aspect
1440 x 1080

This video has effects applied - FilmConvert’s Super 8 grain; FCPX native “aged film” effect applied very sparingly for jitter and a little dust; a telecine’d Super 8 black frame (keyed over footage). If there is interest, I can post the ungraded footage.

Camera-specific discussion / Re: Canon EOS M
« on: October 26, 2018, 12:23:53 PM »
Just interested in the different crop factors for current recording capabilities?

Reverse Engineering / Re: UHS-I / SD cards investigation
« on: May 20, 2018, 12:49:36 AM »
Well, my question was actually about APSC-sensor based DSLRs.  Can a speed booster turn them into full-frame cameras when operating in Life View with full-frame lenses?  Do such speed boosters exist and if yes, does anyone on this forum have any experience with them?

Actually I already made a thread about it. I have a speedboaster, an extra 50D and some ideas about how it can be done, just haven't got to it yet.

Please don't quote out of context. Please link to quotes you are using.

This quote was an answer to reply #49 in this thread and reply #49 links to outdated User Guide found under -> Top of page -> User Guide -> User Guide.

There was no link to Redrock's "User Guide" post.

I apologize for misrepresenting your quote. But then I don't understand. Why did the person ask about another guide in a guide thread named "User Guide thread for the latest nightlies (Help Needed)"? And why would you give such reply in that very thread? Was it just so that it was/is not complete?

EDIT: Nevermind, I realize that you now are mainly focused on choice nr 1 above. I still think there are presentation issues to be addressed, but everything in its own time. Guess I should create a new thread for my specific purpose.

I will just reply myself and add some more questions.

How up to date and usable is the The sticky to end all stickies?
How up to date and usable is the German guide which also have been refereed to in this thread?
How up to date and usable is Redrocks guide since Walter writes "Linked User Guide covers outdated "stable" v2.3. There is no user guide for nightly builds available." in its last post from 2017?
Did I miss any relevant threads/sources?

I am currently in the process of documenting my experience as a first time user coming to the site (which in some ways are not far from the truth). This experience is based on two goals.

1. I have a Canon camera (where there already is ML development) and I want to find out what I can do with it, how to do that, what functions are yet to be implemented for my model and how I can help to develop them (as well as help ML community in general).

2. I heard about Magic Lantern and want to buy a Canon camera in order to use it. I am looking for the different functions (including understanding what they are and if I need/want them) supported by the different models (including resolution, bit depth support etc.) Since I do not need a production camera instantly I am also interested in what functions are possible coming to the different cameras and what would be required for that to happen.

With these two goals I am trying to build a user trajectory and understand how we might make it easier for the user. This of course needs to be coupled with the practical part of keeping development moving while updating information in an easy manner.

Is there more relevant material other than Redrocks guide and the pages with features, builds etc

Camera-specific discussion / Re: Canon 100D / SL1
« on: May 15, 2018, 09:18:33 PM »
Support for RT flash enhancements (5 groups, ...)
Price: Below 200€ in mint condition

Size (if your hands are not that small and especially with big/heavy lenses)
Buttons missing, no dial on back -> ergonomics ...
Battery capacity is a bad joke
AF not state-of-the-art with non-STM lenses

YMMV. I have a little problem seeing it as upgrade. More of a replacement: If you're looking for a smaller cam and don't mind changing/recharging batteries a lot ...

Thank you. What about video capability and features?  2520x1080 resolution at 12 bit lossless and audio seems better than the 50D right? Any other technical specs worth considering?

Camera-specific discussion / Re: Canon 100D / SL1
« on: May 15, 2018, 07:32:17 PM »
Would you say that the 100D is a good upgrade from the 50D? Pros and cons?


I was giving this a lot of thought for around a year ago, unfortunately I did not write it down but I still remember some of the main issues I was contemplating. My interest in the topic i still here and I would like to contribute if I can.

First of all (notwithstanding the fact that I do not understand all technical references) it seems that there are many approaches taken in this thread. Both thoughts about technical implementation and artistic presentation. I would suggest that the first step is to define what functions we are trying to fulfill. 

1- Is it just a database of some sort that can be filled with up to date guides for the different functions (including specifics for different cameras?)?
2- Is it an easy to understand overview and introduction to different functions for new and old users (that could of course be feed/linked to the mentioned database)?
3- Is it a greater tool that does not only make it easy to get an overview of what functions are available through Magic Lantern and how to use them on different cameras, but also if and how a newcomer could help develop the functions for supported and unsupported cameras?

Other functions to be specified is how easy it should be by whom to update the information, how easy it should be to see if the information is up to date and how much development is needed before a camera can be expected to have support implemented? I understand the last one is not an exact science, but could be simplified.

Different choices give different directions for implementation. For example, if choice 1 or 2 is chosen then it makes sense to filter the information by model, but if 3 is chosen you want people to see and be engaged with the functions that are currently not supported by their camera model.  EDIT! I realized that this is not necessary the case, will expand in next post.

I will try to remember the system (presentation wise) I had in mind when I was thinking about this before and come back with a suggestion. Feel free to suggest other functions that you think needs to be considered and or comment on the text above.


Sounds good , In the mean time I would suggest familiarize yourself with this thread , 10-12bit thread and of course the  iso-research source code. (That's where I started from)
You will need a developing environment -- I use a VM (VirtualBox) on Window7 Pro with a preconfigured magic lantern clone of Ubuntu ready to compile ML . Download links for clone of Ubuntu  here
You can run the VM under Mac or Windows just get the correct version for your OS , if you feel adventurous you can setup your own environment @dfort has make some tutorial here and here
You need to be very comfortable with compiling , merging , update source with "HG" etc. ..... I work with a VM because it's faster & easier to get up and running in less then 30 mins .

Thanks for the recommendations, hopefully will make me helpful a bit faster.

Ok --So I decided to forge ahead after urging from some forum members and help from a1ex.
So to get up to speed read the posts below to those members who are following the development , should help explain where I am in all this.
Basically I trying to get back to the 3584x1068 raw buffer I had working here
Stay tuned  :)

Great to hear. As I said, I will be helping as much as I can from September onward.

I really want to get this going, especially for the 50D. As soon as I have fished my thesis I hope to be able to help. Even would like to start a Magic Lantern club in Stockholm. That would be in September though. Please dont give up. I am sure that more people would like to help. I am willing to put in time for this for sure.

Raw Video / Re: Yet Another RAW Video Calculator
« on: May 11, 2017, 01:06:25 PM »
How about including lossless?

Raw Video Postprocessing / Re: ML Samplefiles
« on: January 16, 2017, 01:09:49 PM »
Hi. I will try to provide some 50d footage the coming days.

Raw Video / Re: Raw Recording using an Android Tablet
« on: December 14, 2016, 03:59:57 PM »
Is there another way to get ahold of the developer of DSLR controller because he's not responding to any of my PM's.

It worked fine on iPad Mini Retina with ios 7 and it hasn't been updated for ios 8 as of yet. I can't downgrade back to ios 7 without A SAVED SHSH blob. Oops!

Shame on me I know!

Hi DeafEyeJedi.
Sorry if I bring up an old thread. Did you ever get a hold of him? He is actively posting on the DSLR controller thread at XDA

Also, do you know anything about the possibility of using it during Raw recording as mentioned by 1%?


Hope this thread is still alive. In thread referenced by DFM, ( 1% claims that it is possible to record raw during USB output on 6D and 50D when bypassing (or blocking) ML screen resizing. However it is unclear whether this has to be done in the code or if it is something that can be done in existing ML versions. It would be exellent if someone could spread some light on this question.

Great response. I think there are some (not many) that would not mind learning enough to actually be able to help. Since there are relatively few that are working at the moment (not sure how many) I guess every new developer is greatly appreciated (although it has to be weighted against the time it takes from current developers to help). Still busy with my studies, but would be great to make it easier for people to get going. I know there are other threads also giving advice on what you can do to help like; and maybe (seems it has not been active for a long time).

How much time would you say is necessary to put down in order to learn from scratch dimilligan? I would imagine at least a couple of hundreds of hours.

Pages: [1] 2 3