Author Topic: The CinemaDNG Discussion (raw2cdng)  (Read 922284 times)

chmee

  • Contributor
  • Hero Member
  • *****
  • Posts: 1031
  • raw2cdng
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #850 on: May 21, 2014, 01:32:27 PM »
i just got a file with the same behaviour (strange i hadnt that on other files, the problem is so obvious.) when raw's have no framerate (did they ever had this metadata?) , it will crash while calculating the duration of the video. if framerate is zero, i set it now to 24fps. today i will put a beta6 on the server.

raw2cdng 1.5.0 beta 6 online

* 12bit maximized should work again (with pinkhighlight-fix as well)
* RAW crash fix (divideByZero-Exception)
* more debugdata

http://www.phreekz.de/wordpress/2014/04/magiclantern-raw2cdng-1-5-0/

Jbowdach

  • Freshman
  • **
  • Posts: 74
  • Editor\Colorist for Cinetic Studios
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #851 on: May 22, 2014, 08:01:36 AM »
Will 12 bit regular return? What's the major difference between maximized that requires the huge increase in processing involved to create them?

. never could find that file you mentioned but ill see if i have any future crashes or issues

Thanks as always! Giving your suggestions regarding filenames using f(_) a try for audio sync in Resolve, as I'm having some issues auto syncing.

glubber

  • Member
  • ***
  • Posts: 118
  • 550D
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #852 on: May 22, 2014, 09:23:33 AM »
Hi Chmee,

is it intentional that that the headline of the app shows "rawcdng 1.5" instead of "raw2cdng 1.5"?
EOS 550D // Sigma 18-200 // Sigma 18-70 // Canon 10-18 STM

chmee

  • Contributor
  • Hero Member
  • *****
  • Posts: 1031
  • raw2cdng
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #853 on: May 23, 2014, 12:27:35 AM »
@jbowdach the main difference normal versus maximized is i dont use the original values from canon ( example 5DIII: 2048-15000 from max 16384) but i spread them to the maximum values (0-65535 with 16bit). this is needed for premiere and gives no drawback on other apps. with 16bit we have no problem with changing valuerange, because we're not lowering it. in 12bit we do and every bit we have we should use.

ahh btw. with beta6 i write more from the audioprocess into the debuglog. i want to find this bug for autosync in resolve as well :)

@glubber thanks, will change that :)

Jbowdach

  • Freshman
  • **
  • Posts: 74
  • Editor\Colorist for Cinetic Studios
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #854 on: May 23, 2014, 12:35:14 AM »
@jbowdach the main difference normal versus maximized is i dont use the original values from canon ( example 5DIII: 2048-15000 from max 16384) but i spread them to the maximum values (0-65535 with 16bit). this is needed for premiere and gives no drawback on other apps. with 16bit we have no problem with shortening valuerange, because there isnt. in 12bit we're lowering the bitdepth and every bit we have we should use.

@glubber thanks, will change that :)

Makes sense  thanks for the explanation. Seems to save approx 20% space compared to 16 bit conversions based on my tests last night. Will know of sync worked when the  get home and can check the render output.

Does premiere not accept 12 bit non maximized cdngs sequences? Haven't played w native cdngs in premiere pro yet

chmee

  • Contributor
  • Hero Member
  • *****
  • Posts: 1031
  • raw2cdng
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #855 on: May 23, 2014, 12:46:33 AM »
premiere does not work with biased files (zero is not zero). and because premiere in the actual version only accepts bmcc-like cdng-files, i (we?!) had to code this pinkhighlightfix. BUT it works well with 12/16bit maximized pinkhighlight-fixed files.

make the test for yourself, its a huge difference.

(i promise, in the next beta there will be the vertical banding-button, its no1 on todolist)

chmee

  • Contributor
  • Hero Member
  • *****
  • Posts: 1031
  • raw2cdng
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #856 on: May 23, 2014, 01:15:22 PM »
@a1ex is vertical banding an individual static property of every body? if yes, would it be an idea to write a module to calculate it for the body and save it as a block into the mlv?

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 12564
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #857 on: May 23, 2014, 02:57:42 PM »
From the same body, it seems to differ from clip to clip, but inside one clip it stays pretty much the same.

