rewriting the convert-function back to "simple" bitshifting and the IFDs would be changed, it wouldnt be no more a DNG. (*) it looks like an array not NULLED in loop. (*) for investigating on the converting problem try rawdigger, switch between the Sensel-channels. (*) both are not recognised by photoshop/acr, but viewable with fe irfanview. (*) 16bit shows converting problems - have no time to finish successfully. (*) 14bit is functional with working image (*) not enough time to solve, because workin' hard. *lol* sorry, compiling while Championsleague-Finals is a bad idea. Just to give you some food Here's the link to the app. This thread at EXIFTool was useful in pinpointing the problem. I am sure they are working on it but probably quicker to change Raw2DNG. I asked a Blackmagic guy via John Brawley about Resolve supporting stills DNG, and Pete confirmed it doesn't yet support DNG only Cinema DNG. pack the raw data into IFD0 instead of SUBIFD? Is that a trivial metadata change or more complex? There is a DNG SDK and Cinema DNG docs, someone just needs to understand the file format and write the correct structure into Raw2DNG's code. Resolve reads the thumbnail data in IFD0-Entry but cannot access the raw data packed into a subIFD since it lacks support for this file structure.Ĭould we change Raw2DNG so subIFD becomes ifd0? I.e. The raw data in the stills DNG is in a subfile, and seemingly the primary file is a thumbnail. Stills DNG has support for multiple images in one DNG at different resolutions (subfiles) and Cinema DNG only has one 'primary-image'. My research shows the OP was correct, the problem is. Please look in my blog-entry to find the newest version!īitbucket-sourcecode c# (with 1.5.0beta2 i've left it into the free world)Īctual release : raw2cdng 1.6.5 for windows since 1.6.5 audiosync seems stable, colormatrices are refreshed. With 1.5.0 (coming next) there s a new GUI, and on NAB() Adobe releases a bigger update promising a better workflow with cdng. Resolve, Speedgrade and all ACR-using-Apps are coping well with the cdng's. I decided to stay on the same name and same tool with integrated mlv-convert (since 1.4.5). (*2) is it worth that? Maybe another Fileformat would be more usable? DPX? EXR? TIF? (*1) Raw-Data - Subpixel-Chunks, MSB or LSB first? LittleEndian, so LSB first, right? (+) Raw-Data are packed into a subIFD - as in the DNG-Definition described. (+) IFD0-Entry is the jpg-Preview in 128x96px 8Bit - thats the one you see in Resolve. If asking, why the simple DNG-Sequences are not usable, it might be that These CinemaDNG-Sequences are recognised by Resolve and Speedgrade, but they are chaotic because of wrong handling/converting. So, now i'm sitting on converting these 14bit to 16Bit-Chunks. They are 14Bit, isnt it? I figured out, that Resolve and Speedgrade cant handle 14Bit Raw-Frames! Just 8, 10 or 16Bit, maybe 12Bit. I wrote an App for Win7, building a CDNG-Header with the raw-pictures from the Camera-raw-file. The CinemaDNG-File is just a TIFF/PE File (as DNG is also) with these CDNG-Tags. After reading the CinemaDNG-Definition i saw, there are about 35 mandatory tags.ĭNG Specification 1.4.0.0 - June 2012 - CinemaDNG Specification 1.1.0.0 - September 2011 First i thought it would just be an existing xmp-packet inside the dng-frame, but it wasn't. I'm currently trying to realise a CinemaDNG-Converter.
0 Comments
Leave a Reply. |