Messages

As developer (but not yet involved in the raw_rec recording dev) I see some options to improve the raw recording or add an option for slower cards:

1) if there is enough RAM / Cpu cycles left: I think the best way would be to use lossless compression to do the job. I can imagine this will move the problem to the processor, but there is a chance...

2) add an option to convert to 8bit raw? This will most probably introduces some nasty banding effects, but I am not sure if that is noticeable in real situations? This is quite easy to test and code I guess.

I can't see why I would want either one of these options for myself. Just buy faster cards.

Does anyone know when we may expect to be able to test file spanning?

Has anyone tried 5D3's new firmware with ninja2? I am wondering if it's possible to record internally as well as through hdmi on ninja2.
When 5D3 firmware 1.2.1 is supported by ML, it would be nice to record prores proxy to ninja2 and to record 14bit raw internally. I may be wishing too much.

Someone stated that the 4GB file limit is a constraint the Magic Lantern people put on it while its in experimental stage. They will remove it at some point.

Is this true or not?

I just shot a 4G clip with an external monitor plugged in.  ML reported 8 skipped frames at 1080p on my Lexar 1000x card which is the same as what it reports when I'm on the internal screen.  I haven't looked at the footage, but I'd expect it to be fine.

I just tried it myself and yes, it seems to work fine except for one. Did you notice oddity on frame overlay when shooting 1080p? It looks way off center. Although footage looks good.

The tearing fix is eating quite a bit of RAM. Exmem is not yet fully understood.

That explains! Thanks.

Has there been any development about removing 4gb limit?

Has anyone tried this raw shooting with a hdmi monitor? I assume it won't affect anything, but want to confirm it if anyone tried.

Has there been any development about removing 4gb limit?

Its just set to stop recording at 4gb in the code.

Is this precautionary limit in the code? Will this be removed later?

nope.

It's no because?

I assume someone had already thought about this or at least asked a question like this, but just in case, with the new 5D3 firmware, whenever it becomes compatible with ML, would it be possible to feed this raw directly to Ninja2? I wonder if atomos will look into it also unless there is legal issues with canon.

Its just set to stop recording at 4gb in the code.

What does that mean? There is no actual limit then? We can keep recording?

I can record sound now to the SD card. I did a quick test. I did not want to change any code. I went to the canon menu set up1 and selected record to sd card. I went to magic lantern menu for sound recorder. I started sound recorder. I went back to same canon menu before put back to cf card. I was able to record video at 1080p. This means it is possible. The issue is when I start video recording the audio switch from 48hz to 96hz for some reason. I had to change the sample rate to 96hz to play back the audio correctly.

Interesting! I will try this too. Thanks!

Is global draw off? It's working fine for me with a 600x Lexar

With only focus peaking enabled, I can get stable 1280x720. With peaking and histogram on, I get stable 1280x540.
I will order a lexar 1000x card soon. If I can get stable 1920x720, that would be great.

Hmm.. with the current version, I get drop frames at 1280x720. I used to get stable 1280x720 with previous version. Is this expected?

Here is the current compiled version for the 5D Mark III
https://docs.google.com/file/d/0B7QlH_BH2m32T3RSTXRUM1VXTWM/edit?usp=sharing

Thank you!

Is anyone using Lexar 1000x card on 5D3? I am wondering if full 1080P is stable with this card. Or even higher?

Is lourenco back with newly compiled 5D3 files? Or can anyone else post them please?

The tearing fix module seems to work smoother.

Can you share your compiled files with this fix?

confirmed happening on 5d2 for me during my testing.

I could be wrong, but it seems to be happening when camera is moving. Is that the case for you as well?

Has anyone had an issue with either top third or bottom third tearing on a frame?

lourenco, how did you record sound with this? Did you start raw shooting and then start movie shooting together? Then later sync the sound?

Is there a chance i get some help converting this .raw to .dng?
I downloaded the raw2dng, but when opening it opens and imediatly closes. I supose that there is some specific command to be introduced in the cmd.exe in order to make it process the image.

I'm running windows 8 and tried some compability modes, no luck what so ever.

Thank you

I put raw2dng and raw file in a folder together. from cmd, go to that folder and type raw2dng mxxxxxxx.raw
you'll see dng files created in that folder.

Please download the new version I just posted. You need to load the module under menu option M for Module. You will see the new raw movie shooting option on the ML movie menu.

I will have to compile a newer version later tonight when I have time. I notice some new changes have been mades since I last compiled. Maybe someone else could post a link until that time?

Thank you for your help! To shoot in raw, can I start with start/stop button or should I click start from ML menu?

I just downloaded the compiled version (thank you, lourenco), but I don't see this raw shooting menu. Do I need to turn something on to be able to get to this option?