User Selectable 2.35:1 record window?

Started by -Rogue5-, December 06, 2015, 12:01:23 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

-Rogue5-

Sorry if this is a no brainer,  I'm a long-time follower of ML dev, but have yet to use it.  I tried searching, but keep getting false-positive results, so I thought I'd better ask those more knowledgeable...

Anyway, is it possible to select which part of the sensor you want to record with ML (raw video or otherwise)? 

For example, on a 5D2, if I were shooting 1880x800/23.98fps (max 24p res for 5D2, right?), am I am able to make it record that 2.35:1 frame from the lower-half of the active sensor/image area?  A buddy of mine has a laser-damaged 5D2, but all the damage is in the top 1/2 of the sensor, so I was wondering if I could use ML to capture a 2.35:1 frame from the lower half of the sensor (where there is no damage).

reddeercity

Yes , in 3xCrop mode there Was a function called "Digital Dolly" which with the joy stick you could pan around the sensor with the crop window
while recording raw video so just more the crop window to where the sensor Not damaged , now here the kicker !
it's no longer supported/broken in the New nightly builds you must use very old builds
I used 2013 September build in this video and it shows the "Digital Dolly" feature . Now the video is not about that feature, it's about
the Clean HDMI Capture at that time of ML development and of course it was before Raw MLV 2.0 so it's just Original Raw 1.0 ,
on the good side of things with 5D2 you will be able to record continuous 2048x930 @ 23.976p without problem as long as you have at least a1000x CF (1066x better)
Hope that helps .
   
 

reddeercity

Quote from: -Rogue5- on December 06, 2015, 12:01:23 AM
For example, on a 5D2, if I were shooting 1880x800/23.98fps (max 24p res for 5D2, right?),
Not really in 1:1 mode max is 1872x1058 @ 23.976p+audio continuous(little un-stable thou I use 1872x936) with the New format MLV & in 3x crop mode
2048x1024 @ 23.976p for about 30-45 seconds continuous @ 2048x872.
In the older builds that was just the Raw 1.0 format max was 1880x1058 & 2048x930 in crop mode

a1ex

Quote from: reddeercity on December 07, 2015, 10:20:40 PM
now here the kicker !
it's no longer supported/broken in the New nightly builds you must use very old builds

Eh? I just tried on 5D2, with a recent build, and it's working fine.

Instead of recommending very old builds, do you mind creating proper bug reports?

reddeercity

Ok sure , never tried that feature with the newest builds .
My fault , sorry

-Rogue5-

Thanks for the replies reddeercity/a1ex!

Crud, I knew you could select where the record window is in crop mode, but I wanted to keep it full-frame/1:1 (otherwise I'd just use an APS-C camera)...  Also, I was saying that I'd *happily* shoot at 1880x800/2.35:1 (or, rather, 1872x780/2.4:1) as long as it's continuous+audio...  If I could move the record frame to the bottom half of the sensor (in *non*-crop mode), I'd be set!

So does that mean you can't select where on the sensor the record window is when shooting 1:1/full-frame?

reddeercity

Quote from: -Rogue5- on December 07, 2015, 11:15:40 PM
So does that mean you can't select where on the sensor the record window is when shooting 1:1/full-frame?
Yes that's right , 1:1 using the whole 5.6k sensor because of line skipping & pixel binding I think every third pixel or something like that .
That's the reason for the bad aliasing & moiré in 1:1 , not so in Crop as you are really using a 2k window the uses every line & pixel.
So hence the reason for the "Digital Dolly" to able to move around in the 5.6k  sensor .


-Rogue5-

Yeah, I understand.  That's why I was asking about shooting 2.35:1 and only moving the frame vertically (like "digital dollying") since 2.35:1 is ~2/3rd the height of 16:9...

Realistically, I could shoot 1872x936 (2:1), then crop to 2.35:1 and reframe in post, but I wanted to avoid the extra step, save some extra CF storage space, and reduce the potential for dropped frames (since there'd be ~15% less data throughput needed for a 2.35:1 frame compared to a 2:1 frame.)

Beggars can't be choosers.