Messages

Keep up the good work guys ; )

It's been a while since I've gotten onto the ML forums, and I've waded through a ton of pages and haven't seen the answer to this so please don't bite my head off if someone has already asked this question:

I know our shitty 650D's don't have the bandwidth for 1080p raw video, but what about the original raw mode where you could get 2 seconds of 1080p raw in the buffer and let it do the write-behind to the SD card?  I think that would be a feature worth having.  Of course, next I'm going to hear that the buffer is so tiny that would only work with about 1 second @ 24fps

Anyone know what they are doing on the 5D to suppress the dots, or is this exclusive to the APS-C sensor cameras?

Intervalometer + RAW DNG silent pics is as good as it gets
or FPS override + raw video

Tried the RAW DNG but I get red dots all over the screen in the area that the AF sensors seem to be in.  W/ FPS override, when I shoot 1/24fps for some reason the shutter is super slow (its set to 1/50 but acts more like half a second)...

Hey guys.. Haven't been 'round here for a while since it makes my wait much shorter when not checking the forums every day to see if it's done

Does anyone know if the intervalometer will be able to use RAW video mode to take a time lapse RAW video?  If so, what is the max frame size for these images?

Thanks!

Also, my public sharing limit for dropbox was reached again, haha. I guess I can try hosting it somewhere else, like Mega if you guys think it's a good idea. I'm not a fan of uploading to a video service (youtube, vimeo, etc.) since they recompress the files.

Please do!  I'd like to see it even if it gets a bit mangled by youtube or vimeo.

Hello ladies, gentleman, and trolls...

In the interest in impartiality, and with the understanding that there has been some animosity/impatience brewing on the ML release for the 650D, let me articulate both sides of the issue and maybe propose something that will assuage the angst of waiting for an official ML release.

On the one hand, we have people like nanomad who have spent considerable personal time porting ML to the 650D.  It isn't relevant why he's doing this, other than to point out that he isn't being paid.  He owes no one anything, and if anyone is a better coder/hacker then they should step up to the plate themselves and stop looking a gift horse in the mouth.

On the other hand, some people have certain expectations, unwarranted or otherwise, of individuals who are identified and "privileged" as ML team members.  Some feel that there are others waiting in line with the time and skill to do what the guys who were given cameras bought with donation money should have finished by now.  After all, its been six months and it hasn't even reached alpha.

So these are the two opposing perspectives, each biased with their own interests in mind.  Where is the common ground?

To me this is about setting expectations.  There was an unwarranted expectation that an alpha would be available early on in the year based on the progress of the M and previous ports.  People are not good at accepting "when it's done" as an answer, even if what they are waiting for is free.  I'm not sure why exactly, that's just the way it is.

Because so many ML enthusiasts are laymen when it comes to understanding the coding aspects of ML, it would be a noble gesture for the current coding team to provide a run-down of what has been completed and what specific work yet needs to be done before a stable release is made.  And then the laymen will return that noble gesture with one of their own:  Stop whining like little bitches.

Fair?

Ah, I love the reality TV folks switching to DSLR because of the beauty of the image over VIDEO. And news folks, and documentary producers, and advertising productions....

I have a question for this crowd. Are RED and Black Magic Cinema video cameras? And what should we consider the differences are between digital film and video cameras?

There isn't much difference between a "digital film" camera and a video camera.  Traditional film cameras use a framerate of 23.976fps with usually a 180 degree mechanical shutter.  Because of the size of the film format, film cameras can achieve much shallower depth-of-field than a video camera.  With that shallow DOF, you can pretty much throw autofocus out the window, so you need a set-up with a good manual focus.  Usually you have an assistant cameraman (known as a focus puller) keep the focus while the cameraman is filming.

So a "digital film" camera is a video camera that can simulate a 23.976fps framerate with a 180 degree shutter (2x framerate) with a sensor large enough for a cinema-like depth of field, and a way of doing manual focus pulls.  More expensive cameras like your RED's, ARRI's, and even the Black Magic, will also take advantage of the tack-sharp HD sensor by allowing distortion-free prime lenses to be mounted for bleeding edge sharpness.  Most DSLR's like the Canon 5d and APS-C cameras use a non-optimal method for converting the camera sensor data to a 1080p image thereby limiting how sharp a video image can be, and are instead used for their versatility in achieving the filmic look.  Compare them to something like the Lumix GH3 and you'll know what real 1080P looks like. 

If you do photo timelapes, though, even a Canon 550D will put out jaw-dropping ultra sharp videos. 
Of course, I'm waiting for Nano to release an alpha or something so I can get the intervalometer functionality back on my 650D ; )

Sharp lenses make sharp images... put your money in the glass. Also DSLR produces a great image in low light and you have the bonus of a creamy archival quality image that doesn't look flattened out. My experience is that a wedding is a staged event and with planning and use of jibs and sliders you convey much more of the emotional aspect of the event than with zoom on the fly.



Doc producer: T2i, T4i, 60D, Ex1, Ex3

You can put Zeiss cinema glass on a T4i and I guarantee you it will never be as sharp as a comparable camcorder.  Why?  Simple.  The sensor has no idea what a 1080P image is.  The processor uses extremely crude line & pixel skipping to simulate the 5,184 x 3,456 sensor as a 1920x1080 sensor. 

If you were to grab the centermost 1920x1080 sensor data, you would have your moire-less, tack-sharp HD video.  The problem is that you'd also be stuck with a ridiculous crop factor that wasn't very useful. 

Now, if Magic Lantern was able to change how the raw sensor data was captured, say for example, you pulled the center 3840x2160, then threw out ever 2nd horizontal pixel and every 2nd vertical pixel, you would have a much cleaner image and you would only be dealing with a zoom factor of 26%.  This would also reduce the rolling shutter considerably, because a smaller area of the sensor is being refreshed.

A prosumer video camera? Geez, I haven't seen one of those at a wedding in years. I'd bet that a survey would show most pro wedding photogs now use DSLRs. But I shall not be funding such a survey.

I highly disagree.  DSLR's are completely unfit for shooting weddings.  They lack the handheld stability, the ergonomics, and overall simplified video functionality necessary for on-the-fly style shoots.  DSLR's are also not as sharp as prosumer camcorders, and require special techniques in most cases to avoid things like moire and rolling shutter.  The only thing DSLR's excel at with regards to video is the cinematic/film-look and this is something you cannot easily get with on-the-fly shooting.

Of course this is a conversation best left for another forum!

NANOMAD -

Just my periodic drop-by to see how things are progressing.  Keep up the good work! 

There's a developer kit available for booting your own autoexec file.
I'm doing some tests because I thought I had a stub wrong. Turns out it was correct but on the plus side we now have flicker free magic zoom and peaking

When you say "we"...

Nanomad, keep up the good work!  You're in the home stretch now!  My T4i becons me, asking for me to unleash it!

And I want to apologize to Kilr0y for using a similar nom de guerre, but this is one I've used for a lot of years on a number of different forums, so hopefully we can peacefully coexist.

I've usd Killr0y for about 20 years, but don't let that stop you!

So... I am a Video Production teacher looking to put ML on my T4i (which I am assuming is the same thing as the 650D). Being a newbie to the ML forums, what I gather from this thread is that ML has been ported successfully to the t4i? Would you recommend on using ML at this point or should I wait until the next build?

Sorry if its a silly question, and let me know if I needed to post it somewhere else!

No, ML has not yet been ported.  The camera has been hacked, which means code can now be run on it.  Once the bulk of ML is ported, there will be an alpha release, which is generally unstable and still contains lots of bugs.  Once most of the bugs are fixed it will go into beta.  When the port is completely stable and no major bugs are reported it will then be ready for a final release.

nanomad, I never doubted you for one second!  Ok, maybe for just a second.. or a few hundre.. anyway, congrats on an awesome achievement, and just in time for Chistmas.  Doesn't get much better than that!

How long before we see an alpha?? 

I have 24GB so maybe I'll just set up a virtual machine for you to work on it? 

Step 1: "Hello World"
Step 2: 4k video support 

Can you post the "Hello World" on the 650D as a 1920x1080 so I can use it for my desktop wallpaper 

OMG OMG OMG!  This is insanely good news!!!  My T3i got dunked in the Pacific last weekend and is now dead!  Just ordered a T4i because I found it for almost the same price I would have paid to replace the T3i.  THEN I find out ML isn't out for it yet. 

Here's to hoping this puppy is a relatively painless port and that there are a few pleasant surprises along the way, courtesy of the DIGIC5!

Anything I can do to help speed up the work, I'm all ears!