Messages

got the same messege as:
fauxtoejoe


"wrong version (v5.0, expected v6.0)" when loading."
even thought you said you updated it download again, because i downloaded it today as of 2014.11.25 using this link:

https://bitbucket.org/dmilligan/magic-lantern/downloads/adv_int.mo

Hey if anyone wants to see a video i done with Camera Raw and Dual ISO

https://www.youtube.com/watch?v=qyicaOL9tl4

Hey guys, hope i aint being a nuisance, but any update on the "bright dark detection error, iso blending didnt work" bug?
im really desperate for a fix

or would it be possible if the developers let us know if a fix is to be expected anytime soon, because if not we can move on from waiting and continue with an alternate method



update and notes and tutorial for the un educated people on the following problems:
"bright dark detection error, iso blending didnt work"
flickering when filmed with dual iso

using the older version:
2014.04.08\cr2hdr-20bit.exe, doesnt give the "bright dark detection error, iso blending didnt work" error
whilst
2014.05.06\cr2hdr-20bit.exe, DOES
so apply same levels in post yourself, as cr2hdr same levels parameter uses exiftool to apply same levels anyway
processes the 0 and 1 files, and to apply same levels i used, ExifToolGUI, run the program, navigate to first file of the sequence, on the right find BlackLevel and WhiteLevel, note down the values, select all the files (i found that if i select around 2000 files it doesnt process the command so theres a file ammount limitation, 1430 worked, so maybe 2k is the limit?) at top right of the gui program, click on exiftool direct, copy and paste:

-Exif:BlackLevel=2046

NOTE, the 2046 is the variable, enter the BlackLevel you noted down from first file, click on ok, itll process the files, and create a backup of the original files, if you dont want them backed up, go to options at top left > dont backup files when writing.

now repeat the procedure for the whitelevel:

-Exif:WhiteLevel=2046

again the 2046 is the variable, click on ok, once both the whitelevel and black level have been changed to match the first file of the sequence, there should be no flickering what so ever, i dont believe ACR caused the flickering in the first place, as when i applied ACR adjustments, even to extreme cases, like -100 highlights, +100 shadows, etc, no flickering was caused what so ever

Not yet, but confirmed the bug. Seems to be caused by extreme overexposure in the high ISO (that is, very little overlap to match them properly).

ok thank you, may i ask if a fix is to be expected? i made the mistake on shooting a production in dual iso, even thought i tested it for a week still a new problem came about, and now i cannot continue it until this works, anyway i can help by any chance lol? researching seems to get me nowhere thought as im not a hacker or coder and cannot find any info on this either

but the thing that confuses me, shots, 0 and 1, compared to 2 and 3, are very similar, yet 0 and 1 dont process but 2 and 3 do

A1ex

bright dark detection error, iso blending didnt work

do you have any advice on that, i saw loads of pages back that you fixed it, but for your new version of cr2hdr 20 the error comes up

Hey guys, i got a problem, last few shoots were perfect, camera raw, no crop mode, with dual iso, processed with cr2hdr20 fine, no flickering, all perfect, now i had a 3 day shoot, and tried to process dual isos, got this error:

bright dark detection error, iso blending didnt work

has anyone had this problem before? what do i do

i also tried to process with the old cr2hdr, didnt have any problems with the above, but it did flicker which is unacceptable for this production

im uploading these dng files for you to diagnose if you can please, really confused why as some files processes fine, some dont, just with this cr2hdr20, but i need this one as this one doesnt cause flickering (with same levels parameter)


heres the files:
https://db.tt/VYeGuQoU

so just to recap:
cr2hdr.exe  processes all files fine but flickers
cr2hdr-20bit.exe  doesnt process many files and gives the error code: "bright dark detection error, iso blending didnt work"
the shortcut file is what you drag the dng files onto to use same levels parameter
M23-1529.000000  WONT PROCESS WITH 20bit
M23-1529.000001  WONT PROCESS WITH 20bit
M23-1529.000002  WILL PROCESS WITH 20bit
M23-1529.000003  WILL PROCESS WITH 20bit

trying your code now, compiled in after effects, rendering, and i get an error on frame 37, with an error:

After Effects error: Photoshop file format error (-30504).

( 45 :: 35 )

deleted the processed folder with your code, tried again, exact same result, gonna render 39 frame onwards

nope, seems all frames onward were corrupt, both times of processing, viewed all frames in adobe bridge, it was flickering every 2 frames or so, at extreme conditions, around 2 exposure steps id say, tried opening 39th frame on wards, photoshop cannot open, corrupt, with my previous code, no corruption, all files processed, however there was flickering still

So i believe i figured out how to run the exif tool same levels process, as the above method is too time consuming, HOWEVER BEFORE YOU READ ON, it seems to have made no exposure differences, and it still flickers, but the command that a1ex given me was executed and the files were reprocessed (I BELIEVE)



Heres the mini guide i wrote for myself, so you guys maybe can point out the mistakes:

