Messages

I'm using this:

http://www.amazon.com/Fotodiox-Adapter-Minolta-Rokkor-Digital/dp/B003EB0AY8/ref=sr_1_fkmr1_3?ie=UTF8&qid=1378562189&sr=8-3-fkmr1&keywords=opteka+md+to+ef

It works like a charm with my EF lenses. The adapter has a back element that corrects the focal flange.

Yeah, exactly, with an optical element... I've read that kills some sharpness. But maybe it's not so crucial for video. What's your experience?

Here's another music video I shot with the RAW module.  Lenses used: Minolta MD 50mm f1.4 Rokkor X, 28mm f2.8, 135mm f3.5, 70-200mm f4.

How do you use your Minolta MD lenses on the 5D Mark II? Do you use an adapter with optical element or did you convert the mount in some way? The flange distance for MD lenses is shorter than that for EF lenses so a 'normal' adapter wouldn't work, right?

I have lots of MD/MC lenses (used with my GH2) and I'm thinking of selling them cause they don't fit the EF mount...

Are you sure you are using (one of) the newest build(s)? This black border thing was common in the early days of ML raw.

but I thought that producing a video with 80-95 MB bitrate would demand a card that is capable of faster writespeed than 40 MB/s. Maybe I'm interpreting these numbers all wrong???

The bit rate of that 80/95 Mbps video is is Mb/s, not MB/s.
95 Mbps = 11.875 MB/s.

Raw video with lets say 80MB/s, has a bitrate of 640Mb/s.

No, some shots iso 1600, some 3200. I don't use ETTR, don't see the point for video, I just use manual exposure.

A few test shots. ISO 1600/3200 with 50mm f/1.4 @ 2.0. Shot at 1856 x 1044.
Applied a Arri Lut in Resolve and stabilized some shots a bit, thats about it.
I wish Resolve would handle the raw files better. In ACR the aliasing/moire is a bit less bad. But I like the speed of the Resolve workflow... hard to beat that.

It's Den Haag! Even though I have quite a few anamorphics, I'm still looking for other ones...  Would love to have an Iscorama but prices have gone trough the roof. The days of the bargains are over or you have to be incredibly lucky. Not planning on keeping all the lenses I have either. After switching camera's the past few months I'm planning to settle down with the 5D2.

Welcome to the club! You made me curious, what Anamorphic do you have / plan to get? Anamorphics have been bugging me for a long time, RAW seems ideal to harvest their full potential... but as you have pointed out a mosaic engineering filter should be the first investment!

Thanks
I have too many anamorphics actually... Kowa B&H (2x), ISCO Optic Ultrastar (2x), super small Petit Cinevision (1.5x), Iscomorphot 8/2x.
I have been using them with my Panasonic GH2 mostly. You can check my video's on Vimeo.

Here's a video I shot with the Kowa B&H on the 50D in 4:3 raw:

And a clip I shot 3 months ago with the Kowa B&H on a borrowed 5D II:

Hey guys, I'm joining the 5D Mark II raw club Have been shooting with a 50D for a while but got a nice deal on a 5D II.

Installed the latest build yesterday, with my Komputerbay 64GB card i'm getting about 75Mb/s. I rarely record very long takes so 1880 or 1872 in 16:9 is quite usuable, which is nice!
Planning to use it for anamorphic at 1600x1250 as well. Will share some stuff soon!

Would love to see more real world examples of the VAF 5D2b in action on raw (preferably downloadable 1080p files). The aliasing is the only thing I don't like about the 5D2 raw...

When i import into resolve and apply the blackmagic film color space, the video looks flat and it feels like loosing some color information.. When i apply a look onto that bmcc - a 3dlut it doesnt look right..

When you apply BMD film in resolve you get a very flat look. That doesn't mean you loose the color information, it's still stored in your raw file. From this point you can apply a LUT, make a node for example and choose the BMD film lut (3D lut). For me this works perfectly. The BMD film lut is very colourful, I do turn down the saturation from there.

are you aware that the progress bars lock after processing about 1/4th of the frames?
it still processes all of them, but the GUI greys out until its done if I click inside.

Same here (windows 7).

re: raw video

I'm just wondering if hardcoding common aspect ratios might be a better idea as a lot of the current options will likely never be used by anyone and might confuse some users. Maybe just keep SD, HD and Full HD + cinema ratios and x1.33, x1.5 & x2 options for anamorphic shooters?

Please leave them in... I love the freedom and creativity it gives. The more the better!
For anamorphic I use lots. 3:2, 4:3, 5:4 at various sizes.

Odd sizes could be in an 'advance' menu maybe if its a problem for others?

Thanks for the detailed information. Will give it a try.

I was away for work a few days and now suddenly the 1080p barrier seems broken. Amazing!
I'm away for the weekend - took my camera with yesterdays build by Gregory.
I'm reading about this workflow where you have to use 'don't click me' - whenever I do that my camera crashes hard though. I press it before enabling live view. The display turns black and i cant turn on live view or get a menu on the screen. When I press the shutter I get Err 80.

