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 - jordancolburn

Pages: [1] 2 3
1
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 20, 2014, 03:52:23 AM »
Thanks, that chart is really helpful.

2
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 13, 2014, 04:15:21 PM »
The shutterbug appears when you use the EFM 18-55 lens oin the M with ML. After you turn on the camera in Movie mode, try to take a pic pushing the shutter button and nothing happens. Three workarounds- power off and on real quick before the red led flashes, untwist the lens slightly and then twist back on and reformat using the Canon menu choosing to KEEP the ML files intact and then always having a 4gb record cycle instead of 6gb using exfat. all three work for me. But the shutterbug only relates to The M with the EFM lenses. And some people have different experiences with it, but very similar.

Gary
Strange, I have the 22 EFM and haven't seen it.  Can anybody confirm this happens with the 22 or 11-whatever wide angle lens too?

3
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 13, 2014, 03:02:35 AM »
IIRC, the person porting TL to ML was mostly concerned with 'picture taking' changes to TL, NOT video. So this is of importance to him, I think !!  I am sure it is not easy getting all the code deltas correct, assuming his tools are not so great, shame there is not a 'versioning' code repository to keep each code 'effort/changes' independent by 1% & others.
Acutally, I'm mainly a video guy, so smooth operation of things like zebras, rec picstyle, and basic audio meters are my main concern.  I do use the eosm for photos a lot too, but I haven't experienced the shuterbug, if someone can give me steps to recreate it, I can try to find a fix.

After porting, it's been working well enough for me to use for small family photos and videos, but haven't used it on a real project yet.  I've been pretty busy this past week, but my short list of bugs to look at next:
-shutter speed display in menu
-canon menus overlaying ML menu bugs
-bug I'm experiencing with it hanging every few startups

4
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 06, 2014, 04:21:40 PM »
PS: Now the question is, is it worth the huge trouble processing raw 720p when the world wants 2kHD or even 4kHD !?  Especially considering the ability to get high bit rate compressed H.264, would anyone notice the diff for a huge amount of situations? Maybe only for high ISO situs?
Not really.  720 will still look good as most people viewing your work (if it is meant for web) won't even bother to put it in fullscreen on their tiny laptop monitors.  I've put more than a few hours into trying to develop a raw workflow to even do a simple 1-2 minute project shooting around town, and the results of my simple comparison tests don't show enough difference to warrant all the extra effort.  After the basic stability/usability features get sorted, there is no reason not to push the camera to its limit, but for me, the EOSM is a great tiny camera that I can keep on me to get good video with minimal fuss, and stock h264 really is good enough for most simple doc pickup shots (again, for web delivery).  If  anyone really needs raw on the cheap and it's non-negotioable, they should pick up one of the BMD cameras.

5
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 02, 2014, 01:27:05 AM »
I forgot to say the shutter "menu settings", not the main display screen.
Yeah, the menu settings are really weird, I will look into fixing it.  As a work around you can see what the actual shutter value is by pressing set while on the shutter menu to hide the rest of the menu options and looking at bottom ML bar.

6
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: January 02, 2014, 01:21:29 AM »

Did you figure out the shutter bug?
No, I'm not sure I've seen any steps to reproduce it, and I haven't experienced it myself.

7
I haven't looked at Cinelerra / Kino in a while. I have found kdenlive to be the only useful Linux editor for me, last time I looked into it. The process of importing stills as a sequence into a video file is the same as with After Effects, so I thought I would mention that. In the spirit of 100% open-source.

PinkDotRemover is necessary for the t4i/650d and some other (?) Canons, although the term understates the severity of the problem.
EOSM as well, although the locations of the dots differs depending on the raw crop.  Incorporating the remover into one of the raw converters would be very very useful for people with these cameras.

8
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: December 31, 2013, 04:37:13 PM »
thanx Jordan. The display for the shutter seems strange with all the numbers and letters. Can we get the normal 1/48 and so on back? Headphone does not work. I did record some raw at 720p24, but I don't think it is MLV. There was no playback of the file in the File Manager section like before.

I'll look into the shutter display.  I  never tried it, but I don't think headphone was ever working, even on TL.

9
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: December 31, 2013, 04:35:47 PM »
I have tested the latest release of the EOS ML firmware. There are quite a few bugs and some features do not seem to be active yet. Dual ISO/ ETTR need some working on.

The pink dots while RAW recording are still seen. RAW video replay does not work.

