Messages

Hi, had you shot with the BMCC before? I've shot as b cam on the BMCC alongside the Alexa on a couple of TVCs and i was able to get them to match pretty well.

Would you be willing to share a couple of the original Alexa/BMCC files with me? I'm working on a LUT to help make it easier to match the two.

Cheers.

See my reply at the BMD forum:

http://forum.blackmagicdesign.com/viewtopic.php?f=3&t=9274&p=59210#p59210

Assuming Cinema DNG is too "raw" to bring directly into Resolve, I'm looking for a ProRes workaround.

Resolves RAW convertor doesn't seem to do anything to fix chromatic aberration or any other common RAW 'issues' that ACR etc fix.
The same problem shows up with BMCC Raw files and you have to remove the CA yourself in Resolve.

I've been using the newest RAWMagic beta -> Resolve workflow with the BMD Film and highlight recovery and applying Captain Hook's LUT with my 60D footage and I've been getting fantastic results.

Good to see you finding my LUT useful, just be aware i created it for BMCC footage that generally has a green bias (and my LUT pushes away from that slightly). But the LUT is also NOT mean to be a "neutral" looking and rather appeal to my aesthetics so if it works for you (with i assume some extra adjustments), that's great.

I've thought about making one for 5D3/2 RAW footage but haven't really had time.

Use this to convert the lut (free trial works fine):

http://www.brizsoft.com/lut-converter/

Convert into technicolor mga for LUT Buddy.

- There's a lot of what I would say is chromatic aberation. Pinkish especially in the trees. This could be a white balance thing combined with the sunset highligt, bit my best guess is that something either happened in the RAW recording or the raw2cdng conversion. Anyone with the same issues?

Resolve wont do any chromatic aberration fixing to cDNG's like ACR etc will. I see CA with BMCC DNG's as well. You need to fix it yourself in resolve.

That can beintegrated into raw2dng.app, I've made some test. It need ADC installed in the default location.
What are yous opinions is something needed in raw2dng.app?

