Messages

The main advantages that 1.2.3 gives is the ability to record (allegedly) uncompressed clean HDMI out for use with an external recorder. For .raw uses, this is kinda meaningless unless you're planning on recording a back up pro-res video as proxy. Other advantages of 1.2.3 include the inability to correctly display 3rd party battery charge information.

My advice is that before any type of critical shoot, you run a bunch of tests. For a production where we used the ML raw extensively, we were testing for about a month prior to the shoot to make sure there'd be no surprises.

I don't get it, so the 1066X cards seem to yield the same exact results as the 1000X cards....what's the point?

Unfortunately not. I'm still hoping Adobe solve this in the next version of PP since it's clearly their issue.

Wish you would have been at the CDNG NAB meeting on Wednesday. Some good info was being given. Frustratingly though, Adobe failed to send any of their people over. There are some good things potentially coming to the CDNG standard.

If you're on the Mac, there is a pleasant surprise for you in the near future. Full working CDNG with perfect looking footage in Premiere Pro!

Just got back from NAB. Resolve 11 is probably the most exciting thing I saw there (ok, actually Nuke Studio is, but it's crazy expensive and won't be out for a while).

I think Blackmagic is really listening to the user base and adding some amazing features to their software (did I mention it's FREE?).

The new raw settings are a bit more comprehensive than before. Not quite in the same league as ACR, but we get more controls than before for various levels and it should be plenty to get a "Best Look" pass before hitting the color wheels. Black, Mid and Highlight levels are included, but not for instance things like "Clarity" or "Vibrance" that Adobe seems to provide.

Hopefully a public beta means the update will be out sooner rather than later.

@Midphase
What card exactly are you using? Are you on 1.1.3 oder 1.2.3?

I'm on 1.1.3. I have 4 Komputerbay 64Gb 1000X CF cards which test slightly differently but are all in the general ballpark. 1920X1288 at 24p is roughly 99Mb/Sec so the card needs to keep up with that data write speed. On all my cards I can shoot at least two minutes at that resolution without problems (GD is off).

I'm a bit on the fence about moving to the 1.2.3 firmware with ML if there aren't any specific advantaged to doing so; and from what I can tell, 1.2.3 doesn't appear to give me any new function that 1.1.3 doesn't already have with ML.

And 24fps?

I can do continuous 1920x1288 at 24 on my 5D3 while shooting in .raw. In .mlv I need to decrease the vertical res a bit, especially when also shooting with sound.

Aside from the usual "use a fast CF card" tip, my other trick is to absolutely only load the modules needed and nothing more. For .raw recording that is literally 1 module RAW_REC and nothing else.

I do think that it's an exotic variant of ProRes 444 (which doesn't really exist in Apple's specs) so it's possible that it might be getting incorrectly defined by the likes of FCPX.

I do think though that it would be kinda neat to be able to choose the flavor of ProRes. For instance, many of us might just want to create some proxy ProRes files to edit to and do our final color timing on the CDNG's, so in that case ProRes LT or Proxy would be more than acceptable.


Thoughts?

I agree. People seem to forget that moving several Gb from a CF card unto a hard drive takes time in itself. Simply copying about 64Gb from the CF card to an internal 7200Rpm hard drive takes roughly a little over 10 minutes using USB 3.0 and a good card reader.

Well, one of the other options would be to convert the raw files to CDNG and then bring them into Premiere and edit with them.

One of the things you could do is enable the Card Warm-Up option. Sometimes CF cards need to have data written on them a few times before they get up to full speed. Not sure why.

He didn't say bug free. You know what he means.

He's asking for something akin to the Tragic Lantern thread where certain builds had been verified to not have introduced problems and were essentially stable. It's been discussed before and it wouldn't be a bad idea, unfortunately with nightly builds coming fast and furious, it's hard for any of us to stick with one build for too long before moving on to a newer build.

To answer the OP question, I think in general the nightlies are pretty stable by now. Your best bet is to download and install whichever the latest nightly is and run some thorough tests before you use it on a shoot.

MLRaw can conver also dual iso RAW?

Not yet.

You bring up some legitimate points which is why the same questions keep popping up over and over again much to the general irritation of the regulars around here.

Truth of the matter is that you're kinda right, the forum is a mess and unless you've literally been following things for months, you're going to be pretty lost when you first arrive here. When threads push past the 10+ pages, the practicality of reading through them goes out the window.

Here is what I will tell you:

1. Shooting raw on anything without a CF card slot offers few incentives for going through the trouble of the whole raw process.

2. Some new tools, primarily MLRawViewer are a much better way to convert .mlv and .raw files to CDNG's which can actually be read by the likes of Premiere Pro.

3. Both .mlv and .raw are fairly stable in most cameras. .mlv gives you sound which .raw doesn't have, but .raw gives you a slight edge in performance.

4. You can focus by hitting the zoom button twice, the first time it will go into a b/w crop mode, but the second time should go to a 10X full color magnification.

In all fairness, most sensors are susceptible to stuck pixels, even the high end ones which come equipped on cameras that cost more than my house.

I love mlrawViewer it is the best thing that happened to raw on ml.

MLRawViewer is great, but you should take a look at what Thomas Worth has in store for us with the new version of RAWMagic too!

All I'm saying is that before you sign up for something, that you look at the specs and make sure that it fits your system.

For instance, I'm still running 10.8.4 on my main machine, so I have to carefully read to make sure that my specs fit the required minimums or I'm wasting my time. So that means no Red Giant Universe for me!

Please indicate that this competing app for sale is only for Mac so Windows people do not waste time trying to get the demo and give out info with our email addresses for nothing.

Come on Gary...how about you read up what you're signing up for instead of blaming someone for posting about it?

Pomfort Cliphouse has been around for a long time, in my tests it's clunky and never played back more than a couple of frames at a time. The guys who make it never quite had a response as to why the issue is happening, and if I can't get a good sense of how well the app works from a demo, I'm not going to buy it.

I thought the latest Resolve had fixed this issue?

I have an M and it does not do audio, which is the big reason to use MLV at the moment. So, I use raw and it is also easier to get  Pink Dot Removal from a few apps that only use Raw files and not MLV.

Yup, if you don't need audio then .raw is IMHO superior performance-wise. On my 5D3 I can easily record continuous 1920X1288 on all of my CF cards in .raw. When I switch to .mlv, at times it seems like the camera can hardly keep up with 1920X1080 even with audio disabled.

When i adjust the white balance for a MLV file in MLRawViewer, it doesn't seem to stay with the file. I load another MLV file and then adjust the white balance for that file and extract to a DNG sequence. Now when I load the first DNG seq, the white balance did not stay and it shows the white balance from the last file I adjusted. What am I missing about this?

Hello Gary,

My understanding is that CDNG files are white balance agnostic. What that means is that while the metadata might have information relating to what your preferred white balance setting is, it's not married to the actual image. I think that the white balance and tonal adjustments in MLRawViewer are only applied to the ProRes export.

Maybe Baldand could comment?

It is also an industry standard to use the J K L keys where the K is for stop and play, J is Reverse and L is Forward. Tapping either J or L will increase speed in that direction. I think it is like 30% speed for each tap. I might be wrong, but there is a way for slow motion, fwd or rev. Maybe it is hold the K while tapping either J or L for slow motion increments in decreasing the speed.
Maybe these functions are not needed for this app. Take a vote from users if you are interested to add these functions.

Agreed, JKL is a known workflow that is used by many NLE's. I forgot about that, but I think it's a good point.

I would expect when MLV gets standardized and publicly released that a workflow standard will battle itself out.

Dreamer, you sure do live up to your name.   

You might want to read my somewhat rant-ish thread asking the same question.

I find .raw gives me better performance and has stronger existing conversion tools in the form of RAWMagic on the Mac, but if you need in-camera sound then you really don't have a choice.