mlv with .M01, .M02, .M03......

Started by Nang, April 13, 2014, 10:50:18 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Nang

Hey guys,

Anyone know why I would get extensions like .M01, .M02, .M03, .M04 etc etc? All of them are showing 1KB. I'm using Nightly.2014Mar24.5D3113 build on 5d3 and shooting mlv + sound in 1920x1080.

Thanks


Portfolio: somnang.4ormat.com | Video: https://vimeo.com/somnang
Prime: Olympus Zuiko OM 24mm f/2.8 | Rokinon Cine 85mm T/1.5 | Pentax SMC Takumar 50mm f/1.4 | Helios 44-2 58mm f/2.0 | Jupiter 37A 135mm f/3.5
Zoom: Meteor 5-1 17-69mm f/1.9, Sigma 18-35mm f/1.8, Tamron 24-70mm Di VC f/2.

g3gg0

mlv_rec creates them when recording starts.
This saves you lags during record if your files tech the 4GiB border and a new one has to be created.
When you stop recording, it will delete all those empty files and you should only get the ones with video data.

Does this always happen to you?
Did you try a recent version?
Any crashes or abnormal recording aborts?
Help us with datasheets - Help us with register dumps
magic lantern: 1Magic9991E1eWbGvrsx186GovYCXFbppY, server expenses: [email protected]
ONLY donate for things we have done, not for things you expect!

coryaycock

Today, I was shooting a scene and my two 64GB cards filled up very very quickly.  We had to stop shooting, I ran home, unloaded one of the cards, and the MLV's were there but so were numerous .M00's, .M01's, .M02's, .M03's, etc with each clip.  Some of the extra .M0's were 4GB's!  I had to take magic lantern off and shoot JPEG's to finish the scene. 

I love Magic Lantern, but why would this happen?  I didn't do anything differently than I have before. 

Canon 7D
Nightly Version 2015Feb20
All settings normal--23.976 fps, 48 Shutter, 1728x 972, etc. 

Frank7D

Shooting mlv at 1728x972 at 23.976 fps will get you about 15 min. of video on a 64 GB card.
If you're not used to seeing .M00 etc. then you probably don't usually shoot more than about a minute per clip at those settings. Anything over 4 GB and you will see the spanning files.

coryaycock

I guess I just didn't notice them before because they weren't taking up much space.  This time, 4.29GBs.  This is normal? 
And after just reexamining the clips, they're all cutting off at 1458 frames for some reason. 

So, basically I got 6 minutes of footage for 128 GBs.
I'll keep checking to see if I did something wrong but I'm almost positive I didn't.

Walter Schulz

Do the math:

Your file with 4 GByte (or 4,096 MByte or 4,194.304 kByte or 4,294,967,296 Bytes) contains 1458 frames with 2.8 MBytes each.
A RAW frame is calculated by
Vertical resolution x horizontal resolution x 14 / 8 = 2,939,328 Bytes (for your settings)
Or 2.8 MBytes.


coryaycock

Hey Walter, how about you do the math.  Oh, you already did.  Thanks!

Licaon_Kter

Whats your MLV processor? It should load the M00..Mxx by it self anyway.


Try this, load the MLV and check the frame number.
Move all the files EXCEPT the MLV (to some other folder) and THEN open the MLV and see what frame number you've got.


If it's the same then your program does something wrong. Try MLVFS ot MLRAWVIEWER.

coryaycock

Hi.  I isolated the MLV's first thing from the others and no luck getting past 1458 frames, and I just tried it again.  I talked to my camera operator earlier and he said it was showing on screen that we were rolling the entire take, which was longer than 1:01 (1458 frames).  In the past (different ml version) I was shooting up to 9,000 frames at a time, no problem, and MLRaw Viewer has never disappointed in the past. 

It's ok though.  It was ambitious using Magic Lantern for the scene but we ended up getting enough footage to get us through despite the early cutoffs. Thx :)