Messages

Battery grips can sometimes cause issues. I know for instance that Canon recommends removing battery grips when updating the firmware...so it must have some effect on the camera.

I think if you get a good Komputerbay card, your problems will go away and hopefully you can continue using the battery grip.

Even though my camera can handle files larger than 4GB, just from a practical/safety point of view I still limit my raw video files to 4GB. The thought is if something should go wrong at some point of the recording, hopefully with many smaller files, less footage will be lost.

You mean you don't use ExFAT, or do you mean you limit your takes to about 1 minute or less?

I think they're corrupted frames, but not necessarily skipped frames. I suspect the card might possibly be having some write errors, and if that's the case then it wouldn't trigger for recording to stop since no frames are actually being skipped.

A quick test would be to reduce the resolution to about half that, and see if the errors still occur. I suspect the footage will look fine since the card probably has enough bandwidth to handle the slower data rate.

Just a speculation.

Not sure about the diagnosis. Shouldn't "Frame skipping = off" just stop recording?

@joeydingding: The black frames doesn't by any chance happen after about 4 GByte?

I don't think the black frames are skipped frames.

Thank you, my diagnosis is that the problem is your card.

I'd suggest that you run some benchmarks and see what write speeds you're getting from it.

Hello, Im sorry!

I'm using the latest nightly build.
I'm using Felix 16GB 1000x UMDA 7 card
16:9 at max (continuously)
global draw live only

When I play the video in mlrawviewer I got black frames. The timeline stops when the black frames appears. But resumes afterwards.   Like eye-blinks

First of all, what camera are you using this on? You have 3 listed in your signature...and two of them can use ML. Secondly, the "latest nightly build" isn't good enough, you have to give us a date, the builds change on a daily basis. Thirdly, I haven't heard of "Felix" and I suspect this issue is related to the card. Fourthly, what resolution? Seriously, 16:9 at max means nothing without knowing what camera you're using or if you're in crop mode or not. Lastly...is Global Draw enabled while recording or not?

Please go and do some homework and come back when you can ask reasonably informed questions and give out the pertinent information that allows this community to try and help you.

I set up the camera for 1FPS and wanted to set the resolution to 1920 but at the bottom of the screen I see the following text.

At 1FPS, you're essentially doing time lapse photography and could just set up the intervallometer to do that and get yourself 4K resolution to boot.

The link shows a new methodology to do so without shutter actuations, but IMHO if you're not too concerned with shutter actuations, then the intervallometer method should work just fine.

My guess is that Resolve will need to be updated to support that format. The nice thing is that lately Blackmagic seems to be on a roll between the new firmware, selling the Pocket for half price, and Resolve 11.

Thanks! A Full length film.
Right now is in independent festivals and a couple of cinemas in my country, Argentina (Maybe the next futbol world championship

Hey Buda...looks like someone is trying to steal your thunder. You should let these guys know that you have already shot a feature film in Magic Lantern!!!

http://www.cinema5d.com/snowflake-first-feature-film-shot-with-magic-lantern-seeks-crowdfunding/

I don't think SD card cameras are your best choice for raw video shooting. You need to decide what's more important for you, raw video or still photography and then purchase the camera that fulfills that need understanding that the other function will have to suffer.

I've got some strange issue with Resolve 11 on Mac OSX 10.9.3 with Nvidia GPU. When I open cdng (mlv raw) clips after upgrade footage looks bad (strange anti-aliasing). When I go back to Resolve 10 it looks fine again. Is there any log in Resolve to check for errors ??

What is your raw playback quality set to?

Hello Phil,

I realize you're new here and I would highly recommend that you consider spending some time not only just messing around with your camera and learning by doing, but also reading as much as you can of these forums. While they might seem like a real time suck, it will help you by providing you with a lot of insight and ideas so that you can self-troubleshoot your issues.

I would also advise that you include some critical information along with any questions, such as your firmware revision, the nightly build that you're using, and whether or not you're shooting crop or non-crop, and .raw or .mlv.

I can answer question #2, and I don't know if it's a ML lantern but the way Canon names the files is based on the day and time, so for instance M16-0950 would be the name of any file shot right now. Unfortunately I don't know if ML has control over the name of the file, and the way to avoid such issue might be to make sure not to record two takes within the same minute.

Good question. You should start by watching this video:

http://youtu.be/AJzgpIdoUqw

I have yet to have to reconnect footage from Resolve to other NLE and back to Resolve when switching between CDNG and ProRes, so I don't have experience doing what you need, however I know it's totally possible and doable.

I got the same error yesterday while shooting. My card was 100% formatted ExFAT...no doubt.

Weird as I have never encountered it before. This was on a 5D3 running 1.1.3 and a May 16th build. Global Draw was On and I was shooting 1920x1080 at 24.

Happened again yesterday when shooting on the 5D3 on my May 16th build. I got the error "Are you sure Card is ExFAT?" and in this case I am 100% sure the card was formatted as ExFAT.

Thankfully it appears the file integrity is fine.

Could this discovery lead to higher resolutions of Raw video in full sensor mode?

From the first post:

4K video?

Too early to ask. Find a way to speed up the capture process first (see the research section below).

However, I don't really expect more than 10 fps (in LV crop mode on 5D3, 1/3.6 of the total sensor area is sampled at 30fps). If you implement a burst mode from the current code base, you'll get up to 5 fps.

Oh I see.

I wonder if he re-formatted the card in camera without really thinking that it would turn the card back into a regular FAT format, but still left the ExFAT option on in ML?

Raw files shouldn't be .mov files. The should be either .mlv or .raw.

i have a project coming up where I can use my 5dm3 or a red one mx...(since I haven't shot on the red mx) which one do you think is better for a feature project??

Hate to say it (on an ML forum), but any time you have a chance to use a "pro" camera, use the pro camera. That's not to say that the RED One doesn't come with its own set of issues, but it's field proven over and over and it's a professional camera. ML is a hack, a damn good one at that, and one that I certainly like to use, but a hack nonetheless.

What you get with RED One is access to PL mount lenses, slow motion, no BS monitoring and playback, good audio inputs, and a raw format that technically doesn't require any transcoding of any sorts since most NLEs can deal with it natively. My main annoyance with the RED One is its proneness to crash or develop weird quirks that require restarts. Usually the rebooting process can suck up to 3 minutes which on a set can feel like forever. Plan accordingly.

I'm suddenly experiencing a bug where thin magenta vertical lines appear on the viewer (see pic below) whenever I click on a GUI icon, which then subsequently appear on the render.

Did MLRawViewer always do this or was it working just fine a few days ago? I have to wonder if it has anything to do with the OS you're using, but obviously not if it was working just fine a few days ago.

Best way is to use a heavy blur filter on all the .raw footage!   

I gotta tell you, the 5D3 with raw never ceases to amaze me. If you'd told me that you shot that on an Alexa, or even 35mm, I would have believed you.

Wow, looks amazing.

What did you shoot on?

If none of the above are possible or problematic, then being able to watch the footage shot that day on the set while still on the set,  would be very helpful.

With regards to playback of RAW footage on set, is it possible to load Da Vinci on a laptop and watch the native RAW files directly from a card reader or similar workaround?

We love the look of RAW but would love it more if a reliable, decent monitoring solution could be found - it would be a real Godsend for us here in the midst of a low light horror feature, where gremlins abound and Santa Clause waits patiently somewhere in the 5D chimney.   
   

With only 2 posts under your belt, I'd venture to guess that you haven't done a whole lot of reading around these forums. I also have no idea about what you mean by "5D Santa Clause."

The key to successfully shooting in ML raw in a demanding situation is twofold, good monitoring on the set and a capable and knowledgeable DIT. Shooting anything of substance with ML raw without a good DIT on set is a very frustrating experience IMHO.

Regarding good monitoring, I'm talking about a monitor large enough to provide a clear view while also providing much needed focus peaking and zebras.

About the DIT, I mean someone who really knows the tools available such as the excellent MLRawViever and who can provide on set playback quickly and efficiently while also getting a jump on the time consuming conversion process.

Are spatial and temporal noise reduction available in the Lite version?

No, otherwise why would they bother having a paid version?