If raw2dng is modified to produce cinemaDNG files, OSX will be able to create previews for them just like with BMCC DNGs (that don't contain embedded previews), so ADC would be redundant and is probably the better long-term goal. ADC might make some people happy for now though, maybe as an option though?

I watched that tutorial and as I discovered there's no raw highlight and shadow control in Resolve which makes me really wonder what all the hype over the BMCC is about. From my experience shooting raw stills the real power of raw is the highlight and shadow recovery.

In Resolve you do it all yourself using keys (chroma/luma/saturation) etc. You can do exactly the same stuff (like highlight/shadow recovery if you want), just with a LOT more control. The log controls are actually great for highlight/shadow recovery and i do that all the time. The downside is there's no easy "slider" for a lot of stuff so you have to put it all together yourself for the most part, but the upside is grade management is amazing and it's also easy to store stuff like that as power grades and just call it up in any shot in any project as you need. And now that BMD own Resolve each new release is taking major leaps towards being "user friendly" in the way typical prosumers would expect an app to behave, rather than those coming from 3D/Compositing and other node based apps/workflows (mostly in linux or ported from it) where resolve is actually SIMPLE compared those apps.

It's really different to using normal still RAW apps (Capture One is my personal choice for colour etc), but it's AMAZING for grading motion footage once you learn it and find out how to get the most from it. Don't get me wrong, it could definitely learn from the RAW still apps too, and BMD are working at getting it there.

[I figured out, that Resolve and Speedgrade cant handle 14Bit Raw-Frames!]

I figured out, that Resolve and Speedgrade cant handle 14Bit Raw-Frames! Just 8, 10 or 16Bit, maybe 12Bit. So, now i'm sitting on converting these 14bit to 16Bit-Chunks.

BMCC DNG's are 12bit log that unpack as 16bit linear in resolve.

I think the cinemaDNG discussion belongs in this thread:
http://www.magiclantern.fm/forum/index.php?topic=5404.0

I think in the first DNG file, there is the content of the metadata Cinema (Time Code, Frame Rate, T-Stop, Reel Name, Camera Label) + photo metadata record.

Not in BMCC DNG's.. each DNG just contains some of the DNG Tags as described in the DNG spec here (section 4):
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/photoshop/pdfs/dng_spec_1.4.0.0.pdf

They also use TIFF Tag 51043 for timecode and 51044 for framerate as defined in cinemaDNG spec:
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/cinemadng/pdfs/CinemaDNG_Format_Specification_v1_1.pdf

@Scrax - Registration for Resolve Lite can be filled in with any details, you don't have to be a customer.

I don't get those with dng_validate, can you send me a broken dng?

This is using Scrax's app 0.5 - which i think he said uses and older raw2dng compile? Maybe you've fixed and it's not in Scrax's share yet, but here's a file anyway i just converted:

http://cl.ly/232r0t3P352O

It worked  I just opened a 60Gb file. Thx Captain

Great, i'll leave the rest to Scrax.

[Squig]

I found this for the Cinema DNG's related tags : http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/cinemadng/pdfs/CinemaDNG_Format_Specification_v1_1.pdf

This is the wrong thread i think, but cinemaDNG can simply be a folder of DNG files with sequential numbers so the spec that needs to be followed in just the plain DNG spec.

http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/photoshop/pdfs/dng_spec_1.4.0.0.pdf

Currently using dng_validate (which is in the DNG SDK) gives these errors with DNG's from raw2dng which i've already let a1ex know about (this thread is about an OSX wrapper for that app):

*** Warning: IFD 0 Model is not NULL terminated ***
*** Warning: IFD 0 UniqueCameraModel is not NULL terminated ***
*** Warning: The ExposureTime is <= 0 ***
*** Warning: Too little padding on left edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on top edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on right edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on bottom edge of CFA image (possible interpolation artifacts) ***

To solve that wee need to investigate more the issue, so far I se two problems one is the swallowing of the app and another is the error from raw2dng, for the first I'll try to save dng in the final folder directly, but I don't know yet how.

Yeah, the script is using "ls" to check to see if the folder has any DNG files, but with Squig's large 52gb file this produces so many dng files that ls can't deal with them all, so the script fails before moving all the DNG's out of the resources directory (they actually get converted fine).

I don't have any large files to test (32gb lexar 1000x is largest i have), Squig, could you try replacing your script file with this and test with your 52gb file? (http://www.magiclantern.fm/forum/index.php?topic=5404.msg37139#msg37139) I'm not sure what performance will be like and definitely ideal is for raw2dng to be modified to accept destination directory as an argument (ask a1ex?).

#!/bin/sh

importFILE() {
   if [ "${file_is: -4}" == ".RAW" ] ; then
#      echo "File $file_is Supported"
      name=$(basename -s .RAW "$file_is")
      fldr="$(dirname "$file_is")"/

      ./raw2dng "$file_is"
    
      mkdir "$fldr$name"
     find . -type f -name "*.dng" -print | \
     while read filename
     do
           mv "${filename}" "$fldr$name"/
     done
   
   else
   echo "File not Supported"
   fi
}
   
checkFLDR() {
   for d in $(ls "$FILES_FLDR"); do
      if [ -d "$FILES_FLDR/$d/" ];then
         FILES_FLDR="$FILES_FLDR$d"
         echo "we have: $FILES_FLDR"
         for f in $(ls $FILES_FLDR); do
            file_is="$FILES_FLDR$f"
            echo "SEARCHING: $file_is"
            importFILE
         done
      else
         file_is="$FILES_FLDR/$d"
         echo "SEARCHING file: $file_is"
         importFILE
      fi
   done
}

#################


echo "raw2dng converter GUI for OsX"
echo "Beta ver.0.5"
if [ -d "$1" ];then
   FILES_FLDR="$1"/
   echo "SEARCHING: $FILES_FLDR"
   checkFLDR
elif [ -f "$1" ]; then
   file_is="$1"
   importFILE
else
   echo "Drop a ML .RAW video file or folder here"
fi
exit 0

Scrax - may need to replace "ls" with "find" or something similar?

Good to hear that, meanwhile I've recompiled from last source and now dng extracted from my raw can't be opened anymore in ACR

I just found photoshop doesn't like 5610 dng files and hangs.
Lightroom is currently spitting out tif files for me instead, although it seems much slower than PS would do it which is a shame...

Here are my "LOG" settings by the way that i knocked together VERY quickly.. seems to work well so far with alexa LogC->709/bmcc/my bmcc lut shared via John Brawley (swing log offset tint/gain around)/etc in Resolve (haven't tested thoroughly yet):

PS:
http://cl.ly/1R1W0O1i362z

LR:
http://cl.ly/3x2M2H2n1E3r

Just converted a 15.83GB file.. Thanks again Scrax, rodobot, A1ex, and all ML team.

Just tested 0.5 on a 3gig file.. works here. Thanks Scrax!

Does this one open in DaVinci Resolve?

(I couldn't install it)

No, it still has some issues. Putting it through Adobe DNG convertor does allow Resolve to see it though, but with same problems before of no RAW controls like wb/tint/exposure having an effect on the image.

Here's the info from dng_validate for your file above:

http://f.cl.ly/items/2p231l3u1S1r1q3r1M25/ml.txt

This is the file after running it through Adobe DNG convertor (its added preview image, changed bits per sample, etc etc):

http://f.cl.ly/items/0w1l2s451R1H0c1V130E/adobe.txt

Here's a DNG frame from the BMCC for comparison:

http://f.cl.ly/items/362k3x1o471V2p3t2o3T/bmcc.txt

We still have these warnings on your DNG also:

*** Warning: The ExposureTime is <= 0 ***
*** Warning: Too little padding on left edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on top edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on right edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on bottom edge of CFA image (possible interpolation artifacts) ***

Hope that helps.

Error: API version mismatch: 15052800

Have you tried another RAW file? That error is giving an odd api version - it should be "1" according to this check:

if (raw_info.api_version != 1)
FAIL("API version mismatch: %d\n", raw_info.api_version);

Glad to have helped.

Sent you a PM with links to a couple of frames, hope it helps.

Any ideas about where to look for converting DNGs to CinemaDNGs ready for Resolve?

The DNG's will open in Resolve and play as a single clip but they're not interpreted correctly. Running them through Adobe's DNG convertor helps (the aspect ratio is at least displayed correctly after doing this) but resolve still doesn't know how to adjust wb/tint/etc for the files.

Checking the DNG's from raw2dng with dng_validate shows the following problems:

*** Warning: IFD 0 Model is not NULL terminated ***
*** Warning: IFD 0 UniqueCameraModel is not NULL terminated ***
*** Warning: The ExposureTime is <= 0 ***
*** Warning: Too little padding on left edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on top edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on right edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on bottom edge of CFA image (possible interpolation artifacts) ***

My hunch is once those are corrected in chdk-dng.c, resolve will correctly read the DNG's since they should be to be spec. Running dng_validate on BMCC dng's produces no warnings and checking them with the verbose flag shows lots of XMP data that gives WB/tint/etc info that i'm sure will eventually come from ML for raw2dng.

Where did you put that new information? I,m a noob on this one. Maybe you could put the new one up for download?
Thanks.
//D

-> Right click on the app and choose "show package contents"
-> Go into Contents, then Resources
-> Open the file named "Script" in a text editor and replace with what i posted above - save and reopen the app.

I would rather not post a new download and confuse matters - i'm sure scrax or someone else from ML will update the app if they choose to.

Hi,

I noticed a path with spaces in the raw2dng mac app fails.. i solved this by modifying your script in the package to be like this:

----
#!/bin/sh
time=$(date +"%y%m%d%H%M")
if [[ $1 ]]; then
   fldr="$(dirname "$1")"/
   ./raw2dng "$1"
   if [[ $(ls *.dng) ]]; then
      echo "Moving .dng to $fldr$time"
      mkdir "$fldr$time"
      mv *.dng "$fldr$time"
   else
      echo "Nothing converted"
   fi
else
   echo "DRAG SOMETHING IN THE APP"
fi
exit 0

----
Works okay now for me.

Thanks again everyone at ML for all the hard work.

HDMI chip is probably an off the shelf solution. I doubt its so easy to just feed it a different buffer when it does processing on the data.

I see. Be good to find out either way. Thanks!

Is it just not possible to get the 14-bit Raw feed sent uncompressed to the HDMI out? Or the uncompressed YUV422 to the HDMI out?
Would the YUV422 to HDMI out (if even possible) look better than canon's version?

Sorry to cross-post this, but if you look at the BMCC's Prores recording done on a hyperdeck shuttle (via SDI out of the camera), i imagine IF the 14-bit Raw feed could be sent out the HDMI it would be so much better (than current 5D3 options) and you wouldn't have to worry about write speeds of CF/SD cards: