Messages

the mkII only has one CF slot.

Seriously?

But that's... stupid.

Ah... Guess there was already a post about this.

Just got the router a couple of days ago. Works BEAUTIFULLY... and I even got it to fit on my camera strap! It weighs practically nothing. Now I can do all of my recording from my phone... that is PRICELESS.

i have a 128GB 1000x Card from kumputerbay as well , ive had it for 4 months and never used it , simply because ML Doesnt work on Cards bigger than 64GB ....i have never tested it on raw since i never got to so i cant anything about that .

But... you have a 5D mk II... couldn't you just load ML on a smaller card and then save your files to the Komputerbay?

Lol.. I can see your mask on the background.. doing it the right way is not that simple mate
Grading raw is way different than grading a very VERY flat 4:2:2 (what Dave was doing)

Nice work making a guide though, I'm curious about the result ^^

Ahem...

Here's the first image we'll be working with. This is just something I threw together in a few minutes just to explain the process.

Also I mentioned how that first example was just a "ham-fisted" way of explaining the basics.  I get that you might be an absolute EXPERT at color grading... but this guide starts with people who are not. I wanted to give, in as simple a demonstration as possible, an idea of what the possibilities of this program are. Before gradually revving up the difficulty curve (because I hate "guides" that don't really explain anything and expect you to know all of the things that were the reason you started looking for guides in the first place.)

So if you want "the right way"... then stay tuned for some of the later portions... you might learn something.

..."mate". 

Updated! Slowly but surely I'm getting started...

Thanks for ur reply. should i only switch on these two modules only? the modules i have switched on are:file_man,mlv_play,mlv_rec,mlv_snd,pic_view,raw_rec

You don't get it man... it's not mlv_rec AND raw_rec it's mlv_rec OR raw_rec.

Either one or the other. NOT BOTH.

Nice that so many tools supporty MLV now. But really all I need is Adobe and Resolve to support .mlv and .raw... straight up... out of the box, and I'd straaaaight.

I never did believe in any all-in-one solutions. To me it's all about CR+AE+Premiere+Rez

That's 1st base, 2nd base, 3rd base, and the catcher at Home.

(Though I will check out the 90-day trial of Scratch.

That's something totally different. You need to "conform" your footage to 23.976 in AE. If AE doesn't know what the FPS is (how would it know when you're just giving it a folder full of dngs?) it assumes 30 FPS

He just said he did that. That whole thing where he said he opened it as 23.976.

The only way he could've done that is by interpreting the footage and typing in "23.976"

quite funny, my app is not listed.. seems its

* "some of the more redundant programs"
or
* not mac'ish enough..

regards chmee

You poor thing... (look again...) 

Some of the panning shots are quite fast, but like you said; they do look worse on youtube unfortunately. I also don't know what's up with the saturation.. the youtube version has a lot more saturation then the original one. I never noticed the saturation difference before. I have yet to figure out the best export settings for uploading to youtube..

You can try the suggestion above with the scopes in resolve... but after seeing your video I think I'll avoid Youtube altogether. I never liked their compression to begin with... and with Vimeo around... why even bother with Youtube?

haha, now it is even more impressive

Tell me about it...  I gotta look into those Osirus LUTs!

You think THAT's something... try the "Making of"

Deliriously happy about this.

Great job!

Really nice images Ryan!

@HamboDeluxe : Search the forum for info about the bootflag. I believe it is not possible to remove it safely yet, but try search the forum (I know that there is some function for removing bootflag in latest nightlies, but don't know if this is completely correct/working etc.

This is incorrect. If you'll check out my "2014 Current Raw Capabilities" thread you'll see that bootflag can now be disabled on the 1.2.3 version of ML for the 5D3.

So yes... this can be removed.

which build version should I install for the raw?

I'd go with the latest nightly.

Sure:

1. Load MLV record module
2. Enable in Movie preferences
3. Press record.

I can confirm this for 960 and 1152 resolutions on the 600D.

80% of the time I wind up with at least 3 pink frames (vs. 0% with raw_rec. Same shoot, same day, usually just seconds apart from each other.)

It's pretty consistent. Only 20% of my shots don't have pink frames. They're usually just in the beginning of the clip... but could be anywhere. Version used was this: magiclantern-Nightly.2014Mar26.600D102

I've shot about half a dozen videos using the March 26th version of ML.

Somewhere north of 80 percent of the mlv videos I shoot have pink frames in random places... and the .raw videos do not.

Is this common... or is this just a thing I'm having?

Yeah... That's kinda why I created this thread: http://www.magiclantern.fm/forum/index.php?topic=11243.0

Anyway you should always just TRY whatever the latest version is.  If you don't like the way 1.2.3 runs you can always downgrade back to 1.1.3.

Both of them work just fine for a lot of people.

Well I would imagine a long exposure would be much MUCH longer than 1fps... I think it took a couple of tries to get rid of my hot pixels, so you might want to read through that thread and see what people had to do for your camera specifically.

I couldn't even see the hot pixels at all until I tried doing a really long exposure.

Then I did the fix... maybe 2 or three times... and they were gone.

So if it didn't work the first time around I'd just check the thread and find a 5d mkii solution.

Sigh... I always wanted that lens.

(oh... and I also want to marry Basia.)

Excellent job. Tight focus.

It fixed mine... Let me know how it goes. 

To the best of my knowledge that's not a "dead" pixel... it's a "hot" pixel...

The difference being hot pixels can be fixed... and dead pixels can't. (If the pixel is a color... then it isn't dead.)

Have you tried this?

http://shmuliphoto.wordpress.com/2009/12/03/fix-hot-pixel-canon/

Type: Announcement date
450D: 23 January 2008
500D: 25 March 2009
550D: 8 February 2010
600D: 7 February 2011
650D: 8 June 2012
700D: 21 March 2013

In fact time gap between announcements of 650D and 600D is the largest in xxxD lineup since 450D came up the horizon.

Yeah I'm aware of that. But the distance between the 650D and the 700D was the shortest... which is what we're talking about.

Well! guess I'm gonna have to look into a Panasonic Lumix (GH2 or beyond). That sucks. Thx for the feedback.

GH4 is just a couple of weeks away with 4k video.

If you're looking for cheap I'd go for a used 7D which you can use Compact Flash with... or a used 5D mk II.

Yeah, coming out with the 700D so soon after the 650D really perplexed a lot of people. If you do a side-by-side comparison of the two there's little difference or improvement with the 700D.

Here's a breakdown where the reviewer calls it a tie between the two: http://snapsort.com/compare/Canon-EOS-650D-vs-Canon-EOS-700D

What's your opinion on why they came out with the 700D so quickly?

I think the 650D was rushed to market in the first place. I remember it came out about a week or two after I got my 600D and I was mad as hell... then was an immediate recall because the grip was giving people skin rashes (that made me feel a little better) http://www.techradar.com/news/photography-video-capture/cameras/canon-recalls-eos-650d-cameras-says-faulty-grip-could-cause-skin-rash-1092239

That's just what was going on for the OUTSIDE of the camera.  On the inside there were all these weird little sensor issues and other issues associated with the AF... http://www.dpreview.com/forums/post/50717250

I think there was more wrong with the camera than people knew about... but CANON knew of course. So they decided to quickly release the 700D. Exactly like what Nikon did with the D600 and almost immediately replacing it with the D610 (which I didn't even realize had happened until I went to the camera shop last month.)