Messages

Any suggestion is greatly appreciated:

Using 5dIII 1.2.3,  the storage card is: SanDisk Extreme Pro 128GB, 160MB/s. 

I followed the steps to use crop_rec. Downloaded and installed the Dec 2017 version.  Shot video using the steps as per the video in this forum a few pages back, and the MLV files were created.  But when I import the files into Resolve 14, all I get is noise.  I have successfully did the same procedure with the regular 5dIII 1.2.3 Dec 2017 release (not crop_rec), and everything works fine.  (Just shooting 1920x1080 24p).  Resolve imports the files and they can be edited.

My overall goal is to shoot 1920 x 1080 48p, but I have never been able to do that either using crop_rec.  Same thing, the files seem to be corrupted.  I purchased the EosHD Shooter's Guide (from EOSHD.com), which explains a lot and is helpful.  I followed the steps there.  Same thing, the MLV files seem to be corrupt when imported into Resolve 14.

So basically, to sum up:  I have not had any success creating editable MLV files using the crop_rec release.

Any suggestions are very helpful and appreciated as to the corrupted files problem.  Must be some setting I am missing.  But no idea at this point.  Thanks in advance.

When doing regular videos (no ML) with my 5DIII I have been told to set the shutter at twice the frame rate.  So for 30  FPS I would set the shutter to 1/60. 

My question is -- Now that I have ML  do I need to or should keep doing this? I tried other settings and it doesn't seem to have any impact.

I would like the freedom to set shutter faster so that I can open the lens more without the need for a ND filter.   At a shutter speed of 1/50 (for 24 fps) and in shutter priority mode, the camera set the aperture to f11.  I shot some video. I then changed to aperture priority mode and set the aperture to f5.6, which is more so where I wanted it.  I recall the shutter going to 1/320 or so.  I shot more video.  It didn't seem to make a difference in the final product, and the final video was properly exposed. 

I would love to hear comments on this.  Thanks. 

It seems to me that the key technology is to be able to read directly from the sensor and then process that information rather than going through Canon's OS.  Experts on the Canon 5DIII's bus architecture would know if the hardware is in place to be able to address and access all of the sensor's pixels, or if Canon just put in place what it needed for the feature set it wanted to market.  If the entire sensor can addressed and accessed, then for video it becomes a matter of sampling the sensor periodically (30, 60 or 120 times per second) and then processing and storing that data.  The internal hardware and bus architecture will be a limiting factor at some point. Just what that point is determines what can be done.