raw2dng.app
Convert your magic lantern files to .dng image sequences
raw2dng.app is a GUI wrapper based on platypus (http://sveinbjorn.org/platypus) for the command line tools raw2dng by Alex.
I'm developing this to help osx user who are not familiar with command line stuff.
The approach is to have a simple draggable app that will make it easy for anyone to convert raw video file made with Magic Lantern.
(https://dl.dropboxusercontent.com/u/123918/MagicLantern/MLTools/img/raw2dng.png)
To use it simply extract the app from the last .zip package and optionally move it to your Applications folder, I like to have the icon in the finder window as you can see in the video so to have it always ready.
Once extracted drop a ML .raw file on it's icon or double click it and drag the file on the window of the app.
It will convert the file in a new subfolder in the same folder of the raw file converted. The name of the subfolder is same as the .raw file converted
DOWNLOAD LINKSLAST VERSION 0.13 DIRECT LINK
(https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.13.zip)All versions are hosted here: ML Things Downloads (https://bitbucket.org/600dplus/magic-lantern-things/downloads)
To install: Just delete/overwrite any older version you have with last .zip package contents
Optional SettingsSince 0.13 is possible to set some options. To open up settings dialogs you need to have to drag raw2dng.app icon into an open raw2dng.app windows (like you do with raw files to convert them).
So far you can set:
- a working folder were raw files will be copied and then converted (if none selected file will be converted in the same directory the raw is)
- ProRes generation On/Off
- Custo or auto White Balance (default auto)
To Do-Find a way to make bigger file conversion work
-Batch convert all raw file inside a folder- MLTools integration (half done)
Changes Log- raw2dng.app.0.13.zip First test for conversion options like set wb, working folder and optional ProResHQ 4444.
- raw2dng.app.0.12.zip Updated bin, removed jpg and avi conversion, for now only dng and ProRes.
- raw2dng.app.0.11.zip Cleanup, updated bin with vertical banding fixes, added jpg and avi conversion too (but slows down the process for multiple files).
- raw2dng.app.0.10.zip Accepts more than one file or folder dropped at time (from bashi suggestion).
- raw2dng.app.0.9.zip New way to convert file directly into destination folder, check if it's working or you too.
- raw2dng.app.0.8.zip Fixed some error in finding raw files in folders
- raw2dng.app.0.7.zip Updated with source fixes (2013/05/22)
- raw2dng.app.0.6.zip better handling of generated .dng by Captain Hook (works with 62Gb file too, now)
- raw2dng.app.0.5.zip fixed 64bit conversions problems by rodobot (confirmed workin for file bigger than 10GB)
- raw2dng.app.0.4.zip First folder support implementation, same name of the raw file for the generated folder (from swinxx suggestion)
- raw2dng.app.0.3.zip Can convert more than one raw for minute
- raw2dng.app.0.2.zip Fixes spaces in folder errors by Captain Hook
- raw2dng.app.zip first release
Known issues Wrapper package- dead pixel problems, (going back to ufraw maybe will solve it)
Known issues osx command line tool- Folder are not full cinemaDNG (they can't be imported in DaVinci Resolve) - Dedicated Discussion Thread (http://www.magiclantern.fm/forum/index.php?topic=5618.0) -
Solved issues- raw2dng not compatible with latest ML nightly recorded raw
- Generate dng directly into dest. folder
- Latest (22/05/2013) compatibility fix from source
- Problems with more than 42 Gb raw (thank's to Captain Hook for the fix (http://www.magiclantern.fm/forum/index.php?topic=5508.msg38594#msg38594))
- Can't convert more than one file for minute
- Don't works with spaces in folder names for .raw source (thank's to Captain Hook for the fix (http://www.magiclantern.fm/forum/index.php?topic=5404.msg37101#msg37101))
- Can't convert file bigger than 2Gb. (thank's to rodobot for the fix (http://www.magiclantern.fm/forum/index.php?topic=5247.msg38080#msg38080))
Tip: To being informed about new updates follow this topic
Wonderful
I've not yet being able to record raw file with my 600D so far, so if someone can send me a link for a file big enough to give the size conversion error I'll try to see if I can fix that
Why not? What happened?
If I compile with module on I get a too big file that will not load for the size check, I'm downloading your build now to make it
EDIT: I have my "unconvertible" big raw file done with TL
hello,
today i went out with my camera to shoot some great raw videos (nearly 40 shots.) great.
when i came back i uploaded the files to my mac and wanted to convert them while having a coffee :)
perhaps someone can help me here.. batch processing of mulitple raw files is not working, so my question: is it possible that someone can implement that?
and the second thing.. the conversion app made directories with complete different names.. is it possible to change the name of the made directories to the same name as the raw file.. that would be really handy..
so it would be great if i could take a bunch of raw files, put them into the converter and then the converter creates directories with the name of the raw files with the dng files in it..
have i missed something or is this just not possible yet.?
all in all great!
thx
thx re
It's on the "to do" list.
great.
thx
Great work scrax, and thanks again squig for all your help!
beta 0.4 (https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.4.zip) is out with a first test for folder support, report any bugs found.
hahahahaha... you are great!!!
this works pretty good here.. also with long folder names and spaces in between..
so when the app also supports batch processing it is perfect.
thank you very very much.
Quote from: swinxx on May 19, 2013, 07:32:40 PM
hahahahaha... you are great!!!
this works pretty good here.. also with long folder names and spaces in between..
so when the app also supports batch processing it is perfect.
thank you very very much.
have you tried dropping a DCIM folder on 0.4?
aahhh. ok. now i understand.
i can drop a folder with multiple files. ok.. great.
i tried to drop multiple selected files.. and that didn´t work..
but now i understand.
great. that saves a LOT of time now.
thank you so much
Quote from: scrax on May 19, 2013, 07:34:12 PM
have you tried dropping a DCIM folder on 0.4?
aaaa, you,re tha man Scrax! Tried dropping a dcim folder containing two clips and the both got converted into two separate folders. Awesome!
Beautiful work Scrax. It evens names the folders the same name as the original file. Even better :)
Are Windows users being left behind here?
Quote from: eoshq on May 19, 2013, 09:43:08 PM
Are Windows users being left behind here?
Already exists a batchconversion tool for windows I believe?
Thanks Scrax we needed this!
I'm happy to see that this is working and useful, thank's for the feedback.
What about a proper icon?
So far it uses ML logo as app icon, but I'll like to use a specific icon and if someone want to suggest something would be great!
Scraw it still doesn't work with the larger file sizes. Anything over 2 gb won't convert for me (I'll do them on my windows computer) but still this is a huge improvement thanks
so far didn't found any solution, still working on it.
I've found a way to compile for 64bit seem, but chdk-dng.c gives problems:
MacBook-Pro-di-scrax:raw_rec scrax$ make
[ CC ] raw_rec.o
[ MODULE ] raw_rec.mo
[ GCC ] raw2dng
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:134: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:134: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:134: error: (near initialization for 'ifd0[3].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:138: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:138: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:138: error: (near initialization for 'ifd0[7].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:139: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:139: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:139: error: (near initialization for 'ifd0[8].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:147: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:147: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:147: error: (near initialization for 'ifd0[16].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:148: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:148: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:148: error: (near initialization for 'ifd0[17].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:150: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:150: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:150: error: (near initialization for 'ifd0[19].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:155: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:155: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:155: error: (near initialization for 'ifd0[24].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:156: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:156: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:156: error: (near initialization for 'ifd0[25].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:157: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:157: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:157: error: (near initialization for 'ifd0[26].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:158: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:158: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:158: error: (near initialization for 'ifd0[27].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:159: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:159: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:159: error: (near initialization for 'ifd0[28].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:160: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:160: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:160: error: (near initialization for 'ifd0[29].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:161: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:161: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:161: error: (near initialization for 'ifd0[30].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:162: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:162: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:162: error: (near initialization for 'ifd0[31].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:171: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:171: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:171: error: (near initialization for 'ifd1[1].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:172: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:172: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:172: error: (near initialization for 'ifd1[2].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:173: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:173: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:173: error: (near initialization for 'ifd1[3].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:178: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:178: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:178: error: (near initialization for 'ifd1[8].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:179: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:179: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:179: error: (near initialization for 'ifd1[9].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:180: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:180: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:180: error: (near initialization for 'ifd1[10].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:181: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:181: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:181: error: (near initialization for 'ifd1[11].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:185: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:185: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:185: error: (near initialization for 'ifd1[15].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:186: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:186: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:186: error: (near initialization for 'ifd1[16].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:187: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:187: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:187: error: (near initialization for 'ifd1[17].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:188: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:188: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:188: error: (near initialization for 'ifd1[18].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:189: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:189: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:189: error: (near initialization for 'ifd1[19].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:190: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:190: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:190: error: (near initialization for 'ifd1[20].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:202: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:202: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:202: error: (near initialization for 'exif_ifd[0].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:203: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:203: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:203: error: (near initialization for 'exif_ifd[1].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:205: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:205: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:205: error: (near initialization for 'exif_ifd[3].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:207: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:207: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:207: error: (near initialization for 'exif_ifd[5].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:208: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:208: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:208: error: (near initialization for 'exif_ifd[6].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:209: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:209: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:209: error: (near initialization for 'exif_ifd[7].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:210: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:210: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:210: error: (near initialization for 'exif_ifd[8].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:211: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:211: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:211: error: (near initialization for 'exif_ifd[9].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:214: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:214: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:214: error: (near initialization for 'exif_ifd[12].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:215: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:215: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:215: error: (near initialization for 'exif_ifd[13].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:216: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:216: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:216: error: (near initialization for 'exif_ifd[14].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:217: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:217: error: initializer element is not constant
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:217: error: (near initialization for 'exif_ifd[15].offset')
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c: In function 'create_dng_header':
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:284: warning: cast from pointer to integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:366: warning: cast to pointer from integer of different size
/Users/scrax/magic-lantern-fixes/modules/raw_rec/../../src/chdk-dng.c:395: warning: cast to pointer from integer of different size
lipo: can't figure out the architecture type of: /var/folders/93/ygydrxys37s1s77l9f05m5hw0000gn/T//cc4X1vSY.out
make: *** [raw2dng] Error 1
If compiled with chdk-dng.c in 32bit and raw2dng.c in 64bit I have a different error than not a raw file:
MacBook-Pro-di-scrax:raw_rec scrax$ make
[ GCC ] raw2dng
[ GCC ] raw2dng
../lv_rec/raw2dng.c: In function 'main':
../lv_rec/raw2dng.c:33: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
../lv_rec/raw2dng.c:33: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
../lv_rec/raw2dng.c: In function 'main':
../lv_rec/raw2dng.c:33: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
../lv_rec/raw2dng.c:33: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
[ GCC ] raw2dng
ld: warning: ignoring file chdk-dng.o, file was built for i386 which is not the architecture being linked (x86_64): chdk-dng.o
MacBook-Pro-di-scrax:raw_rec scrax$ ./raw2dng /Users/scrax/Movies/raw\ tests/M0000000.RAW
Error: sizeof(lv_rec_file_footer_t) = 200, should be 192
Makefile
raw2dng: FORCE
$(call build,GCC,gcc -c $(SRC_DIR)/chdk-dng.c -m32 -O2 -Wall -I$(SRC_DIR) -arch i386)
$(call build,GCC,gcc -c ../lv_rec/raw2dng.c -m32 -O2 -Wall -I$(SRC_DIR) -arch i386 -arch x86_64 -D_FILE_OFFSET_BITS=64)
$(call build,GCC,gcc raw2dng.o chdk-dng.o -o raw2dng -lm -m32 -arch i386 -arch x86_64)
Quote from: scrax on May 19, 2013, 07:03:13 PM
beta 0.4 (https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.4.zip) is out with a first test for folder support, report any bugs found.
Nice work, thanks mate. Now we just have get over the 64bit 2Gb limit hurdle.
Following. As stated since the first release... MUCH APPRECIATED!
Didn't realize you were already 4 updates in hahaha
EDIT: How do I follow a topic(preferably with an email), that I didn't create?
Quote from: scrax on May 19, 2013, 11:55:05 PM
If compiled with chdk-dng.c in 32bit and raw2dng.c in 64bit I have a different error than not a raw file:
MacBook-Pro-di-scrax:raw_rec scrax$ make
[ GCC ] raw2dng
[ GCC ] raw2dng
../lv_rec/raw2dng.c: In function 'main':
../lv_rec/raw2dng.c:33: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
../lv_rec/raw2dng.c:33: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
../lv_rec/raw2dng.c: In function 'main':
../lv_rec/raw2dng.c:33: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
../lv_rec/raw2dng.c:33: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
[ GCC ] raw2dng
ld: warning: ignoring file chdk-dng.o, file was built for i386 which is not the architecture being linked (x86_64): chdk-dng.o
MacBook-Pro-di-scrax:raw_rec scrax$ ./raw2dng /Users/scrax/Movies/raw\ tests/M0000000.RAW
Error: sizeof(lv_rec_file_footer_t) = 200, should be 192
I think the reason the footer is of a different size on 64-bit Mac OS is because the pointer type is now 8 bytes wide and
8 byte aligned. raw_info has a pointer as the second field in the struct. The compiler skips 4 bytes to align the pointer to the next 8-byte word and it is 8 bytes wide. This would account for the size being 8 bytes off. Maybe changing the void* to an unsigned int might fix the alignment. Not sure what casting that will affect elsewhere. I will try later if I can find some time.
Don't know anything in programming, so just would like to thanks for your jobs, it work like a charm, experience some bug with the 0.1 version & old firmware.
Now can't find something wrong, except the 2go files, but i'll wait!
Thanks
i can`t open the DNG files !
mac osx 10.7 + cameraraw 8.1 (newest update)
will not open the DNG´S !
any ideas ???
• in Photoshop CS6
https://dl.dropboxusercontent.com/u/33878668/camerarawupdate.jpg
• the Adobe DNG converter
https://dl.dropboxusercontent.com/u/33878668/dng.jpg
• & After effects !
https://dl.dropboxusercontent.com/u/33878668/ae.jpg
Somebody else had the same problem. Version 7 works fine on Lion and Mountain Lion.
Quote from: dngrhm on May 21, 2013, 12:07:35 AM
I think the reason the footer is of a different size on 64-bit Mac OS is because the pointer type is now 8 bytes wide and 8 byte aligned. raw_info has a pointer as the second field in the struct. The compiler skips 4 bytes to align the pointer to the next 8-byte word and it is 8 bytes wide. This would account for the size being 8 bytes off. Maybe changing the void* to an unsigned int might fix the alignment. Not sure what casting that will affect elsewhere. I will try later if I can find some time.
Don't seems really an issue with the footer size, if that check is commented out I get the second one as error and so on, I suppose that all the stuff needed to do those check is missing because of chdk.dng compiled only in 32bit and not added to the 64bit raw2dng executable.
I suppose that once chdk.dng.c could be compiled with -arch x86_64 it should work good
Quote from: ZUPPORT on May 21, 2013, 07:34:29 AM
i can`t open the DNG files !
mac osx 10.7 + cameraraw 8.1 (newest update)
will not open the DNG´S !
any ideas ???
I'm still with 7 for now.
Scrax please check http://www.magiclantern.fm/forum/index.php?topic=5247.1375 post #1376.
The guy might have found a way to fix 2gb limit.
Quote from: KMA_WWC on May 21, 2013, 08:58:20 AM
Scrax please check http://www.magiclantern.fm/forum/index.php?topic=5247.1375 post #1376.
The guy might have found a way to fix 2gb limit.
I'm testing it ;)
EDIT: Seems working! is generating something :D
will update to 0.5 in a few minutes
Let me know if you want me to give it a try before making it public. I have lots 4gb+ files.
Just tested 0.5 on a 3gig file.. works here. Thanks Scrax!
Updated first topic with the new fixes by rodobot, now we can convert also file bigger than 2Gb.
Please report if it works also with huge file like 10GB
Quote from: CaptainHook on May 21, 2013, 09:35:18 AM
Just tested 0.5 on a 3gig file.. works here. Thanks Scrax!
:)
Good to hear it, credits for the fix goes to rodobot...
I'm just making the packaging
Quote from: scrax on May 21, 2013, 09:04:36 AM
I'm testing it ;)
EDIT: Seems working! is generating something :D
will update to 0.5 in a few minutes
Perfect! Mad props scrax and rodobot for getting this working. I did a batch with one file over 2Gb. Recording a huge file now.
Quote from: squig on May 21, 2013, 09:36:53 AM
Perfect! Mad props scrax and rodobot for getting this working. I did a batch with one file over 2Gb, it's good for any size now yeah?
We just need someone with the latest build (exfat record ready build) to shoot/test out files bigger than 10gb and that would be perfect.
doin it now
Nevermind I got it!
system disk is full :-[ time to get that raid array. I recorded a 60Gb file on my 64Gb card and was going to stop recording @ 60Gb but it stopped automatically @ 60 and is 62Gb in length. Not sure if it's gonna be corrupted, just moving some files around first.
Quote from: squig on May 21, 2013, 09:57:31 AM
system disk is full :-[ time to get that raid array. I recorded a 60Gb file on my 64Gb card and was going to stop recording @ 60Gb but it stopped automatically @ 60 and is 62Gb in length. Not sure if it's gonna be corrupted, just moving some files around first.
Haha, so basically you decided to take the test to another extreme level with recording 60gb file :)
I like to break stuff, it's one thing I'm good at.
Everybody grab a coffee, it's gonna take another 20min to clean up this drive. ;D
Just converted a 15.83GB file.. Thanks again Scrax, rodobot, A1ex, and all ML team. :)
Although it's 4am I couldn't resist, just tested a 10.5GB file, everything works perfectly! This is amazing! Thanks again to everyone involved :D
Quote from: squig on May 21, 2013, 10:17:58 AM
I like to break stuff, it's one thing I'm good at.
;D
Quote from: CaptainHook on May 21, 2013, 10:20:24 AM
Just converted a 15.83GB file.. Thanks again Scrax, rodobot, A1ex, and all ML team. :)
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, some changes in chdk-dng.c maybe broke it. Once solved will update the app to keep it up to date with last code changes
I've tested this too on OSX Mountain Lion. Working great for 8GB file so far! I'll make a test tomorrow with a larger file. Great work this is awesome!!!
Error: API version mismatch: 679478560
ls: *.dng: No such file or directory
Nothing converted
::)
Ok well now we know not to let the file write to the end of the card. (I think we already knew that)
Quote from: scrax on May 21, 2013, 10:26:59 AM
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, some changes in chdk-dng.c maybe broke it. Once solved will update the app to keep it up to date with last code changes
Is this another one since the 0.5 that I tested?
Quote from: squig on May 21, 2013, 10:44:39 AM
Is this another one since the 0.5 that I tested?
Yes, 0.5 code was updated 18.05.2013 but with the 4Gb fix added today
Quote from: scrax on May 21, 2013, 10:26:59 AMGood 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. :D
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
Tried a 52Gb file
/Applications/raw2dng.app/Contents/Resources/script: line 10: /bin/ls: Argument list too long
Nothing converted
:'(
Quote from: squig on May 21, 2013, 11:22:52 AM
Tried a 52Gb file
/Applications/raw2dng.app/Contents/Resources/script: line 10: /bin/ls: Argument list too long
Nothing converted
:'(
52Gb file, now that is one massive moviefile :)!!
Now I'm getting the same error with every file, even under 2Gb. :'(
Ok I think I get what's going on now. raw2dng swallowed up the 52Gb file, the app is now 53.05Gb hehe.
I trashed the app. reinstalled and converted a 21Gb file, opened in ACR 7, no issues.
Scrax - may need to replace "ls" with "find" or something similar?
Gotta get home from work and some serious raw-encoding, seriously, this is so funky
Tested 42Gb and 37Gb conversion, no issues.
So if the App is ballooning when saving large files, perhaps Raw2Dng should show some kind of dialog box to save to a location other than the Raw2Dng app?? Will this overcome the file size errors and not have to delete the app everytime?
The app only ballooned with the 52Gb file (twice). Saving to the app isn't a feature, it's a bug triggered by the 52Gb file, everything 42Gb and under is being saved where it's supposed to be. I haven't tested between 42 and 52Gb.
It's quite slow with the larger files so a 64bit version would be a welcome addition.
THIS IS WHAT I HAVE BEEN WATING FOR, THE NEWEST VERSION ROCKS! THANK YOU ALL FOR YOUR HARD WORK!!
Hello,
First of all, thank you for the tremendous work done on the 5D Raw and the raw2dng.app !!
I wanted to know if it was possible to incorporate CinemaDNG specifications in the conversion of raw to DNG. In fact, Da Vinci Resolve does not recognize DNG or partially because they do not contain the following metadatas : Time Code, Frame Rate, T-Stop, Reel Name, Camera Label.
For rushes of BMCC (also in Cinema DNG), these metadatas are only stored in the first DNG, which allows it to be read in Resolve and help us to create proxies (id. ProRes LT) to mount on any NLE. Then we can make a XML to conform and send it to Da Vinci. This would avoid making color corrections before the editing and would give to the 5D Raw video, access to use for a feature film workflow.
It's being looked at, nobody's figured out how to do it yet.
Thank you Scrax!
My tests have shown that with .5 batch is working on batch 4gb files, I have yet to test beyond that, no bugs, no hickups, I'll fill up my card tonight and report back, thanks again scrax!
I do use resolve as a grading tool
regular dng files are not working on resolve.. so i have to go through photoshop, AE or any other conversion method
Could raw2dng make cinema dng files?
This would make the workflow easier
thanks
f
Quote from: squig on May 21, 2013, 06:18:22 PM
It's being looked at, nobody's figured out how to do it yet.
No progress since then :D Welcome to the bleeding edge. The workflow might suck, but the view is nice.
Perhaps Adobe has released an SDK Cinema DNG
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 (P.20)
Quote from: squig on May 21, 2013, 03:56:28 PM
The app only ballooned with the 52Gb file (twice). Saving to the app isn't a feature, it's a bug triggered by the 52Gb file, everything 42Gb and under is being saved where it's supposed to be. I haven't tested between 42 and 52Gb.
It's quite slow with the larger files so a 64bit version would be a welcome addition.
I suppose that for the 52Gb it converted most of the stuff but since the dng are moved after finishing conversion they were not moved out from the app
In future without trashing all the app just right click it and select show package contents, then navigate to Resources folder and you will find all the dng converted.
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.
Quote from: CaptainHook on May 21, 2013, 12:38:15 PM
Scrax - may need to replace "ls" with "find" or something similar?
where? I don't get the difference but explain me more please, since probably it could be improved a lot.
Quote from: 12georgiadis on May 22, 2013, 12:15:40 AM
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) ***
Quote from: scrax on May 22, 2013, 12:42:59 AM
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
Quote from: CaptainHook on May 22, 2013, 06:09:49 AM
*** Warning: IFD 0 Model is not NULL terminated ***
*** Warning: IFD 0 UniqueCameraModel is not NULL terminated ***
I don't get those with dng_validate, can you send me a broken dng?
It worked :) I just opened a 60Gb file. Thx Captain
Quote from: a1ex on May 22, 2013, 06:44:53 AM
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
Quote from: squig on May 22, 2013, 07:08:28 AM
It worked :) I just opened a 60Gb file. Thx Captain
Great, i'll leave the rest to Scrax. :)
Quote from: CaptainHook on May 22, 2013, 06:09:49 AM
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) ***
Ok, sorry if I'm in the wrong thread (I'm new), I did not know it had been discussed elsewhere. Do you have the link to the right thread?
If I understand correctly, the files that come out of raw2DNG contain metadata errors that are the reason why Da Vinci Resolve does not recognize the result of DNG files (in a folder) as Cinema DNG?
With Black Magic Cinema Camera for example, additional metadata (timecode, Frame Rate, T-Stop, Reel Name, Camera Label) are contained in the first DNG but not in the other DNG file.
If there is a way for the DNG to be recognized in Da Vinci Resolve, the workflow would Become the same as the BMCC and could be used to make feature films. But it's more complicated if you have to go through Photoshop and After Effects before the editing.
Quote from: 12georgiadis on May 22, 2013, 10:15:00 AM
If there is a way for the DNG to be recognized in Da Vinci Resolve, the workflow would Become the same as the BMCC and could be used to make feature films. But it's more complicated if you have to go through Photoshop and After Effects before the editing.
We know. It's a work in progress.
New release with fixes from Captain Hook: raw2dng.app.0.6.zip
for the problem with dng_validate, here a raw2dng compiled with latest sources, just replace it in the app package to test it:
Ok with latest sources I have no more problem with photoshop so here right to 0.7 check the dng_validate problem should be fixed: https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.7.zip
Quote from: CaptainHook on May 22, 2013, 07:12:14 AM
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:
Updating source fixed all my problem with photoshop! Now 0.7 is up to date with source
Hi scarx,
Thanks so much for the lightning fast development of an easy to use app that now seems very solid!
One thing though: You write Known Issues: None, but there's still that thing with the dng's not being cinemaDNG's. I just wanted to make sure you guys are aware of the importance of this part about the files being less easy to handle that way. Being able to import them into Resolve would make a huge difference for many as it would not only improve and enhance the workflow, but also make it a more professional solution in terms of consistency and file generations/handling.
Or is the issue somewhere else?
Thanks anyway for providing this great solution so far.
Quote from: cinema5D on May 22, 2013, 11:52:47 AM
Hi scarx,
Thanks so much for the lightning fast development of an easy to use app that now seems very solid!
One thing though: You write Known Issues: None, but there's still that thing with the dng's not being cinemaDNG's. I just wanted to make sure you guys are aware of the importance of this part about the files being less easy to handle that way. Being able to import them into Resolve would make a huge difference for many as it would not only improve and enhance the workflow, but also make it a more professional solution in terms of consistency and file generations/handling.
Or is the issue somewhere else?
Thanks anyway for providing this great solution so far.
Your are right, the dng file are generated by raw2dng (developed by Alex) that's inside the raw2dng.app package so this is something that need to be solved there, the know issue are relative to the GUI wrapper that do the work of starting the command line tool for the raw dragged in.
Added it to first topic
I think alex is already working on it. I can't test that problem because don't know Resolve and all those raw video procedures with proxies and so on.
What is the basic raw video workflow?
RAW to DNG
folder that should be cinemaDNG
Editing software
I saw that there is a win batch converted that converts to tiff and makes proxy but didn't get why or what they are.
Quote from: scrax on May 22, 2013, 12:02:56 PM
Your are right, the dng file are generated by raw2dng (developed by Alex) that's inside the raw2dng.app package so this is something that need to be solved there, the know issue are relative to the GUI wrapper that do the work of starting the command line tool for the raw dragged in.
Added it to first topic
I think alex is already working on it. I can't test that problem because don't know Resolve and all those raw video procedures with proxies and so on.
What is the basic raw video workflow?
RAW to DNG
folder that should be cinemaDNG
Editing software
I saw that there is a win batch converted that converts to tiff and makes proxy but didn't get why or what they are.
Scrax, here is the workflow that I do with the Black Magic Cinema Camera that records in 12-bit Raw Cinema DNG (which work the same with the 5D Raw if you can transform raw to DNG DNG cinema..) :
When you open Da Vinci Resolve It recognizes Cinema DNG because 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.
Then we created proxies to ProRes 422, which only contain the metadata cinema to edit the footage on any professional NLE (Premiere, FCP X, Avid, etc..).
Once finished editing, you export the project in XML and conformation is due to metadata Cinema, to link to the DNG. From there, Resolve recognizes files and keeps the edit right.
We can then do the color grading in raw.
If DNG is converted to Tiff is no longer raw.
And there is a light version of Da Vinci Resolve which is free and can handle 1920 X 1080 resolution. So, perfect to test the Cinema DNG compatibility ;-)
Quote from: 12georgiadis on May 22, 2013, 12:32:30 PM
And there is a light version of Da Vinci Resolve which is free and can handle 1920 X 1080 resolution. So, perfect to test the Cinema DNG compatibility ;-)
Yes I were to download it but they asked registration. :)
I think the cinemaDNG discussion belongs in this thread:
http://www.magiclantern.fm/forum/index.php?topic=5404.0
Quote from: 12georgiadis on May 22, 2013, 12:25:57 PM
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. :)
Quote from: CaptainHook on May 22, 2013, 12:44:06 PM
I think the cinemaDNG discussion belongs in this thread:
http://www.magiclantern.fm/forum/index.php?topic=5404.0
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. :)
Thanks for the informations. So if these tags are added (TC + DNG's tags from chapter 4) it should theorically work in Resolve?
i have been trying to find info on how to create CinemaDNG... since its open source everything seems available freely
adobe official page with white papers and specs: http://www.adobe.com/devnet/cinemadng.html
some interesting discussion about converting dng to cinemadng : http://forums.creativecow.net/thread/277/22358
im no coder but im trying hard to figure it out...it must be really a difference in metadata xmp data
Quote from: Felixlgr on May 22, 2013, 09:05:58 PM
i have been trying to find info on how to create CinemaDNG... since its open source everything seems available freely
adobe official page with white papers and specs: http://www.adobe.com/devnet/cinemadng.html
some interesting discussion about converting dng to cinemadng : http://forums.creativecow.net/thread/277/22358
im no coder but im trying hard to figure it out...it must be really a difference in metadata xmp data
Thank you for the creative cow link. So it could be the thumbnail added by Adobe DNG Converter (if there is a reconversion after raw2DNG) that pose a compatibility problem. Perhaps by removing it, the DNG would work with resolve =)
it would be so great to make the raw dngs work with resolve :)
thx to the developers.. hope you will be able to make it happen.
The CinemaDNG Discussion
http://www.magiclantern.fm/forum/index.php?topic=5618.msg39228;topicseen#msg39228
Quote from: Lars Steenhoff on May 23, 2013, 01:36:51 PM
The CinemaDNG Discussion
http://www.magiclantern.fm/forum/index.php?topic=5618.msg39228;topicseen#msg39228
thanks for the link it was really needed, will put it in the first topic
Quote from: scrax on May 22, 2013, 12:40:51 PM
Yes I were to download it but they asked registration. :)
Thanks for the explanation. Regarding Resolve registration simply input anything into the fields and you'll be able to download immediately. You don't have to actually register.
Cheers
some bugs, please help ((((
Hack OS 10.7.3
Beta ver.0.7
/Users/alexunderboots/Desktop/raw2dng.app/Contents/Resources/script: line 3: 93216 Segmentation fault: 11 ./raw2dng "$file_is"
with al the files?
can you describe better how you were using it?
are you booting in 64 or 32bit mode?
what's the size of the app?
yes, it happens to all the files. add them to the program, it creates a folder and then stops showing the error.
64 bit
app size 397.5 KB 397,535 bytes
do you have enough space on the disk where the file are?
yes, i try it on network and local HDD
command-line work perfect, but app - no ((((
I found some errors in the scrip but unrelated to your problem so try with 0.8 will post it right now
EDIT: https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.8.zip
thanks, its worked :D
This is fantastic! It's been able to handle everything I've thrown at it.
I would love to be able to set a destination for the output. That way I could read the RAW files straight off of the card and send the DNGs right into my hard drive. With the command line app, I would simply browse to the directory I wanted to files to be dumped into, and run the app from there. Worked like a charm.
Quote from: mnteddy on May 25, 2013, 06:29:34 PM
This is fantastic! It's been able to handle everything I've thrown at it.
I would love to be able to set a destination for the output. That way I could read the RAW files straight off of the card and send the DNGs right into my hard drive. With the command line app, I would simply browse to the directory I wanted to files to be dumped into, and run the app from there. Worked like a charm.
MLTools is for that (and more), but for now it's giving me problems with the crc check for moved files so I suggest you to be a little patient until raw video conversion isn't added to it. I'll post link and documentation when ready, so far I had almost none feedback so I've keept it dirty since I was able to use it without issue.
MLTools is configurable so you can choose the working folder and autoimport (using image acquisition to start it when the card is mounted).
I get "could not complete your request because an unexpected end-of-file was encountered" in PS
actually I can get 960x540 shots in
I did a 64Gb batch with 74 files using beta 0.8 and it worked without a hitch. Thx scrax.
Thanks for this Tool.
I have some complaints: I don't think it's very elegant to put the Converted Files into the Raw2Dng.app itself and copy them later... Converting Raw on external Drive - and everything gets copied twice, once to my System HD (Which is not thaat Big - SSD), and then back to drive. Sound like a hack to me ;-)
This as well messes things up, if one wants to convert multiple Raw at the same time, since they overwrite each others results...
Can't it be made that the conversion happens where the RAW file is? (without copying stuff)
This copy thing as well causes my Mac to freeze occasionally.. ;-)
Quote from: bashi on May 26, 2013, 03:28:08 PM
Thanks for this Tool.
I have some complaints: I don't think it's very elegant to put the Converted Files into the Raw2Dng.app itself and copy them later... Converting Raw on external Drive - and everything gets copied twice, once to my System HD (Which is not thaat Big - SSD), and then back to drive. Sound like a hack to me ;-)
This as well messes things up, if one wants to convert multiple Raw at the same time, since they overwrite each others results...
Can't it be made that the conversion happens where the RAW file is? (without copying stuff)
This copy thing as well causes my Mac to freeze occasionally.. ;-)
Simply put the converter app on the external harddrive and drag and drop from there. All copying and conversions will take place and space on your external harddrive and not on your computerdrive. This app is beauuutiful
That's a ridiculous workflow suggestion ;-) Why should i copy the App seven times to make seven Raw conversions (at the same time)? lol
Why does it need to copy the Dng at all? the raw2dng in terminal allows direct conversion, not? (raw2dng input output)
Quote from: bashi on May 26, 2013, 06:28:32 PM
That's a ridiculous workflow suggestion ;-) Why should i copy the App seven times to make seven Raw conversions (at the same time)? lol
Why does it need to copy the Dng at all? the raw2dng in terminal allows direct conversion, not? (raw2dng input output)
Since you can drag the whole folder onto the app you only need one app. Still ridiculous?
A bit less ridiculous? ;) thanks for the tip.
Quote from: bashi on May 26, 2013, 03:28:08 PM
I have some complaints: I don't think it's very elegant to put the Converted Files into the Raw2Dng.app itself and copy them later... Converting Raw on external Drive - and everything gets copied twice, once to my System HD (Which is not thaat Big - SSD), and then back to drive. Sound like a hack to me ;-)
This as well messes things up, if one wants to convert multiple Raw at the same time, since they overwrite each others results...
Can't it be made that the conversion happens where the RAW file is? (without copying stuff)
This copy thing as well causes my Mac to freeze occasionally.. ;-)
I have to agree, but I do glass bottles for job, not software ;)
raw2dng need to be patched to support output destination, but I have half idea on how to do it from bash. Just follow the topic for when it will be working
Ok, great, thanks.
cool job.
Quote from: bashi on May 26, 2013, 08:30:12 PM
Ok, great, thanks.
cool job.
Ok, the new version with the conversion directly inside the destination folder should work in 0.9 (https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.9.zip), please test it and report back.
Quote from: scrax on May 27, 2013, 02:59:43 PM
Ok, the new version with the conversion directly inside the destination folder should work in 0.9 (https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.9.zip), please test it and report back.
Worked perfectly! Didn,t try it with any larger files but should work fine. Very good work
Quote from: Danne on May 27, 2013, 04:27:03 PM
Worked perfectly! Didn,t try it with any larger files but should work fine. Very good work
Good, since raw2dng is the same as 0.8 file size don't matter for testing it, thank's.
How can I batch convert multiple files to dng? Also, is there a way with other software to batch convert the dngs to tiff or similar?
Quote from: olik on May 28, 2013, 12:44:50 AM
How can I batch convert multiple files to dng? Also, is there a way with other software to batch convert the dngs to tiff or similar?
You have read this thread right?
Also dude - just a gentle reminder not to be cross posting: http://www.magiclantern.fm/forum/index.php?topic=934.msg1141#msg1141
Please perform a search first and then if you don't find the answer, stick to asking in threads which already have a discussion regarding this topic.
To answer your question - yes there is software for batch extracting DNG's on both Windows and Mac. For Mac - read this thread. Windows - look here: http://www.magiclantern.fm/forum/index.php?topic=5557.0
Many thanks for your amazing little app...0.9 works like a charm here... i drop my RAW folder on it and it process everything smoothly and place everything in its own folder
keep up the good work !!
I'm getting a couple errors that cause the app not to function if it's in a directory leading up to it's containing folder that contains a space in the name. For example: If have the app here "/Applications/RAWApps", it's fine. If it's here "/Applications/Magic Lantern/RAWApps" (space in Magic Lantern", no dice. This didn't occur with earlier versions. Aside from that, still handles the .RAWs like a champ.
Keep up the good work!
Quote from: mnteddy on May 28, 2013, 03:36:52 AM
I'm getting a couple errors that cause the app not to function if it's in a directory leading up to it's containing folder that contains a space in the name. For example: If have the app here "/Applications/RAWApps", it's fine. If it's here "/Applications/Magic Lantern/RAWApps" (space in Magic Lantern", no dice. This didn't occur with earlier versions. Aside from that, still handles the .RAWs like a champ.
Keep up the good work!
will try to reproduce and fix
Hey, that works like a charm. I've had a look at the it and changed the script so it would import all files put on it, if you drop multiple Raw on it, not just the first one.
EDITII:forget the following and look next post ;-)
In INIT after checkFLDR:
elif [ -f "$1" ]; then
for i in $*
do file_is=$i
importFILE
done
else
not so sure about check for $1 and then operate on $*.... but it works in all Chases (Single File drop, Multiple File drop, Folder drop). Thank you.
EDIT: It does not work if drop Folder and Files... So still room for improvement ;-) I might look at this as well.
Ok, here is the INIT Code that works in all Cases:
INIT
for i in $*
do
if [ -d "$i" ]; then
FILES_FLDR=$i/
echo "SEARCHING: $FILES_FLDR"
checkFLDR
elif [ -f "$i" ]; then
file_is=$i
importFILE
else
echo "Drop a ML .RAW video file and/or folder here"
fi
done
exit 0
@scrax, would you mind testing it, and if it works maybe put it in app if you like?
Since i now see the app is basically a shell script, i'm thinking about implementing dcraw and ffmpeg. Dcraw for make tiff out of DNG and ffmpeg to make Video from tiff. I have tinkered the last Days with them and Automator, to batch-convert them.
But there are some issues for me... I'm not familiar with Menu builder (or how its called, the thing to make UI), and it would almost need some UI for it, out of following reasons: for dcraw i would like to set at least the WhiteBalance. Automatic does not work well enough. But this would almost require a preview of at least one DNG file. Other variant would be to have only setting for Tungsten, Daylight and others. (Kelvin would be a bit difficult sine draw does not have Kelvin, but RGB multipliers).
for ffmpeg it would make sense to be able to choose Codec or probably some Preset Codec/Container combination. (ffmpeg shell execution is quite complex, and i'm not a programmer myself, except some basic Shell/Phyton)
About xcode menu builder. Since you have used it somewhat, what you think about it? Is it difficult or relative "easy" to learn? I'm willing to spend some time. Just let me know what you thing about it there.
This for now, and now some questions:
1. Is somebody already planing an app to do this?
2. How do you feel about having this in raw2dng app? Should it be a separate app? (I think it kind of makes sense to have all together, maybe with options to do DNG and/or Tiff (or jpeg) and/or Video.)
3. Do you think there will be World Peace? ;-)
Well, let's see...
Quote from: bashi on May 28, 2013, 07:35:37 PM
Ok, here is the INIT Code that works in all Cases:
INIT
for i in $*
do
if [ -d "$i" ]; then
FILES_FLDR=$i/
echo "SEARCHING: $FILES_FLDR"
checkFLDR
elif [ -f "$i" ]; then
file_is=$i
importFILE
else
echo "Drop a ML .RAW video file and/or folder here"
fi
done
exit 0
@scrax, would you mind testing it, and if it works maybe put it in app if you like?
Good idea, adding it now, about the GUI, in raw2dng.app we are using this platypus that has just some default windows. To make other elements take a look at MLTools, if value are fixed we can have dropdown menu or some simple buttons
So far i still can't make a GUI from xcode to trigger some simple bash scripts (that in that case could be a good think to have a nicer GUI)...
0.9 does not work in my setup..
i have the raw2dng app in my dropbox folder, linked with my finder window (i can see the appicon in in the top of every finder window)
and when i drag my folders to the icon raw2dng0.8 worked as expected, but 0.9 did not convert the files (but created the dirs)
thx
I extract my app wthin the programfolder on my mac. From there I drag it to the top so it sticks on top of the folder. Then I can use the app from any location I choose to convert my folders with rawfiles.(//)
Have you try this open source? I´m not programmer, maybe you can get something about it: http://www.squared5.com/svideo/mpeg-streamclip-mac.html
It´s free for mac , windows and linux.
Quote from: swinxx on May 29, 2013, 07:09:44 AM
0.9 does not work in my setup..
i have the raw2dng app in my dropbox folder, linked with my finder window (i can see the appicon in in the top of every finder window)
and when i drag my folders to the icon raw2dng0.8 worked as expected, but 0.9 did not convert the files (but created the dirs)
thx
Do you see any message in the raw2dng window?
Quote from: bashi on May 28, 2013, 07:35:37 PM
INIT
for i in $*
do
if [ -d "$i" ]; then
FILES_FLDR=$i/
echo "SEARCHING: $FILES_FLDR"
checkFLDR
elif [ -f "$i" ]; then
file_is=$i
importFILE
else
echo "Drop a ML .RAW video file and/or folder here"
fi
done
exit 0
@scrax, would you mind testing it, and if it works maybe put it in app if you like?
Tested it and fixed with that: "$@" instead of $* because it was giving problem with spaces in files names. It's in beta 0.10 (https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.10.zip)
Quote from: budafilms on May 29, 2013, 10:42:57 AM
Have you try this open source? I´m not programmer, maybe you can get something about it: http://www.squared5.com/svideo/mpeg-streamclip-mac.html
It´s free for mac , windows and linux.
didn't tried and from the site I can't find any source or opensource license, it's free but not open for what I could understand.
I keep on getting this "Error: This ain't a lv_rec RAW file" error.
The footage was shot in a normal way. Any way to recover what's inside the .raw files? Mac.
Hi scrax,
I've been trying to edit the raw2dng app to allow me to choose a destination folder for the DNG shot folders (to save me copying the .RAW files from the CF card, and instead just extract the DNGs directly into a folder on my hard drive).
Have you got any pointers for how to edit the app in interface builder? I'm fine with the unix script, as long as there's a way to grab a chosen file path value from the GUI and use it in the script.
Quote from: electronicwomble on May 30, 2013, 10:24:48 PM
Hi scrax,
I've been trying to edit the raw2dng app to allow me to choose a destination folder for the DNG shot folders (to save me copying the .RAW files from the CF card, and instead just extract the DNGs directly into a folder on my hard drive).
Have you got any pointers for how to edit the app in interface builder? I'm fine with the unix script, as long as there's a way to grab a chosen file path value from the GUI and use it in the script.
MLTools can do that, but is less tested than raw2dng. Maybe you could tacke a look at it to see how it's working. i used cocoadialog (http://mstratman.github.io/cocoadialog/) for the dialog windows.
The idea under MLTools is that it should start and import ML media from a card to a predefined folder when the card is inserted, once copied or moved the file it should convert them based on the type of file or bracketing script (but this part is not updated with nightly builds). Last changes to raw2dng.app are not yet in MLTools (but they are maybe also not needed)
Thanks, will give that a look :)
Quote from: electronicwomble on May 30, 2013, 10:51:45 PM
Thanks, will give that a look :)
basically you should add cocoadialog.app in the package and putt something like this in the script
INIT() {
echo "raw2dng converter GUI for OsX"
echo "Beta ver.0.10"
#Make raw2dng working from any folder
#export PATH="$PATH":"$(pwd)"
mybin="$(pwd)"/
CD="CocoaDialog.app/Contents/MacOS/CocoaDialog"
rv=`$CD fileselect \
--text "Choose a folder where to import and save converted file. Now set: $workingDIR" \
--with-directory $HOME/ \
--select-only-directories`
if [ -n "$rv" ]; then
workingDIR="$rv"/
printf "Working folder: %s\n" $workingDIR
fi
}
importFILE() {
if [ "${file_is: -4}" == ".RAW" ] ; then
echo "$file_is File Supported"
name=$(basename -s .RAW "$file_is")
fldr="$(dirname "$file_is")"/
if [ "$workingDIR" ] ; then
fldr="$workingDIR"
mv "$file_is" "$workingDIR$name".RAW
fi
if [ ! -d "$fldr$name" ] ; then
mkdir "$fldr$name"
fi
cd "$fldr$name"
"$mybin"raw2dng "$fldr$name".RAW
#find . -type f -name "*.dng" -print | \
#while read filename
#do
# mv "${filename}" "$fldr$name"/
#done
else
echo "$file_is File not Supported"
fi
}
tested working for setting the folder,
but it fail conversion... :( now it works, sort of
Wanted to thank you guys. This is an excellent app. Everything worked perfectly and I enjoy this workflow a lot.
Alright guys, I'll take any help possible. I got the original RAW2DNG to work on PC, on Mac I could get files under 2GB. I've tried all the updated ones, changing scripts and even the batch ones and nothing works.
I'm using a MK3 @ 1920x1080 @ 23.98 - each time file maxed out at 4.29GB.
This is the error I'm getting -
rm: *.dng: No such file or directory
raw2dng converter GUI for OSX
Beta ver.0.10
Error: This ain't a lv_rec RAW file.
After I do that, its creates a folder but no DMGs are made.
I try again and the error I get is
raw2dng converter GUI for OSX Beta ver.0.10
/Users/ebutka/Desktop/M00000003.RAW File Supported
mkdir: /Users/ebutka/Desktop/M00000003: File exists
Error: This ain't a lv_rec RAW file.
I tried every single file. All 8 of them stopped recording on the camera due to file sizes - using the May 20th build.
Anyone have any ideas? If someone would like to give it a try, I'd be more then happy to upload the RAW file to dropbox.
hello guys.
today i have compared dngs from osx 0.10 and the newest raw2dng windows version (why? because of the vertical lines problem)
and i dont know if i am right but it seems to be there in both versions but they are a little bit smaller now? (call my crazy but i can see them.)
i have build 31_May
made a reset with canon settings
so what else can i do to eliminate this vertical noise problem?
what have you guys who fixed it done to fix it?
thx.
If you don't post images showing the problems, and also conversion logs, nobody can help you ;)
Hi alex!
I will, when i am back home again ;)
ok, i´m back home, made a comparison folder in my dropbox.
here is the link.
https://www.dropbox.com/sh/bua4hwbm8w1i47f/Db01mXRpH4/Test_31_MAY_5D_Mk3/Comparison%201
i have included all files, a raw photo file, the dng files (mac and pc) i made a screenshot out of the adobe camera raw program..
please tell me if you need more additional infos and files.
(the original raw file is also in the folder but needs some time to upload.)
thx.
I guess my pixel peeping skills are a bit sub-par, but I can't see any vertical lines or issues with these pics...
Hi alex.
When i compare (in the upper left corner between the windows) the raw photo and the raw dng i can identify vertical lines in the dng. When you are ok with that i am too, but i can see them..
Greets and thx you so much for your time and effort.
sw
it is possible to open 4gig raw movie file canon 5d mark iii
from the latest raw2dng for mac I have this message "Error: This ain't a lv_rec RAW file"
Thanks
Quote from: swinxx on May 31, 2013, 05:26:05 PM
Hi alex.
When i compare (in the upper left corner between the windows) the raw photo and the raw dng i can identify vertical lines in the dng. When you are ok with that i am too, but i can see them..
Greets and thx you so much for your time and effort.
sw
All that peeping will make yo go blind :D Looks perfectly fine to me.
What about adding also conversion of dng file to Adobe DNG Converter to have them showing right in preview?
Since ADC supports command line we can make raw2dng to save a copy of the dng that will be compatible with preview on osx, it will need ADC installed so it will be a sort of option, without ADC you got the dng like now, with ADC installed you will get both actual dng versions and a subfolder with ADC converted dng
Here a discussion about ADC conversion on mac: http://www.magiclantern.fm/forum/index.php?topic=5939.0
Hi,
First, thanks to ML people for all their great work! You guys ROCK!!!
I am having the same problem with the Error: This ain't a lv_rec RAW file" as well. I've been reading all these posts and I thought that the mac version could handle the BIG files. Is there something I'm doing wrong??
Thanks
Steve
It would be great if the .app included the original raw filename in the dng filenames, now we have usable names out of camera. This would make it easier to track footage from raw, through dng, to whatever offline codec, then back to the dngs for online.
If you use the 'New Comp from Selection' command in AE to produce compositions from image sequences, it will use the part of the filename common to all images in the sequence to name the composition. This would give you a relatively smooth process.
Drag a load of RAWs into raw2dng.app > use AE's Smart Import script to import the resulting folder full of dng sequences > do a quick one lamp grade in ACR as they import > select all the imported footage and right click for New Comp from Selection > select all the resulting comps and Add to Render Queue > If you have the right preset as default hit render
Not the prettiest workflow but manageable.
Dam...
I got it. I had to format in fat EX. Once I did that, that solved everything!! Cant' wait for someone to come out with cinema DNG for Resolve!
Steve
What is up with the new version of this that is supposed to fix the banding? :-D
Anyone working on it?
*Wish I was a coder, but i'm just a tester - i guess.
Version 0.10 came out before the banding fix.
I understand. But I'm a mac user, and would love to have it for me and my kind. ;-)
Me and you both.
Quote from: AnotherDave on June 03, 2013, 01:44:17 AM
I understand. But I'm a mac user, and would love to have it for me and my kind. ;-)
I'll upload a new version later, didn't noticed that change
Scrax, your work is incredible, I have been using raw2dng.app since it's first beta, and the progress is truly amazing (also thank you to captain hook and the others who helped with dev).
Chmee is currently working on a cinemadng converter and is getting some workable cdngs imported to resolve on a pc.
Scrax, any plans to port this to mac?
Here's the link for the thread http://www.magiclantern.fm/forum/index.php?topic=5618.25
As always, thank you all for your hard work.
It's kinda sad that the PC side seems to be advancing so much more quickly than the Mac :-/.... guess it's just the world we live in these days.
#wishiknewhowdowhatyouguysdo
Quote from: sicetime on June 03, 2013, 04:12:25 PM
Scrax, your work is incredible, I have been using raw2dng.app since it's first beta, and the progress is truly amazing (also thank you to captain hook and the others who helped with dev).
Chmee is currently working on a cinemadng converter and is getting some workable cdngs imported to resolve on a pc.
Scrax, any plans to port this to mac?
Here's the link for the thread http://www.magiclantern.fm/forum/index.php?topic=5618.25
As always, thank you all for your hard work.
Chmee will eventualy add his changes to raw2dng directly when he has finished so it will be working for any os, so far I can open it with mono, load a file and it starts the conversion :)
(http://i.imgur.com/C7Hscex.png)
EDIT: Hum... it's working, but gives windows folder structure to the name of files so they need tobe renamed after conversion
For who want to try install mono from here: http://download.mono-project.com/archive/2.10.11/macos-10-x86//MonoFramework-MRE-2.10.11.macos10.xamarin.x86.dmg
once installed open terminal write:
mono and then drop raw2cdng.exe in the terminal window you should end with something like this:
mono /Users/scrax/Downloads/raw2cdng.0.99.exepress enter and the app should load.
Quotemono
and then drop raw2cdng.exe in the terminal window you should end with something like this:
mono /Users/scrax/Downloads/raw2cdng.0.99.exe
press enter and the app should load.
I get this error
/Users/sicetime/Downloads/misc-master/raw2cdng.0.99.exe: cannot execute binary file any ideas?
you have to install mono and put the word: "mono" before the file with a spaces
scrax that worked perfectly. got it running on parralels too. I get these errors though, have you been able to process things? I am at work currently but will be testing soon and don't have any raw files here.
Jun 3 14:01:16 Andrew-Siceloffs-MacBook-Pro.local mono[1455] <Error>: kCGErrorInvalidConnection: CGSGetWindowTags: Invalid connection
Jun 3 14:01:16 Andrew-Siceloffs-MacBook-Pro.local mono[1455] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Quote from: sicetime on June 03, 2013, 08:05:49 PM
scrax that worked perfectly. got it running on parralels too. I get these errors though, have you been able to process things? I am at work currently but will be testing soon and don't have any raw files here.
Jun 3 14:01:16 Andrew-Siceloffs-MacBook-Pro.local mono[1455] <Error>: kCGErrorInvalidConnection: CGSGetWindowTags: Invalid connection
Jun 3 14:01:16 Andrew-Siceloffs-MacBook-Pro.local mono[1455] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
I have the seame errors and files generated have wrong names but if you convert hem to 16 bit they will be visible in preview so i think it works. Probably in parallels you will have no problem with files names
Are there any plans to update again with the black vertical bar fix?
I think the developer is waiting to integrate raw2cdng...
Last week and monday I had no issues with RAW. Shot a video yesterday and now Lightroom/Photoshop won't read any of the files. Is this a raw2dng problem that I might fix by reconverting from a PC instead of the mac side? I'm using .10
Will upload a new app with the last raw2dng bin with vertical banding in a few hours, also added jpg and avi converter. i have no clue if they will be useful to somebody so post your opinions, but keep in mind that for raw2dng I prefer to keep it without options to keep it simple to use.
Quote from: DerekDock on June 05, 2013, 07:22:51 PM
Last week and monday I had no issues with RAW. Shot a video yesterday and now Lightroom/Photoshop won't read any of the files. Is this a raw2dng problem that I might fix by reconverting from a PC instead of the mac side? I'm using .10
I had that problem some time ago when updating 0.4 IIRC, have you updated ML since last week?
Can you try with 0.4 with a small RAW just for a test?
Quote from: scrax on June 05, 2013, 09:41:57 PM
Will upload a new app with the last raw2dng bin with vertical banding in a few hours
Have you updated ML since last week?
Thanks. Hopefully that will help. I used the build from 5/31 on Monday and didn't catch the newest version before shooting yesterday. Just uploaded the newest build and shot a test with no problems. Go figure. I wonder if there is a way to reheader the info from yesterday?
I'm not sure to have understood right, I suppose was ML making wrong raw and not raw2dng
Quote from: scrax on June 05, 2013, 09:52:19 PM
I'm not sure to have understood right, I suppose was ML making wrong raw and not raw2dng
I'm not really sure where the problem is lying. All I know is that I took a new clip and it was fine in the current raw2dng.
Quote from: DerekDock on June 05, 2013, 10:07:47 PM
I'm not really sure where the problem is lying. All I know is that I took a new clip and it was fine in the current raw2dng.
Once I got that problem to but solved updating from source, so now you have some dng that can't be opened and not anymore the raw file?
btw
/doing last test and refinement to 0.11
Quote from: scrax on June 05, 2013, 10:36:40 PM
Once I got that problem to but solved updating from source, so now you have some dng that can't be opened and not anymore the raw file?
btw
/doing last test and refinement to 0.11
I still have the RAW files. Just no matter how many times I run them the dng's won't import anywhere.
you can try to convert it with 0.4 or 0.5 if 0.11 don't work. Here (https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.11.zip) the updated link for 0.11
thank you scrax!
Hi Scrax, Thank you very much for your contribution with this program. The last update saved me lots of clicks hehehe. Monday i got a brand new 50D, now converting files for editing a little test. Cheers from Madrid! :)
Hey Scrax! How are you buddy? Just tested the latest version with 32gb file and this is what I got:
raw2dng converter GUI for OsX
Beta ver.0.11
M05-1921 File Supported
Generating jpg preview
dyld: Library not loaded: /usr/local/lib/libexiv2.10.dylib
Referenced from: /Users/KMA_WWC/Desktop/RAWToDNG/raw2dng.app/Contents/Resources/ufraw-batch
Reason: image not found
/Users/KMA_WWC/Desktop/RAWToDNG/raw2dng.app/Contents/Resources/script: line 31: 1674 Trace/BPT trap: 5 "$UFRAW" --out-type=jpg --out-path=../"$FILE_NAME"_jpg *.dng >> "$LOG"
Generating avi preview
dyld: Library not loaded: /usr/local/Cellar/ffmpeg/1.1.3/lib/libavdevice.54.dylib
Referenced from: /Users/KMA_WWC/Desktop/RAWToDNG/raw2dng.app/Contents/Resources/ffmpeg
Reason: image not found
/Users/KMA_WWC/Desktop/RAWToDNG/raw2dng.app/Contents/Resources/script: line 31: 1676 Trace/BPT trap: 5 "$FFMPEG" -i ../"$FILE_NAME"_jpg/%6d.jpg -vcodec mjpeg -qscale 1 ../"$FILE_NAME".avi >> "$LOG"
Is this normal? It also created txt log file inside the dng folder, and also created separate empty jpeg folder. Not sure if its ok or not, but just wanted to report it.
Quote from: scrax on June 05, 2013, 09:41:57 PM
Will upload a new app with the last raw2dng bin with vertical banding in a few hours, also added jpg and avi converter. i have no clue if they will be useful to somebody so post your opinions, but keep in mind that for raw2dng I prefer to keep it without options to keep it simple to use.
I had that problem some time ago when updating 0.4 IIRC, have you updated ML since last week?
Nicely done with the update. Now, I had a dream last night about adding ProResHQ 422 or 444 and cinema DNG to the jpg and avi converter ;). Would that be possible?
Thanks again Scrax, for the app of the year
//D
Quote from: KMA_WWC on June 06, 2013, 02:54:51 AM
Hey Scrax! How are you buddy? Just tested the latest version with 32gb file and this is what I got:
raw2dng converter GUI for OsX
Beta ver.0.11
M05-1921 File Supported
Generating jpg preview
dyld: Library not loaded: /usr/local/lib/libexiv2.10.dylib
Referenced from: /Users/KMA_WWC/Desktop/RAWToDNG/raw2dng.app/Contents/Resources/ufraw-batch
Reason: image not found
/Users/KMA_WWC/Desktop/RAWToDNG/raw2dng.app/Contents/Resources/script: line 31: 1674 Trace/BPT trap: 5 "$UFRAW" --out-type=jpg --out-path=../"$FILE_NAME"_jpg *.dng >> "$LOG"
Generating avi preview
dyld: Library not loaded: /usr/local/Cellar/ffmpeg/1.1.3/lib/libavdevice.54.dylib
Referenced from: /Users/KMA_WWC/Desktop/RAWToDNG/raw2dng.app/Contents/Resources/ffmpeg
Reason: image not found
/Users/KMA_WWC/Desktop/RAWToDNG/raw2dng.app/Contents/Resources/script: line 31: 1676 Trace/BPT trap: 5 "$FFMPEG" -i ../"$FILE_NAME"_jpg/%6d.jpg -vcodec mjpeg -qscale 1 ../"$FILE_NAME".avi >> "$LOG"
Is this normal? It also created txt log file inside the dng folder, and also created separate empty jpeg folder. Not sure if its ok or not, but just wanted to report it.
Good report, those are the things that I can't easily find out, dependencies :)
So the app ufraw-batch needs more thing to work. Will try something else like ImageMagick to convert the dng.
the text log is a new addition that should have the conversion to dng report, the jpg folder is empty because of ffmpeg error
Quote from: Danne on June 06, 2013, 09:29:11 AM
Nicely done with the update. Now, I had a dream last night about adding ProResHQ 422 or 444 and cinema DNG to the jpg and avi converter ;). Would that be possible?
Thanks again Scrax, for the app of the year
//D
It can be done if there are command line tools that do it, any suggestion?from wikipedia:
QuoteOn 29 October 2011, FFmpeg introduced a free encoder, enabling ProRes 422 encoding on all FFmpeg supported platforms.
so if i can solve the ffmpeg dependencies problem ProResHQ 422 should be possible. for CinemaDNG I'm waiting for responses from Thomas Worth, he could probably help us to add it.
EDIT: Just converted to ProRes, if someone want to try, you will have to right click and select "show package contents" on raw2dng.app
The navigate to the Resources folder and open the file script in TextEdit
find this line
"$FFMPEG" -i ../"$FILE_NAME"_jpg/%6d.jpg -vcodec mjpeg -qscale 1 ../"$FILE_NAME".avi
and change it to that:
"$FFMPEG" -i ../"$FILE_NAME"_jpg/%6d.jpg -vcodec prores -profile:v 3 -qscale:v 1 ../"$FILE_NAME".mov
Scrax, I,m totally satisfied with your app. Everything added is a bonus.
Finally bought a transcend 1000x card, works perfect for 1920x1088 so gonna start collecting some raw-material soon.
Thanks!
//D
Thanks to all the feedback guys really appreciated. I hope to add CinmaDNG too in future, for now seems that ProResHQ 422 is possible, also tif gave me some errors.
I'm thinking that the best way to be sure about dependencies is to keep ffmpeg and ufraw as external optionals installations.
I can make raw2dng to detect them and if present ufraw or imagemagick it will convert to jpg, if ffmpeg present it will convert to ProResHQ, also if Adobe Dng Converter installed it could pass the dng to make them working with finder preview.
Will make 0.12 with that.
Awesome!
@scrax,
i think prores -qscale 1 is overkill. I have done some "research" on this the last couple of weeks and came up with this:
ffmpeg -f image2 -i %6d.tiff -r 24 -vcodec prores_kostya -profile:v 2 -qscale:v 6 -vendor ap10 -pix_fmt yuv422p10le -threads 4 -y -r 24 ProResHigh.mov
Let me explain some things:
the first -r 24 is necessary since ffmpeg standard framerate for image sequence would be 25
-prores_kostya is supposed to be a bit better than prores
-profile 0-3 is setting Proxy, LQ, SQ, HQ quality - SQ and HQ give almost same quality. I use 2 or 3 there
-qscale:v 6 Settings between 5 - 10 should be fine. Lower the better but bigger file size.
-vendor ap10 Makes the resulting video file to appear as to be made by quicktime - i think it is more compatible
-pix_fmt yuv422p10le set it to 422. You can use yuv444p10le to make 444. Not sure if it really makes a difference - i rembember i got same file size for 422 and 444 - maybe ffmpeg does something wrong or i do.
-threads 4 just to use all of my 4 threads
the last -r 24 sets output to 24 fps - not entirely sure it's necessary.
as for raw to dng - i found dcraw to work fine and fast - ufraw is based on dcraw.
my settings there:
dcraw -T -H 0 -6 -W -q 3 -S 13000 -a ******.dng
again some info:
-T makes tiff
-H 0 is highlight treating - -H 0 is save to use
-6 makes 16bit output
-W don 't apply auto-brightening of image
-q 3 quality scale
-S 13000 Saturation i found works best for 5DIII - this is not necessary to set
-a is auto WhiteBalance - works ok in most cases - but not in all
I do somehow think the user should have the choice if he wants the raw2dng makes jpg (or tif) and/or video too. What i mean the raw2dng app should be able to do raw to dng conversion only - in case somebody has a different workflow. Not that i think it should not be able to do other things too.
On this whole Auto-Conversion, the thing that bugs me most at the moment is the White Balance setting... Since the dng don't have WB from Camera embedded/included (why actually not? it should! ;-) we need to do it automatically - which, as said, is not optimal in some cases - or do it manually. It just have not found a way yet to make this nicely in batch converting...
Thanks all for your work. bashi
As for having the ffmpeg and ufraw or dcraw as external installation would make sense at the moment, until we found out how to bundle the necessary dylib and whatever is needed.
I've already updated the code for using already installed tools, will add dcraw.
I've an idea for add a way to open an options menu. Maybe here we can let user chose default workflow:
So far they could be:
1. Only raw2dng (simple/default)
2. dng, tiff prores (prores)
3. dng, tiff jpg prores mjpg (all)
4. toggle use dcraw or ufraw
5. Set work folder (to import and convert from card)
Quote from: scrax on June 06, 2013, 02:30:45 PM
I've already updated the code for using already installed tools, will add dcraw.
I've an idea for add a way to open an options menu. Maybe here we can let user chose default workflow:
So far they could be:
1. Only raw2dng (simple/default)
2. dng, tiff prores (prores)
3. dng, tiff jpg prores mjpg (all)
4. toggle use dcraw or ufraw
5. Set work folder (to import and convert from card)
This is so cool :)
As stated, the white balance with the magenta really needs the files to be processed through raw DNG at the moment so yes, number 1 option should be only raw to dng/cdng. That,s the fullproof workhorse :). After that adding the tiff, jpg options and maybe sum it up with the ProResHQ422 which is a moviefile format. Heck, or maybe just divide in two steps. 1 being original raw2dng and the 2 all the rest?
Important feature would definitely be the batch conversion tool. To have them converted place in folders works fine. Maybe to have the ProRes files placed in the same folder would be to hard to achieve? I don,t think placing tiffs och jpegs in one filder would work due to the huge amounts of files but prores would be moviefile-segments.
The workfolder thingy. I think most users simply drag the files to a folder to the computer and go from there. I know I do anyway :)
I,m sure it will work fine with some beta-testing :)
Gooood work Scrax!
Hi. Thanks so much for your continued work on this.
This version breaks the 5D2 metadata -- .dng files open up as Camera model "Canikon" in Photoshop on Mac, and picture styles are no longer available.
For reference, here are the metadata tags from a v0.10 that correctly identify the 5D2:
Make : Canon
Model : Canon EOS 5D Mark II
UniqueCameraModel : Canon EOS 5D Mark II
If you can include these again in the next compile, that would be fabulous.
Thank you!
Quote from: Hazer on June 06, 2013, 06:22:53 PM
Hi. Thanks so much for your continued work on this.
This version breaks the 5D2 metadata -- .dng files open up as Camera model "Canikon" in Photoshop on Mac, and picture styles are no longer available.
For reference, here are the metadata tags from a v0.10 that correctly identify the 5D2:
Make : Canon
Model : Canon EOS 5D Mark II
UniqueCameraModel : Canon EOS 5D Mark II
If you can include these again in the next compile, that would be fabulous.
Thank you!
Can you check if with 0.10 they are correct using the same .RAW
RAW2DNG 0.11 create a foilder called jpg empty. This is for what? prepare a folder to leave the files worked in ACR? Thanks.
Quote from: scrax on June 06, 2013, 12:37:56 PM
the jpg folder is empty because of ffmpeg error
Quote from: scrax on June 07, 2013, 05:47:58 AM
Can you check if with 0.10 they are correct using the same .RAW
I just checked on the same raw file and yes, the older version that I have adds the 5d2 metadata, whereas 0.11 does not. Thomas Worth on the RawMagic thread indicated that there is no camera metadata in the actual .RAW files. So it would seem that the older version that I'm using must have "Canon 5D Mark II" hard-coded. This may be a custom version that was uploaded at one point just for the 5D2.
If that is indeed the case, it would be great if Raw2DNG had some kind of drop-down to specify which camera you're using, so it could set the correct metadata.
Eventually, the best solution would be for the .RAW files themselves to be set with the correct metadata at capture time -- camera model, white balance, and so forth. Of course everybody's plate is pretty full right no, so we'll get there when we get there.
Anyway thanks again for your work on this!
Hi, maybe is a report.
I was tried again with 0.11 and i transform from RAW to DNG around 4 gb.
After that, I open, color processing and exporter from ACR to tiff folder.
So, I have 9 gigabites.
Compressor cannot open the file sequence, but with other RAW2DNG, I didn´t have that problem.
I divided the 9 GB file in two and Compressor works like ever before.
Any idea?
Hi, thanks for this GUI its been great so far...
However, with the latest 60D compile v.11 just produces empty folders - both DNG & JPEG (but Jpeg was always like this).
In the DNG folder it has produced a log file & it has the normal stuff on it, apart from it just says processing file 1 of 129 & then nothing else...
I have reverted back to v.10 & it works just fine...strange?!
Hi Scrax! I see Alex updated the rawtodng.exe today, some kind of purple fringing issue? Are those issues exactly the same on your app? Are you using the same source coed for both mac and windows?
Hi Scrax! Tried converting a rawclip filmed with 50fps. In version 0.11 it creates two empty folders , dng, and jpg, nothing gets converted. In version before, 0.10 conversion from 50fps works really good bu tnot in the latest?
//D
Quote from: Hazer on June 07, 2013, 08:52:59 PM
I just checked on the same raw file and yes, the older version that I have adds the 5d2 metadata, whereas 0.11 does not. Thomas Worth on the RawMagic thread indicated that there is no camera metadata in the actual .RAW files. So it would seem that the older version that I'm using must have "Canon 5D Mark II" hard-coded. This may be a custom version that was uploaded at one point just for the 5D2.
If that is indeed the case, it would be great if Raw2DNG had some kind of drop-down to specify which camera you're using, so it could set the correct metadata.
Eventually, the best solution would be for the .RAW files themselves to be set with the correct metadata at capture time -- camera model, white balance, and so forth. Of course everybody's plate is pretty full right no, so we'll get there when we get there.
Anyway thanks again for your work on this!
In source I saw once the string Canikon so i suppose it's from there, and I think it's not camera specific so the module can be "universal", maybe alex could explain us better if it's possible to link it to the camera model.
Quote from: Bioskop.Inc on June 08, 2013, 02:49:49 PM
Hi, thanks for this GUI its been great so far...
However, with the latest 60D compile v.11 just produces empty folders - both DNG & JPEG (but Jpeg was always like this).
In the DNG folder it has produced a log file & it has the normal stuff on it, apart from it just says processing file 1 of 129 & then nothing else...
I have reverted back to v.10 & it works just fine...strange?!
can you post somewhere the log and where you have raw2dng.app and the raw file (full addres),is strange that someone can use 0.11 and someothers have problem generating the .dng, but could be that in the clean-up I've made some typos. will try to find the problem tomorrow and post a 0.12 withthe lates rawa2dng sources
Quote from: Danne on June 08, 2013, 07:40:33 PM
Hi Scrax! I see Alex updated the rawtodng.exe today, some kind of purple fringing issue? Are those issues exactly the same on your app? Are you using the same source coed for both mac and windows?
Yes the source code for raw2dng is the same for win, osx and linux. Will update it in 0.12
We can embed the camera model in the header, but it needs updating all the converters. So... at the next major file format upgrade.
If you consider an update/change of the raw/dng format, please consider to include creation time and date, because this data then can be used for embedded time code and reel name in the later process.
Sure. The problem with current metadata is that we can't extend it without breaking current converters, so the first step is to have something where we can add things easily.
I can also get microsecond-level timestamps for each frame, if it helps.
Quote from: scrax on June 09, 2013, 12:01:37 AM
can you post somewhere the log and where you have raw2dng.app and the raw file (full addres),is strange that someone can use 0.11 and someothers have problem generating the .dng, but could be that in the clean-up I've made some typos. will try to find the problem tomorrow and post a 0.12 withthe lates rawa2dng sources
Here's the log file that was generated, but as you'll see it just seemed to get stuck:
https://dl.dropboxusercontent.com/u/90827273/_log.txt
& i put the RAW2DNG into the applications folder (as i did with the other versions). Normally i just open it & drag the Raw files into it - it does the rest. I just put the Raw files in a folder on my desktop. Its all worked fine until the recent update/compile this morning - v.10 works fine & v.11 was working fine until Sat newest 60D build.
Also, since the RAWMagic v.4 will include 60D (well all our cameras) it might not be a problem for much longer.
But always useful for Silent Pics etc...
Is the last version the link in the first topic? I was reading in Hudson and is talking about new fixes...
@scrax
there is away to convert from dng directly to video, without saving images. Using PIPE function. I'm new to this stuff, so i don't really know much about, but here a shell script that works:
for f in "$@"; do shell script
cd $f
/opt/local/bin/dcraw -c -H 0 -6 -W -q 3 -S 13000 -a -o 1 ******.dng | /opt/local/bin/ffmpeg -f image2pipe -vcodec ppm -r 24 -i pipe:0 -vcodec prores_kostya -profile:v 3 -qscale:v 5 -vendor ap10 -pix_fmt yuv422p10le -threads 4 -y -r 24 $f/ProResHigh.mov
echo "$f converted"
done
input $@ in this case folders with the dng
the important thing is in draw the "-c" = Write image data to standard output
and in ffmpeg the "-f image2pipe -vcodec ppm" and the " -i pipe:0"
This way is faster plus it does not need that much disk space.
Quote from: bashi on June 09, 2013, 01:55:25 PM
@scrax
there is away to convert from dng directly to video, without saving images. Using PIPE function. I'm new to this stuff, so i don't really know much about, but here a shell script that works:
for f in "$@"; do shell script
cd $f
/opt/local/bin/dcraw -c -H 0 -6 -W -q 3 -S 13000 -a -o 1 ******.dng | /opt/local/bin/ffmpeg -f image2pipe -vcodec ppm -r 24 -i pipe:0 -vcodec prores_kostya -profile:v 3 -qscale:v 5 -vendor ap10 -pix_fmt yuv422p10le -threads 4 -y -r 24 $f/ProResHigh.mov
echo "$f converted"
done
input $@ in this case folders with the dng
the important thing is in draw the "-c" = Write image data to standard output
and in ffmpeg the "-f image2pipe -vcodec ppm" and the " -i pipe:0"
This way is faster plus it does not need that much disk space.
Nice find, so we just need to have installed installed ffmpeg, dcraw seems to work from the package.
as addition: if we add a & behind it it gets even faster since all the conversion is done simultaneously with background jobs. (tried to explain as good as possible)
so in my example it looks like:
dcraw -c -H 0 -6 -W -q 3 -S 13000 -a -o 1 ******.dng | ffmpeg -f image2pipe -vcodec ppm -r 24 -i pipe:0 -vcodec prores_kostya -profile:v 2 -qscale:v 6 -vendor ap10 -pix_fmt yuv422p10le -y -r 24 ProResHigh.mov &
(i removed the -threads 4 from ffmpeg too - doesn't make sense anymore)
a concern for me is still how to set proper White balance and avoid the automatic there...
Latest version of raw2dng not working with the latest compile of ML
I drag the folder(or individual file) onto the app, it starts to process but only takes a fraction of a second for each raw. Creates both the dng and jpg folders, and they're both empty
Quote from: aaphotog on June 09, 2013, 07:29:36 PM
Latest version of raw2dng not working with the latest compile of ML
I drag the folder(or individual file) onto the app, it starts to process but only takes a fraction of a second for each raw. Creates both the dng and jpg folders, and they're both empty
I've compiled a new raw2dng from source I suppose recent changes broke it., time to goto 0.12
Quote from: bashi on June 09, 2013, 04:13:28 PM
as addition: if we add a & behind it it gets even faster since all the conversion is done simultaneously with background jobs. (tried to explain as good as possible)
so in my example it looks like:
dcraw -c -H 0 -6 -W -q 3 -S 13000 -a -o 1 ******.dng | ffmpeg -f image2pipe -vcodec ppm -r 24 -i pipe:0 -vcodec prores_kostya -profile:v 2 -qscale:v 6 -vendor ap10 -pix_fmt yuv422p10le -y -r 24 ProResHigh.mov &
(i removed the -threads 4 from ffmpeg too - doesn't make sense anymore)
a concern for me is still how to set proper White balance and avoid the automatic there...
so far the other code can generate the mov but it's empty, i need to make some more test.
I get this:
raw2dng converter GUI for OsX
Beta ver.0.11
M08-1643 File Supported
Generating jpg preview
dyld: Library not loaded: /usr/local/lib/libexiv2.10.dylib
Referenced from: /Applications/raw2dng.app/Contents/Resources/ufraw-batch
Reason: image not found
/Applications/raw2dng.app/Contents/Resources/script: line 31: 46298 Trace/BPT trap: 5 "$UFRAW" --out-type=jpg --out-path=../"$FILE_NAME"_jpg *.dng >> "$LOG"
Generating avi preview
dyld: Library not loaded: /usr/local/Cellar/ffmpeg/1.1.3/lib/libavdevice.54.dylib
Referenced from: /Applications/raw2dng.app/Contents/Resources/ffmpeg
Reason: image not found
/Applications/raw2dng.app/Contents/Resources/script: line 31: 46300 Trace/BPT trap: 5 "$FFMPEG" -i ../"$FILE_NAME"_jpg/%6d.jpg -vcodec mjpeg -qscale 1 ../"$FILE_NAME".avi >> "$LOG"
the files come out fine but it makes two folders, one of them blank
I also did a clean install of macports after, still the same output
i've hacked the raw2dng script convert file() to:
convert_file() {
cd "$FLDR$FILE_NAME"_dng
"$RAW2DNG" "$FLDR$FILE_NAME".RAW
/opt/local/bin/dcraw -c -H 0 -6 -W -q 3 -S 13000 -a -o 1 *.dng | /usr/local/bin/ffmbc -f image2pipe -vcodec ppm -r 24 -i pipe:0 -vcodec prores -profile hq -b 120M -pix_fmt yuv444p10 -y -r 24 "$FILE_NAME".mov & >> "$LOG"
}
i switched ffmpeg to ffmbc. It seems to be easier to configure. (the bitrate setting works in ffmbc - i haven't got this to work in ffmpeg. this could be a very easy way to set quality of video - set bitrate and set quality hq, std, lt or proxy)
http://code.google.com/p/ffmbc/
the quality settings - i'm still trying to find the sweet spot. for ffmpeg -profile:v 2 -qscale 6 seems to be too low. i would recommend -profile:v 2 without -qscale. this gives roughly 120MBit/s. -profile:v 3 is about 185MBit/s
the code above for ffmpeg would look like:
convert_file() {
cd "$FLDR$FILE_NAME"_dng
"$RAW2DNG" "$FLDR$FILE_NAME".RAW
/opt/local/bin/dcraw -c -H 0 -6 -W -q 3 -a -o 1 *.dng | /usr/local/bin/ffmpeg -f image2pipe -vcodec ppm -r 24 -i pipe:0 -vcodec prores_kostya -profile:v 2 -pix_fmt yuv444p10 -y -r 24 "$FILE_NAME".mov & >> "$LOG"
}
(i removed the dcraw -s 13000 here - this is saturation level for my 5diii - don't think this value is good for other cameras...)
now, if we could make raw2dng pipe as well we could convert .RAW to ProRes (or any other video) directly without .dng files ;-) Somehow i like the idea of archiving the .RAW instead of a bunch of .dng seq..
EDIT: The framerate fixed to 24 is not very nice. the raw2dng reads the framerate when it makes .dng - is there a way to get to this information and put a variable there?
Any idea when 0.12 will be available?
When using raw2dng v.11 on latest SnowLeopard - it always gives segmentation fault.
Do I need to install some other software for it to work?
Thx
Mike
Any updates?
When using raw2dng, after dragging my .raw files onto the app, Im getting 2 folders(jpg and dng) and they are BOTH EMPTY!
Im using the newest build of Magic Lantern
can the ones of you that have issues please do the following:
-right-click on raw2dng.app and select "Show Package Contents"
go to raw2dng.app/Contents/MacOS/
and double-click raw2dng there
this will start raw2dng together with a terminal console
now drag-drop your .raw file on it
look at the Terminal Console and copy/paste the stuff that is output there into here as a comment
this gives at least the chance of seeing where the problem is.
Hey guys, dont know if this was mentioned before, but:
Had no problem converting to dng, but I use the program Aperture, not Photoshop. When I try to open the files in Aperture, It says that the file format is unrecognized.
Solutions?
Quote from: bashi on June 12, 2013, 07:36:07 PM
can the ones of you that have issues please do the following:
-right-click on raw2dng.app and select "Show Package Contents"
go to raw2dng.app/Contents/MacOS/
and double-click raw2dng there
this will start raw2dng together with a terminal console
now drag-drop your .raw file on it
look at the Terminal Console and copy/paste the stuff that is output there into here as a comment
this gives at least the chance of seeing where the problem is.
I'm having the same issue with 0.11. I opened through terminal as you have instructed, but I only get feedback in the raw2dng GUI. Here's what it says:
raw2dng converter GUI for OsX
Beta ver.0.11
M11-2220 File Supported
Generating jpg preview
dyld: Library not loaded: /usr/local/lib/libexiv2.10.dylib
Referenced from: /Applications/raw2dng.app/Contents/Resources/ufraw-batch
Reason: image not found
/Applications/raw2dng.app/Contents/Resources/script: line 31: 2925 Trace/BPT trap: 5 "$UFRAW" --out-type=jpg --out-path=../"$FILE_NAME"_jpg *.dng >> "$LOG"
Generating avi preview
dyld: Library not loaded: /usr/local/Cellar/ffmpeg/1.1.3/lib/libavdevice.54.dylib
Referenced from: /Applications/raw2dng.app/Contents/Resources/ffmpeg
Reason: image not found
/Applications/raw2dng.app/Contents/Resources/script: line 31: 2927 Trace/BPT trap: 5 "$FFMPEG" -i ../"$FILE_NAME"_jpg/%6d.jpg -vcodec mjpeg -qscale 1 ../"$FILE_NAME".avi >> "$LOG"
I would like to add a feature request:
Can the DNG sequence include the .RAW clip name in the naming structure? Right now, I just get a folder (properly named) and a DNG sequence going from 0000.dng through the final frame. As a result, I cannot easily batch process the sequences in After Effects without first manually making comps with unique naming. If I import 100 different image sequences in AE, they all look the same and it's tedious to rename to keep everything organized.
it would be best if it renamed like so:
M11-2220_0000.dng
M11-2220_0001.dng
...and so on
Based on some earlier posts, it looked as though this might have been working at one point in time. ?
Thanks for the great work, guys!
I had similar output as other user opening as you suggested:
log.txt:
Resolution : 1920 x 1080
Frames : 18
Frame size : 3629056 bytes
Frame skip : 1
FPS : 0.000
Processing frame 1 of 18...
App Details:
raw2dng converter GUI for OsX
Beta ver.0.11
M12-0229 File Supported
/Users/user/Downloads/raw2dng.app/Contents/Resources/script: line 31: 281 Segmentation fault "$RAW2DNG" "$FLDR$FILE_NAME".RAW >> "$LOG"
Generating jpg preview
dyld: Library not loaded: /usr/local/lib/libexiv2.10.dylib
Referenced from: /Users/user/Downloads/raw2dng.app/Contents/Resources/ufraw-batch
Reason: image not found
/Users/user/Downloads/raw2dng.app/Contents/Resources/script: line 31: 284 Trace/BPT trap "$UFRAW" --out-type=jpg --out-path=../"$FILE_NAME"_jpg *.dng >> "$LOG"
Generating avi preview
dyld: Library not loaded: /usr/local/Cellar/ffmpeg/1.1.3/lib/libavdevice.54.dylib
Referenced from: /Users/user/Downloads/raw2dng.app/Contents/Resources/ffmpeg
Reason: image not found
/Users/user/Downloads/raw2dng.app/Contents/Resources/script: line 31: 285 Trace/BPT trap "$FFMPEG" -i ../"$FILE_NAME"_jpg/%6d.jpg -vcodec mjpeg -qscale 1 ../"$FILE_NAME".avi >> "$LOG"
MY GUESS: ffmpeg dynamic library is not installed as expected or is incompatible with this version of OS (10.6.8).
I have ffmpeg working just fine on this computer - if what you are doing has cmd line equivalent - please share and I can just use ffmpeg
Otherwise please provide version with static linked library not dynamic linked.
My hard drives are getting full. Im recording, but unable to actually convert anything
Quote from: consmi on June 12, 2013, 09:16:07 PM
Hey guys, dont know if this was mentioned before, but:
Had no problem converting to dng, but I use the program Aperture, not Photoshop. When I try to open the files in Aperture, It says that the file format is unrecognized.
Solutions?
Hi, download (free) Adobe DNG Converter from the Adobe website (Windows and Mac versions) and use it to process your files into camera raw DNG files which Aperture can import and process.
Photoshop Elements (which is often thrown in free with scanners and the like) can also convert the raw2dng files into TIFFS, and also eliminates hot pixels if you have that problem (as I have on my old 50D, though only in video).
I think v 0.11 may be incompatible with raw files created by the latest ML Raw version. RawMagic works.
Hey, I have noticed that our the raw2dng.app inserting vertical lines into digital negatives. If i export in Apple Pro Res 4444, the vertical lines are still present, but if I convert the dng .RAW video sequence into an h.264 mp4 video file, it compresses them away.
I am not sure if this is our Mark III sensor, or an issue with compression. See Images Below.
(http://i.imgur.com/ZaxuZrC.png)
This 100% clip from a .RAW sequence converted in raw2dng, and then exported as apple pro res 4444 in After Effects CS6.
[/b]
(http://i.imgur.com/1BAx0vh.png)
100% clip from .RAW sqeuence convereted in raw2dng, then exported as h.264 mpeg (.mp4) in After Effects CS6.
[/b]
Any information would be great, thanks. 8)
New version uploaded, updated the app with last bin (so it should work with also latest ML generated raw files). ffmpeg and dcraw should work now. link (https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.12.zip)
For vertical lines latest ML code and 0.12 should fix it
Quote from: S3Dcentre on June 16, 2013, 02:15:51 AM
Hey, I have noticed that our the raw2dng.app inserting vertical lines into digital negatives. If i export in Apple Pro Res 4444, the vertical lines are still present, but if I convert the dng .RAW video sequence into an h.264 mp4 video file, it compresses them away.
I am not sure if this is our Mark III sensor, or an issue with compression.
It's a sensor issue and we're not sure what causes it. The strange thing is it doesn't affect every 5D, I've never had a problem with it. http://www.magiclantern.fm/forum/index.php?topic=5614.0
Quote from: squig on June 16, 2013, 03:05:46 AM
It's a sensor issue and we're not sure what causes it. The strange thing is it doesn't affect every 5D, I've never had a problem with it. http://www.magiclantern.fm/forum/index.php?topic=5614.0
Same things here. Haven't seen that issue on my camera on any builds. I have even OLPF removed.
I suspect it only affects a particular batch of cameras.
Quote from: scrax on June 16, 2013, 02:24:57 AM
New version uploaded, updated the app with last bin (so it should work with also latest ML generated raw files). ffmpeg and dcraw should work now. link (https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.12.zip)
For vertical lines latest ML code and 0.12 should fix it
TO DO:
Extract dead pixel list from dng and use it in dcraw to remove dead pixels.
Dcraw wont read the dead pixel information from the source file but needs an external list file.
Quote from: scrax on June 16, 2013, 02:24:57 AM
New version uploaded, updated the app with last bin (so it should work with also latest ML generated raw files). ffmpeg and dcraw should work now. link (https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.12.zip)
For vertical lines latest ML code and 0.12 should fix it
Thanks Scrax! It,s working fine :). Good work. The ProRes looks fine. Also the white balance issue seems fine. Is the white balance information recorded from what you see in the camera to the ProRes files?
I got a few questions. When I remove the dcraw and ffmpeg from your app, It simply converts the dng;s again. Is that the way I should do if I want to skip the ProRes part? Sometimes only the dng,s would be enough.
Also, is there an alternative If I simply only wants the ProRes files and skip the dng,s? Also, what bitrate and quality is the ProRes in? 422HQ, 444?
A lot of questions, I know. Still, I believe this is one of the best converters out there.
Thanks a lot Scrax!
//D
off topic
Could someone explain or link me to how to convert spanned files on the rawtodng converter? Seem that I,ve missed that part of my raw-education lessons ;).
Quote from: Danne on June 16, 2013, 12:17:35 PM
Thanks Scrax! It,s working fine :). Good work. The ProRes looks fine. Also the white balance issue seems fine. Is the white balance information recorded from what you see in the camera to the ProRes files?
I got a few questions. When I remove the dcraw and ffmpeg from your app, It simply converts the dng;s again. Is that the way I should do if I want to skip the ProRes part? Sometimes only the dng,s would be enough.
Also, is there an alternative If I simply only wants the ProRes files and skip the dng,s? Also, what bitrate and quality is the ProRes in? 422HQ, 444?
A lot of questions, I know. Still, I believe this is one of the best converters out there.
Thanks a lot Scrax!
//D
off topic
Could someone explain or link me to how to convert spanned files on the rawtodng converter? Seem that I,ve missed that part of my raw-education lessons ;).
White Balance currently uses dcraw automatic - quite ok in lot of cases - not in all...
unfortunately ml does not seem to be record WB in Raw...
the ProRes is about 422HQ with qscale 5 - about 76MBit/s - but it is somewhat dependend on input.
@scrax: to get FPS out of raw2dng:
convert_file() {
cd "$FLDR$FILE_NAME"_dng
"$RAW2DNG" "$FLDR$FILE_NAME".RAW > r2dlog.txt
FPS=`awk '/FPS/ { print $3; }' "$FLDR$FILE_NAME"_dng/r2dlog.txt`
rm r2dlog.txt
printf "Generating ProResHQ 422\n"and then in ffmpeg replace the two -r 24 by -r $FPS
there might be a way without saving r2dlog...
i have been playing around with gui creation based on your script - there is pasha to make ui from script. I have it working here with Image preview and manual WB and some more options.
Included ffmbc and dcrawU (i guess U means universal?), tried to build with static libs (no idea if it worked ;-)
https://www.dropbox.com/s/gxm2vvdtbjxl9tl/r2v.zip (https://www.dropbox.com/s/gxm2vvdtbjxl9tl/r2v.zip)
i have seen you started with white balance option and cocoadialog... (I will get the rgbg multipliers for the 5d III, can send them to you)
I've used what Bashi suggested so basically:
WB is on auto for now.
It should be yuv422p10le if it means something to you.
I suppose it could be 444 too maybe
So far we can't make the ProRes without the dng part.
Do you mean the .RAW .R00 .R01 and so on? I'm thinking that they could be merged and converted from raw2dng.app but how are they called?
For now you can from terminal use that:
cat drop_first.RAW drop_other.R00 again_with.R01 and_so_on.R02 >> merged.RAW
cat is the command used to merge the files, then you have to drop them in the correct order into the terminal window so they will have the correct address
>> those thing will save the cat output to a new file called
merged.RAW the name of the file merged
Quote from: bashi on June 16, 2013, 12:57:10 PM
White Balance currently uses dcraw automatic - quite ok in lot of cases - not in all...
unfortunately ml does not seem to be record WB in Raw...
the ProRes is about 422HQ with qscale 5 - about 76MBit/s - but it is somewhat dependend on input.
@scrax: to get FPS out of raw2dng:
convert_file() {
cd "$FLDR$FILE_NAME"_dng
"$RAW2DNG" "$FLDR$FILE_NAME".RAW > r2dlog.txt
FPS=`awk '/FPS/ { print $3; }' "$FLDR$FILE_NAME"_dng/r2dlog.txt`
rm r2dlog.txt
printf "Generating ProResHQ 422\n"
and then in ffmpeg replace the two -r 24 by -r $FPS
there might be a way without saving r2dlog...
i have been playing around with gui creation based on your script - there is pasha to make ui from script. I have it working here with Image preview and manual WB and some more options.
Included ffmbc and dcrawU (i guess U means universal?), tried to build with static libs (no idea if it worked ;-)
https://www.dropbox.com/s/gxm2vvdtbjxl9tl/r2v.zip (https://www.dropbox.com/s/gxm2vvdtbjxl9tl/r2v.zip)
i have seen you started with white balance option and cocoadialog... (I will get the rgbg multipliers for the 5d III, can send them to you)
downloading now, Good to hear that you are working on this too :)
do you think it will be better to have a repo to share our code?
Thanks all!
yes, they,re calle r00 etc, will try the terminal later. Real nice work. Thanks for clarifying on white balance.
Will check in later, gotta go now for now.
Thanks :)!
//D
Quote from: aaphotog on June 13, 2013, 05:54:36 AM
My hard drives are getting full. Im recording, but unable to actually convert anything
0.12 works?
I did a quick card full test, no probs. Prores is cool but can you make it an option?
Quote from: scrax on June 16, 2013, 01:08:37 PM
downloading now, Good to hear that you are working on this too :)
do you think it will be better to have a repo to share our code?
this might make sense at some point. but first have a look at it and then we can see. my coding isn't really great ;-)
note: the wb multipliers in my app are wrong.
Quote from: mkorho on June 16, 2013, 04:45:09 AM
TO DO:
Extract dead pixel list from dng and use it in dcraw to remove dead pixels.
Dcraw wont read the dead pixel information from the source file but needs an external list file.
this is a feature request?
here the canon 5d III dcraw white balance rgbg multipliers:
Daylight
1.950195 1.000000 1.605469 1.000000
Shade
2.226562 1.000000 1.369141 1.000000
Cloudy
2.089844 1.000000 1.477539 1.000000
Tungsten
1.412109 1.000000 2.392578 1.000000
White Fluorescent
1.720703 1.000000 2.291016 1.000000
Quote from: bashi on June 16, 2013, 01:46:49 PM
this is a feature request?
Yes it is.
All the 3x and 5x zoom mode raw recording have more than 5 dead pixels, at least on my camera.
It is funny that nobody else is seeing them. (or dont care)
To me red, green and blue pixels in video is a NO NO. :)
And manual removal is too painful process.
Adobe camera raw and Ufraw can read the dead (hot) pixel list from the source file but dcraw cant.
@scrax
here your script edited for fps and white balance dialog with cocoadialog working:
set_wb(){
"$CD" standard-dropdown \
--text "Pick a wb" --title "wb Options" --items "Auto" "Daylight" "Shade" "Cloudy" "Tungsten" "White Fluorescent"\
--string-output | tail -1 > wb.txt
wb=`awk ' { print $1; }' "$FLDR$FILE_NAME"_dng/wb.txt`
rm wb.txt
#Set rgb multiplier
if [[ $wb = Auto ]]
then
Wtemp="-a"
elif [[ $wb = *Daylight* ]]
then
Wtemp="-r 1.950195 1.000000 1.605469 1.000000"
elif [[ $wb = *Shade* ]]
then
Wtemp="-r 2.226562 1.000000 1.369141 1.000000"
elif [[ $wb = *Cloudy* ]]
then
Wtemp="-r 2.089844 1.000000 1.477539 1.000000"
elif [[ $wb = *Tungsten* ]]
then
Wtemp="-r 1.412109 1.000000 2.392578 1.000000"
elif [[ $wb = *White* ]]
then
Wtemp="-r 1.720703 1.000000 2.291016 1.000000"
fi
}
convert_file() {
cd "$FLDR$FILE_NAME"_dng
"$RAW2DNG" "$FLDR$FILE_NAME".RAW > r2dlog.txt
FPS=`awk '/FPS/ { print $3; }' "$FLDR$FILE_NAME"_dng/r2dlog.txt`
rm r2dlog.txt
set_wb
printf "Generating ProResHQ 422\n"
#find "$FLDR$FILE_NAME"_dng -type f -name "*.dng" -print | \
#while read dng
#do
"$DCRAW" -c -H 0 -6 $Wtemp -W -q 3 *.dng | "$FFMPEG" -f image2pipe -vcodec ppm -r $FPS -i pipe:0 -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt yuv422p10le -y -r $FPS "$FLDR$FILE_NAME".mov
#done
printf "Done\n"
}
Quote from: mkorho on June 16, 2013, 02:18:57 PM
Yes it is.
All the 3x and 5x zoom mode raw recording have more than 5 dead pixels, at least on my camera.
It is funny that nobody else is seeing them. (or dont care)
To me red, green and blue pixels in video is a NO NO. :)
And manual removal is too painful process.
Adobe camera raw and Ufraw can read the dead (hot) pixel list from the source file but dcraw cant.
will look into it... (we just switched ufraw to dcraw - might switch back then ;-)
it's not too high of a priority for me though.
Quote from: bashi on June 16, 2013, 02:57:55 PM
@scrax
here your script edited for fps and white balance dialog with cocoadialog working:
I've added fps as you suggested early, now I'm looking into a way for having some options to set, but they should be optional (for advanced use only).
Quote from: scrax on June 16, 2013, 03:14:41 PM
I've added fps as you suggested early, now I'm looking into a way for having some options to set, but they should be optional (for advanced use only).
something like an advanced checkbox on first window perhaps... not really sure how to change platypus default window to do that. so far i'm not getting "warm" with platypus and cocoadialog. as far as i see you can only trigger dialog popup (i might be wrong) which is not great to use.
i think the app (the ideal app) should be something like:
-be as easy as possible
-give as much control over the image (raw->img process) as possible (if desired, advanced option). Since those settings gets "backed" into resulting img seq or video.
-be suitable for batch process
btw, did my app work on your computer?
i don't like on mine:
-no drag drop on app (in file selection does work)
-not nice ui (but hey, a ui ;-)
-no feedback about what it is doing ( while raw2dng and dcraw-video)
We should consider use pashua instead of cocoadialog and keep Platypus as wrapper. Pashua will be good for the preference page maybe.
Your app is working in making the dng, then it show the options for video rendering but video is not generated.
The big issue I see so far is that in batch conversion setting wb for each file will be not ideal.
My idea is that settings should be something that is related to app and not to raw file. For example if we enable ProRes conversion in settings all the file imported will be converted, if we set a working folder all file go in that folder and so on.
Things like wb, fps etc. should be automatic and right. Maybe ML could make a video.log of raw captures too like for normal video, and we can use that for finding out needed settings...
EDIT: I can open a settings dialog by dropping raw2dng.app into his window ;)
set_pref(){
printf "Preference panel to be added!\n"
}
##### Main
if [[ ! "$1" ]]; then
usage
else
if [[ "$1" == *raw2dng.app ]]; then
set_pref
fi
#set_workdir
...
Quote from: scrax on June 16, 2013, 03:51:06 PM
We should consider use pashua instead of cocoadialog and keep Platypus as wrapper. Pashua will be good for the preference page maybe.
Your app is working in making the dng, then it show the options for video rendering but video is not generated.
The big issue I see so far is that in batch conversion setting wb for each file will be not ideal.
My idea is that settings should be something that is related to app and not to raw file. For example if we enable ProRes conversion in settings all the file imported will be converted, if we set a working folder all file go in that folder and so on.
Things like wb, fps etc. should be automatic and right. Maybe ML could make a video.log of raw captures too like for normal video, and we can use that for finding out needed settings...
EDIT: I can open a settings dialog by dropping raw2dng.app into his window ;)
set_pref(){
printf "Preference panel to be added!\n"
}
##### Main
if [[ ! "$1" ]]; then
usage
else
if [[ "$1" == *raw2dng.app ]]; then
set_pref
fi
#set_workdir
...
use platypus and pasha seems ideal. will try this.
what i think of:
on first dialog have checkbox advanced and combo box White Balance with default Auto. if advanced unchecked it will work as usual and convert all raw with this White Balance setting.
if advanced checked it will open for each raw a preview thing to make settings and then render.
additionally on first dialog checkbox image and video, to make img seq and/or video.
this would allow to batch process but as well fine tuning of each.
EDIT: I can see that it can make sense to edit all videos with the same settings. At the same time i see cases where it would be great to edit each. So an option to edit settings for all or for each could make sense.
So far I've a 0.13 candidate that will use cocoadialog to set working folder and if Prores should be generated or not.
Since we,re on the ProRes topic. Will the files contain similar dynamic range possibilities as with the dng,s? I compared the raw imported with the ginger plugin(trial) and the generated ProRes file. It seems contrasts and highlight information differs. Maybe one could get a flatter profile ProRes file somehow? The first three are the ginger plugin one and the other three are the ProRes. Might it be a white balance thing?
(http://s8.postimg.org/u18tifodd/Ginger1.jpg) (http://postimg.org/image/u18tifodd/)
(http://s8.postimg.org/ybnhe0tgh/Ginger_2.jpg) (http://postimg.org/image/ybnhe0tgh/)
(http://s8.postimg.org/61ggo50rl/Ginger_3.jpg) (http://postimg.org/image/61ggo50rl/)
(http://s8.postimg.org/skxb0algh/Pro_Res_1.jpg) (http://postimg.org/image/skxb0algh/)
(http://s8.postimg.org/rz8c46qe9/Pro_Res_2.jpg) (http://postimg.org/image/rz8c46qe9/)
(http://s8.postimg.org/s1wt4rjfl/Pro_Res_3.jpg) (http://postimg.org/image/s1wt4rjfl/)
Quote from: Danne on June 16, 2013, 06:55:13 PM
Since we,re on the ProRes topic. Will the files contain similar dynamic range possibilities as with the dng,s? I compared the raw imported with the ginger plugin(trial) and the generated ProRes file. It seems contrasts and highlight information differs. Maybe one could get a flatter profile ProRes file somehow? The first three are the ginger plugin one and the other three are the ProRes. Might it be a white balance thing?
Magic Lantern RAW is 14bit, ProRes is 10bit. There is no way (i know of) to increase ProRes bit depth.
There might be the possibility to output raw video (not sure if it would be 14bit), but FileSize is similar to CinemaDNG, so i don't see it make sense, better work of CinemaDNG sequence then.
the raw converter in use (dcraw) can do gamma correction, so we should be able to get a flatter profile. It can also do Highlight blending and reconstruction. But those things are not in raw2dng.app for now.
White balance has influence on Highlights too.
Thanks a lot for answering
Hello and thank you for the new version of raw2dng. Just wanted to report that when the app is generating the prores file it doesn't seem to be able to make a file greater than 645 frames. Any else experienced this ?
Thank You Again !!
Quote from: Jason Montalvo on June 17, 2013, 01:20:50 PM
Hello and thank you for the new version of raw2dng. Just wanted to report that when the app is generating the prores file it doesn't seem to be able to make a file greater than 645 frames. Any else experienced this ?
Thank You Again !!
thanks for report. not good ;-) will look into it.
If you click in raw2dng.app on the Details button left, after it failed, can you copy the last part of the text output bellow to here (or pasteall.org)?
@Bashi
I just tried it again and now it seems to have converted the entire clip to a prores file. I'll try more and let you know if I discover anything.
Sweet this version is working well for me and the ProRes output is a nice feature too, drag n drop into afters, change color bit from 8bit to 16 and using adjustment layers all seems sweet!
Iv noticed that it dosnt convert the very last frame so i got 187 out of 188, this isnt a major problem at all but i thought id let you know.
Thanks!
Quote from: Jason Montalvo on June 17, 2013, 04:23:39 PM
@Bashi
I just tried it again and now it seems to have converted the entire clip to a prores file. I'll try more and let you know if I discover anything.
it's bashi ;-) Good to hear, and please let us know of any issues.
@Doyle4: Thanks for the info.
just converted some files with 0.12 to me it worked pretty good... i still prefer to proRes4444 with AE. It would be amazing if we could batch convert with raw2dng and have the option to create just DNG's or DNG's and proRes... anyway its killing it. thanks guys!
Quote from: noix222 on June 17, 2013, 10:59:52 PM
just converted some files with 0.12 to me its worked pretty good... i still prefer to proRes4444 with AE. It would be amazing if we could batch convert with raw2dng and have the option to create just DNG's or DNG's and proRes... anyway its killing it. thanks guys!
"-pix_fmt yuv444p10″ specifies that you want to use the ProRes 4444 codec specifically
we can do that. ;-)
so this would be prores 4444 12bit.
(until now i had some confusion with those pixel formats)
the option to make dng and/or video will come soon.
Quote from: bashi on June 18, 2013, 12:35:40 AM
we can do that. ;-)
so this would be prores 4444 12bit.
(until now i had some confusion with those pixel formats)
the option to make dng and/or video will come soon.
that's awesome thanks!!! its possible to batch convert multiple .RAW files with raw2dng? I went through a lot of time going one by one :P
I using RAW module for 60D made by marekk.
http://www.magiclantern.fm/forum/index.php?topic=5653.0
UPDATE #9:
Hot/dead pixels removed automatically by ACR (you need fresh raw2dng)
ML with raw_rec compiled hourly by rocket's scripts:
https://www.dropbox.com/sh/1kitzbmanifb6sf/qgkHzW3gn2
The ProRes files were made by raw2dng.app 0.12 have some Hot/dead pixels.
Thanks.
Hi Guys, what kind of Pro Res is the file created by RAW2DNG: 422, 4444, LT? Because in Quicktime information only said the creator´s name. Thanks!
Quote from: noix222 on June 18, 2013, 04:58:43 AM
that's awesome thanks!!! its possible to batch convert multiple .RAW files with raw2dng? I went through a lot of time going one by one :P
just drag 'n drop all files on it, or folder containing them.
Quote from: budafilms on June 18, 2013, 07:55:14 AM
Hi Guys, what kind of Pro Res is the file created by RAW2DNG: 422, 4444, LT? Because in Quicktime information only said the creator´s name. Thanks!
currently it's 422 HQ, but 4444 is possible and will be enabled.
Just an Update to say all working great still :)
As for batch converting dng's to Proress, import the first DNG into after effects, select the first image, choose image sequence and force alphabetical order. Drag the batch file to ur time and export as appleproress4444 :) dont forget to change ur comp settings to ur frame rate if you havent already, (comp settings> change frame rate>ok)
Cheers,
Doyle
Hey,
great work so far!
Is there a way to get files larger >4GB working?
raw2dng always comes up with:
[image2pipe @ 0x102019600] Could not find codec parameters for stream 0 (Video: ppm): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[image2pipe @ 0x102019600] Estimating duration from bitrate, this may be inaccurate
pipe:0: could not find codec parameters
Done
What do you think?
No problem with 4Gb+ files here. Is your card exFat formatted?
Is there a way to stop the program from making prores files?
Great program!
Quote from: Felix on June 19, 2013, 11:04:06 AM
Is there a way to stop the program from making prores files?
Great program!
0.13 (https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.13.zip)
will have has an option to toggle it.
To open the options dialogs you have to double click raw2dng.app and then drop the app inside it's windows like if it was a raw file, the app will recognize it and open the options instead of trying to convert it ;)
Is it possible to have this JUST convert to ProRes? Any chance we could select options for the ProRes output? It'd be great to get a ProRes 422 HQ option.
Quote from: AnotherDave on June 19, 2013, 03:40:23 PM
Is it possible to have this JUST convert to ProRes? Any chance we could select options for the ProRes output? It'd be great to get a ProRes 422 HQ option.
Just convert to prores - i've tried this several ways with no luck. looks like the raw2dng is not able to be piped in a way we can use the output without it being written to disk... will do some more testing, cause this feature would be great!
EDIT: more options will come, most likely 422/4444, quality (Proxy, LQ, STD, HQ).
@all and scrax
It looks like the White Balance Automatic does apply on every image separately... This means it can change during the shot - not good.
@scrax: we might need to find a way do get the rgb multiplier from the first image (or any), by -v verbose and read/save the shell output value and set it as variable it then uses for all further conversion.
@all again
further the White Balance Presets (multipliers) are taken from 5D III. Not sure how much difference there is to other camera models.
I'm as well not entirely sure those WB Presets are really correct - so please test them and report back here.
Quote from: scrax on June 19, 2013, 03:21:27 PM
To open the options dialogs you have to double click raw2dng.app and then drop the app inside it's windows like if it was a raw file, the app will recognize it and open the options instead of trying to convert it ;)
You're the man!
Quote from: scrax on June 19, 2013, 02:24:47 PM
0.13 (https://bitbucket.org/600dplus/magic-lantern-things/downloads/raw2dng.app.0.13.zip) will have has an option to toggle it.
No beans. Don't see the option to toggle.
Quote from: scrax on June 19, 2013, 03:21:27 PM
To open the options dialogs you have to double click raw2dng.app and then drop the app inside it's windows like if it was a raw file, the app will recognize it and open the options instead of trying to convert it ;)
Haha, I like it :)
Hm, nice idea, but the ProRes files I get are quite unusable. Correctly exposed RAW files turn into 3 stops underexposed .mov's that don't seem to have the color information needed to get them back up, results in extreme overall noise.
Also I'm not sure the automatic WB is needed since it should have been set correctly in camera, right? Only Green/Magenta Shift should be set to 0.
Thanks
Quote from: cinema5D on June 19, 2013, 07:22:46 PM
Hm, nice idea, but the ProRes files I get are quite unusable. Correctly exposed RAW files turn into 3 stops underexposed .mov's that don't seem to have the color information needed to get them back up, results in extreme overall noise.
Also I'm not sure the automatic WB is needed since it should have been set correctly in camera, right? Only Green/Magenta Shift should be set to 0.
Thanks
In most conditions, try overexposing your RAW shooting by 1 EV (compensate in the image fine-tuning for display) you'll get a nice surprise with a higher signal to noise ratio. *Just make sure you're not blowing out your highlights.
This feature would be great for use as a proxy to start editing, but ProRes 4444 is a bit much for a proxy...
Quote from: cinema5D on June 19, 2013, 07:22:46 PM
Hm, nice idea, but the ProRes files I get are quite unusable. Correctly exposed RAW files turn into 3 stops underexposed .mov's that don't seem to have the color information needed to get them back up, results in extreme overall noise.
Also I'm not sure the automatic WB is needed since it should have been set correctly in camera, right? Only Green/Magenta Shift should be set to 0.
Thanks
i think the camera wb doesn't get saved - at least the dng don't have it saved in them...
very happy with the prores files, this allows me to see much faster which shots are ok. Thank You!!
VEry nice! I think it,s the gamma curve who gives a pretty hard contrast. It,s pretty simple to get it back in post as it,s ton of information in the ProRes444. An added alternative creating proxies could be nice for fast viewing and editing.
Thanks for all the develompment. Really good stuff
Quote from: Danne on June 19, 2013, 11:31:43 PM
VEry nice! I think it,s the gamma curve who gives a pretty hard contrast. It,s pretty simple to get it back in post as it,s ton of information in the ProRes444. An added alternative creating proxies could be nice for fast viewing and editing.
Thanks for all the develompment. Really good stuff
As I mentioned the information can't be gotten back. 3 stops underexposed is a pretty intense loss of quality. This seems like an error of the software.
I havn,t experienced any 3 stop underexposure though. Still, havn,t tried it extensevily. I,ll do some testing later today.
App seems great, tho could the combining of the first .RAW with the subsequent .R00, .R01, .R02 be done automatically for all us 5Dmk2 users ? if so that would be super great ! J
Quote from: scrax on June 19, 2013, 03:21:27 PM
To open the options dialogs you have to double click raw2dng.app and then drop the app inside it's windows like if it was a raw file, the app will recognize it and open the options instead of trying to convert it ;)
Quote from: Nickbibs on June 19, 2013, 05:31:25 PM
No beans. Don't see the option to toggle.
If it doesn't work check so your directory names doesn't contain any spaces.
You should see the full path when clicking details and Error 125 if that is the case
Quote from: bashi on June 18, 2013, 11:16:01 AM
just drag 'n drop all files on it, or folder containing them.
currently it's 422 HQ, but 4444 is possible and will be enabled.
0.13 Works great, much better resolution and WB!!! DNG open in ACR is terrible the WB, maybe something more real for not loose tu much time and information trying to get correct WB wil be perfect.
Hi, Used 0.13. Computer says it can't open the prores sequence. It's not a video.
The end of the verbose inside the app:
"frame= 409 fps=1.7 q=0.0 size= 385499kB time=00:00:17.05 bitrate=185125.8kbits/s
/Applications/raw2dng0.13.app/Contents/Resources/script: line 40: 2216 Done "$DCRAW" -c -H 0 -6 -W -q 3 "$Wtemp" *.dng
2217 Segmentation fault: 11 | "$FFMPEG" -f image2pipe -vcodec ppm -r "$FPS" -i pipe:0 -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt yuv444p10 -y -r "$FPS" "$FLDR$FILE_NAME".mov
Done"
If that can help you.
Not sure if I was using an older raw2dng osx, but I grabbed it from the MKii thread. I was getting a green dot in the mov previews that raw2dng made. It was pretty annoying. I figured out that the actual dng files didn't have the green dot so if I followed the normal workflow (raw2dng->PS->QT7) then everything is fine. Is this a known issue or do I have the wrong version? The one I have says raw2dng converter GUI for 5D2 // Beta 1.0 Thanks
Quote from: jc on June 20, 2013, 09:17:14 PM
App seems great, tho could the combining of the first .RAW with the subsequent .R00, .R01, .R02 be done automatically for all us 5Dmk2 users ? if so that would be super great ! J
so yeah any thoughts on auto joining the 5d2 4GB files?
Thanks. James
Quote from: Indianac on June 21, 2013, 04:54:49 PM
Not sure if I was using an older raw2dng osx, but I grabbed it from the MKii thread. I was getting a green dot in the mov previews that raw2dng made. It was pretty annoying. I figured out that the actual dng files didn't have the green dot so if I followed the normal workflow (raw2dng->PS->QT7) then everything is fine. Is this a known issue or do I have the wrong version? The one I have says raw2dng converter GUI for 5D2 // Beta 1.0 Thanks
We never reached 1.0, is possible that it's rawmagic what you have?
Quote from: jc on June 21, 2013, 07:13:07 PM
so yeah any thoughts on auto joining the 5d2 4GB files?
Thanks. James
It's just a matter of finding time to code it, but it will be added in future release.
Quote from: frenchps49 on June 21, 2013, 03:47:01 PM
Hi, Used 0.13. Computer says it can't open the prores sequence. It's not a video.
The end of the verbose inside the app:
"frame= 409 fps=1.7 q=0.0 size= 385499kB time=00:00:17.05 bitrate=185125.8kbits/s
/Applications/raw2dng0.13.app/Contents/Resources/script: line 40: 2216 Done "$DCRAW" -c -H 0 -6 -W -q 3 "$Wtemp" *.dng
2217 Segmentation fault: 11 | "$FFMPEG" -f image2pipe -vcodec ppm -r "$FPS" -i pipe:0 -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt yuv444p10 -y -r "$FPS" "$FLDR$FILE_NAME".mov
Done"
If that can help you.
0.12 works?
Hello,
With 0.13 i activate in the options ProResHQ 4444, but the generated .mov is in ProRes 422 HQ (With cmd + i or in FCPX)
What i do wrong ?
Best regards
Quote from: meditant on June 22, 2013, 09:01:06 AM
Hello,
With 0.13 i activate in the options ProResHQ 4444, but the generated .mov is in ProRes 422 HQ (With cmd + i or in FCPX)
What i do wrong ?
Best regards
You do nothing wrong. the movie is 4444, but it gets the wrong codec flag (its apch, shoult be ap4h) . this is an issue from ffmpeg. If you open the movie in vlc, you can see in info (cmd+i) decoded Format Planar 4:4:4 YUV. As well you can see the difference from 422 to 444 in some places, like very hard contrast, for example the canyon scene from lukas neumann. Not sure if this causes any problems - haven't found one.
Quote from: jc on June 21, 2013, 07:13:07 PM
so yeah any thoughts on auto joining the 5d2 4GB files?
Thanks. James
for now you can join them manually:
open terminal then type:
cd /Volumes/bashi/Pictures/Raw (or wherever your RAW files are, you can just drag and drop the folder to terminal)
hit Enter
cat NAME.RAW NAME.R00 NAME.R01 > merged.RAW (input as many .R00, .R01 you have)
hit Enter
then you have a .RAW that contains all raws - drop this merged.RAW to raw2dng.app
I love this little app. Is it possible to add some sort of dead pixel filter for when converting to proRes especially? I find som tiny dlts when pressing iso and in 5x mode. Preferably optional like the other stuff.
Thanks guys
//D
Quote from: bashi on June 22, 2013, 01:57:56 PM
You do nothing wrong. the movie is 4444, but it gets the wrong codec flag (its apch, shoult be ap4h) . this is an issue from ffmpeg. If you open the movie in vlc, you can see in info (cmd+i) decoded Format Planar 4:4:4 YUV. As well you can see the difference from 422 to 444 in some places, like very hard contrast, for example the canyon scene from lukas neumann. Not sure if this causes any problems - haven't found one.
Ok thanks for the info, in vlc 444 10 bits !
It exist a 14bits mov codecs ?
Best regards
Quote from: meditant on June 22, 2013, 05:52:52 PM
Ok thanks for the info, in vlc 444 10 bits !
It exist a 14bits mov codecs ?
Best regards
I haven't found one yet. Currently i'm aiming at 12bit, but even this seems difficult... i've read somewhere that the setting we are using currently is 4444 12 bit, but that seem be wrong, since vlc says 10 bit...
If you want to use 14bit, use the cinemaDng converter and use those image sequences.
i personally kind of see no point in having a video that is equal or bigger in size than this cinemaDng would be..
i'm as well open for suggestions of other codecs - prores is really nice for editing, but it is soft.
Quote from: frenchps49 on June 21, 2013, 03:47:01 PM
Hi, Used 0.13. Computer says it can't open the prores sequence. It's not a video.
The end of the verbose inside the app:
"frame= 409 fps=1.7 q=0.0 size= 385499kB time=00:00:17.05 bitrate=185125.8kbits/s
/Applications/raw2dng0.13.app/Contents/Resources/script: line 40: 2216 Done "$DCRAW" -c -H 0 -6 -W -q 3 "$Wtemp" *.dng
2217 Segmentation fault: 11 | "$FFMPEG" -f image2pipe -vcodec ppm -r "$FPS" -i pipe:0 -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt yuv444p10 -y -r "$FPS" "$FLDR$FILE_NAME".mov
Done"
If that can help you.
has this video 409 or 410 frames? if so try to delete the last frame and re-run. I got this error on a video, where the last .dng file is messed up.
otherwise try to open the .dng around frame 409 (408, 410) - are they ok?
Yo
Quote from: bashi on June 22, 2013, 07:54:41 PM
has this video 409 or 410 frames? if so try to delete the last frame and re-run. I got this error on a video, where the last .dng file is messed up.
otherwise try to open the .dng around frame 409 (408, 410) - are they ok?
You are right. The last DNG is messed up. It happened to all the shots I have checked. I'd be glad to rerun one. You suggest to remove the last frame but how can I remove the last frame of the RAW file ??? The problem happens when I want the Prores 4444 from the Raw file. Thanks for helping.
it is possible to see the fps of the file you're converting, like some older versions?? thanks guys !!
Quote from: frenchps49 on June 22, 2013, 09:47:22 PM
Yo
You are right. The last DNG is messed up. It happened to all the shots I have checked. I'd be glad to rerun one. You suggest to remove the last frame but how can I remove the last frame of the RAW file ??? The problem happens when I want the Prores 4444 from the Raw file. Thanks for helping.
prores is made from .dng anyway, so you can delete it after all the dng's are copied over and while the prores is made...
Quote from: bashi on June 22, 2013, 11:41:24 PM
prores is made from .dng anyway, so you can delete it after all the dng's are copied over and while the prores is made...
Your solution works. Although you must admit it's not efficient if you have a long batch of clips to convert. Maybe you can make it automatic. Easy for me to say...
Thank you all and continue with the good work.
Quote from: noix222 on June 22, 2013, 10:06:24 PM
it is possible to see the fps of the file you're converting, like some older versions?? thanks guys !!
Yep, restored back in 0.14
Hello, guys.
I don't think it's a bug. But i think it will be good if you can add these options in upcoming builds:
1) please add an option to proceed apple prores 4444 WITHOUT auto white balance either any whitebalance presets (cloudy, shade, tungsten etc,)
Here's the short movie where you can see how auto white balance does really bad thing
http://youtu.be/0rCHzaa0--E
I think it's really useful to be able to get prores 4444 on the go, but in some cases auto white balance works just not right.
2)add an option for user to be able not to procced DNGs but to result only in MOV file instead.
If i need a MOV why would i need a DNG's?
Add an option to chose whether we need both DNG and MOV neither we need only DNGs or only MOV.
Just a request but, could you put an empty loading bar when first opening raw2dng? Also when you start processing can we get a actual loading bar? In another words a blue indicator that shows the progress of the extraction? Also could we get a ding when the processing is finished? The tri-toned one that you hear after you successfully install software.
Quote from: Gumadzon on June 23, 2013, 10:32:26 PM
Hello, guys.
I don't think it's a bug. But i think it will be good if you can add these options in upcoming builds:
1) please add an option to proceed apple prores 4444 WITHOUT auto white balance either any whitebalance presets (cloudy, shade, tungsten etc,)
Here's the short movie where you can see how auto white balance does really bad thing
http://youtu.be/0rCHzaa0--E
I think it's really useful to be able to get prores 4444 on the go, but in some cases auto white balance works just not right.
2)add an option for user to be able not to procced DNGs but to result only in MOV file instead.
If i need a MOV why would i need a DNG's?
Add an option to chose whether we need both DNG and MOV neither we need only DNGs or only MOV.
They have the raw2dng.app becoming very self INTUATIVE, so open the app then just like dropping a .RAW file into the window drop the raw2dng.app into the window, then it will give you the option of turning off the progress 4444 white balance also.
Pro Res 4444 should be the only format you should put into you editor.
Quote from: dariSSight#1 on June 24, 2013, 04:57:16 AM
They have the raw2dng.app becoming very self INTUATIVE, so open the app then just like dropping a .RAW file into the window drop the raw2dng.app into the window, then it will give you the option of turning off the progress 4444 white balance also.
Pro Res 4444 should be the only format you should put into you editor.
Yes, i have figured out this preferences that you described. But in drop down list there are only presets, like cloudy, tungsten or auto. I need prores 4444 to get white balance properties as it is (as it was shot). I can't get it now, because there's no such feature in current v 0.13 of raw2dng.
Am I wrong?
You can,t get "as shot whitebalance". Magic L raw mode doesn,t record it to the file. I all has to be done in acr if you want to be 100%
Quote from: Danne on June 24, 2013, 01:25:21 PM
You can,t get "as shot whitebalance". Magic L raw mode doesn,t record it to the file. I all has to be done in acr if you want to be 100%
Previous workflow used conversion from DNGs to TIFFs in Photoshop and user was able to just select all frames in sequence WITHOUT doing any corrections. Can you add this "WITHOUT CORRECTION" feature to raw2dng to proceed prores 4444 video files? Is it clear to you?
Quote from: Gumadzon on June 24, 2013, 02:17:09 PM
Previous workflow used conversion from DNGs to TIFFs in Photoshop and user was able to just select all frames in sequence WITHOUT doing any corrections. Can you add this "WITHOUT CORRECTION" feature to raw2dng to proceed prores 4444 video files? Is it clear to you?
not clear to me. There is no raw bayer to rgb or whatever conversion without some sort of "correction". After all you convert a black and white image to colors... You want uniWB? doubt it. You want fixed WB, what value then? You want adobe conversion? then use adobe...
Regarding the whitebalance settings in raw to dng. Are the presets consistent kelvin-numbers? I understand auto is doing some kind of frame by frame stuff but maybe not the other presets? Would be golden with some kind of tumbnail before applying the whitebalance to the ProRes but it,s not necessary.
Awesome app guys!
Quote from: Danne on June 24, 2013, 04:57:03 PM
Regarding the whitebalance settings in raw to dng. Are the presets consistent kelvin-numbers? I understand auto is doing some kind of frame by frame stuff but maybe not the other presets? Would be golden with some kind of tumbnail before applying the whitebalance to the ProRes but it,s not necessary.
Awesome app guys!
what we use currently, dcraw, has no kelvin, unfortunately, but rgb multipliers. Auto setting currently does frame by frame - like to change that to take the wb setting from first (or whatever) frame and then apply this to all frames.
My version of raw2dng.app has full preview ;-) don't know if scrax is going to implement it... maybe i release my version separate...
Quote from: dariSSight#1 on June 24, 2013, 04:57:16 AM
Pro Res 4444 should be the only format you should put into you editor.
Isn't the raw data 442? If so, wouldn't Pro Res 444 be a waste of space?
Quote from: silvertonesx24 on June 24, 2013, 05:36:12 PM
Isn't the raw data 442? If so, wouldn't Pro Res 444 be a waste of space?
the raw is even more than 444...
Quote from: bashi on June 24, 2013, 05:32:11 PM
My version of raw2dng.app has full preview ;-) don't know if scrax is going to implement it... maybe i release my version separate...
Auto set the same for all would be sweet :).
Oh man, full preview would be even more sweet :-X
Thanks guys!
/D
Hello,
The dng files dont work with resolve 9.1.4 or 9.1.3, i have this strange low-res files :
(http://www.franck-rondot.com/images/divers/raw2dngbug.jpg)
regards
Quote from: meditant on June 24, 2013, 08:45:45 PM
Hello,
The dng files dont work with resolve 9.1.4
regards
use rawmagic for now.
http://www.magiclantern.fm/forum/index.php?topic=6218.0 (http://www.magiclantern.fm/forum/index.php?topic=6218.0)
it's work fine with raw magic but its strange ?
Quote from: bashi on June 24, 2013, 05:32:11 PM
what we use currently, dcraw, has no kelvin, unfortunately, but rgb multipliers. Auto setting currently does frame by frame - like to change that to take the wb setting from first (or whatever) frame and then apply this to all frames.
My version of raw2dng.app has full preview ;-) don't know if scrax is going to implement it... maybe i release my version separate...
Very interesting! But how to keep this dcraw to wb ratio and bring it to a prores 4444 video?What kind of correlation there's between dcraw and final wb kelvin number in final prores 4444 video? Are you trying to say that we don't need this information anymore?! Neither are we enabled to obtain this information in a different way?
It's a great feature to add preview! I have thought about it today also. Neither an ML devs could make an additional metadata able to be entered on creating new video. (Like BMCC). Very useful IMO.
Quote from: Gumadzon on June 24, 2013, 09:44:53 PM
Very interesting! But how to keep this dcraw to wb ratio and bring it to a prores 4444 video?What kind of correlation there's between dcraw and final wb kelvin number in final prores 4444 video? Are you trying to say that we don't need this information anymore?! Neither are we enabled to obtain this information in a different way?
sorry ;-) but i don't understand most of this...
the dng are raw bayer data, like image cr2 raw, has no wb applied. dcraw converts this raw image to a color image and there you set the wb (by multiplying the rgb (rgbg)). out of this images the video, in this case prores is made. I don't know of any (non-propiertary) video format that works with raw data. now there's the cinemaDNG format (not the same as DNG) that fills this gap, raw image data for video use.
Quote from: meditant on June 24, 2013, 08:45:45 PM
Hello,
The dng files dont work with resolve 9.1.4 or 9.1.3, i have this strange low-res files :
(http://www.franck-rondot.com/images/divers/raw2dngbug.jpg)
regards
Da Vinci Resolve interprets correctly only CinemaDNG. DNG (Digital Negative) is for photography. raw2dng.app creates DNG sequence. CinemaDNG has more metadata in xmp than regular DNG. Basically Resolve gets "confused" with thumbnail data created by raw2dng.app. That is, as far as I know, problem with regular DNG in Resolve. If there is a way to put this metadata in DNG's during conversion in raw2dng.app, that would be very nice for workflow.
What's the command line to convert to ProRes? I'd like first to work on dng's in Lightroom then export tif's to ProRes
Quote from: pavelpp on June 25, 2013, 08:38:43 AM
What's the command line to convert to ProRes? I'd like first to work on dng's in Lightroom then export tif's to ProRes
ffmpeg -vcodec tiff -i &6d.tiff -r FPS -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt yuv444p10le -y -r FPS OUTPUT.mov
cd to your folder containing tiff.
replace both FPS with your actual fps!
Quote from: bashi on June 25, 2013, 09:43:23 AM
ffmpeg -vcodec tiff -i &6d.tiff -r FPS -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt yuv444p10be -y -r FPS OUTPUT.mov
cd to your folder containing tiff.
replace both FPS with your actual fps!
Thanks, exactly what I needed!
However is it -pix_fmt yuv444p10be or -pix_fmt yuv444p14be ?
sorry, should be: yuv444p10le
that's the "highest" i got to work.
Quote from: scrax on June 22, 2013, 05:56:08 AM
It's just a matter of finding time to code it, but it will be added in future release.
Great! Would remove one big step for me having to join files ! So looking forward to it :-)
Yes also a hot pixel fix if possible would be great too! James
It's very nice to see now, that raw2dng moves the files to a specific folder (in my case from the CF-card to an external drive) and creates ProRes4444.
But that's useless, unless spanned files are supported!
the prores4444 files are created but can't be ready by Premiere or Quicktime, anyone else having this issue? Also I can't find out how to turn off the creation of the prores files to save space since they don't work.
Quote from: zmelms on June 26, 2013, 03:05:04 AM
the prores4444 files are created but can't be ready by Premiere or Quicktime, anyone else having this issue? Also I can't find out how to turn off the creation of the prores files to save space since they don't work.
What os, qt and premiere version?
Mine read just fine on pr po cs5
10.8.4
QT x
CS6 all the newest stuff
and I have Apple Compressor installed for the ProRes components.
Here's the weird thing. The only file that worked (aka was recognized by quicktime) was one that I hit the cancel button part way thru the conversion.
Quote from: zmelms on June 26, 2013, 08:48:32 PM
10.8.4
QT x
CS6 all the newest stuff
and I have Apple Compressor installed for the ProRes components.
Here's the weird thing. The only file that worked (aka was recognized by quicktime) was one that I hit the cancel button part way thru the conversion.
let's see, 1. can you open the last .dng in those folder without error?
if , this is a known issue and will be resolved. you can hack it to work by deleting this .dng while it is converting to video.
otherwise, After the conversion, click the arrow left near Details, can you copy to the content to pasteall.org or here?
With the older versions of raw2dng, it would allow me to have the app on my desktop, and wherever I dragged the .raw file from is where the converted files would go. Now, they always go to my desktop. My computer hard drive is full but I have an external with space. The raw files are on the external, but when I drag and drop them in raw2dng, it places the converted files on my dektop AND moves a copy of the raw file to my desktop. I've also tried putting the raw2dng app on my external and working on it from there... still places the files on the desktop. I also tried opening raw2dng (from both the external and the one on my desktop) and dragging the app icon onto the opened app and selecting the work folder and it STILL puts the files on my desktop. Any help? I have these files that need to be done and I cant even get the dngs extracted.
NVM, I figured it out. If anyone has the same problem.
All you have to do is redownload it. Put the zip on whatever drive your files are on and unzip it there. If you try just dragging the app to the new drive, it wont work.
Scrax, I figured out the solution to my error BUT, when opening the app(on my external) then dragging the same icon(raw2dng icon) onto the app, I don't get the menu, therefore I can't disable the prores file thing. Any ideas?
Hi Scrax,
Fantastic work with raw2dng!
As a suggestion for your next version, could you please make the app modify the ProRes video file to have the same file creation date at the original .RAW file?
This can be done with Touch http://en.wikipedia.org/wiki/Touch_%28Unix%29 (http://en.wikipedia.org/wiki/Touch_%28Unix%29)
Then timecode can be easily added to the converted ProRes video file using http://www.videotoolshed.com/product/42/qtchange
(http://www.videotoolshed.com/product/42/qtchange)
I've written a blog post for how to manually add timecode to video files created from raw2dng:
http://punkoryan.com/2013/07/04/how-to-add-timecode-to-raw-video-from-canon-5d-mark-iii-with-magic-lantern-hack (http://punkoryan.com/2013/07/04/how-to-add-timecode-to-raw-video-from-canon-5d-mark-iii-with-magic-lantern-hack)
Thanks!
hey guys. not a programmer but a filmmaker here with limited coding knowledge.
I'm shooting RAW 1280x720 with my t4i.
When i get files larger than 2GB I can't get them to open in Raw2DNG. this forum says thats Captain Hook fixed this issue but I can't seem to get it to work, even when I download the latest build of Raw2dng (0.13).
Thanks for your help guys!
I love the raw2dng.app .RAW converter, I'm wondering how accurate the white balance auto, can you give an option like we have with ProRes 4444 and Destination folder to turn off.
Hey, thanks for the program but, How to deactivate DNGs for keep only prores 4444?
you can,t at the moment. I fiddled around with adobe media encoder and managed to export rawfiles to ProRes by adding the ginger-plugin to the media encoder encoder. You could try that if you work with adobe software.
Instructions
http://www.magiclantern.fm/forum/index.php?topic=6550.msg51797#msg51797
Thanks but I think at this moment, the best solution is Raw2dng.
figured it out, i was downloading the executables with CHROME on my Mac and for some reason CHROME messes up files downloaded that have to install.
does anyone know why this would be? Even messes up DMGs when they are downloaded to 100%.
Hi!
Would it be possible to implement an extra step wich would give the alternative to produce a more edit-friendly proxyfile?. Maybe at half size of the original-file. 1920x1080 dng and 960x540 proxy (ProRes-files)?
Thanks
//D
Has development stopped for this fantastic app?
I really hope not as it shows a lot of promis but features people were looking for include:
1) joining of multiple .r001 .r002 etc.. Files for the 5d2, 50d and others that require 4gb split files
2) a better GUI for selecting options such as if it makes a pro-res file and options for it ( as opposed to dragging in the GUI into its self with limited options )
3) some kind of preview of clips before they are converted over .. Maybe dropping frames or even B&W but this would be a huge time saver as I could know what clips are what
I think the option of a lower res prores sounds a great idea too! :-)
Also for me the pro res files come out way too dark on my 5dii, do others have this issue. Currently editing in premiere and auto levels fixes this just fine but it's an odd issue
Also will it be open sourced ? Seems that as magic lantern is an open effort the raw converter tools would benefit from being so too!
Anyway love to see some more progress ! James
this raw2dng gives me directly Prores4444, Just Drag and Drop. cool.
But now i checked the prores files and they are shit.
The color within a shot keeps changing. Not really from frame to frame,
but with in 3 or 4 frames, skin tones suddenly green or blue.
Sucks.
But when i do Photoshop then export to tiff then quicktime pro to sequence,
everything fine.
Now I need a new converter from raw to dng,
cause raw2dng does the prores transfer automatically and that keeps ages.
Quote from: Olli5D on July 17, 2013, 04:54:58 PM
this raw2dng gives me directly Prores4444, Just Drag and Drop. cool.
But now i checked the prores files and they are shit.
The color within a shot keeps changing. Not really from frame to frame,
but with in 3 or 4 frames, skin tones suddenly green or blue.
Sucks.
But when i do Photoshop then export to tiff then quicktime pro to sequence,
everything fine.
Now I need a new converter from raw to dng,
cause raw2dng does the prores transfer automatically and that keeps ages.
Olli5D, from what I understand the generated ProRes file is to be used for reference, not as an actual finished ProRes file. It allows you to quickly look at your converted raw footage so to have an idea how they came out. From there you can judge if it will be a useable clip for you.
Well... that makes sense.
But wait so long just for a preview? without having the option to skip this process and stay with your dngs?
Strange.
Is this still a problem with raw2dng?
For some reason, the proresHQ 4444 file put out by raw2dng is unrecognized by my system - OSX 10.8.4
(http://i.imgbox.com/abgLd3AS.png)
Anybody has any idea why? Here's the resultant text:
raw2dng converter GUI for OsX
Beta ver.0.13
M28-1957 File Supported
Generating ProResHQ 4444 with FPS: 23.976
ffmpeg version 1.2.1-tessus Copyright (c) 2000-2013 the FFmpeg developers
built on May 9 2013 21:58:14 with llvm-gcc 4.2.1 (LLVM build 2336.1.00)
configuration: --prefix=/Users/tessus/data/ext/ffmpeg/sw --as=yasm --extra-version=tessus --disable-shared --enable-static --disable-ffplay --enable-gpl --enable-pthreads --enable-postproc --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libspeex --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libxavs --enable-version3 --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvpx --enable-libgsm --enable-libopus --enable-fontconfig --enable-libfreetype --enable-libass --enable-filters --enable-runtime-cpudetect
libavutil 52. 18.100 / 52. 18.100
libavcodec 54. 92.100 / 54. 92.100
libavformat 54. 63.104 / 54. 63.104
libavdevice 54. 3.103 / 54. 3.103
libavfilter 3. 42.103 / 3. 42.103
libswscale 2. 2.100 / 2. 2.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 2.100 / 52. 2.100
[image2pipe @ 0x102019600] Stream #0: not enough frames to estimate rate; consider increasing probesize
[image2pipe @ 0x102019600] Estimating duration from bitrate, this may be inaccurate
Input #0, image2pipe, from 'pipe:0':
Duration: N/A, bitrate: N/A
Stream #0:0: Video: ppm, rgb48be, 1920x1080, 23.98 tbr, 23.98 tbn, 23.98 tbc
Output #0, mov, to '/Users/oscarmoreno/Desktop/test/M28-1957.mov':
Metadata:
encoder : Lavf54.63.104
Stream #0:0: Video: prores (apch / 0x68637061), yuv444p10le, 1920x1080, q=2-31, 200 kb/s, 11988 tbn, 23.98 tbc
Stream mapping:
Stream #0:0 -> #0:0 (ppm -> prores_kostya)
frame= 3 fps=2.1 q=0.0 size= 2844kB time=00:00:00.12 bitrate=186177.9kbits/s
frame= 4 fps=1.6 q=0.0 size= 3792kB time=00:00:00.16 bitrate=186204.1kbits/s
frame= 5 fps=1.4 q=0.0 size= 4740kB time=00:00:00.20 bitrate=186198.5kbits/s
frame= 6 fps=1.3 q=0.0 size= 5688kB time=00:00:00.25 bitrate=186211.6kbits/s
frame= 7 fps=1.3 q=0.0 size= 6637kB time=00:00:00.29 bitrate=186225.3kbits/s
frame= 8 fps=1.2 q=0.0 size= 7585kB time=00:00:00.33 bitrate=186231.5kbits/s
frame= 9 fps=1.2 q=0.0 size= 8533kB time=00:00:00.37 bitrate=186225.4kbits/s
frame= 10 fps=1.2 q=0.0 size= 9481kB time=00:00:00.41 bitrate=186221.4kbits/s
frame= 11 fps=1.1 q=0.0 size= 10428kB time=00:00:00.45 bitrate=186206.4kbits/s
frame= 12 fps=1.1 q=0.0 size= 11377kB time=00:00:00.50 bitrate=186209.4kbits/s
frame= 13 fps=1.1 q=0.0 size= 12325kB time=00:00:00.54 bitrate=186211.3kbits/s
frame= 14 fps=1.1 q=0.0 size= 13273kB time=00:00:00.58 bitrate=186209.0kbits/s
frame= 15 fps=1.1 q=0.0 size= 14221kB time=00:00:00.62 bitrate=186216.2kbits/s
frame= 16 fps=1.1 q=0.0 size= 15169kB time=00:00:00.66 bitrate=186212.7kbits/s
frame= 17 fps=1.1 q=0.0 size= 16118kB time=00:00:00.70 bitrate=186218.8kbits/s
frame= 18 fps=1.1 q=0.0 size= 17065kB time=00:00:00.75 bitrate=186210.9kbits/s
frame= 19 fps=1.1 q=0.0 size= 18013kB time=00:00:00.79 bitrate=186204.8kbits/s
frame= 20 fps=1.1 q=0.0 size= 18961kB time=00:00:00.83 bitrate=186203.5kbits/s
frame= 21 fps=1.1 q=0.0 size= 19909kB time=00:00:00.87 bitrate=186204.9kbits/s
frame= 22 fps=1.0 q=0.0 size= 20857kB time=00:00:00.91 bitrate=186204.0kbits/s
frame= 23 fps=1.0 q=0.0 size= 21805kB time=00:00:00.95 bitrate=186202.9kbits/s
frame= 24 fps=1.0 q=0.0 size= 22752kB time=00:00:01.00 bitrate=186202.0kbits/s
frame= 25 fps=1.0 q=0.0 size= 23701kB time=00:00:01.04 bitrate=186206.6kbits/s
frame= 26 fps=1.0 q=0.0 size= 24650kB time=00:00:01.08 bitrate=186209.7kbits/s
frame= 27 fps=1.0 q=0.0 size= 25597kB time=00:00:01.12 bitrate=186208.6kbits/s
frame= 28 fps=1.0 q=0.0 size= 26546kB time=00:00:01.16 bitrate=186211.4kbits/s
frame= 29 fps=1.0 q=0.0 size= 27494kB time=00:00:01.20 bitrate=186211.7kbits/s
frame= 30 fps=1.0 q=0.0 size= 28442kB time=00:00:01.25 bitrate=186208.4kbits/s
frame= 31 fps=1.0 q=0.0 size= 29389kB time=00:00:01.29 bitrate=186205.5kbits/s
frame= 32 fps=1.0 q=0.0 size= 30337kB time=00:00:01.33 bitrate=186203.8kbits/s
frame= 33 fps=1.0 q=0.0 size= 31284kB time=00:00:01.37 bitrate=186198.8kbits/s
frame= 34 fps=1.0 q=0.0 size= 32233kB time=00:00:01.41 bitrate=186201.7kbits/s
frame= 35 fps=1.0 q=0.0 size= 33181kB time=00:00:01.45 bitrate=186202.6kbits/s
frame= 36 fps=1.0 q=0.0 size= 34129kB time=00:00:01.50 bitrate=186203.7kbits/s
frame= 37 fps=1.0 q=0.0 size= 35077kB time=00:00:01.54 bitrate=186202.6kbits/s
frame= 38 fps=1.0 q=0.0 size= 36026kB time=00:00:01.58 bitrate=186206.1kbits/s
frame= 39 fps=1.0 q=0.0 size= 36973kB time=00:00:01.62 bitrate=186205.2kbits/s
frame= 40 fps=1.0 q=0.0 size= 37922kB time=00:00:01.66 bitrate=186205.4kbits/s
frame= 41 fps=1.0 q=0.0 size= 38869kB time=00:00:01.71 bitrate=186203.8kbits/s
frame= 42 fps=1.0 q=0.0 size= 39817kB time=00:00:01.75 bitrate=186205.0kbits/s
frame= 43 fps=1.0 q=0.0 size= 40765kB time=00:00:01.79 bitrate=186204.8kbits/s
frame= 44 fps=1.0 q=0.0 size= 41713kB time=00:00:01.83 bitrate=186201.0kbits/s
frame= 45 fps=1.0 q=0.0 size= 42660kB time=00:00:01.87 bitrate=186196.7kbits/s
frame= 46 fps=1.0 q=0.0 size= 43608kB time=00:00:01.91 bitrate=186196.9kbits/s
frame= 47 fps=1.0 q=0.0 size= 44556kB time=00:00:01.96 bitrate=186196.1kbits/s
frame= 48 fps=1.0 q=0.0 size= 45503kB time=00:00:02.00 bitrate=186195.8kbits/s
frame= 49 fps=1.0 q=0.0 size= 46452kB time=00:00:02.04 bitrate=186197.0kbits/s
frame= 50 fps=1.0 q=0.0 size= 47401kB time=00:00:02.08 bitrate=186200.4kbits/s
frame= 51 fps=1.0 q=0.0 size= 48349kB time=00:00:02.12 bitrate=186202.9kbits/s
frame= 52 fps=1.0 q=0.0 size= 49298kB time=00:00:02.16 bitrate=186206.9kbits/s
frame= 53 fps=1.0 q=0.0 size= 50247kB time=00:00:02.21 bitrate=186210.0kbits/s
frame= 54 fps=1.0 q=0.0 size= 51195kB time=00:00:02.25 bitrate=186209.3kbits/s
frame= 55 fps=1.0 q=0.0 size= 52144kB time=00:00:02.29 bitrate=186211.3kbits/s
frame= 56 fps=1.0 q=0.0 size= 53092kB time=00:00:02.33 bitrate=186213.0kbits/s
frame= 57 fps=1.0 q=0.0 size= 54041kB time=00:00:02.37 bitrate=186213.6kbits/s
frame= 58 fps=1.0 q=0.0 size= 54988kB time=00:00:02.41 bitrate=186213.1kbits/s
frame= 59 fps=1.0 q=0.0 size= 55936kB time=00:00:02.46 bitrate=186211.6kbits/s
frame= 60 fps=1.0 q=0.0 size= 56884kB time=00:00:02.50 bitrate=186212.4kbits/s
frame= 61 fps=1.0 q=0.0 size= 57832kB time=00:00:02.54 bitrate=186209.4kbits/s
frame= 62 fps=1.0 q=0.0 size= 58779kB time=00:00:02.58 bitrate=186209.0kbits/s
frame= 63 fps=1.0 q=0.0 size= 59727kB time=00:00:02.62 bitrate=186208.0kbits/s
frame= 64 fps=1.0 q=0.0 size= 60675kB time=00:00:02.66 bitrate=186208.5kbits/s
frame= 65 fps=1.0 q=0.0 size= 61624kB time=00:00:02.71 bitrate=186208.7kbits/s
frame= 66 fps=1.0 q=0.0 size= 62572kB time=00:00:02.75 bitrate=186208.7kbits/s
frame= 67 fps=1.0 q=0.0 size= 63519kB time=00:00:02.79 bitrate=186206.9kbits/s
frame= 68 fps=1.0 q=0.0 size= 64467kB time=00:00:02.83 bitrate=186207.1kbits/s
frame= 69 fps=1.0 q=0.0 size= 65415kB time=00:00:02.87 bitrate=186206.6kbits/s
frame= 70 fps=1.0 q=0.0 size= 66364kB time=00:00:02.91 bitrate=186209.1kbits/s
frame= 71 fps=1.0 q=0.0 size= 67312kB time=00:00:02.96 bitrate=186209.0kbits/s
frame= 72 fps=1.0 q=0.0 size= 68261kB time=00:00:03.00 bitrate=186210.4kbits/s
frame= 73 fps=1.0 q=0.0 size= 69208kB time=00:00:03.04 bitrate=186209.6kbits/s
frame= 74 fps=1.0 q=0.0 size= 70158kB time=00:00:03.08 bitrate=186213.7kbits/s
frame= 75 fps=1.0 q=0.0 size= 71106kB time=00:00:03.12 bitrate=186213.8kbits/s
frame= 613 fps=1.0 q=0.0 size= 581090kB time=00:00:25.56 bitrate=186187.0kbits/s
/Applications/raw2dng.app/Contents/Resources/script: line 40: 4661 Done "$DCRAW" -c -H 0 -6 -W -q 3 "$Wtemp" *.dng
4662 Segmentation fault: 11 | "$FFMPEG" -f image2pipe -vcodec ppm -r "$FPS" -i pipe:0 -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt yuv444p10 -y -r "$FPS" "$FLDR$FILE_NAME".mov
Done
Also OSX 10.8.4 here. But works fine with me.
What version of FCP you have?
(EDIT) Was my firewall.
Quote from: Olli5D on July 17, 2013, 05:34:22 PM
Also OSX 10.8.4 here. But works fine with me.
What version of FCP you have?
Still using FCP 7. . .
Quote from: Olli5D on July 17, 2013, 05:26:38 PM
Well... that makes sense.
But wait so long just for a preview? without having the option to skip this process and stay with your dngs?
Strange.
If you doubleclick the app and the drag and drop the app onto the app a bunch of options appear in front of you. In there you can skip the ProRes and also choose white balance presets. I suggest you choose cloudy for your ProRes instead of automatic.
Download link works fine. It,s on the first page, the first topic.
This doesn't work for me. When the app is on an external I don't get the options. When the app is on my desktop, I get the options but when I select the external as my output drive, it still puts the files on my desktop where the app is. So I can only have one or the either. Files get placed on my external, but I can't stop the pro res, or I can stop the pro res, but files must be on the desktop.
Strange. Works fine over here on my external drive. I have extracted my app in the same folder as the raw-files. Have you checked your names of your folders, maybe some issue with those?
Lately I skipped raw2dng due to not being able to convert larger files. For now I extract proxy pro res with adobe media encoder and dng,s with rawmagic.
By the way, where,s Scrax lately? vacation :)?
Quote from: aaphotog on July 17, 2013, 08:44:31 PM
This doesn't work for me. When the app is on an external I don't get the options. When the app is on my desktop, I get the options but when I select the external as my output drive, it still puts the files on my desktop where the app is. So I can only have one or the either. Files get placed on my external, but I can't stop the pro res, or I can stop the pro res, but files must be on the desktop.
If it doesn't work check so your directory names doesn't contain any spaces.
You should see the full path when clicking details and Error 125 if that is the case.
It outputs to your desktop because that is saved in the options.
Newbie to RAW here; Trying to convert my first 5Dii RAW test with raw2dng 0.13 on a 2007 Macbook pro.
After I drag and drop, it starts to process then the application quits unexpectedly!
Is my comp just too old and slow to do it, or am I missing something?
Do you have prores on the macbook?
Drop the raw2dng app icon onto the raw2dng dialog window and try it without doing a prores conversion.
Working with raw files will be painfully slow on that mac.
Thanks for the tip, Squig.
Tried it with ProResHQ 444 Conversion set to No... application quits unexpectedly.
I'm thinking it's my archaic machine. I'm going to give it a try on a friends newer pc.
It's 64bit.
Try rightclick on the icon. Choose 32-bit?
Ok, I'm getting a dead pixel in my footage. Not sure if it's a h/w issue on the sensor, the build (July 11 A1ex), or the raw2dng. I have the raw files from the camera if someone would like to take a look. Let me know where to drop it.
H/W: 5D Mark ii, Shot on various lenses, 64gb Komputerbay 1000x CF
Post: raw2dng ->davinci resolve lite 9 -> fcpx
Settings:
1880x800
2.35:1
1880: on
Frame Skipping: off
Small Hacks: on
https://vimeo.com/70832943
Quote from: menoc on July 17, 2013, 05:28:30 PM
Is this still a problem with raw2dng?
For some reason, the proresHQ 4444 file put out by raw2dng is unrecognized by my system - OSX 10.8.4
(http://i.imgbox.com/abgLd3AS.png)
Anybody has any idea why? Here's the resultant text:
raw2dng converter GUI for OsX
Beta ver.0.13
M28-1957 File Supported
Generating ProResHQ 4444 with FPS: 23.976
ffmpeg version 1.2.1-tessus Copyright (c) 2000-2013 the FFmpeg developers
built on May 9 2013 21:58:14 with llvm-gcc 4.2.1 (LLVM build 2336.1.00)
configuration: --prefix=/Users/tessus/data/ext/ffmpeg/sw --as=yasm --extra-version=tessus --disable-shared --enable-static --disable-ffplay --enable-gpl --enable-pthreads --enable-postproc --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libspeex --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libxavs --enable-version3 --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvpx --enable-libgsm --enable-libopus --enable-fontconfig --enable-libfreetype --enable-libass --enable-filters --enable-runtime-cpudetect
libavutil 52. 18.100 / 52. 18.100
libavcodec 54. 92.100 / 54. 92.100
libavformat 54. 63.104 / 54. 63.104
libavdevice 54. 3.103 / 54. 3.103
libavfilter 3. 42.103 / 3. 42.103
libswscale 2. 2.100 / 2. 2.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 2.100 / 52. 2.100
[image2pipe @ 0x102019600] Stream #0: not enough frames to estimate rate; consider increasing probesize
[image2pipe @ 0x102019600] Estimating duration from bitrate, this may be inaccurate
Input #0, image2pipe, from 'pipe:0':
Duration: N/A, bitrate: N/A
Stream #0:0: Video: ppm, rgb48be, 1920x1080, 23.98 tbr, 23.98 tbn, 23.98 tbc
Output #0, mov, to '/Users/oscarmoreno/Desktop/test/M28-1957.mov':
Metadata:
encoder : Lavf54.63.104
Stream #0:0: Video: prores (apch / 0x68637061), yuv444p10le, 1920x1080, q=2-31, 200 kb/s, 11988 tbn, 23.98 tbc
Stream mapping:
Stream #0:0 -> #0:0 (ppm -> prores_kostya)
frame= 3 fps=2.1 q=0.0 size= 2844kB time=00:00:00.12 bitrate=186177.9kbits/s
frame= 4 fps=1.6 q=0.0 size= 3792kB time=00:00:00.16 bitrate=186204.1kbits/s
frame= 5 fps=1.4 q=0.0 size= 4740kB time=00:00:00.20 bitrate=186198.5kbits/s
frame= 6 fps=1.3 q=0.0 size= 5688kB time=00:00:00.25 bitrate=186211.6kbits/s
frame= 7 fps=1.3 q=0.0 size= 6637kB time=00:00:00.29 bitrate=186225.3kbits/s
frame= 8 fps=1.2 q=0.0 size= 7585kB time=00:00:00.33 bitrate=186231.5kbits/s
frame= 9 fps=1.2 q=0.0 size= 8533kB time=00:00:00.37 bitrate=186225.4kbits/s
frame= 10 fps=1.2 q=0.0 size= 9481kB time=00:00:00.41 bitrate=186221.4kbits/s
frame= 11 fps=1.1 q=0.0 size= 10428kB time=00:00:00.45 bitrate=186206.4kbits/s
frame= 12 fps=1.1 q=0.0 size= 11377kB time=00:00:00.50 bitrate=186209.4kbits/s
frame= 13 fps=1.1 q=0.0 size= 12325kB time=00:00:00.54 bitrate=186211.3kbits/s
frame= 14 fps=1.1 q=0.0 size= 13273kB time=00:00:00.58 bitrate=186209.0kbits/s
frame= 15 fps=1.1 q=0.0 size= 14221kB time=00:00:00.62 bitrate=186216.2kbits/s
frame= 16 fps=1.1 q=0.0 size= 15169kB time=00:00:00.66 bitrate=186212.7kbits/s
frame= 17 fps=1.1 q=0.0 size= 16118kB time=00:00:00.70 bitrate=186218.8kbits/s
frame= 18 fps=1.1 q=0.0 size= 17065kB time=00:00:00.75 bitrate=186210.9kbits/s
frame= 19 fps=1.1 q=0.0 size= 18013kB time=00:00:00.79 bitrate=186204.8kbits/s
frame= 20 fps=1.1 q=0.0 size= 18961kB time=00:00:00.83 bitrate=186203.5kbits/s
frame= 21 fps=1.1 q=0.0 size= 19909kB time=00:00:00.87 bitrate=186204.9kbits/s
frame= 22 fps=1.0 q=0.0 size= 20857kB time=00:00:00.91 bitrate=186204.0kbits/s
frame= 23 fps=1.0 q=0.0 size= 21805kB time=00:00:00.95 bitrate=186202.9kbits/s
frame= 24 fps=1.0 q=0.0 size= 22752kB time=00:00:01.00 bitrate=186202.0kbits/s
frame= 25 fps=1.0 q=0.0 size= 23701kB time=00:00:01.04 bitrate=186206.6kbits/s
frame= 26 fps=1.0 q=0.0 size= 24650kB time=00:00:01.08 bitrate=186209.7kbits/s
frame= 27 fps=1.0 q=0.0 size= 25597kB time=00:00:01.12 bitrate=186208.6kbits/s
frame= 28 fps=1.0 q=0.0 size= 26546kB time=00:00:01.16 bitrate=186211.4kbits/s
frame= 29 fps=1.0 q=0.0 size= 27494kB time=00:00:01.20 bitrate=186211.7kbits/s
frame= 30 fps=1.0 q=0.0 size= 28442kB time=00:00:01.25 bitrate=186208.4kbits/s
frame= 31 fps=1.0 q=0.0 size= 29389kB time=00:00:01.29 bitrate=186205.5kbits/s
frame= 32 fps=1.0 q=0.0 size= 30337kB time=00:00:01.33 bitrate=186203.8kbits/s
frame= 33 fps=1.0 q=0.0 size= 31284kB time=00:00:01.37 bitrate=186198.8kbits/s
frame= 34 fps=1.0 q=0.0 size= 32233kB time=00:00:01.41 bitrate=186201.7kbits/s
frame= 35 fps=1.0 q=0.0 size= 33181kB time=00:00:01.45 bitrate=186202.6kbits/s
frame= 36 fps=1.0 q=0.0 size= 34129kB time=00:00:01.50 bitrate=186203.7kbits/s
frame= 37 fps=1.0 q=0.0 size= 35077kB time=00:00:01.54 bitrate=186202.6kbits/s
frame= 38 fps=1.0 q=0.0 size= 36026kB time=00:00:01.58 bitrate=186206.1kbits/s
frame= 39 fps=1.0 q=0.0 size= 36973kB time=00:00:01.62 bitrate=186205.2kbits/s
frame= 40 fps=1.0 q=0.0 size= 37922kB time=00:00:01.66 bitrate=186205.4kbits/s
frame= 41 fps=1.0 q=0.0 size= 38869kB time=00:00:01.71 bitrate=186203.8kbits/s
frame= 42 fps=1.0 q=0.0 size= 39817kB time=00:00:01.75 bitrate=186205.0kbits/s
frame= 43 fps=1.0 q=0.0 size= 40765kB time=00:00:01.79 bitrate=186204.8kbits/s
frame= 44 fps=1.0 q=0.0 size= 41713kB time=00:00:01.83 bitrate=186201.0kbits/s
frame= 45 fps=1.0 q=0.0 size= 42660kB time=00:00:01.87 bitrate=186196.7kbits/s
frame= 46 fps=1.0 q=0.0 size= 43608kB time=00:00:01.91 bitrate=186196.9kbits/s
frame= 47 fps=1.0 q=0.0 size= 44556kB time=00:00:01.96 bitrate=186196.1kbits/s
frame= 48 fps=1.0 q=0.0 size= 45503kB time=00:00:02.00 bitrate=186195.8kbits/s
frame= 49 fps=1.0 q=0.0 size= 46452kB time=00:00:02.04 bitrate=186197.0kbits/s
frame= 50 fps=1.0 q=0.0 size= 47401kB time=00:00:02.08 bitrate=186200.4kbits/s
frame= 51 fps=1.0 q=0.0 size= 48349kB time=00:00:02.12 bitrate=186202.9kbits/s
frame= 52 fps=1.0 q=0.0 size= 49298kB time=00:00:02.16 bitrate=186206.9kbits/s
frame= 53 fps=1.0 q=0.0 size= 50247kB time=00:00:02.21 bitrate=186210.0kbits/s
frame= 54 fps=1.0 q=0.0 size= 51195kB time=00:00:02.25 bitrate=186209.3kbits/s
frame= 55 fps=1.0 q=0.0 size= 52144kB time=00:00:02.29 bitrate=186211.3kbits/s
frame= 56 fps=1.0 q=0.0 size= 53092kB time=00:00:02.33 bitrate=186213.0kbits/s
frame= 57 fps=1.0 q=0.0 size= 54041kB time=00:00:02.37 bitrate=186213.6kbits/s
frame= 58 fps=1.0 q=0.0 size= 54988kB time=00:00:02.41 bitrate=186213.1kbits/s
frame= 59 fps=1.0 q=0.0 size= 55936kB time=00:00:02.46 bitrate=186211.6kbits/s
frame= 60 fps=1.0 q=0.0 size= 56884kB time=00:00:02.50 bitrate=186212.4kbits/s
frame= 61 fps=1.0 q=0.0 size= 57832kB time=00:00:02.54 bitrate=186209.4kbits/s
frame= 62 fps=1.0 q=0.0 size= 58779kB time=00:00:02.58 bitrate=186209.0kbits/s
frame= 63 fps=1.0 q=0.0 size= 59727kB time=00:00:02.62 bitrate=186208.0kbits/s
frame= 64 fps=1.0 q=0.0 size= 60675kB time=00:00:02.66 bitrate=186208.5kbits/s
frame= 65 fps=1.0 q=0.0 size= 61624kB time=00:00:02.71 bitrate=186208.7kbits/s
frame= 66 fps=1.0 q=0.0 size= 62572kB time=00:00:02.75 bitrate=186208.7kbits/s
frame= 67 fps=1.0 q=0.0 size= 63519kB time=00:00:02.79 bitrate=186206.9kbits/s
frame= 68 fps=1.0 q=0.0 size= 64467kB time=00:00:02.83 bitrate=186207.1kbits/s
frame= 69 fps=1.0 q=0.0 size= 65415kB time=00:00:02.87 bitrate=186206.6kbits/s
frame= 70 fps=1.0 q=0.0 size= 66364kB time=00:00:02.91 bitrate=186209.1kbits/s
frame= 71 fps=1.0 q=0.0 size= 67312kB time=00:00:02.96 bitrate=186209.0kbits/s
frame= 72 fps=1.0 q=0.0 size= 68261kB time=00:00:03.00 bitrate=186210.4kbits/s
frame= 73 fps=1.0 q=0.0 size= 69208kB time=00:00:03.04 bitrate=186209.6kbits/s
frame= 74 fps=1.0 q=0.0 size= 70158kB time=00:00:03.08 bitrate=186213.7kbits/s
frame= 75 fps=1.0 q=0.0 size= 71106kB time=00:00:03.12 bitrate=186213.8kbits/s
frame= 613 fps=1.0 q=0.0 size= 581090kB time=00:00:25.56 bitrate=186187.0kbits/s
/Applications/raw2dng.app/Contents/Resources/script: line 40: 4661 Done "$DCRAW" -c -H 0 -6 -W -q 3 "$Wtemp" *.dng
4662 Segmentation fault: 11 | "$FFMPEG" -f image2pipe -vcodec ppm -r "$FPS" -i pipe:0 -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt yuv444p10 -y -r "$FPS" "$FLDR$FILE_NAME".mov
Done
known issue, delete the last .dng in the folder(s). will be resolved
Quote from: Olli5D on July 17, 2013, 04:54:58 PM
this raw2dng gives me directly Prores4444, Just Drag and Drop. cool.
But now i checked the prores files and they are shit.
The color within a shot keeps changing. Not really from frame to frame,
but with in 3 or 4 frames, skin tones suddenly green or blue.
Sucks.
But when i do Photoshop then export to tiff then quicktime pro to sequence,
everything fine.
Now I need a new converter from raw to dng,
cause raw2dng does the prores transfer automatically and that keeps ages.
known issue.: currently the raw converter calculates WB for each frame, will be resolved by option to keep WB same for all
Quote from: Lucas480 on July 09, 2013, 08:33:55 AM
Hey, thanks for the program but, How to deactivate DNGs for keep only prores 4444?
currently not possible. The raw2dng in raw2dng.app is only able to output files to folder. We could delete it afterwards though.. IMO the raw2dng should be abgle to be piped - so we can 1. don't save them to disk, only keep them in memory and 2. we could extract frame ranges. This needs to be done by someone familiar with C and raw2dng.
it'd be pretty great to be able to set some simple settings that can go to prores (like make it LT, or lower resolution) and even select white balance per shot.... i think this would make for an ideal workflow... you dump out the prores right away, edit with that, and only then when you are ready for the master do you worry about the whole correction thing with RAW.
speaking of master... is there anyway to easily automate the process and relink the TIF folder in premiere/fcpx WITHOUT creating a prores version? im unable to relink a prores proxy with an image sequence.
Quote from: Danne on July 09, 2013, 09:30:35 AM
you can,t at the moment. I fiddled around with adobe media encoder and managed to export rawfiles to ProRes by adding the ginger-plugin to the media encoder encoder. You could try that if you work with adobe software.
Instructions
http://www.magiclantern.fm/forum/index.php?topic=6550.msg51797#msg51797
The ginger hdr plugin is freaking awesome, allows you to edit your RAW files directly in premeiere. I would lose alot of color space when using raw2dng as well as the weird white balance issues.
Hi, will you implement dual iso post processing in future release?
Hello,
It is possible to add the possibility to add a prefix when the .dng files is created ?
with the curent version :
Directory : M10-1449_dng
Files in directory : 000000.dng 000001.dng etc...
with prefix maybe in future version ;-) :
Directory : M10-1449_dng
Files in directory : M10-1449_000000.dng M10-1449_000001.dng etc...
This change can be very useful in resolve fcpx workflow
Best regards and thanks for you work
Quote from: jc on July 16, 2013, 04:28:00 PM
Has development stopped for this fantastic app?
I really hope not as it shows a lot of promis but features people were looking for include:
1) joining of multiple .r001 .r002 etc.. Files for the 5d2, 50d and others that require 4gb split files
2) a better GUI for selecting options such as if it makes a pro-res file and options for it ( as opposed to dragging in the GUI into its self with limited options )
3) some kind of preview of clips before they are converted over .. Maybe dropping frames or even B&W but this would be a huge time saver as I could know what clips are what
Anyway love to see some more progress ! James
I second these suggestions!
i was wondering if there was anyway to let the program accept cinemadng files that have already been converted instead of the .raw?
I was wondering the same thing ... There must be some command line options to ffmpeg and the raw converter that this app issues to convert the folder on dng's to a pro res... Just don't know / yet to work out what they are! ( in my case I used after effects )
Hey guys,
I have the latest version of Raw2dng (0.13) that generates prores444 video files from RAW. It's a bit strange because when i put the video created by Raw2dng into VideoSpec software (a freeware to know parameters of videos http://videospec.free.fr/english/) it says that it's Prores422... here is the screenshot : http://d.pr/i/hlbw
Any idea to solve this issue ?
Thanks a lot !
Leo.
development seems to have slowed down or stopped ( for the time begin at least )
this one looks to be quite good tho.. download link on the third forum page! http://www.magiclantern.fm/forum/index.php?topic=7266.0
I am using the OSX version of Raw2dng and about 2/3rds of my ProRes builds fail. The unpacking of the dng directories is fine, but the ProRes build often fails. Any ideas?
Cheers
Tony
Hey guys,
Does this look right?
The quality of the image is coming out like this http://imageshack.us/photo/my-images/600/sqes.png/.
When I import it to raw2dng here is what I get.
Once I drop the RAW file it looks like this:
http://imageshack.us/photo/my-images/401/0143.png/
Then during the process it looks like this:
http://imageshack.us/photo/my-images/821/f2o8.png/
Then at the end it looks like this:
http://imageshack.us/photo/my-images/208/4dm.png/
I installed ML on the 6D as described here http://www.magiclantern.fm/forum/index.php?topic=5530.0 .
raw2dng deleted my raw files without creating dmg files first. Does anyone know if it's possible to get the raw files back? HOW?????
Never mind, got them back, switching to Son of Batch :-\
Hey guys,
Sorry if this was reported or resolved. But I shot some stuff a couple of weeks ago, used the raw2dng, everything looks great in ACR, the ProRes files look good too. Now, when I try to drop the dngs in Davinci, is not reading the files. A few months ago, around late june, I was able to drop DNG files in Davinci and everything worked great, no problem. Did anything change? am I doing anything wrong?
please help.
thanks!
I checked with the previous shoots I've done and it seems to be a problem with the stuff I shot with either 7'th or 9th of August 5d2 build. Shots from previous builds are loading fine.
What about mlv2dng WITH conversion to Apple Prores? It is possible?
Hi, Im new in the forum...
I have a 550d and I'm trying the last night build version, to check how it works the raw video, and I dont know how to convert this in the PC I saw that there is a application raw2dng but I can not find this application or oder similar to ubuntu.
There is other option for ubuntu?
Thanks
hello.
is it possible to make a selection between the prores versions (4444, 422 HQ, 422, LT) ... ?
(sorry if this was asked before; i was off for a while)
Hi there,
It seems that the Camera Model (5DM2) is not included in the DNG when convert using Raw2DNG for Mac. So I cannot use my VSCO Camera Profiles. Any hint on how to solve this? RawMagic instead allows me to choose the Camera Model, but I feel more comfortable using the last build of Raw2DNG.
Thanks a lot,
Pablo
Quote from: Danne on July 17, 2013, 06:38:16 PM
If you doubleclick the app and the drag and drop the app onto the app a bunch of options appear in front of you. In there you can skip the ProRes and also choose white balance presets. I suggest you choose cloudy for your ProRes instead of automatic.
Download link works fine. It,s on the first page, the first topic.
Hi guys,
first of all, thank you for all your efforts. I've been a long time lurker and reader and tried to find my answers without questioning around to avoid unnecessary posts and stupid questions. Although I hoped that I can start my first post with a contribution it will be the complete contrary ... totally stupid, but after hours of trying to figure it out I'm desperate...
I read the instructions, I read the whole thread, I tried everything that came into my mind to solve it, but nothing worked --> HOW do I open the settings box for raw2dng.app 0.13?!?!
I had the app in different folders and locations. I took the icon from the desktop, from finder, from pathfinder, from dock, from the »get info« panel ... literally everywhere, but nothing worked. It always says:
raw2dng converter GUI for OsX
Beta ver.0.13
SEARCHING: /Volumes/.../RAWtoDNG/raw2dng_0.13.app/
Nothing found
I'm using Mac OSX 10.6.8.
And I downloaded the app several times, but always the same issue.
//edit
FOUND IT!!!
--> it seems that you must not change the original name of it. Since I have several version of raw2dng I always changed the name of it and added the version number. Furthermore it only works if the app is on the desktop.
Ok, so if this app is still developed is there any chance that you implement the settings option into the GUI itself as a button or something? Or at least that it doesn't matter to change the name as well as put it somewhere else than the desktop.
HA, finally, I could contribute a tiny bit at least :D
Hi people!
Do you know if DNG extracted from RAW2DNG it´s the same as the Son of batch?
Both programs are useful but RAW2DNG onlye created 4444 and take a lot of time, and I need to select the shoot before work
Thanks!
It seems the latest version of raw2dng is .13 - but it also seems to be older than latest builds of ML.
Renato mentioned in another forum (or responded to someone) that there are several identically labeled versions of raw2dng.
Really? How would we know which is which?
And better yet someone posts they finally found the newest one but provided no link or details.
Please...
I also am finding that it seems to be outputting 422 not 444. Asked once or twice if others could confirm and I only see a few others claiming output is 422.
If you know where the answers are in the forum please post or private message me.
Thx
Mike
Quote from: mkrjf on October 09, 2013, 06:56:04 AM
It seems the latest version of raw2dng is .13 - but it also seems to be older than latest builds of ML.
Renato mentioned in another forum (or responded to someone) that there are several identically labeled versions of raw2dng.
Really? How would we know which is which?
And better yet someone posts they finally found the newest one but provided no link or details.
Please...
I also am finding that it seems to be outputting 422 not 444. Asked once or twice if others could confirm and I only see a few others claiming output is 422.
If you know where the answers are in the forum please post or private message me.
Thx
Mike
I know you can choose dragging the icon over the icon in the dock some options as 4444 Yes, and define the folder to extract. Maybe devs can develop two option: Proxy version at 720 to visualize , and 4444 full res.
My resolution is still not changed. Looking further the cause.
Hello,
I have some problems with prores files converted from sequences of over 4,3GB. I read somewhere that it was possible to drag and drop directly .RAW and .R00 files in rawtodng but it doesn't work for me, so I first join them using terminal like explained here on other topics and then convert the resulting .RAW file. Converting it to .dng seems to work well (apart from a pink picture on the last frame) but the prores file does not seem to work. I'm doing this on a OS X Maverick platform. I am doing right now some intense work using a 50D with huge amount of footage, so I need the simplest solution possible to have prores files. Anybody might have an insight ?
Best Regards,
Tom
Quote from: speakingcake on October 26, 2013, 04:21:01 PM
Hello,
I have some problems with prores files converted from sequences of over 4,3GB. I read somewhere that it was possible to drag and drop directly .RAW and .R00 files in rawtodng but it doesn't work for me, so I first join them using terminal like explained here on other topics and then convert the resulting .RAW file. Converting it to .dng seems to work well (apart from a pink picture on the last frame) but the prores file does not seem to work. I'm doing this on a OS X Maverick platform. I am doing right now some intense work using a 50D with huge amount of footage, so I need the simplest solution possible to have prores files. Anybody might have an insight ?
Best Regards,
Tom
How do you use the .R00 files? I have a few from my project today.
Quote from: dariSSight on October 27, 2013, 12:27:03 AM
How do you use the .R00 files? I have a few from my project today.
Search ¨spanning files raw magic lantern¨.
Good shots!
How can you set it up so that it recognizes the camera, instead of embedded canikon?
it's not working in Mavericks, the last OSX from Apple!
Quote from: budafilms on November 06, 2013, 06:14:23 AM
it's not working in Mavericks, the last OSX from Apple!
I'm running Mavericks and it's working fine.
Can you post your version? I can't run in Mavericks, I have three computers and is not working.
I'm having trouble with OSX Mavericks as well.
Can someone please post a link to a version that runs in Mavericks?
Is there a way to convert .MLV files to DNG? (an what are the .idx files for?)
I run the latest version in the first post and maverick. Upgraded from 10.6 so probably have a lot of old code still in there :)
I have used a free app called Data Glue and it is great for Mac. Just rename the files file.001, file.002...etc. (ensuring that the number acts as file extension and there is not a hidden extension, you can see that in file properties) drag and drop in the app and rename the resulting file adding the .RAW extension in the name. ???
Quote from: dariSSight on October 27, 2013, 12:27:03 AM
How do you use the .R00 files? I have a few from my project today.
in terminal, you can use =
cd NameOfDirectoryWhereYourFilesAre
cat Mxx-hhmm.RAW Mxx-hhmm.R00 Mxx-hhmm.R01 Mxx-hhmm.R02 Mxx-hhmm.R03 > Mxx-hhmm-complete.RAW
Quote from: budafilms on December 08, 2013, 07:58:04 AM
Can you post your version? I can't run in Mavericks, I have three computers and is not working.
This is the one I use in Mavericks:
https://dl.dropboxusercontent.com/u/7439425/magiclantern/raw2dng.zip (https://dl.dropboxusercontent.com/u/7439425/magiclantern/raw2dng.zip)
Quote from: sebble on December 15, 2013, 04:16:46 PM
Is there a way to convert .MLV files to DNG? (an what are the .idx files for?)
Read up on mlv_dump process here:
http://thejohnha.blogspot.com/2013/12/converting-magic-lantern-mlv-files-to.html (http://thejohnha.blogspot.com/2013/12/converting-magic-lantern-mlv-files-to.html)
I recommend doing batchprocessing with either one of these tools
http://www.magiclantern.fm/forum/index.php?topic=9731.msg93586#msg93586
http://www.magiclantern.fm/forum/index.php?topic=8447.0
raw2dng converter GUI for OsX
Beta ver.0.13
/Volumes/Untitled/DCIM/100EOS5D/M13-0326.MLV File not Supported
Hallo everybody,
I'm on Mac Mavericks and I've just started to use raw2dng but it convert my native .raw in a quicktime mov and nont in a .dng sequence...? What is wrong?
Second question: I used RAwMagic and I'd like to know which are the differnt and if raw2dng can clean better my native raw which are full noise also if I use always ISO 100 until max 320 (DAY). I've Canon 60D.
Many thanks!
hi there
I have downloaded raw2dng file for osx but couldn't install it
somehow my macbook doesn't accept it
is there some body knows how to install it??
thanks
Hello scrax,
since a few days now there's a discussion about the future resolutions available for the 5D2 (and maybe other cameras).
It started with a1ex:
Quote from: a1ex on March 14, 2014, 09:55:26 PM
The horizontal resolution is restricted to multiples of 8 bytes and 16 pixels according to latest findings. This restriction is valid at least for 5D3 and 6D (didn't do much testing on other cameras), but I'd like to keep the code portable without camera-specific exceptions.
So, before including this change in nightly builds, I'd like to ask you which is better: 1888 with 8 pixels of black border that you will have to crop, or 1856 without any border pixels? Between these 2 values, there are no valid resolutions that respect the alignment restrictions.
This change was discussed here:
http://www.magiclantern.fm/forum/index.php?topic=3904.msg106087#msg106087
https://bitbucket.org/hudson/magic-lantern/pull-request/438/raw-recording-force-line-size-to-be/diff
In my opinion, it would be no problem to simply discard black borders from an image while converting to dng:
Quote from: guentergunter on March 24, 2014, 08:39:02 AM
...and it's also no coding effort to discard pixels while converting to dng. The user wouldn't even realize it!
This way, no one has to crop anything actively in post! It's simply done in background in the ever necessary converting (to dng) step.
I'm no programmer (just some very basic skills).
Thus it would be really great, if you could just leave a little comment about it as a programmer to help us sort things out for the 5D2 (and other cameras with the same problem):
Specific 5D2 threat (http://www.magiclantern.fm/forum/index.php?topic=5533.new#new)
Thank you very much!
I hope this is the right place to post this--I spent a lot of time searching and reading until I finally arrived here.
So the situation is like this, a brand new EOS-M camera and a new MacBook Pro. Shooting RAW in 1280x720 3x-crop. Using raw2dng.app 0.13 to make DNG image sequence and ProRes QuickTime. Works great but--pink dots! The PinkDotRemoval Java app doesn't work on my Mac or a Windows box. It is broken and has been unmaintained for a while now. What does work is A1ex's raw2dng_cs2x2_ahdlike_noise.exe -- unfortunately it only seems to be available for Windows.
Is there any way to get raw2dng_cs2x2_ahdlike_noise as an OSX app?
Thanks again to all the developers for these amazing applications!
Any way to get the DNGs to include the source filename? Right now it exports DNGs as a 6-digit number sequence that is not-unique. Can it be set up to be "sourcefilename_6digitnumbersequence"?
For instance, source filename = MR_5722. DNG convert folder contains DNGs named "MR_5722_000000" etc etc.
Thanks!
Just to be clear, the ProRes files that are created by raw2dng -- are they just proxy files for editing? I assume so, and that "prores_kostya" is a lower bitrate variety of ProRes that's not equivalent to HQ, but wanted to make sure before doing a bunch of redundant work by bringing the DNGs into AE.
Thanks for your help!
Working great here OSX Mountain Lion.
El Capitan, and the osx gui version isnt working for me.
I get
raw2dng converter GUI for OsX
Beta ver.0.13
/Users/Helen/Desktop/RawTest/M16-2115.MLV File not Supported
Any suggestions?
Mlv files are not supported. Try MLP or MLVFS or some other converter.
Thanks fotorojas,
I used your solution and it helped me as well! ;D
I've dropped a RAW file onto the raw2dng icon and I've got a .mov file and a folder with dng files in except the dng files look like so:
I havent had any luck still with this app?
(https://i.ibb.co/SdWm4JG/Screen-Shot-2019-02-12-at-23-38-24.png) (https://ibb.co/SdWm4JG)
The images are meant to be more blue and of things like a table should be visible? But as you can see its a pink haze, and very low resolution.
What is wrong with the file how can I get accesses to the images? Can someone please help
Many Many thanks!
Joel
You may want to test your footage with some not-so-outdated application ...
Take a look into the sticky threads...