so, go into windows explorer folder with the dual iso processed files with different levels that flicker, make sure exiftool.exe is in the same folder, whilst holding shift right click in the explorer window blank area > open command window here, right click at the top of the window > edit > paste:

exiftool M28-1423.000000.DNG -WhiteLevel -BlackLevel

M28-1423.000000.DNG is the variable, copy and paste the filename that has the most correct exposure of your sequence, then to insert the command in cmd, copy the command, right click on top of the cmd window > edit > paste, press enter, it will give you the white and black levels, take away the smaller number from the big one

now copy and paste this command into cmd

exiftool "-WhiteLevel+=27808" C:\0\8

the number 27808 is the first variable, which is the answer that you get when you take the small number from the large number, and the C:\0\8 is the location of the files that have different levels, processed dngs, press enter, and it will process all files making new files and renaming the original file extensions, once done you can delete the old renamed files.

seems like it didnt make any exposure changes at all, still flickering

Hey again guys, about exiftool, using it to even out the levels, i got the tool to read the levels of a reference image by:

exiftool IMG_1234.DNG -WhiteLevel -BlackLevel
White Level                     : 47752
Black Level                     : 2032

but im curious, about this:
exiftool *.DNG "-WhiteLevel<BlackLevel"
exiftool *.DNG "-WhiteLevel+=45720"

thats two lines of codes, also, how do i process the above code to a sequence file, is it done one by one? is there a way to do it for all files, as it done 1 line of code:
exiftool *.DNG "-WhiteLevel<BlackLevel"
said 1 file was processed
then the next line, same, 1 file processed




UPDATE:

i dont know why i didnt think of this sooner, i feel so silly now:

ok i finally got the solution, if youre limited to around 500 files (file path too long etc), make a folder with 1 character name in root of c drive, say 0, make each individual subfolders for everyclip extracted from your shoot, and within each folder, select all dng files, (DONT SELECT WAV), rename with one character say "1", windows will rename them in same order), this way it uses less characters, and now you will be able to process very long sequences

for running multiple instances, its best used when you have a shoot with many clips, so dont use the script, instead, run cr2hdr with same levels parameter, for every clip in the collection rather than for every frame, so this way you will still have many instances, utilizing the CPU, running for every clip rather than frame

i downloaded the version you just linked me to, and this one doesnt even let me type in anything, the only thing it lets me do is press enter which will reveal more information on exiftool, if i press the p character, it will display "Lines:", but if i type in numbers, any other characters, they wont come up, so i cant enter --help, with the version i originally had and the one you provided me with, i tried dragging and dropping in a DNG file, and it just gives me a list of file types, and at the end:
-- More -- Lines: 22814260000400

really seems confusing just to correct exposures for a sequence

hey again everyone, i been trying to find some guide for exiftool with no luck, can anyone point me to a guide or a discussion for it please? i dont understand how to use it or input commands or anything, i run the .exe, click and drag a single file or a sequence onto it, it shows up some text, then an
-- More  -- Lines:
with numbers at the end of lines, i cannot input text, only numbers, so i dont see how i am supposed to input the code that a1ex provided me to even out the levels to make the sequence "same levels" rather than using cr2hdr's same levels, so i can process sequenceses with 500+ frames,

also, the script for running multiple instances, now crashes every version of cr2hdr that is ran, does the script need to be updated for the latest version?

hope to hear some feedback

if it helps i can provide screenshot if needed of anything, just let me know what you need them off

if it helps, im using, windows 7 64bit ultimate, 5d mk3, mlv conversion using mystic PP with after effects

in acr process 2012, just below white balance, its exposure first, i was refering to that, im afraid im not as well educated as you guys, but as far as im seeing theres exposure, contrast, shadows, highlights, etc, i dont see a midtone option in acr, so yeah, i was refering to absolute exposure, but i guess its different with cr2hdr

what do you mean process a bright and dark image? do you basically mean the dual iso file? note the black/white levels printed, would they be printed as results for each dng processed individually in cr2hdr?

and nope, when i click and drag around 700+ files onto the cr2hdr, or the shortcut for it, it will give me the error, file name too long, im very sure youve come across that error as ive seen people post about it before in this forum, but i havent seen a solution, if you havent i can post a screenshot, so im still limited to around 500 files

oh and i think i understand some of what you said now, you say process a black and white level image, im sure you must mean a dual iso now, once that is process, cr2hdr will print on cmd the black and white levels on screen, right? and use this setting printed with the rest of the sequence using the script that runs multiple instances of cr2hdrm with the code a1ex posted?:
exiftool *.DNG "-WhiteLevel<BlackLevel"
exiftool *.DNG "-WhiteLevel+=50000"
just change the variable with the one printed in cmd?
however once again i dont know what to do with this code, where do i input it in, is it for the cr2hdr file? use it the same way as the --same-levels parameter? the only way i know how to run THAT parameter alone is single line, how would i input two line code in there

also you say use exiftool at the end, do you mean after the cr2hdr process? what is the purpose of this if the file has already been processed and ready for PP

