Menu

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.

Show posts Menu

Messages - cameron12x

#1
Tragic Lantern / Re: Tragic Lantern for EOS M
August 22, 2013, 02:30:44 PM
Quote from: Rush on August 22, 2013, 11:24:22 AM
OH, It is not available for EOS M yet...


WOW!  It would be nice to have all of those FOCUS functions available for the EOS-M!

Praying for them!  :)
#2
Tragic Lantern / Re: Tragic Lantern for EOS M
August 22, 2013, 12:38:37 AM
Quote from: Rush on August 21, 2013, 11:50:28 PM
check Focus tab. with most electronic lenses - it automatically calculates DOF and Hyperfocal distance, based on current lens settings and will report if you are in hyperfocal distance
Where is the "focus" tab?  I don't see it with my version of ML.  Thanks!
#3
Tragic Lantern / Re: Tragic Lantern for EOS M
August 21, 2013, 11:13:46 PM
Quote from: haomuch on August 21, 2013, 10:59:15 PM
They can't even provide a usable magic room focus function currently. So I think you may need to wait for a very long time.

What is a "magic room focus function?"  And how is that less difficult than an automatic hyperfocal distance focuser?  Just curious.
#4
Has any more thought been given to this? 

I think that all of us have had shooting situations where we wanted everything in focus from infinity to the hyperfocal distance indicated by the lens focal length and aperture setting.  It would be a great time saver!
#5
Tragic Lantern / Re: Tragic Lantern for EOS M
August 21, 2013, 08:57:36 PM
Does ML have a "hyperfocal" focus mode, where you simply compose the photo and the camera calculates what will be in focus (from infinity distance to closest distance in focus) using the selected aperture?

Say I select f/8 and want everything to be in focus from infinity to the closest point that f/8 will allow (hyperfocal distance).  Can ML do that automatically?  It would be great if it could!  Thanks for all of the great work!
#6
Tragic Lantern / Re: Tragic Lantern for EOS M
August 17, 2013, 02:13:57 PM
Quote from: thegunshow101 on August 17, 2013, 08:39:46 AM
Sorry but converting the RAW file direct to Cineform is missing the most critical point of color correcting directly from the RAW source....  This is not the correct way.

Establishing the correct workflow is useful for experienced videographers and beginners like me.

I'm glad everyone is taking a stab at documenting what they do. It's a real help, and I'm sure the workflow will be refined over time.

Thanks, and keep it up, please!
#7
Tragic Lantern / Re: Tragic Lantern for EOS M
August 12, 2013, 12:23:55 AM
Quote from: gary2013 on August 11, 2013, 10:16:28 PM
+1 on fixing the installer. It's a real PIA always having to to install thru update firmware each time. :-) I have also asked a few easy questions here and no one ever answered. Is there another way to get into ML menus besides a two finger swipe? I only have one finger from a car accident and its difficult for me always needing to use two toes and leave a shoe off all the time. LOL J/K, but I would rather have the Menu button open ML menus. And, how do I exit ML menus? I have been waiting until it exits on its own. I would rather the menu stays open and then we hit some button to close the menus. The menus keep shutting off on me while I try to read and learn things within them. Then I have to swipe the display again with two toes to continue with where I left off. :-)

Gary

+1000!  Amen.
#8
Tragic Lantern / Re: Tragic Lantern for EOS M
August 11, 2013, 05:19:08 AM
Quote from: cameron12x on August 10, 2013, 01:35:58 PM
Hmm...  interesting.  What do those folders/files do?  What do they have to do with "crop marks?"  Why __MACOSX?

Ok, I've created the CROPMKS folder under ML and placed a couple of cropmark (bmp) files there from the library.

I've selected one from the ML menu and have enabled cropmarks, but they don't show up in either video record mode or standard still image mode.  What might I be doing wrong?  Thanks!
#9
Tragic Lantern / Re: Tragic Lantern for EOS M
August 10, 2013, 01:35:58 PM
Quote from: freshbreath on August 10, 2013, 06:28:19 AM
In your case it seems to be looking for folders/files found in __MACOSX directory of the Alpha zip. Copy that over to the root directory of your SD card as well.

Hmm...  interesting.  What do those folders/files do?  What do they have to do with "crop marks?"  Why __MACOSX?
#10
Tragic Lantern / Re: Tragic Lantern for EOS M
August 10, 2013, 06:14:09 AM
Quote from: 1% on August 10, 2013, 05:09:23 AM
No boot flag, fir

if you had 1.06 make sure the card itself is bootable too (ie the EOSCARD step) for linux just run it in wine.

If you had 2.0.2 and no ML you need the fir file + ml folder/modules/sym

For the utility, it just may not work. The camera has to create jpegs in parallel to send over USB. Will have to log it and see.

I think this is functionality that a LOT of people will want:  remote shooting.

Separate topic now.  I have the new EOS-M and it came with the 2.0.2 firmware installed.  I've gone through what I understand to be the ML installation process and I have these folders and files:

DCIM -- for photos
MISC -- currently empty
ML -- subfolders: DATA (contains FONTS.DAT file), MODULES (contains modules), SETTINGS (contains MAGIC.CFG file)
autoexec.bin  (381K)
UpDaterM.fir  (393K)

My MODULES sub-folder contains the following files:

EOSM_202.sym (34K)
ETTR.CFG (1K)
ettr.mo (17K)
file_man.mo (14K)
pic_view.mo (5K)
RAW_REC.CFG (1K)
raw_rec.mo (33K)

Are those the correct files for the MODULES sub-folder?  Do I have all of the needed files?

Also, what about a SYM sub-folder?  Is one needed?  If so, does it go under the MODULES folder?  And if so, what should it contain (and where to get the files)?