My heuristic (for speed reasons) is to compute it from the first frame only. This works fine most of the time, but if you start recording with lens cap on for example, it will fail. A better approach would be to take say 5 or 10 frames, evenly spread across the footage, and compute from there. Most likely, averaging the coefficients or taking the median value should do the trick.

I don't know exactly how it behaves with long recordings though, but I assumed the current approach works fine, since there were no relevant bugs reported for this use case.

chmee

  • Contributor
  • Hero Member
  • *****
  • Posts: 1031
  • raw2cdng
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #858 on: May 23, 2014, 03:07:12 PM »
thx. it was only my assume, the banding is kind of fingerprint per body-electronics. so it was a simple idea to implement the calculations into the body, calculate it once and saving the array of floatingpoint on the body. but it's not i know now.

anandkamal

  • Freshman
  • **
  • Posts: 81
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #859 on: May 27, 2014, 01:48:56 PM »
hi chmee, with beta 6, audio sync in resolve works with certain footage and some others are wrongly synced. Same audio synced twice to different footage.

Just another note which i wanted to share is that, i used to optimize the flickering problem in resolve by changing file name codes in raw2cdng. I had to work with .raw files and .mlv files together for a project. A single timeline in resolve having both raw's cdng and mlv's cdng really threatened me regarding flickering issues. However, i went through resolve's manual and now one can overcome the flickering issue by checking the "Output single field when paused" option from "General Options" in resolve. It worked for me (but I also changed file naming in converter). Hope the solution works and has nothing to do with file naming... thanks

contactarproyectos

  • New to the forum
  • *
  • Posts: 4
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #860 on: May 29, 2014, 04:21:05 AM »
Hi guys,
This could be an old question, but I really need some help:
The only raw2cdng version I can launch are 1.2.0 or olders. With newest: “raw2cdng has stopped working” appear. I´ve tried run as adm, compatibility mode, etc, and nothing.
Do you know why?
OS win7, 64bits

Thanks!

chmee

  • Contributor
  • Hero Member
  • *****
  • Posts: 1031
  • raw2cdng
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #861 on: May 29, 2014, 09:33:58 AM »
Hmm. It seems, my app cant write some data. It writes two Files:

* debug.log - since 1.4.6, into the same path as the app
* raw2cdng.settings.json - since 1.2.1, into Users/[User]/Appdata/roaming

* Dont use programs or windows as path.
* maybe it has something to do with special chars in your username?

* try a start from root or other harddisk.
* under file-properties, try to set admin static.
* wait a moment, it should show a some debug info, there will be some files in a temp-directory. the small xml-file should show the reason.

contactarproyectos

  • New to the forum
  • *
  • Posts: 4
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #862 on: May 29, 2014, 07:20:39 PM »
* No debug.log file
* No raw2cdng.settings.json file

I found this xml files:

-C:\Users\Dario\AppData\Local\ElevatedDiagnostics\733862231\2014052901.000\PCW.0.debugreport.xml:

miércoles, 28 de mayo de 2014 22:19:02true6.1Clientamd641.5Microsoft WindowsHaga que los programas antiguos se ejecuten en esta versión de Windows.03740x0C:\Windows\diagnostics\system\PCW0x00000000006B5C40<Answers Version="1.0"> <Interaction ID="IT_LaunchMethod"> <Value>ContextMenu</Value> </Interaction> <Interaction ID="IT_SelectProgram"> <Value>NotListed</Value> </Interaction> <Interaction ID="IT_BrowseForFile"> <Value>C:\Users\Dario\Desktop\magic lantern\raw2cdng.1.5.0.beta6.exe</Value> </Interaction> </Answers>50380x803C0100


-C:\Users\Dario\AppData\Local\Temp\WER5B1F.tmp.WERInternalMetadata.xml:

