paulinventome

Beg to differ on this one ?
If you have a high contrast edge and use various scaling algorithms, Lanczon, Sinc, etc,. Often the scale results in negative lobes (like a curve overshoot). It's quite easy to see this. Happens in compositing all the time. It's exacerbated by working Linear as we always do (i suspect because of the dynamic range). So it's a well established trick to cover to log, scale, and convert back to linear. I suspect some apps do this automatically (maybe resolve does, i don't know)
https://www.sciencedirect.com/topics/computer-science/ringing-artifact
It's a bit geeky but there's a diagram of a square pulse and lobes that extend beyond it.
Sony had this issue in camera on the FS700, very bright edges would give black pixels as the scale went negative.
My gut tells me in the case of a bayer sensor it could be even worse - partly because of the negative signal but also the tendancy to have stronger edges because of missing bits of image?
Kindest
Paul
 
Cool.
But are they not just taking each RGGB into a separate greyscale image, so you have 4 grey images roughly 3000x1250. Scale those to 1920x1080. Then create bayer data for 3840x2160 by just alternating pixels to build up the RGGB again?
So we are maybe seeing artefacts in the scale process based on algorithm used. It might even be nearest neighbour which is what i think you're demonstrating - when you take an existing pixel and alternate to make up the UHD image.
But if that scale is done properly - is it not going to improve the image OR is the fact that scaling those 4 layers, which are already missing pixels in-between actually makes it worse?
The Ideal is take each RGGB layer then do an interpolation, so that instead of going from 3K (one channel) you interpolate that up to the full 6K by interpolating the missing pixels and *then* scale it down to to 1920 and then the resulting bayer image might actually look really good....?
cheers
Paul 

I processed the first frame with Resolve and with Rawtherapee (which includes very fine-grained, expert debayering controls). When tuning the debayering in Rawtherapee, choosing AMaZE as the demosaicing algorithm with 'border' set to 4 and 'False color suppression steps' set to 5, the result is visibly better than from Resolve, but still far from perfect - see the attached frame grabs:
 

Rawtherapee
 

Resolve