Any advice on the don't click me thing?

I can't seem to get good speeds with that build Gregory. 65-68MB/s in all modes and all resolutions I've tried... Komputerbay 64GB 1000x.

I missed the last few builds since I was away for a few days. I might be doing something wrong. Will check some of them to see if speeds get better.

Why would that make the color resolution pure?
14 bit raw video is just like a 14 bit raw photo, only you get less pixels per frame. That doesn't have anything to do with the data that is in the pixels.

Just checked. Your work flow is better . Because with image it is not possible to check this.
Only a video will help, which is having same field in both the resolutions. Then only we can compare.

I don't think it will be any different with video. It would be easy to try, but I'm not going to do it (sorry). I just don't believe that upscaling something 200% will look better than upscaling something 50%. There is just a lot more detail if you shoot at the highest possible resolution. You're not magically getting that detail back by a 200% upscale.

If there is a way to simply solder in an audio in connector (to be used e.g. with Zoom H1 recorder) that would be super sweet.

Even if that is possible it still has to be implemented in the software...

Good idea I think it needs a bit more 'structure' to get started though. If 20 people start editing this document at the same time, that's bound to be inefficient.

What is the plan? What should be in it, what should not be? (I think it should be about raw - there is plenty of documentation for vanilla ML).

Make everything from scratch or try to collect all the available and relevant info into one place?

I think the latter is the easiest way. We could mail some websites who wrote tutorials for example to ask if we can include their tutorials/text (with credits/back link).

Distribution - how? Google Docs can be nice, but a public editable document isn't a good idea for distribution. A PDF is too easily outdated. Maybe make one final Google Doc / Presentation that is editable only by a few moderators who can keep it up to date?

I am new to ML. Just want to know can u record in desired resolution in ml? or it is having some presets for recording resolutions. Can you record raw in 960x540 (60/30/25/24/23.9p) with high quality ?
Why because as I have seen when we resize image by double it looks better then scaling it disproportional.
you can check this concept with images. I don't know i it same in case of videos. The whole idea is if anyhow we are scaling it because of limitations. why not try low res. high quality video and do other things in post mostly scaling in proportional way.

I get your point, but I doesn't work like that. More important with downscaling I think.
Try it out yourself, take a random image, resize it to 1584x892 and save. Resize to 960x540 and save as copy. Now open both files and resize to 1920x1080...

Agree with g3gg0.

Don't like it? Don't buy it. It's a free world we're living in.

I haven't bought the guide and I won't, because I've been following the developments for hours a day the past few weeks. Small chance I'll find something new in there that makes it worth the money.

But hey, if you want to jump into the game now... this might be a good buy. Of course, it would be cool if someone would make the whole thing for free. Actually I've been planning to make a simple (free) tutorial video to do raw on the 50D (for beginners). It's a lot of work though so I never get to finish it. Even something small like that. Imagine putting the whole guide together.

I have more respect for this pdf - that is the only available document right now - than all those book publishers with their 'how to'  crap books. Especially the photography ones made by shitty photographers.

Anyway, why bother complaining about it. Make a guide yourself - start a topic or a Google Doc where we can all collaberate on making the ultimate ML raw guide for free! I would put some time into it.

And to all the 'donate to ML!' sayers - there is currently no way of donating directly to ML... So that comment doesn't make any sense.

I'm not getting this issue in Resolve. Have you set input or output scaling to fill the frame?

Yeah. Tried different options. But I also get it when I make a project with the exact pixel size...

I'm getting weird results in Resolve when loading CinemaDNG's converted with raw2cdng.1.1.6. I'm shooting with the Canon 50D.
If I open the frames in ACR, they look fine. In Resolve there is a faint blue/orange coloured line inside of the frame.

See screenshot here: http://www.magiclantern.fm/forum/index.php?topic=5586.msg52177#msg52177

Could this be caused by raw2cdng? I don't think so since the DNG's look fine in ACR. Could it be a 50D problem? Anyone seen this and knows a fix for Resolve?

Good to know I'm not the only one...
It's blue on one side, orange-ish on the other side. Barely visible with BMD Lut, but really annoying in the final result.
I'm using  raw2cdng.1.1.6. That's the only option I think.. (Windows).

I'm getting weird results in Resolve.
Colored lines around the frame and a 1px black border.

Looks like this:


Framegrab from exported h264 file at 300% + curves to make it more clear.

The CDNG file is fine (converted with raw2cdng.1.1.6) if I open it in Photoshop so must be a setting in Resolve somewhere I suppose.

Anyone seen this before? What could it be?

[ml-2013Jun16.50D.109.go.unified.b93d6ae2b30d]

I will post my experiences with new builds here.
Latest build I've been using is ml-2013Jun16.50D.109.go.unified.b93d6ae2b30d. Will report back on it soon.