Messages

I'm curious.. is 3x3 binning of the whole sensor possible (e.g. 1920x1280) or would that be too heavy to achieve reasonable frame rates?

Hmm... I haven't to my knowledge enabled burst mode.

Here's the MLV Dump output:

Code Select Expand

MLV Dumper v1.0
-----------------

Mode of operation:
   - Input MLV file: '34620000.MLV'
   - Verbose messages
   - Verify file structure
   - Dump all block information
File 34620000.MLV opened
File 34620000.M00 not existing.
Processing...
File Header (MLVI)
    Size        : 0x00000034
    Ver         : v2.0
    GUID        : 9730002281247010475
    FPS         : 1.#INF00
    File        : 0 / 0
    Frames Video: 1
    Frames Audio: 0
Block: RAWI
  Offset: 0x00000034
    Size: 180
    Time: 1741.469000 ms
    Res:  5936x3950
    raw_info:
      api_version      0x00000001
      height           3950
      width            5936
      pitch            10388
      frame_size       0x02721B98
      bits_per_pixel   14
      black_level      2048
      white_level      14783
      active_area.y1   80
      active_area.x1   138
      active_area.y2   3950
      active_area.x2   5934
      exposure_bias    0, 0
      cfa_pattern      0x02010100
      calibration_ill  1
Block: IDNT
  Offset: 0x000000e8
    Size: 84
    Time: 1743.813000 ms
     Camera Name:   'Canon EOS 5D Mark III'
     Camera Serial: '2C7A373949'
     Camera Model:  0x80000285
Block: WBAL
  Offset: 0x0000013c
    Size: 44
    Time: 1743.830000 ms
     Mode:   1
     Kelvin:   6800
     Gain R:   826
     Gain G:   1024
     Gain B:   330
     Shift GM:   0
     Shift BA:   0
Block: STYL
  Offset: 0x00000168
    Size: 52
    Time: 1743.839000 ms
     picStyle:   33
     contrast:   -4
     sharpness:  0
     saturation: -1
     colortone:  0
Block: RTCI
  Offset: 0x0000019c
    Size: 44
    Time: 1748.777000 ms
     Date:        27.07.2016
     Time:        18:53:22 (GMT+0)
     Zone:        ''
     Day of week: 3
     Day of year: 208
     Daylight s.: 0
Block: EXPO
  Offset: 0x000001c8
    Size: 40
    Time: 1749.435000 ms
     ISO Mode:   0
     ISO:        100
     ISO Analog: 72
     ISO DGain:  0/1024 EV
     Shutter:    269000 microseconds (1/3.72)
Block: LENS
  Offset: 0x000001f0
    Size: 96
    Time: 1749.457000 ms
     Name:        ''
     Serial:      ''
     Focal Len:   50 mm
     Focus Dist:  0 mm
     Aperture:    f/14.00
     IS Mode:     0
     AF Mode:     3
     Lens ID:     0x00000000
     Flags:       0x00000000
Block: VIDF
  Offset: 0x00000250
    Size: 41032632
    Time: 1754.484000 ms
   Frame: #0000
    Crop: 0x0
     Pan: 0x0
   Space: 0
Reached end of chunk 1/1 after 9 blocks
Processed 1 video frames
Done

I wasn't familiar with mlv_dump, thanks, that helps a lot.  I used a script command with it to batch convert all the MLVs to DNGs.  For my purposes that seems better than raw2cdng.

I tried it out again last night and the same thing happened again, each frame got its own .mlv file.  At least now I know how to get the DNGs out of it now.

Thanks for the help!

Lately I've been trying out the intervelometer in conjunction with the "Full Res" Silent Picture feature (set to MLV mode) on my 5D3, and have been capturing some great footage.

But yesterday I came home and my card was full of files that look like this:


It seems that instead of a series of .MLV .M00 .M01 .M02 etc. files, it was often creating a new .MLV file every other shot (or so I assume, since the file size of 40,072KB is double a normal raw image).  The larger .MLV files open in raw2cdng and mlrawviewer, but the smaller 40MB ones do not.

Is there any way for me to open/convert these files, or is this footage lost?

The only thing I did differently from what I usually do is I set the interval to 0sec instead of something slower.  Is the 0sec feature not stable enough to work reliably, or did I need to make sure some other setting was in order for it to work?