<?xml version="1.0" encoding="UTF-16"?>
-<WERReportMetadata>-<OSVersionInformation><WindowsNTVersion>6.1</WindowsNTVersion><Build>7601 Service Pack 1</Build><Product>(0x30): Windows 7 Professional</Product><Edition>Professional</Edition><BuildString>7601.18113.amd64fre.win7sp1_gdr.130318-1533</BuildString><Revision>1130</Revision><Flavor>Multiprocessor Free</Flavor><Architecture>X64</Architecture><LCID>3082</LCID></OSVersionInformation>-<ProblemSignatures><EventType>CLR20r3</EventType><Parameter0>raw2cdng.1.4.9.exe</Parameter0><Parameter1>1.0.0.0</Parameter1><Parameter2>52f7c322</Parameter2><Parameter3>raw2cdng</Parameter3><Parameter4>1.0.0.0</Parameter4><Parameter5>52f7c322</Parameter5><Parameter6>82</Parameter6><Parameter7>c8</Parameter7><Parameter8>System.IO.FileNotFoundException</Parameter8></ProblemSignatures>-<DynamicSignatures><Parameter1>6.1.7601.2.1.0.256.48</Parameter1><Parameter2>11274</Parameter2><Parameter22>0a9e</Parameter22><Parameter23>0a9e372d3b4ad19135b953a78882e789</Parameter23><Parameter24>0a9e</Parameter24><Parameter25>0a9e372d3b4ad19135b953a78882e789</Parameter25></DynamicSignatures>-<SystemInformation><MID>8C63604C-DCF0-4276-B73A-601CDEFC9D85</MID><SystemManufacturer>System manufacturer</SystemManufacturer><SystemProductName>System Product Name</SystemProductName><BIOSVersion>2102</BIOSVersion></SystemInformation></WERReportMetadata>


- and this txt:

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="raw2cdng.1.4.9.exe" FILTER="CMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="mlv_dump.exe" SIZE="271511" CHECKSUM="0x89C7DAE7" MODULE_TYPE="WIN32" PE_CHECKSUM="0x48851" LINKER_VERSION="0x10000" LINK_DATE="02/06/2014 20:42:55" UPTO_LINK_DATE="02/06/2014 20:42:55" EXE_WRAPPER="0x0" FILE_ID="000019729fc7e9e575a55adfed708247462ec458211f" PROGRAM_ID="00034d1e3b779acee3608899521a05a279ae0000ffff" />
    <MATCHING_FILE NAME="raw2cdng.1.4.9.exe" SIZE="553472" CHECKSUM="0x276FD127" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION="raw2cdng" PRODUCT_NAME="raw2cdng" FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="raw2cdng.exe" INTERNAL_NAME="raw2cdng.exe" LEGAL_COPYRIGHT="Copyright ©  2013" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="02/09/2014 18:04:18" UPTO_LINK_DATE="02/09/2014 18:04:18" VER_LANGUAGE="Independiente del idioma [0x0]" EXE_WRAPPER="0x0" FILE_ID="0000e0cfb8a8373eb6a02cd0171346989ea56ad09f07" PROGRAM_ID="000391263d3901eb726be10e0256222aeca100000000" />
</EXE>
<EXE NAME="KERNELBASE.dll" FILTER="CMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="KernelBase.dll" SIZE="274944" CHECKSUM="0xE4148384" BIN_FILE_VERSION="6.1.7601.18015" BIN_PRODUCT_VERSION="6.1.7601.18015" PRODUCT_VERSION="6.1.7601.18015" FILE_DESCRIPTION="Archivo DLL de cliente API BASE de Windows NT" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Sistema operativo Microsoft® Windows®" FILE_VERSION="6.1.7601.18015 (win7sp1_gdr.121129-1432)" ORIGINAL_FILENAME="Kernelbase" INTERNAL_NAME="Kernelbase" LEGAL_COPYRIGHT="© Microsoft Corporation. Reservados todos los derechos." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4AA27" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="6.1.7601.18015" UPTO_BIN_PRODUCT_VERSION="6.1.7601.18015" LINK_DATE="11/30/2012 04:56:42" UPTO_LINK_DATE="11/30/2012 04:56:42" EXPORT_NAME="KERNELBASE.dll" VER_LANGUAGE="Español (España, internacional) [0xc0a]" EXE_WRAPPER="0x0" FILE_ID="000090b069cbc93c701394b47d4e830cdd7d384f5d5c" PROGRAM_ID="0000f519feec486de87ed73cb92d3cac802400000000" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="CMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="1114112" CHECKSUM="0x9725986B" BIN_FILE_VERSION="6.1.7601.18015" BIN_PRODUCT_VERSION="6.1.7601.18015" PRODUCT_VERSION="6.1.7601.18015" FILE_DESCRIPTION="Archivo DLL de cliente API BASE de Windows NT" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Sistema operativo Microsoft® Windows®" FILE_VERSION="6.1.7601.18015 (win7sp1_gdr.121129-1432)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. Reservados todos los derechos." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x11B7A6" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="6.1.7601.18015" UPTO_BIN_PRODUCT_VERSION="6.1.7601.18015" LINK_DATE="11/30/2012 04:56:41" UPTO_LINK_DATE="11/30/2012 04:56:41" EXPORT_NAME="KERNEL32.dll" VER_LANGUAGE="Español (España, internacional) [0xc0a]" EXE_WRAPPER="0x0" FILE_ID="0000f9ac70c562ba70dd7917e99b00ed6878531de66f" PROGRAM_ID="0000f519feec486de87ed73cb92d3cac802400000000" />
</EXE>
</DATABASE>