However, I just discovered the H.264 recording at 3X zoom. And wow! This feature alone makes this release worth a million bucks.
I think ETTR hints on the menu are correct, but the actual feature isn't correct.  I have not tried dual ISO on any camera, so I can't speak to that, but again, my focus is weird menu things, audio/video features before working on dual ISO, raw, etc.

Pink dots are just what this camera does from hardware, the pink dot remover will take care of that.  Raw playback was working (slowly) on TL, so when I get to working on that, it shouldn't be too bad to pull over.

10
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: December 31, 2013, 04:04:22 PM »
Fix the red box temp settings. I have posted before that it is definitely incorrect saying it is Centigrade. It should be down to around 30C and my M is always showing around 100C more or less even when I first turn it on.
Yes, I think there might be more than just changing C to F going on.  My camera has shown temps of 100C after just turning on in a cool room, and the camera is very cool to the touch.  I will add this as well.

11
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: December 31, 2013, 04:03:21 PM »
it would be good to have the audio return to it's ON state after shooting raw and then going back to shooting H264. Raw disables the sound, so enable the audio when we disable the raw settings to go back to H264.
Thanks, I think this was an issue on TL as well.  I will add it to the list.

12
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: December 31, 2013, 03:59:55 PM »
How you make it?  Video? :)
There is a setting under the video tab in the ML menu that lets you turn on/off the 3x crop.  This uses the center area of the sensor and gets rid of moire and aliasing.  With the 22mm lens, this feature gives you a lot of flexibility to get semi-wide and close up shots in a small package.

13
Camera-specific discussion / Re: EOSM-Updated ML for 2.02 firmware
« on: December 31, 2013, 04:31:13 AM »
Finally got a chance to test the nightly.  It works for me, with a couple of bugs the I plan to work on.  The canon menus seem to briefly overlay the ML menus during things like half shutter presses and autofocus face recognition, but this does not seem to affect taking pictures or video.  Also, if you switch the camera off when in 3x crop movie mode and change to a card without ML, there is no way to go back to regular movie mode without rebooting from a ML card and changing it back to uncropped movie mode.

14
Hardware and Accessories / Re: Sound improvement on Canon Rebel T3i
« on: December 31, 2013, 04:05:27 AM »
I wouldn't recommend behringer, even though it probably is in your price range. One $20 umbrella will outlast four $5 umbrellas.
For a utility mixer, it's great, I bought a 12 channel $40 mixer 6+ years ago and use it for video, submixing keyboards, live looping, reall everything, never had an issue.  We also have a behringer digital mixer as our main live board at church and it offers a lot of great routing options and it hasn't let us down yet.

Also, I second the rode videomic if your application for more documenting events as they happen.  It has been a big improvement over internal sound and a cheap external audio technica stereo mic. 

If you need a simple mic for a closeup headshot, then I have had good luck using something like this straight into an eosm and 22mm lens. http://www.amazon.com/AZDEN-EX503-Omni-Directional-Lavaliere-Microphones/dp/B000BSMKPY

15
Camera-specific discussion / Canon EOS M
« on: December 30, 2013, 10:21:20 PM »
The nightly build is now available here:
http://builds.magiclantern.fm/#/

Installation:
1) Format the card from the camera.
2) Make sure you are running Canon firmware 2.0.2.
3) Copy ML files on the card and run Firmware Update.

Uninstallation:
1) Run Firmware Update from your ML card.
2) Follow the instructions.



Thanks a1ex   //Audionut.



I moved some of the great  work 1% did to get ML functioning on the EOSM for firmware 2.02 back into the main ML code base.  I'm sure its missing some features and bugs from it's TL counterpart, but if you are interested in testing ML and helping make it stable and in sync with the code for other ML cameras for all base features, please comment here and I'll do my best to port 1%s bugfixes, or to test, create issues for new bugs and attempt to solve.  IMO, the main focus is ensuring all basic ML functions work well before branching out to things like raw video.

(I have not tried the nightly yet, but my own local compile from a few nights ago works for me)

16
Hardware and Accessories / Re: Sound improvement on Canon Rebel T3i
« on: December 30, 2013, 10:01:20 PM »
If you a video where the main cam is on a tripod, a cheap audio option could be one of the small Behringer mixers or a portable zoom recorder with a few preamps.  Run any XLR mic you want (lavs, shotguns, condesensors to pick up room sound) into the mixer/recorder, pan tracks you will want to adjust later to different L/R (A two person interview might have one lav left and one right, or a single person performance might have lav panned left and room mic to the right) and take the output via an rca or 1/4" to 1/8" adapter straight into the mic input on the camera.  Turn the volume on the mic input one notch above 0 and use the mixer for all your gain.  We use an old zoom recorder with a line out essentially as a preamp for lav mics and have recorded many quality interviews this way with no need to sync.

