Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - kaco

Pages: [1]
Raw Video / How to get a proper crop_rec 1080p48 preview?
« on: September 02, 2018, 04:07:39 PM »

Thank you everyone involved in development of ML, I am shooting raw since the very beginning it came out (, Almost every week I shoot approx 2-5 Tb of data.

Squeezed 48p is still great, but the resolution is not much.

I would love to switch to crop_rec 48p 3x3 binning, only not sure how you work with the preview? With the BW low resolution preview in is really hard to focus.

Is there any chance to port this new module to 5D3 FW 1.2.1 and then use HDMI viewfinder? And then ultimately hack the HDMI feed with some red cross when not recording (Since I experience frame skipped from time to time, it would be great to know from the feed if the camera is recording or not).


Feature Requests / [DONE] FPS override to 36fps
« on: January 23, 2018, 10:03:28 AM »

Is there any fundamental reason why FPS override settings is disabled to the value of 36? (When you scroll on FPS override it jumps from 35 to 37)

Having 36fps would mean better workflow for documents - 150 % for slowmo, blending every third frame for real speed. Realtime playing back 35/37fps footage in 24fps sequence brings much more problems.

Thank you,

Raw Video / 5Dm3 10-bit aperture moving while shooting
« on: July 31, 2017, 01:11:20 PM »

I've been using MLraw a long time for a weddings. Since january I started using 10bit 37fps instead of squeezed 48p. I found a little flickering in the image, but I though it is some kind of a problem with FPS override.

I found out that the aperture is slightly changing it's size while shooting. You can see the problem here, pay attention to how the aperture is floating all the time.

Tested also with the latest build 2017-07-02 22:47 and the problem is still there.

5D mk3, FW 1.1.3.
Lens: Canon 35mm f/2 IS (IS turned off for this test)
FPS override: desired 37, optimize for Exact FPS, actual fps 37.001
I can see the problem on f/2.2, f/2.4, f/3.2, f/3.5, f/4.5, f/4.9, f/7.0, f/9.1...
The aperture is okay (fixed, not moving) when on f/2.8, f/4, f/5.6, f/6.4, f/8,...

Second problem: Sometimes I am not able to change aperture while shooting. In the bottom-left corner I see a sign "BUSY" and the aperture changing does not work. When I press "Q button", the "BUSY" sign will get away and everything starts working again. See the problem here:

Raw Video / BUG 5Dm3 113/123 ISO screen stuck during raw recording
« on: December 06, 2016, 01:16:10 PM »
Hi guys,

I've been shooting hours of raw with ML, thank you! However, with latest builds from 2016, there was introduced bug, which makes ML raw unusable for me. In documentary, we have to change ISO a lot even during recording.

Here's the bug reported:

Feature Requests / Global Draw in HDMI output
« on: November 08, 2016, 06:06:06 PM »
Is there a chance to include global draw into the HDMI mirrored stream? It would be great to be able to use EVF and still see if the mlv_rec module is rolling for instance.

Raw Video / Empty 82 Gb MLV file?
« on: July 19, 2014, 09:07:16 PM »

I've got one 82,2 GB (88 354 624 096 bytes) MLV file and I cannot read it. Could someone please help me to investigate if the file is totally empty, or just partially corrupted?

We shoot whole day on many cards. Card containing this file had previous and next MLV without a problem. We even do not remember any on location problem. Maybe the battery run out during recording? We really can't remember. We shoot with the some build from feb to may, but don't know exactly which (we updated the cards in the meantime.

Here's some details:
Code: [Select]
K:\>mlv_dump -v M07-1702.MLV

 MLV Dumper v1.0

Mode of operation:
   - Input MLV file: 'M07-1702.MLV'
   - Verbose messages
   - Verify file structure
   - Dump all block information
File M07-1702.MLV opened
File M07-1702.M00 not existing.
[ERROR] Invalid block size at position 0x00000000
Processed 0 video frames

Here's the screenshot from HxD:

How could the camera create 82 gigs of zeros?

Pages: [1]