* I´ve tried in an old xp and it works!

Any idea?

chmee

  • Contributor
  • Hero Member
  • *****
  • Posts: 1031
  • raw2cdng
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #863 on: May 29, 2014, 09:28:43 PM »
Is .net4.0 installed?

contactarproyectos

  • New to the forum
  • *
  • Posts: 4
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #864 on: May 30, 2014, 12:21:25 AM »
It´s installed.

A while ago I made some changes in the regional language settings for another program compatibility (pro tools), but today I restored to default and nothing happened.
Could be something there, maybe?

Thanks for your time chmee

chmee

  • Contributor
  • Hero Member
  • *****
  • Posts: 1031
  • raw2cdng
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #865 on: May 30, 2014, 01:08:20 AM »
try to save an empty textfile into the roaming-path i described before, then name it raw2cdng.settings.json or (>=1.5.0) raw2cdng.2.settings.json.

contactarproyectos

  • New to the forum
  • *
  • Posts: 4
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #866 on: May 30, 2014, 04:49:34 PM »
Done, but nothing has changed.

What about updating to netframework 4.5? It´s safe? Vulnerability risk or something?

chmee

  • Contributor
  • Hero Member
  • *****
  • Posts: 1031
  • raw2cdng
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #867 on: May 30, 2014, 05:49:23 PM »
someone's said, it needs 4.5 - didnt found the parts i used 4.5-code.. so. the main thing is, 4.5 is NOT backward compatible to 4.0 - 4.5 is NOT an update from 4.0. if you wanna try and tell me if it works after installing 4.5, would be great. THEN i would analyze my code once again for this dotnet-thing.

ChadMuffin

  • Member
  • ***
  • Posts: 127
  • RAWsome - 5D3
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #868 on: June 07, 2014, 02:54:27 PM »
I just wanted to let you know that I used 1.5 Beta 6 and did not have any issues on my Windows 8.1, GeForce GTX 780, and pulling the footage into Premiere CC with audio synced. No pink highlights or green frames. Even when viewing the DNGs in Explorer, the images were scaled correctly and the colors were represented properly. Great work building this from the bottom up! Excited to see more to come and what Adobe does with the rumors of more DNG support.

sergiocamara93

  • Freshman
  • **
  • Posts: 58
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #869 on: June 18, 2014, 09:01:16 PM »
Hey chmee, I wanted to offer you some testing results regarding the timecode issue of the WAVs auto-sync in Resolve, I've read that your software uses the datetime of the file to generate the timecode. I've tested this and I found why Resolve it's not syncing some of the files properly. I used two files M03-1753 and M03-1755.

The timecode generated for M03-1713 and its WAV was 20:15:59:00 to 20:16:28:12 (6 more for the WAV)
The timecode generated for M03-1715 was 20:15:28:00 - 20:16:05:18 (5 more for the WAV)