17
I've been using vi and grep to poke my way around the code.  It works pretty well, but I haven't had to do any big copy/pasting or formatting.

18
Feature Requests / Re: MJPEG
« on: December 16, 2013, 10:34:32 PM »
Yeah, C is expensive, but the sony is closer to 3k and BMCC is 2k and BMPCC is 1k, so there are options.  I guess my point is, when you can get a BMPCC new for the same cost as a used 5dII, as a shooter I would rather not deal with a hack to get a midrange mjpg and would rather go with the out of the box prores with no need for developers to reinvent the wheel.  Granted, you can argue ergonomics, or photo capability and everything and it's all valid. But, the way I see things now is the best value is in the sub $600 DSLRs (t3is, eosm) b/c such video quality for such little money is insane!  If you really need a better codec, try raw and deal with the limitations or there are all kinds of cameras with an astounding variety of options from 1k-10k that have great compressed codecs.  People are obviously eager to see how far we can push DSLRs since: 1) It's fun, 2) We already have them and 3) it's cheap, but if someone is doing a real paid work, I would encourage them to examine all the great options that are out there.

19
Feature Requests / Re: MJPEG
« on: December 16, 2013, 10:07:43 PM »
I mean, I think your options are either deal with the "Bad" codec.  It is actually not that bad, really, tens of thousands of people use canon h264 every day for content that looks great.  It might not push or pull in post as much as you want, but for small file size, one man band or a small budget team, if you can't make a decent looking video in h264, raw isn't necessarily going to be the silver bullet that solves all your problems.

The raw hack is a super interesting way of getting better quality out of these cameras, but is still getting the kinks in shooting and post worked out.  Most of the negatives you had to say about raw apply to raw in general and not just ML.  The large file sizes, need for fast media and extra post work make raw still a little unreasonable for most projects that have a time or budget crunch (what project doesn't).

If you want a camera that shoots a nicer codec, with still decent file sizes, look for something like a c100, sony fs100 or prores on the blackmagic cameras (having used none of these cameras, I'm only recommending based on reviews).

20
General Help Q&A / Re: New owner concerned about status of ML on 6d
« on: December 16, 2013, 02:59:23 AM »
Sorry, I don't mean to underplay it, but it really was just a lot of recreating 1%s changes by hand (where they applied) to the ML code.  He's done a lot of awesome things that really took time and research and trial and error, it will just take some time for people to apply those to the main ML branch in a way that it can move forward with the widest camera support.  It will take time, and I am starting with moderate coding ability (I work doing web development, but have my MEng in EE, with some courses in C and assembly stuff), but the barrier to getting the code compiling and committing changes wasn't as bad as I thought and would just like to encourage others to dive in if they have an interest.

21
General Help Q&A / Re: New owner concerned about status of ML on 6d
« on: December 14, 2013, 09:24:10 PM »
When (if?) someone starts maintaining the 6d build, I think the important thing is that end users move over and test, if everyone is using TL and nobody can vouch that ML doesn't have bugs for the 6d, there's not really a reason for it to exist.  Also, as a very, very, newbie dev, I found it was pretty easy to update ML to work for the EOSM, so if anyone has even moderate coding skills don't be afraid to step up and help maintain it.

22
plus, anybody that rents a regular 5dIII could put magic lantern on it themselves for free (although I wouldn't mess around with a rented camera), you're paying for their labor, not for ML.

23
Well it means extra work for their staff to test ML, decide which builds are stable enough to rent out to working professionals, make sure the cards they send work and they have enough training material included so that a clueless joe somebody renting can avoid jacking their cameras up (ML is pretty safe, but there are some basics you need to understand about it).  So extra man hours = higher rental, I don't really see whats wrong with that.  Its like a company that provides paid support for open source software, plenty of successful businesses are based on it and there's nothing morally wrong with it.

24
General Chat / Re: Can't get compiled autoexec.bin to run
« on: December 13, 2013, 02:48:23 PM »
That's what I was looking for, thanks!

25
General Chat / Re: Can't get compiled autoexec.bin to run
« on: December 13, 2013, 05:36:31 AM »
Ok, I got it working.  The issue was that I was building for EOSM.106 for the old firmware.  The newer updates for TL are in the tragic-lantern-6d repo and not in tragic-lantern-2.0.  I didn't realize that ML was so far behind for the eosm.  I still would appreciate any resources that explain how to create the ML folder for SD cards as I still can't seem to find any info on that.

Pages: [1] 2 3