Messages

At first I was not sure it worked till after I used RAW2DNG on the RAW then I dragged the DNG's onto the CR2HDR.exe and it modified the interlaced ones correctly.

Now one can process dual iso video just with new raw2dng. It combines dual exposures automatically right from raw file and gives the ready dng's at output.
Check the first post in this thread: http://www.magiclantern.fm/forum/index.php?topic=7139.0
There is a link to the latest raw2dng at the postprocessing section.

Guys, I can't find where to download the cr2hdr.exe from

http://www.magiclantern.fm/forum/index.php?topic=7139.0

Yes, it works. Congratulations, brotherhood! )

Examples below are from my first extreme test. Exposure pushed up in ACR all the way up to +5 f-stops.
First crop is from usual iso 100 cr2, second from dual iso 100-1600 dng processed with cr2hdr.exe



(exactly the same settings for both, no any noise reduction)

mixer2, thank you. So much useful info.

there isn't any algorithm that checks, if it should fix the dot, or something like that.

Got it. Figured that out already, studying the source

there will be a better algorithm for interpolation in the next version which should lead to much less artifacts

That would be great, we'll be looking forward to that. Guys you rock!

By the way, mixer2, which IDE you'd recommend for java development?

Dual ISO works only in photo mode on 5d2. HDR video is different matter.

Anyway, if you are interested in HDR video workflows, you should read the Post-processibg thread: http://www.magiclantern.fm/forum/index.php?board=14.0

Also, use search on the forum, it gives at least 80 results by "hdr workflow" request.

In general, you should split the flickering video into two streams: high and low exposure, then combine them using different blending modes or combining them into real hdr's. You can achieve it by different ways. Manually in After Effects, using Photomatix, scripts for VirtalDub etc.

http://www.youtube.com/watch?v=hC4AbMwpKWo&feature=youtu.be

see what exactly i mean

Oh, man, maybe you just got HDR video enabled? ))

I have been able to manage to record 1728x648 for 60 frames instead of 24.

I've just got 58 frames 1728x692 @23.976 fps

Foorgol, I have a question:

Using PDR tool in interpolate mode gives an overall good results (it eliminates the consistent pink dots around high contrast edges, which set dead pixel method can't do), but it produces another problem: pronounced somewhat random colorful artifacts in detailed contrasty areas, such this:


Let's say I can live with some quality loss, if so, is there any simple method to interpolate those things hell of a lot? I mean, turn off that judgement algorithm, you've been talking earlier ( http://www.magiclantern.fm/forum/index.php?topic=6658.msg55325#msg55325 ), and just interpolate all of them?
Should I change something in dotData files for example? Or, if there's no way to do this from dotData files, wouldn't it be a good idea to integrate some option in your program, like slider gives a user a possibility to determine how sensitive this decision algorithm is?

EDIT: The positions of these artifacts are not random of course, they belong the same grid. It seems like just something is wrong with the interpolation method. Watching carefully to particular dot, shows that when surrounding is smooth, it interpolates fine, but when the surrounding is some kind of an edge, then fancy colors appears: sometimes green, sometimes magenta or yellow etc. for the same dot.

May be this is something to do with the "finding the minimum gradient" in your PinkDotRemover.java source.
I'd like to dig in and experiment with that, but I need some help: can you guys please point me to the resources on how to build from java?

I just want to make sure you have seen this
https://bitbucket.org/hudson/magic-lantern/pull-request/184/700d-650d-remove-pink-dots-from-raw/diff

So maybe there is no need for integrate the pinkdotremover.  (ATM except EOS M)

That method doesn't work, so 650d users still need the Pink Dot Remover tool. It would be great to implement it in Batchelor.

Use RAW_TYPE 78 or 99

I missed the focus points in 14

These raw_types acts exactly the same (at least for 650D).

Pink dot remover tool gives better results for now.
First crop below shot with older build, cleaned up with pink dot remover tool and processed with ACR.
Second crop was made with RAW_TYPE 78 and then processed with ACR.
As you can see, in the case of using raw_types ACR has to interpolate not only the focusing pixels, but also that green pattern all over the frame, causing the black spot appears like a whole mess of green-magenta stuff. First picture is much cleaner. (I use the mosaic engineering vaf filter, so there's no place to aliasing and moire at these examples, and first one in video looks acceptable and usable, but second is not).

Well, I don't think these raw_type manipulations are exactly the Solution. Pink dots around high contrast edges are still there.
I mean, this method doesn't excludes the focusing pixels from raw stream, it just adds correct hot/dead pixel info, so we can chose whatever soft we want to deal with them. Right?

Also, TheUnknOwn said, that "With raw_type 14 you don't get any image anomalies using Adobe software". Anyone can confirm that? In my experience, when i change the string in raw.c to #define PREFERRED_RAW_TYPE 14, compile and process with ACR, i see the same pink-green artifacts around high contrast edges:

Guys, may I ask you please to share a build with RAW_TYPE 14. I compiled it by myself, but I cant see any difference: the pink dots pattern is the same. May be i'm doing something wrong.

Windows version is unstable by now, it sometimes outputs less frames than raw file consists of (with no compression option selected), sometimes there is some kind of tearing on several frames
(it looks even like a wrong frame numbering on playback)

Is there anybody who tried mosaic engineering filters on 550d?
Or at least anybody who heard anything about such dare people?
Some information at all? O_o

Can anyone comment on what is reasonably usable resolution wise on the 550d, say around 10 seconds. I understand that max continuous resolution is 960x540, is this really comparable sharpness and resolution wise to the 1080 h264, would those of you that have used and compared it opt for the 550 RAW over the h264?

I am considering shooting a project in RAW and could probably manage with 10-12 second bursts, what are we looking at roughly, for a 2.35 or 16x9 finish, i was thinking 1200x500 maybe?

1200x500 is ok for 500+ frames = 21 sec at 24 fps

I believe you installed it wrong. Look at the website for instructions. You are supposed to enter LV mode, and then put it in.

I've re-checked and verified every step i did of cause.
Somewhere in my mind there is a small glint of info, that there were some similar problem discussed, the author states that vaf txi filter works perfectly with canon 600d but gives an error with 550d, but i believe, nobody solved that situation.

Now i wonder, are there any successful examples of installation this filter on 550d AT ALL? ))
I'm searching the web for this info, but no results yet. That's strange.

Oh by the way, i've tested it on two different bodies, and i've got a couple of random successful attempts with one of them... It just worked for a moment. After the camera turning on, shutter pops and there were no error, shot some test, turned it off, and then the problem comes back.

Recieved the Mosaic Engineering VAF_TXi filter recently. Installed on my 550d, but when switching on or activating LV shutter pops and gives me an Err 20.
Anyone had the same problem with t2i?

Recieved one Vaf-Txi filter recently. It fits perfectly, but that's the only good news ))
When switching on / entering LV mode, shutter pops, camera gives me an Err 20 and stops.

Has anyone the same experience with 550d and vaf-txi ?

@rewind: it is useful if the fork you compiled will be fused into unified with on-off menu options: do you know if the author will make a pull request and with the necessary on-off menu functions?

I can't see it in pull requests, but i'm not sure, i'm not really understand the structure of branches and how the work organized in general. So now what i'm doing here is just searching for good stuff and compile it for myself )

I build the raw_rec module from pravdomil's source:
https://bitbucket.org/pravdomil/magic-lantern-hack/commits/all

Raw_rec has some tasty features like black bars and auto global draw off while recording.
It looks like this now on my 550d:

Nice, huh?
I've noticed a tiny but consistent frame count increase with this. For example, with my previous build i've got about 500–510 frames with 1200x496 at 24 fps, now i'm getting 550-570.

Also, there is a small present for those of you, who dare enough to shoot the tv works on 550d — nice 3X4 cropmark, useful for PAL world )

Other stuff is from unified.
You can try my ML set here.

Notice: I have removed a large set of resolutions (useless for my works), and added 1200 and 1.42:1
This build also includes ETTR, file_man, pic_view.
See this thread if you are interested.

Recently got a 500d at a great deal from a friend. Just wondering, how can I enable raw video? I've installed tragic lantern on a 600d before but I can't seem to find modules that work for a 500d.

Watch this and you will can easily build it for yourself. Also there was a ready-made build from mk11174, you may ask him personally. 

Hmm, I own a t2i/550d and it barely chugs along at 1088x488 with 2:51:1 aspect ratio, so in short: I highly doubt it, sorry.

Oh, come on, man! We are getting at least 1200x496 (2.4:1) stable for more than 20 secs, that's enough for almost any film cut, so we are already filming our works with 2ti's ))
By the way, 500d can get more buffer memory at this stage of development, so you can get more frames with 500d )

It seems that latest "small hacks" doesn't work on 550d, right?
This option gives me an error at 0. expected e3a00032, got 100
should we completely disable it in our builds?

Oh boy! ))
Just change your comp settings to 48 fps, then apply twixtor with input framerate 24, and speed 100%.
That's all you actually have to do ))

Try to check the option to tolerate frame skipping, and tell me the results: only one frame lost every 10 or 36 seconds shouldn't be noticeable at all ! Let me know !

It is obviously enough, with this buffering strategy, you will get a whole bunch of skipped frames after the first one