Note: when flashing the firmware (I have to do this every time I start the camera), I get the following message:

"ML/CROPMKS dir is missing"  What is this all about and how do I fix it?

*** Many thanks in advance for help with all of this ! ***
#11
Tragic Lantern / Re: Tragic Lantern for EOS M
August 09, 2013, 04:58:21 PM
Quote from: 1% on August 09, 2013, 04:30:33 PM
Signed version = fir
Normal version = autoexec.bin


If you're having to run the fir every time and got EOSM with 2.02 pre-installed then you're stuck with the signed version for now.

My camera came with 2.0.2 pre-installed.

I have both of those files in my root folder.   Is that correct?

What does the signed version do differently from the autoexec.bin version?
#12
Tragic Lantern / Re: Tragic Lantern for EOS M
August 09, 2013, 03:50:15 PM
What is the "signed version" and how does that affect the intervalometer?
#13
Tragic Lantern / Re: Tragic Lantern for EOS M
August 09, 2013, 03:13:06 PM
@mixer2:  Thanks for the baby steps.  I see how to do that now.

But how do I get the sequence to actually start?  I tried setting a test run of 4 images, and it looked like the intervalometer counted down and went through the process, but when I try to review images it says no images found?
#14
Tragic Lantern / Re: Tragic Lantern for EOS M
August 09, 2013, 02:07:13 PM
I can get to the sub-menu, no problem.  I don't see how to change the setting from 10s, once there, however.
#15
Tragic Lantern / Re: Tragic Lantern for EOS M
August 09, 2013, 01:18:39 PM
@mixer2:  Where are the instructions for the intervalometer?  It likes 10s is the only option?  I would think it would be more flexible than that.

Also, I get error loading symbol files, despite having the EOS_202.sym file in the MODULES folder.  Thanks!
#16
Tragic Lantern / Re: Tragic Lantern for EOS M
August 09, 2013, 07:48:02 AM
Has anyone been able to use the intervalometer functionality on the EOS-M yet?

If so, are there any tricks?  Thanks!
#17
Tragic Lantern / Re: Tragic Lantern for EOS M
August 04, 2013, 05:14:40 PM
Quote from: mixer2 on August 04, 2013, 04:51:54 PM
ah, ok nice! thx

This is a "no-installer" version, right?  How do we "install" it on our cameras?
#18
Tragic Lantern / Re: Tragic Lantern for EOS M
August 04, 2013, 04:49:30 PM
Quote from: 1% on August 04, 2013, 04:47:14 PM
Yep, just let me make sure the video stuff works.
Awesome!  Does that mean we're within a few days of the first "alpha" release for the firmware 2.0.2 update?

Keep up the great work!
#19
Tragic Lantern / Re: Tragic Lantern for EOS M
July 31, 2013, 09:43:19 PM
Quote from: 1% on July 31, 2013, 09:13:07 PM
Depends whats up with 2.02.. if it still has jacked up LV and doesn't work without any other usb live preview, probably not.
Gotcha.  Where does this fit in the list of priorities?
#20
Tragic Lantern / Re: Tragic Lantern for EOS M
July 31, 2013, 08:45:10 PM
Quote from: 1% on July 31, 2013, 08:31:19 PM
60P is the 60FPS mode on other cameras. What would be needed to make it work is probably support for this gimpy mode in eos utility. That is likely the reason its disabled, also it may not be making the preview stream to send to eos utility at all since its underpowered and they made every effort to skimp on processing (ie, not having a real idle LV at 24fps except crop mode).

Do you think it could be made to work on the EOS-M?  How much effort would it take?

I'm sure more than just a few people would love the capability to shoot remotely, particularly those who are into astrophotography.
#21
Tragic Lantern / Re: Tragic Lantern for EOS M
July 31, 2013, 08:20:34 PM
If the EOS-M LiveView is 60P sized at 30fps what would it need to be in order to work?  (What does 60P mean?)
#22
Tragic Lantern / Re: Tragic Lantern for EOS M
July 31, 2013, 08:07:23 PM
If you can port to the 2.0.2 firmware release and also unlock Remote Shooting via the EOS Utility you will be considered a God!
#23
Tragic Lantern / Re: Tragic Lantern for EOS M
July 17, 2013, 05:45:07 AM
Quote from: 1% on July 16, 2013, 03:13:16 PM
I found my bug so I'll start working on upgrading to 2.0.2 soon.

You're the BEST!  Thanks!   :)
#24
Feature Requests / Tethered Shooting with EOS-M?
July 16, 2013, 02:25:32 AM
Question:  Did the original ML port for the previous firmware release support tethered shooting?  This is a very important missing piece of functionality from the EOS-M.  It would be GREAT if tethered shooting (e.g. camera controlled remotely via USB cable from a computer) could be made to work.
#25
Tragic Lantern / Re: Tragic Lantern for EOS M
July 16, 2013, 02:22:08 AM
I'm new to the Magic Lantern community.

First, thanks to all of the people who have contributed to make this project a huge success!  Where would we be without you folks?

I just received the EOS-M with firmware 2.0.2 installed.  I am hoping that ML is ported to this firmware release as I too would like to:

"I want to perch this thing on my telescope and take some wide-sky astrophotos with the 22mm f/2 lens, and ML's intervalometer and bulb control are just what I need."

Question:  Did the original ML port for the previous firmware release support tethered shooting?  This is a very important missing piece of functionality from the EOS-M.  It would be GREAT if tethered shooting (e.g. camera controlled remotely via USB cable from a computer) could be made to work.

Again, thanks so much for all of your efforts...  they are truly appreciated!