Jump to content

Juan Melara

Members
  • Content Count

    21
  • Joined

  • Last visited

  • Days Won

    1

Juan Melara last won the day on March 3

Juan Melara had the most liked content!

1 Follower

About Juan Melara

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi all, after several requests I've now updated the P4K2Alexa and P6K2Alexa PowerGrades with new ACES versions. This allows you to match the Alexa when working in Resolve's ACES colour science. It's a free upgrade, get in touch if you never received your update email.
  2. That's going to be tough if not impossible to correct completely. If it's a short video I would look at qualifying and using shapes to isolate and correct as much as possible. If it's long, I would probably see how far the first methods I suggested could get you. Followed by making it B&W. And if that isn't acceptable I would look at reshooting.
  3. It could be pretty difficult to correct. I would start by shooting an outside scene with and without those filters. Use shutter speed to compensate for the lack of ND on the unfiltered shot. Take both into Resolve and use temp and tint to get as close as possible to the unfiltered version. Then use the RGB curves to correct any non linear differences. And depending on how bad it is you might need to use hue v hue, or even qualify and correct specific colours.
  4. Beyond charts, I didn't put them side by side. But in real world testing the difference in highlight range is hard to notice in most situations. At ISO800 theres 6.5 stops above middle gray for the P4K, 6.9 on the P6K, 7.8 on the Alexa. On charts the differences are easy to see. In the real world with correct exposure anything above about 6-7 stops is into extreme highlight territory, which doesn't actually occur often in outdoor scenes. In all the P4K/Alexa sample images in this post it's only the lights in the dusk shot that are beyond 7 stops. So for most shots the extra ~0.4 stop is hard to notice. Where it would be noticeable is if you place anything important up in that range and try and bring it back, like those tests you linked to.
  5. Here you go: Visit the Vimeo link to download a full res 3840x1080 Prores 422HQ file.
  6. I would say it's because the Alexa is already doing highlight recovery as part of it's dual gain architecture. ARRIRAW or Prores recording, It's on by default. You can set to tint to whatever makes your image look good. 0 is just the suggested value as that creates the most neutral response across the entire luminance range for most scenarios. Apart from general colour, the two main areas the Alexa excels at is dynamic range and handling mixed temperature or off temp light sources. The PowerGrade can't change dynamic range so it doesn't help there. But the way you expose on set and the ISO you rate the camera, can close the gap. For mixed temp sources, as long as you are prepared to adjust the white balance and tint, you can get pretty close.
  7. The sensors are different enough that I wouldn't even think they are part of the same family. I actually wasn't expecting that. It required a bit of work to even out the non linear quirks. As long as you process the footage at 0 tint, P4K2Alexa will sort out the red channel, well all channels actually.
  8. It's not easy is it! To make it easier, the best workflow is to linearise the GH5, make the corrections, then return it back to log. That means shooting in a gamma that can be converted to linear via a CST, or via something like Lattice. If you don't linearise, you'll be forever chasing your tail. A correction at 0EXP will throw something out at 2EXP, fix it at 2EXP and you've just thrown it back out at 0EXP. When you linearise you remove the variability of the log curve, which can make it so much easier.
  9. I was going to send it to you for free, but then you wouldn't appear on the customer list, so you wouldn't get any free updates. Flick me an email and I'll get you a full refund or figure something out. You definitely want this version as the sensors are quite different. I could make one. Just need to see what the demand is like and then would need to source the cameras. Yeah there's a good stop and a half extra on the Alexa. Highlight recovery brings that down to maybe a stop difference. I'm glad you didn't mention the Alexa's "highlight roll-off." The Alexa doesn't have a highlight roll-off! It's completely linear up there.
  10. P4K2Alexa is out. Accurately match BMPCC 4K footage to the ARRI Alexa via a clean, non destructive 3x3 matrix. With none of the downsides of using a LUT. Fully editable, no clipping, no clamping, no snake oil. https://juanmelara.com.au/products/bmpcc-4k-to-alexa-powergrade-and-luts
  11. After many requests, P4K2Alexa PowerGrade + LUTs coming in the next day or two. Dawn to dusk, one PowerGrade, no adjustments to the transform.
  12. The Cinema 5D guys measured at ISO400. Rating and exposing at ISO800 shifts the mid point, allocating one stop extra to the highlights. It also lifts the shadows, revealing one more stop down the bottom. That last stop will be slightly noisy. And thats what can make measuring DR tricky, as each tester will have a different tolerance to what is an acceptable level noise and whether the bottom stops actually count towards usable dynamic range. And if you're Red, just count everything and say it's 17+ stops. Here is another image to show you the bottom stops of both cameras The previous example didn't have deep enough shadows to crop into. The exposure is matched on the day with false colour, this time I reckon they're identical. No noise reduction. Shot BRAW 5:1 / Prores 444 on the Alexa, which would be compressing out a bit of noise. Remember that the P6K has actually been cropped in to match the FOV of the Alexa, as I shot a 25mm on P6K and a 35mm on the Alexa. The crop is 1.32, so I'm actually only using a 4.6K portion of sensor. It would be less noise if I used the full sensor and scaled down.
  13. Yeah that info was gone on the Alexa. The Alexa was shooting Prores 444, but there is no difference in dynamic range between Prores 444 and ARRIRAW. And there is no highlight recovery on ARRIRAW either, so there would be no chance of bringing it back.
  14. Yeah you're correct, but I already had a library of those charts from various sensors and stocks, so it made sense to keep adding to it. Plus it's also actually quite helpful to have so many samples within the colour space, rather than just a few samples right at the edges. Thanks mate! Much appreciated. Another interesting thing I found in testing is how much dynamic range the P6K actually has. According to the charts published by BMD and ARRI, when both cameras are exposed at ISO800, the Alexa has 1 stop extra range in the highlights, but approximately the same amount of stops in the shadows. In testing I found this to be pretty much spot on. I found I could expose one of the charts exactly one stop higher on the Alexa before it touched the clip point. The interesting thing is how that actually translates in real world scenarios, and what that difference looks like. Here are some crops of a scene shot on both cameras. In LogC, so the differences are visible. I matched exposure on the day using false colour, they're as close as I could get them. Probably less than 1/20th of a stop of difference in exposure. The left image is the P6K. When comparing it to the Alexa image in the middle, thats exactly what 1 stop difference in the highlights looks like in a real world situation. It's interesting to see what happens to that 1 stop difference when highlight recovery is enabled – the P6K actually retains more highlight detail. Obviously you would never actually place important image information in that range (not that you would ever do that with the Alexa either). But if you need it create a smoother roll-off in anything neutral in colour like specular highlights, clouds etc, it is possible to outperform the Alexa in highlight dynamic range... sometimes.
  15. Hey guys, late last year I bought a P6K to work alongside the Alexa I normally shoot with. The goal was to have smaller, lighter camera that would live on a gimbal or could be used in situations where a full size Alexa wouldn't work. Knowing that both cameras would need to intercut seamlessly, I set about profiling the P6K using the same process I had previously used to profile the Alexa sensor and various negative film stocks. This process generates approximately 14,000 data points per camera. I then took the visual form of this data into Resolve and created a PowerGrade that accurately matches the P6K to the Alexa. After several requests, I've now packaged up the PowerGrade and added it to my store. You can check it out here: https://juanmelara.com.au/products/bmpcc-6k-to-alexa-powergrade-and-luts The PowerGrade At the heart of a PowerGrade is a custom 3x3 matrix that aligns the P6K's colours with the Alexa's. Because this is done through a matrix in linear space, the result is actually closer to a technical transform. The benefits this brings over a LUT is that it's non destructive, there's no danger of clipping or clamping data. And if you really wanted to, you could fully reverse the transform with zero loss in quality. This is because it doesn't break Resolve's 32bit float space like LUTs do. Probably one of the best features of a PowerGrade is that is fully editable and customisable. But since editing a 3x3 matrix isn't the easiest thing in the world, I've also included a Hue vs Hue/Hue vs Sat curve approximation of the matrix which is far easier to customise. And because it's a PowerGrade you can see exactly what is being done by each node, which means that I'm not able to hide snake oil like you can with a LUT. The LUTs Speaking of LUTs, knowing that a lot of people actually prefer to work with LUTs, I also created a LUT version. It's the exact same transform but in LUT form. One of the biggest limitations with most LUTs is that they clip any information that exceeds the top of the waveform, so basically any value above 1.0. This is a big issue with BMPCC footage as enabling Highlight Recovery or working with any ISO above 400 pushes valuable information above 1.0, where it is permanently clipped. With this BMPCC specific requirement in mind, I developed the LUTs to accept and work with values exceeding 1.0. So no matter if you enable Highlight Recovery or push the ISO to 6400, the LUT is able access and process all the information extending above 1.0. Anyway, check it out and let me know if you have any questions or comments. I'm keen to get feedback from any users to see what can be improved or expanded on. Comparisons Here are a few comparison images shot with the P6K mounted on the Alexa's top handle. The Alexa was using a Zeiss Milvus 35mm, the P6K was using a Zeiss Milvus 25mm, then cropped in post to match the FOV. The Alexa images are untouched, the P6K images feature minor exposure adjustments only. Check the store link for more images.
×
×
  • Create New...