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

Thanks, that chart is really helpful.
Quote from: gary2013 on January 13, 2014, 03:20:51 AM
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.

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?
Quote from: RavingRover on January 06, 2014, 07:26:52 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
Tragic Lantern / Re: Tragic Lantern for EOS M
January 07, 2014, 06:33:39 PM
Quote from: a1ex on January 07, 2014, 05:06:06 PM
Welcome to Linux Airlines. Unlike BMPCC, ML is a spare-time community project and nobody of us is developing full-time. Identifying the bugs is a very time-consuming process for us, and doesn't require any coding skills, so you can help a lot simply by documenting these issues properly.
BMD has full time developers and still hasn't realeased fixes/features for their cameras (audio meters?) that the ML team solved on cameras that they don't even make.
Quote from: RavingRover on January 05, 2014, 11:24:04 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.
Quote from: gary2013 on December 31, 2013, 08:15:42 PM
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.
Quote from: tob on January 01, 2014, 10:12:10 PM

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.
Quote from: debrecen on December 31, 2013, 05:52:25 PM
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.
Quote from: gary2013 on December 31, 2013, 05:23:14 AM
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.
Quote from: Canon eos m on December 31, 2013, 12:45:52 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.
Quote from: gary2013 on December 31, 2013, 03:59:59 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.
Quote from: gary2013 on December 31, 2013, 03:56:39 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.
Quote from: Oswald on December 31, 2013, 01:54:20 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.
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.
Quote from: ItsMeLenny on December 31, 2013, 02:49:22 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.
Tragic Lantern / Re: Tragic Lantern for EOS M
December 30, 2013, 10:23:00 PM
EOSM is back into the nightly builds for ML.  Try it out and comment on your experience and the things that you need to see fixed in order for it to be useful to you:
Camera-specific Development / Canon EOS M
December 30, 2013, 10:21:20 PM
The nightly build is now available here:

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.

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)
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.
Tragic Lantern / Re: Tragic Lantern for EOS M
December 20, 2013, 05:42:04 PM
Quote from: R4dev on December 20, 2013, 04:01:17 AM
Hi there! I'm new to the forum, and want to thank you all for your hard work.

I have a problem that I hope you can help with. I recently bought an EOS-M and couldn't wait to put ML on it. It downloaded fine and everything seems to work fine, except when I try to  shoot RAW video. It seems to start shooting, then after a second the camera restarts, without saving any files. It happens in crop mode as well. I'm using Transcent 32GB SDHC class 10 card and I tested with 1408x362 resolution at 2.35:1 ratio. Sorry if this problem has been resolved before, the topic is 89 pages long now and my search found nothing.
While I never experienced the camera restarting, I had issues with a class 10 transend card.  Try turning on FPS override to something like 8 fps just to test the stability and post workflow, and look for something like a sandisk 45 MBs card once you're ready to take the next step.
Tragic Lantern / Re: Tragic Lantern for EOS M
December 19, 2013, 09:51:08 PM
Quote from: gary2013 on December 19, 2013, 09:19:10 PM
I know, I have said it over and over again, but since you asked, I would like to see the audio headphone out to work on the M. 1% spoke a few times as if he was just about to get to working on it and that he felt it was doable. Having the ability to hear the audio before , during and after an interview is crucial along with seeing the video playback on the lcd of the M. The whole purpose, at least for me, was buying the M to use in making documentaries while being discreet and having light weight without having lots of extra gear to carry and setup. The  sound on camera is just fine for me. So, please try and get the audio out for headphones on the AV port as well as getting the audio meters to be visible before recording and during recording.
Lightweight docs is why I got the M too, and audio will be one of the big things I'll look at.  I think audio meters before recording probably can't happen since the chip is only active once you start.  You can test levels in the Canon manual setup and see meters before recording, or just record a test clip to test the levels (this is what I do on the t3i). I am a little more concerned with trying to pick up all the bugs and stability stuff first, and 1% is sure to be better and faster for new feature stuff like that, but I'll give it a try to.

The EOSM seems perfect for grabbing quick interviews for Docs, a simple clip on lav with 1/8" connector can fit in a jacket pocket with the EOSM, 22mm lens and a backup battery and card, and you are always ready to grab a quick interview or story (on some recent trips, we always find that when people are most at ease and willing to share their stories, is when we're least prepared shoot and out to eat or something).
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.
Feature Requests / Re: MJPEG
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.
Feature Requests / Re: MJPEG
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).
Tragic Lantern / Re: Tragic Lantern for EOS M
December 16, 2013, 03:08:31 AM
All the basics do seem to work for me.  Zebras focus peaking(the old style i think), 3x zoom (fantastic with the 22mm lens) and all that seem good. I think the stuff to iron out will be little bugs like with AF on, it seems to track faces through the ML menu and 3x zoom setting persists after turning the camera off, so switching to a non ML card, you get stuck in crop mode for video.
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.