Messages

Barracuda is only a gui for the original cr2hdr command line, but you're welcome ;-)

Hello mrd777,

When you take a dual_iso picture, can you see some banding? Does the picture look weird to you? If so, camera wise, you're doing it right. If so, let's get on the Barracuda software.

Use the BarracudaGUI.exe with the "attached" cr2hdr.exe and dcraw.exe in the same folder. Then simply run barracuda, you get a DNG file and then it's up to the Light Room or Photoshop to give it that extra punch in color, that's basically it.

Edit: Oh, and if you are using ETTR, try dual_iso module with it off, sometimes for some reason, it equals the ISO values for ex. 100/100 = 0 DR 

[big]

hi guys,

Don't know if this is the appropriate topic but, I would like to share a dual_iso picture just to show one of the big advantages of using the dual_iso module.

Kitty scratching in HDR! May be plain to some, I loved the final result!

http://imagizer.imageshack.us/v2/1600x1200q90/32/hqp8.jpg

And if you ever want to boot the camera without having ML run whilst it's still on the card, then just hold down the "ok" button when switching camera on.

"ok" or "set" 

Doesn't the warranty (in MOST cases) only analyze the product hardware-wise rather than if it was "tampered" with software, I mean, ML isn't even a Firmware per say and not some kind of hack, it's more like a "Original Firmware Unlocker" or "Firmware Add-on" if you will...

Just curious about how Canon support will act upon a situation where it is detected a 3rd party bootflag on the camera.

[my]

Tried the latest build and here are my conclusions:

Good news:
shoot_malloc already has memory allocated, don't know if it's associated in any way but hey... It doesn't freeze anymore when we shut down the camera!

Bad news:
Screenshot does freeze the camera (hence the picture taken with my phone).
Memory benchmark still gives the "malloc error "



A thanks to alex in any case for partially solving this issue which, for me, was a great step for stability

If shoot malloc is used=0 then it's going to crash, at least, happened with me every time.

#drumrolling. ;-) fingers crossed

I'm not at home atm but if 47crows or somebody who also has these problems could post the error ide be thankful. It's weird that it's only happening to the both of us, that I know of. :-)

Yes, still hangs with zero modules loaded and if you record a video there shall be the white pixel flashing too. Screenshot function hangs as well.

Yup! Same with me, exactly the same... The shoot_malloc on these later builds don't have any data allocated, don't know if this helps but it's one of the ways I can promptly detect that it's going to hang.

Tried again the latest build for the benefit of a doubt but... It hangs, freezes the display when I turn off the camera, shoot_malloc block value is zero, as I mentioned before, same ol' same ol', back to older build (01.02.14), for now...

1) Sorry, thought it was you who launched the good news, my bad. 2) Not rushing anything, a rushed code is a dead one.
3) You are right, sorry for the off-topic, just trying to make some convo while 47Crows gives us a screenshot.

Must be careful trying to be nice next time...

Hello! How's the raw video module coming up Alex? :-)

Sure should, at least for now until the devs start debugging and find what's up with the new builds. Shouldn't be long though... Although it's Friday so they must be recharging their coding juice ;-)

47Crows, exactly what happened to me with other builds and with that nightly so...  Back to the old version for me again :-(  something went terribly wrong from Feb 9th and up,  more or less...

Even now that it's working? Only the benchmark doesn't work. But I can upload it. No problem ;-)

"Patience and Precision are a gift given only to some..."

Great video!! Congrats!! 

[Edit:]

Okay then, in an attempt of being some what productive, I can say that the Nightly build from February 1st down, doesn't freeze anymore. So, these problems may occur on more recent Nightlys! I'm staying with this one for the time being, startup even seems snappier and the whole "messing around" seems more stable! 

Interesting facts:
.shoot_malloc now has 1 block and detects memory
.benchmark still shows shoot_malloc error (but who cares now that it won't hang anymore? still a fact though)
.screenshot works (yeeey)
.no freezes when I turn the camera off (got so happy I jumped up and "woohooed!")
.movie mode that I used was CBR @ 1.7x with a Cinema "effect" FPS @ 23.976 
Video test can be viewed here: http://www.youtube.com/watch?v=BRTPvZpHd1M&feature=youtu.be



Feast your eyes on ye' screen shot! arrg! 

Edit: AND ... No flickering white pixel of death in movie! FWPOD be gone!! 

PS: Thanks for everybodys Help! ML Back online for me! 

Woaah! Dual ISO all the way! Excelente work! Love the concept, am blown away by the results! ;-)

Sorry alex,  felt that it kinda got lost in the middle there amongst other topics. 4x is a charme, sorry for the flood.

I second this! :-D but it may be hard, even by lining up a row of focus points, idk! Let's see what the devs have to say ;-)

Okay, I'll analyze carefully my silly me ideas next time ;-)  anyway, I'll go back a few months and check if I can find the nightly culprit ;-)  i have to ask this again, sorry, white pixel flickering using cbr movie method, anyone else?

Taken 2 exposures 4 EV apart and called it a day.

LOL! Good one Audionut... I have no argument to counter attack on that one!!     

But, wouldn't it be nice to have a preview? It was just an idea 

Thanks for the tip dmilligan!  Will do!

How far should I go back? January? I'll try later on then and see if I can find which Nightly is the culprit, I'm just amazed that it only happens with me