I don't think is a problem of timecode generation. Its consistent for video and audio, and they seem to match but, as you see, the timecodes for the two files are not unique and overlap, therefore, when Resolve syncs them it goes to the first file it can find that has some of that timecode (the first file when shorted by name that has some of that time interval, it defaults to that and ignores the reelname - because audio doesn't catch the reelname from the folder).
The timecode match the date of creation of the file on the hard drive, that means when the .MLV was copied to the hard drive, which obviously makes files overlap because the creation times are usually close.

I believe there can be a quick workaround for this (the proper fix would be emulating the BMCC WAVs) taking the timecode start from the name of the file i.e: "1713". As I mention this would be just a workaround because in the case of having files created at the "same time" in different days the timecode would overlap, also when using different cameras, and, Resolve would go crazy again. But this is solvable. When put in different folders of the Media Pool in Resolve (Day 1, Day 2 / Camera A, Camera B...) And selecting the clips in those folders, then clicking the auto-sync, the two files sync properly and only with the WAVs that have the same timecode in that folder. If timecodes did not overlap in one folder, we should be just fine. It's not perfect, but it works.

Well, in any case, I hope some of this testing offers some insight and helps in solving the problem.

Tech details:
- Camera: 5D Mark III
- raw2cdng 5.0beta6
- MLV / Nightly ML build of February 14th 2014 (I know, it's an old build, but I'm not aware of any changes on the timecode/name/file creation process that can influence the issue reported)
5D Mark III

Johannes

  • New to the forum
  • *
  • Posts: 26
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #870 on: June 22, 2014, 10:04:19 PM »
Create clean cDNG´s from MLV would be so great! Cant wait!

actingnurse

  • New to the forum
  • *
  • Posts: 38
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #871 on: June 23, 2014, 02:47:13 AM »
Create clean cDNG´s from MLV would be so great! Cant wait!

Raw2CDNG 1.5.0 beta 6 is what I use and it does break MLV files apart into wav and CDNG..

actingnurse

  • New to the forum
  • *
  • Posts: 38
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #872 on: June 23, 2014, 02:48:41 AM »
I just wanted to let you know that I used 1.5 Beta 6 and did not have any issues on my Windows 8.1, GeForce GTX 780, and pulling the footage into Premiere CC with audio synced. No pink highlights or green frames. Even when viewing the DNGs in Explorer, the images were scaled correctly and the colors were represented properly. Great work building this from the bottom up! Excited to see more to come and what Adobe does with the rumors of more DNG support.

Chad - ditto here. I use 1.5.0 beta 6 with Adobe Premiere CC 2014 on Windows 8.1, GeForce GTX 670M, and have no issues.

chmee

  • Contributor
  • Hero Member
  • *****
  • Posts: 1031
  • raw2cdng
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #873 on: June 23, 2014, 10:24:29 AM »
thanks. so, next days i will turn back on coding. i'll try to implement vertical banding and chroma smoothing. as i've seen, the new dng-import-module in premiere 8.0 does pink highlights as well. hummm, and they#re working on a fix. do some tests today. i hoped, i can delete/forget the highlightfix.

@sergiocamara93
thanks for tests. it wonders me, why it behaves this way. its not unusual, that there are more files with nearly the same timecode (multicam).
Quote
..proper fix would be emulating the BMCC WAVs..
by now i tried to do my best to implement all things, that are in bmcc-wav files.
http://www.magiclantern.fm/forum/index.php?topic=11520.0

chmee

  • Contributor
  • Hero Member
  • *****
  • Posts: 1031
  • raw2cdng
Re: The CinemaDNG Discussion (raw2cdng)
« Reply #874 on: June 24, 2014, 04:13:59 PM »
by the way. i told days ago i wrote a diagnostic tool for mlv-files. here it is.

mlvdiag 1.0.0 - download here
whats the idea behind it?
* analytic look into the blockdata saved inside the mlv
* important for me: saving a minimal set of blocks into a new file for app-problems and debugging
-> it writes all metadata, one videoframe and one audiochunk into a new file, found on same place as original.
-> if you have some problems with raw2cdng-crashes this minimal mlv can help me to find those bugs.
* its not perfect, but it works :) ('til now)



regards chmee