isnt there a default exposure? like when you open with ACR its on 0, so i asume theres a default, am i wrong? if that is true, then is there a way to set on default= 0, or something like that, rather than the program auto adjusting it

im having a difficult time because i need to process around 700 frames sequence but i cant since it says the file path is too long, i am able to process 500, but what is the solution for this problem, does anybody know?

Thank you for your responce, just processed 100 files, seems the exposure is the same, but the luma changes, ill post process with after effects ACR now

When you have some free time could you please go over the complete messege i sent you above please, i think i highlight some points many other people would question and come across, especially high frame counts, (i cant process 600 for example using 1 process)

and thank you again for your batch processing advice, but i really dont understand what to do with those commands, any chance you could link me to a discussion, guide, or anything that would point me in the correct direction? do i still use cr2hdr and the script for multiple instances? where would i put in those parameters, in the script?

Hope you understand my ignorance in coding

oh wow, congrats a1ex, you fixed it, now i will try with the parameter same levels, in a batch convertion of 100 files from 0 upwards, hopefully it wont crash and no flickering, if all good, ill be very happy, well done dude, few notes and suggestions:

may i ask, what was the issue, did the screen shot help figure it out?

few days ago before i knew the cause of flickering i used the script for running multiple instances of cr2hdr, i asume it wont work since the same levels needs to be used within the initial single process, right? if thats the case, how about instead of using "same levels", we assing a specific variable to run with a parameter that sets the exposure, so this way each instance using the script would process the same level, speeding up the processing for video sequences greatly (hopefully its not something i missed in the forum)

the above i believe is necessary for longer sequences with many frames, if i try to click and drag even a 100 files, it will give me an error saying file path too long

also, how about putting a list of versions of cr2hdr in the very first post, i found the actual list of versions, but its the code only not the exe file, and im no where near a coder so i wouldnt know what to do with the code, im sure it would benefit many people

maybe theres a way to put the latest file in the first post? i gotta be honest it took me a few days to figure out the flickering cause, at first i found its ACR, shadow and highlight changes, then cr2hdr, i processed some NON dual iso sequences and there was no flickering what so ever, (even with process 2012 in acr), so i dont think its ACR issue, so yeah, would be useful for many people i think if the latest file was in the first post

big respects for your work and the speed of your fixes, just making suggestions for problems ive encountered as a regular user that im sure many other users would experience (finding the right information. i.e latest cr2hdr file)



NOTE FOR THOSE WHO DO NOT KNOW ABOUT RUNNING PARAMETERS, make a shortcut of the "cr2hdr-20bit.exe" file, right click on shortcut > properties, in the target, copy and paste  --same-levels at the end of the taget, if the target has spaces in the url, put " at the beginning of the url and at the end of it, for example:
"C:\camera raw dual iso converter\cr2hdr-20bit.exe"  --same-levels
putting this info here to save time for people who dont know (like me)

also do you know anyway of evening out the flickering in the dngs after processing them with the old cr2hdr that didnt have the same levels parameters

i removed it, the first page said it was optional, i tried it with it being in the same folder, same results, but i will try again and include it in the dropbox folder

update: yup, tried it with exiftool in same folder, same results as before with 20bit cr2hdr (crashes), but with  2014.01.23 version, converts correctly, added exit tool to folder: https://www.dropbox.com/sh/d5g3jlugmqqkjdl/8-fIwn3kRg

updated the folder with screenshots of the crash, versions of cr2hdr that crash and dont crash, and dcraw
https://www.dropbox.com/sh/d5g3jlugmqqkjdl/8-fIwn3kRg
i tried it on two computers, maybe im using wrong version of dcraw or something? im using the one from the first page of this forum topic
cant think of any other variables, hope you can give some advice as to what im doing wrong

here you go:
https://www.dropbox.com/sh/d5g3jlugmqqkjdl/8-fIwn3kRg

Hey guys, ive been going crazy here, i been trying to use the latest: cr2hdr-20bit.exe a1ex has provided, it is stored in "C:\0" along side dcraw.exe and exiftool.exe files in the same folder, some dual iso dng files process fine, but then i get to a certain file and it cause cr2hdr-20bit.exe to crash forcing me to click the close program button, it is not just one video, its many, it works completely fine with older versions of cr2hdr, like the 2013.10.04 version, also 2014.01.23, but they dont have the "same levels" parameter options that i need to keep the sequence flicker free. i found other versions of dcraw, exiftool, replaced them, same thing, so im assuming its cr2hdr.exe file, or something wrong with me, i even tried on another computer, rebooting it, cant think of anything else, i shot another video, same thing, it will crash on certain frames, im very sure the frames are fine as they have the same dng file size as its neighbouring files and they open fine in photoshop, bridge, etc, tried running with the --same-levels parameters initially, same results if i clicked and dragged dng files onto the original exe, or the shortcut with the parameters, tried individual files, all the same, tried redownloading your latest cr2hdr file, same

Hope to hear something back because im lost, i dont understand why this version crashes, am i the only one?