Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - janvkem

#1
Thanks for the reply, going to implement this into my workflow!
#2
Looking good DeafEyeJedi! Do you create the darkframe by shooting (with the same settings) with the lenscap attached? Can you do it anytime after the shot (like when i go on holiday and i make the darkframes when i come back home) or does it have to be close together in time? For windows users mlv_dump can do this right?

Quote (with pics removed):
Quote from: DeafEyeJedi on May 11, 2017, 07:54:00 AM
Some fun stuff w DarkFraming Avg Process in 12-bit lossless @ ISO 6400 from 5D3.123 shot w Helios 44-2.

Cinelog_Rec709 has been applied for comparison viewing purpose. Full album can be found here: https://flic.kr/s/aHskVk85io

Such a relief that @bouncyball, @Danne, @g3gg0 and the rest of you all have made this possible to bring back this useful feature in DarkFraming Average Processing. Especially for lossless.

Yes, all of this was solely done with the latest and greatest cr2hdr.app (Thanks @Danne for standing by with all of your love & support!)
#3
Quote from: goldenchild9to5 on April 08, 2017, 04:18:37 AM
@a1ex What if you don't know how to run that script.. Can you point me to a detailed instruction on how to run that code, would be greatly appreciated. 

This is what I just did to test it (for Windows):
1. Install python for your computer: https://www.python.org/downloads/
2. Make sure to check add python x.x to PATH
3. Make a backup of your current camera's ROM (using magic lantern)
3. When done make a new folder and copy your ROM1.bin to that folder (i made E:/tmp)
4. In the same folder make a new .txt file and rename it to testrom.py --> make sure you have file extensions visible
5. Open the file in your favorite text editor (i like notepad++) and copy the code in a1ex's post
6. Open a command window in the folder you just created (press right click on the folder while holding shift key, select Open command window here and type this:

    py testrom.py ROM1.bin

7. Read and follow the output on your screen.
#4
Quote from: a1ex on April 01, 2017, 05:02:05 PM
Can you share your settings directory, so I can try to reproduce?

Sorry, my bad. Checked again with a completely fresh card (other test was just with deleting the ML folder and autoexec.bin file) and issue appears to be gone. I had 2 additional files on the card but cannot recall the names (removed them before I saw your post unfortunately)... My apologies for the incorrect information.
#5
Great to see this getting along! Just tested and the DNG files are ~2.3 MB each whereas they normally are ~3.5 MB (1920x1080), so ~65% compression! It seems that there is still some bug inside however: When I record it crashes after a couple of seconds. There is an MLV file created on the card. Inspecting it on my pc showed roughly a double size of the MLV file compared to the extracted DNG files (819 MB for the MLV file and 387 MB for the extracted DNG files).
#6
Installed magiclantern-crop3x.2017Mar21.5D3113 and all seems to work (only checked briefly). Thanks a lot for combining it with the 10 bit recording! I really like the pre rec option!
#7
User Introduction / Hello!
February 13, 2017, 08:53:24 PM
Hi all,

After lurking around on this forum for quite some time I think it is appropriate to introduce myself. I have been shooting video's mainly on holiday using my 7D (underwater) and recently upgraded to a 5DIII (underwater housing on the way :) ). Really looking forward to find out all the possibilities of this camera with ML installed. Thanks for all the effort so far!

Jan
#8
Great feature! Excellent for unpredictable action. Am I impolite if I'd ask for a 10-bit capable version?  :)
#9
Quote from: dfort on December 10, 2016, 04:15:13 AM
Sure--check the first page of that document I pointed out.

QuoteWould you trade half of vertical resolution for 3 stops of extra dynamic range?

Many people believe that dual_iso is something that should be on all the time and some people that only shoot stills do in fact use it almost all the time. It does seem to work miracles but there is a loss in resolution. When you are shooting video your vertical resolution is less than 1/3 of the resolution for stills so the loss is more noticeable. Here's a sample that was shot a few years ago by MA Visuals:

I've seen dual iso video samples that show extreme aliasing but of course I can't find them now.

So the resolution loss percentage wise is equal in still and video, but the effective loss in sharpness is greater in video as you have lower resolution. If I understood correctly the loss in resolution is only apparent in highlights/shadows. If i look at the video you posted i mainly see losses in sharpness in the dark areas. Mid tones should hardly loose resolution is that correct?
#10
I am currently reading up on ML on 5DMKIII as I'm thinking about upgrading my 7D especially for the improved video and low light options of the 5DMKIII and found this post interesting to read. The remark given by dfort is not really clear to me.

Quote from: dfort on November 26, 2016, 08:17:40 AM
Dual ISO is great for shooting stills at the full resolution of the sensor. Using it with 1920x1080 video -- not so much. You're sacrificing vertical resolution for increased dynamic range. I'd recommend reading this technical paper on dual iso:

http://acoutts.com/a1ex/dual_iso.pdf


dfort, could you elaborate on your statement? I don't see anywhere mentioned in the article that there is a difference between stills and video in the way of taking data from sensor. Isn't it just that a smaller area of the sensor is sampled in video mode and that the relative loss in resolution is the same for video and stills? What I understood from the pdf is that the gain in dynamic range is independent of the sampling resolution. Only possible impact i see is that sharpness might go down due to the interpolation that is applied.