I think the Rs are good for photography because they tend to show two different renders wide open (glowing) and stopped down, especially the Mandler designed ones (the lux's you quote). I found the 90 summicron very poor with flare, almost unusable. The 24 is not a Leica design and it shows. And the 28mm f2.8 Mark II is excellent. The last version of the 19 pretty good too, much better than the contax 18. 
Yes, i have focus gears for the M lenses. Studio AFS make some aluminium gears that you can twist on, like the Zeiss gears but they do them with scalloped inserts that will hold around the smaller barrels of the Ms. The Zeiss versions don't go small enough. They're really good and easy to twist on and off when needed.
The issue with the Ms are cost. I'm heading for a 90 APO and the latest 28 summicron. But i may have the sell the first born. But actually you get what you pay for (up to a certain point)
I don't find Resolves debayer very good. I am trying to get some fixes to Nuke that will allow these DNGs to go through there. 
I don't see there being any reason why we should see coloured pixels if the algorithm understands what the content is, right? I mean it's all recreated - so why false colours? In this case i believe this artefacts look like the AHD(?) algorithm.
cheers
Paul

In practice, you can switch forth and back between full frame 4K raw and APS-C 4K raw video recording without great image quality penalty. (The difference in noise and resolution is IMHO invisible if you master in 1080p). And you can put the full frame vs. APS-C crop switch on the camera's quick access menu.
That effectively turns any prime lens into a dual-focal length lens - or virtual dual lens turret. Often, this makes a zoom lens unnecessary in the field.
It's a neat (and often overlooked) little feature of the camera.

As promised, the Sigma fp centered release of slimRAW is now out, so make sure to update. SlimRAW now works around Resolve's lack of affection for 8-bit compressed CinemaDNG, and slimRAW compressed Sigma fp CinemaDNG will work in Premiere even though the uncompressed originals don't.
There is also another peculiar use: even though Sigma fp raw stills are compressed, you can still (losslessly) shrink them significantly through slimRAW. It discards the huge embedded previews and re-compresses the raw data, shaving off around 30% of the original size. (Of course, don't do this if you want the embedded previews.)

Thanks for Clarifying officially!
If you actually do this then the settings are Color Space: Blackmagic Design, Gamma: Blackmagic Design Film. The gamma curve brings all the range in and the colourspace is BMD.
What does that actually mean though, you say that it won't touch gamut?
To try and understand i use the CIE diagram scope. And setting the DNG to P3 vs BMD Film 1 (in a P3 timeline) i see the first two diagrams. First is BMD Film into a P3 Timeline and the second is debayering P3 into a P3 timeline.
Now this is basically a point of confusion in Resolve for me - to understand what resolve is actually doing in this case. A saturated Red in sensor space in the DNG is transformed into 709/P3/BMD Film - but is that saturated Red actually mapped into the target space or is it placed at the right point. I cannot work it out. So for example if that sensor Red is outside of 709 space then IMHO Resolve could either clip the values or remap them. But if you switched to P3 and that Red lay within it then no mapping has to happen.
But on the CIE diagram i do not see this. I would expect to switch between 709 and P3 and the colours inside the triangles not move. In other words in a sufficiently large colourspace on that CIE diagram i ought to be able to see what the camera space is (ish).
So when i do this and choose BMD Film and set the timeline to that as well i get the 3rd diagram - which is beyond visible colours
so i have to assume i just don't understand what Resolve is doing here or that CIE diagram is not working?
Any light shed (pun intended) would be super nice!
cheers
Paul
 

"BMD Film" (version 1 which will be applied to non-BMD DNGs) will just apply a log type gamma curve and not touch colour (gamut). So you will be getting Sigma fp sensor RGB space in terms of gamut and no colour 'errors' except that a sensor response isn't meaningful on a display. To transform into a common display space would not be straight forward though unless Sigma or someone provided the correct conversion, so unless you could get something you're happy with by manually correcting the colours it might be easier and more straight forward to decode into a known defined space like 709 or something and go from there.

Since I found the YouTube comparison between the Sigma fp and the Blackmagic Pocket Cinema Camera 4K so worthless, I did a comparison test of my own.
I wanted to compare the cameras in two respects: 
(1) dynamic range when shooting a high-contrast subject under optimal light/with optimal exposure + robustness in grading the resulting image;
(2) low light/extreme high ISO image.
My setup was as follows:
Completely dark room; Both cameras with the same lens, Tokina 28-70mm/2.8 (Nikon mount adapted to L-mount and MFT respectively) at the same aperture setting (f4) on both cameras, but at 35mm focal length on the Pocket 4K and at 70mm on the Sigma fp to compensate for the different sensor sizes; Record settings: UHD 23.98p on both cameras, full frame CinemaDNG 12bit on the Sigma fp and BRAW Q0 on the Pocket 4K (= best quality codec settings on both cameras);  For the high-contrast test: daylight-temperature LED fresnel with maximum focus/spotlight on a plastic appliance reflecting some of the light to create high contrast; both cameras at minimum/native ISOs exposed ETTR/to the right. Both cameras set to 11.25 degrees shutter angle (in lieu of an ND filter, since motion rendering is irrelevant in this test).
(Note: Lowest, respectively native, ISOs on the two cameras are ISO 100 on the Sigma fp and ISO 400 on the Pocket 4K. Never mind that nominal difference, both cameras have almost identical clipping behavior at these settings, i.e. ISO 100 on the Sigma fp behaves like ISO 400 on the Pocket 4K. On both cameras, the zebras turned out to be reliable indicators for sensor clipping: To go absolutely sure that I would optimally expose the sensor, I also shot the scene at larger shutter angles - 22.5, 45, 90 and 172.5 degrees -, with zebras popping up as early as at 22.5 on both cameras. When looking at the material in Resolve, this was indeed where clipping had occurred and waveforms remained clipped in the RGB parade even when lowering exposure in Resolve's Raw control tab.)  For the low-light test: same 'scene' as above, but with the LED fresnel turned off and only a practical light in the background turned on. Both cameras set to maximum ISO (256.000), at f4 and 172.5 degrees shutter angle. Treatment in Resolve:
Basic image adjustments only in the Raw tab, interpretation in P3 color space with Rec. 709 gamma: adjustment of white balance/tint and exposure to make the Sigma fp and Pocket 4K footage match. (The raw material of the Blackmagic Pocket 4K was much warmer than that of the Sigma fp with the same Kelvin settings...) No highlight recovery. (Wasn't necessary anyway since there was no clipping in the images.) No noise filtering or sharpening, although the Pocket 4K's BRAW codec already has some baked-in temporal noise filtering. For the extreme grade, only a solarization-like custom curve was applied that pushed the shadows to the maximum and was meant to provoke banding in the material by pushing contrasts:
I exported 16bit TIFF screengrabs which can be downloaded here (6 TIFF files in a zip archive, 133 MB).
Here's how the well-exposed high-contrast scene looks like (25% downscaled images):

Sigma fp

Pocket 4K

- Note that the difference in sharpness may be my user error, and is also influenced by the different depth-of-field between 35mm/f4 on MFT and 70mm/f4 on full frame. The manual focus aides on the Pocket 4K are much better with latest firmware, so nailing focus without an external monitor was easier.

1:1 crops of the above two images:
 
Sigma fp (left) - Pocket 4K (right).
 
Extreme grade, with the same curve (as posted above) applied to the two above images:


Sigma fp

Pocket 4K
1:1 crops of the above:

Sigma fp

Pocket 4K
 
Low light, with both cameras at maximum (256,000) ISO, 172.5 degrees shutter and f4:

Sigma fp

Pocket 4K
1:1 crops of the above:

Sigma fp

Pocket 4K
So, to summarize, I think it's fair to say that the full-frame 12bit CinemaDNG material of the Sigma fp simply shows the benefit of a larger sensor and its lower image noise (even at base ISO if you compare the full-size TIFFs). It's thus only logical that it holds up better in extreme grades and in low light.
My likely user error in nailing the focus of Sigma fp also shows the strengths of the Pocket 4K, namely better camera assist functions and overally a better user interface/more practical user experience for video shooting. - But it's also nice to see that the Sigma fp has some genuine advantages over the Pocket 4K, especially for my own type of videomaking which revolves around event videos (concerts at indie/DIY venues) shot in extreme low light conditions.
 

That's very kind of you, thank you.
Post is minimal at the moment however i think one 'trick' is that i have this as a Resolve project which is YRGB Color Managed, my timeline is 709, output colourspace is 709 but my Timeline to Output Gamut Mapping is RED IPP2, with medium and medium. (Input colourspace is RedWideGamut but AFAIK when dealing with RAW and DNGs this is ignored)
This is because most of the project is Red based. BUT the sigma fp footage is debayering into 709 (So in Camera RAW for DNG is it Colourspace 709 and Gamma 709 with highlight recovery by default).
What happens is that the DNGs are debayered correctly, with full data. But that IPP2 mapping is handling the contrast and highlight rolloff for my project as a whole, including the DNGs. IMHO i do this all the time with various footage, not least because it's easier to match different cameras but mostly because that IPP2 mapping is really nice.
Whilst i'm sure you can massage your highlights to roll off softly, it makes more sense for me to push footage through the same pipeline.
Take some footage and try. When you push the exposure underneath IPP2 mapping the results look natural and the colours and saturation exposes 'properly' Turn it off and then you're in the land of saturated highlights and all sorts of oddness that you have to deal with manually. This is not a fault of the footage but the workflow. Running any baked codec makes this more difficult - the success of this approach is based on the source being linear and natural.
As i say the fp is like an old cine camera, the bells and whistles are minimal but if you're happy manual everything i think it can produce lovely images and it's so quick to pull out of a bag.
If the above doesn't make sense let me know and i'll try to put together a sample.
Cheers
Paul
insta: paul.inventome

That's very kind of you, thank you.
Post is minimal at the moment however i think one 'trick' is that i have this as a Resolve project which is YRGB Color Managed, my timeline is 709, output colourspace is 709 but my Timeline to Output Gamut Mapping is RED IPP2, with medium and medium. (Input colourspace is RedWideGamut but AFAIK when dealing with RAW and DNGs this is ignored)
This is because most of the project is Red based. BUT the sigma fp footage is debayering into 709 (So in Camera RAW for DNG is it Colourspace 709 and Gamma 709 with highlight recovery by default).
What happens is that the DNGs are debayered correctly, with full data. But that IPP2 mapping is handling the contrast and highlight rolloff for my project as a whole, including the DNGs. IMHO i do this all the time with various footage, not least because it's easier to match different cameras but mostly because that IPP2 mapping is really nice.
Whilst i'm sure you can massage your highlights to roll off softly, it makes more sense for me to push footage through the same pipeline.
Take some footage and try. When you push the exposure underneath IPP2 mapping the results look natural and the colours and saturation exposes 'properly' Turn it off and then you're in the land of saturated highlights and all sorts of oddness that you have to deal with manually. This is not a fault of the footage but the workflow. Running any baked codec makes this more difficult - the success of this approach is based on the source being linear and natural.
As i say the fp is like an old cine camera, the bells and whistles are minimal but if you're happy manual everything i think it can produce lovely images and it's so quick to pull out of a bag.
If the above doesn't make sense let me know and i'll try to put together a sample.
Cheers
Paul
insta: paul.inventome

So i said i'd post some stills, these are basically ungraded.
This frame is in a sequence with car lights, i like the tonality of this very subdued moment. Shot 12bit to manage shadow tonality.

From a different point above. All shot on a 50mm M Summicron probably wide open.

I think i hit the saturation slider here in Resolve. But this had car rolling over camera. It's a 21mm CV lens and i see some CA aberrations from the lens that i would deal with in post. But i'd never let a car run over a Red!

shot on an 85mm APO off a monopod. Nice tonality again and it's day light from windows with some small panel lights bouncing and filling in

A reverse of the above.

Some fun shots.
I think the true benefit of something like the fp is the speed at which you can see something and grab it. Using it just with an SSD plugged in and manual M lenses gives a more spontaneous feel. Now most of the film will be shot on Red, in controlled conditions with a crew and that's the right approach for multiple dialogue scenes and careful blocking. But the fp has it's place and i may hand it too someone and just say grab stuff.

 
cheers
Paul

So i said i'd post some stills, these are basically ungraded.
This frame is in a sequence with car lights, i like the tonality of this very subdued moment. Shot 12bit to manage shadow tonality.

From a different point above. All shot on a 50mm M Summicron probably wide open.

I think i hit the saturation slider here in Resolve. But this had car rolling over camera. It's a 21mm CV lens and i see some CA aberrations from the lens that i would deal with in post. But i'd never let a car run over a Red!

shot on an 85mm APO off a monopod. Nice tonality again and it's day light from windows with some small panel lights bouncing and filling in

A reverse of the above.

Some fun shots.
I think the true benefit of something like the fp is the speed at which you can see something and grab it. Using it just with an SSD plugged in and manual M lenses gives a more spontaneous feel. Now most of the film will be shot on Red, in controlled conditions with a crew and that's the right approach for multiple dialogue scenes and careful blocking. But the fp has it's place and i may hand it too someone and just say grab stuff.

 
cheers
Paul

That's very kind of you, thank you.
Post is minimal at the moment however i think one 'trick' is that i have this as a Resolve project which is YRGB Color Managed, my timeline is 709, output colourspace is 709 but my Timeline to Output Gamut Mapping is RED IPP2, with medium and medium. (Input colourspace is RedWideGamut but AFAIK when dealing with RAW and DNGs this is ignored)
This is because most of the project is Red based. BUT the sigma fp footage is debayering into 709 (So in Camera RAW for DNG is it Colourspace 709 and Gamma 709 with highlight recovery by default).
What happens is that the DNGs are debayered correctly, with full data. But that IPP2 mapping is handling the contrast and highlight rolloff for my project as a whole, including the DNGs. IMHO i do this all the time with various footage, not least because it's easier to match different cameras but mostly because that IPP2 mapping is really nice.
Whilst i'm sure you can massage your highlights to roll off softly, it makes more sense for me to push footage through the same pipeline.
Take some footage and try. When you push the exposure underneath IPP2 mapping the results look natural and the colours and saturation exposes 'properly' Turn it off and then you're in the land of saturated highlights and all sorts of oddness that you have to deal with manually. This is not a fault of the footage but the workflow. Running any baked codec makes this more difficult - the success of this approach is based on the source being linear and natural.
As i say the fp is like an old cine camera, the bells and whistles are minimal but if you're happy manual everything i think it can produce lovely images and it's so quick to pull out of a bag.
If the above doesn't make sense let me know and i'll try to put together a sample.
Cheers
Paul
insta: paul.inventome

I'm hoping supply of used ones increases over there by the time I arrive as its a bit hit and miss when I check stores at the moment.
God forbid I have to buy a new one and only save £800
 

@paulinventome those shots look gorgeous. What is your post workflow? 
I think an FP may be in my future if you keep posting more shots like this.
Maybe @BTM_Pix will pick up an extra one for me when he heads Japan.
Btw, that last shot is insanely good!!!

Looks good! 

So i said i'd post some stills, these are basically ungraded.
This frame is in a sequence with car lights, i like the tonality of this very subdued moment. Shot 12bit to manage shadow tonality.

From a different point above. All shot on a 50mm M Summicron probably wide open.

I think i hit the saturation slider here in Resolve. But this had car rolling over camera. It's a 21mm CV lens and i see some CA aberrations from the lens that i would deal with in post. But i'd never let a car run over a Red!

shot on an 85mm APO off a monopod. Nice tonality again and it's day light from windows with some small panel lights bouncing and filling in

A reverse of the above.

Some fun shots.
I think the true benefit of something like the fp is the speed at which you can see something and grab it. Using it just with an SSD plugged in and manual M lenses gives a more spontaneous feel. Now most of the film will be shot on Red, in controlled conditions with a crew and that's the right approach for multiple dialogue scenes and careful blocking. But the fp has it's place and i may hand it too someone and just say grab stuff.

 
cheers
Paul

So i said i'd post some stills, these are basically ungraded.
This frame is in a sequence with car lights, i like the tonality of this very subdued moment. Shot 12bit to manage shadow tonality.

From a different point above. All shot on a 50mm M Summicron probably wide open.

I think i hit the saturation slider here in Resolve. But this had car rolling over camera. It's a 21mm CV lens and i see some CA aberrations from the lens that i would deal with in post. But i'd never let a car run over a Red!

shot on an 85mm APO off a monopod. Nice tonality again and it's day light from windows with some small panel lights bouncing and filling in

A reverse of the above.

Some fun shots.
I think the true benefit of something like the fp is the speed at which you can see something and grab it. Using it just with an SSD plugged in and manual M lenses gives a more spontaneous feel. Now most of the film will be shot on Red, in controlled conditions with a crew and that's the right approach for multiple dialogue scenes and careful blocking. But the fp has it's place and i may hand it too someone and just say grab stuff.

 
cheers
Paul

So i said i'd post some stills, these are basically ungraded.
This frame is in a sequence with car lights, i like the tonality of this very subdued moment. Shot 12bit to manage shadow tonality.

From a different point above. All shot on a 50mm M Summicron probably wide open.

I think i hit the saturation slider here in Resolve. But this had car rolling over camera. It's a 21mm CV lens and i see some CA aberrations from the lens that i would deal with in post. But i'd never let a car run over a Red!

shot on an 85mm APO off a monopod. Nice tonality again and it's day light from windows with some small panel lights bouncing and filling in

A reverse of the above.

Some fun shots.
I think the true benefit of something like the fp is the speed at which you can see something and grab it. Using it just with an SSD plugged in and manual M lenses gives a more spontaneous feel. Now most of the film will be shot on Red, in controlled conditions with a crew and that's the right approach for multiple dialogue scenes and careful blocking. But the fp has it's place and i may hand it too someone and just say grab stuff.

 
cheers
Paul

So i said i'd post some stills, these are basically ungraded.
This frame is in a sequence with car lights, i like the tonality of this very subdued moment. Shot 12bit to manage shadow tonality.

From a different point above. All shot on a 50mm M Summicron probably wide open.

I think i hit the saturation slider here in Resolve. But this had car rolling over camera. It's a 21mm CV lens and i see some CA aberrations from the lens that i would deal with in post. But i'd never let a car run over a Red!

shot on an 85mm APO off a monopod. Nice tonality again and it's day light from windows with some small panel lights bouncing and filling in

A reverse of the above.

Some fun shots.
I think the true benefit of something like the fp is the speed at which you can see something and grab it. Using it just with an SSD plugged in and manual M lenses gives a more spontaneous feel. Now most of the film will be shot on Red, in controlled conditions with a crew and that's the right approach for multiple dialogue scenes and careful blocking. But the fp has it's place and i may hand it too someone and just say grab stuff.

 
cheers
Paul

So i said i'd post some stills, these are basically ungraded.
This frame is in a sequence with car lights, i like the tonality of this very subdued moment. Shot 12bit to manage shadow tonality.

From a different point above. All shot on a 50mm M Summicron probably wide open.

I think i hit the saturation slider here in Resolve. But this had car rolling over camera. It's a 21mm CV lens and i see some CA aberrations from the lens that i would deal with in post. But i'd never let a car run over a Red!

shot on an 85mm APO off a monopod. Nice tonality again and it's day light from windows with some small panel lights bouncing and filling in

A reverse of the above.

Some fun shots.
I think the true benefit of something like the fp is the speed at which you can see something and grab it. Using it just with an SSD plugged in and manual M lenses gives a more spontaneous feel. Now most of the film will be shot on Red, in controlled conditions with a crew and that's the right approach for multiple dialogue scenes and careful blocking. But the fp has it's place and i may hand it too someone and just say grab stuff.

 
cheers
Paul

So i said i'd post some stills, these are basically ungraded.
This frame is in a sequence with car lights, i like the tonality of this very subdued moment. Shot 12bit to manage shadow tonality.

From a different point above. All shot on a 50mm M Summicron probably wide open.

I think i hit the saturation slider here in Resolve. But this had car rolling over camera. It's a 21mm CV lens and i see some CA aberrations from the lens that i would deal with in post. But i'd never let a car run over a Red!

shot on an 85mm APO off a monopod. Nice tonality again and it's day light from windows with some small panel lights bouncing and filling in

A reverse of the above.

Some fun shots.
I think the true benefit of something like the fp is the speed at which you can see something and grab it. Using it just with an SSD plugged in and manual M lenses gives a more spontaneous feel. Now most of the film will be shot on Red, in controlled conditions with a crew and that's the right approach for multiple dialogue scenes and careful blocking. But the fp has it's place and i may hand it too someone and just say grab stuff.

 
cheers
Paul

So i said i'd post some stills, these are basically ungraded.
This frame is in a sequence with car lights, i like the tonality of this very subdued moment. Shot 12bit to manage shadow tonality.

From a different point above. All shot on a 50mm M Summicron probably wide open.

I think i hit the saturation slider here in Resolve. But this had car rolling over camera. It's a 21mm CV lens and i see some CA aberrations from the lens that i would deal with in post. But i'd never let a car run over a Red!

shot on an 85mm APO off a monopod. Nice tonality again and it's day light from windows with some small panel lights bouncing and filling in

A reverse of the above.

Some fun shots.
I think the true benefit of something like the fp is the speed at which you can see something and grab it. Using it just with an SSD plugged in and manual M lenses gives a more spontaneous feel. Now most of the film will be shot on Red, in controlled conditions with a crew and that's the right approach for multiple dialogue scenes and careful blocking. But the fp has it's place and i may hand it too someone and just say grab stuff.

 
cheers
Paul

So i said i'd post some stills, these are basically ungraded.
This frame is in a sequence with car lights, i like the tonality of this very subdued moment. Shot 12bit to manage shadow tonality.

From a different point above. All shot on a 50mm M Summicron probably wide open.

I think i hit the saturation slider here in Resolve. But this had car rolling over camera. It's a 21mm CV lens and i see some CA aberrations from the lens that i would deal with in post. But i'd never let a car run over a Red!

shot on an 85mm APO off a monopod. Nice tonality again and it's day light from windows with some small panel lights bouncing and filling in

A reverse of the above.

Some fun shots.
I think the true benefit of something like the fp is the speed at which you can see something and grab it. Using it just with an SSD plugged in and manual M lenses gives a more spontaneous feel. Now most of the film will be shot on Red, in controlled conditions with a crew and that's the right approach for multiple dialogue scenes and careful blocking. But the fp has it's place and i may hand it too someone and just say grab stuff.

 
cheers
Paul

So i said i'd post some stills, these are basically ungraded.
This frame is in a sequence with car lights, i like the tonality of this very subdued moment. Shot 12bit to manage shadow tonality.

From a different point above. All shot on a 50mm M Summicron probably wide open.

I think i hit the saturation slider here in Resolve. But this had car rolling over camera. It's a 21mm CV lens and i see some CA aberrations from the lens that i would deal with in post. But i'd never let a car run over a Red!

shot on an 85mm APO off a monopod. Nice tonality again and it's day light from windows with some small panel lights bouncing and filling in

A reverse of the above.

Some fun shots.
I think the true benefit of something like the fp is the speed at which you can see something and grab it. Using it just with an SSD plugged in and manual M lenses gives a more spontaneous feel. Now most of the film will be shot on Red, in controlled conditions with a crew and that's the right approach for multiple dialogue scenes and careful blocking. But the fp has it's place and i may hand it too someone and just say grab stuff.

 
cheers
Paul