Magic Lantern Forum
Developing Magic Lantern => Modules Development => Topic started by: a1ex on July 01, 2014, 05:11:15 PM
-
Update: now available in the nightly builds! (http://www.magiclantern.fm/forum/index.php?topic=12523.msg143510#msg143510)
Another pipe dream came true :)
- are you afraid to waste shutter clicks on timelapse or focus stacks?
- do you need to take pictures in quiet environments?
- do you have problems with mirror vibration (e.g. at very long focal lengths)?
- your shutter is worn out so badly that you can no longer take pictures (ERR20)?
- old silent picture mode's resolution was too low for these tasks?
I believe I've just found the solution to all of the above.
(http://a1ex.magiclantern.fm/bleeding-edge/silent-fullres.png)
How it works?
I've tried to call a factory test routine: FA_CaptureTestImage (helped by FA_CreateTestImage and FA_DeleteTestImage). At first sight, it did not do anything visible (g3gg0 already tried it years ago), but the diagnostic log and the EDMAC info box revealed the magic: the sensor was sampled at full resolution, without shutter actuation!
So, to take an useful image, I went to LiveView first to open the shutter and raise the mirror, then I've paused LiveView (from ML powersave routines, or by going to PLAY mode or Canon menu from LiveView). Then I've called the above routines, and after that, all I had to do was to fill the raw_info structure and save the DNG.
If you call these routines without going to LiveView first, the result will be a dark frame (interesting for astro - you can take 300 dark frames without wearing the shutter mechanism).
For more details, take a look at this changeset (https://bitbucket.org/hudson/magic-lantern/commits/3d88b92ca1d7).
Limitations
- The fastest shutter speed I've got is around 1/10 seconds (very rough estimation by comparing brightness from a regular picture). With regular pictures, faster speeds are done via mechanical shutter actuation.
- Long exposures are fine up to 15 seconds (longer exposures will crash the camera).
- Fastest capture speed: 220ms on 5D3, 320ms on 5D2. This includes a dummy readout, which is probably a bias frame.
- So, at least for now, the usefulness is limited to timelapse and medium-long exposures (no moving subjects).
- If you use the intervalometer, I recommend taking a picture every 10 or 15 seconds (not faster). Saving DNGs from the camera is slow.
- In photo mode, aperture will be most likely wide open, regardless of the setting, because of exposure simulation (enable Expo Override to fix it).
4K video?
Too early to ask. Find a way to speed up the capture process first (see the research section below).
However, I don't really expect more than 10 fps (in LV crop mode on 5D3, 1/3.6 of the total sensor area is sampled at 30fps). If you implement a burst mode from the current code base, you'll get up to 5 fps.
Is it safe?
You'll have to judge yourself; I'll just give you some details.
- I've discovered this the day before yesterday
- I took less than 100 pictures, on 4 different cameras (5D3, 5D2, 550D and 60D)
- The functions I'm calling were meant for factory testing (see these comments from silent.c (https://bitbucket.org/hudson/magic-lantern/commits/3d88b92ca1d734fa5ab0914f5b1639b858aac1e3#Lmodules/silent/silent.cT679) for some details on what they do)
- The functions I'm calling will change some properties back and forth, e.g. PROP_FA_ADJUST_FLAG (you know, properties are usually persistent settings, and a mistake there may soft-brick the camera)
- The sensor is sampled in the same way as in photo mode, just without mechanical shutter actuation
- I won't include it in the nightly builds at this stage; early adopters will have to compile it themselves.
How do I install it?
Download the latest nightly build and enable silent.mo.
Research
- log file from 5D2: FA_CaptureTestImage.log (http://a1ex.magiclantern.fm/bleeding-edge/FA_CaptureTestImage.log)
- some of my experiments on 5D2: http://pastebin.com/6Lyhrqtj
- http://magiclantern.wikia.com/wiki/ADTG
- http://magiclantern.wikia.com/wiki/Register_Map
- How does the camera take a picture? (http://www.magiclantern.fm/forum/index.php?topic=1915)
- ADTG registers thread (http://www.magiclantern.fm/forum/index.php?topic=6751) and classic adtg_gui (http://www.magiclantern.fm/forum/index.php?topic=6751.msg71720;topicseen#msg71720)
- enhanced adtg_gui (https://bitbucket.org/hudson/magic-lantern/src/iso-research/modules/adtg_gui/) from the iso-research (https://bitbucket.org/hudson/magic-lantern/branch/iso-research) branch
- analyze Canon debug messages with the code from the dm-spy-experiments (https://bitbucket.org/hudson/magic-lantern/branch/dm-spy-experiments) branch
- figure out how to speed up the capture process (maybe without the dummy capture step, or find out how to trigger the continuous readout mode)
- figure out how to get fast shutter speeds, as in LiveView (electronic shutter)
- implement a fast bracketing, exposure stacking or other funky capture modes
- compare the dynamic range with regular photo mode, with raw_diag (check the ISO research thread (http://www.magiclantern.fm/forum/index.php?topic=10111))
- don't burn your sensor ;)
Please do not ask for builds in this thread. This thread is for development related feedback only.
If you would like a build compiled, so you can help the Magic Lantern development team by testing this feature and providing feedback, please see this thread (http://www.magiclantern.fm/forum/index.php?topic=12608.0).
-
Chapeau!
-
You're an animal! It will be interesting to watch as it progresses. Congrats!
-
GREATEST THING SINCE RAW VIDEO! so fucking awesome man, you're awesome! :')
-
a1ex, thanks for your awesome work !
4K silent timelapse ? :) why not :)
We can put captured frames in mlv container to avoid DNG processing on camera.
-
(...)
If you call these routines without going to LiveView first, the result will be a dark frame (interesting for astro - you can take 300 dark frames without wearing the shutter mechanism).
Very nice. ;D
(...)
Limitations
- The fastest shutter speed I've got is around 1/10 seconds (very rough estimation by comparing brightness from a regular picture). With regular pictures, faster speeds are done via mechanical shutter actuation.
- Long exposures are fine up to 15 seconds (longer exposures will crash the camera).
(...)
So it is a solution for time-lapses, not really for astronomy (15s is a bit short), for the moment.
BTW I'm pretty sure that it is possible to get same params than a regular picture (exposure duration etc.), because the Canon LX NR do it (we can do 15mn dark frame for ex.). The question is 'will it be possible in LV'..
-
A1ex, awesome work!
@marekk: Yea, that would be great and perfect for the Workflow!
-
Thank you so much A1ex!!
-
@marekk: Yea, that would be great and perfect for the Workflow!
[/quote]
Of course. Or full res!
-
5K VIDEO, HERE WE COME!!!!
-
Awesome news! I look forward to seeing where this could be taken!
-
Wow! Thanks so much, A1ex!
-
Will this work for the 50D? Is there a module I can install to try it out?
-
Congrats! :)
-
Wow :D!
-
Great find!
-
500D :
(http://s30.postimg.org/87yrz4p69/VRAM1.png)
Thanks A1ex! :D
-
awesome! Once this allows faster shutter speeds it will become even more fun to experminet with. I could think of some useful cases in conjunction with flash to bypass some restritions with flash sync speed...
-
I could think of some useful cases in conjunction with flash to bypass some restritions with flash sync speed...
This is not possible. Try to video mode, shoot one frame using the flash.
-
Amazing :D
-
April fools!
-
Works fine on 550D here
(http://savepic.ru/5237567.jpg)
(http://savepic.ru/5222207.jpg)
-
I want your brain, A1ex. 8)
-
DAMN!!! Gr8 find a1ex!
-
Canon 5D Mark III Mirrorless Edition :)
-
Respect, Alex, nice findings!
-
Just dreaming... ;D
Is pixelbinning a CPU heavy task ?
Could this lead to a "no more line skipping" video mode (realtime pixelbinning from full res picture readout), or are there boundaries in CPU and memory resources available in camera?
-
I believe binning is hardwired directly on the CMOS chip (here's a hint from Chipworks (http://www.chipworks.com/en/technical-competitive-analysis/resources/blog/full-frame-dslr-cameras-canon-stays-the-course/), which seems to agree with my experiments).
If you would do it in software, I expect several seconds for one image.
-
I believe binning is hardwired directly on the CMOS chip (here's a hint from Chipworks (http://www.chipworks.com/en/technical-competitive-analysis/resources/blog/full-frame-dslr-cameras-canon-stays-the-course/), which seems to agree with my experiments).
If you would do it in software, I expect several seconds for one image.
Too bad... :(
Had some little hope that the better video performance(no line skipping) in the 5d3 could be copied to other camera's in the canon range.
But it looks like the 5d3 has a sensor with different readout options then the other canon camera's.
But, damn! What a cool finding 8) for shutterless time-lapses!
-
To compare the sensor configuration from LiveView vs silent mode, you can follow these steps with adtg_gui:
step 0: movie mode, manual exposure (optional FPS override, depending on camera)
step 1: enable Debug -> ADTG registers
step 2: turn on and off LiveView a few times (and remain in LiveView)
step 3: select "Show: Modified from now on" in adtg_gui menu
step 4: select "Advanced -> Disable logging: in LiveView" (so, from now on it will record only changes from photo mode, including full-res silent pics)
step 5: take a full-res silent pic
step 6: go back into adtg gui menu, and you'll se register differences on the ADTG/CMOS/DFE side
step 7: select "Log registers now" to get this log (http://a1ex.magiclantern.fm/bleeding-edge/lv-vs-silent.log)
In the log, which matches what you have seen in menu at step 6, 0001 is ADTG1, 0002 is ADTG2, 00f0 is CMOS and f000 is DFE (that's the internal coding).
The "was" part is liveview, and the number before that is for the silent photo.
-
500D, averaged 100 black frames (+5 EV and shadows/whites) :
http://s15.postimg.org/9gbedu0ih/100.jpg
-
I wish this could work in bolt trigger module, I only need 1 picture recorded when strike is detected, but is it even possible to make use of the detection method with this way of doing it? I think it works by using a ring buffer till a white level in the live view is changed which forces a save on that frame. Seems like if it can just loop 2 frames maybe that would be enough time to save just the frame at pixel change, then that would mean full res day time lightning pictures, that would be so cool!
-
Just thinking, silent full resolution picture mode is probably also used by Canon to (re)map hot/dead pixels...
The manual sensor cleaning with the body cap on the camera instead of lens.
-
I wish this could work in bolt trigger module, I only need 1 picture recorded when strike is detected, but is it even possible to make use of the detection method with this way of doing it? I think it works by using a ring buffer till a white level in the live view is changed which forces a save on that frame.
Yes, just call FA_CaptureTestImage in a loop, and whenever lightning (or motion) is detected, save the raw file. Ring buffer is not necessary, but it may let you do some cool tricks, like also saving the frame before the event. You can allocate only 2 or 3 buffers at a time anyway.
Minor detail: you might (or might not) have to call Create/DeleteTestImage (didn't try), but these are very fast.
To detect the lighting, I suggest polling raw_hist_get_percentile_level(95%) - when the value gets way above average, save the file. Should be fast enough, and easy to call.
Would be cool to have a full-res LiveView mode and keep compatibility with existing tools (raw recorders, motion detection and so on), but it's probably a little hard, need to think about it. But adding some simple motion detection to the silent picture module should be easy.
-
Great find, a1ex and this is definitely a step closer in convincing my bosses to allow me install Magic Lantern on all of our 5D3's at work...
Since the shutter can be loud and annoying during studio recording and I've already been using the silent pic mode on my personal 5D3 as well as the 7D from work...
Keep up the good work, a1ex!
-
Memory discussion moved here: http://www.magiclantern.fm/forum/index.php?topic=12528.0
(let's keep this thread about silent pictures)
-
Whoa! Amazing!
Is this available in the newest 5dMKII nightly/alpha build? Or is it coming up in a future build?
-
You may want to read the first post by a1ex.
-
Working on the 700D, cam was set to 2" for shutter speed.
(http://s4.postimg.org/cg1z1dv65/VRAM0.jpg)
-
Electronic shutter do gradient few examples :
(shutter speed Canon menu)
(http://s8.postimg.cc/ptta0eh51/image.jpg)
(http://s8.postimg.cc/ra4sijk1x/image.jpg)
(http://s8.postimg.cc/nrxdzw8jp/image.jpg)
(http://s8.postimg.cc/ci4o4y3id/image.jpg)
(http://s8.postimg.cc/gd827imo5/image.jpg)
(http://s8.postimg.cc/5g6qiqzwl/image.jpg)
-
Cool find :D
This means the exposure probably starts at the same time for all rows, but finishes sooner for top rows and later for bottom rows. In LiveView, the exposure starts early for top rows and it's delayed for bottom rows, so each row gets the same amount of light.
Right now I have no idea how to change this behavior though (is it enough to tweak some ADTG registers? some other stuff to do?)
(btw, can you process the images with same overall exposure - that is, darken the last images a bit - to see the gradient better?)
-
Quick analysis of the gradient:
I took a regular picture at 1/4 seconds, and compared it to a silent picture, with shutter set to 1/8000. 5D2, no lens (totally defocused), ISO 100.
Script used for taking the pictures: dont-click-me.c (http://a1ex.magiclantern.fm/bleeding-edge/gradient/dont-click-me.c)
The test images: regular.CR2 (http://a1ex.magiclantern.fm/bleeding-edge/gradient/regular.CR2) and silent.DNG (http://a1ex.magiclantern.fm/bleeding-edge/gradient/silent.DNG) (warning: large files)
Since the test images were taken from the same static scene, same ISO, same aperture, I should be able to plot the exposure difference and figure out the shutter speed from there, right?
So, I've loaded the two images in octave, and wrote this script for analysing them: gradient.m (http://a1ex.magiclantern.fm/bleeding-edge/gradient/gradient.m)
Results:
Images in linear space, brightness scaled to fit the entire range (0-255):
(http://a1ex.magiclantern.fm/bleeding-edge/gradient/regular.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/silent.png)
Images in log space (EV), brightness scaled:
(http://a1ex.magiclantern.fm/bleeding-edge/gradient/regular-ev.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/silent-ev.png)
Image difference in log space (EV), brightness scaled:
(http://a1ex.magiclantern.fm/bleeding-edge/gradient/expo-delta.png)
Exposure difference per row, in EV (left) and linear (right):
(http://a1ex.magiclantern.fm/bleeding-edge/gradient/row_exposure.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/row_exposure_time.png)
Numerical results:
Exposure range : 1/59.97 ... 1/3.86
Rolling shutter : 0.24 seconds
Not exactly ideal for moving subjects, even if we find a way to fix the gradient. But it could be interesting as a fast slit-scan mode.
You are welcome to run these scripts on more cameras, and post the results. I expect a little less rolling shutter from 5D3.
edit: this rolling shutter value was actually expected - in LiveView, Samuel H measured a rolling shutter of 25.9ms on 5D2 (http://www.dvxuser.com/V6/showthread.php?303559-Measuring-rolling-shutter-put-a-number-on-this-issue), and here it's reading out 9x as many pixels.
-
Heh, so we almost got ourselves a complete GND filter effect in ML, after all. If only the strength of the effect and the start/end points were adjustable. :-)
-
The strength is adjustable, but only by adding a constant to the total exposure time (the exposure difference between the top row and the bottom row will be fixed to 0.24 seconds on 5D2, with linear time variation).
It might be possible to slow it down by tweaking timer A during exposure (didn't try, but worth researching). From FPS override, you already know that increasing timer A will increase the rolling shutter effect.
-
Awesome job a1ex! Could this function work together with ettr + deflicker + advanced intervalometer module too?
-
Amazing A1ex !!!!
-
I see no problem in this gradient for use on landscape photos/time-lapses :D
-
@a1ex je ne sais pas comment compiler ces modules . peut-tu le faire pour moi stp ? je veut tester ça .. Canon 5d mark III 1.2.3
-
@a1ex je ne sais pas comment compiler ces modules . peut-tu le faire pour moi stp ? je veut tester ça .. Canon 5d mark III 1.2.3
Il a dit que nous devrons attendre pour ceux qui savent comment la faire de completer leurs tests :(
-
Any status update about the process? I would like to try out on my 700D
-
Want to try it on your camera heres how.....
- I won't include it in the nightly builds at this stage; early adopters will have to compile it themselves.
How do I install it?
Compile ML (both core and silent.mo) from the fullres-silent-pics (https://bitbucket.org/hudson/magic-lantern/branch/fullres-silent-pics) branch. For 5D3-123, merge the two branches locally first.
If you get a compile error in raw.c, see the porting notes below, find the missing values for your camera, and submit a pull request to the fullres-silent-pics branch.
Porting notes
- RAW_PHOTO_EDMAC needs to be changed on all cameras (see these comments in raw.c (https://bitbucket.org/hudson/magic-lantern/commits/a0a2afea2d57))
- Skip offsets for photo mode will have to be re-calibrated (example (https://bitbucket.org/hudson/magic-lantern/commits/33a03bef1998)). Fortunately, it's much easier these days: download raw_diag.mo (http://a1ex.magiclantern.fm/bleeding-edge/raw_diag.mo), select the "OB zones" option, and adjust the offsets until you get the following picture (note the cyan box being just inside the noisy borders):
-
Could this discovery lead to higher resolutions of Raw video in full sensor mode?
-
Could this discovery lead to higher resolutions of Raw video in full sensor mode?
From the first post:
4K video?
Too early to ask. Find a way to speed up the capture process first (see the research section below).
However, I don't really expect more than 10 fps (in LV crop mode on 5D3, 1/3.6 of the total sensor area is sampled at 30fps). If you implement a burst mode from the current code base, you'll get up to 5 fps.
-
From the first post:
4K video?
Too early to ask. Find a way to speed up the capture process first (see the research section below).
However, I don't really expect more than 10 fps (in LV crop mode on 5D3, 1/3.6 of the total sensor area is sampled at 30fps). If you implement a burst mode from the current code base, you'll get up to 5 fps.
Maybe 2.5k ;)
-
Anyone test on 5D2 yet? are there EXIF info?
-
:) Nice work, once again a1ex et al!
I am hoping that someone who does end up testing this on a 5d2 would share the module for the less code-savvy of us. I really can't wait to try. :)
-
Video tutorial about the install method would be great!
-
I have been trying to create a trigger for this Full Res silent picture to help capture day lightning, and so far I have it working to where it actually works to where using a half shutter trigger I can capture once I see a flash and it looks like it captures the flash I saw not what I see when I pressed the button.
I was hoping someone with real code know how could look it over to help me clean it up or improve it???
I was trying to use it with a motion trigger or a luminance trigger, but I guess it is not possible since live view has to be paused to make it work?
I did try to use the code from the bolt_rec module and add that as my trigger, but that does not work either, the calculations stop once the full res code starts up.
But this method would be great for hand trigger to get better results that using the camera with mechanical shutter and its faster then using the Full_Res_Silent picture method because captures are 250 to 300ms which is to slow.
So if someone with experience could look it over quickly and just maybe give some tips to make it better and more stable I would be greatful! :)
// Full-Res Silent Pictures //
#include <module.h>
#include <dryos.h>
#include <bmp.h>
#include <menu.h>
#include <config.h>
#include <property.h>
#include <raw.h>
#include <shoot.h>
#include <zebra.h>
#include <beep.h>
#include <lens.h>
static int full_res_enabled = 0;
static int save = 0;
static char* silent_pic_get_name()
{
static char imgname[100];
char *extension = "DNG";
int file_number = get_shooting_card()->file_number;
char pattern[100];
snprintf(pattern, sizeof(pattern), "%s/%04d%%04d.%s", get_dcim_dir(), file_number, 0, extension);
get_numbered_file_name(pattern, 9999, imgname, sizeof(imgname));
bmp_printf(FONT_MED, 0, 35, "%s ", imgname);
return imgname;
}
static void silent_pic_save_dng(char* filename, struct raw_info * raw_info)
{
save_dng(filename, raw_info);
}
static void capture()
{
while(1)
{
if(full_res_enabled)
{
PauseLiveView();
clrscr();
vram_clear_lv();
struct JobClass * job1 = (void*) call("FA_CreateTestImage");
call("FA_CaptureTestImage", job1);
call("FA_DeleteTestImage", job1);
}
if(full_res_enabled && get_halfshutter_pressed())
{
save = 1;
break;
}
}
if(full_res_enabled && save == 1)
{
save = 0;
void raw_buffer_intercept_from_stateobj();
raw_buffer_intercept_from_stateobj();
int new_gui = GUISTATE_QR;
prop_request_change_wait(PROP_GUI_STATE, &new_gui, 4, 1000);
/* preview the raw image */
raw_set_dirty();
raw_update_params();
clrscr();
raw_preview_fast();
/* prepare to save the file */
struct raw_info local_raw_info = raw_info;
/* leave some time for overlays to get displayed */
/* (fixme: saving the DNG will destroy the contents of the raw buffer) */
//msleep(2000);
/* save the raw image as DNG */
char* fn = silent_pic_get_name();
bmp_printf(FONT_MED, 0, 60, "Saving %d x %d...", local_raw_info.jpeg.width, local_raw_info.jpeg.height);
silent_pic_save_dng(fn, &local_raw_info);
bmp_printf(FONT_MED, 0, 60, "Saved %d x %d. ", local_raw_info.jpeg.width, local_raw_info.jpeg.height);
msleep(10);
}
return;
}
static void full_res_enable()
{
/* toggle the lv_save_raw flag from raw.c */
raw_lv_request();
capture();
msleep(50);
}
static void full_res_disable()
{
raw_lv_release();
}
static void raw_lv_request_update()
{
static int raw_lv_requested = 0;
if (full_res_enabled && lv && is_movie_mode())
{
if (!raw_lv_requested)
{
full_res_enable();
raw_lv_requested = 1;
}
}
else
{
if (raw_lv_requested)
{
full_res_disable();
raw_lv_requested = 0;
}
}
}
static unsigned int capture_loop_cbr()
{
raw_lv_request_update();
if (!full_res_enabled)
{
return 0;
}
if (!lv || !is_movie_mode())
{
return 0;
}
return 0;
}
static struct menu_entry res_menu[] = {
{
.name = "FullResDNG",
.priv = &full_res_enabled,
.max = 1,
.depends_on = DEP_LIVEVIEW,
},
};
static unsigned int full_res_init()
{
menu_add("Shoot", res_menu, COUNT(res_menu));
return 0;
}
static unsigned int full_res_deinit()
{
return 0;
}
MODULE_INFO_START()
MODULE_INIT(full_res_init)
MODULE_DEINIT(full_res_deinit)
MODULE_INFO_END()
MODULE_CBRS_START()
MODULE_CBR(CBR_SHOOT_TASK, capture_loop_cbr, 0)
MODULE_CBRS_END()
MODULE_CONFIGS_START()
MODULE_CONFIGS_END()
UPDATE: Sorry about making the code a quote before.
-
I think the idea would be not to use LV for the trigger, but to just continuously take silent pics, do the analysis on that data and then only save it if you detect a strong change in luminance. The only slow part is saving the dng.
-
YES!
But how do I compile this? how can i download the magic lantern file with this that will work on the 550d? Could someone send me the compiled file?
-
I think the idea would be not to use LV for the trigger, but to just continuously take silent pics, do the analysis on that data and then only save it if you detect a strong change in luminance. The only slow part is saving the dng.
Sounds like an idea! Any ideas on how I can code that? I am not a programmer, just very basic knowledge. And thank you for your input!
-
You can try something like this (it's like a full-res LiveView):
while(1)
{
/* capture a raw image */
struct JobClass * job = (void*) call("FA_CreateTestImage");
call("FA_CaptureTestImage", job);
/* tell the raw backend to catch the raw buffer address from RAW_PHOTO_EDMAC */
void raw_buffer_intercept_from_stateobj();
raw_buffer_intercept_from_stateobj();
/* preview the raw image */
raw_set_dirty();
if (raw_update_params())
{
raw_preview_fast();
}
call("FA_DeleteTestImage", job);
}
Inside this loop, you can add some luma checks (the easiest way is with raw_hist_get_percentile_level), and once you hit some threshold, save the frame as DNG.
Optimizations:
- do the raw preview in some other task, as in mlv_play. Or just switch to grayscale; the overhead should be very small.
- once you detected a change, save not only that frame, but also the next few frames (you can buffer a small number of them - calling srm_malloc_suite(0) will tell you how many).
-
You can try something like this (it's like a full-res LiveView):
Great! will try this, thank you very much, hoping to test on lightning later today, its that time of the year here in Florida.
-
Some more rolling shutter analysis (with the same script as before (http://www.magiclantern.fm/forum/index.php?topic=12523.msg120758#msg120758)):
5D3:
Test images: regular.CR2 (http://a1ex.magiclantern.fm/bleeding-edge/gradient/5D3/regular.CR2) and silent.DNG (http://a1ex.magiclantern.fm/bleeding-edge/gradient/5D3/silent.DNG) (warning: large files)
Canon settings: 1/4 vs 1/8000, ISO 100.
Image difference in EV (left), exposure difference per row, in EV (mid-left), in milliseconds (mid-right) and timer register configuration (right):
(http://a1ex.magiclantern.fm/bleeding-edge/gradient/5D3/expo-delta.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/5D3/row_exposure.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/5D3/row_exposure_time.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/5D3/fps-registers.png)
Exposure range : 1/33.19 ... 1/6.30
Rolling shutter : 0.13 seconds
6D:
Test images from 1%: regular.CR2 (http://ge.tt/4WkpZJo1/v/0?c) and silent.DNG (http://ge.tt/45UEYJo1/v/0?c.DNG) (warning: large files)
Canon settings: 1/4 vs 1/4000, ISO 100.
(http://a1ex.magiclantern.fm/bleeding-edge/gradient/6D/expo-delta.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/6D/row_exposure.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/6D/row_exposure_time.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/6D/fps-registers.jpg)
Exposure range : 1/3.09 ... 1/1.87
Rolling shutter : 0.21 seconds
500D:
Test images from Greg: regular.CR2 (http://a1ex.magiclantern.fm/bleeding-edge/gradient/500D/regular.CR2) and silent.DNG (http://a1ex.magiclantern.fm/bleeding-edge/gradient/500D/silent.DNG) (warning: large files)
Canon settings: 1/4 vs 1/4000.
(http://a1ex.magiclantern.fm/bleeding-edge/gradient/500D/expo-delta.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/500D/row_exposure.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/500D/row_exposure_time.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/500D/fps-registers.png)
Exposure range : 1/83.45 ... 1/3.43
Rolling shutter : 0.28 seconds
5D2:
(copied the results from my previous post, just to have everyting in one place)
Test images: regular.CR2 (http://a1ex.magiclantern.fm/bleeding-edge/gradient/regular.CR2) and silent.DNG (http://a1ex.magiclantern.fm/bleeding-edge/gradient/silent.DNG) (warning: large files)
Canon settings: 1/4 vs 1/8000.
(http://a1ex.magiclantern.fm/bleeding-edge/gradient/expo-delta.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/row_exposure.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/row_exposure_time.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/fps-registers.png)
Exposure range : 1/59.97 ... 1/3.86
Rolling shutter : 0.24 seconds
Now, let's look at the numbers from the graph and at the FPS timers configured in adtg_gui, and cross-check them with the theory from FPS override: http://magiclantern.wikia.com/wiki/VideoTimer
Let's take the 5D2 first. The main clock, from FPS override, is 24 MHz. Timer A is configured at 0x5db+1 = 1500 units. In the second part of the exposure, timer B is configured at 0xdf+1 and then at 0xedc+1. Exposure time is 1 / (MainClock / timerA / timerB), so the timers are programmed to do 1/71.42 + 1/4.20 seconds = 0.014 + 0.2378 seconds.
So, the last value for timer B (0xedc => 0.2378 seconds) must be for the ramping part (the lines are read out one by one, but since the shutter is open, bottom rows are receiving more light). It matches the measured rolling shutter value.
The previous value for timer B (0xdf) must be for the constant exposure part (the entire sensor is capturing light). Total exposure for the last row would be 0.014 + 0.2378 = 1/3.971 seconds, and for the first active row, there is an optical bar 51px wide => 0.014 + 0.2378 * 51/3804 = 1/58.18 seconds.
The first part of the exposure (0x2f+0x207) is called DummyReadout. I'm not sure what it does, but it seems to be related to FPN correction.
500D: main clock 32 MHz, timer A 0xaf9+1, timer B 0x71+0xc83 (+1+1). The last number must be the rolling shutter: 0.281 seconds. The previous one must be the constant exposure part: 0.01 seconds. Total exposure: bottom row 0.281+0.01 = 1/3.436 seconds, top row 0.281*26/3204 + 0.01 = 1/81.43 seconds. Notice there's no dummy readout step.
5D3: main clock 24 MHz, timer A 0x317+1 and timer B 0x21d+0x1ce4+0x12e+0xf75 (+1 for each term). Rolling shutter: 24e6 / (0x317+1) / (0xf75+1) = 0.1306 seconds.
The previous one (0x12e) must be constant exposure: 0.01 seconds. Total exposure: bottom row 1/7.11, top row 0.01 + 0.1306*80/3950 = 1/79.08. Unexplained: around 0.018 seconds of exposure for all rows.
6D: main clock 25.6 MHz, timer A 0x597+1, timer B 0xe8d+1, rolling shutter 0.208 seconds.
Constant exposure part: 0x335 => 0.046 seconds. Bottom row exposure 1/3.94, unexplained 0.28s. Top row exposure 1/20.78, unexplained 0.275s. Notice the total exposure time is much higher than on the other cameras - exactly this "unexplained" time.
From the screenshot, adding two more timers (0x218+0x110f) gives 1 / (25.6e6 / (0x597+1) / (0x110f+0x218+2)) = 0.274 seconds. Coincidence? Why did the 5D3 get a shorter exposure? (it also has a large timer in the screenshot)
In all cases, notice the FPS timers are giving accurate values for rolling shutter (they match the measured values) and also notice the FPS timer B matches the vertical resolution of the camera (including top optical black bar, and a few extra pixels in newer cameras).
From this, I think the FPS timer A gives the clock for row readout (at each timer A rollover, a line is read out). If you know the main clock, the timer A, and the vertical resolution, you can compute the amount of rolling shutter with very good accuracy. This result probably applies to LiveView readout too, but needs to be double-checked.
Nitpick: you may want to multiply the rolling shutter, as computed from FPS timers, by (total_height-ob_height) / total_height, which is about 0.97...0.99.
If you want to see the same analysis for your camera, take the two test images with this script (http://a1ex.magiclantern.fm/bleeding-edge/gradient/dont-click-me.c), then get the ADTG screenshot by following these steps (https://bitbucket.org/hudson/magic-lantern/commits/e261cbbbdf25a380f74c15ddb671952518693b26#comment-1086388).
-
Is that longer exposure time the cause for the noise in the 6D image?
-
No idea, maybe just less light.
-
Didn't consider less scene light.
The results for 6D are very different to the other cameras. Wonder if 1% was using some (FPS?) code from his repo during the test?
-
FPS override has no effect on silent pictures. From the discussion on Bitbucket (https://bitbucket.org/hudson/magic-lantern/commits/e261cbbbdf25a380f74c15ddb671952518693b26), the settings seem to be alright.
It doesn't hurt if anyone else double-checks it, but I expect the same results.
edit: updated the above post with 6D screenshot and some more numbers.
-
none of these other cameras flip fps, ie 5D3 could use fps override without doing it from EVF state.
-
Just had an idea:
Use the full-res silent pics to meter for ETTR before taking a pic (when not in LV)
Edit: meh, nevermind I forgot you'd still have to raise the shutter anyway, so it's not saving shutter clicks :p
-
Is this gonna come available for time-lapse use, or is there more research needed to implement this for time-lapses ?
Maybe this can be put somehow in the intervalometer menu, as an option for silent full res pics ::)
-
The intervalometer is already able to capture silent pictures, just enable both and it works. :-)
The large delay between the shots, if not reduced, is going to be a little problematic for timelapses, as it will result in rather high real-time multipliers in the finished videos. For example, 1 frame / 20s = real-time x 480 @ 24 fps.
-
Didn't know that it is that usable already :o
The long delay is no problem, I'm mostly interested in nighttime time lapses, skies full of stars.
Normally I would have 15 or 20 seconds between pictures for nighttime time lapses
Do you have a 6d build with full res silent pictures option, or should I ask somebody else to compile it for me ?
-
I recommend turn off the "Long exp. Noise reduction". Currently, if this feature is enabled, cause err 70.
-
Didn't know that it is that usable already :o
The long delay is no problem, I'm mostly interested in nighttime time lapses, skies full of stars.
Normally I would have 15 or 20 seconds between pictures for nighttime time lapses
Do you have a 6d build with full res silent pictures option, or should I ask somebody else to compile it for me ?
I'm confused about this new develop in the Silent Pictures, so what does it allow for you to do higher DNG VIDEO Then the RAW or MLV?
In laymen terms what is the new development.
-
Full res RAW video but quite low fps numbers.
-
Full res RAW video but quite low fps numbers.
So does this mean the 5D Mark II can do Full Res 23fps
(Let's take the 5D2 first. The main clock, from FPS override, is 24 MHz. Timer A is configured at 0x5db+1 = 1500 units. In the second part of the exposure, timer B is configured at 0xdf+1 and then at 0xedc+1. Exposure time is 1 / (MainClock / timerA / timerB), so the timers are programmed to do 1/71.42 + 1/4.20 seconds = 0.014 + 0.2378 seconds).
-
So does this mean the 5D Mark II can do Full Res 23fps
NO! Read the OP
However, I don't really expect more than 10 fps (in LV crop mode on 5D3, 1/3.6 of the total sensor area is sampled at 30fps). If you implement a burst mode from the current code base, you'll get up to 5 fps.
-
I'm confused about this new develop in the Silent Pictures, so what does it allow for you to do higher DNG VIDEO Then the RAW or MLV?
In laymen terms what is the new development.
It means that you can take full resolution pictures without using the shutter mechanism.
For normal photography this isn't really that interesting.
The most interesting part right now would be time lapses.
DSLR's can take about 100,000 pictures (the expensive ones more) before the shutter mechanism wears out.
Timelapse videos with a frame rate of 25 FPS take (60seconds x 25 pictures) 1500 pictures per minute.
So if you want 1 minute of time-lapse video you need 1500 pictures.
Now with this new development, you can make a time-lapse, for example, 1500 pictures, and the shutter mechanism is only used one time (by opening it for live view).
So this way we could make a lot more time-lapse before the shutter mechanism breaks down...
-
I would like give FRSP a try for focus stacking as well. ML's focus stacking method works with AF lenses only and I think I'm not the only one with some strange looking opto-mechanical setup for 3:1 macro and below. Kind of steam punk but as in Bauhaus "form follows function". DOF below 0.25 mm and AF totally absent.
-
Tried this on my 5D3 (fw 1.2.3).
Grabbed the fullres-silent-pics branch and merged the 5D3-123 branch into it.
'Simple' mode silent pics works ok; but full res crashes with Err 70.
Crash log:
ASSERT: 0
at ./Param/HivshdParam.c:64, task ShootCapture
lv:0 mode:3
Magic Lantern version : Nightly.2014Jul18.5D3123
Mercurial changeset : b1838cf8d136+e0a1e77aeb30+ (fullres-silent-pics)
Built on 2014-07-18 09:30:21 UTC by xxx.
Free Memory : 167K + 3895K
Phil.
-
everything works fine on 700D after several tests, though I was unable to view the full-res DNG files via ML menu (both modules activated as silent pic requires: pic_view, file_man). That's not a big problem, but hope it gets fixed.
-
@philmoz: what exposure settings did you use? If one of them was auto, that would be interpreted as 0 (which is not valid). These routines were meant for factory testing, and they do behave a little different than regular pictures (they use a separate code path in scsReleaseData, codenamed FA DARK_MEM1)
@wyrlyn: do you see any error in Debug menu, on the Free Memory entry? Can you post a screenshot of EDMAC channel 0 right after taking a regular picture, without going to LiveView? (Debug -> Show EDMAC -> scroll to the right)
Can you also upload a sample DNG?
(I guess the raw image size, as declared in raw.c, might be a bit too large)
-
@philmoz: what exposure settings did you use? If one of them was auto, that would be interpreted as 0 (which is not valid). These routines were meant for factory testing, and they do behave a little different than regular pictures (they use a separate code path in scsReleaseData, codenamed FA DARK_MEM1)
Thanks, was using Auto ISO - setting manual ISO fixed that problem.
Also got this crash a few times - not sure how to reproduce it; but may be from switching to full-res after taking a few silent pics in simple mode. Last time this happened the camera locked up when turning off (had to pull the battery).
Edit: reproducible on my 5D3. Take a Simple mode silent pic. Switch to Full-Res mode, get 'Raw Error' when half press shutter and Err 70 when full press shutter.
ASSERT: GetMemoryAddressOfMemoryChunk( GetFirstMemChunk( pMem1AllocateListItem->hMemSuite ) ) == pMessage->pAddress
at SrmActionMemory.c:1619, task RscMgr
lv:0 mode:3
Magic Lantern version : Nightly.2014Jul18.5D3123
Mercurial changeset : b1838cf8d136+e0a1e77aeb30+ (fullres-silent-pics)
Built on 2014-07-18 09:30:21 UTC by xxx
Free Memory : 167K + 3893K
Phil.
-
No error in Free Memory Entry, it works fine.
EDMAC Channel 0 pic: http://s15.postimg.org/dj8y7m2az/20140718675.jpg (http://s15.postimg.org/dj8y7m2az/20140718675.jpg)
Viewing the picture works now with the mentioned modules enabled it just takes about 5-6 sec to get it loaded after a black screen (might be because of the large file size).
-
Yeah; loading is fast (less than 1 second in my test), but processing is slow. It can be optimized (one needs to write some 14-bit unpacking code for big endian - Canon encodes as little endian, but the DNG spec requires big endian for 14-bit encoding), but not a priority for me. This endianess conversion is what's slowing things down.
If you scroll to EDMAC channel 0, you will see the complete resolution; the overview page only displays the width.
The easiest way to speedup things would be to use the MLV or RAW format (even if it's just one frame, or a burst sequence).
-
Some interesting info about sensor scanning modes, with pictures: http://www.ximea.com/support/wiki/allprod/Sensor_Shutter_Modes
So, our sensors use the "Global Reset Release Mode" for stills (including these silent pics), and the rolling shutter mode for LiveView. When doing the timing analysis earlier, I've assumed the "Global Reset Release Mode" (confirmed by motion blur), so what I called "rolling shutter" is probably better called "sensor readout speed". But it's just a nitpick - the start of the exposure is global and the end of the exposure is rolling.
-
If you scroll to EDMAC channel 0, you will see the complete resolution; the overview page only displays the width.
EDMAC on channel one after entering live view and taking a picture or not taking one shows only something on Size B : 4175c (5980 x 4) but it flashes back and forth with 100f8 (248 x1)
Address at top flashes with it from 1fa36ac for 248 and 1fa72b0 for 5980
Update, I guess it was because I was checking from the full_res build Cause it reads differ when I use the unified Cause when I take a picture I get a steady
9240x0
9240x0
3528x0
On EDMAC #0
-
This is for A1ex brain, not me. Very interesting with paper below to the right.
Reading most pro companies reduce the rolling with a mechanical solution - before the software read the information.
http://www.teledynedalsa.com/imaging/products/cameras/area-scan/falcon2/
-
Test time lapse -
-
Oh boy, waiting for this to use on my 6d :D
The exposure is fluctuating, are you not in "m" manual mode when you shoot time lapses ???
Hope this is not a side effect of full res silent pictures.
-
The sun is behind the clouds. Exposure is constant (manual mode, expo override).
Maybe I should use the dual iso and script BridgeRamp.
-
Thanks to mk11174 I have experimented with the full frame silent on my 5DIII 123.
I tried ETTR and it appears to overexpose a little, ie saturate. I estimate about half a stop, whereas in normal mode, with the same settings, it would not.
dual ISO appears to capture an image, but of course without EXIF I can't process it.
As I say, just some feedback, with no expectations at this stage, ie early days.
Cheers
Garry
-
Test time lapse -
Thanks. What are Canon settings, FPS, camera?
-
Tried finding the CCDWriteEDmacCompleteCBR from EOSM.202 rom, but couldn't. No problems finding it from 5D3.123 rom so I think it's just not there. Any ideas where to look next? I blindly tried the values used for other cameras, but just got error "Exposure too long".
Edit: If I just comment out the check for 15s exposures, I get somewhat correct images with RAW_PHOTO_EDMAC value used by 5D3 and 700D. A bit overexposed but quite good.
-
Test night sky time-lapse on the Canon EOS 60D (18/07/2014)
-
Why is it actually impossible to get less then 260 ms as exposure?
-
Thanks. What are Canon settings, FPS, camera?
500D (CPL and ND8 filter), 17mm, aperture about F14, Intervalometer -> Take pics... -> like crazy (currently writing take some time, so the delay is not needed)
Silent Picture -> Full-res ;D
-
so Greg, am assuming the shutter speed is around 1/10 of a second?
-
In Canon menu 1/10 - 1/50 (I do not remember)
-
Here is my test result from today. mk11174 thank you so much for compiling for me and of course thnx A1lex for making the impossible, possible.
Manual mode, F2.8, 1/4sec, ISO 100, Tiffen variable ND filter, 15sec interval
361 frames, 2160p, 23.976 frame rate, After Effects (best view fullscreen at 4K)
NOTE: 2 frames are completely black (frame 241 and 362 out of 363 were shot)
Don't know why or how to avoid.
BTW silent.mo were the only module loaded. and Global draw was set off.
Question: would ETTR helps?
-
What is min exposure time for raw full-res?
-
Working on 600D! Thanks so much! Im gonna try this in the night with Intervalomat enabled.
For TimeLapse it would be realy nice if every sequenz is saved in a seperat .mlv or .raw or even a new .tls (TimeLapseSequenz) container.
U r the real MVPs!
-
This is so great ... after all this time alex is still in the game for great new developments!
I always wanted silent pics for timelapse, so my dream seems to come true.
Is it possible to get a nice configurable timelapse-section in ML?
-
Some testing feedback on the 5DIII.
If I try and use an ETTR setting, at 0%, the FF silent DNG is always about 1 stop over exposed. ETTR setting was 2s, so beyond FF silent min.
If aperture set fully open, ETTR seems to be OK, ie stopping down doesn't work.
Linking the FF-Silent with timelapse generated an ERR 70 and some crash logs: https://www.dropbox.com/sh/mnqjd20ejr6qowg/AAD0RXnnPGfEpsGe_xjdE8aCa
Will carry on testing and reporting.
-
ASSERT: 0
at ./Param/AccumulateTime.c:53, task ShootCapture
lv:0 mode:3
Magic Lantern version : Nightly.2014Jul18.5D3123
Mercurial changeset : e0a1e77aeb30+ (5D3-123)
Built on 2014-07-18 19:19:21 UTC by mathew@mathewubuntu64.
Free Memory : 136K + 3731K
-
EDIT:Exp override was off,just read the previous post.
MLV worked for me as well as ML raw video converter 1.9.1 with my 60D.
I did a simple exposure test primarily to find out how to expose.
I shot 1 photo mlv timelapses trying the next shutter step starting from 1'' exposure until 1/400.
Used f1.4 and iso 100 throughout and wrote down the milliseconds.
Extracted and imported to LR to measure (alas by eye and histogram) exposure and possible issues.
Here are my initial findings.
1'' - 1333ms
0.8'' - 1081
0.6' ' - 964
0.5 - 809
0.4'' - 640
0.3'' - 616
1/4 - 549
1/5 - 460
1/6 - 438
1/8 - 389
1/10 - 360
1/13 - 344
1/15 - 324
1/20 - 320
1/25 - 312
1/30 - 292
1/40 - 284
1/50 - 281
1/60 - 276 After this exposure bumped up and started getting random numbers from 269+ms to 280+ so i stopped the test
1/80 - 282 yep
So exposure changes are not very linear as far as i can see (or maybe i am wrong?),and after 1/30 there is no point in closing the shutter further.
Plus there is a strange top-corner vignetting after 1/30 which seems it exists anyway in the all pictures in every exporuse although it isnt always very noticeable.
EDIT:Exp override was off, just read the previous post.
-
Thank you i will test this.
Cheers.
2nd sloppy test with the 60D with the modules brapodam linked.
Exposure simulation, and override, (if the latter matters) ,was ON.
f1.4 iso 100 exposures starting from 5'' until 1/250 exported using mlv converter and imported into LR.
Bug?next shutter (ie to go from 1/50 to 1/60) wouldn't change unless i went 2 steps ahead and then 1 back,
(had to go from 1/50 to 1/80 and then go back to 1/60 for it to engage and show in the screen).Maybe exp override does that?
So:
5'' - 5686ms f-stop reports incorrectly to LR (shutter reports 1.0s)
4'' - 4442 same as above
3.2'' - 3490 same as above
2.5'' - 2980 same as above
1.6'' - 1887 same as above
1.3'' - 1631 same as above
1'' - 1333 same as above
0.8'' - 1091 same as above
0.6' ' - 954 same as above
0.5 - 799 reports correctly as 0.5''
0.4'' - 680 ----reports as 0.5''---
0.3'' - 616
1/4 - 539
1/5 - 460
1/6 - 438
1/8 - 399
1/10 - 360 After this step exposure changed very little and top corners vignette became more and more noticeable
1/13 - 354
1/15 - 324
1/20 - 310
1/25 - 301
1/30 - 302 ?
1/40 - 284
1/50 - 291
1/60 - 276
1/80 - 271
1/100- 270
1/125- 268
1/160- 266
1/200- 275
1/250- 264
Dont know if all these mean much, if there are other means to test this further and provide useful info, let me know.
A few random pics with shutter 1/3, 1/8, 1/30, 1/125.
http://postimg.org/image/3uxdr5bdv/
http://postimg.org/image/yb3ap9wwz/
http://postimg.org/image/t66ole9cz/
http://postimg.org/image/eygzwqwo3/
-
A few tests on the 50D show different ms. Haven't gone through the whole range, but matched ISO100 and f/1.4
Shooting at 5s gave 5607ms
Shooting at 1/10s 310-312ms (this too seems to be the sweet spot for no darkness at top of frame, with least amount of motion)
-
Shutter speed is set from a table, in scsDummyReadoutDone, first call right after NormalCapture; on 60D, the table is at 0xFF5B4DA8; it was first mentioned here (http://www.magiclantern.fm/forum/index.php?topic=1915.msg23797#msg23797).
These numbers are plugged into a routine which prints something about VSizeSetting, and does some math, which transforms the time value in units for FPS timer B.
On 60D, that table looks like this:
raw_shutter printed_time time_ms fps_timer_B_units
16 32" => 32292 ms 2131 + 132*5004
17 32" => 30480 ms 5000 + 124*5004
18 32" => 27951 ms 3176 + 114*5004
19 25" => 25632 ms 655 + 105*5004
20 20" => 23505 ms 2069 + 96*5004
21 20" => 21555 ms 2110 + 88*5004
22 20" => 19767 ms 471 + 81*5004
23 20" => 18127 ms 1864 + 74*5004
24 16" => 16623 ms 1045 + 68*5004
25 16" => 15244 ms 2786 + 62*5004
26 16" => 13980 ms 1885 + 57*5004
27 12.5" => 12820 ms 3114 + 52*5004
28 10" => 11757 ms 1331 + 48*5004
29 10" => 10782 ms 1352 + 44*5004
30 10" => 9888 ms 3032 + 40*5004
31 10" => 9068 ms 1229 + 37*5004
32 8" => 8316 ms 819 + 34*5004
33 8" => 7626 ms 1680 + 31*5004
34 8" => 6994 ms 3729 + 28*5004
35 6" => 6414 ms 1844 + 26*5004
36 6" => 5883 ms 963 + 24*5004
37 5" => 5395 ms 963 + 22*5004
38 5" => 4948 ms 1803 + 20*5004
39 5" => 4538 ms 3401 + 18*5004
40 4" => 4162 ms 696 + 17*5004
41 4" => 3817 ms 3627 + 15*5004
42 4" => 3501 ms 2151 + 14*5004
43 3.2" => 3211 ms 1209 + 13*5004
44 3" => 2946 ms 778 + 12*5004
45 2.5" => 2702 ms 778 + 11*5004
46 2.5" => 2478 ms 1188 + 10*5004
47 2.5" => 2273 ms 1987 + 9*5004
48 2" => 2085 ms 3135 + 8*5004
49 2" => 1913 ms 4610 + 7*5004
50 2" => 1755 ms 1372 + 7*5004
51 1.6" => 1610 ms 3401 + 6*5004
52 1.5" => 1477 ms 676 + 6*5004
53 1.3" => 1355 ms 3176 + 5*5004
54 1.3" => 1243 ms 881 + 5*5004
55 1.3" => 1141 ms 3790 + 4*5004
56 1" => 1047 ms 1864 + 4*5004
57 1" => 961 ms 5102 + 3*5004
58 1" => 882 ms 3483 + 3*5004
59 0.8" => 809 ms 1987 + 3*5004
60 0.7" => 743 ms 635 + 3*5004
61 0.6" => 682 ms 4385 + 2*5004
62 0.6" => 626 ms 3237 + 2*5004
63 0.6" => 575 ms 2192 + 2*5004
64 0.5" => 528 ms 1229 + 2*5004
65 0.5" => 485 ms 5348 + 1*5004
66 0.5" => 445 ms 4528 + 1*5004
67 0.4" => 409 ms 3790 + 1*5004
68 0.3" => 376 ms 3114 + 1*5004
69 0.3" => 345 ms 2479 + 1*5004
70 1/3 => 317 ms 1905 + 1*5004
71 1/3 => 292 ms 1393 + 1*5004
72 1/4 => 268 ms 901 + 1*5004
73 1/4 => 247 ms 471 + 1*5004
74 1/4 => 227 ms 4651
75 1/5 => 209 ms 4282
76 1/6 => 192 ms 3934
77 1/6 => 177 ms 3627
78 1/6 => 163 ms 3340
79 1/6 => 150 ms 3073
80 1/8 => 138 ms 2827
81 1/8 => 128 ms 2622
82 1/8 => 118 ms 2418
83 1/10 => 109 ms 2233
84 1/10 => 100 ms 2049
85 1/13 => 93 ms 1905
86 1/13 => 86 ms 1762
87 1/13 => 79 ms 1618
88 1/15 => 73 ms 1495
89 1/15 => 68 ms 1393
90 1/15 => 63 ms 1290
91 1/20 => 59 ms 1209
92 1/20 => 54 ms 1106
93 1/25 => 51 ms 1045
94 1/27 => 47 ms 963
95 1/28 => 44 ms 901
96 1/30 => 41 ms 840
97 1/35 => 38 ms 778
98 1/38 => 36 ms 737
99 1/40 => 33 ms 676
100 1/45 => 31 ms 635
101 1/50 => 30 ms 614
102 1/55 => 28 ms 573
103 1/58 => 26 ms 532
104 1/60 => 25 ms 512
105 1/70 => 23 ms 471
106 1/80 => 22 ms 450
107 1/80 => 21 ms 430
108 1/90 => 20 ms 409
109 1/100 => 19 ms 389
110 1/110 => 18 ms 368
111 1/120 => 17 ms 348
112 1/125 => 17 ms 348
113 1/140 => 16 ms 327
114 1/150 => 15 ms 307
115 1/160 => 15 ms 307
116 1/180 => 14 ms 286
117 1/200 => 14 ms 286
118 1/215 => 13 ms 266
119 1/235 => 13 ms 266
120 1/250 => 13 ms 266
121 1/280 => 12 ms 245
122 1/300 => 12 ms 245
123 1/320 => 12 ms 245
124 1/350 => 11 ms 225
125 1/400 => 11 ms 225
126 1/430 => 11 ms 225
127 1/470 => 11 ms 225
128 1/500 => 10 ms 204
129 1/560 => 10 ms 204
130 1/600 => 10 ms 204
131 1/640 => 10 ms 204
132 1/750 => 10 ms 204
133 1/800 => 10 ms 204
134 1/850 => 10 ms 204
135 1/900 => 10 ms 204
136 1/1000 => 10 ms 204
137 1/1100 => 10 ms 204
138 1/1200 => 10 ms 204
139 1/1250 => 10 ms 204
140 1/1500 => 10 ms 204
141 1/1600 => 10 ms 204
142 1/1700 => 10 ms 204
143 1/1900 => 10 ms 204
144 1/2000 => 10 ms 204
145 1/2300 => 10 ms 204
146 1/2400 => 10 ms 204
147 1/2500 => 10 ms 204
148 1/3000 => 10 ms 204
149 1/3200 => 10 ms 204
150 1/3500 => 10 ms 204
151 1/3800 => 10 ms 204
152 1/4000 => 10 ms 204
153 1/4500 => 10 ms 204
154 1/4800 => 10 ms 204
155 1/5000 => 10 ms 204
156 1/6000 => 10 ms 204
157 1/6400 => 10 ms 204
158 1/7200 => 10 ms 204
159 1/7800 => 10 ms 204
160 1/8000 => 10 ms 204
These numbers are the exposure times for the very first image row (which is actually in the optical black border). The gradient effect was already (http://www.magiclantern.fm/forum/index.php?topic=12523.msg120750#msg120750) discussed (http://www.magiclantern.fm/forum/index.php?topic=12523.msg121962#msg121962) (if you have trouble understanding it, read this first (http://www.ximea.com/support/wiki/allprod/Sensor_Shutter_Modes)), and the last number from this table should match the timer B setting before the final readout. On 5D2, the last number from the same table is 14ms = 224 timer B units, which is 0xdf + 1 and matches the previous results.
When comparing the exposure times from the table above, with the run times of the capture function (as posted by gcrook), keep in mind there are other delays in the process, not exactly known (the capture code is quite complex), and most cameras (except 500D and 1100D) use a dummy capture step (which adds a constant delay before the actual capture).
So, these exposure times are approximate and slightly larger than the actual exposure; the exact exposure time is done (or expected to be done) by mechanical shutter.
Reminder: these are some test results I'm looking for, to complete the timing analysis. The test script is not present in the pre-compiled builds, so it's for those of you who compiled ML yourselves.
take the two test images with this script (http://a1ex.magiclantern.fm/bleeding-edge/gradient/dont-click-me.c), then get the ADTG screenshot by following these steps (https://bitbucket.org/hudson/magic-lantern/commits/e261cbbbdf25a380f74c15ddb671952518693b26#comment-1086388).
-
600D full-res silent pics:
Manual mode and AutoISO gives an error:
ASSERT: 0
at Param\HivshdParam.c:115, task ShootCapture
lv:0 mode:3
Magic Lantern version : Nightly.2014Jul22.600D102
Mercurial changeset : 4493f6e04e5f (fullres-silent-pics)
Built on 2014-07-22 19:10:51 UTC by edgar@linux-indh
Free Memory : 232K + 947K.
Manual mode and fixed ISO: no error
Edgar
-
Ok, lets get this thread back on track. :D
This thread is for full resolution silent picture development discussion. Before posting here, please stop to consider your post. Will it help development?
For discussion about capturing silent pictures using raw video formats, please see this thread by dmilligan: http://www.magiclantern.fm/forum/index.php?topic=12733.0
Want to request a build to help with development? There is already a thread created here: http://www.magiclantern.fm/forum/index.php?topic=12608.0
Note: Other members who can compile builds are more then welcome to fill requests in that thread.
Thankyou all for your understanding.
-
what is the difference between battery consumption with full res silent pics timelapse and standard timelapse ?
-
It takes about 10 minutes to find out. Look in Debug menu - once the percentage decreases by 2 units under a given workload, you can write down the estimated drain rate.
Of course, if you want better accuracy, you can do a few tests and average them - that will take some more time :P
-
Everybody, please double-check the skip offsets in raw.c and post the confirmation screenshots. The ones from 600D are wrong.
download raw_diag.mo (http://a1ex.magiclantern.fm/bleeding-edge/raw_diag.mo), select the "OB zones" option, and adjust the offsets until you get the following picture (note the cyan box being just inside the noisy borders):
(http://a1ex.magiclantern.fm/bleeding-edge/iso50/ob/ob-zones-5d3-6400.png)
-
500D :
(http://s27.postimg.org/oeossyufn/photo.png)
-
Everybody, please double-check the skip offsets in raw.c and post the confirmation screenshots. The ones from 600D are wrong.
600D, raw_diag.mo loading
tcc:error: undefinied symbol 'log2f'
failed to link modules
Edgar
-
It's there, just checked the current nightly.
00cd1644 log2f
If it's not present in your custom build, you can add a call to it in builtin-enforcing.c.
-
Everybody, please double-check the skip offsets in raw.c and post the confirmation screenshots. The ones from 600D are wrong.
I did post a screenshot the night I added the edmac and before you accepted it you said the skips were correct, so how are they wrong now???
Update: Just saw you commented me on bitbucket, but the screenshot was after edmac change because I got error if no change was made and tried full res silent picture.
-
http://www.magiclantern.fm/forum/index.php?topic=7139.msg123281#msg123281
Your screenshot was most likely done before the EDMAC changes.
-
http://www.magiclantern.fm/forum/index.php?topic=7139.msg123281#msg123281
Your screenshot was most likely done before the EDMAC changes.
Maybe something wrong in my source, I can try raw diag using the nightly and see what we get unless someone already got you one, but trust me, there was no way for me to get a screen before the edmac change, so I don't know what is wrong now?
-
Hm, the raw_diag screenshot was directly on a silent picture? Can you upload a DNG?
edit: I get it now, you got the screenshot from LiveView, not from photo mode...
You can get the raw_diag screenshot from regular photo mode, outside LV. If you really want to get it from a silent picture, use the intervalometer, not half-shutter. In both cases, the offsets should be equal, because it's the same Canon code that writes the raw data.
-
Hm, the raw_diag screenshot was directly on a silent picture? Can you upload a DNG?
Well, I turned on the fullres on the silent module, then I turned on Raw Diag with the zone option, then I did a half shutter press and held it for a second till I saw the Raw Diag text so I guess it was a silent picture it took cause the shutter did not activate.
Let me get her camera so I can do more tests with the tool and send you the DNG too.
Crap, just remembered the fullres is not in nightly yet.
So Ill create a new local repo and build and try, but do you want one with nightly too without fullres?
-
Hm, the raw_diag screenshot was directly on a silent picture? Can you upload a DNG?
edit: I get it now, you got the screenshot from LiveView, not from photo mode...
Ok, so just tell me exactly what you want and Ill grab it for you, I have camera now.
Gotcha, sorry, I thought it had to be a regular silent picture, I better check my 700d now to then!
Here is the screen from photomode and a regular photo take without silent picture turned on.
Looks real off doesnt it?
So any idea what the offsets should be now to start with for correction?
(http://s9.postimg.org/peef79q2n/OB_ZONES.jpg)
-
Look for CONFIG_600D in raw.c, and the last block has the offsets from photo mode. You can start from the values I've linked above, and maybe fine-tune a few pixels from there.
-
Look for CONFIG_600D in raw.c, and the last block has the offsets from photo mode. You can start from the values I've linked above, and maybe fine-tune a few pixels from there.
Ok, no problem, I know where they are in raw.c and how to adjust them, but was hoping for a starter point, thanks for that from the one post will give them a try and go from there and send you new screen when I get them correct.
-
I was just curious on what a screen would look like from nightly and here is a screen with a straight build from nightly, does this mean there wrong in the nightly which is before the EDMAC change?
(http://s15.postimg.org/7sqog85kb/OB_ZONES.jpg)
-
Yep. This one is going to cause black level issues that can be very hard to track down, and ETTR is probably not much better than random exposure on this camera.
And here's how I'll fix it. I'll merge the full-res silent picture branch next week, and I'll break all the nightly builds for which I don't have a raw_diag screenshot.
-
It's there, just checked the current nightly.
00cd1644 log2f
If it's not present in your custom build, you can add a call to it in builtin-enforcing.c.
Hmm, I compiled from latest ML-sources and math.h is included in builtin-enforcing.c. But the module isn´t loading. In the nightly the modul is loading. Don´t know, how to add a call in my build.
-
Something like: float x = log2f(3.14);
-
Sorry, don´t understand what to do. I must break this stuff, till I have got more understanding in coding.
-
#ifdef CONFIG_600D
width = 5344; //From Guess Py
height = 3465;
skip_left = 142;
skip_top = 50;
#endif
To close to edge?????
(http://s11.postimg.org/tchzuxg03/OB_ZONES.jpg)
-
Maybe. Check the RAW zebras for borders.
-
Maybe. Check the RAW zebras for borders.
(http://s11.postimg.org/oe8q4zxab/VRAM0.jpg)
Was this ok or is that a border at the top?
-
Here is
#ifdef CONFIG_600D
width = 5344; //From Guess Py
height = 3465;
skip_left = 142;
skip_top = 52;
#endif
(http://s27.postimg.org/ujghyeck3/VRAM6.jpg)
(http://s21.postimg.org/df822jyt3/OB_ZONES.jpg)
-
Here is the 700d with the current skips.
width = 5280;
height = 3528;
skip_left = 72;
skip_top = 52;
(http://s21.postimg.org/6s3h9s4jb/VRAM4_700d.jpg)
(http://s29.postimg.org/krzvmu4qf/OB_ZONES_700d.jpg)
-
Oh, both these tests are with fullres-silent-pics build.
-
Here is unified 700d screens
width = 5280;
height = 3528;
skip_left = 72;
skip_top = 52;
(http://s30.postimg.org/fasyko01d/VRAM5unified_700d.jpg)
(http://s22.postimg.org/q4aplu86p/OB_ZONES_Unified_700d.jpg)
-
Here is the 600d Unified build with tweaked skips
width = 5344; //From Guess Py
height = 3465;
skip_left = 158;
skip_top = 54;
(http://s29.postimg.org/b7d18c4tz/VRAM9_Unified_600_D.jpg)
(http://s14.postimg.org/i3a9yltb5/OB_ZONES_Unified_600d.jpg)
Whats up with the white overlap on the left side???
-
Whats up with the white overlap on the left side???
Don't worry about the current unified behavior. For many cameras, the old value for RAW_PHOTO_EDMAC would often result in image buffers that needed to be skipped ahead by some amount (usually 16 pixels) to have proper alignment. Once the fullres-silent-pics branch is merged, this will no longer be the case on most (or all?) cameras.
-
Everybody, please double-check the skip offsets in raw.c and post the confirmation screenshots. The ones from 600D are wrong.
60D:
(https://bitbucket.org/dmilligan/magic-lantern/downloads/OB-ZONES.png)
-
Curiously enough to ask if that means that we will not need to press 5X button to go into full pixel mode RAW recording in the future?
If somebody "accidentally" finds how to port these raws through that jpg pipeline...and, combining with that 1/3 stop highlight reduction, and... wrap it with sound into MLV format...I have dropped down in bed to think more about it. Ciao ;)
-
Don't worry about the current unified behavior. For many cameras, the old value for RAW_PHOTO_EDMAC would often result in image buffers that needed to be skipped ahead by some amount (usually 16 pixels) to have proper alignment. Once the fullres-silent-pics branch is merged, this will no longer be the case on most (or all?) cameras.
Right. Some more background info about this change:
This value for EDMAC is the one used at photo capture step. The previous one was from some other postprocessing stage, and usually different on each camera. From the capture to the CR2 and then to LCD preview, there are a bunch of postprocessing steps, like cropping some borders, FPN correction, bad pixel correction, maybe digital ISO (e.g. on 5D2 at ISO > 1600) and who knows what else.
The fullres silent picture code only calls the photo capture step - but not the processing into CR2, YUV, JPG and so on. So, right now I'm sure I'll get the original RAW buffer, as captured, and the behavior will be consistent on all cameras. Furthermore, since the buffer has the data before any postprocessing, modifying the data in this buffer is very likely to end up in the CR2 and the JPG; before, this happened on some cameras, but not on others.
So, this was a good opportunity to make sure the photo raw behavior is consistent on all cameras.
Bad offsets could cause subtle issues that are unlikely to be reported as bugs, and very hard to track down (ML uses these black borders for noise analysis, so any exposure or postprocessing tool that relies on this would give inaccurate results - from slightly weird to totally broken).
There's still a minor issue with this approach: the DNG might be a few pixels larger than the CR2, so the skip offsets might not match. This will only be an issue if you will take a dark frame from a few hundreds of silent pictures, then find out it's not perfectly aligned with your CR2's. Should be easy to fix in post though, and those shooting astro certainly have the skills to do this.
-
If you want to see the same analysis for your camera, take the two test images with this script (http://a1ex.magiclantern.fm/bleeding-edge/gradient/dont-click-me.c), then get the ADTG screenshot by following these steps (https://bitbucket.org/hudson/magic-lantern/commits/e261cbbbdf25a380f74c15ddb671952518693b26#comment-1086388).
60D:
silent.DNG (https://dl.dropboxusercontent.com/u/74060/silent.DNG) regular.CR2 (https://dl.dropboxusercontent.com/u/74060/regular.CR2)
(https://bitbucket.org/dmilligan/magic-lantern/downloads/60D_FPS_Timers.png)
I'm having trouble getting the octave script to work though, perhaps it something to do with this:
warning: your version of GraphicsMagick limits images to 8 bits per pixel
I just end up with a flat graph. I know there's some rolling shutter, you can see it visually just looking at the silent.DNG
-
Yeah, you need a custom-compiled version of both octave and GraphicsMagick, and that's because the package maintainers on both Mac and major Linux distros chose to build the 8-bit version only.
http://wiki.octave.org/GraphicsMagick
http://marcelojoeng.blogspot.com/2012/11/compile-octave-using-1632-bits-colour.html
If you find a way to do this on Mac, let me know, because I'm preparing a tutorial on processing RAW images in Octave, and I'm a bit stuck because of this issue (the prebuilt versions will not run the tutorial).
(http://a1ex.magiclantern.fm/bleeding-edge/gradient/60D/expo-delta.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/60D/row_exposure.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/60D/row_exposure_time.png) (http://a1ex.magiclantern.fm/bleeding-edge/gradient/60D/fps-registers.png)
Exposure range : 1/86.47 ... 1/5.55
Rolling shutter : 0.17 seconds
The timer math is left as an exercise to the reader. The 60D sensor seems fairly fast, probably required for high burst rates.
-
I don't know what am doing but I installed the module, then made full-res silent dng mode active then took a pic from LCD
Here is the result
5D2
(http://199.167.201.88/screencaptures/5d2ob-zones.jpg)
-
Wondering if someone could post a link to the compiled module and core. I'm on a 5D2.
Many thanks!
-
Here are results from the 50D. For this particular model, I note that TimerB, at 0xc9c=3228, is precisely the number of rows of the raw buffer, and thus is the number of times that TimerA should elapse. That simplifies my conception of the timer math described earlier in this thread, making intuitive sense why it is that both TimerB and the vertical resolution are linked to the rolling-shutter time.
Exposure range : 1/85.05 ... 1/6.66
Rolling shutter : 0.14 seconds
(https://www.dropbox.com/s/7d1f71u36izbimj/silent%20picture%20gradient%2050D.png?dl=1)(https://www.dropbox.com/s/vynckfvd5h4bmwx/fullres-50D-timers.png?dl=1)
Timer math:
- Rolling shutter
- TimerA(0x4f5+1) / Clock(28.8 MHz) * Rows(3177) = 0.140 s
- Constant exposure duration
- TimerA(0x4f5+1) / Clock(28.8 MHz) * TimerB(0xe1+1) = 0.010 s
- Shortest exposure for a row
- Constant exposure + TimerA(0x4f5+1) / Clock(28.8 MHz) * OB rows(50) = 0.012 s
-
Another fast sensor - didn't quite expect it.
If you consider the lower resolution...
// TimerA / Clock / Columns
5D3 : (0x317+1) / 24.0 / 5936 = 5.56 nanoseconds per pixel
50D : (0x4f5+1) / 28.8 / 4832 = 9.13 nanoseconds per pixel
60D : (0x57d+1) / 28.8 / 5344 = 9.14 nanoseconds per pixel
6D : (0x597+1) / 25.6 / 5568 = 10.05 nanoseconds per pixel
5D2 : (0x5db+1) / 24.0 / 5792 = 10.79 nanoseconds per pixel
500d: (0xaf9+1) / 32.0 / 4832 = 18.17 nanoseconds per pixel
the 50D sensor is clocked just as fast as the 60D one (the speed difference is too small). So, the 50D should be a good candidate for higher FPS (60D's LiveView goes up to around 37 fps, but the H.264 encoder can no longer keep up).
LiveView clocks seem to be a little slower:
5D3: 440 / 24.0 / 2080 = 8.81 ns/px, overclocked 7.97
60D: 546 / 28.8 / 1880 = 10.08 ns/px, overclocked 9.90
50D: 696 / 28.8 / 1664 = 14.52 ns/px, overclocked 14.31
So, there must be a way to fine-tune the pixel clock somehow, and that should be found by comparing LV with photo capture code (how the hardware is configured in both cases).
edit: fixed a typo, thanks ayshih
-
I've got a stupid question ;) How to merge two branches ??
Now I'm using this commands in my script:
hg clone https://bitbucket.org/hudson/magic-lantern/
cd magic-lantern
hg update 5D3-123
hg merge unified
what should I change to add fullres-silents-pics branch ??
-
You can just merge 5D3-123 with fullres-silent-pics.
If you want to merge 3 branches, you can create a "work" branch, let's say starting from "unified", then merge 5D3-123 into it, then commit, then merge fullres-silent-pics into it.
More info: www.magiclantern.fm/forum/index.php?topic=9524
-
Is it normal that DNG fullres silent pic is much brighter than actual picture displayed in LV ?
-
Answered in the first post and many times throughout the thread.
-
marekk , exposure overide need to be on. as instucted by alex
-
LiveView clocks seem to be a little slower:
5D3: 440 / 24.0 / 2080 = 8.81 ns/px, overclocked 7.97
60D: 546 / 24.0 / 1880 = 12.10 ns/px, overclocked 11.88
50D: 696 / 28.8 / 1664 = 14.52 ns/px, overclocked 14.31
I think you made a typo: doesn't the 60D have a 28.8 MHz clock (as you used earlier)? I think it should be:
60D: 546 / 28.8 / 1880 = 10.08 ns/px, overclocked 9.90
which is closer to the photo readout time.
I wonder how much time is needed to bin pixels, and perhaps the 50D's hardware can't do it efficiently. Comparing the 50D and 60D in LV zoom mode:
50D: 636 / 28.8 / 2064 = 10.70 ns/px, overclocked 10.60
60D: 734 / 28.8 / 2520 = 10.11 ns/px, overclocked 10.09
which is a lot closer than in LV normal mode.
-
Correct.
From the rolling shutter tests in video mode (http://www.magiclantern.fm/forum/index.php?topic=12656.msg123560#msg123560), 5x zoom and 1080p use roughly the same timing on 60D.
60D 1080p : 546 / 28.8 / 1880 = 10.08 ns/px, overclocked 9.90
60D 5x zoom: 734 / 28.8 / 2520 = 10.11 ns/px, overclocked 10.08
-
my 5d3 still has brightness issue even with exposure override on
-
Answered in the first post and many times throughout the thread.
and no, it's not about exposure override.
-
if I'm right the overexposing is caused by the 1/10sec limit, but you can get rid of that by using fader ND or just post-process the file using Camera Raw (adjusting exp).
-
Right, and the exact timings for the fastest possible exposure were analyzed in the previous pages (all those funky graphs).
-
I'll merge the full-res silent picture branch next week, and I'll break all the nightly builds for which I don't have a raw_diag screenshot.
Hint for 6D, 7D, 550D, 650D, 1100D and EOS-M.
-
Non-coder with 650D and 7D here. Anything I can do?
-
Not really. Sadly, breaking the builds seem to be the only way to "motivate" some people, so I'm going to use it more often (better breaking the builds now, instead of discovering it's totally broken after 5 months or more - see the 600D screenshot, for example).
-
I'll break all the nightly builds for which I don't have a raw_diag screenshot.
Noooooooo... Quick, where's my 6d ;D
I downloaded the raw_diag.mo and made the screenshot(see PNG) you asked for(plus some offset info):
https://drive.google.com/folderview?id=0B1BxGc3dfMDaazVGRF9JOTF2VzQ&usp=sharing
It's not 100% perfect aligned as you can see, made this with the 18Juli2014 Nightly build for 6d.
The offset used in this Magic Lantern build seems, Active area: 50, 84, 3708, 5554 (crop size 5470,3658).
The offset seen in exif info from normal Canon CR2 is:
Sensor Left Border = 84
Sensor Top Border = 50
Sensor Right Border = 5555
Sensor Bottom Border = 3697
Which results in an image 5472 width and 3648 Height
Hope this is enough data to keep the 6d alive in the nightly builds :D
-
Hope this is enough data to keep the 6d alive in the nightly builds :D
Nope, it should be corrected. The test should be done with the fullres-silent-pics branch (the offsets changed).
With these results, ETTR on this camera is also not much better than random exposure.
-
I'm no coder, I have no idea how to correct this ?
To do this test with the fullres-silent-pics branch, I probably need to compile I guess :-[ (which is beyond my knowledge...)
Or is there somewhere some place where there is a build for the 6d with fullres-silent-pic branch ?
Audionut and NikFreak, please, help is needed over here, I guess...
-
@Alex,
Tried the raw_diag.mo (downloaded it today) with the newest Nightly build for Canon 6d.
But it doesn't work, it says in the module tab:
Wrong version, (v5.0, Expected v6.0)
-
1100D uses edmac channel #2
(https://bitbucket.org/dmilligan/magic-lantern/downloads/1100D_OB-ZONES.png)
first picture works fine, take another and I get Err80 (no logs).
EDIT: the error seems to be related to dumping the raw buffer as DNG (I guess this is b/c dng code modifies the raw buffer and it looks like it's a little too big)
-
That's quite possible (had this problem on 5D3). You could reduce height a little - check EDMAC channel 2 in Debug menu to find the exact size. You may have to add 1 to the height displayed there (upload the EDMAC screenshot and I'll tell you).
Nice fonts :D
For 6D, a good starting point for the offsets is here: https://bitbucket.org/hudson/magic-lantern/commits/e261cbbbdf25a380f74c15ddb671952518693b26#comment-1089535 (reduce the resolution to be able to read everything).
-
reduced the buffer start offset by 3 rows and fixed the skip offsets, no more crash when saving DNG
#ifdef CONFIG_1100D
// from debug log: [TTJ][150,2551,0] RAW(4352,2874,0,14)
width = 4352; //From TTJ Log
height = 2874;
skip_top = 16;
skip_left = 62;
raw_info.buffer += width * 14/8;
#endif
(https://bitbucket.org/dmilligan/magic-lantern/downloads/1100D_OB-ZONES_fixed.png)
-
Nice fonts :D
They look even better nearest neighbor on the tiny 1100D screen :P
-
Do you still need to skip one line? (check raw zebra colors)
If it's like this, it's correct:
(http://s21.postimg.org/6s3h9s4jb/VRAM4_700d.jpg)
If it's like this, it's wrong:
(http://s29.postimg.org/b7d18c4tz/VRAM9_Unified_600_D.jpg)
-
I checked the DNG colors, they are correct.
-
I'm not expert but I was wondering. Is it transfer speed to card that preventing record in higher FPS or just sensor won't let it? If it is transfer speed then can be pictures shrink to low resolutions with bicubic or bilinear interpolation (Instead of line-skipping) in camera then save to card. With this we can eliminate moire and aliasing at least mostly. It might be discussed earlier or not. Because it might be stupid idea, I don't know.
There is one more idea that might be stupid. Can HDMI connection be used for transferring raw data like Alexa's T-Link? As you know Alexa uses dual link SDI as a data connection to Codex. May be HDMI connection can use for something like that. HDMI 1.0 has 5.0 Gbit bandwidth in theory. 5120x2700 (5K) 14 bit 24p raw fits in that limit. I know still need a compatible device that hasn't been invented yet. Just ideas...
-
@Levas:
For 6D I compiled for you "fullres-silent-pic" branch but before compiling I made changes to "raw.c" as a1ex and 1% have been discussing on bitbucket (https://bitbucket.org/hudson/magic-lantern/commits/e261cbbbdf25a380f74c15ddb671952518693b26#comment-1092792):
First I defined edmac like discussed above:
#if defined(CONFIG_5D3) || defined(CONFIG_700D) || defined(CONFIG_6D)
#define RAW_PHOTO_EDMAC 0xc0f04008
#endif
and also changed height + skip-values according to a1ex's suggestion on bitbucket discussion linked above:
#ifdef CONFIG_6D //Needs check from Raw dump but looks aligned.
width = 5568;
height = 3722;
skip_left = 72; //Meta Data
skip_right = 0;
skip_top = 52; // Meta Data
#endif
Here's the zip to try for you @Levas:
http://www59.zippyshare.com/v/38767089/file.html (http://www59.zippyshare.com/v/38767089/file.html)
Please lemme know if you have no time to do the necessary test before a1ex will drop 6D out of this
Before anyone gets the idea to use thos for anything othe rthan 6D: I had to use fake stubs and defines for some cameras to get this compiled. So this will only work with 6D.
Edit: fixed link with correct zip containing modules
-
@NikFreak, Thanks for helping :D
Downloaded the build in the link, but the modules folder only contains one file (6D_113.sym) for the rest it is empty...that's not good is it ?
I expected at least a silentpics module and raw_diag module.
Can you take a look at it ?
Happened before, a build with no modules, audionut said this about it:
@nitfreak, for future reference, run make in the source directory, then browse to the required platform directory (6D.113 in this case), and run make zip.
This will compile the modules and produce a nightly type zip in the platform directory.
-
Yeah I did it like Audionut instructed. But you are right about missing modules. They don't get added cause of some missing rst2html:
Building module silent...
REBUILDING
[ README ] module_strings.h
cat README.rst | grep -v -E "^:([^:])+:.+$" | rst2html --no-xml-declaration | python ../html2text.py -b 700
/bin/sh: 1: rst2html: not found
(<type 'exceptions.SystemExit'>, SystemExit(1,), <traceback object at 0x2ad947187368>)
make[4]: *** [module_strings.h] Error 1
-
Do you know how to solve this ?
-
Done! had to fix my docutils:
Here you go http://www59.zippyshare.com/v/38767089/file.html (http://www59.zippyshare.com/v/38767089/file.html)
Sorry again.
-
Downloaded your build, it has indeed modules now :D
RAW_DIAG module is not in it, downloaded RAW_DIAG module from the first page of this thread and put in the module folder.
Unfortunately the RAW_DIAG is not loaded at startup, it says, "OldAPI" instead of "OK",
And displays, "Wrong version, (v5.0, expected v6.0)"
So at this moment I can't do the test Alex asks for...
Is this message for RAW_DIAG module "Wrong version, (v5.0, expected v6.0)" , something you can fix, Nikfreak ?
Or do we need Alex to ask what's going on (Alex is probably working on a newer RAW_DIAG, V6.0, but it's not yet online ?)
-
I have really no clue. I compiled "fullres-silent-pics" branch and what's that about v5.0 / 6.0 I don't know cause I didn't try myself. If a1ex tells what to do I will do and we can do the requested test for 6D. Sorry still freshman over here....
Btw that raw_diag module from 1st page is prebuilt. I have no idea where the sources are so that I could increase a version number in source and compile myself
@a1ex: This is what I did: http://magiclantern.fm/forum/index.php?topic=12523.msg124160#msg124160 (http://magiclantern.fm/forum/index.php?topic=12523.msg124160#msg124160)
Where did I wrong? Can you teach plz?
-
No problem, already glad you could help this far :D
@A1ex, Can you help us out here ?
The RAW_DIAG module on page one of this thread does not work with currently compiled builds.
The module won't load at startup, OldAPI.
It shows the message "Wrong version, (v5.0, expected v6.0)"
-
The version of the module API was bumped up a few days ago (this commit (https://bitbucket.org/hudson/magic-lantern/commits/ae33c8a7addf756b812543cf4f66a8b634767e17)) due to the expectation of bugs resulting from changes in FIO return values. That's why previously-built modules will no longer run.
You should be able to build a new raw_diag.mo yourselves from the iso-research branch, after first locally merging it with the current unified. If merging is difficult, you might be able to just copy over the raw_diag source files from that branch to the current unified and build it that way.
-
Thx for your response. Merging gets me headache. i am still uncomfortable with hg mercurial compared to using git / github. I tried copying raw_diag into unified and tried compiling as you suggested but that gave me compile errors. Dunno at least me and Levas tried. Hopefully this is honored and 6D won't be thrown out. Maybe ayshih you can instuct me or upload a raw_diag.mo for us so we can use my built zip from "fullres-silent-pics" branch from today which I compiled for 6D??
-
Yeah, I'm much better at Git than Mercurial too.
I won't be back at my ML build environment for many many hours, so hopefully someone else can figure out how to get raw_diag.mo to build in the meantime. If you'd like, you can PM me the compile errors you're getting, but I may not be able to diagnose them from remote.
-
Updated the link, should be OK now.
You can simply compile from iso-research branch and take the .mo file; the branch is up to date.
-
Thanks, Nikfreak, Ayshih and A1ex!
It works finally :D
The Cyan box fits perfectly inside the noisy borders (for 6d that is).
See "OB-Zones-6d-31Juli2014.png" on my google drive
https://drive.google.com/folderview?id=0B1BxGc3dfMDaazVGRF9JOTF2VzQ&usp=sharing
Although, I don't get the bright noise on the bottom left in the white box, what's that A1ex ?
-
Looks alright. Can you also take a screenshot showing some overexposed raw zebras?
-
How do I take a Screenshot of the zebra's ?
I Did try to use the "screenshot -10s" option in the Debug menu, but the zebra's don't show up on the screenshot written on the memory card...
The zebra's do show up on my camera LCD screen, but their not visible in the screenshot ?
-
Wait, problem solved.
Zebra's were on Luma, now they're on RGB and they show up in the screenshot.
-
For Raw zebra's screenshot from the 6d:
Check my google drive for "Raw-Zebras-6d.png"
https://drive.google.com/folderview?id=0B1BxGc3dfMDaazVGRF9JOTF2VzQ&usp=sharing
Edit, wrong screenshot
-
Zebras must be RAW, not YUV.
Also, they must be in photo mode, not LiveView. Either the silent full-res or the regular photo mode, they are the same.
-
Took 2 pictures the normal way and with picture review it makes a colored overlay of the overexposed areas.
See "Raw-Zebras-6d.png" and "Raw-Zebras-6d-.png"
https://drive.google.com/folderview?id=0B1BxGc3dfMDaazVGRF9JOTF2VzQ&usp=sharing
-
Alright, it's correct then :D
-
Whoehoe!
So we're done (for) now 8)
Full-res-silent pics will be introduced in the nightly builds soon and Canon 6d will be in those nightly builds :D
Thanks everyone who helped
-
Now you're gonna kill me: I've deleted a bunch of code, is it still working?
https://bitbucket.org/hudson/magic-lantern/commits/5925e186ed67
You no longer need to check any offsets; if there are problems with the new method, silent pictures and zebras would be totally broken (easy to notice, unlike the possible problems caused by wrong offsets).
-
Still the skip offsets were worth it plus I learned to correct some mistakes
-
I've deleted a bunch of code, is it still working?
If it ain't broken, don't fix it! >:(
No kidding ;D , you probably had a good reason for it, like cleaner code...
Do I have to test some stuff or are you asking Nikfreak to look at the code ?
-
Same game. Fullres-silent-pics branch needs to be compiled and retested. we do this tomorrow ok?
-
Yeah, but this time there's nothing special to test - just see if it works.
-
Understood i am just at the dmspy branch with your hints from toay so I will recompile fullres-silent-pics tomorrow. got it!
-
600D
Compiled the new stuff from fullres-silent-pics. Compiling mlv-rec gives this error:
mlv_rec.c: In function 'raw_video_rec_task':
mlv_rec.c:3080:13: error: implicit declaration of function 'FIO_SeekFile' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make: *** [mlv_rec.o] Fehler 1
I have to disable some more features, before I can test anything (mem-size too big again). Will search later, maybe tomorrow...
Edgar
-
Nikfreak when you compiled it, can you also test it ?
I've got permission to take photos at a dance festival this saturday 8)
Don't want to risk bricking my precious 6d one day before this festival takes place... :P
If you don't want to test it, I'll be able to do it, but then it will be probably monday.
-
No problem
-
Compiled the new stuff from fullres-silent-pics. Compiling mlv-rec gives this error:
Pull the branch again; the fix on unified (this commit (https://bitbucket.org/hudson/magic-lantern/commits/ac953260397f25c65d54265f3e234a058952f300)) looks to be merged in now.
-
Now you're gonna kill me: I've deleted a bunch of code, is it still working?
Yup, still works on 50D.
-
600D after todays changes.
(http://s16.postimg.org/o461f381x/VRAM0_600_D.jpg)
(http://s14.postimg.org/hh3xwy6w1/OB_ZONES_600_D.jpg)
-
"Compile ML (both core and silent.mo) from the fullres-silent-pics branch. For 5D3-123, merge the two branches locally first."
has someone successfully merged the core&fullres-silent mode files for 5d3 FW123?
is it possible to get the file somewhere for testing? link?
or will there be a nightly/alpha version in the near future?
thanks!
-
Same question for 6D.
-
Please add it to the 5d3 1.1.3 nightly build for test. Thanks
-
And here's how I'll fix it. I'll merge the full-res silent picture branch next week, and I'll break all the nightly builds for which I don't have a raw_diag screenshot.
in case you are not following along rrrmusic
-
Just for fun, I wanted to test the power of dmilligan's amazing Adobe Bridge Script for time-lapse. And to compare AV mode vs ETTR . So I tried shooting Full-resolution silent pictures in AV mode :P Well it seem to shoot by looking at the LCD but did not save as DNGs or MLV. Am wondering if I miss a step or is it not possible at the moment. I had AV mode on and Auto ISO on ETTR off .
-
Is here somewhere a tutorial for noobs how to "install" or compile this ful-res mod to a eos 600D ?
I tried something Mercurial but i couldn't figure out what am actually doing :) Thanks !
-
Getting started with development (http://www.magiclantern.fm/forum/index.php?topic=991.0)
-
I'll merge the full-res silent picture branch next week
Alex, I thought that the above quote meant that it will become available in the nightly builds, is it ?
No need to rush, I have a build for the 6d where I can take full-res silent pics with. (but it's not a complete build of all the magic lantern options/modules available ;))
I'm keeping an eye on the nightly builds for full res silent picture option :D
-
Do you mind if I'll delay it by 1-2 weeks? Right now there were too many crashes reported for my taste (which I couldn't diagnose), and I don't want to flood the forum with support requests. And I'll be away next week.
Sorry about that.
-
No problem, take your time.
Just wanted to make sure that I understood it right, that this function will eventually become available in the nighly builds.
-
Forgive me if this has been asked before: is it the intention for the full res (DNG) silent to have a crop mode?
That is, like RAW video, so that you get the x3 multiplier effect on a lens, eg my 500mm becomes a pseodo 1500mm, albeit with less resolution.
Such captures will be acceptable for many uses, ie stills for digital and timelapses etc.
-
Unlike with raw video, you have the FULL resolution available.
That's why it's called, full res silent pics.
You can crop all you want in post ;D
With video, you do not have all pixels/resolution available in normal mode, because of the pixelbinning, so 3x zoom has is use for video.
-
Of course!
How stupid of me!
I must engage my brain in future, before posting!
:-o)
-
Continuous writing without return live view :
-
Continuous writing without return live view :
If you can do this 24 times for second, I thinks A1ex give you an Oscar Lantern.
-
If you can do this 24 times for second, I thinks A1ex give you an Oscar Lantern.
Possible but the resolution will be such as live view crop mode.
-
work on 50D ? i dont see this in my 50D :-\
-
work on 50D ? i dont see this in my 50D :-\
Compile source code for yourself or wait for it to be included in Nightly Release... it's experimental.
-
High Five for Greg!
I guess thats gonna save a lot battery life when you shooting Timelapse.
-
High Five for Greg!
I guess thats gonna save a lot battery life when you shooting Timelapse.
battery / and / make timelapses more fluent, connected due to not much time between shots
-
battery / and / make timelapses more fluent, connected due to not much time between shots
Sorry? What do u wanted to say?
-
Sorry? What do u wanted to say?
I'm saying that it's not only going to be beneficial for battery life, but also give the artistic tool of making timelapses more fluid (less segmented) aesthetically, because one frames will connect much closer to each other (not so much time lost between shots) :)
-
Yes, ofc. Lets hope u r right. Right now i cant go under 5s intervall :/
-
Yes, ofc. Lets hope u r right. Right now i cant go under 5s intervall :/
Me neither, but I got to say this 5-6 sec delay gives quite a charming flicker to the video. First time I've seen it it's quite a nice change from the creamy-smooth timelapses I'm used to through MLV timelapses.
-
Possible but the resolution will be such as live view crop mode.
Hypothetical question:
Do you think there is any way to shoot raw video in full res, but process it as 1080p (so that the camera is able to capture 24 fps)? The 5d mIII already does that in a certain way, it uses the full sensor (=> no line skipping) for shooting video, but processes it as 1080p. The result is almost no alyasing and moire.
My 50d produces a lot of alyasing, that's why I'm asking.
-
Hard to tell if the other DSLR's from Canon can do video without lineskipping.
Probably depends if the (vertical) pixelbinning is done in hardware or software. (if it's done in hardware, good chance that the option is not available in other dslr's)
There are a lot of settings in camera where picture scaling and sensor readout can be controlled.
Take a look at this topic:
http://www.magiclantern.fm/forum/index.php?topic=10111.825
It is possible to not do any lineskipping, but you get only 1/3 of the picture height, cause nothing is scaled/averaged/binned, and it stops by about 1080 pixel height.
Also it seems possible to do full sensor readout in live view, but you (probably) never gonna get 25fps. ( on 6d full sensor readout gives 4,7 fps. )
-
Read the quote by dmilligan in the first post here: http://www.magiclantern.fm/forum/index.php?topic=950.0
-
we have this in a nightly yet?
-
are we there yet?
-
Great Job,
Maybe i misunderstood Greg "24fps resolution like live view crop" but not in live view?
Best
David
-
Hi ! Is there any chance I could get a build for 600D? Promise I'll learn to compile myself too :)
-
Just some short Info. 600D 19July Nightly + silent.mo from dmiligan ist still working great for me. Taking 500 pictures without any dropframes and saves same into seperat .mlv/.m00 files. Extracting with mlv_dump.exe and works perfectly. Dont wanne miss or lose this in my Canon!
Here is one framegrab from a little "ML Full Res Silent Pic" promo video im putting together...
(http://i.imgur.com/pAeHXxy.jpg)
-
@Attero Is there even a build from 19th of July? I can only see the one from 18th and from 22nd .
-
Can somebody please provide me a build for the 5D MKII ... I'm aware of the risk. :-)
-
I have been thinking about the possibility of using the silent picture mode for an auto-guider setup (exp. time of only 15 seconds, but fine for my purposes) using an 1100D, but since the build for it is broken, I was out of luck. I only considered the simple mode (no high res), and I thought that that would be available, so I downloaded and built the code.
Alas, it seems that the build is broken for all things silent for 1100D (simple, etc.) hence I was not able to see if what I had in mind would work (I need the LV active while the image is being exposed).
Then, I have reverted to an old version of silent.c and commented out the offending lines. The build was a success, and while in LV I could activate the silent picture. However it just says that it is taking a frame, but hangs. A .dng file is written on the card, but it is black and the file size is too small. I don't exclude the possibility that I have commented out more than was permissible though ;D
I guess I will have to wait until the build is enabled; in the meantime I can contribute by sending a test .raw image for the 1100D (if still needed). It would be good if the build was only broken in such a way that only the new silent functionality was missing, and the older silent features were still there for the 1100D... 8)
-
but since the build for it is broken
What do you mean by "broken"? Builds failed to compile?
https://builds.magiclantern.fm/jenkins/job/1100D.105/
Or do you mean the silent pic bit?
-
Yes, only the silent pic part of the build. I was referring to the comment made by a1ex earlier in the thread that he broke the silent pic part of the build to motivate people. Otherwise, the build compiles just fine. Sorry for the misunderstanding.
-
http://www.magiclantern.fm/forum/index.php?topic=12523.msg124853#msg124853
tells quite a different story ...
Do you mind if I'll delay it by 1-2 weeks? Right now there were too many crashes reported for my taste (which I couldn't diagnose), and I don't want to flood the forum with support requests. And I'll be away next week.
Sorry about that.
-
The silent pic module depends on the LiveView RAW backend, which is not yet enabled on 1100D. The full-res functionality doesn't depend on that, but the module was written with LV RAW in mind.
You can try the raw video branch ( http://www.magiclantern.fm/forum/index.php?topic=1009.msg119468#msg119468 ). It needs some small cleanups and it's pretty much ready for integration in the nightly builds if I remember well.
-
Got it. Thanks Walter, and thanks a1ex for the explanation and the suggestion. I know now where I went wrong. I looked at the code for a short while before starting to hack, and I have probably commented out the references to the LiveView RAW. Of course, then the consequence was that the silent pic was not working as intended. I believe what sent me in this direction was that I saw somewhere on the forum that someone was able to use silent pic on 1100D (simple, before the full res ability was added), so I tried to "revert" back to that state (unsuccessfully).
I will try the raw video branch and see how that goes.
-
I have it working on 1100D, one thing you can do is use WEAK_FUNC for all the LV raw backend functions in silent.c (if you do that, LV raw wont work, but fullres still will), but you'll still need the updated skip offsets (and perhaps the PHOTO_EDMAC too, I think it is the same as before). I have it working in my repo (https://bitbucket.org/dmilligan/magic-lantern), there's an 1100D-Fullres branch, but I've made other changes and disabled a bunch of stuff so I could use adtg_gui, so perhaps go back a couple commits.
-
Thanks dmiligan! I think I have enough things to keep me busy for a while. When I have results, I will report back.
-
hello,
as i can not build my own nightly like many others would it be possible that someone can post a link to a 5D mk3 build with Full Res Silent Pics enabled?
the download section only provides a nightly from 7 aug. and the full res was not implemented within the build.
thank you very much.
-
I have tried the approach suggested by a1ex, built the raw video branch, and the silent functionality works (the image is distorted and with black borders, probably because of the pix offsets being wrong for the 1100D). I could not build the branch referred to by dmilligan (probably checked out the wrong commit).
Anyway, with what I have right now I can't really do what I intended to. Namely, the exposure duration of the silent image is always the same, I can't seem to take a silent picture with a longer exposure (say 5 seconds). a1ex mentioned that longer exposures should be possible (at the first post of this thread), but that may apply only to full res silent pics. I activated LV, changed the exposure setting back and forth, but the silent pic was always recorded immediately, there was no perceptible "accumulation" time before the save message even at exposure settings of 5-10 seconds. I have tried both .raw and. jpg formats.
For the "autoguide mode" to be useful, I would need to have a silent pic with exposure time of say 10 seconds (the longer the better) while the LV shows uninterrupted video on the screen. Not sure if this is possible (was not mentioned whether the display is refreshed during a long exposure silent image).
-
Namely, the exposure duration of the silent image is always the same, I can't seem to take a silent picture with a longer exposure (say 5 seconds).
FPS override
I would need to have a silent pic with exposure time of say 10 seconds (the longer the better) while the LV shows uninterrupted video on the screen. Not sure if this is possible.
No, that is impossible. From what data would the display be updated while capturing an image? The sensor can't make two different exposures at the same time.
-
No, that is impossible. From what data would the display be updated while capturing an image? The sensor can't make two different exposures at the same time.
I did not use FPS override because I was hoping that the readout of the sensor was done in such a way that a long exposure image could be captured while in uninterrupted LV (non-destructive read), but I guess I was hoping for too much :D
Maybe something like this would be possible if we could control the readout such that odd pairs of lines are read with 25 fps for the LV display, and the rest are kept on hold for a user defined exposure time. Before coming across this thread on the forum, I was reading around to find out whether this was possible; probably not, and even if it were, it is highly unusual and would be very time consuming to research and implement. In conclusion, it was a nice idea, but too ambitious. Thanks for the support.
-
I did not use FPS override because I was hoping that the readout of the sensor was done in such a way that a long exposure image could be captured while in uninterrupted LV (non-destructive read), but I guess I was hoping for too much
Even if it was possible, and with using zoom mode to get an unscaled image of the guide star in the field, it looks it would be hard to compute a precise drift analysis on fly with taken silence picture in parallel. Maybe we will get some black out during several seconds because of silence pictures computation.
By the way, using ML as an autoguiding system should be very nice. Without using the camera for imaging, just as a guiding camera.
But is there a way to send ST4 commands (0/I output orders in 4 ways) directly from the body through the USB ?
-
By the way, using ML as an autoguiding system should be very nice. Without using the camera for imaging, just as a guiding camera.
But is there a way to send ST4 commands (0/I output orders in 4 ways) directly from the body through the USB ?
I have thought about this too. I think you'd need a arduino or something to act as USB PTP host and translate commands. The other option would be a photo-transistor taped to the LED, and some kind of decoding circuitry, then you could send commands via LED blinks.
-
SpcCb: I have a specific astro-photo setup, and was not planning too long exposures. I needed the LV video as a reference (with a cross-hair overlay perhaps) to do periodic corrections manually (my mount is cheap and it tends to lag after a few seconds at the focal length I use), so not a proper autoguidng setup, but an exploration of the possibilities using what I have. And the silent image accumulating during that time would have been the exposure I need. At full frame there would have been probably an issue with detecting movement of the guide star, but there is an ability within ML to show the 5x zoom in a separate window during the LV, so maybe that would have been enough.
dmilligan: Indeed, there is a Raspberry PI project out there which takes an image input and does the rest (calculations and sends control signals to the mount). To do all that in ML may turn out to be too much for the camera.
To come back from OT, since I don't have a guidescope, my plan was as stated above. If per line readout of the CMOS can be achieved, then some possibilities exist, but I understand that it would take too much effort. ML is already impressive enough.
-
Ah yes, through the PTP protocol it should be possible. An Arduino also should be enough to do protocol conversion (PTP -> ST4).
aleks > What is the ratio between 'how the mount can track fine' and 'how long exposures are expected'? (should be interesting to know the sampling on the imaging camera and an tracking error log on the mount) Because if it is only a question of polar alignment drift compensation _every nn seconds_ there are other solutions (if you see what I point :) ).
-
What is the ratio between 'how the mount can track fine' and 'how long exposures are expected'? (should be interesting to know the sampling on the imaging camera and an tracking error log on the mount) Because if it is only a question of polar alignment drift compensation _every nn seconds_ there are other solutions (if you see what I point :) ).
The setup is very basic, it is a Meade ETX Alt-Az mount which has poor tracking when the camera is attached. It can manage only 3 seconds of good tracking before it needs a correction. My goal is to increase the S/N of the images, hence I wanted longer exposures on the cheap, and wanted to try guiding while exposing, hopefully using silent pics with ML.
-
With an Atl-Az mount it will be useless to try to guide because of the field rotation.
And even with a very high S/N (hundred of silence pictures registered for example), you will be limited by the short exposure time before that the rotation was visible : You could get a very high S/N but with a low magnitude. (plus I don't speak about FPN inter-correlation if you don't dither between exposures)
The first thing to do should be to DIY a Lat. support to pass the mount on equatorial.
(or to buy it, but well.. I don't want to promote something)
Beside, Full Resolution Silent Picture is very interesting in planetary imaging. Specially with some ADTG optimizations to get the best dynamic and a low [none] electronic amplification.
-
I can't succeed in averaging multiple dng's in a full res silent picture MLV file.
I did some Full-res silent shooting with MLV output (Got a build from August 8 for the canon 6d).
Now I got multiple files M00, M01, MLV etc.
Trying to process them with mlv_dump on mac didn't work. (got newest mlv_dump build from August 31)
This is what I get:
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000000.MLV'
- Rewrite MLV
- Output only one frame with averaged pixel values
- Output into '00000000_frame_'
File 00000000.MLV opened
File 00000000.M00 opened
File 00000000.M01 opened
File 00000000.M02 opened
File 00000000.M03 not existing.
Processing...
/Users/wij/Documents/Foto's en video's/Video/2014/2014-09-16 - Darkframes/10seconde/Average-mlv.command: line 7: 619 Segmentation fault: 11 /usr/bin/mlv_dump -o ${BASE}_frame_ $FILE -a
logout
[Proces voltooid]
So I thought, let's do it again, but with a maximum of 90 pictures, so I end up with one single MLV file.
Also didn't work:
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000001.MLV'
- Rewrite MLV
- Output only one frame with averaged pixel values
- Output into '00000001_frame_'
File 00000001.MLV opened
File 00000001.M00 not existing.
Processing...
/Users/wij/Documents/Foto's en video's/Video/2014/2014-09-16 - Darkframes/Average-mlv.command: line 7: 704 Segmentation fault: 11 /usr/bin/mlv_dump -o ${BASE}_frame_ $FILE -a
logout
[Proces voltooid]
-
@Levas: Why would u average, lets say, 400 frames or even 90? If u want to extract single dng's u have to comand "--dng" but i guess u know that. If its only for experimental purpose, extract the dng's, develop them with, lets say, LR and average them with Photoshop. Maybe u could upload the 90 Frame .mlv so others can try to average the file`?
PS: I put together some sequenzes i've shoot with the new modul. I hope u enjoy this short clip.
A High-Five to A1ex, Dmilligan and the whole Magic Lantern Team for this modul!
-
I want to average a whole lot of dark frames for dark frame subtraction.
When I shoot a time-lapse at night, stars in the sky, I shoot at iso 6400 (about 10 seconds exposure time).
Now these pictures of course contain noise 8)
Now I've a bunch of photo's taken with the same iso and exposure time and with the lens cap on...so called dark frames, these frames contain nothing but noise...
Now I want a single dng file which represents the averaged out dark frames.
This single dark frame I can subtract from the normal time-lapse photos to reduce noise.
The single MLV with the 90 pictures I have 2,5 GB... so I better make a smalles one with less photo's to share :P
-
"PS: I put together some sequenzes i've shoot with the new modul. I hope u enjoy this short clip."
I like the clips at the end with the low sun above meadows :D
See on youtube that you did things in 4k timeline.
But the video on youtube in 1080p looks very compressed, I expect far more detail with your workflow.
What where your export settings in premiere, which codec/format and what bitrate ?
-
Ahh, ok now i got the point.
Export settings were 1080p | 25fps | h.264 | High Profil | Level 5.0 | VBR1 | 15mbit/s avg. 35mbit/s max.
I uploaded the clip at 1080p because my Inetconnection is very bad, 2mbit - 45kb/s upload...
And yea, the Youtube compression sucks... dunno what to do, to let the video look more crisp and clean. Any tips or hints?
Im going to upload the clip to vimeo very soon. Lets see what they do with the file.
-
Nothing wrong with the export settings, so it's probably the youtube compression.
And yea, 2Mbit sucks, same here, 2,5Mbit max, is all I can get :'(
-
go for 24fps, that leaves more bitrate for actual frame, meake it as clean you can - youtube hates grain, other - use vimeo :) and preferably get better internet if you can.
-
Could someone please compile this for the &600D/Ti3 and post the link here? I would really appreciate that.
-
Hi guys! My 5d3 crash quite often wit this module. Like every 100 pics. Here is the log:
ASSERT: GetMemoryAddressOfMemoryChunk( GetFirstMemChunk( pMem1AllocateListItem->hMemSuite ) ) == pMessage->pAddress
at SrmActionMemory.c:1505, task RscMgr
lv:0 mode:3
Magic Lantern version : Nightly.2014Sep21.5D3113
Mercurial changeset : 1a0167779348 (fullres-silent-pics) tip
Built on 2014-09-21 07:51:37 UTC by magiclantern@magiclantern-VirtualBox.
Free Memory : 139K + 3738K
Shooting DNG every 10 sec to Lexar x1000 CF card
-
So far I've got these crashes only when press shutter halfway *while* a silent picture was taken. There is a race condition when switching the GUI mode to QuickReview - Canon code unlocks the GUI and the half-shutter press returns to LiveView, where it can't continue, because the resources are already allocated for picture taking.
I've never got the error during a timelapse (~300-500 frames).
-
Consistently crash here with built-in intervalometer. I do not touch the camera at all.
-
Can you post your SETTINGS directory?
-
Sure:
https://dl.dropboxusercontent.com/u/17452116/settings-silientpic-crush.zip
-
I have been out out coding for about 8 years LOL but I am going to see if I can get this built for my 60D I will let you all know what works and what does not.. My build environment is being finicky.. If I can get it working. I am on Saturday going to be in the mountains shooting start time lapses this might be handy.. :) With a 50mm f1.8 at 6400iso to expose the milky way I need a 14 second exposure.. So considering the limit is 15 seconds. This may work..
-
Hi All,
I've searched the forum (and also found 46 min youtube video) on how to compile ML features.... but it seems very complicated for me. Can anybody please help to compile this for 600D or 5D Mark III?
-
Yah its not fun I have been banging my head against the wall for 2 days. Would love a build for my 60D but I want to learn. Still if any one feels like building one for the 60D while I bash my head against the wall I am all for it..
I am getting hung up with.. The following I have searched high and low and tried a ton of different things. This is actually quite a bit of progress from what I had. Note I do do a make clean prior. Also this is on a mac.
brians-mac-mini:fullres-silent-pics brianhursey$ make 60D
make -C /Users/brianhursey/Code/fullres-silent-pics/platform/60D.111
[ VERSION ] ../../platform/60D.111/version.bin
[ CPP ] magiclantern.lds
/bin/sh: -v: command not found
make[1]: *** [magiclantern.lds] Error 127
make: *** [60D] Error 2
brians-mac-mini:fullres-silent-pics brianhursey$ cat Makefile.user
ARM_PATH=~/Code/gcc-arm-none-eabi-4_7-2013q2
ARM_BINPATH=$(ARM_PATH)/bin
GCC_VERSION=4.7.4
CC=$(ARM_BINPATH)/arm-none-eabi-gcc-4.7.4
OBJCOPY=$(ARM_BINPATH)/arm-none-eabi-objcopy
AR=$(ARM_BINPATH)/arm-none-eabi-ar
RANLIB=$(ARM_BINPATH)/arm-none-eabi-ranlib
LD=$(CC)
HOST_CC=gcc
HOST_CFLAGS=-O3 -W -Wall
UMOUNT=echo
CONFIG_TCC = y
CONFIG_MODULES = y
CONFIG_CONSOLE = y
PYTHON=python
brians-mac-mini:~ brianhursey$ cat .bash_profile
# Set architecture flags
export ARCHFLAGS="-arch x86_64"
# Ensure user-installed binaries take precedence
export PATH=/usr/local/bin:$PATH
# Load .bashrc if it exists
test -f ~/.bashrc && source ~/.bashrc
if [ -f $(brew --prefix)/etc/bash_completion ]; then
. $(brew --prefix)/etc/bash_completion
fi
export PATH="$PATH:$(brew --prefix coreutils)/libexec/gnubin"
Also /bin/sh does esxist..
brians-mac-mini:fullres-silent-pics brianhursey$ /bin/sh -v
sh-3.2$
-
Yah its not fun I have been banging my head against the wall for 2 days. Would love a build for my 60D but I want to learn. Still if any one feels like building one for the 60D while I bash my head against the wall I am all for it..
https://bitbucket.org/mk11174/magic-lantern-fullres/downloads/magiclantern-Nightly.2014Sep23.60D111.zip (https://bitbucket.org/mk11174/magic-lantern-fullres/downloads/magiclantern-Nightly.2014Sep23.60D111.zip)
Hi All,
I've searched the forum (and also found 46 min youtube video) on how to compile ML features.... but it seems very complicated for me. Can anybody please help to compile this for 600D or 5D Mark III?
https://bitbucket.org/mk11174/magic-lantern-fullres/downloads/magiclantern-Nightly.2014Sep23.600D102.zip (https://bitbucket.org/mk11174/magic-lantern-fullres/downloads/magiclantern-Nightly.2014Sep23.600D102.zip)
-
You sir are awesome..
I have to now figure out how to keep live view from turning off on my 60D during time-lapse.. :)
Ahh it was the camera that was turning off. I doubt you can just turn off the lcd during the captures can you? even though I have it dimmed it still is on.. This weekend I am going to be on top of a mountain doing time lapse and every little battery % saved the better... It will be a 1 time deal. :)
-
Thanks you very much, mk11174. I already did some test shots and man this is awesome!!! I can open these dngs directly in Resolve!!!
-
Verry nice work Alex. I was testing the viability of this for my astro photography trip.. It seems I am getting a tad more noise however this could be because Lightroom recognizes the cr2 file and apply noise profile vs the dng? Anways here are to crops zoomed in showing the difference.
Canon 60D 14 second exposure f2.8 6400iso
Normal Capture Non silent:
(https://farm3.staticflickr.com/2943/15334935351_eae8eb69dc.jpg)
Silent picture:
(https://farm4.staticflickr.com/3913/15151397380_decc14a93b.jpg)
You can see some more color noise in the silent picture however still very usable don't you think? Note this is cropped.. No black frames or stacking.
What is the max frame time lapse did any one get?
I did notice one thing interesting. With a 4x ND filter event at 100 iso i got over exposed at 1/15 to be safe. however with the ND filter for some reason I was able to up the shutter speed to around 1/200 without it crashing This caused the exposure to be more in line.. That was very odd because before it would crash if I went that high.. Although the people were blurring so it seems like it was not at true 1/200.. Just wondering if any one noticed this..
-
From what I read on page 1 after 1/10 it stays 1/10 no matter what your settings are. But I can be wrong. I can go up to 1/8000 without crashing, but it's not actual speed.
-
Yah but what was odd was at 1/10 it was blown out but when I went 1/200 it was fine. I switched to non silent picture and the picture was not blown out at the same settings. I will mess around with it some more. Maybe Live view is not handling the ND filter?
-
It's only roughly 1/10; the minimum exposure time is actually a gradient and varies from camera to camera.
http://www.magiclantern.fm/forum/index.php?topic=12523.msg121962#msg121962
-
bhursey > Noise difference is maybe because you use liveview for frame recording; I made some series in deepsky imaging with silent picture and noted that heating of the sensor with liveview activated during a long time just before shooting (and obviously heating of the mother board too) generate more thermal signal on frames.
This issue is also well know without using silent picture.
-
@SpcCb - you mean the sensor heating done before taking the picture, while the camera was in LiveView, right?
(because the silent pic code is the same as for regular photos, just without mechanical shutter movement and without JPG/CR2 conversion)
@bhursey: can you upload the CR2 and the DNG? (I can check the noise levels in octave)
-
Alex sent the link and password via PM. Its a home server and don't want a ton of people hitting it..
I am going to test battery time time-lapse today.. I want to see how long and how many frames I can get on a 32 gig card for practuse for saturday night.. I will update on test results for long time lapse..
-
Noise levels are the same. Another difference is that (at least on 60D) the DNG does not have the bad pixels corrected, but the CR2 has.
So the issue might be metadata; try copying it from the CR2:
exiftool 10260000.DNG -tagsFromFile IMG_1026.CR2
-
Well tested a 4 hour time lapse.. I had 2 batteries. Battery 56% Battery 2 62% and 970 frames before my 32 gig sd card filled. Not bad..
No the copy of the exif data did not do anything. O well I have define and other tools.
-
Hi everybody, can someone compile - or share - Full Res Silent Picture in the last build 1.2.3 ML for 5D Mark III.
I tried lot of times and I'm not good compiling - I read the first post A1ex, believe me... and I tried, ;) .
-
@SpcCb - you mean the sensor heating done before taking the picture, while the camera was in LiveView, right?
Absolutely, activation of the liveview during a couple of minutes makes sensor reach Δt~30°C[1] and Δt~40°C[1] for the mainboard (CPU + FPGA + ASIC + LCD heating) witch participate to the heating inside the body (and the sensor heating by the way).
You can easily see it by monitoring the temperature given by the camera, who is the temperature of the probe in the motherboard (slightly different from the real sensor temperature).
From scratch (ambient temperature) it rises quickly during next minutes when you activate the liveview.
It is not very noticeable _in thermal signal_ with 'not so long exposures', but IMHO silent picture should not used for 'very long exposures' needs in astrophotography or low flux imaging.
However, silent picture is not very interesting with long exposures because it means we don't take a lot of pictures, so no shutter mechanism stress. So...
[1] => tsensor/tambient
-
I would rather no shutter stress.. Also noticed something about every 200+ photos the shutter does flip once, or that could be the mirror.
Has any one tried bulb ramping or like hdr photos.? LOL
-
Is it possible to disable the LCD, while retaining the liveview functionality?
-
Hi Bhursey,
Coincidental that I read you query about HDR photos. I tried the native HDR photo function on my 5DM3 with the ML intrevalometer today morning. Worked like a breeze. However, if there is movement in front of the lens (which is the idea of taking continuous shots anyway), the HDR thingi does not come out as intended since the 3 frames once combined are not aligned.
-
If one of the brackets of the HDR is shooting at a slow shutter speed it will be more pronounced. If there is movement in front of the camera, no matter what you will not get the alignment you desire.
Imagine someone walking in 3 frames. It's impossible for those 3 frames to be the same.
-
Did a few tweaks.
- powersaving for timelapse (like display off, or showing battery remaining time), please test.
- MLV fix: I've changed the file format after starting a timelapse, and got corrupted files (MLV data written into a RAW); should no longer happen
- MLV fix from dmilligan (compatibility with MlRawViewer - not tested, I can't run the latest versions)
- dropped RAW format
The powersave trick works for the 1-minute auto power off, but I didn't test it for the mirror going up after half an hour (that part might not behave the same way, because the camera doesn' turn off).
-
@all
I've added a little note to the first post of this thread. Feel free to redirect people who ask before searching.
Please do not ask for builds in this thread. This thread is for development related feedback only.
If you would like a build compiled, so you can help the Magic Lantern development team by testing this feature and providing feedback, please see this thread (http://www.magiclantern.fm/forum/index.php?topic=12608.0).
@mk11174
Thankyou for providing builds for the community. Please post your builds in the linked thread to help keep threads on topic, and minimise the amount of (eventually outdated) builds scattered throughout the forums. Thanks.
-
@Audionut
No problem :)
-
Did a few tweaks.
- powersaving for timelapse (like display off, or showing battery remaining time), please test.
The battery status does not show very long especially when using MLV format, while its set to DNG you can see it for a couple seconds, but it does show.
-
New version is much more stable on my 5d3. Took 1500 pics and no out of memory errors. Great.
Can we get a sync signal on hot-shoe and PC port when silent pic is taken? Will allow timelapse rails control.
-
The battery status does not show very long especially when using MLV format
Correct; it only shows until file saving is done. I could look at image review settings in Canon menu and use that - useful?
New version is much more stable on my 5d3. Took 1500 pics and no out of memory errors. Great.
Yay!
Can we get a sync signal on hot-shoe and PC port when silent pic is taken? Will allow timelapse rails control.
I have no idea how to talk to the hot shoe. What about placing a photodiode to look at the camera screen? (it will turn on after every picture, so maybe you could program the motor to move one step when the display turns on).
-
cool. confirmed workin on my 5d mark 3 firmware 1.1.3
-
after 1 month of wait i downloaded a version from yesterday 26.09.2014 and i have to report that it is very unstable (fullres silent pic) with my canon 5d mk3 1.2.3 - got some err70 freezes while shooting (never got them before) .. will post the log today. thank you.
-
Now you understand why it's not yet in the nightly?
-
@swinxx
http://www.magiclantern.fm/forum/index.php?topic=12608.msg129663#msg129663
mk11174 uploaded a new version for 1.2.3 which may work better
-
thx. the updated version works, but i got too many err70 freezes, so i probably have to wait a little longer. greets.
-
Correct; it only shows until file saving is done. I could look at image review settings in Canon menu and use that - useful?
It is nice to know about the battery for sure, but since I guess most people will use the MLV option, they won't have time to read the battery info because at least on the 700D it is just a flash, so if it was able to be adjusted say as long as the Canon image review, then that would be good idea for sure so it can be useful in MLV saving mode.
-
Any user getting the black Raw Error screen, please double check you have your picture quality set to RAW.
-
One thing I notice on the 550D because the LED tells me things is if you load FullRes and take a fullres silent picture, then turn off FullRes then turn off cam, it looks like task is looping, because after maybe 10 seconds the led starts blinking 1 flash every few seconds.
If you just load FullRes and don't take a picture and just turn it off, it does not loop any task, it is only if you take at least 1 fullres silent picture and then turn it off.
And of course after you try to load camera again it says it crashed so it cant load modules and then you have to restart.
So, at least on the 550D, if you use Fullres you will need to take battery out after your done using it and turn off camera to shut the loop off.
And to confirm, this does not happen on the 700D, no lights blinking and no errors loading camera on next boot, so nothing looping on this camera.
UPDATE!, Also on 550D as far as the task looping, I notice this only happens in PHOTO MODE, even though it is only really meant for PHOTO MODE, I tried it in MOVIE MODE and no looping happens after taking a silent picture and turning cam off. You have no control of shutter of course in movie mode for FullRes, but at least it might be useful to note that this looping only happens in photo mode.
UPDATE 2! Just to note, none of your new tweaks is causing this issue with the looping task for the 550D, it also does it before your tweak updates, so its not from any new changes you made.
-
I got a black screen and a resulting error 70 code when I held down the shutter button longer than needed taking a picture. Had to remove battery. 5D mark 3 firmware 1.1.3
-
With all these results, I def see why this is not in the nightly, it works really well on the 700D, but it is clear there are many issues with other cameras for sure, so this is good all these tests can be made with these other cameras, maybe it will help to get things fixed so one day it will be stable enough for the nightly, but I am sure the DEVS need more feedback from all users and cameras that test this and good details on what happens and what they do during an error, so anyone that has errors, please post as much info as possible, not just that it crashed or something. :)
-
Yes, sorry. I, ll post the crash log when back home
-
Yes, sorry. I, ll post the crash log when back home
Oh, no problem, I was not referring to you or anything, it was just for everyone.
You let us know that you held button down to long, so that is some detail at least, so def not directed toward you or anyone else, just want to make a note for any users testing it to help speed up the debugging process.
-
Do I put log messages here or at bitbucket somewhere?
Anyway.
5d mark 3 firmware 1.1.3 gave a black screen and a error 70 and a crash log after I tried to press and hold shutter button a while longer than needed. Was thinking maybe I get some longer shutter speeds :P
Crash log
ASSERT: GetMemoryAddressOfMemoryChunk( GetFirstMemChunk( pMem1AllocateListItem->hMemSuite ) ) == pMessage->pAddress
at SrmActionMemory.c:1505, task RscMgr
lv:0 mode:3
Magic Lantern version : Nightly.2014Sep26.5D3113
Mercurial changeset : 81a2fd653497+ (fullres-silent-pics) tip
Built on 2014-09-26 19:53:38 UTC by mathew@mathewubuntu64.
Free Memory : 149K + 3789K
-
Do I put log messages here or at bitbucket somewhere?
I would think here is good.
-
One thing I notice on the 550D because the LED tells me things is if you load FullRes and take a fullres silent picture, then turn off FullRes then turn off cam, it looks like task is looping, because after maybe 10 seconds the led starts blinking 1 flash every few seconds.
Can you record a video to show the issue, and paste your settings directory? I'm trying to reproduce, without success.
Meanwhile I've fixed most half-shutter-related errors, as reported by Danne. Maybe it was related.
-
Can you record a video to show the issue, and paste your settings directory? I'm trying to reproduce, without success.
Ok, in video you will see me reset ML config first so its all defaults since non of that changes the outcome.
I will then take a fullres silent pic and then shut off cam, and wait for led to flash and then turn back on, but for this video, the bug is not letting me enter live view again, until I take bat out and then you will see the not loading modules warning message.
Then I will load module without taking a picture and do same process of restarting without issue.
Then I will do first step once more with same error results.
-
Reproduced.
At 1 second exposure time, it fails. At 0.8 seconds it's fine.
Minimal code for reproducing (no need to enter LiveView):
void* job = (void*) call("FA_CreateTestImage");
call("FA_CaptureTestImage", job);
call("FA_DeleteTestImage", job);
-
I just do that by habit with turning off module. :)
And I guess the long exposure might make sense since in movie mode it does not do it and you have no control of exposure in that mode because you can't go lower than the video frame rate.
Double checked on my 700D with longer exposures, no issue still for that cam at least.
-
If you trigger these long exposures with the intervalometer, it should be fine (cameras affected so far: 550D and 500D).
It seems to conflict with Canon meter. If I wait 5 seconds after last half-shutter press, before taking the silent picture, it's fine. If I wait only 3 seconds, it fails.
-
It seems to conflict with Canon meter. If I wait 5 seconds after last half-shutter press, before taking the silent picture, it's fine. If I wait only 3 seconds, it fails.
Nice catch, good to keep in mind.
-
Using intervolmeter, even setting start and delay between each picture to as high as 15seconds for 1sec exposures still causes issue to happen,, but have not tried with your latest tweak to half shutter yet
-
Indeed, in LiveView it always fails, regardless of the time since the last half-shutter press. My previous test was outside LiveView, and there it appeared to work if the test code was ran at least 5 seconds after pressing half-shutter.
Some more progress: the problem is triggered by DarkCurrentCorrection, which is only executed for 1-second or longer exposures. I've tried to patch the code so it doesn't do this noise reduction step, with partial success: camera shuts down correctly, but you can no longer take regular pictures (bottom bar says BUSY).
patch_instruction(0xff07f6d0, 0x8b07fd32, 0xeb07fd32, "silent NR off");
patch_instruction(0xff07f754, 0x8a0000b1, 0xea0000b1, "silent NR off");
call("FA_CaptureTestImage", job);
unpatch_memory(0xff07f6d0);
unpatch_memory(0xff07f754);
(to run this, you need to merge with the patchmgr branch and include "patch.h")
I think I'll limit the exposure times to 1 second for the affected cameras (550D and 500D so far) for now (unless I'll find a better solution over the weekend).
-
I have tried to compile silent.mo from silent.c https://bitbucket.org/hudson/magic-lantern/src/8ad793b88c3050ed443c64f01741e566d76f316c/modules/silent/?at=fullres-silent-pics (https://bitbucket.org/hudson/magic-lantern/src/8ad793b88c3050ed443c64f01741e566d76f316c/modules/silent/?at=fullres-silent-pics) but got an error
magiclantern@magiclantern-VirtualBox:~/magic-lantern/modules/silent$ make clean
[ RM ] silent.o silent.mo silent.sym silent.dep module_strings.h *.o *.d *.dep *.sym hgstamp
magiclantern@magiclantern-VirtualBox:~/magic-lantern/modules/silent$ make
Updated HGVERSION
[ README ] module_strings.h
[ CC ] silent.o
silent.c: In function 'silent_pic_take_fullres':
silent.c:1005:12: error: invalid use of void expression
silent.c:1067:9: error: invalid use of void expression
silent.c:1068:9: error: invalid use of void expression
make: *** [silent.o] Error 1
magiclantern@magiclantern-VirtualBox:~/magic-lantern/modules/silent$ Please help
-
Please use the full branch to compile:
https://bitbucket.org/hudson/magic-lantern/commits/branch/fullres-silent-pics
Don't simply compile the module. Fully compile to get your nightly zip and try it out.
-
Thank you! But I do not know how to compile full branch...
-
e.g.
mkdir fullresvst
cd fullresvst
hg clone -r fullres-silent-pics https://bitbucket.org/hudson/magic-lantern
cd magic-lantern
make -j2
cd platform
cd 6D.113 (if you wanna compile for 6D)
make zip
Please also read this:
http://magiclantern.fm/forum/index.php?topic=7579.0
You might have to adjust makefile.user.default if you don't have gcc 4.8.3
-
Thank you very much! It works. 5D3.113. There is no any sing about 5D3 after execute "make -j2", but there are many errors. There is no raw_rec.mo in zip. Why? I compiled it in Modules/raw_rec folder
-
Thank you very much! It works. 5D3.113. There is no any sing about 5D3 after execute "make -j2", but there are many errors. There is no raw_rec.mo in zip. Why? I compiled it in Modules/raw_rec folder
If alls you need is the fullres-silent-pics version all up to date just use the build I compiled, nothing has changed since the update.
http://www.magiclantern.fm/forum/index.php?topic=12608.msg129663#msg129663
-
Thanks a lot! But my compilation works too.
-
Great to hear that you got it working!
-
mk11174 sais "If alls you need is the fullres-silent-pics version all up to date just use the build I compiled, nothing has changed since the update.
http://www.magiclantern.fm/forum/index.php?topic=12608.msg129663#msg129663"
It works in my 50D. Thanks a lot!
-
I have some questions:
Is it possible to capture Full Resolution Silent Pictures in Jpeg format? (Live View, Video Mode)
If so, is it then possible to capture Full Frame (5K) in an MJpeg stream? thereby solving the bus/data transfer speed limitation, as well as the Moire problem. (Smaller File Sizes)
I remember reading that one of you guys were working on MJpeg for live view 1920x1080 a long time back.
I own a 5D MKII and 7D.
-
Fantastic A1ex ... been watchin' on the side foaming at the mouth ... Timelapse and Focus Stacking are my bag and this is HUGE for us ...
Is it possible to capture Full Resolution Silent Pictures in Jpeg format?
I agree with this comment as well because although it's handy for Timelapses to have the colour range it's sometimes handy for Focus Stacking to get a decent result, in a small amount of time, using JPGs ... once we get a decent image it would be great to do it again but with the option of DNGs dynamic range ... the work flow at the moment is quite time consuming using DNGs, so JPGs would really speed up write time therefore reducing the focus stacking session considerably ... that would be awesome ...
Thanks for this feature though A1ex ...
I'm gutted I cannot take more than 3 photos at the moment without it crashing/freezing on Full Res ... am I doing something wrong? ...
Gem
-
Well i have over the past few weeks shot about 8 time lapse clips with it. I am still working on them However this one is by far my favorite.. I will post my final composition with once done. Awesome work Alex.
-
e.g.
mkdir fullresvst
cd fullresvst
hg clone -r fullres-silent-pics https://bitbucket.org/hudson/magic-lantern
cd magic-lantern
make -j2
cd platform
cd 6D.113 (if you wanna compile for 6D)
make zip
Please also read this:
http://magiclantern.fm/forum/index.php?topic=7579.0
You might have to adjust makefile.user.default if you don't have gcc 4.8.3
make zip command for 5D3.113 has an error:
Building module raw_rec...
Updated HGVERSION
[ README ] module_strings.h
[ CC ] raw_rec.o
[ MODULE ] raw_rec.mo
[ STRIP ] raw_rec.mo
[ EXPORTS ] raw_rec.sym
00001948 raw_video_enabled
00001978 raw_movie_filename
[ DEPENDS ] raw_rec.dep
Will load on:
5D3, 60D
Not checked (compile ML for these cameras first):
1100D, 500D, 50D, 550D, 5D2, 600D, 650D, 6D, 700D, 7D, EOSM
[ GCC ] raw2dng
[ GCC ] raw2dng
../lv_rec/raw2dng.c:174:5: error: conflicting types for вЂraw_set_pixel’
In file included from ../lv_rec/lv_rec.h:24:0,
from ../lv_rec/raw2dng.c:26:
../../src/raw.h:87:6: note: previous declaration of вЂraw_set_pixel’ was here
make[4]: *** [raw2dng] Error 1
********************************************************
WARNING: module raw_rec failed to build, deleting
********************************************************
make[4]: Entering directory `/home/magiclantern/magic-lantern/fullresvst/magic-lantern/modules/raw_rec'
[ RM ] raw_rec.o raw_rec.mo raw_rec.sym raw_rec.dep module_strings.h *.o *.d *.dep *.sym hgstamp
[ RM ] raw2dng
make[4]: Leaving directory `/home/magiclantern/magic-lantern/fullresvst/magic-lantern/modules/raw_rec'
make[3]: Leaving directory `/home/magiclantern/magic-lantern/fullresvst/magic-lantern/modules/raw_rec'
-
https://bitbucket.org/hudson/magic-lantern/commits/9697dbde3d1f7c2544846708cee1e64188c4a229 (https://bitbucket.org/hudson/magic-lantern/commits/9697dbde3d1f7c2544846708cee1e64188c4a229)
-
Thank you, but unfortunately I do not know what to do with this.
-
Thank you, but unfortunately I do not know what to do with this.
You just need to get the latest unified to make sure that is up to date, then merge in fullres-silent-pic to get all caught up to date past the point the change to setpixel was made.
-
Thank you mk11174! I used instruction from
e.g.
mkdir fullresvst
cd fullresvst
hg clone -r fullres-silent-pics https://bitbucket.org/hudson/magic-lantern
cd magic-lantern
make -j2
cd platform
cd 6D.113 (if you wanna compile for 6D)
make zip
Please also read this:
http://magiclantern.fm/forum/index.php?topic=7579.0
You might have to adjust makefile.user.default if you don't have gcc 4.8.3
so the Q is what dir should be used to get the latest unified - fullresvst/magic-lantern? And how to merge in?
-
The answer is: better wait until it gets merged in officially. Afterwards all nightlies will have it.
The alternative would be to fork the repositories and merge 'em yourself. But that's another story.
-
Thank you mk11174! I used instruction fromso the Q is what dir should be used to get the latest unified - fullresvst/magic-lantern? And how to merge in?
It could get real messy if done wrong, and I am def not a master at it yet. But I would start another local repo just to be sure you dont mess your current one up and start with unified first, and then just hg merge fullres-silent-pic to merge the latest into the unified.
Or you can use the one you have and then hg merge unified into that one since you started with the fullres-silent-pic
Something like that, but it can get very messy if you dont commit changes on new updates unless you really know what your doing with hg commands.
-
Thank you very much! I'll try to learn hg commands.
-
I have been testing this out after the past couple of weeks. One thing I noticed is like said at the beginning you can get about 1/10 however in translation 1/10 is 1/8000 on the actual camera. With that during the day I have to be at f22-32 and 100iso with a 4x ND filter to get day usage... It is very usable in the field it seems. I really have been enjoying it. I did notice after a while I went back to normal camera mode and I pushed the shutter and herd clunk. then let go and herd clunk.. I reset my custom functions and it worked again.. Thanks every one for your hard work and it is amassing here. Is my first real time-lapse video I ever made. All with silent.. Please watch in 1080p. :)
-
hi, I installed the nightly build (26/09) on my 550D with the Full Resolution option in Silent Pic mode
but when I use this mode, my pictures are over exposed
in Simple mode they look fine (same settings)
-
am I overlooking something here?
Yes. You neglected to fully read the OP. The answer is right there. Also a number of times throughout this thread where people have asked the same exact thing.
-
Yep max your cameras shutter up.. to like 1/8000.. it really will be about 1/10 you will need to be at like 100iso f22 f32 even with a 4x nd filter. Really a ND filter is a must during the day with this..
-
Did full-res silent already made it to the nightly builds?
-
Question for 550D users who have successfully taken more than 3 Full Res photos in Silent Mode ...
Arwen can you take more than 3 photos in Full Res mode? .... and does your 550D crash or freeze? ...
I still cannot take more than 3 photos with my 550D (in Full Res Silent Mode) before the camera frezzes/crashes ... (black/blank screen) ...
Do I have to set any other options to make this NOT freeze or crash ... would the Shutter speed not set at 8000, or the fstop set to f22 have any effect on this? ...
I'm not using any other feature in Magic Lantern, just Silent Picture ... but I am wondering if other features need to be switched on to get this working right? ...
I have tried the Magic Lantern Nightly 2014 Sep26 550D 1.09 [Full Res Release] and the Stable Release: v2.3 Release Date: July 23, 2012 ... I'm also using manual focusing as I'm trying to use Silent Picture Full Res for Focus Stacking (MacroPhotography) ...
Simple Mode works ok for my Focus Stacking but I have a lot (hell of a lot) of image noise in my photos ... this may be due to the speed and fstop discussed above? ...
Gem
-
On 550D/500d, you can't take exposures longer than 0.8 seconds without crashing.
-
Not sure, but could it help to turn off long exposure noise reduction in Canon menu ?
Long exposure noise reduction kicks in at about 1 second and longer exposures, so maybe there's something going on there ?
-
It does not solve the problem.
On long exposure noise reduction - ERR70
Off long exposure noise reduction - the camera is busy, you can not turn off, you need to remove the battery
-
Explain the details and the settings of the issues with your exposure. If you read through the thread you will see that the shutter speed isn't really accurate to reflect normal shooting so you have to fiddle with it..
-
I must've missed the text about 0.8 sec ... :-\ ... thanks A1ex ...
Didn't think about noise reduction ... will check ... thanks Levas ...
bhursey:
Yes I read about the issues regarding exposure hence why I thought it may of contributed to the crashing ... unfortunately I wasn't taking notes when I done the last Silent Picture Full Res session ... I will on the next one, being as I need to now have a retry with the suggestions above i.e. noise reduction and faster shuter speeds ... ;)
Gem
-
... I find out that I can convert .mlv file using mlv2dng! ...
In my PC mlv2dng.exe crashes when trying to convert mlv with lots of frames (e.g. 250 frames). I tried drag'n'dropping onto mlv2dng.exe only the .mlv file (not the side files, m01, m02...) and it crashes after a couple of seconds, producing no gng files.
Does anyone find that I made something wrong? Or any other way to convert mlv files?
-
use:
./mlv_dump <src> -d -o <path>
-
use:
./mlv_dump <src> -d -o <path>
Thank you g3gg0, I will try. I think I'll need also your mlv_dump.exe module, right?
Can you explain what the -d and -o parameters mean? Is there a list of parameters available and where I can find it?
Thanks again!
-
here (http://ml.g3gg0.de/modules/mlv_dump.zip/mlv_dump.zip)
just supply the -? option and it should print the options. (or was it -?, dont remember)
-
Ok, this is my first time-lapse using full res silet pictures on a 5D3:
I shot 250 frames, but only 102 have come from the mlv conversion. I use mlv_dump as suggested, it give me an error.
Maybe it happened because of mlv trunks (m00, m01...)? I use a Fat32 Lexar 1000x 32gb CF. I want to try formatting it exFAT, does anyone have a suggestion on the best cluster size I can use to format it?
-
Is it possible to capture Full Resolution Silent Pictures in Jpeg format?
-
Please do not ask for builds in this thread. This thread is for development related feedback only.
If you would like a build compiled, so you can help the Magic Lantern development team by testing this feature and providing feedback, please see this thread (http://www.magiclantern.fm/forum/index.php?topic=12608.0).
-
hello.
i have made some tests with full silent picture + stack focus. the setup was 550D + Sigma 150mm F/2.8
1/3 seconds exposure time is very good for macro photography in the early morning, when light is low, the wind is slow and the insects are slow because of the cold temperature. the idea is to take some similar picture like this one
http://www.fotonatura.ro/forum/album/eliz/insects/2010/IMG_24172-74-76-77-78.jpg.html (http://www.fotonatura.ro/forum/album/eliz/insects/2010/IMG_24172-74-76-77-78.jpg.html)
this is a report with problems that i have encountered
--------------------------
(1) when shooting full silent picture, the lens aperture seem to be stuck wide open.
the camera was set to M mode (manual) and full silent DNG picture. changing the aperture from F/2.8 to F/8 (while ISO and exposure time constant) gives a picture with identical exposure. also the DOF (depth of field) seems to remain the same.
i have tried to press the DOF preview button with full silent picture activated in the ML menu, but instead of preview the aperture (in liveview), i got a picture.
turn off the full silent picture in menu, and the DOF preview seems to work ok, the image will turn dark on the screen when pressing the button.
proposed logic: keep the aperture open to make (first) autofocus, but when stating the stack process the aperture must be closed and kept like this (for minimize the shacking) up till the moment when the stack shoot is finish.
--------------------------
(2) the whole process fullsilent + stacking, is to slow.
i made a test, it lasted 46 seconds for 5 stacked DNG silent pictures to take. this is quite to much time in realworld for the insect to stay unmoved or for the wind to not move the subject.
if you manage to capture 3 pictures at F11/F16 aperture in a short time like 5 seconds, will probably make this function to get good results in the realworld.
400ms to read the sensor + 1 second to review the picture + 6 seconds to write the DNG + 1 second to do refocus.
is there any way to use the buffer memory to take as many as pictures possible, and writing the pictures after that?
proposed logic :
a) do not wait for image data to be written on the card, before starting the re-focus process. instead use the camera buffer (similar with Canon firmware does on continuous shooting mode on mechanical shutter)
when the buffer is full, pause the stacking process, write the data to the card, clear the buffer, continue the stacking process
b) can live view be turned off while taking the stacked shots if this is speeding the capture process? (like in this example (http://www.magiclantern.fm/forum/index.php?topic=12523.msg125178#msg125178) ). once you made focus on insect, seeing the process on the screen is useless after you start running the Stack function.
c) image review can be turned off for faster speed. but it seems Magic Lantern show me the DNG picture on the screen after capture, even if Image Review is set to OFF in the Canon menu.
--------------------------
as a conclusion, these two functions combination must be perfected for use in the realworld for stacked macro photography (i mean live subjects).
p.s. i observed that MLV are captured in 3 seconds which is an advantage, but i have used DNG for test to simply the conversion process, because i toked like 500 pictures for this tests. i have used shutter times between 1/10 and 0.8 seconds. no error 70 for me, or any kind of errors.
-
Full Resolution Silent Pictures shot in Jpeg. Any chance that it's possible? I'm curious as well.
-
The 23 sept 2014 full resolution silent picture build that I found somewhere on the forum works only if previously ML is overwritten with the build from 7 october. So copy original ML on card, after that overwrite with 7 oct build, after that comes 23 sept build and silent picture works fine on 600d. I don't know why this succession of overwrites works, maybe someone will build a working silent picture module that works fine the first time is installed. Anyway I'm pleased with this arangement anyway
-
That's not possible. You must be mistaken. It was probably something else that is an unrelated coincidence.
There's a good reason this feature is not in the nightly builds yet, and you probably shouldn't be using it unless you know what you are doing.
-
However it is working for me without crash. I don't know why but I suppose some modules that are stable from 7 oct build are still working after rewrite the version from 23 sept.
However this build alone does not work but only after I overwrite on 7 oct build for 600d. I know it's not recomended to make such cocktails but it works. After this however the focus peak module is not present anymore - and maybe others too but I didn't check.
-
So are you able to reliably reproduce this behavior? I doubt it. You are mistaken. If you overwrite files then they are no longer present and can have no effect. It is something else unrelated. I bet you only tried this once didn't you? And because it happened to work after you overwrote the "oct 7 build" then you assume that that was what caused it to work, when in fact it was a completely unrelated coincidence. Start with a freshly formatted card and reset all camera settings and try again.
"focus peak" is not module
-
Right - focus peak feature.
However it is possibile for someone to check in safe conditions if what I did is safe for long term? In fact I'm asking for a confirmation.
First time I did was last thursday afternoon and it worked for a few hours half pressing the shutter and then in combination with intervalometer and advanced bracketing. After that the next day didn't work, I don't know why. I tried after that with 2 card formatting again and again for almost 10 times, the same crash - black screen and an error and quickly removing the battery. I gave up being afraid not to crash the camera for good.
Today I combined as I said the two builds and it works, I took about 50 full res pictures in silent mode just for test - with and without intervalometer and advance bracketing. It gave me at some point and error but only one time and none for the next 30-40 pictures.
I'm still not very relaxed to use it but I'll try to see if it's stable and hope it works.
The reason is to save the shutter because anyway I use a tripod for most of the time.
And I've copied in the same succession it on 2 cards, both working.
And once again 2 minutes ago after formatting the card in Windows on pc too.
-
And it also doesn't work if you don't use your "succession"?
My guess is that it's some camera or exposure setting that is different that's causing it to work or not.
-
Indeed, after clearing the settings, I found out that with auto ISO didn't work. I'll try without my "succession" (give me a synonym) and without auto exposure.
Yes it works without my "succesion". One or more of these must be changed (fixed ISO), quality of image raw or L+ raw, disable Canon info using INFO key in order to work with 23 sept build. However I must check if it's stable. Sorry for my "succession"...
As a conclusion:
Full res pictures works with:
but:
- image quality must be L+raw or raw
- ISO must be fixed
-
Both of these issues have already been discussed in this thread and checks for them in the code have been added (but probably after mk11174 made that build). Yet another reason not to use this unless you know what you are doing and at very least have bothered to read this thread. I highly discourage people from using and posting these unofficial builds.
/* there are problems with shutter speeds slower than 15 seconds */
/* (corrupted image and camera lockup, at least on 5D2 and 550D) */
if (prop_shutter < SHUTTER_15s)
{
error_msg = "Exposure too long";
goto err;
}
if (prop_iso == 0)
{
error_msg = "Auto ISO not compatible";
goto err;
}
if (!can_use_raw_overlays_photo())
{
error_msg = "Set picture quality to RAW";
goto err;
}
-
I compiled Full-Res Silent Pics from the full-Res branch. It works on my 50D. The only thing thing that did not work is Full Resolution saving as MLV file. When I open it with MLRawViewer it's all dark.
Is this the case for everyone using full resolution silent pics?
-
That can also be due to texture size limits with your GPU. MlRawViewer assumes it can make a big enough texture for the frame, but full res silent pictures can exceed that limit on older GPUs
-
umm . . . so It's my laptop's GPU that cannot handle it? Or is it MLRawViewer that can't handle it in combination with that GPU? It's an Early 2012 15" Macbook pro.
-2.6GHz quad-core Intel Core i7
-8GB of 1600MHz DDR3 memory
-Resolutions: 1440 by 900 (native)
-Intel HD Graphics 4000
-NVIDIA GeForce GT 650M
-1TB SSD
I'm gonna try it on my Mac Pro - it's a more capable system.
-
Also try using a different converter to ensure it is in fact an issue with MLRawViewer
-
umm . . . so It's my laptop's GPU that cannot handle it? Or is it MLRawViewer that can't handle it in combination with that GPU? It's an Early 2012 15" Macbook pro.
-2.6GHz quad-core Intel Core i7
-8GB of 1600MHz DDR3 memory
-Resolutions: 1440 by 900 (native)
-Intel HD Graphics 4000
-NVIDIA GeForce GT 650M
-1TB SSD
I'm gonna try it on my Mac Pro - it's a more capable system.
I'm getting the same thing on my Mac Pro:
NVIDIA GeForce GTX 660
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 2048 MB
On the other hand, MLVMystic has no problem extracting the DNGs from the MLV file and they look fine in ACR. It must be something with MLRawViewer not being able to handle 4K MLV files. This is what I get - all dark:
(http://i.imgbox.com/rJnAvqIi.jpg) (http://imgbox.com/rJnAvqIi)
-
This is how magiclantern-Nightly.2014Sep26.5D3123_FIX from mk11174 saves MLV:
(https://farm9.staticflickr.com/8573/15750331687_cabf2fac45_o_d.png)
Despite card formatted FAT32 or ExFAT, after creating the first file it start to save every frame in new file (and with illegal characters in file extension too). MlvDump extracts frames just from first file silently ignores the rest, so, I can't get more than 103 frames at once.
I've read about 1500+ shots - what's wrong with my setup?
-
compiled from a branch fullres-silent-pics module and autoexec.bin for 600d canon. Removes, writes that retained, but the map is empty :( what did I do wrong?
-
magiclantern-Nightly.2014Sep26.5D3123_FIX from mk11174
what's wrong with my setup?
Compile from the most recent changes in the repository, there could have been fixes implemented since that build was generated (see my conversation with florinfl above). Please also keep in mind that this is a feature still under development and lots of things are likely not working or buggy. Feel free to look at the code, figure out the problem, and fix it.
Removes, writes that retained, but the map is empty
I have no idea what that means. Please be more specific.
-
compiled from a branch fullres-silent-pics module and autoexec.bin for 600d canon.
When shooting in the full-res mode, on the display information on successful saving a picture on the memory stick is displayed. But actually the memory stick is empty.
-
Compile from the most recent changes in the repository, there could have been fixes implemented since that build was generated
It's out of my skills currently, sorry.
Moreover,
mk11174 insist there is no changes:
http://www.magiclantern.fm/forum/index.php?topic=12523.msg130425#msg130425
And lureb74 reports absolutely the same:
http://www.magiclantern.fm/forum/index.php?topic=12523.msg132058#msg132058
But I went further and tried ExFAT - not working :(
More info: magiclantern-Nightly.2014Aug06.5D2212 can save more than one "big" file at once with similar setup - I shot timelapse on MkII with that build.
Same time this magiclantern-Nightly.2014Sep26.5D3123_FIX record regular (not Full-res silent) MLV just perfectly - i can save 10GB file on ExFAT formatted card and several 4GB files at once on FAT32.
magiclantern-Nightly.2014Sep26.5D3123(without FIX) - Show "Raw error" when I try to capture full-resolution silent pic
magiclantern-Nightly.2014Jul18.5D3123 - have just DNG write option...
magiclantern-Nightly.2014Sep26.5D2212 - same problem, as magiclantern-Nightly.2014Sep26.5D3123_FIX
so, it's probably last A1ex tweaks :(
mlv_dump reports "Error: GUID within the file chunks mismatch" - this why just first file extracted.
Hope this info ^^^ will be useful for someone willing to fix this.
-
When shooting in the full-res mode, on the display information on successful saving a picture on the memory stick is displayed. But actually the memory stick is empty.
saving as what type? what are your other settings? how did you verify the "memory stick is empty" ? you won't be able to view or transfer the files directly from inside the camera, you have to put the card in a card reader connected to a computer.
-
I apologize. Really through a card reader files are visible. Thanks!
-
Dears,
My questions may comes a bit late, but is it possible to take full res silent pict via USB / EOS utility or a kind like Helicon Focus Remote ?
Cheers
Pierre
-
works at canon 600D. But there is a problem. If exposure of 1 second and above, the camera is incorrectly cut out.
-
Start reading at: http://www.magiclantern.fm/forum/index.php?topic=12523.msg129874#msg129874
This is a known issue with 500D, 550D, and now I suppose also 600D.
-
thank you
-
Does anyone still have a build with full-res silent picture mode? Or can anyone clarify as to which build still has it?
I know Audionut was removing them as it's possibly too unstable or dangerous but I have a 5Dmk3 with a broken shutter, so I'm really hoping to get my hands on the Full res mode and help test it as much as I can, if the community would benefit from it.
-
@blackcannonfilms -- were you able to compile and get it to work on your 5D3 yet?
-
I'm not can compile module, have this error, but if type
make clean
make (after this have error)
make (here compiling is done, but module not work, camera boot, but after ~10 sec not work)
magiclantern@magiclantern-VirtualBox:~/magic-lantern/modules/silent$ make clean
[ RM ] silent.o silent.mo silent.sym silent.dep module_strings.h *.o *.d *.dep *.sym hgstamp
magiclantern@magiclantern-VirtualBox:~/magic-lantern/modules/silent$ make
Updated HGVERSION
[ README ] module_strings.h
cat README.rst | grep -v -E "^:([^:])+:.+$" | rst2html --no-xml-declaration | python ../html2text.py -b 700
/bin/sh: 1: rst2html: not found
grep: write error: Broken pipe
(<type 'exceptions.SystemExit'>, SystemExit(1,), <traceback object at 0x4031e504>)
make: *** [module_strings.h] Error 1
-
This (http://www.magiclantern.fm/forum/index.php?topic=11278.0) will help with rst2html.
-
You also need to compile the ML core
-
You also need to compile the ML core
You mean make command in platform folder?
-
That's one way to do it, yes.
-
I was wondering what kind of realistic frame rate I could achieve with this on a 6D (assume with a fast enough SD card to get the max ~40MB/s) using a remote shutter release to do the half-press?
I'm trying to develop a technique with which to telecine my family's old 8mm home movies. I've been messing with shooting video and trying to detect and remove all the duplicate frames but that gets very complicated very quickly.
I have mounted a microswitch on the projector shutter which I could adapt to short the half-press shutter "button" on the cable remote connection. Previously I abandoned that route as I would quickly wear out the mechanical shutter on the camera (3600 frames per 50meter film adds up quickly). But I wonder if this silent module could be able to do what I want? I don't even need the full resolution of the sensor--I would be happy with 720p (crop mode?)
I also read the thread about silent mode into an MLV container as opposed to DNGs would make writes faster. Would that help me?
Normally the projector runs at 18fps but it has a slow motion function I can use to do 16, 12, 9, 6 or 3fps.
So A1ex or anyone else familiar with this function--can you tell me if this is likely to work or not? I know most everyone else is using this module for timelapse. I would be doing 1/10 second exposures (the fastest shutter speed available, right?) triggered from the projector using the cable remote and would need to capture at 3fps (or even better 6fps if possible) via simulated half-presses. I am willing to experiment, but if there's no possible way it can work please let me know so I can go back to the shoot video/remote dupe frames method.
Thank you!
-
Fastest shutter speeds with full-res-silent-pics is about 1/3 of a second... So no way fast enough to do more then 3 frames a second.
But if you want to mimic 8mm film.
I'd choose a 1:1 aspect ratio in MLV raw menu and use fps override to do 18 fps.
This way you're shooting 18 fps in a square frame format.
-
Thanks Levas. When you say fastest shutter speeds with full-res-silent pics is 1/3 of a second are you actually talking about the shutter speed? Because I thought a1ex in the first post said the fastest shutter speed was 1/10 of a second.
And I'm actually not trying to mimic 8mm film, I'm trying to digitize pre-existing 8mm film. I know I can shoot at 18fps and set the projector to 18fps, but the projector uses an AC motor so the frame rate is not going to be precisely 18fps--thus the camera becomes unsynced and starts capturing frame transitions.
What I am trying to accomplish is the projector advances a frame, then tells the 6D to take a picture. That would allow me to achieve 1:1 frame capture (one still image for each frame of 8mm film). I can run the projector at 3fps if this silent mode can take photos at 3fps.
-
Ah you're trying to digitize 8mm.
I used some full-res-silent builds for Canon 6d in August this year, so maybe there are some improvements done after that.
But fastest shutter speeds I got on my 6d are in the range of 300 mili-seconds
Could be that there are some faster Canon camera's around which could handle 1/10th of a second.
I think in this case the readout speed of the 6d Sensor is the bottleneck, probably it really takes about 1/3 of a second to read the whole thing out. (6d has a slow burst rate against other Canons).
So 3 frames per second could be done...BUT due to the SD card slot, you can only write away 40Mb/s. So that's one frame per second for the 6d (35Mb per frame).
You're probably better of by searching for some store/person who has a dedicated scanner for 8mm...
-
I read though the entire thread so forgive me if I just missed it, but is it possible to fire flash with fullres silent? I don't see this specifically mentioned anywhere. I am still working on trying to compile it.
-
@bookemdano. I've made a slider with an arduino and stepper that moves a specified amount, then fires the half shutter (operated via iPhone app). I'd been thinking recently that the same design would suit telecine very well. You just have to swap the AC motor for a stepper then fps and sync are non issues.
-
Hey guys, I allready posted in the "Want to help with the latest development but don't know how to compile?" thread but i got no realy awnser.
Hey
In the end of July i tested the new FRSP modul with my old 600D and i was very happy with it. I took various photos with it and i produced even a little promo vid for this modul.
I tryed to find the borders of this modul and reported every bug i found. There were real not much ! ( :) )
Now, 5 months later, i sold my 600D and bought a 6D. Not hard to imagine that i want to try this new modul on the 6D too and help u guys with further developing. But.
I searchd now nearly 2 hours in the forum to find current silent.mo builds for the 6D but i found nothing useful. Now i read that people just asked for builds and didnt reported bugs :/ to sad.
So, the result from Audionut is totaly understandeble.
Now my question.
Is there any chance that a user, how is willing to "test" the FRSP modul, getting a working build for the 6D?
It would be realy awesome! This new feature would help me so much by taking timelapse's!
So i want to ask the same here.
Can some1 provide me a build for the 6D with the new full res silent pic mode?
Like i wrote. I tested it on my old 600D, which i sold few weeks ago, and i was totaly happy with it and it had realy just a few minor bugs. I took like 10k images without any dropped frames.
-
The bugs, limitations, and issues are pretty well known at point. What's really needed is further development. Once some more work is done there might be something to test, but if there's nobody developing, there's nothing to test.
-
I did a lot of timelapses and hyperlapses on 5D II&III this month on my vacation using FRSP, DualISO, AutoETTR. I reported some bugs i find before in my previous post. Here are the rest.
1. Build for MKII more usable - in addition to ability to shot more than 4GB at once it shows live image between shots which is helpful for hyperlapse. On MKIII I can see just final image for so short time I just even can read RAW exposure hint. I've read this is done for battery saving, but I don't meet any shortage - after 300 shots I had 65% battery on MKII and 85% on MKIII(I need to restart intervalometer every 100 shots on MKIII).
2. AutoETTR unreliable with FRSP, I disabled it after several attemps.
2.1 AutoETTR doesn't care that shorten exposure beyond about 1/30 has no effect on exposition.
2.2 Meeting overexposure AutoETTR ... rises ISO and doesn't push it back, so my sunrise timelapses after some time gets 1/8000 and 12800 ISO :)
I must say that RAW exposure hint is a real savior in such situation. It cares about DualISO. Anyway, AutoETTR can't change aperture or insert/eject ND filter for you :)
My conclusion: FRSP need some minor bug fixes and improvements, but usable, at least on MKII & III. It's stable, doesn't overheat cameras(I shot in tropics by the way) and decent battery draining
-
@mothaibaphoto: Yeha, i got the same experiences with the 600D. Its very useable and with a simple ND-Filter and some knowledge it works amazing.
Ok, so lets change the question. Is some1 here how can provide me an build with the FRSP modul for the 6D113?
I realy want to use this feature in my vacations for some timelapses! So i dont have to hurt my new 6D with thousands of shutter actions...
-
See reply 358 then follow the link... asking over and over again isn't going to get it built for you. That has stopped because people abused it, now you need to build it for yourself if you want it.
-
Hello everyone,
I understand according to @Audionut -- the FRSP module has been removed for safety purposes. Oddly enough I was in the middle of my Holiday trip with the family and decided to try the FRSP again since it has been awhile. It worked well before and now whenever I try to use it.. it just shows a black frame (like as if I had the hood on the end of the lens) so I decided to turn off Full_Res and use the simple version instead which works fine.
Has anyone experience this? I was hoping I can take this particular testing further to help the dev's. However, I went into my external drives to find the FRSP Modules that I had saved as back up... I reinstalled that into the card and the 'Black screen' still persist?!
I find this kind of annoying because I have not changed anything within the ML settings in the past three months and yet so strange that it just stops working out of nowhere...
So I decided to give it a shot with the latest nightly build (1_3_14 for 5D3 1.1.3) and merge the FRSP module and still shows the black frame when triggering the silent mode. Obviously either something happened without my knowledge or the ML gods just decided to spike my 5D3? lol (I know its not funny really but still)
Thoughts?
*EDIT*
I decided to just wipe the card clean again and start fresh (without using the new autoexec.bin with the old ML settings, etc...) so with ONLY using the autoexec.bin/ML files from 9/26/14 build installed altogether -- FRSP was alive once again! *sighs*
Now I plan on testing this further to see if it'll be compatible with the new auto exec.bin (from 1/3/15 or earlier) to see if the problem still exist.
Because I am itching to get the FRSP to work with the latest nightly 1.1.3... such as the newest 1/3/15 build!
Thanks again everyone!
-
There are changes to the ML core needed for full-res silent pics to work. (You need the entire ML compiled from the full-res branch, not just the silent.mo module).
We should have changed the minor module version number in this branch so that the silent.mo from this branch would refuse to load on a nightly build (b/c it won't work anyway)
-
That makes sense. Thanks @dmilligan -- guess at this point I'll have to 'toggle' between nightly builds depending on what I need for each shoot.
Not a big deal... :o
Ran into a error crash report pop-up window while recording MLV recently, tried triggering FRSP which caused this... Anyone care for this particular crash report?
I find it odd that the report itself came out rather short -- literally almost like nothing.
-
Just thought I'd drop a line here, I've finally got Full Res Silent pics working, it's a great way to maintain the use of my 5Dmkiii (which has a broken shutter) for more than just video.
I'm going to try spend some time playing around with it over the next few weeks and see how stable/useable it is.
-
Glad you got FRSP to work on your 5D3 (even w a broken shutter) @blackcannonfilms! 8)
-
I'm a noob, so I haven't managed to make it work on my 7D :(.
I would have loved to try to do timelapse without ruining my shutter even if the firmware isn't stable.
Anyway, thanks for all your work :) This little feature is very awaited.
-
This one "little feature" might never come out :(
-
I looked at fullres silent pics feature on the 7D and succeed in making it works with some fixes.
--- a/src/raw.c Sun Sep 28 20:07:07 2014 +0300
+++ b/src/raw.c Sun Jan 11 17:43:56 2015 +0100
@@ -117,7 +117,7 @@
* and http://a1ex.bitbucket.io/ML/states/ for state diagrams.
*/
-#if defined(CONFIG_5D2) || defined(CONFIG_50D) || defined(CONFIG_60D) || defined(CONFIG_550D) || defined(CONFIG_500D) || defined(CONFIG_600D) || defined(CONFIG_1100D)
+#if defined(CONFIG_5D2) || defined(CONFIG_50D) || defined(CONFIG_60D) || defined(CONFIG_550D) || defined(CONFIG_500D) || defined(CONFIG_600D) || defined(CONFIG_1100D) || defined(CONFIG_7D)
#define RAW_PHOTO_EDMAC 0xc0f04208
#endif
@@ -650,10 +650,10 @@
#ifdef CONFIG_7D /* very similar to 5D2 */
skip_left = 158;
- skip_top = 52;
+ skip_top = 50;
/* first pixel should be red, but here it isn't, so we'll skip one line */
/* also we have a 16-pixel border on the left that contains image data */
- raw_info.buffer += width * 14/8 + 16*14/8;
+ //raw_info.buffer += width * 14/8 + 16*14/8;
#endif
dbg_printf("Photo raw buffer: %x (%dx%d)\n", raw_info.buffer, width, height);
If the line where raw_info.buffer is updated is not commented out, the resulting silent pictures are pink
here is the relevant OB-ZONES picture from raw_diag module :
(http://www.bleuazur.com/~vyskocil/OB-ZONES-7D-20150111.png)
Here is a sample silent pic, at 100% it looks a bit weird, what do you think ?
http://bleuazur.com/~vyskocil/21850007.jpg (http://bleuazur.com/~vyskocil/21850007.jpg)
-
Nice, I had tried it a few months ago but couldn't get past the bugs (crashing/freezing the camera), never had a chance to make good use of it or even report the issues. Can you post the dng? It looks a little off but much better than any of my results. Black level maybe?
-
Nice, thanks vyskocil.
The image looks fine to me; what kind of weirdness are you talking about? Other than some lens softness (quite common when you shoot wide-open), I don't see anything strange.
-
Hello.
First, thanks for all you work.
I spend last days trying to use silent.mo to make some timelapses.
I have a very few C notions, and I couldn’t really help with coding.
I’m really interested into improving this feature, so I would like to help in any way.
I searched on the forum and I saw that you appreciate complex feedbacks with a lot of info on your code’s behavior.
I have decided to try to do my best here, if I can help more in any way, don’t hesitate to ask for it, I will keep an eye on this topic.
-I used the 7D latest build from the development branch.
-I took DNGs in full raw format. It does not work with S and M format.
-Focus has to be made before shooting
-You can’t do silent pic from EOS utility (it just takes normal pics)
-You can pictures with:
Half shutter
Af On button
Also with AF off button (set on remember exposure button)
And even with aperture button.
-Exposure is always a bit higher than on the preview, even with expo override and exp sim.
-So you can’t focus when silent.mo is activated. It would be great to be able to focus with AF on button.
-I noticed no difference in times for taking the pictures, with only silent.mo or all modules activated.
-Saving the pic takes always about 3500ms.
-Let’s measure times related to shutter speed:
1s = 2100ms
0.5s = 727ms
1/10 = 293ms
1/30 = 227ms
1/60 = 211ms
1/80 = 208ms
1/100 = 206ms
1/3200 = 195ms
It’s strange because at 1/100 I see the same amount of light than at 1/8.
So it seems that the shutter can’t go beyond 1/50.
-If I press receptively the shutter I see blinking black/LV screen (pictures trying to be taken) and the camera ends by crashing, sometimes with ER70. When not, the CF’s led is blinking.
I can shut it down properly without having to remove the battery.
I also can get a crash with error message, here’s the .log file crash00.
-ETTR module works for me and the « bipbip » occurs just after saving the picture, when the picture is being reviewved.
-Review of the pictures is shown until the shutter button is pressed again
-There is no EXIF info on the DNG file so, can't use LRTimelapse holy grail method... But there's info in .MLV format :DDD.
-If pressed while recording video.. it takes a pictures and crashes the camera.
A crash.log I got from pressing too many times:
ASSERT: GetMemoryAddressOfMemoryChunk( GetFirstMemChunk( pMem1AllocateListItem->hMemSuite ) ) == pMessage->pAddress
at SrmActionMemory.c:1154, task RscMgr
lv:0 mode:3
Magic Lantern version : Nightly.2014Sep26.7D203
Mercurial changeset : 81a2fd653497+ (fullres-silent-pics) tip
Built on 2014-09-26 21:55:08 UTC by mathew@mathewubuntu64.
Free Memory : 208K + 2955K
Here's a 10s timelapse I have made:
Also, I have the raw_diag module enabled.. Not sure with what I should do with it. :'(
-
@a1ex -- so does that mean the FRSP for the 7D is back in service?
-
Nice, I had tried it a few months ago but couldn't get past the bugs (crashing/freezing the camera), never had a chance to make good use of it or even report the issues. Can you post the dng? It looks a little off but much better than any of my results. Black level maybe?
The picture looked a bit weird at first for me, but I think that a1ex is right it was taken in bad conditions with a fast lens wide open(Sigma 50mm f/1.4), in dark and underexposed. I also noticed some vertical banding in dark area.
Here is a link to the DNG : http://www.bleuazur.com/~vyskocil/21850007.DNG (http://www.bleuazur.com/~vyskocil/21850007.DNG)
-
Cool thanks. The highlights are clipping to blue in the dng in ACR. White balance or level issue?
-
For me, the white balance is something like 300K lower than the preview of LV.
It only appears on the review of the silent image. Not applied to the final .mlv file.
Here's two pictures I took with the exact same settings:
I see no differences except the exposition.
http://www.mediafire.com/download/ymwcc9099wzot40/MLV_DNG.zip
-
In camera preview uses hardcoded white balance multipliers (for speed reasons). If you save as DNG in camera, there's not much metadata (including not any WB metadata).
-
i've applied the changes to the 7D code and it looks okay to me.
made a lot shots, but only had trouble with the single-file-MLV writing code when reaching > 4GiB.
will look into it.
-
@g3gg0 -- sounds interesting. Do you know if this is included in the latest nightly or is it something like I have to add the modules manually to make it work again?
-
I noticed a problem related to metadata:
Above 1s of shutter time.. it only says "1s".
So let's say I take pictures with 10s shutter time.
I convert it to .DNG with MLVMystic.
On the .dng, I will only get 1s info, while the .log created by MLVMystic shows the good shutter speed.
It brings problems when doing timelapses, because I need precise indication to compensate the exposition in software.
Maybe it's only related to MLVmystic.
-
Sounds like an issue with MLVMystic and not ML. You can verify the metadata is correct in the MLV file with mlv_dump -v
The shutter speed metadata isn't exactly correct either. It's based on timing how long FA_CaptureTestImage takes, and there's extra stuff going in there besides just the exposure. This issue still needs to be fixed.
Just out of curiosity, which changeset did you compile from?
-
Hello.
So I tried MLV_DUMP:
http://image.noelshack.com/fichiers/2015/03/1421189009-cvb.png
And MLVFS can't extract DNG from MLV files created with silent.mo module.
So I'm not able to say who is deffective between MLVmystic or silent.mo.
Concerning the changeset, I don't understand what you are talking about.
If you want to know what build I used, I stole it there:
https://bitbucket.org/mk11174/magic-lantern-fullres/downloads
:'(
-
So I tried MLV_DUMP
nope, you didn't.
you tried to call mlv_dump, and that didnt work ;)
execute ./mlv_dump.osx or rename it to mlv_dump
-
If you want to know what build I used, I stole it there:
https://bitbucket.org/mk11174/magic-lantern-fullres/downloads
:'(
I don't recommend using these unofficial builds unless you really know what you are doing. There have been changes and improvements since then: http://www.magiclantern.fm/forum/index.php?topic=12523.msg133776#msg133776
-
Thanks you both.
So I can now confirm to you that with both MLVMystic and MLV_Dump, I can't get .DNG files with meta data that goes above 1s.
This leads to wrong exposure correction, in post with LRtimelapse.
So it may be silent.mo that is the problem.
I would like to try more recent builds but i'm too much of a noob. :(
But I need this since I don't want to blow my shutter because of abusing of timelapses.
And since I have to use it, I try to do my best to find problems :).
-
Testing the latest build on 7d. Silent pics save fine as .DNG but when trying to save them in .MLV format, the camera freezes up. Tried with MLV module on and off, and in photo and video mode. Top LCD starts to flash busy after a few seconds.
Only way to get rid of the
Saving 5202x3466
Captured in 292 ms.Is to pull the battery. Doesn't go away on powering off.
-
uhm what are your settings?
during the last days i made ~90Gib of MLV full res silent pictures with the 7D.
7D v2.0.3
hg revision 12044
-
I'll try compiling again and double-check everything. Still trying to get the hang of this.
-
@N/A -- Upon avail ... Any chance I can get a copy of your compile regarding FRSP for the 7D?
Thx!
-
I need to work out all the bugs first. Full res mlv's lock the camera up, or save them into one big .dng instead of .mlv when I compile on my MacBook.
-
can you try these 7D files?
autoexec.bin (http://ml.g3gg0.de/pub_files/478857efe8a33ad868b579a0aadb33a3/autoexec.bin)
7D_203.sym (http://ml.g3gg0.de/pub_files/c8cb30cc95aeb601ba925dfc5d2f4f07/7D_203.sym)
silent.mo (http://www.magiclantern.fm/modules/modules/silent.mo/silent.mo)
mlv_rec.mo (http://www.magiclantern.fm/modules/modules/mlv_rec.mo/mlv_rec.mo)
-
@google: are those latest changes also available for 5d mk3 123 ;) ?? Thx
-
google?
-
Ups... Hahahah.. Sorry my friend ;)
-
google?
LOL
can you try these 7D files?
autoexec.bin (http://ml.g3gg0.de/pub_files/478857efe8a33ad868b579a0aadb33a3/autoexec.bin)
7D_203.sym (http://ml.g3gg0.de/pub_files/c8cb30cc95aeb601ba925dfc5d2f4f07/7D_203.sym)
silent.mo (http://ml.g3gg0.de/modules/silent.mo/silent.mo)
Same issue. Weird. I tried with your files and JUST your silent.mo, the modules I compiled, and even the modules from the latest nightly build. All this was after an in-camera format, and deleting all the config files on the card also. And just to verify, mlv_rec, mlv_play, and pic_view for full res silent dng's all work fine. I'll review all my settings and see if anything looks off, but it seems like its hanging when it writes to the cf. I'm assuming I have an issue with my mlv_rec or mlv_play modules, I'll compile those again and see if I have any warnings/errors.
-
forgot that... mlv_rec.mo (http://upload.g3gg0.de/pub_files/5e4cb904161481742c07c8ce411f8638/mlv_rec.mo)
-
Thanks @g3gg0 & @N/A for the updates -- I definitely will copy these links for the 7D and try compiling them out this weekend since I'll be off from work, FINALLY!
-
forgot that... mlv_rec.mo (http://upload.g3gg0.de/pub_files/5e4cb904161481742c07c8ce411f8638/mlv_rec.mo)
With just your files on the card, full res mlv's work fine with intervalometer, and taking a full res pic with half shutter AFTER an intervalometer cycle saves as an mlv. But trying to save one with half shutter to mlv without running the intervalometer first is what locks it up. Haven't tested this yet with my compiles.
-
Gents-
Oddly as this may seem but after successfully copying these Four files (Thanks @g3gg0) and compiled them with the latest nightly (7D 2.0.3 Jan 15th) somehow made this to work.
However, per N/A's responds from earlier regarding the 'lock up' after when trying to take a FRSP w half shutter BEFORE using the Intervalometer module. <-- (I actually use the Adv. Intervalometer)
I even tried this same routine three times and it only locked up once out of these three attempts (not sure why though) but if you feel this isn't a good enough of a troubleshoot, pls tell me!
FYI -- I also tried using @dmilligan's latest update on his MLVFS which works quite well with MLV files created from the Intervalometer module. ;)
Please let me know if I'm such a lazy @$$ and I'll see what more I can do with it...
Thanks again everyone!
-
thanks, that makes sense to me now.
gonna fix it.
-
@g3gg0 -- also I noticed when 'locked-up' frequently... I just decided to change the file format from MLV to DNG (which then worked fine) and switched back to MLV which seems to help get it working again.
May be related to shutter speeds being changed due to ETTR? Whenever I disable ETTR (always on) it would not 'lock up' as often as oppose to when having ETTR enabled.
Kind of a strange pattern that I thought it may be worth noting.
Thanks again!
-
So is it possible to use silenpic fullres mlv with 5d mk3 123? Would be nice if it will finally work. I am waiting 5 month now.. but the hope never dies ;)
-
can you try these 7D files?
autoexec.bin (http://ml.g3gg0.de/pub_files/478857efe8a33ad868b579a0aadb33a3/autoexec.bin)
7D_203.sym (http://ml.g3gg0.de/pub_files/c8cb30cc95aeb601ba925dfc5d2f4f07/7D_203.sym)
silent.mo (http://ml.g3gg0.de/modules/silent.mo/silent.mo)
mlv_rec.mo (http://ml.g3gg0.de/modules/mlv_rec.mo/mlv_rec.mo)
updated silent.mo with this stuff:
- fixed crash if no intervalometer ran before
- MLV header now contains frame count (allows playback with MLRawViewer)
- allow user to choose between DNG, Single-Frame-MLV and Multi-Frame-MLV (disable and re-enable "Silent Pic" from menu to start a new file in Multi-Frame-MLV mode)
you will have to use a recent mlv_dump to MODIFY the FPS field in the file if you want to play it back in MLVRawViewer faster.
if you set intervalometer to 10 sec, the FPS field will be 0,1 fps. non-intervalometer shots have 1 fps.
you might want to use 'mlv_dump in.mlv -o out-mlv -A 25000' to set 25 fps.
but these features is only available - again - in RECENT mlv_dump binaries :)
-
Brilliantly done @g3gg0!!!
Will definitely test them out today...
*cheers*
-
its not brilliant, its just about investing time :)
these things were requested before iirc.
5D3 v1.2.3: no idea. i only have the 1.1.3.
not sure if it will work.
-
*feedbacks*
Not sure if this will help you @g3gg0 but after copying the new four files from the link in your recent quote...
I've been getting these "Failed to link Modules" errors on my 7D...
(https://farm8.staticflickr.com/7552/16126320030_5111020853_n.jpg) (https://flic.kr/p/qz2B7w) (https://farm8.staticflickr.com/7473/16287985186_02cd128832_n.jpg) (https://flic.kr/p/qPjbwN)
Not sure why it worked yesterday with the other files...Gonna try your old files from yesterday's post above to see if I can get it to work again (regardless of the lock-up bug which is easy to get around)
Either way Thanks again for your dedication on this, however, I compiled the same way I did yesterday w the older files but again this may be an Error on my part! (Not sure how/when)
**EDIT**
I just tried another CF card and load that with yesterday's compile that I took from your original first Four files and it's working fine again other than that lock-up bug occasionally (which I don't mind atm until the fix)
Will definitely try another CF card w your latest Four files and see if the errors still persist.
Thanks again!
***EDIT(Part 2)***
I couldn't stand it so I decided to just try and take the silent.mo and compile that with yesterdays files. I wasn't sure if I should to compile them with the other 3 (autoexec.bin, 7D_203.sym, mlv_re.mo) because I wonder if that's what was causing the error I encountered earlier unless they are the same as yesterday's and you only updated/fixed the silent.mo alone?
correct me if I'm wrong because it seems to be working... even tried using half-shutter full_res BEFORE using intervalometer which hasn't produced any 'locked-up' bug as of yet. so THANK YOU and excuse me for my mess!
-
thanks, that makes sense to me now.
gonna fix it.
Happy to be of assistance.
-
@DeafEyeJedi:
ive just read the last few lines and it seems you found the issues?
dont enable old modules if you get such errors.
-
hi,
so i downgraded to 1.1.3 with success :)
can somebody please be so kind to post an updated fullres silent pic module for the latest nightly of 1.1.3 5d mk3. thank you
greetings sw
-
@swinxx -- PM me for a somewhat working copy of FRSP module for 1.1.3 (or 1.2.3) ...
-
thx. my prob is that i have just no compiling skills
-
@g3gg0:
Any chance we could see similar to what you did for the FRSP on 7D 2.0.3 for the 5D3?
1.1.3 or 1.2.3 doesn't matter to me... preferably 1.1.3 if we had to make a choice! lol
but I'm curious because I like what you did for the 7D in terms of choosing Multi-Frame MLV or Single Frame MLV...
that would be a big +1 !
-
Hi,
DeafEyeJedi was kind enough to forward me a link to this thread and I have tested the full-res silent.mo posted by g33g0 on 2015/01/16.
Below is my feedback on the tests performed:
Just as background, my 7D is running the latest nightly build dated 2015/01/15.
Initially I overwote the files on my CF card with those downloaded from g33g0's links dated 2015/01/16 (autoexec.exe, 7D_203.sym, silent.mo and mlv_rec.mo files).
Upon starting the camera the following errors were displayed and none of the modules loaded. This is similar to DeafEyeJedi's initial experience.
tcc: err: undefined symbol 'is_native_movie_mode'
tcc: err: undefined symbol 'is_custom_movie_mode'
[E] faqiled to link modules
I then:
- Formatted the CF card in the camera and retained ML
- Deleted the autoexec.exe file and all of the modules and settings files from within the ML directories.
- Then copied the files supplied by g33g0 to their respecitve locations on the cf card.
- Loaded the card back into the camera and was then able to successfully load the silent and mlv-rec modules. (note that these are the only modules on the card).
Time to test:
Test 1: Silent pics - full-res, DNG format images, no intervalometer.
Sunny with light clouds, ISO, 100, 200 and 400, f5.6
Result: failed. Error message "exposure too long"
Interesting given that the indicated exposure on the top screen was 500th of a second or greater.
Reverting back to simple silent-mode resulted in images being captured as expected.
Test 2: Silent pics - full-res, DNG format images, intervalometer enabled.
Sunny with light clouds, ISO, 100, 200 and 400, f5.6
Result: failed. same as test 1, Error message "exposure too long" and no images taken
(note the intervalometer did cycle through it's range as per its paramaters).
Test 3 & 4 : Silent pics - full-res, Multi-MLV and Single_MLV format images, no intervalometer.
Sunny with light clouds, ISO, 100, 200 and 400, f5.6
Result: failed. same as test 1, Error message "exposure too long"
I don't have the tools or skill to grab the source codes and recompile a custom build. Any thoughts, on what the issue may be?
(Happy to test any new versions)
Also, I haven't tried to test the MLV-REC.mo yet as I don't know what has changed and as such, don't know what sort of testing is required. If someone can enlighten me I'll put this module through its paces as well.
-
set M mode and retry
-
First post on the forums, sorry that it's a question!
I found a nightly build on the forums for 600D (2014Sep26) with silent.mo which works nicely.
However the aperture seemed to be wide open even with Expo Override on. Is there any known fixes for this?
So after that I decided to try compiling the fullres branch myself to see if it was a issue fixed in a newer release.
I can't seem to be able to compile silent.mo though. All the other modules and core compile just fine.
Basic settings I was using:
hg clone https://bitbucket.org/hudson/magic-lantern/
hg update fullres-silent-pics
ARM_ABI=none-eabi
ARM_PATH=~/arm-toolchain/
GCC_VERSION=-4.7.3
CONFIG_TCC = y
CONFIG_MODULES = y
CONFIG_PICOC = y
make clean
make 600D
cd platform/600D.102
make zip
And the error I'm getting:
silent.c:1302:21: warning: initialization makes integer from pointer without a cast [enabled by default]
"Writes an extra MLV for every picture being taken.\n",
^
silent.c:1302:21: warning: (near initialization for '(anonymous)[2].submenu_width') [enabled by default]
silent.c:1307:9: error: initializer element is not constant
},
^
silent.c:1307:9: error: (near initialization for 'silent_menu[0]')
make: *** [silent.o] Error 1
Any help would be appreciated!
-
delete the comma at the end of line 1301, this is an error that was recently committed to the source
-
@g3gg0 - Is there a reason for the mlv_rec.mo link that you posted in recent post #444 for 7D 2.0.3 is from 4/18/14 whereas the one from before (@N/A's post #437 (http://www.magiclantern.fm/forum/index.php?topic=12523.msg137989#msg137989@N/A's post #437)) that was from 1/16/15? (or was this a mistake?)
Should I be using the new mlv_re.mo (1/16/15) instead of the one from 4/18/14 -- correct?
I'm asking because the one I downloaded from your post (4/18/14) was the one Module that was actually causing the error I posted from earlier post.
So I then decided to compile with the mlv_rec.mo (1/16/15 from @N/A's post) which seemed to be working really well. Strange or normal?
Playback is nice on MLRawViewer... [emoji1]
Just wanted to confirm... Thanks!
-
updated silent.mo with this stuff:
- fixed crash if no intervalometer ran before
- MLV header now contains frame count (allows playback with MLRawViewer)
- allow user to choose between DNG, Single-Frame-MLV and Multi-Frame-MLV (disable and re-enable "Silent Pic" from menu to start a new file in Multi-Frame-MLV mode)
Just tested it, works like a champ now. Thanks again. Got a wedding to shoot in a few days, might try it out on some static shots.
What else does FRSP need before it gets pulled into unified?
-
@DeafEyeJedi:
indeed. sorry. i accidentally uploaded it using the wrong uploader. my wrong.
fixed.
-
delete the comma at the end of line 1301, this is an error that was recently committed to the source
Cheers! That worked and also seems to be fixed now in the branch.
Also after reading around I realised that the Expo Override not working was because of the lens.
Changed the lens and works nicely. Happy days!
-
What lens is causing trouble with expo override?
-
@DeafEyeJedi:
indeed. sorry. i accidentally uploaded it using the wrong uploader. my wrong.
fixed.
No worries @g3gg0 -- just thought it was worth noting to prevent snowballs of unnecessary complaints/questions from those who don't enjoy troubleshooting. [emoji6]
-
What lens is causing trouble with expo override?
Was the 600D kit lens (18-55) that I tried originally with. I did try with and without stabilizer and AF incase those have any effect.
Canon 50mm 1.8 works perfectly tho!
-
**feedbacks**
This quick test was done on 7D 2.0.3 w latest nightly (v2.3.NEXT.2015Jan12.7D203 fee1d1dd5a2d+ [fulres-silent-pics] tip ) along with custom compile for FRSP (from @g3gg0 & @N/A) which I decided to see what happens with varies of shutter speeds (beyond 1/30th) and here are the results...
'FRSP_7D203_MLV_DNG's' (http://https://www.dropbox.com/sh/6ezzwfszjyft8c4/AABRpp08NqrfPbzxZ6r0-vkja?dl=0'FRSP_7D203_MLV_DNG's')
Included are the orignal MLV file created from FRSP as well as the converted DNG's respectively!
-
general warning:
FRSP are only possible in M mode. in other modes the results are unpredictable
-
general warning:
FRSP are only possible in M mode. in other modes the results are unpredictable
Was this for me as well?
If so, this test was actually done in M mode and I ONLY use M mode for literally all types of shooting.
**EDIT**
Also has anyone try this? Just manually change the shutter speeds after each take on FRSP during (Non-Timelapse) Multi Frame or Single Frame MLV's and it seems to bypass the limit that FRSP used to have 1/15 or 1/30 whatever it was.
This applies only to the 7D 2.0.3 FRSP (not the 5D3 atm)
Or am I high on Magic Lantern? :P
-
Hello everyone,
I have a 5dm3 firmware 1.1.3 with magiclantern and the last build january 25, and I want to test full-resolution pictures silent but I can't find the compiled download link.
can someone help me?
thanks
-
@hawaii75cc -- I believe the last decent FRSP for 5D3 1.1.3 that's currently working (that I know of) is a fixed version compiled with Sept 27th build.
It has been taken offline for safety reasons and hopefully it'll be implemented into the nightlies soon.
-
Ladies & Gentlemen:
I'm just a bit jealous of the fact that the 7D 203's FRSP works slightly better than the 5D 113's... (not sure why/how) really frustrating and yet so confusing at times.
Will get to the bottom of this one way or another...
:P
-
Hi. I'm using 550d and last nightly ML build :
Latest Build
magiclantern-Nightly.2015Jan24.550D109.zip
Built on: 2015-01-24 03:22:51 +0200
Changeset: 04a1daf
How can I install full resolution silent picture module? Or where I can get this module compilled? Just don't know how to compile it :)
-
Update: mlv_play now works with those huge frame sizes :)
My free time is slowly returning to normal levels, and this thing is next on the list for including into the nightly builds. Thanks @g3gg0 for fixing the MLV output routines.
-
Glad to see you coming back!! Welcome again a1ex!' ;)
-
Yes, our halcyon days are over. See
https://bitbucket.org/hudson/magic-lantern/commits/all
Nice, really nice!
-
Great news @a1ex and as expected we all knew you would be back after your much deserved hiatus or holiday break... Whatever you wanna call it!
[emoji2]
-
What a good news !!!
A1ex !!! Please, pay attention to this:
http://www.magiclantern.fm/forum/index.php?topic=12523.msg134853#msg134853
http://www.magiclantern.fm/forum/index.php?topic=12523.msg134863#msg134863
http://www.magiclantern.fm/forum/index.php?topic=12523.msg136363#msg136363
-
the MLV issues were already fixed weeks ago.
-
Yes, our halcyon days are over.
I had to Google the meaning of that phrase, just learned something new. Thanks!
-
Happy to report full-res silent MLV files now work with MLRawViewer. Yey! - now I need a faster laptop to playback 4K MLVs :P
(http://i.imgbox.com/KFsSraFn.png) (http://imgbox.com/KFsSraFn)
-
@ devs: can you please tell me whats the fastest shutter speed with silent pic right now (with canon 5d mk3 1.1.3) and would it be possible to update the silent.mo from time to time in the #1 post with all the newest additions for the different cams, especially canon 5d mk3 FW 1.1.3 :)))
or for simplification: would it make sense to add the new full res silent pic module to the nightlys.
thanx very much :))
-
Do you actually read the thread before posting?
Fastest shutter speed: http://www.magiclantern.fm/forum/index.php?topic=12523.msg121962#msg121962
Nightly:
[...] this thing is next on the list for including into the nightly builds.
-
@ devs: can you please tell me whats the fastest shutter speed with silent pic right now (with canon 5d mk3 1.1.3) and would it be possible to update the silent.mo from time to time in the #1 post with all the newest additions for the different cams, especially canon 5d mk3 FW 1.1.3 :)))
or for simplification: would it make sense to add the new full res silent pic module to the nightlys.
thanx very much :))
I believe A1ex is working on getting silent.mo in the nightlys. Posting the silent.mo alone may not be a good idea as some dependencies may also have to be compiled. It is best to compile the ML core along with the modules to avoid crashes. I'd suggest you setup a machine to compile and compile the full-res branch.
-
Bah . . . you beat me to it A1ex . . . :)
-
Hey :P
I believe that full res update will be integraten in new nightly builds for 550D and other cameras. Because everyone can't compile it by itself.
Maybe there are a tutorial how to compile this branch for ML?
ps sorry for english :D
-
Ok, thx a1ex. I have tried to read it. So i will try to find the answer for my question, although the thread is a little bit too technical for my understanding. and i believe that i can remember that there was some progress for the 7d not 5d? Perhaps this is crap.. However greets sw
-
Fastest shutter speed on 5D3: 1/33.19 at the top of the image and 1/6.30 at the bottom. Linear gradient in-between.
-
Ah. Thank you. So i have to use my nd filter ;) best wishes, sw
-
Could anyone please tell me if the current fastest shutter speed for M1 w FRSP is still about 1/15th - correct?
Thanks!
-
I'm sure this has been asked billions of times by now, but could it be possible to use FRSP or a spin off of it, to get better quality full HD jpeg sequences at 24fps on something like a 600D? or is that just simply too processor intensive?
-
Update:
https://bitbucket.org/hudson/magic-lantern/pull-request/609/fullres-silent-pics/diff
-
Could anyone please tell me if the current fastest shutter speed for M1 w FRSP is still about 1/15th - correct?
On my M1 it doesn't record pictures faster than 239ms.
Regarding FRSP on the EOS M1, any chance to separate the * (STAR) button from half-shutter? As reported before ( http://www.magiclantern.fm/forum/index.php?topic=12523.msg137532;topicseen#msg137532 ) no matter what option I choose in the custom function IV menu, pressing * will take a picture and it will not AF.
(http://support-sg.canon-asia.com/img/G0136677.gif)
Now, testing a bit, while using the intervalometer (w/ or w/o silent pics) the * button behaves the same, takes a picture, but if one sets a delay before starting the sequence you can see that the camera tries to autofocus in that time before it will start shooting.
-
Possible, but requires some reverse engineering. Currently, all cameras interpret the * button as a half-shutter press.
Watching the memory contents around HALFSHUTTER_PRESSED (0x3F224 on EOS-M) might be a good starting point. Also, the mem spy utility should help as well. Analyzing the messages from MPU might be helpful too, but this is a pretty advanced topic.
-
Possible, but requires some reverse engineering. Currently, all cameras interpret the * button as a half-shutter press.
Umm, ok, any reason it needs to be halfshutter? Say, since you are bypassing normal shooting anyway, can't it be made to take a picture when pressing other button that is not used like BGMT_REC 0x1E button (presuming that is the movie REC button and that it's accessible in non-movie mode that is). And this should apply to intervalometer too.
-
you start to run into camera specific problems, on my camera the rec button is also the LV button, so if you pressed it, you would exit LV, you could probably use SET though
-
you start to run into camera specific problems, on my camera the rec button is also the LV button, so if you pressed it, you would exit LV, you could probably use SET though
Since there is a per platform modularisation in ML anyway, it's a given, I guess a selector would be nicer so that a user can choose the button of choice.
And another thing, the Wiki states, that for silent pictures: "from the LiveView image buffer when you press the shutter halfway. Make sure you don't have autofocus assigned to half-shutter press (put it on * or turn it off)" which a guess needs to be edited out as is not possible to use * for AF?
-
not possible to use * for AF?
Its possible on my 60D
-
Its possible on my 60D
And it's not interpreted as halfshutter so it's usable for AF even for silentpics?
Then this is a M1 only issue? 4 posts above @a1ex said otherwise.
-
it is interpreted as half-shutter
-
I had some success with detecting the AF-ON button: https://bitbucket.org/hudson/magic-lantern/commits/793908427d2f
Works pretty good, but AF is triggered a few ms later than the half-shutter press event. So, I had to wait 4 LiveView frames, that is, about 0.13 seconds of extra shutter lag if you use autofocus.
Tested on 60D.
-
Yes that one works for 70D now, too.
*-button still takes the pic but AF-ON now focuses as it should and it's printing "Focusing...." on screen while pressing AF-ON
-
Works pretty good, but AF is triggered a few ms later than the half-shutter press event. So, I had to wait 4 LiveView frames, that is, about 0.13 seconds of extra shutter lag if you use autofocus.
Not working on my M1, I get a "Hold on..." and a unfocus silent picture is taken, that is using the * and any C.FnIV option.
-
Boo. Can you print the values of lv_focus_status when focusing and when idle?
-
Boo. Can you print the values of lv_focus_status when focusing and when idle?
How do I do that?
In the mean time, I messed around silent.c, in line 1343 I got wait_lv_frames(4); bumped to 20, which gives me:
1. on a * single press -> "Hold on..." -> snaps pic (unfocused!)
2. on a * hold -> "Hold on..." flashes quickly-> "Focusing..." and it just sits here forever with LV on BUT it does AF as it should -> a half-shutter press or a single * press snaps a pic (FOCUSED!)
compare that with your code now at 4:
1. on a * single press -> "Hold on..." -> snaps pic (unfocused!)
2. on a * hold -> "Hold on..." flashes quickly-> "Half-shutter pressed..." is written on a black screen and it just sits here forever WITH the AF light on, and rising my finger off the * will snap a pic (unfocused!)
-
You can print things with bmp_printf or NotifyBox, or simply printf.
The behavior after bumping sounds about right.
On 60D, when pressing AF-ON for about 1 second to focus, the behavior was like this:
- with 2 it worked in roughly 2/3 of situations (that is, it did not take a picture, but focused properly)
- with 3 it worked in most cases, but there were isolated cases (say 1 out of 10) where it took a picture instead of focusing
- with 4 it focused every time.
I think it's worth trying smaller values like 5 or 6.
About short presses, I'm not sure what I can do.
-
You can print things with bmp_printf or NotifyBox, or simply printf.
Right, I saw that in your code, I'll try.
I think it's worth trying smaller values like 5 or 6.
I'll do this next, at first I though I go up to 10 but then I wanted it to be really long just to be sure my 22mm (non-USM, non-IS) that I test with has time to hum along, now what I do what to know is at 20 it should take I picture by itself eventually or did I read this wrong? If so, how long it should take?
About short presses, I'm not sure what I can do.
Actually it's better now, having a way to AF is more important. Although I would still like a way to select other button ( like REC/INFO/SET/whatever ) and leave * alone only for AF, as far as I can see this should be possible by replacing get_half_shutter_pressed() with a custom get_silent_button() or something.
And another thing, on this branch now raw_rec and dual_iso modules fail to build:
Building module raw_rec...
Updated HGVERSION
[ README ] module_strings.h
[ CC ] raw_rec.o
[ MODULE ] raw_rec.mo
[ STRIP ] raw_rec.mo
[ EXPORTS ] raw_rec.sym
00001960 raw_video_enabled
00001988 raw_movie_filename
[ DEPENDS ] raw_rec.dep
Will load on:
EOSM
Not checked (compile ML for these cameras first):
1100D, 500D, 50D, 550D, 5D2, 5D3, 600D, 60D, 650D, 6D, 700D, 7D
[ GCC ] raw2dng
../../src/chdk-dng.c: In function ‘save_dng’:
../../src/chdk-dng.c:763:9: warning: implicit declaration of function ‘FIO_RemoveFile’ [-Wimplicit-function-declaration]
FIO_RemoveFile(filename);
^
[ GCC ] raw2dng
[ GCC ] raw2dng
chdk-dng.o: In function `save_dng':
chdk-dng.c:(.text+0x17f8): undefined reference to `FIO_RemoveFile'
collect2: error: ld returned 1 exit status
Makefile:13: recipe for target 'raw2dng' failed
make[4]: *** [raw2dng] Error 1
andBuilding module dual_iso...
Updated HGVERSION
[ README ] module_strings.h
[ CC ] dual_iso.o
[ MODULE ] dual_iso.mo
[ STRIP ] dual_iso.mo
[ EXPORTS ] dual_iso.sym
0000136c dual_iso_calc_dr_improvement
000013c4 dual_iso_set_enabled
000013e4 dual_iso_is_enabled
000013f4 dual_iso_is_active
00001414 dual_iso_get_dr_improvement
00001594 dual_iso_get_recovery_iso
000015b4 dual_iso_set_recovery_iso
[ DEPENDS ] dual_iso.dep
Will load on:
EOSM
Not checked (compile ML for these cameras first):
1100D, 500D, 50D, 550D, 5D2, 5D3, 600D, 60D, 650D, 6D, 700D, 7D
[ gcc ] cr2hdr
../../src/chdk-dng.c: In function ‘save_dng’:
../../src/chdk-dng.c:763:9: warning: implicit declaration of function ‘FIO_RemoveFile’ [-Wimplicit-function-declaration]
FIO_RemoveFile(filename);
^
/tmp/ccAsd4aT.o: In function `save_dng':
chdk-dng.c:(.text+0x17f8): undefined reference to `FIO_RemoveFile'
collect2: error: ld returned 1 exit status
Makefile.cr2hdr:16: recipe for target 'cr2hdr' failed
make[4]: *** [cr2hdr] Error 1
i guess you need to add some defines in chdk-dng.c to the save_dng function to separate in camera and desktop modes since this commit https://bitbucket.org/hudson/magic-lantern/commits/9e99764f432025872286f87d5b7e10014061277f?at=fullres-silent-pics (https://bitbucket.org/hudson/magic-lantern/commits/9e99764f432025872286f87d5b7e10014061277f?at=fullres-silent-pics) ?
Now, I believe raw_rec can be ignored as is superseeded by mlv_rec anyway, right?
/LE:
Got to build it with multiple values:
To work C.FnIV must be set as 1 or 3.
"Hold on..." has lv_focus_status=1
"Half-shutter pressed..." has lv_focus_status=1
"Focusing..." has lv_focus_status=3 when the lens is focusing and lv_focus_status=1 when idle, it jumps between these values as you change focus point and hold * again.
wait_lv_frames = 4 or 6 never gets to "Focusing..."
wait_lv_frames = 8 gets "Focusing..." sometimes
wait_lv_frames > 10 gets "Focusing..." every timeYou need to select a focus point or else it does not work, it took me a while to get this, being used with the Canon software since it has some sort of default point anyway. :D
-
wait_lv_frames > 10 gets "Focusing..." every time
The value is higher than expected; does this mean there is a noticeable delay between pressing the button and focusing?
Another hypothesis: what FPS do you have in LiveView in photo mode? IIRC it's 60 on the EOS-M, and 30 on most other cameras.
every time you need to select a focus point or else it does not work
If you don't select a focus point, what happens? It stays on 1?
Good catch about compiling errors.
-
The value is higher than expected; does this mean there is a noticeable delay between pressing the button and focusing?
Not that I see, given the 22mm is slow(ish).
Another hypothesis: what FPS do you have in LiveView in photo mode? IIRC it's 60 on the EOS-M, and 30 on most other cameras.
How do I see the FPS?
If you don't select a focus point, what happens? It stays on 1?
Yep, behaves like wait_lv_frames = 4 does for me.
On another thought, I can't repro the success with wait_lv_frames = 10 anymore.
I was testing in a dark room in the previous post, but now in daytime light it just does not focus. I bumped it to 15 and it's better but it still misses sometimes, might depend on whether the AF says it's got focus faster or something?
Also, after it starts, even if C.FnIV is on 1 or 3 it will not engage Focus unless I change the mode, say from 1 to 3 and back, after that it works.
-
I think instead of waiting X frames and then waiting for focus, we need to check the focus status after each frame.
FPS is easy to check, open the FPS override submenu, but don't enable the feature (just read the default configuration).
-
FPS is easy to check, open the FPS override submenu, but don't enable the feature (just read the default configuration).
29.9xx
-
Hi,
I recently started using ML on a 1100D for astrophotography. Great!
To gain more flexibility towards short but frequent exposures, I would like to use the silent mode.
Therefore, I installed Cygwin/Yagarto as described in http://magiclantern.wikia.com/wiki/Build_instructions/Unified and downloaded the fullres-silent-pics branch (hudson-magic-lantern-e6e97539f082.zip).
I failed, however, to compile because of this error: "Makefile.filerules:33: rule for destination „entry.o“ failed" (translated from the german message, possibly not exactly correct). I found that entry.d was built, but not entry.o. When I executed the build command manually, gcc (4.6.2) also created entry.d, but not entry.o - without error message.
Since I'm not familiar with unix, I don't understand what happens, but it looks to me a bit like a compatibility problem. Is the Cygwin/Yagarto setup still up-to-date?
-
I recently started using ML on a 1100D for astrophotography.
I would like to use the silent mode.
You can't, it's not supported: http://builds.magiclantern.fm/#/features (http://builds.magiclantern.fm/#/features)
Trying to compile it yields:
Will NOT load on:
1100D (raw_lv_redirect_edmac, raw_lv_request, raw_lv_settings_still_valid, raw_lv_release)
-
Maybe a dumb question, but I just installed the latest nightly build on my 5D3 and in the drop down options menu of the silent mode the "full res" option is missing. The last option is slit-scan. Is the full-res mode already included or am I missing something?
Thanx!
Niels
-
Not included in nightly builds yet. You may compile it by yourself or use a silent.mo made available for download. You have to search a bit in this thread or wait a little longer.
-
@eloml
silent.mo doesn't compile on 1100D because the LV raw data is not available on 1100D. The full-res stuff doesn't actually need raw LV. So you can WEAK_FUNC those functions. The module will compile and you can use full-res mode, but none of the other modes will work. You can also try merging the 'new-lv-buffer-detection' branch which has support for LV raw on 1100D, but it is incomplete and quite out of date, so you will lots of merge conflicts.
-
Maybe a dumb question, but I just installed the latest nightly build on my 5D3 and in the drop down options menu of the silent mode the "full res" option is missing.
Here is a build for 5D3 with firmware 1.1.3: http://we.tl/WTYtLFJv98 (http://we.tl/WTYtLFJv98)
Info about the build here: http://www.magiclantern.fm/forum/index.php?topic=9741.msg142766#msg142766 (http://www.magiclantern.fm/forum/index.php?topic=9741.msg142766#msg142766)
If you are using firmware 1.2.3 you are out of luck for now, as it's has a separate branch and I'm not that brave to try and merge it with the FRSP one :D
/LE:
Disclaimer:
I don't have anything else besides a M1, but I can compile ML, so keep in mind the warning on top of this page: http://magiclantern.fm/downloads.html (http://magiclantern.fm/downloads.html) STILL applies if you choose to install one of these builds.
-
Thanks for sharing @Licaon_Kter and will definitely check it out.
Hopefully at the hotel that I'm staying at in PR will have computers with USB so I can download and test it out w 5D3 113.
If not, then I'll have to wait till I get back into USA on the 27th. (Wife wouldn't allow me to bring MBP on vacation w me - LOL)
However, I already have one compiled from a week or two ago not sure if it'll be the same but since it came from the same branch in which I'm sure it is.
[emoji108]
-
I recently started using ML on a 1100D for astrophotography. Great!
To gain more flexibility towards short but frequent exposures, I would like to use the silent mode.
Do you plan to use it for planetary or deepsky imaging?
Because there's no significant gain to use FRSP for astrophotography; too slow for planetary and not relevant about mechanical stress vs sensor heating for deepsky.
-
Do you plan to use it for planetary or deepsky imaging?
For planetary imaging the raw video feature should be useful, but since it's not really available for the 1100D (yet?) I postponed this.
I plan to use the silent mode for bright deepsky objects, e.g. globular clusters, for which exposure times well below a minute are sufficient, at least at high ISOs. (Surprisingly, I found that stripe like artefacts, which look like those produced by CCD readout amplifiers, are not amplified proportionally when I increase the ISO value. Therefore, I prefer to set ISO to 3200, take a large number of images (hundreds to thousands a night), and stack them.)
-
I see, for bright deepsky objects _indeed_ FRSP looks interesting.
However live view will be active during all acquisitions time so the thermal signal will be very high on frames. Sensor will reach 45~50°C (loc.temp.<10°C) in a few time and it will be very hard to reduce it with calibration even with hundreds of dark frames, because temperature rising is not linear and not stable during acquisitions. Plus bias frames are a bit... tricky to make in FRSP (see the minimum exposure time what you can expect, it depends of your camera) so the FPN + offset reduction is not perfect. :/
-
Does LiveView heat the sensor also during regular intervalometer / bulb timer shooting? At least during cold nights during the last weeks here, the results I got were not so bad despite I had actived LiveView permanently. Mostly, the final limitation for resolution was due to bright skies or amp glow of the 1100D.
Anyway, here comes into play the biggest advantage of the 1100D: Its low price. I plan to disassemble the body in order to remove the filters and perhaps the mirror, which starts to shadow at F/4 or below. Thereby, I plan to insert a peltier like I did earlier with an IXUS.
-
However live view will be active during all acquisitions time
That's not true. FRSP runs in "LV mode" so that the shutter is open, but LV itself is disabled during acquisition, and you could have disabled the whole time if you wanted.
-
Updated my M1 build again (http://www.magiclantern.fm/forum/index.php?topic=9741.msg143100#msg143100)
@a1ex: What's holding this branch from merging in master?
If there's a need for more testers I can build it for some cameras, as needed ( well except off branch ones like 5D3 1.2.3 :D )
-
That's not true. FRSP runs in "LV mode" so that the shutter is open, but LV itself is disabled during acquisition, and you could have disabled the whole time if you wanted.
We can open the shutter and take FRSP without activated the LV? o.O
My mistake, I never could do this on the 5D2; I have to activate the LV to open the shutter and get access to FRSP. What version do you use?
Of course, if the LV _I mean flux processing made by DIGIC and screen_ is off it should not heat too much face to regular RAW pictures.
Stays the problem of bias frames BTW...
-
LV cannot be running during the call to FA_CaptureTestImage, otherwise it won't work. You enter LV "mode" (to get the shutter open), but when you actually take a pic, FSRP disables LV.
/* get out of LiveView, but leave the shutter open */
PauseLiveView();
It then turns LV back on after QR, but if you're shooting a time lapse for example with a short enough interval between shoots, you'll probably never get back into LV. Therefore LV is effectively not running at all, even though you are in LV "mode"
-
A couple of Questions (EDITED):
a - Can I use Half Shutter as Autofocus only, and * or other button for silent pictures? (I did 500 hundred silent pict doing manual focus for this) (RESOLVED, read my post below)
b - Can I put off the sound of the ETTR for use in a quite enviroment situation, like a theatre, where Silent Pic is optimal? (YES< BEEP, Test Tones > OFF
c - Can someone provide me a link to download ML for 5d 1.1.3, including Silent Pic Full Res? Actually I have 1.2.3 RESOLVED! READ @@DeafEyeJedi
Thanks!
-
a - I've request for this in the past to no avail. It would really help us a lot though obviously not having to rely on manual!!! (However, @Licaon_Kter may have fixed this in recent build from link below.)
b - Not sure if this would be possible but it would be a good advantage -- good thinking!
c - Did you not like the build I sent you for 113 FRSP? Perhaps you rather implement this with the latest nightly - correct?
If so, here's the latest build for 5D3 113 compiled w FRSP from @Licaon_Kter (haven't test this one myself yet since I'm in PR until this weekend)
http://www.magiclantern.fm/forum/index.php?topic=12523.msg142895#msg142895
-
@DeafEyeJedi
That compile doesn't work fine.
I think we can wait for someone with skills to compile the last one for 1.1.3
Any help?
-
The link I just provided above is a different build compiled w FRSP for 5D3 113 than the one I sent you earlier few weeks ago (which was compiled by @kosmarnik) sorry for the confusion...
But you should definitely check this one out in particular!
Thanks again @Licaon_Kter for compiling this build w Autofocus fix for FRSP... [emoji106]
-
The link provided by @DeafEyeJedi works perfect as I tried with 20 pictures. The only module that don't have is Old Raw. But this is to other thread.
- I've founded that if you press Half Shutter you can do Autofocus and not take photo. For me is perfect!
- Hi res Pic works fine!
- Can we take Silent Picture High Res Dual ISO pic?
Thanks @Licaon_Kter your build works perfect.
Thanks Again @DeafEyeJedi
-
Sweeet and yes ofc you can use Dual-ISO during FRSP! [emoji6]
-
Hi,
Any chance of a fresh build for a 7D please.
Cheers.... Otto
-
Are you able to compile it?
-
If I was able to code I would. Unfortunately I can't hence my request.
I don't have the facility to compile either.
Always willing to test though.
-
@Licaon_Kter: I've updated autofocus detection code; can you check whether it still requires 10 iterations, or fewer of them are enough now?
-
Compiled all the platforms supported by the silent module (http://builds.magiclantern.fm/#/features) so maybe more testers help.
Some notes:
1. Up to commit 3082908 (https://bitbucket.org/hudson/magic-lantern/commits/branch/fullres-silent-pics)
2. Added some lv_focus_status printing maybe it helps troubleshooting.
3. Added the Depth of field display (http://www.magiclantern.fm/forum/index.php?topic=14734.0) patch plus these (https://bitbucket.org/hudson/magic-lantern/commits/848d3944d5b91f84d4b195b02ee8db5231f773f4) three (https://bitbucket.org/hudson/magic-lantern/commits/d190470d38c889cabcc75e0cc9e4b08ec7af6aa0) tweaks (https://bitbucket.org/hudson/magic-lantern/commits/35295ffb47063166ddf5bbd2761db7aee0dec682).
4. Bypassed the dual_iso/raw_rec module build error introduced in commit 9e99764 (https://bitbucket.org/hudson/magic-lantern/commits/9e99764f432025872286f87d5b7e10014061277f?at=fullres-silent-pics) ( info here (http://www.magiclantern.fm/forum/index.php?topic=12523.msg142493#msg142493) )
5. For the 5D3 1.1.3 build I got the .FIR from the nightlies.
6. Both the 550D and the 600D build have no .FIR, not even in the nightlies.
7. For 7D there are 2 builds, maybe 7D owners know why/how.
8. 650D was not build because
[ CC ] raw.o
../../src/raw.c: In function 'raw_update_params_work':
../../src/raw.c:538:10: warning: #warning FIXME: are these values correct for 720p and crop modes? [-Wcpp]
#warning FIXME: are these values correct for 720p and crop modes?
^
../../src/raw.c:573:47: error: 'RAW_PHOTO_EDMAC' undeclared (first use in this function)
raw_info.buffer = (void*) shamem_read(RAW_PHOTO_EDMAC);
^
../../src/raw.c:573:47: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [raw.o] Error 1
make[1]: Leaving directory `/magic-lantern/platform/650D.104'
make: *** [650D] Error 2
Link: <removed>
@a1ex:
1. src/focus.c is missing an S in line 24 at dof.diplay
2. *-hold AF works as expected with the default 5 iterations now.
/LE: use nightly
-
Before merging, I'd like feedback on the following tests:
https://bitbucket.org/hudson/magic-lantern/pull-request/609/fullres-silent-pics/diff
-
Technical issues aside, those look mostly ok, can you point me to a post where maybe the correct workflow is explained?
(https://i.imgur.com/VJv9EEX.jpg)
As of now it look like I'm always some stops wrong
if I set = I get
1/125 = 240ms ( 1/4 )
1/4 = 500ms ( 1/2 )
0.5" = 789ms
I can never get the chance to see what I will get, even with Exp.Override the result is over exposed compared to what I previously seen on screen.
What am I doing wrong?
-
What am I doing wrong?
http://www.magiclantern.fm/forum/index.php?topic=12523.msg120758#msg120758
-
http://www.magiclantern.fm/forum/index.php?topic=12523.msg120758#msg120758 (http://www.magiclantern.fm/forum/index.php?topic=12523.msg120758#msg120758)
I've seen that but I don't know how that helps.
Later I'll try to run the program too.
-
It explains why your numbers don't match.
In a normal exposure, the mechanical shutter controls integration time. There are periods of time where the pixels are "active" (able to collect light), but are being blocked by the mechanical shutter. Mostly this is the time after the shutter closes, but while the pixels are still being read out. FSRP uses basically the same sequence, except the mechanical shutter is not activated. So pixels are receiving light during the periods of time they would normally be blocked by the mechanical shutter.
It takes some finite amount of time to read every line of the sensor, and the lines are read one by one. You can't deactivate or reset the lines before you read them out. So if you don't use a mechanical shutter, you are going to see a brightness gradient, and there's going to be some extra exposure time.
Maybe I can explain better with an example (way over simplified, but makes the point):
t1: global reset (turn the pixels on)
t2: mechanical shutter open
t3: mechanical shutter closed
t4: readout begin
t5: readout finish
Normal photo exposure time = t3 - t2
FSRP exposure time = gradient from (t4 - t1) to (t5 - t1)
FSRP total exposure time* = t5 - t1
*according to a1ex, there is some other stuff happening that is making the reported FSRP time even longer (longer than actual integration time), the time you see on the screen is simply the amount of time the function call to FA_CaptureTestImage took.
-
@SpcCb: I've added the ability to take dark and nearly-bias frames (press half-shutter outside LiveView).
Probably it's not very useful without a way to mix regular pictures with dark/bias frames, but I think this would be a job for the scripting engine.
Still, this trick now lets you take a large number of dark frames without wearing the shutter mechanism.
note 1: by nearly-bias frames I mean dark frames with the shortest exposure time possible - same thing that you would get with a regular picture at 1/4000 and lens cap on, for example.
note 2: in LiveView, with some cameras, it is possible to take true bias frames (with zero exposure time) by removing the range checks from the shutter fine-tuning feature.
note 3: if we ever figure out how to drive the sensor at full resolution and with rolling shutter (thus removing the shutter speed limitation), true bias frames might be possible as well. But for now I'm kinda clueless about how to setup the sensor this way.
-
Beautifully well done, @a1ex!!!
Looking forward to testing these out...
Glad to see you back in action!
[emoji108]
-
It explains why your numbers don't match. 8<-------------8<-------------8<-------------8<-------------
Thanks, although I do understand how things work, I do want to have a useful LiveView for FRSP too, hence my question.
Is there a way ( I initially thought Exp.Override was it, but it's not ) to see in LV what you will get when you use FRSP?
I know that using LV display gain with say 3 EV get's things on par though, so maybe this is the solution.
@a1e: So no dark/bias frames on M1 since LV is always on?
-
I did a little experimentation between Silent Full Res vs Regular shutter.
Same settings in both shots.
Like other user say: the exposition is over exposed in the live view. And for get a normal result I had to underexpose too much for understand what I am shooting. After the shoot, I have enabled zebras to show me the over exposition in black and green.
5 Mark III 1.1.3 compile by @Licaon_Kter FRSP commit e6e9753
Lens Canon 50 MM 1.4 @F5
Iso 100
1/20
Auto WB
I tried to apply ETTR but I get over exposure and everything is blank.
I think if Silent Picture function is taking more continuous light and is a normal operation for the no actuation of the shutter, could be implement a filter like a digital ND. In that case, I don't know if this is possible, - maybe is not constant - how many EV over the the regular photo is working Silent Pic to create that filter (Sorry A1ex, this is not my territory ;)
Here the photos: https://www.dropbox.com/s/iau9k8vwbibls9n/Silent%20Pic%20vs%20regular.zip?dl=0
-
Is this the version with the latest changes?
Mercurial changeset : 5ce22358adb5 (fullres-silent-pics) tip
Built on 2015-03-25 05:03:58 UTC by codio@tina-fire.
I'm learning how to build from source and want to make sure, before I report bugs on a 7D
-
@guisquil
FRSP commit e6e9753
-
Compiled all the platforms supported by the silent module (http://builds.magiclantern.fm/#/features) so maybe more testers help.
Some notes:
1. Up to commit 5ce2235 (https://bitbucket.org/hudson/magic-lantern/commits/branch/fullres-silent-pics)
2. Added the Depth of field display (http://www.magiclantern.fm/forum/index.php?topic=14734.0) patch plus these (https://bitbucket.org/hudson/magic-lantern/commits/848d3944d5b91f84d4b195b02ee8db5231f773f4) three (https://bitbucket.org/hudson/magic-lantern/commits/d190470d38c889cabcc75e0cc9e4b08ec7af6aa0) tweaks (https://bitbucket.org/hudson/magic-lantern/commits/35295ffb47063166ddf5bbd2761db7aee0dec682).
3. Bypassed the dual_iso/raw_rec module build error introduced in commit 9e99764 (https://bitbucket.org/hudson/magic-lantern/commits/9e99764f432025872286f87d5b7e10014061277f?at=fullres-silent-pics) ( info here (http://www.magiclantern.fm/forum/index.php?topic=12523.msg142493#msg142493) )
4. For the 5D3 1.1.3 build I got the .FIR from the nightlies.
5. Both the 550D and the 600D build have no .FIR, not even in the nightlies.
6. For 7D there are 2 builds, maybe 7D owners know why/how.
7. 650D was build too this time since a1ex fixed it
Link: <removed>
/LE: use nightly
-
Great. But i can not find a build for 5d mk3 fw123 ??
-
Great. But i can not find a build for 5d mk3 fw123 ??
eh http://www.magiclantern.fm/forum/index.php?topic=12523.msg143101#msg143101 (http://www.magiclantern.fm/forum/index.php?topic=12523.msg143101#msg143101)
see below
-
I know that using LV display gain with say 3 EV get's things on par though, so maybe this is the solution.
The problem is that the difference between the exposure time you set and actual exposure time varies. It varies by camera (b/c readout times/speeds vary by camera), varies by shutter speed (faster shutter speeds are more off than slower ones), and it even varies line by line within the same image.
I don't think it wouldn't be that hard to implement something like this, but you would need to precisely quantify this curve on every camera. This data would also be quite useful in other ways, for example getting the exposure metadata exactly correct.
-
I don't think it wouldn't be that hard to implement something like this, but you would need to precisely quantify this curve on every camera. This data would also be quite useful in other ways, for example getting the exposure metadata exactly correct.
So I need to run this: http://www.magiclantern.fm/forum/index.php?topic=12523.msg120758#msg120758 (http://www.magiclantern.fm/forum/index.php?topic=12523.msg120758#msg120758) and that would help?
/LE: Compiled 5D v1.2.3 also, hopefully it merged ok from commit c7655e9 (https://bitbucket.org/hudson/magic-lantern/commits/branch/5D3-123)
Same link: < (https://mega.co.nz/#F!YVBl0ZhS!Z5-ZnbWm8EU7xBE29nNPJw)removed>
/LE: use nightly
-
Thanks for the builds licaon_Kter I will endeavour to test over the next few days. In answer to your question re: the 7d Builds:
6. For 7D there are 2 builds, maybe 7D owners know why/how.
I have downloaded both. From what I can see the magiclantern-Nightly.2015Mar25.7D_MASTER203_DoF_FRSP_commit5ce2235.zip file does NOT include the following files:
- 7D_203.fir at the root level
- 7D_203.sym in the modules folder
That would suggest the build contained in file "magiclantern-Nightly.2015Mar25.7D203_DoF_FRSP_commit5ce2235.zip" is the correct one to download and test with.
Cheers... Otto
-
@Licaon_Kter:
Please read this thread before providing any more builds.
http://www.magiclantern.fm/forum/index.php?topic=12608.0
-
With the 7D set in 'M'anual mode I am no longer able to adjust the exposure compensation.
Upon investigation I discovered that the large thumbwheel appears to be mapped to the "Bracketing" exposure control normally linked to the small thumbwheel. Note that the 'Bracketing' exposure control was still associated with the small thumbwheel at the same time. (this is a repeatable problem)
Also, when I switched from 'M'anual to 'AV' mode and tested the exposure override it worked as per normal however, whilst making the adjustment, the camera froze. Battery removal was required to power down and reset the camera. I could not reproduce this on demand so will monitor this.
Auto ETTR seems to be a workaround for the lack of manual exposure control but it needs to be fixed.
Cheers.... Otto
-
@a1ex: Any chance to have the AF wait cycle count selectable in ML menu? It's 5 now, but I feel it might need a bit longer and compiling, extracting card, card reader, copy, card reader, insert card and test is getting tiresome.
And you've got a PM.
-
For your own experimentation, yes, feel free to add this setting to the menu. But for everyday usage, I'd rather try to find a value that covers most cases (ML menu is very cluttered anyway - search for "yamlmo" ;) ).
-
Tested the build from Licaon_Kter on my 50D. I can take single FullRes photos, but if i try the intervalometer after the first photo i get 1 white photo, 1 black photo, 1 white photo, and so on...
Do you need a sample or log?
-
Can you record a video of the camera screen, and upload two sample DNGs (1 black and 1 white)?
-
After some tries i realised that my previous description of the bug was not 100% correct.
The procedure after installing ML build(magiclantern-Nightly.2015Mar25.50D109_DoF_FRSP_commit5ce2235):
-reset ML defaults
-activate Silent.mo
-take a bunch of full-res-silent pics
-activate the intervalometer with the LV off (4 pics every second).
-leave menu and the intervalometer starts: the previews are white noise and the DNGs are full black
-enter menu with LV still on and leave menu, the intervalometer starts: the previews are full white but the DNGs are OK.
-take a bunch of full-res-silent pics
Video of the procedure: Sample of 1 black DNG (white noise on previre) and 1 OK (white on preview): http://we.tl/yLhsuXXNJu
-
Same link: https://mega.co.nz/#F!YVBl0ZhS!Z5-ZnbWm8EU7xBE29nNPJw
Tested with a Canon 7D, I get this crash, and as other commented pictures are over exposed.
https://www.youtube.com/watch?v=99flO-87y2s&feature=youtu.be (https://www.youtube.com/watch?v=99flO-87y2s&feature=youtu.be)
Crash log:
ASSERT: GetMemoryAddressOfMemoryChunk( GetFirstMemChunk( pMem1AllocateListItem->hMemSuite ) ) == pMessage->pAddress
at SrmActionMemory.c:1154, task RscMgr
lv:0 mode:3
Magic Lantern version : Nightly.2015Mar25.7D203
Mercurial changeset : 5ce22358adb5+ (fullres-silent-pics) tip
Built on 2015-03-25 09:23:46 UTC by magiclantern@magiclantern-VirtualBox.
Free Memory : 238K + 2720K
-
@vascostmr: solved (removed the dark frame feature for now).
@guisquil: does the crash happen every time you take a regular picture after a silent one? does it also happen after you record a raw video and then try to take a picture?
-
@guisquil: does the crash happen every time you take a regular picture after a silent one?
Yes it happens every time I take a Picture, and not just when i do it after a silent one, I noticed that when im not in live view if I only do a half press on the shutter the camera still takes a silent pic, when I try to see the picture in file manager, sometimes i see this message:
"Preparing
A:?DCIM/10EOS7D/DARK000.MLV
Error: GUID within the file chunks mismath"
-
Dark frame feature removed, so it no longer makes sense to report bugs about it.
Also, I have difficulties understanding your post, since you seem to mix unrelated issues in the same phrase. I'm still confused about when the crash happens.
Half-shutter press is the proper way to trigger a silent picture. Full press probably just happens to work, especially if you don't press it too fast (but I don't know how to intercept it properly).
-
Also, I have difficulties understanding your post, since you seem to mix unrelated issues in the same phrase. I'm still confused about when the crash happens.
The crash happens when I take a picture using the regular view finder not live view while the silent.mo is On / Full-res, MLV
-
@SpcCb: I've added the ability to take dark and nearly-bias frames (press half-shutter outside LiveView).
Probably it's not very useful without a way to mix regular pictures with dark/bias frames, but I think this would be a job for the scripting engine.
Still, this trick now lets you take a large number of dark frames without wearing the shutter mechanism.
note 1: by nearly-bias frames I mean dark frames with the shortest exposure time possible - same thing that you would get with a regular picture at 1/4000 and lens cap on, for example.
note 2: in LiveView, with some cameras, it is possible to take true bias frames (with zero exposure time) by removing the range checks from the shutter fine-tuning feature.
note 3: if we ever figure out how to drive the sensor at full resolution and with rolling shutter (thus removing the shutter speed limitation), true bias frames might be possible as well. But for now I'm kinda clueless about how to setup the sensor this way.
E-nor-mous.
Over flow by work right now, but right I get free times I'll experiment this!
Do you know witch camera could done the ZET (zip exposure time, what we have on scientific cameras)?
-
@a1ex
"@guisquil: does the crash happen every time you take a regular picture after a silent one? does it also happen after you record a raw video and then try to take a picture?"
It's my case of crash and error, I removed the battery and everything is fine.
The only thing that I can't understand is the exposition in the live view. I tried ETTR but is going to high. By me, the user, I have to underexposed too much in order to get something decent. Any post about it? I read this thread.
-
@SpcCb: to experiment with dark frames, compile 5ce22358adb5 (not later). This feature caused problems (see last reports); it's not very hard to fix, but it adds quite a bit of complexity (if I fix this, it may delay merging fullres to main tree even more). So I've removed it for now, and revisit it after merging (but the code is still there to experiment with).
What do you mean by "zip exposure time"? (have a link?)
@budafilms: ETTR with the SET option in LiveView will set the exposure for regular pictures, so it will overexpose the silent ones. You need ETTR to meter directly from the silent image - e.g. set it on "always on". You will need to take a few test pictures until the exposure settles (it won't get it right from the first try). But during a timelapse, usually the exposure variations are small enough, and if you close the aperture enough, it will work just fine.
For timelapse, I recommend staying above ~0.5 seconds anyway, otherwise it will be next to impossible to deflicker with current tools (that don't know about the exposure gradient).
-
I know that using LV display gain with say 3 EV get's things on par though, so maybe this is the solution.
On a second thought... LV Display Gain is no solution as it will disable: Zebras, Spot Meter, False Color, Histogram, Waveform and Vectorscope. :-|
@Licaon_Kter: I've updated autofocus detection code; can you check whether it still requires 10 iterations, or fewer of them are enough now?
Tested a bit more and the current 5 works ok _most_ of the time, but not always.
I bumped it to 10 and it works better (at least on my M1), I find it's kinda hard to miss press * and have it take a picture now, while with 5 I had to be careful to hold it quickly enough.
Regarding AF slow down, I don't see any but then again, my 22 is rather slow, I'll retest with the 18-55 when I get a chance.
-
@SpcCb: to experiment with dark frames, compile 5ce22358adb5 (not later). This feature caused problems (see last reports); it's not very hard to fix, but it adds quite a bit of complexity (if I fix this, it may delay merging fullres to main tree even more). So I've removed it for now, and revisit it after merging (but the code is still there to experiment with).
I saw it, don't worry ;)
What do you mean by "zip exposure time"? (have a link?)
I mean camera who have capability to take ultra short exposures by electronic shooter, like 1/10 000s, what is considerate as a 0s exposure (zip => zero, in 'underground' language).
You can find it on cameras made by Finger Lake Instrumentation (http://www.flicamera.com/), The Imaging Source (http://www.astronomycameras.com/), Santa Barbara Instrument Group (https://www.sbig.com/), etc.
It is a very important point in scientific imaging because with this kind of camera we can make very precise Master Bias Frames, very hard to get with a camera with a 'long' electronic exposure because we get 'some' thermal signal on frames mixed with other signals. It refers to our discussion about FPN reduction etc.
Beside, it's opening many other applications, like ultra short exposure time for high speed imaging, etc.
Things what we can do with CHDK for example.
-
You can do that in LiveView at low resolution (with shutter fine-tune - iirc it does 1/50000 on 60D), but with rolling shutter.
-
Bumped into an issue on my M1 (at least using my modified build with 10 cycles): forget FRSP on (MLV or DNG it does not matter) and switch to Movie mode (normal one not RAW)
And now 2 things might happen when you press/hold * for AF
1. When not recording you get a black screen with "Manual (M) mode required" warning
2. When recording you get the same black screen with "Manual (M) mode required"
BUT then the led blinks orange fast and camera shuts down!
Trying to start it again yields led flickering green slower, lens activating and deactivating ( the 22mm is noisy) and then the camera stops. (it did not show anything anyway)
Removing the battery fixes it.
The card has no MOV recorded but there's a 0bytes CRASH.LOG.
Yep, this is why this needs more testing: more users digging up AND reporting issues and avoiding merging in main 'till it's good enough, chicken and egg all the way. :D
Testing the other silent modes while movie is recording:
1. simple - takes the pictures but stops recording when it's done.
2. slit-scan - stops the recording, shows a black screen until you press a button again.
-
@a1ex
ETTR " Always ON" Works perfect for Silent Picture!
I think more USERS should try this. I will paste the text for more visibility:
@budafilms: ETTR with the SET option in LiveView will set the exposure for regular pictures, so it will overexpose the silent ones. You need ETTR to meter directly from the silent image - e.g. set it on "always on". You will need to take a few test pictures until the exposure settles (it won't get it right from the first try). But during a timelapse, usually the exposure variations are small enough, and if you close the aperture enough, it will work just fine.
-
@guisquil: if you take a regular picture, outside LiveView, but with silent pics turned off, do you get any crash?
If not, I think it must be a race condition between silent pics and Canon picture taking code, and it might also happen if you try to take a silent pic by fully pressing the shutter (instead of just half-press).
-
I would like to use the silent picture mode on two bodies:
-5D3 (preferably 1.2.3, but if there is only a 'reliable' build for 1.1.3 I will consider downgrading to 1.1.3). Where can I get the latest build with full-res silent picture for de 5D3 1.1.3?
-550D firmware 1.0.9. Is there a build available for this camera? Of course, I will test it and provide feedback
One other question: I use these bodies extensively on a cognisys stackshot where the camera is triggered with a shutter cable. Unfortunately, this cable only allows full shutter button press. Is there a possibility to configure the camera to take a silent picture in live view when the shutter button is fully pressed? I don't care about autofocus, since everything is manual focus only.
Thanx!
Niels
-
You just need a tweaked cable where shutter release (full press) is connected to focus input. Everyone with an soldering iron could do that.
And drop the word "2-pole 3-way switch/4 way" to your soldering artist ...
-
@guisquil: if you take a regular picture, outside LiveView, but with silent pics turned off, do you get any crash?
If not, I think it must be a race condition between silent pics and Canon picture taking code, and it might also happen if you try to take a silent pic by fully pressing the shutter (instead of just half-press).
I don't get a crash when silent pics is turned off and taking regular pictures.
-
Thanx Walter,
I think I will manage to get / make a cable.
Where can I get the proper builds for the 550D 1.0.9 and the 5D3 1.1.3?
Niels
-
Top of page -> Downloads -> Browse Nightly Builds
-
I downloaded the old v2.3, installed it on my 550D and replaced the files with the ones from •magiclantern-Nightly.2015Mar26.550D109.zip
In the menu under silent picture the "full resolution" option is missing >:(
What am I doing wrong?
-
Nothing. FRSP is not included in nightlies yet.
See reply #547
-
I see. I couldn't resist and installed the nighties from the links in reply #547. A quick test seems to show that it works pretty well on both my 550D 1.0.9 as well as my 5D3 1.2.3 :D
This is amazing. A wonderful job!
Is this page: https://mega.co.nz/#F!YVBl0ZhS!Z5-ZnbWm8EU7xBE29nNPJw
updated as bug's are fixed and new versions come out? Can I just bookmark it and regularly check for new versions? Where can I provide my feedback?
One other thing that amazes me: a normal CR2 file at 100 iso from my 550D is 19.0 MB. A DNG from the FRSP at 100 iso is 31.3 MB. Where is the difference coming from?
Thanx
Niels
-
Is this page: <removed>
Nope, no sense since so few added feedback here too, and there are plenty of issues before this will get merged.
Do feel free to give feedback regarding these issues: https://bitbucket.org/hudson/magic-lantern/pull-request/609/fullres-silent-pics/diff (https://bitbucket.org/hudson/magic-lantern/pull-request/609/fullres-silent-pics/diff)
-
One other thing that amazes me: a normal CR2 file at 100 iso from my 550D is 19.0 MB. A DNG from the FRSP at 100 iso is 31.3 MB. Where is the difference coming from?
CR2s are compressed. Silent pics are the raw data dumped straight into uncompressed DNG format (or MLV). Canon probably uses some kind of lossless compression implemented in hardware. AFAIK, we don't know how to get the Canon firmware to save some raw image buffer as a CR2 or use the hardware compression module, though it should be theoretically possible if it is reverse engineered. We could also do our own compression, but running on the general purpose ARM processor, it would be really slow (potentially several minutes to save a single, full res image).
-
For my memory cards it is not a problem, but for harddrive space it is nice if there is some compression. Of course, this is easily solved with winrar :D
Would also be (very) nice if the people from canon would support Magic Lantern to allow writing CR2's and many other features.
-
2. When recording you get the same black screen with "Manual (M) mode required"
BUT then the led blinks orange fast and camera shuts down!
On 60D, this behaves in an interesting way: when the black screen appears, recording is paused, and it's resumed cleanly (!) after this screen goes away.
Furthermore, during that pause, a fake shutter sound gets recorded in the video :P
Cool find.
-
Furthermore, during that pause, a fake shutter sound gets recorded in the video :P
Just tried it. That is crazy!
-
recording is paused, and it's resumed cleanly (!) after this screen goes away.
Furthermore, during that pause, a fake shutter sound gets recorded in the video :P
Normal (non raw) picture taking (non silent) during filming yields that for me.
/LE: Updated to 6e3bdba (https://bitbucket.org/hudson/magic-lantern/commits/branch/fullres-silent-pics) and it's working nicely, I see you raise the cycles to 10 (I keep forgetting to select a focus point before shooting, but after selecting one it AFs fine with *-hold) and you fixed the movie mode bug. Thanks
/LE2: But now I've hit another one (http://www.magiclantern.fm/forum/index.php?topic=14734.msg143409#msg143409) unrelated.
-
Alright folks, full-res silent pictures are now in the nightly builds!
Limitations:
- You can't do short exposures (please don't complain about overexposure).
- Minimum exposure time (when you set Canon shutter to 1/4000 or 1/8000) is actually a gradient (http://www.magiclantern.fm/forum/index.php?topic=12523.msg120750#msg120750) (timing analysis here (http://www.magiclantern.fm/forum/index.php?topic=12523.msg121962#msg121962)). For example, 5D3 can get 1/33.19 at the top of the frame and 1/6.30 at the bottom.
- 500D, 550D and 600D can't take exposures longer than 0.8 seconds :(
- No support for 1100D yet.
- All other cameras can take exposures up to 15 seconds.
Usage tips:
- To set aperture, you must enable Expo Override (or use a manual lens).
- ETTR works best together with intervalometer: use the "Always On" option, and close the aperture enough (or use ND filters), as much as you need to get exposure times above 0.5 seconds (otherwise the result may be impossible to deflicker with current tools).
General notes:
- Image is captured in the same way as a regular picture, but without shutter movement, and it's saved as DNG/MLV, not CR2/JPG.
- You should go to LiveView in order to open the shutter. However, during a silent capture (or during a silent timelapse), LiveView is paused (http://www.magiclantern.fm/forum/index.php?topic=12523.msg143120#msg143120).
Some things on the waiting list (research doesn't stop here) :
- luminance trigger (e.g. for lightning) (https://bitbucket.org/hudson/magic-lantern/pull-request/596/luminance-triggered-fullres-silent-pics)
- 30-second exposures (there is a semaphore that times out at 20 seconds, can be patched)
- dark and bias frames (http://www.magiclantern.fm/forum/index.php?topic=12523.msg143186#msg143186), for astrophotography (exposures with shutter closed)
- composite long exposures (e.g. average 1-second frames), which could improve dynamic range, temporal aliasing, erase moving subjects and other crazy things like that (backend: EekoAddRawPath (http://www.magiclantern.fm/forum/index.php?topic=13408))
- and (unicorn at the moment): driving the sensor in rolling shutter mode, to achieve fast exposure times (as in LiveView)
Thanks to the contributors (especially dmilligan and g3gg0) and testers from this thread (especially mk11174, Greg, nikfreak and Licaon_Kter)!
-
First short test looks fine on 600D. Exifs like aparture, focallenght, shutter-resease are not stored in dng, that´s correct?
Edgar
-
They are saved if you use the MLV format.
Didn't notice they are not present when you save as DNG, since I don't really use this info.
-
@a1ex Where do I donate? Can you pinpoint me to the right link. By the way great job Team Magic Lantern.
-
This has DNG metadata for silent pictures: https://bitbucket.org/hudson/magic-lantern/pull-request/603/dng-module-wip/diff
-
Alright folks, full-res silent pictures are now in the nightly builds!
Pô po pôo po ! Huge ! ^.^
-
Congratulations!!!! Great work!!!!
-
Any chance that we can use a * button as a back focus button on 5D3 to focus rather than taking the silent pic (halfway shutter works well) but if I had the * back button set as a focus (it still takes the silent photo as if I had pressed the shutter but didn't) I remember seeing @Licaon_Kter provide a fix copy of FRSP to being able to use * button for the M or did I read that one from another thread earlier?
Congrats on merging the FRSP into the nightlies @a1ex!
-
@a1ex
Question about ETTR with Silent Pic in this nightly build:
- I set ETTR Always ON
- The camera automatically set a value,
- I take the Silent Pic
In the top of the image said: ETTR Next ISO 800 1/15 (Was 3200 1/15)
When Live View return to the image, for a fraction of second show the Next iso, but the Always ON Mode start too fast to calculate the value. And the result is the over exposition. So, I go to the menu and turn OFF ETTR
Am I doing something wrong? Or this are the steps?
-
Any chance that we can use a * button as a back focus button on 5D3 to focus rather than taking the silent pic (halfway shutter works well) but if I had the * back button set as a focus (it still takes the silent photo as if I had pressed the shutter but didn't) I remember seeing @Licaon_Kter provide a fix copy of FRSP to being able to use * button for the M or did I read that one from another thread earlier?
It's already fixed, well on my M1 is, does it work on your M1 but not on 5D3?
You mean if you press * it takes a picture
BUT if you press * AND HOLD IT it does not focus and just takes a picture?
And you have custom function set up like this with 1 or 3 selected (or equivalent for your camera), right?
(http://support-sg.canon-asia.com/img/G0136677.gif)
And most important, you need to select a point FIRST ( touch the screen on your M1) before holding * !!! I keep forgetting this too.
/LE: looks like it's working without a point mostly anyway so your results may vary, per focus mode I guess.
-
@Licaon_Kter:
That's the exact setting I do for my photo work. Back focus button is a must. Tested on M1 and still takes the pic thinking it's "half shutter pressed" after pressing *.
Tested this on 5D3 and wow... it actually works as expected. It stays "Focusing" while holding down * which is beautifully well done -- It's mesmerizing to me! Thanks for the fix @Licaon_Kter and kudos to @a1ex & ML team for implementing this.
However, not sure what I could be doing wrong regarding the M1 on my end since it works for you, right?
5D3:
https://vimeo.com/123646026 (https://vimeo.com/123646026)
M1:
https://vimeo.com/123646027 (https://vimeo.com/123646027)
Another thing I noticed strange that FRSP won't work during movie mode anymore... with previous compiles in the past I used to be able to snap silent photos during recording (in case I like this particular look while filming) and it worked well for the most part. (h.264 I'm speaking of.. won't work w MLV/RAW recordings as expected which is probably the main reason why @a1ex put the restrictions on it in the nightlies? or no?) Perhaps we can ONLY still have it on during h.264 shooting?
*EDIT*
As per @Licaon_Kter's suggestion from earlier regarding M1 (hold * seamlessly after taking FRSP pic which seems to do the trick but not consistently)...
M1 (Test #2):
https://vimeo.com/123655190 (https://vimeo.com/123655190)
Thanks for your inputs!
-
@budafilms:
Enable the intervalometer as well (this way, it won't return to LiveView).
-
@DeafEyeJedi: It's @a1ex that did the work, I just provided some apparently needed feedback. :D
I just reset ML to defaults, enabled silent (and mlv_rec or not if saving DNG), but it doesn't behave like yours does.
For one, after it takes a FRSP it shows the picture and says<path to file.DNG/MLV...>
Saving 5....x2... ( xxx ms, xx Mb/s)
Captured in xxx ms.While yours doesn't or it looks like it does really fast. Do you have image review on or something?
Also, you said "hold * seamlessly after taking FRSP pic" but I did not say that, I was just enumerating the cases, not the steps.
You either single press * and get a picture OR you straight hold it, which in my is case is rather painful as I find the button size good enough for a small japanese girl ( target demographic for the M1 maybe? :D ) than for my chubbymanly hands.
And regarding this, while it focuses it just says "Focusing..." on screen, and it stays like that even if you stop pressing, which in your clips I did not see, did I miss it or ?
Sample: https://mega.co.nz/#!oABHHIyb!VNOQugQF-xqmH957FFU4MTHPjZfv2nSugY03P4JFAEU
Regarding movie mode silent snapping see this post: http://www.magiclantern.fm/forum/index.php?topic=12523.msg143308#msg143308 (http://www.magiclantern.fm/forum/index.php?topic=12523.msg143308#msg143308)
-
Well I just meant that you actually set the ball rolling to get @a1ex up to speed with the progress in FRSP so I thank you for that.
Anyway yes I did try both with and without image review within Canon Menu. Still doesn't make a difference.
I raw that thread earlier about movie mode snapping... it just worked fine for me on 5D3 during h.264 recording (yes I encounter these crashes before but taking the battery out helped sort it out) which may not be ideal for most users out there but to me I think it can be handy for some situations.
No big deal, really!
Just trying to understand why 5D3 back focus button * works flawlessly whereas the M1 seems to be a bit picky (definitely helps by pressing * immediately after taking the first FRSP and sometimes stays consistent for 2-3 FRSP snaps but then it goes back to taking pic thinking its half shutter pressed (although it would try to FOCUS for a second or two before taking the FRSP photo) so it's definitely focusing on its part but then something is overlapping the M1 into thinking the shutter is being pressed half way when it isn't...
Thanks again!
-
Looking at your last video, it says 40mm f/2.8, I only have the 18-55 and the 22, and they work ok.
Since you use the EF/S converter (right?) maybe it introduces some sort of delay that messes up the 10 cycles wait time, but since it's native for 5D3 it works faster.
Do you have any EF-M lens to test with?
-
Actually I did use the Pancake 40 with the EF/S adapter to use for all EF lenses... perhaps that's the culprit of this?
Good catch and will try again with an EF-M 22...
Stand by!
*EDIT*
https://vimeo.com/123680713 (https://vimeo.com/123680713)
Seems to be the same results? Works but inconsistently... Guess I'll just have to get used to this.
Though I don't think it is our big phat thumbs that are to be blamed for this kind of behavior... lol!
8)
-
I can repro this if I disable ExpSim, like you have it in all these M1 videos but not in the 5D3 one, with it on works as expected.
-
alex wrote:
They are saved if you use the MLV format.
Didn't notice they are not present when you save as DNG, since I don't really use this info.
Just for info and to give a feedback:
Yes, exifs are present in mlv and in dng, decoded with mlv_dump. But I noticed, the lensname-tag (or lensmodel, don´t know, what is needed) isn´t covered by my programs. And this lensname seems to be important for automated lens-correction in post-processing.
Tested with darktable, rawtherapee, ufraw, showfoto.
I cannot try the dng-module from dmilligan, because I cannot setup my compiling envirement at the moment.
Edgar
-
Is lens name recorded properly in regular MLVs?
In theory, it should work, since MLV silent pics reuses the metadata code from mlv_rec.
-
Block: LENS
Offset: 0x000001f0
Size: 96
Time: 1705.499000 ms
Name: 'EF100mm f/2.8 Macro USM'
Serial: ''
Focal Len: 100 mm
Focus Dist: 139 mm
Aperture: f/8.00
IS Mode: 0
AF Mode: 3
Lens ID: 0x000000BE
Flags: 0x00000000
Seems, that darktable and co use another tag for the lensname
Edgar
-
I readed a bit in darktable.
The lens is recognized by exiv2 and passed to the lensfun-library for len-correction
With a CR2-file I get these lens tags:
edgar@linux-9hqd:~/fullres> exiv2 -pt 5.CR2 | grep -ai lens
Exif.CanonCs.LensType Short 1 Canon EF 100mm f/2.8 Macro
Exif.CanonCs.Lens Short 3 100.0 mm
Exif.Canon.LensModel Ascii 70 EF100mm f/2.8 Macro USM
Exif.Photo.LensSpecification Rational 4 100/1 100/1 0/0 0/0
Exif.Photo.LensModel Ascii 70 EF100mm f/2.8 Macro USM
Exif.Photo.LensSerialNumber Ascii 12 0000000000
Usning a dng-file, decoded with mlv_dump from mlv, I see nothing..
edgar@linux-9hqd:~/fullres> exiv2 -pt 4.dng | grep -ai lens
edgar@linux-9hqd:~/fullres>
I really don´t need this lens-stuff for my astro-mlvs, but that´s, what I´ve seen playing with fullres-silent pics.
Edgar
-
I can't get FRSP to work.
When I set Silent Picture to Full-Res, the Silent tab turns "grey green" I suppose this has something to do with it telling me some setting is not alright. If I put it back to Simple, it turns back to real green.
I have tried taking pictures with Full Res, Half shutter, * and AF ON or what ever button I can press. If I take a normal picture, I see Silent picture taking a picture too before the camera crashes to Error 70.
I always end up with Error 70 what ever way I have tried taking a picture with FRSP.
I basically don't know how to take picture with FRSP, there are only two ways that I have managed to take FRSP and that is with Intervalometer with one of its many ways of activation or by taking a normal picture where I hear the shutter activate and once saw a Full Res Silent pic load right before the camera crashed and I got Error 70.
Please tell me what I am doing wrong or just what has to be done for it to work, I would very much like to do some timelapses without eating up my Shutter.
-
Delete ML directory and Autoexec.bin from card. Download latest nightly build. Copy extracted nightly build to card. Retry. Results?
-
When I set Silent Picture to Full-Res, the Silent tab turns "grey green" I suppose this has something to do with it telling me some setting is not alright.
Correct - read the help and do what it says (just like with most other ML functions).
Trying to take a regular picture and a silent picture at the same time will usually result in race condition, and there's little I can do about it.
-
@ Walter
Did that.
@ A1ex
I am not trying to take a normal picture and FRSP at the same time, that is one of two ways that I can activate it. The other way is with Intervalometer and its 3 different ways of activation.
If have the camera in P mode and when I scroll over FRSP it says FRSP only works in (M) Manual Photo mode. So I put it in Manual mode with Liveview ON and then it says FRSP only works with M (manual) Photo mode.. I can't or don't know how to take a picture with FRSP. What button do I press? Which one is default? I have Top-Bottom scan, is that not okey?
-
1.) Prefs tab -> Config files -> Restore ML default
2.) Restart cam
3.) Activate Silent.mo
4.) Restart cam
5.) Put cam to M mode
6.) Activate FRSP (Shoot tab -> Silent Picture -> Silent Mode -> Full-res)
7.) Activate Liveview
8.) Press shutter half
Results?
-
Half-shutter.
Are you in manual photo mode, or movie? Silent pics are only meant to work in photo mode. I could change that for cameras without a dedicated movie mode, but it's kinda pointless, because the shutter speeds useful with silent pics are not available in movie mode.
Settings that are grayed out should have no effect (if they have, that's a bug).
-
If have the camera in P mode and when I scroll over FRSP it says FRSP only works in (M) Manual Photo mode. So I put it in Manual mode with Liveview ON and then it says FRSP only works with M (manual) Photo mode.
Auto ISO. You must also select an ISO; auto ISO is not allowed (every exposure setting must be manual).
-
Ok, thanks guys for leading me through this.
I never take pictures with my MK III, this is the main reason for my great misunderstanding regarding "photo mode"
What was confusing me was the M Mode and Photo Mode.. When it said Liveview had to be ON I kept putting it on Movie Mode and not pressing the Start button while on Photo mode.
My MK III has 300 pictures taken and 800 Shutter Activations from when I turn the Camera On in Movie Mode ;)
Now to perform some Timelapses and keeping that shutter count low :)
-
Tab called "Shoot" and icon used may give some hint ...
-
I found out that raw_twk.mo makes the camera activate the shutter while taking a FRSP and then crashes the camera to Error 70.
I suppose there wont be a fix for this as raw_twk seems more or less unsupported.
Its not something of a world problem, I can just activate/deactivate the module depending on what I want to do. But it would be nice if I didn't have to :)
Atleast its on record now.
-
I am very excited by full-res silent pictures, because I have a pretty high shutter count on my camera and love to shoot timelapse.
I have a Canon 60D. I tried installing the latest nightly (Nightly.2015Mar29.60D111), and am running into the following behavior.
- I deleted the existing ML folder and copied over the new one.
- I start up the camera, go to modules, load silent.mo
- I turn off the camera. I turn on the camera after waiting a moment. The "sensor cleaning" icon comes up, and then freezes part way through. After a moment, an error message is displayed in the top display with a blinking "Err: 80" message. The sensor cleaning animation is still frozen.
- Restarting the camera with silent pics not loaded works as expected.
Let me know if I can test, or further clarify. Would love to help get this working on my camera!
Thanks so much! Magic Lantern is so exciting and awesome :)
-
You missed to replace Autoexec.bin.
-
My M1 is doing the same back button focus thing with the 22/2 and with other lenses on the adapter. I can tell with my sigma lens that it just starts trying to focus then stops when the silent picture starts. Like less than 50ms probably.
550d works normally, both were downloaded tonight. The M1 is the March29 nightly.
edit: It works sometimes if I tap the screen each time but still not entirely consistent.
-
Thanks a lot for this amazing feature! I'm testing it with my 7d - no issues seen there so far.
I have an Dynamic Perception rig that i would love to use it with. Since the controller do both motor actuations and shutter in perfect sync its preferred not to use ml's intervalometer. But the issue here is the half shutter actuation to take silent pic...
Could you implement a choice somewhere to shutter silent pics on full shutter instead? 8)
-
If you have a wizard with a soldering iron at hand: Drop word "4 way switch" to wizard and your problem is gone. All you need is to switch focus button with shutter release button.
-
Oki, thanks! Hoped for a sw solution ;) But since i consider myself as an hw wizard i think i can solve this 8)
-
Just tried this on my 600d and was amazed how easy it was to get all this working, weathers terrible here today i was hoping to hit the city and bring you a 4k timelapse of york.
two things, why is the shutter limited to 0.8'', i was having wet dreams of full res star trails....
and how do you manage with the cards filling so fast, like 500 shots max in a 16gb card, can we get full res that isnt full res... (yes i know thats a Doh! statement lol)
Thanks for the work on this guys, I had been looking at changing my camera but having this to play with i think i'll be hanging on to it a while longer, which makes life easier, as the OH wont kill me in my sleep for spending more money....
Lez, and thanks again, loving having something new to play with.
(if anyone see my old login details wandering around looking lost, tell them where i am, i had to rejoin to get in and thankyou all!)
-
and how do you manage with the cards filling so fast, like 500 shots max in a 16gb card
Get a 128/256 GByte card
-
Right at the end you can see my test silent-picture. But I'm sure once you expert people start you will get much better results than me.
-
two things, why is the shutter limited to 0.8'', i was having wet dreams of full res star trails....
That's the way it works: http://www.magiclantern.fm/forum/index.php?topic=12523.msg120758#msg120758 (http://www.magiclantern.fm/forum/index.php?topic=12523.msg120758#msg120758)
edit: It works sometimes if I tap the screen each time but still not entirely consistent.
Can you try to change C.FnIV mode say from 1 to 3 or the other way around after you power on and then (after first selecting focus point) try a silent pic?
On my M1 it works like this: https://mega.co.nz/#!oABHHIyb!VNOQugQF-xqmH957FFU4MTHPjZfv2nSugY03P4JFAEU
-
two things, why is the shutter limited to 0.8'', i was having wet dreams of full res star trails....
You are not the only one....
For some reason the 500,550 and 600 crash at shutterspeeds slower than 0,8"
Limitations:
[....]
- 500D, 550D and 600D can't take exposures longer than 0.8 seconds :(
[...]
For Details see post #314ff
http://www.magiclantern.fm/forum/index.php?topic=12523.msg129872#msg129872 (http://www.magiclantern.fm/forum/index.php?topic=12523.msg129872#msg129872)
I tried a day/night - timelapse 2 days ago with an old built from mk1174... well it works, but crashed several times before it run successfully.
And another problem i faced with this outdated build was i couldn't extract all frames from the MLV + .M00 to .M99 files.
(Must have been 130 (MLV with 4 GB) +99 frames but i only got 150)
Right now i'm investigating on how to extract all files.
So in the end i spent more time troubleshooting than taking pictures ;D
For now i guess it's best to accept the limitation.
-
How do you guys process the MLV file? Which programs do you use?
None of the programs I've used can convert it to DNG. They either crash or dont do anything.
-
try MLVMystic, you can find it on the forum. (MLRawViewer also able to do that, but for me it crashed several times at large amount of dngs)
-
tried both and neither of them work for me.. :/
-
and http://www.magiclantern.fm/forum/index.php?topic=13152.0 (http://www.magiclantern.fm/forum/index.php?topic=13152.0) ?
what OS?
-
Sorry, I am on Windows.
I'd like to convert the MLV to C/DNG to then process it in AE.
-
- Describe in detail what you are doing
or
- Take a video/screen capture of said action
- Or let's make a date via TeamViewer.
-
I downloaded mlv2dng, though slow and no settings to apply, I managed to convert the entire MLV file.
But I don't find the resolution overly impressive. Also a weird resolution it is, at 5936x3950, my normal CR2 are 5760x3840. So I end up with a fat black border on the top and left side. Is the resolution normal for FRSP ?
Might be my noobiness with FRSP, but I really don't find the pictures sharp, the pixels seem very crammed..
If you want, I could upload DNG for you to see or just give me plain answers here.
-
How long were your exposures and have you used a tripod?
-
Yes tripod.
2 sec interval. Shutter was right under 2 secs
But is the resolution normal? The black borders and all that?
-
Using MLV files made from FRSP Timelapse works well with latest MLRawViewer (just be sure to change the FPS settings 'Shift + F') to get the look/feel you want.
-
when you say latest MLrawViewer version? Which one is that?
I am using 1.3.3 and it crashes after a few frames of playing and even fewer of conversion.
-
MLRV 1.4.3 (https://bitbucket.org/baldand/mlrawviewer/downloads) <--- download link inside
-
@Licaon_Kter:
My apologies for letting this one slip under me. Yes, you were, in fact, correct regarding ExpSim being DISABLED in the ML menu (thus causing the inconsistent back focus) so once I enabled that ON.
Back focus button seems to work OK.
Thanks for double checking!
*cheers*
-
Yes, you were, in fact, correct regarding ExpSim being DISABLED in the ML menu (thus causing the inconsistent back focus) so once I enabled that ON.
Now, this is a bug then?
-
https://vimeo.com/124125147 (https://vimeo.com/124125147)
-
is it possible to shoot Dual ISO images with FRSP currently? (and in intervalometer mode).
-
Why not test it yourself?
/PS: It works :P
-
Firstly, well done to Alex and everyone else involved in developing/testing FRSP.
I have been using/testing it over the last few days capturing stills in DNG as well as MLV format. I have also taken a number of FRSP timelapse captures in MLV format.
From a capture perspective, all appears to be working correctly. I can review the DNG's and MLV files within the camera.
Unfortunately, after transferring the files to my PC I am not able to process the MLV files. Methods tried are:
mlrawviewer v1.4.3:
Can navigate to the file location but it stops responding and hangs when trying to open the file.
Individual files contain from 4, 16, 20, 110 and 150 frames.
raw2cdng v1.7.1
For MLV files containing 4 frames it completes the extraction process but only extracts 3 of the 4 frames.
For MLV files containing more than 4 frames, the file loads into the batch queue correctly and it can previewed.
however when trying to convert, the application crashes with the following windows error:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: raw2cdng.1.7.1.exe
Problem Signature 02: 1.67.0.0
Problem Signature 03: 551fe5f8
Problem Signature 04: mscorlib
Problem Signature 05: 4.0.30319.34209
Problem Signature 06: 534894cc
Problem Signature 07: 2bd7
Problem Signature 08: 8
Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
OS Version: 6.3.9600.2.0.0.768.101
Locale ID: 3081
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: a10f
Additional Information 4: a10ff7d2bb2516fdc753f9c34fc3b069
Pismo File Mount:
Unable to mount any FRSP MLV file. The application crashes with the following windows error:
Problem signature:
Problem Event Name: APPCRASH
Application Name: pfmhost.exe
Application Version: 1.0.0.175
Application Timestamp: 5517b2bd
Fault Module Name: StackHash_c488
Fault Module Version: 6.3.9600.17668
Fault Module Timestamp: 54c850f5
Exception Code: c0000374
Exception Offset: PCH_C4_FROM_ntdll+0x000000000009133A
OS Version: 6.3.9600.2.0.0.768.101
Locale ID: 3081
Additional Information 1: c488
Additional Information 2: c4887998465a0053994a59c41760d391
Additional Information 3: a2d1
Additional Information 4: a2d1fc25570421d6d613ec3976b986db
Camera: 7D
ML Version: April March 30 nightly build
PC OS: w8.1, 8gb ram, 500gb HD.
I'm at a loss re: what to try next. any suggestions?
Cheers....Otto
-
@Ottoga
I am also pondering the same problem with the MLV files.
On a windows machine I am unable to use any of the newer post processing tools to extract the DNG's and MLRV 1.4.3 can't play more than a few frames before crashing.
I managed to convert a 380 frame timelapse with mlv2dng, though the quality seems fishy too me.. (possible that I captured it wrong)
MLV2DNG: http://magiclantern.fm/forum/index.php?topic=7802.0
Can you give it a try with mlv2dng and tell me either here or by PM how you find the quality and what resolution do you have compared to your normal CR2 Full Res pictures.
-
i am on the road at the moment.
but with mlv_dump you can patch the FPS field and make it look like a normal MLV.
dont know the option, i think it was -F <fps>
-
Thinking about the 'card filling so fast' issue and the suggestion of buy a 128/256, i think the 600d max is 64gb, which is still only about 2k shots (my 16gb card filled in half an hour)
BUT.......
I have a eye-fi card that uploads all the .jpgs to 'the cloud' and never fills..
so can i hack/hex edit the FW so when it creates the filename 000001.dng it instead call its .jpg, that is not changing the format of the file etc, but just tricking the eye-fi card, I know this breaks the standard on many levels but it would be a workaround...
thoughts?
-
Thinking about the 'card filling so fast' issue and the suggestion of buy a 128/256, i think the 600d max is 64gb, which is still only about 2k shots
600D supports SDXC (48 GByte and up).
[...]eye-fi[...]
If you get your eye-fi card working with ML (most just don't) it would be not a big problem to create a script doing some renaming. After LUA scripting module is available, of course.
-
Sorry everyone for the long post, but I thnk that it s important for Windows users to be aware of what does and doesn't work re FRSP.mlv file extractions.
@g3gg0
Thanks for the reply. The actual parameter was -A <fps>. This had no impact. I was however able to extract the images via the -dng parameter.
As general feedback, after more experimenting today, the below table is a summary of my experience trying to extract FRSP images from MLV files (in the windows world).
Extraction
Application Comments
--------------- -----------------------------------------------------------------------------------------------
MLV_Dump Successfully extracts the dng's from all frsp.mlv files attempted. With one exception the
quality of the images extracted was as expected. All the images extracted from the exception
MLV had significant artefacts (green spots) rendering them unusable. The images were
extracted again using mlv2dng and there were no artifacts nor were there any on the control
CR2 image taken. (ref examples below)
MLV2DNG Successfully extracts the dng's from all but 1 of the frsp.mlv files attempted. The following
error/warning message is displayed for each file processed.
"Exception! Header not recognized: 'STYL'".
The one major issue with this aplcation is that the image off-sets are incorrect in the resultant
dng files (ref: example below).
MLRawViewer v1.4.3 Loads the files and allows preview but crashes on export - all frsp.mlv files
raw2cdng v1.7.1 Loads the files and allows preview but crashes on export - all frsp.mlv files
Pismo File Mount Fails to mount ant frsp.mlv files - crashes
WebDAV Doesn't support mlv files. Still need to try using MLV_Dump to convert the files to
standard raw and see if that works.
Below are example images highlighting the MLV_Dump artifacts issue (note that this only occured in one of the frsp.mlv files processed).
The MLV2DNG extracted image also highlights the image off-sets error (Black border across the top and the left hand side of the image)
MLV_Dump extracted image
https://www.dropbox.com/s/gutb5jl56pjf615/MLV_DumpTest_5496_000005.dng?dl=0
MLV2DNG extracted image
https://www.dropbox.com/s/vqq1y8x6ir8c6rn/MLV2DNG_Test_5496_000005.dng?dl=0
Canon CR2 image
https://www.dropbox.com/s/1l8h20b3lkzcr4g/IMG_5496.CR2?dl=0
@Kharak,
This may answer your questions, if not pm me please. Just remember when capturing tha the camera must be in manual mode and liveview (not movie mode} exposure should be 1/15 of a second or slower (Alex please correct me if this is no longer true). A variable ND filter will help with his.
I'm still having fun and games getting my exposures right. A topic for another post after a controlled test that I have in mind.
-
->raw2cdng<- will look into the code today.
edit: help: liveview with halfshutter gives me DNG, how to get MLV with FRSP?
-
@chmee - excellent, thanks.
Happy to test for you.
-
edit: help: liveview with halfshutter gives me DNG, how to get MLV with FRSP?
Also load mlv_rec module and then in the silent module options select MLV instead of DNG
Just remember when capturing tha the camera must be in manual mode and liveview (not movie mode} exposure should be 1/15 of a second or slower (Alex please correct me if this is no longer true).
Using a slow speed yields even slower times, on my M1:
if I set speed = I get FRSP speed
1/125 = 240ms ( 1/4 )
1/4 = 500ms ( 1/2 )
0.5" = 789ms
-
with mlv_dump you should preprocess the MLV file.
e.g. mlv_dump -A 25000 -o out.mlv in.mlv
-
@Kharak,
This may answer your questions, if not pm me please. Just remember when capturing tha the camera must be in manual mode and liveview (not movie mode} exposure should be 1/15 of a second or slower (Alex please correct me if this is no longer true). A variable ND filter will help with his.
Here Alex talks about 1/8000 being a gradient http://www.magiclantern.fm/forum/index.php?topic=12523.msg121962#msg121962
Guess this is a trial and error thing, I better just start slamming some FRSP's.
-
Using a slow speed yields even slower times, on my M1:
if I set speed = I get FRSP speed
1/125 = 240ms ( 1/4 )
1/4 = 500ms ( 1/2 )
0.5" = 789ms
The time displayed is the total runtime of the image capture function (which is always higher than actual capture time).
Most likely, the time displayed should be equal to bottom row exposure time + a model-specific constant. If one creates a table with shutter speeds vs capture times, we might attempt to fit a mathematical model (and find that constant).
-
Alex, are there any way to auto-end the pic review after taking silent pics? I'm working on getting external trigger to work properly, and the only thing stopping me now is that it's only taking pics every second time. The ml intervalometer behavour is perfect, but it's not taking external halfshutter signal in that mode... Maybe there could be a setting setting "external trigger" in that menu?
I have tweaked a cable to make the trigger signal reach halfshutter.
-
Is it possible to create a software for automatic gradient correction in DNGs?
-
@breaker: I'll take care of it.
@itsskin: yes, but there are two difficulties:
- difference between top row and bottom row can be up to around 2...5 stops, depending on camera model (so there will be either clipped or pink highlights)
- we should find some way to measure top/bottom exposure times
- method 1: somebody has to sit down and do the measurement for every single shutter speed (and repeat for every camera model) - really boring and hard to maintain
- method 2: find a way to tell the exposure times from other parameters (partial success here (http://www.magiclantern.fm/forum/index.php?topic=12523.msg121962#msg121962))
-
These particle results looks pretty precise :) How can we all help here?
IMHO this gradient effect heavily limits the use of FRSP. Pretty hard to eliminate it in post, especially when there is a lot of pushing of clarity/exposure/contrast.
-
- method 1: somebody has to sit down and do the measurement for every single shutter speed (and repeat for every camera model) - really boring and hard to maintain
Canon 6D:
SV Time (ms)
15" 16987
13" 13175
10" 12109
8" 8659
6" 6220
5" 5731
4" 4495
3"2 3542
3" 3276
2"5 3031
2" 2431
1"6 1937
1"5 1804
1"3 1681
1" 1372
0"8 1131
0"7 1065
0"6 1004
0"5 849
0"4 739
0"3 697
1/4 592
1/5 513
1/6 497
1/8 445
1/10 408
1/13 399
1/15 382
1/20 363
1/25 359
1/30 350
1/40 343
1/45 341
1/50 339
1/60 334
1/80 331
1/90 330
1/100 329
1/125 326
1/160 325
1/180 324
1/200 324
1/250 322
1/320 322
1/350 321
1/400 321
1/500 317
317ms being the smallest capture time. The boring bit was formatting it for this post. :P
-
Tv Tv t2i ms dif m1 ms diff
sec ms actual actual
1/4000 0.3 281 280.8 238 237.8
1/3200 0.3 281 280.7 238 237.7
1/2500 0.4 282 281.6 238 237.6
1/2000 0.5 282 281.5 238 237.5
1/1600 0.6 281 280.4 238 237.4
1/1250 0.8 281 280.2 238 237.2
1/1000 1.0 281 280.0 238 237.0
1/800 1.3 281 279.8 238 236.8
1/640 1.6 281 279.4 238 236.4
1/500 2.0 281 279.0 238 236.0
1/400 2.5 282 279.5 238 235.5
1/320 3.1 283 279.9 240 236.9
1/250 4.0 284 280.0 240 236.0
1/200 5.0 286 281.0 241 236.0
1/160 6.3 287 280.8 243 236.8
1/125 8.0 288 280.0 244 236.0
1/100 10.0 291 281.0 248 238.0
1/80 12.5 292 279.5 250 237.5
1/60 16.7 297 280.3 252 235.3
1/50 20.0 301 281.0 257 237.0
1/40 25.0 304 279.0 262 237.0
1/30 33.3 313 279.7 267 233.7
1/25 40.0 322 282.0 278 238.0
1/20 50.0 330 280.0 285 235.0
1/15 66.7 344 277.3 300 233.3
1/13 76.9 364 287.1 317 240.1
1/10 100.0 380 280.0 333 233.0
1/8 125.0 410 285.0 362 237.0
1/6 166.7 450 283.3 400 233.3
1/5 200.0 481 281.0 431 231.0
1/4 250.0 560 310.0 510 260.0
300 637 337.0 584 284.0
400 701 301.0 655 255.0
500 820 320.0 765 265.0
600 974 374.0 920 320.0
800 1101 301.0 1048 248.0
1000 1290 290.0
1300 1599 299.0
1600 1853 253.0
2000 2329 329.0
2500 2947 447.0
3200 3457 257.0
4000 4408 408.0
5000 5643 643.0
6000 6664 664.0
8000 8569 569.0
10000 11038 1038.0
13000 13079 79.0
15000 16887 1887.0
I did a t2i and an M1. What's weird it I did 13" on the M1 a few times and it always gives me a really short difference. I'm not sure if that means something about it lines up better so it goes faster or if it's not really 13 seconds...
-
Interesting, the differences become a bit strange at long exposure times. A while ago, I've noticed that long exposures are made in smaller increments (http://www.magiclantern.fm/forum/index.php?topic=1915) (that is, the sensor is reconfigured a few times during a long exposure). I should probably measure the rolling shutter effect at long exposures as well.
Look for this string in Canon firmware: "VSizeSetting Time:%d Acc:%d loop:%d" / "VSize T:%d A:%d l:%d". This routine decides how many increments are used to take an exposure. Its input value is time in ms, taken from this table (http://www.magiclantern.fm/forum/index.php?topic=1915.msg23797#msg23797).
I've tried to run that function for different input values, and here's the output for EOS-M (in 1/3 EV steps):
Tv Time Acc out[1] out[2] loop
1/4000 15 345 0 3532 1
1/3200 15 345 0 3532 1
1/2500 15 345 0 3532 1
1/2000 15 345 0 3532 1
1/1600 15 345 0 3532 1
1/1250 15 345 0 3532 1
1/1000 15 345 0 3532 1
1/800 15 345 0 3532 1
1/640 15 345 0 3532 1
1/500 15 345 0 3532 1
1/400 16 368 0 3532 1
1/320 17 391 0 3532 1
1/250 17 391 0 3532 1
1/200 19 437 0 3532 1
1/160 20 460 0 3532 1
1/125 21 483 0 3532 1
1/100 24 552 0 3532 1
1/80 26 599 0 3532 1
1/60 29 668 0 3532 1
1/50 34 783 0 3532 1
1/40 38 875 0 3532 1
1/30 45 1036 0 3532 1
1/25 54 1244 0 3532 1
1/20 62 1428 0 3532 1
1/15 77 1774 0 3532 1
1/13 95 2188 0 3532 1
1/10 111 2557 0 3532 1
1/8 140 3225 0 3532 1
1/6 177 4078 0 3532 1
1/5 208 4792 0 3532 1
1/4 266 1589 5004 3532 2
0.3" 341 3317 5004 3532 2
0.4" 413 4976 5004 3532 2
0.5" 523 2511 5004 3532 3
0.6" 678 1082 5004 3532 4
0.8" 805 4009 5004 3532 4
1" 1043 4493 5004 3532 5
1.3" 1352 1612 5004 3532 7
1.6" 1607 2488 5004 3532 8
2" 2083 3456 5004 3532 10
2.5" 2700 2672 5004 3532 13
3.2" 3210 4423 5004 3532 15
4" 4162 1359 5004 3532 20
5" 5396 4792 5004 3532 25
6" 6417 3317 5004 3532 30
8" 8320 2165 5004 3532 39
10" 10789 4055 5004 3532 50
12.5" 12830 1082 5004 3532 60
16" 16637 3801 5004 3532 77
20" 21575 2580 5004 3532 100
25" 25656 1612 5004 3532 119
32" 32323 5230 5004 3532 149
notes:
- Tv is shutter speed string as displayed by ML
- Time is from Canon's shutter timing table (in ms), and it's also printed in the string below
- Acc and loop are from this string: "VSizeSetting Time:%d Acc:%d loop:%d"
- out[1] and out[2] are also output values from VSizeSetting, just not displayed in debug messages
-
First let me thank everybody involved in the FRSP development. This sounds awesome for timelapse :)
Sadly, today's nightly build doesn't seem to work on my 50D. Regular photo, lo-res silent pictures and video mode work as usual, but FRSP just flashes the screen (no message, just light gray) and the blue LED and then turns both off. The camera is still running at this point and everything goes back to normal after turning liveview off and on again or just going to Canon menu and then pressing half shutter again. The top display even shows "busy" for the set exposure time, but nothing gets written to the memory card, even after waiting 5 minutes without touching the camera. I did check the card with the card reader, not in camera.
Any guesses what I could have done wrong?
I can supply more information or a video of this behaviour, if it helps.
Settings: M mode, ISO 100, f/4, different shutter speeds from 10s to 1/50s, daylight WB, video inactive, expsim and exp-override active. Fresh installation from Nightly.2015Apr06.50D109 onto formatted card with no modules except silent.mo and mlv_rec.mo.
-
Is there currently a solution for sending a trigger signal via PC sync port on camera (or attached to hot shoe) when the silent picture is 'taken'? Some way to trigger external intervalometer/motor setup would be great, but uncertain how feasible this idea is as a search doesn't yield much success on any idea similar. Thanks.
-
@halbmoki: did it ever work? A video of the camera screen would help.
@Pyriphlegethon: see this (http://www.magiclantern.fm/forum/index.php?topic=11913), this (http://www.magiclantern.fm/forum/index.php?topic=9601), this (http://www.magiclantern.fm/forum/index.php?topic=8912) and this (http://www.magiclantern.fm/forum/index.php?topic=11732).
-
@a1ex: No, it never worked. This is the first version I'm trying, since I'm not very good with coding and compiling. I'm just assuming it's my mistake, because someone else reported success with a 50D earlier in the thread.
Here's a video of what happens when I try to take a full-res silent picture:
The first 2 half-shutter presses are regular silent pics (always worked and still do), then one with FRSP/DNG and one with FRSP/MLV. Both are repeatable and the screen stays black for more than 10 minutes every time, unless I press some other button than half-shutter.
Little correction from my last post: There is a message "Hold on..." on the screen for a moment before it turns black. Didn't notice that before, because it's really fast.
The camera also crashed (frozen inside ML menu, had to remove battery) once while turning video off when FRSP was already on. I couldn't reproduce this after a few tries, though.
-
@halbmoki: I think I found the problem: set image review in Canon menu to a nonzero value. Without it, some cameras can't trigger the QuickReview mode for previewing the image.
@breaker: what kind of trigger signal do you use? If I redefine half-shutter to trigger another picture, there will be no easy way to return to LiveView. If your trigger signal is a little longer, I could let short presses to return to LiveView, and long presses to trigger another picture (without adding yamlmo).
-
@alex: I'm using an Dynamic Perception MX3. I could not find anything in the documentation, and all i have in hand now is a slow multimeter. Anyway, i estimate the trigger signal to be somewhere between 500 and 1000 ms. I might measure it with oscilloscope tomorrow.
Another thing - i can also activate bulb mode on the trigger, so that will let me choose whatever trigger lenght i would like :)
Edit: fully adjustable, 120 ms default.
-
Thank you, a1ex! That did it. The image takes about 3 seconds to save, but it does work and the results look great. Now I only need a bunch of memory and a completely new editing maching that doesn't melt at the thought of 4K timelapse ;)
-
@ alex
oh well, this should also be the problem which I PMed you. will test that later.
but the image review was intended to be 0 for better battery runtime (timelapse), or isn't that the case anyway? Man, I'm still waiting for a possibility to deactivate that shitty screen. ^^ But I know, this probably won't ever be solved.
-
I was able to re-trigger an exposure by a second half-shutter press, but with some restrictions:
- with image review turned off in Canon menu, works nice, but will not trigger ETTR (same behavior with regular pictures, and you get a warning in the menu)
- with image review enabled, half-shutter will take me back to LiveView and I can't stop it, so a long press will also enable LiveView for a split-second (it will eat up a bit of battery juice)
https://bitbucket.org/hudson/magic-lantern/commits/41267aa1a330
Before including it in the nightlies, here's a compiled module for you to try it:
silent.mo (http://a1ex.magiclantern.fm/bleeding-edge/silent.mo)
-
Tried it with the actual nightly and image review 0. Works fine so far, also intervalometer seems to work.
But why do I have to press half shutter again after a FRSP to get back to liveview?
-
Thanks Alex! Works fine. This also brings a "Take pics like crazy" if you keep holding halfshutter (only in MLV mode EDIT: and CanonReview time is 0) :)
With the MX3 controller i can adjust shutter signal to 0 ms, and when I adjusted the focus signal to 1000ms it worked with original cable!
The only issue is that it might be strange to some people when the screen is black without any information after review is timed out.
But I have exactly what I need 8)
-
when the screen is black without any information after review is timed out.
Maybe we can draw a simple version of the Canon display you see outside of LV with exposure parameters etc. on it.
Then we just need a rangefinder attachment for composing the shot and LV can just stay off :P
-
Hello,
There're surprisingly few tutorials on silent full-rez timelapses of sunsets and all searches bring here. So I'll dare to ask in this branch.
I am using the latest nightly build (maybe it's an overkill and I need simply the latest ML, pls, tell me) on my T3i (600D) and willing to learn only one thing - capture a silent full-rez timelapse of sunrise/sunset. The problem: I set up ETTR, intervalometer, silent mode, M-mode, but regardless of how I reinforce the ISO, it keeps jumping to the highest 3200 once the longest allowed shutter speed is reached. So if I start at 800 1/25th, it'll eventually roll over to 3200 3". Is it expected behavior? Or should I set the max shutter speed to 10sec? Other ideas?
I see all these wonderful stary nightlapses, but I also want to blend in some of the sunset.
-
TV ML Canon ms
-4.0 16" 15" 16887
-3.8 16" 15" 16887
-3.7 16" 13" 13080
-3.6 12.5" 13" 13080
-3.5 10" 10" 12014
-3.3 10" 10" 11038
-3.2 10" 8" 8569
-3.1 10" 8" 8569
-3.0 8" 8" 8569
-2.8 8" 8" 8569
-2.7 8" 8" 6665
-2.6 6" 6" 6665
-2.5 6" 5" 6132
-2.3 5" 5" 5644
-2.2 5" 4" 4410
-2.1 5" 4" 4410
-2.0 4" 4" 4410
-1.8 4" 4" 4410
-1.7 4" 3"2 3458
-1.6 3.2" 3"2 3458
-1.5 3" 2"5 3191
-1.3 2.5" 2"5 2948
-1.2 2.5" 2" 2331
-1.1 2.5" 2" 2331
-1.0 2" 2" 2331
-0.8 2" 2" 2331
-0.7 2" 1"6 1854
-0.6 1.6" 1"6 1854
-0.5 1.5" 1"3 1721
-0.3 1.3" 1"3 1599
-0.2 1.3" 1" 1290
-0.1 1.3" 1" 1290
0.0 1" 1" 1290
0.1 1" 1" 1290
0.2 1" 0"8 1049
0.3 0.8" 0"8 1049
0.5 0.7" 0"6 983
0.6 0.6" 0"6 922
0.7 0.6" 0"5 767
0.8 0.6" 0"5 767
1.0 0.5" 0"5 767
1.1 0.5" 0"5 767
1.2 0.5" 0"4 656
1.3 0.4" 0"4 656
1.5 0.3" 0"3 614
1.6 0.3" 0"3 584
1.7 1/3 4 510
1.8 1/3 4 510
2.0 1/4 4 510
2.1 1/4 4 510
2.2 1/4 5 431
2.3 1/5 5 431
2.5 1/6 6 416
2.6 1/6 6 401
2.7 1/6 8 363
2.8 1/6 8 363
3.0 1/8 8 363
3.1 1/8 8 363
3.2 1/8 10 334
3.3 1/10 10 334
3.5 1/10 13 327
3.6 1/13 13 319
3.7 1/13 15 301
3.8 1/13 15 301
4.0 1/15 15 301
4.1 1/15 15 301
4.2 1/15 20 285
4.3 1/20 20 285
4.5 1/20 25 281
4.6 1/25 25 278
4.7 1/27 30 269
4.8 1/28 30 269
5.0 1/30 30 269
5.1 1/35 30 269
5.2 1/38 40 261
5.3 1/40 40 261
5.5 1/45 50 261
5.6 1/50 50 258
5.7 1/55 60 253
5.8 1/58 60 253
6.0 1/60 60 253
6.1 1/70 60 253
6.2 1/80 80 251
6.3 1/80 80 251
6.5 1/90 100 251
6.6 1/100 100 251
6.7 1/110 125 251
6.8 1/120 125 251
7.0 1/125 125 251
7.1 1/140 125 251
7.2 1/150 160 251
7.3 1/160 160 251
7.5 1/180 200 251
7.6 1/200 200 251
7.7 1/215 250 251
7.8 1/235 250 251
8.0 1/250 250 251
8.1 1/280 250 251
8.2 1/300 320 251
8.3 1/320 320 251
8.5 1/350 400 251
8.6 1/400 400 251
8.7 1/430 500 251
8.8 1/470 500 251
9.0 1/500 500 251
9.1 1/560 500 251
9.2 1/600 640 251
9.3 1/640 640 251
9.5 1/750 800 251
9.6 1/800 800 251
9.7 1/850 1000 251
9.8 1/900 1000 251
10.0 1/1000 1000 251
10.1 1/1100 1000 251
10.2 1/1200 1250 251
10.3 1/1250 1250 251
10.5 1/1500 1600 251
10.6 1/1600 1600 251
10.7 1/1700 2000 251
10.8 1/1900 2000 251
11.0 1/2000 2000 251
11.1 1/2300 2000 251
11.2 1/2400 2500 251
11.3 1/2500 2500 251
11.5 1/3000 3200 251
11.6 1/3200 3200 251
11.7 1/3500 4000 251
11.8 1/3800 4000 251
12.0 1/4000 4000 251
12.1 1/4500 4000 251
12.2 1/4800 4000 251
12.3 1/5000 4000 251
12.5 1/6000 4000 251
12.6 1/6400 4000 251
12.7 1/7200 4000 251
12.8 1/7800 4000 251
13.0 1/8000 4000 251
For 700D if this info is still needed.
-
ISO, it keeps jumping to the highest 3200 once the longest allowed shutter speed is reached. So if I start at 800 1/25th, it'll eventually roll over to 3200 3". Is it expected behavior? Or should I set the max shutter speed to 10sec? Other ideas?
I see all these wonderful stary nightlapses, but I also want to blend in some of the sunset.
But it's not overexposed is it? You got to give it longer exposure time to bring in enough light at a dark night. Normally 15 to 30 seconds (high will bring startrails). By now Silent Fullres is restricted to 15 seconds, so that is all you got now. Aperture somewhere around 8-10, but you might have to lower it a bit because of the 15 seconds restrictor.
-
Hello,
There're surprisingly few tutorials on silent full-rez timelapses of sunsets and all searches bring here. So I'll dare to ask in this branch.
I am using the latest nightly build (maybe it's an overkill and I need simply the latest ML, pls, tell me) on my T3i (600D) and willing to learn only one thing - capture a silent full-rez timelapse of sunrise/sunset. The problem: I set up ETTR, intervalometer, silent mode, M-mode, but regardless of how I reinforce the ISO, it keeps jumping to the highest 3200 once the longest allowed shutter speed is reached. So if I start at 800 1/25th, it'll eventually roll over to 3200 3". Is it expected behavior? Or should I set the max shutter speed to 10sec? Other ideas?
I see all these wonderful stary nightlapses, but I also want to blend in some of the sunset.
A few pages back and you will see posts that 600D has 0.8 sec Shutter limit, posts also include explanation links. I was also dreaming about starry timelapses with my 600D, but with current nightlies it is not possible (correct me if new versions allow more than 0.8s) In the old stable release there is no FRSP. Hope the community can figure it out.
-
breaker, Franz,
Thank you for the input. Yes, the pictures are perfect. But I'm not sure if we're talking about the same moment of shooting. I'm trying to get a feeling of how the process is going while the sun is hitting the horizon and the amount of light is gradually goes down. Let me elaborate:
Probably I was more wondering about re-inforcing the ISO. Yes, I read about the longest shutter speed, I understand that I may not get a night-lapse after all, but... I thought if I set ISO to 800, it wouldn't go up without me specifically telling it to. I thought silent timelapse is functioning like a AV mode, to some extend. I set up ISO, do manual focus, maybe even use some vintage lens and set up apperture manually... and all it'll do - adjust digital shutter. Once the slowest shutter speed is hit, it stops. It seems now that as soon as the slowest shutter speed is reached, it jumps onto next ISO (from 800 to 1600, then from 1600 to 3200), shoots, reaches 3200 with slowest shutter speed and only then stops. Is it so? Has anyone played with sunsets/sunrises much? Maybe all I need is elaborate tutorial on setup cause I'm missing something.
What if I wanted to shoot with ISO 1600, for example, and shoot up until the shutter speed is 0.8?
Thanks
p.s. really want to master the whole process in the next 4-5 days before vacation.
-
@g3gg0
with mlv_dump you should preprocess the MLV file.
e.g. mlv_dump -A 25000 -o out.mlv in.mlv
Tried this with a number of frsp.mlv files and verified the frame rate change via raw2cdng. MLRawViwer is still is still fussy when opening the output files and crashes 100% of the time when attempting to export.
-
Probably I was more wondering about re-inforcing the ISO. Yes, I read about the longest shutter speed, I understand that I may not get a night-lapse after all, but... I thought if I set ISO to 800, it wouldn't go up without me specifically telling it to.
You better read this (http://wiki.magiclantern.fm/ettr), and other ETTR related threads. Shutter and ISO is what ETTR manipulate. If you don't want ISO to change you'll better stay with AV ;) I also recommend you to do the testing with normal noisy pics, then you don't get restricted by the Silent's limitations.
-
Why wouldn't you want the ISO to increase? That's the whole point of ETTR.
-
@Ottoga:
Which version of MLRV are you using that's crashing with MLV's produced by FRSP?
-
@DeafEyeJedi
MLRawViewer 1.4.3
-
Try deleting all existing .IDX files and retry?
Did you try changing FPS Settings? (Shift + F) see if that helps?
If not, send me a copy of your MLV's.
-
5d3 times:
SV Time (ms)
15" 16874
13" 13065
10" 11023
8" 8553
6" 6649
5" 5628
4" 4393
3"2 3441
2"5 2931
2" 2313
1"6 1837
1"3 1582
1" 1272
0"8 1034
0"6 906
0"5 751
0"4 641
0"3 569
1/4 493
1/5 416
1/6 384
1/8 347
1/10 319
1/13 302
1/15 284
1/20 269
1/25 261
1/30 251
1/40 245
1/50 241
1/60 236
1/80 234
1/100 232
1/125 228
1/160 227
1/200 226
1/250 224
1/320 224
1/400 223
1/500 220
-
@DeafEyeJdei
Try deleting all existing .IDX files and retry? Done before each attempt to process - They are never fully built as MLRV crashes almost immediately
Did you try changing FPS Settings? (Shift + F) see if that helps? - I have changed the FPS setting using MLV_Dump to no effect i.e: MLRV still crashes, not able to do it in MLRV.
If not, send me a copy of your MLV's. - The link is to an original file as captured with FRSP.
https://www.dropbox.com/s/6z2j2irdppappzv/54830000.MLV?dl=0 Be aware, 700mb file
I have also over the last couple of days built a Linux VM in VBOX and have installed MLRV into that. It seems to have installed ok but its not behaving as expected either. e.g.: Can't run the GUI, only via the command line and I'm having a bunch of OpenGL issues with this build. I don't know if it is a VBOX or a Linux build issue. Way out my comfort zone with this.
I appreciate your assistance with this.
Cheers... Otto
-
I do focus stacking extreme macros and have been waiting for this feature to make it to the nightly build. Thank you A1ex and all other contributors!
I have made a few tests for focus stacking and it looks very promising. Found a few minor issues though:
1: The white balance is different from what I get when doing a normal exposure with the same settings.
2: Also the exposure is 1-2 steps lighter with silent pictures.
3: Exposure settings are reported as 1 s at f/1.0 in the EXIF information.
The exposure can be compensated for and the white balance can be fixed in post processing, so it is not a major issue. But I wonder if it is something I am doing wrong.
/Pontop
-
Yeah, DNG EXIF would be great to have for lens correction and other stuff :)
-
This needs fixing for EXIF (https://bitbucket.org/hudson/magic-lantern/pull-request/524/silent-pics-enable-exif-info-in-dng/diff).
-
I have a separate PR that revamps the entire DNG writing code. For now, if you want metadata, use MLV format. You'll get EXIF metadata when you convert the MLV to DNG, assuming your converter handles it properly (most of them should).
-
I shot a test timelapse today and got some strange artifacts. Don't have direct comparison with normal CR2, but I'm pretty sure I never saw them before. It's iso 100 @ 5 sec exposure.
(https://dl.dropboxusercontent.com/u/17452116/Screen%20Shot%202015-04-14%20at%2023.26.11.jpg)
Though can be problematic shot. Others are ok. Like this one:
(https://dl.dropboxusercontent.com/u/17452116/Screen%20Shot%202015-04-14%20at%2023.33.33.jpg)
-
I too am having crashes with MLRV 1.4.3 . I am on Mavericks 10.9.4 Mac Mini .
I start the MLRV program navigate to my file and it starts up black, then if i scrub it crashes immediately, if i don't and just add it to the render queue for mov and then wait for the output the file is black.
With MLVFS i can safely make DNGs out of them but I do love MLRV. with its Luts
Hoping that this can get fixed.
-
@Ottoga:
Thanks for the MLV file. Ran MLRV 1.4.3 in Yosemite and exported both .mov & .dng's fine.
(https://farm9.staticflickr.com/8799/16967420280_eae1f061cd_n.jpg) (https://flic.kr/p/rRmsUY)
(https://farm8.staticflickr.com/7723/16534811033_9c0fe6b12a_n.jpg) (https://flic.kr/p/rc8efR)
(https://farm9.staticflickr.com/8761/16967189808_042d1d82a9_n.jpg) (https://flic.kr/p/rRkhpj)
https://vimeo.com/125021447 (https://vimeo.com/125021447)
Not sure what could be causing the crashes on your end?
-
@DeafEyeJedi
Thanks for testing the clip out for me. It looks like the issue is in my PC although I can't think what at the moment (W8.1 professional, 6GB ram, Intel i5 processor, Intel HD graphics).
Are there any dependencies that I need to install? i.e. my old notebook had Python and Pearl installed?
Cheers... Otto
-
I shot a test timelapse today and got some strange artifacts. Don't have direct comparison with normal CR2, but I'm pretty sure I never saw them before. It's iso 100 @ 5 sec exposure.
Underexposed. Increase exposure and/or ISO.
-
Greetings, I am attempting FRSP with intervalometer on my 5D2 and I am only getting one picture with an ugly black bar across the pic with "intervalometer wating for first pic" across it. Please help, I am using the latest nightly, I have tried with IV set to take photo on half shutter and on first pic, I have the IV set to like ten pics, the shutter is at like 1/15 of a sec, I have tried with canon menu review time like 2 sec and off, expo override on and off, MLV and DNG... I imagine there is some small thing I am missing, not a noob to ML, but to FRSP I guess I am. Could someone who is successfully setting up FRSP with intervalometer please let me know what I might be missing? Thanks to all the devs!!! a1ex g33o mk1174 and everyone!!
-
Replied to the commit (https://bitbucket.org/hudson/magic-lantern/commits/41267aa1a3302100233fac32053a086138567372#comment-1832542) but I'll add it here too:
On my M1 I now get:
* image on screen for X sec followed by black screen that waits for a button press with Canon->"Image review"->"X sec" and no matter what ML->"Image Review Settings"
* image on screen that waits for a button press with Canon->"Image review"->"Hold" and no matter what ML->"Image Review Settings"
* black screen that waits for a button press with Canon->"Image review"->OFF and no matter what ML->"Image Review Settings"
What settings should I set and how to get NO image review at all BUT no black screen waiting for a button press either?
-
Correct - this behavior minimizes the power draw for an external-triggered timelapse.
To get no image review at all, and return to LiveView right away... I don't know, press half-shutter twice?
-
Underexposed. Increase exposure and/or ISO.
Sure, and blow all highlights :D Blame ETTR for exposure :D
-
Yeah ticky.
Trying to record a bit with the intervalometer, to answer @JoshuOne, got the timer running, 10s, FRSP, MLV, the screen was always off which is nice, but after 9 frames or so:
ML ASSERT:
lv
at ../../src/zebra.c:4202 (idle_display_dim), task cls_task
lv:0 mode:3
Magic Lantern version : Nightly.2015Apr15.EOSM202
Mercurial changeset : 693ec08e528e (unified) tip
Built on 2015-04-14 22:08:34 UTC by jenkins@magiclantern.fm.
Free Memory : 134K + 3233K
and the screen looked like this (had to pull battery for it to recover):
(https://i.imgur.com/KhbKPFO.png)
Also, I initially thought that it might be a problem with my builds, as the official nightlies did not exhibit it until now, but I get asserts like this all the time:
ML ASSERT:
lv
at ../../src/raw.c:1690 (raw_lv_request), task ettr_task
lv:0 mode:3
Magic Lantern version : Nightly.2015Apr15.EOSM202
Mercurial changeset : 693ec08e528e (unified) tip
Built on 2015-04-14 22:08:34 UTC by jenkins@magiclantern.fm.
Free Memory : 140K + 3095Kand
ML ASSERT:
lv
at ../../src/raw.c:1690 (raw_lv_request), task livev_hiprio_task
lv:0 mode:3
Magic Lantern version : Nightly.2015Apr15.EOSM202
Mercurial changeset : 693ec08e528e (unified) tip
Built on 2015-04-14 22:08:34 UTC by jenkins@magiclantern.fm.
Free Memory : 158K + 3135K
What do they mean?
Sure, and blow all highlights :D Blame ETTR for exposure :D
Yeah ETTR and FRSP don't yet cooperate.
-
Sure, and blow all highlights :D Blame ETTR for exposure :D
No, always blame the user :P
What highlights were you trying to protect? Some stars?
-
What do they mean?
It means that ETTR tried to request LV raw data while LV wasn't actually running.
-
I was testing FRSP so sometimes it ended up in a black screen hence ETTR/zebras could not get its needed data, makes sense.
For now I will set Zebras->RAW Zebras to OFF so that maybe that won't trigger again on intervalometer use, when the camera does not get a chance to display the image at all anyway.
Another thing, are asserts a sign of things being unstable (like the error that I got later) or just plain warnings that can be ignored?
-
It just depends on the actual assert itself. These types of asserts (asserts from ML code), indicate that something ML considers invalid happened. Asserts in general are a sort of a 'self-test' of the code. If something "shouldn't" happen, then we explicitly check and make sure that it doesn't, and if it does, throw an error, so we'll know about it and fix it (this is good programming practice). An assert could be for something simple with no real possibility of causing instability, or it could be for something quite dangerous, the assert itself could also be the problem (an invalid or incorrectly coded assert).
There are also asserts that come from canon code, these are a different sort of beast, since we didn't make them ourselves, don't have the original code and we can't easily tell what the assert is for and why (at least not without a lot of reverse engineering and analyzing assembly code).
-
Hi!
Way back here,
http://www.magiclantern.fm/forum/index.php?topic=12523.msg121962#msg121962
I understood that at capture time, FPS timer A controlled the time allotted per row. Per that interpretation, some later posts talked about reducing the timer value for faster exposures.
Then here,
http://www.magiclantern.fm/forum/index.php?topic=12523.msg143510#msg143510
I got thrown about the comment that the sensor wasn't being read in rolling shutter mode.
I'm really interested to know if timer A can be increased for slit-scan full-resolution images. Because that would be awesome.
I'm wondering if:- A - It's totally possible already, and someone will just put in the menu option for adjusting timer A if I ask nicely, or
- B - This finding opens the door to full-resolution slit-scan but it will require some engineering, in which case I'll roll up my sleeves and contribute if/when I have something, or
- C - I've got confused or lost at some point and there's no direct approach to this idea yet
Thx :-)
-
I didn't really experiment much with this timer, but I couldn't decrease it too much. You should however be able to increase it quite a bit, which will give a stronger gradient.
I don't know yet if the timer can be changed during an exposure - if so, you might be able to tweak the shape of the gradient (e.g. try to make it linear in EV space, rather than exposure time).
Once one figures out how to drive the sensor in fullres rolling shutter mode, slowing it down for slit-scan capture should be pretty easy.
On 500D, Greg was able to capture a full-width LiveView image (in rolling shutter mode) here (http://www.magiclantern.fm/forum/index.php?topic=10111.msg123909#msg123909) with the help of FPS override.
-
I must confess, I do not understand. Is tehre something special I must do in order to use intervalometer with Full Res Silent Pics on the 5Dmkii? Any help is much appreciated. I am in SF this weekend for a journalism conference and would love to be able to get some crowded Market street timelapses without burning out my tired shutter :) As it is now, I get one photo with a black bar across it that says "intervalometer waiting for first pic..."
Thanks everyone.
-
Use the 'leave menu' trigger.
It appears that the 'take a pic' trigger only triggers off of an actual photo being taken not a silent picture (I suppose that should be fixed). The 'half shutter' trigger doesn't work so well either if you try and start from LV, as it conflicts with the silent picture itself (which also tries to trigger off of half shutter). When you press half shutter, it's intercepted by silent picture, and you simply get a silent picture and the intervalometer isn't started (it didn't get that you pressed half shutter and displays that message that you see, b/c it thinks you still haven't pressed half shutter). Half shutter trigger seemed to work fine though, if you started outside LV.
So, your best bet is to simply use the 'leave menu' option. It works just fine in any scenario.
-
Thanks so much, dmilligan! That was one thing that I hadn't tried and the one thing that worked. I am not sure how well, but a simple 10-shot test seemed to do fine. THANKS!! :)
-
I can confirm that the "leave menu" works fine. Also, Even though your camera will likely be on a tripod, I would also set a start delay of a few seconds. Just a bit of insurance to ensure that there is no camera shake due to a heavy handed button presses when exiting the menus.
-
Trying to record a bit with the intervalometer, to answer @JoshuOne, got the timer running, 10s, FRSP, MLV, the screen was always off which is nice, but after 9 frames or so:
ML ASSERT:
lv
at ../../src/zebra.c:4202 (idle_display_dim), task cls_task
lv:0 mode:3
Figured it ( by setting up ML multiple times ) how it was trigger ( BUT it's obvious now since it's written RIGHT THERE in the assert daamit :P ) and reported it: https://bitbucket.org/hudson/magic-lantern/issue/2262/dim-display-triggers-assert-in-zebras-when (https://bitbucket.org/hudson/magic-lantern/issue/2262/dim-display-triggers-assert-in-zebras-when)
-
Does anyone know, perhaps A1ex ???, if the sensor can be read out line by line, but with a pause somewhere.
Is it possible to create a real gradient filter by reading out the highest lines quick, then pause, and resume with the rest of the image lines ?
-
I'm using a 7D.
I tried old versions and latest released FRSP module.
I tried fresh magic lantern install.
I have activated expo sim & expo override.
In M mode.
I have 3 lens:
50mm 1.8
55 250 STM
10 18 STM
With the 50mm, setting the manual aperture in live view works great.
I can see direct result on screen.
The FRSP is exposed as is the simulation.
With my two STM lens, aperture change leads to.. Absolutely no change in exposure. I can see exposure result for 1/5sec when I halfpress the shutter and when "exposim" from canon menu is darkened.
But when the picture is taken with FRSP : exposure correspond to what I have on screen, so it's overexposed.
So I can't use FRSP in daylight because it's always over exposed.
Is this normal? Why is it behaving differently with my 50 and my STM lens?
I can make a video if you wish so.
-
It is normal because for FRSP the fastest shutter is avg @ 1/15th of a sec for the most part.
So either close down the Iris or get a ND for daytime use.
-
I know that I can't get a fast shutter speed.
I wasn't talking about the shutter speed.
You advise me to close the iris.
The iris as you say is also called the aperture.
And I just tried to explained that I can't change the aperture with my two STM lens while it works perfectly fine with my canon 50mm 1.8 with the exact same settings, just by changing the lens.
50mm: touch the aperture settings: exposure change on screen: exposure of the silent pic change.
My two new stm lens: touch the aperture settings: change on camera: no change on screen: no change on exposure.
Strange.
I tried with MF/AF and with IS/no IS just to see...
Can't get why it is stucked only with my two stm lens.
-
Sounds like expo override may not work with STM lenses. Any other STM lens users can confirm?
Can you manage to take a picture with the DOF preview button pressed?
-
I have a 18-55mm IS STM, a 55-250mm IS STM and a 24mm STM. Expo override works Ok on the three lenses, no problem to adjust aperture during FRSP on a 500D.
-
I can confirm that expo-override does not work on 5D3 + EF 40/2.8 STM in the latest nightly. I had the same issue yesterday. The aperture does not close more than about f/4.0 or f/5.6.
It works fine with other lenses.
-
I tried using FRSP with A-ETTR in a day-to-night timelapse two days ago with the actual nightly. For that purpose i used the .mlv-format, set A-ETTR to a max shutter-time of 10s and used a 12s interval. The result was that A-ETTR worked fine but i only got a picture every 24s and in the metadata the shutter time was always 1s but i can see from the exposure of the picture that the shutter time changes very often. So A-ETTR worked correct but the metadata was written wrong. Aperture and ISO worked fine.
Do you have any ideas about the shutter time? Is there something wrong in the code or a user-error?
-
Sounds like expo override may not work with STM lenses. Any other STM lens users can confirm?
Confirmed on my EF-M 22mm 1:2 STM too.
Now that I think of it the other thing (http://www.magiclantern.fm/forum/index.php?topic=5768.msg145480#msg145480) shows it exactly as described.
Can you manage to take a picture with the DOF preview button pressed?
Umm, having C.FnIV (6) setting Trash for "DoF preview", a single-press will trigger a quick iris closing up to my set up aperture AND after the iris moves back to max-aperture it will trigger a FRSP too, weird !? Also while *-press or half-shutter press exit the preview, pressing Trash again does not.
Hold-press Trash most of the time will close the iris properly but the screen will go from "Hold on..." to black screen with "Raw error" until you depress Trash and after it will stay as a black screen that waits for *-press or half-press, no FRSP will be taken on hold.
Actually as far as I can see it will always make a FRSP at max aperture no matter what I have selected and whether ExpOverride is used or not.
-
During my test yesterday on 500D (nightly 2015 March 29th) expo override worked fine for my STM lenses, as I already posted.
But now I've tested it also on my recently purchased EOS M. And there is really a problem with STM lenses.
Lenses I have tested (EOS-M nightly 2015 April 14th)
- EF-M 18-55mm STM Expo override does not work, exposure in FRSP does not change at all when changing aperture.
- EF-M 11-22mm STM Same behaviour, expo override does not work
- EF-M 22mm STM Exposure in FRSP does not change when going from F2.0 to F11, but there is some degree of exposure reduction at F16 and F22
Using the EF to EF-M adapter on EOS M I get:
- EF 50mm f1.8 and several EF-S USM lenses: expo override works Ok.
- EF-S 24mm STM: same behaviour as EF-M 22mm STM prime, exposure only changes for F16 and F22
- EF-S 18-55mm STM and EF-S 55-250mm STM: same behaviour as EF-M zooms, expo override not working, exposure does not change at all.
Tonight I will repeat tests on 500D with a more recent nightly.
-
- EF-M 18-55mm STM Expo override does not work, exposure in FRSP does not change at all when changing aperture.
- EF-M 11-22mm STM Same behaviour, expo override does not work
Yep, confirmed the same behaviour with my own EF-M 18-55mm STM
-
Tested again on 500D, with nightly 2015 April 19th. Expo override works well with my EF-S STM lenses (18-55mm, 55-250mm and 24mm).
It seems that on the old 500D the STM, USM and micromotor lenses work all in the same way (it makes sense, STM lenses did not exist when 500D was launched). But in newer cameras (optimized for STM lenses, with phase detection AF on the sensor), probably the STM lenses are corntrolled in a different way...
-
Video related to the aperture problem with STM lens as promised.
Same problems as stated before.
It's funny to see that I'm kind of the first to point out that problem.
I'm glad to see that it wasn't only a mistake from me :)
Lens tried:
10-18 STM
55-250 STM
-
I do high magnification stacked macro pictures and am really thrilled by the full res silent function. For high magnification vibration is a big problem and one way to solve it is by using flash. I am planning for a circuit that will let me trigger the silent shooting, wait a defined time and then fire the flash.
I noticed that after taking a picture I need to half press the shutter again. Is there a way around that? To let the camera automatically return to live view after taking the silent picture?
I was told that there is considerable variation in the delay between pressing the shutter and taking the picture from standard live view - at least on the EOS Ti1. Do you know if that is also the case for silent pictures? Has anyone measured the time from the half-press shutter to the clearing of the sensor is done?
/Bo
-
During my test yesterday on 500D (nightly 2015 March 29th) expo override worked fine for my STM lenses, as I already posted.
But now I've tested it also on my recently purchased EOS M. And there is really a problem with STM lenses.
Lenses I have tested (EOS-M nightly 2015 April 14th)
- EF-M 18-55mm STM Expo override does not work, exposure in FRSP does not change at all when changing aperture.
- EF-M 11-22mm STM Same behaviour, expo override does not work
- EF-M 22mm STM Exposure in FRSP does not change when going from F2.0 to F11, but there is some degree of exposure reduction at F16 and F22
Using the EF to EF-M adapter on EOS M I get:
- EF 50mm f1.8 and several EF-S USM lenses: expo override works Ok.
- EF-S 24mm STM: same behaviour as EF-M 22mm STM prime, exposure only changes for F16 and F22
- EF-S 18-55mm STM and EF-S 55-250mm STM: same behaviour as EF-M zooms, expo override not working, exposure does not change at all.
Tonight I will repeat tests on 500D with a more recent nightly.
Add the 18-135mm STM to this list, I've tested it yesterday on my 70D (firmware 1.1.1B) and it wouldn't work even with Expo Override...
-
It's funny to see that I'm kind of the first to point out that problem.
The slow speed ( max 1/4 ) kinda duped me, a lower aperture was not wanted/needed anyway, hence this got away.
-
500D VSizeSetting :
Tv Time Acc loop
1/4000 10 114 1
1/3200 10 114 1
1/2500 10 114 1
1/2000 10 114 1
1/1600 10 114 1
1/1250 10 114 1
1/1000 10 114 1
1/800 10 114 1
1/640 10 114 1
1/500 10 114 1
1/400 11 125 1
1/320 12 137 1
1/250 13 148 1
1/200 14 160 1
1/160 15 171 1
1/125 17 194 1
1/100 19 217 1
1/80 21 240 1
1/60 25 285 1
1/50 30 342 1
1/40 33 377 1
1/30 41 468 1
1/25 51 582 1
1/20 59 674 1
1/15 73 834 1
1/13 93 1062 1
1/10 109 1245 1
1/8 138 1577 1
1/6 177 2022 1
1/5 209 2388 1
1/4 268 91 2
0.3" 345 971 2
0.4" 409 1702 2
0.5" 528 3071 2
0.6" 682 1805 3
0.8" 809 240 4
1" 1047 2960 4
-
Hi, I have just download Magic lantern (•magiclantern-Nightly.2015Apr28.5D2212.zip
•Built on: 2015-04-28 00:10:02 +0200) to test full resolution on silent mode and after successfull installation, I have followed this steps I found in this fórum on my camera 5d mark II
1.) Prefs tab -> Config files -> Restore ML default
2.) Restart cam
3.) Activate Silent.mo
4.) Restart cam
5.) Put cam to M mode
6.) Activate FRSP (Shoot tab -> Silent Picture -> Silent Mode -> Full-res)
7.) Activate Liveview
8.) Press shutter half
But I do not get anything. There is a message in orange letters:
"full-res pictures only work in manual (M) photo mode"
but I am already in M photo mode and manual focus.
so I am wondering, Am I missing something in this basic tutorial?
I have got success on Silent mode -> simple: dng and mlv format works great.
Resolution I got is: 1880*1250px.
Also, I cannot see dng and mlv pictures on camera. Only in computer.
Of course, I have load modules: pic_view, file_man and mlv_play and restart cam.
If I take mlv raw video I can see it on my camera but I can not see simple pictures.
Any suggestion? Something I am doing wrong with 5d mark II?
thanks,
-
Since you can record MLV videos, you are probably in movie mode. Switch to photo mode.
-
thank you so much. You are right.
I was in "stills+movie". I have changed Live view to "stills only".
So basic tutorial for beginners like me would be like this:
camera: 5d mark II
0.1) Set camera to photo mode: Live view settings: stills only
0.2) Set quality RAW+L
1.) Prefs tab -> Config files -> Restore ML default
2.) Restart cam
3.) Activate Silent.mo
4.) Restart cam
5.) Put cam to M mode
6.) Activate FRSP (Shoot tab -> Silent Picture -> Silent Mode -> Full-res)
7.) Activate Liveview
8.) Press shutter half
:)
-
3.) Activate Silent.mo
you need mlv_rec.mo loaded too for saving in .MLV
also press * for AF ( if you set up back-button focus that is )
-
I really want exposure overide to work with my stm lenses... So if there's any test I can to help you determine what's the problem, just tell me :)
-
Press the DOF preview button then turn the lens like 45 degrees. It should disconnect the electronics and lock the aperture to what you set (just make sure the lens is still on camera)
Old trick, but works for STM
-
Thanks for the tip, already knew it. It's a good technique since if you use ETTR with a tiny aperture, it will force the shutter speed to go above 1/10th, and then no much troubles.
Still, i d prefer to have aperture control over stm lenses, of course :) .
Also, ETTR should have a feature that set max and min shutter time (you can only set the slowest shutter) and also max and min aperture. Shouldn't be too hard to implement I hope.
It would then make ETTR usable for Timelapsers. :p
I have read that I'm not the only one wanting to use it for timelases... The only problem is when shutter goes way above 1/10th...
So meta data for LRTimelapse are unusable.
Also, when using "take pics like crazy" it a bit of struggling to change the parameters manually without introducing shake in the picture, because it needs a lot of try because taking effect.
I bought a cheap ND filter: will do the job to help me with exposure. And I just have made a 2k picture timelapse... Overexposed when I felt asleep. Ahahaha. I thought that the weather would have been more shady :( I will try to get used to doing timelapses.. And then my project as a low-budget-student, is to do a timelapse of the city where I'm studying :) I'm also composing a music, I will gladly share it with you.
Thanks :)
-
Looking forward to your work @Slasheal!
-
Add the 18-135mm STM to this list, I've tested it yesterday on my 70D (firmware 1.1.1B) and it wouldn't work even with Expo Override...
On my M I had a whole afternoon of fun with the EF/S to EF-M converter and a Canon EF 100mm f/2.8 L IS USM, nice lens, BUT it behaves the same, neither normally nor with ExpOverride, trying to make a FRPS goes to max apperture ( 2.8 ) and snaps an overexposed pic even if I set it up for the lowest apperture ( 32 ) :(
-
With the new 50mm 1.8 STM coming... We will need a fix :o
-
I'll most probably get 'told off' for this post, but here goes.
I think many understand the limitations of full silent DNGs (FSDs), but some still think FSDs will simply replace normal shutter actions.
Maybe FSDs will get better, as gurus find tweaks, but from what I understand we will always see a shutter shortfall in the FSDs.
I was thus wondering whether it would be possible to 'hardwire' in the shutter limitations. In other words when shooting FSDs, only ML can control!set the shutter, ie lock out Canon control.
Doing this will bring in some realism and things can be adjusted as alternative ways are found to extend the FSD range.
As I say, just a thought.
-
Definitely an interesting thought, @garry32!
-
I just realised that aperture work with my stm lenses.. on video mode.
-
I just spent several days testing full-res silent pictures functionality.
I used ML nightly build for 5d3 from April 28, 2015.
I tested silent pictures with 2 lenses: EF 24mm f/2.8 IS USM and EF 100mm f/2.0 USM.
Setting aperture does not work on 24mm lens. The photo is always taken on the widest aperture which is f/2.8 for this lens.
Here are 2 images.
(http://i57.tinypic.com/124x2qp_th.jpg) (http://oi57.tinypic.com/124x2qp.jpg) (http://i62.tinypic.com/11rsmr7_th.jpg) (http://oi62.tinypic.com/11rsmr7.jpg)
Left one is a master CR2 image taken with all ML settings off. I had to put markers indicating distance from tripod in my backyard :)
The camera was focused on the nearest marker '.8'. Aperture set to f/22. You see that all the markers are in focus.
Right image is MLV image taken with 'silent.mo' and 'mlv_rec.mo' modules. Silent picture settings were set to 'full-res'. Exposure simulation and exposure override were enabled in ML menu.
Camera was focused on the same point.
However, the picture was taken at f/2.8.
At the same time setting aperture works with EF 100mm f/2.0 USM on the same camera with same ML build.
Summary:
1. Liveview says that picture will be taken at f/22.
2. Exif says that picture was taken at f/22.
3. Actual picture was taken at widest open aperture.
4. Setting aperture does not work on EF 24mm f/2.8 IS USM and works on EF 100mm f/2.0 USM.
Sounds like expo override may not work with STM lenses. Any other STM lens users can confirm?
EF 24mm f/2.8 IS USM is not STM lens, but aperture does not work on it too.
-
for ML-developer:
I have 5DII. Is the problem "Exposure too long (max 16)." in settings in Canon menu?
( Live View/Movie func. set. > Metering timer > 16 sec. )
Can higher value could help?
-
Please read the OP (the "Limitations" section). A detailed technical explanation of the limitation can also be found in this thread.
-
I confirm that
... Setting aperture does not work on EF 24mm f/2.8 IS USM ...
with FRSP. When I try to close diaphragm with rear wheel - it closes a bit, than opens again. I found the only way to make it works - move photo/video switch to video mode. Yes, I got 1/30 exposure time. Maybe it's possible to solve this "video" exposure time limitation with FPS override, for example - i didn't try.
-
Hello A1ex,
I am a mad microminerals stacker, like pontop and many others, and would like taking HiRes silent pictures using Helicon Remote / Helicon Focus since this app is quite effective on this kind of work.
I have ask for generating a "half shutter" signal instead of usual shot signal and the editor seems OK to implement this possibility. Seing the numbers of body I alone burnt in stacking, I guess it may increase the number of ML users :)
The software works on Linux, Mac, and Win., and is thetering using USB.
Would generating a "half shutter" signal would be OK?
Please would you mind kindly explaining exactly the right way to make it working?
Best regards
Pierre
-
Half-shutter from external apps should work just fine (not tested, but I don't see any reason why it wouldn't work).
-
Hey guys,
am i the only one who get's wrong exposure times in the final FRSP-DNGs?
To be excat, it looks like this:
a) When .mlv is used as container for the FRSPs:
for exposure times <1s the value is correct. All exposure times >=1s are displayed in Photoshop as 1s-exposure.
b) When .DNG is used for the RSP:
the displayed exposure time is always 1s inpedently of the actual exposure.
This is kind of annoying when doing day-to-night timelapses as lrtimelapse is having a hard time correcting the exposure changes.
-
When using LRTimelapse for timelapses use the "Visual Workflow" with silentpics. Under Expert settings check "Use optical Keyframe...".
I have done this now severel times and works fine.
-
Thanx glubber! I did this once. It made some mistakes but worked most of the time. But having correct metadata is the better way.
-
Even if EXIF would be correct, the time measured by ML is the total capture time (which is a bit longer than the actual exposure time), so using this info for deflicker is probably not going to give the best result. I'd say the best way is to use a deflicker tool that looks at image brightness, and I recommend dmilligan's deflicker script: http://www.magiclantern.fm/forum/index.php?topic=8850
The bigger issue with full-res silent pics is that exposure time is not constant (it's a gradient). To my knowledge, there were no attempts to deflicker such images, so it's probably best to use exposure times longer than say 1 second (so the gradient effect is no longer noticeable) and use a regular deflicker tool.
-
OK , Trying to get Started with FRSP on 5D2 with magiclantern-Nightly.2015Jun25.5D2212 , But I have run in to some "Error 70" problems.
I have the Clash logs plus the cam's rom . Here is the cam setup :Silent Picture-->Full-Res-->MLV , Intervalometer-->Take pics-->Like Crazy-->Start trigger-->Leave Menu-->Start after-->3s Modules loaded , file_man, mlv_play, mlv_rec, mlv_snd, silent and Liveview set to"Photo,ExpSim" &"Photo,no ExpSim"
Link to Crash Logs+Rom ->https://www.dropbox.com/sh/qr83z9ltzkye4lo/AADre4uTh-Vz6P-0cPl9IaiWa?dl=0
Links to Zip file with all the Crash logs+Rom ->https://www.dropbox.com/s/dltd9tzzewygko2/Crash%20Logs%20FRSP%2BRom.zip?dl=0
Basically all I want is the FRSP to save to One "MLV" file , this only happen once (6-frame) and the rest of the time gave me single frame mlv files.
Then when I tried to set a stop point of 50 frames it kept going and for some reason you can not exit or stop the Intervalometer, in the end I pressed the AF button then the cam would stop & error out did this four time in a row .Pull battery restart cam then it would want to start in the Intervalometer and take pic's
unless you get in to the ML menu right now. Then all of a sudden the " Cam started to Fire photo with the mirror snapping back and forth , I think about 10 or so CR2 . Then LCD Liveview when black and the cam displayed a message, Needs liveview for picture I think ,so I quickly powered off the cam and pulled the battery , deleted that nightly build and reinstalled my 02-15-2014 build I use, rebooted cam back to normal now, but did have me really concerned about loosening Liveview like that . So I'll just do more research on this , don't what to brick my cam . Is there any one with 5D2 that has great success with FRSP
without crashes , I would like to get at least 300-500 frames per-session, Thanks :)
-
The logs indicate a SRM memory error. I'll try this configuration in about 2 weeks; meanwhile, it would be helpful if other 5D2 users could try.
One thing I didn't try is the "like crazy" option. Does it help if you use a 10-second interval?
-
Hello pholler,
as I want to use full-resolution silent pictures not only for timelapse I needed at least
the normal setting information of the camera (and of course the exposure time).
a) the time stamp of the picture
b) the value of aperture
c) the value of focus length
d) the value of the used ISO
e) the value of the exposure time
I am a very beginner of programming ML but as I
looked at the sources I found out that the setting of this information was not so complicated for DNG.
Similar things are already available for the MLV.
As exposure time I used the total capture time.
(And for test purpose the lower 3 digits of the capture time I write into the meta data 'SubsecTime', see example below)
I am testing this on my CANON EOS 700D and I am happy to see now my camera settings in the DNG.
@a1ex: Should we implement this into the silent modul? Or are there other ideas?
Example of EXIF-Info:
Filename - 72540083.DNG
ImageWidth - 128
ImageLength - 84
BitsPerSample - 8 8 8
Compression - 1 (None)
PhotometricInterpretation - 2
ImageDescription - (ML DNG silent picture)
Make - Canon
Model - Canon EOS 700D
StripOffset - 1536
Orientation - Top left
SamplesPerPixel - 3
RowsPerStrip - 84
StripByteCount - 32256
PlanarConfiguration - 1
Software - Magic Lantern
DateTime - 2015:06:25 12:55:06
Artist -
Copyright -
ExifOffset - 728
Serial Number -
Lens Model -
ExposureTime - 1/2.0 seconds
FNumber - 12.80
ExposureProgram - Not defined
ISOSpeedRatings - 100
ExifVersion - 0221
DateTimeOriginal - 2015:06:21 12:55:06
ShutterSpeedValue - 1/1 seconds
ApertureValue - F 1.00
ExposureBiasValue - 0.00
MaxApertureValue - F 1.00
MeteringMode - Unknown
Flash - Not fired
FocalLength - 29 mm
SubsecTime - 508
SubsecTimeOriginal - 508
FocalLengthIn35mmFilm - 0 mm
-
@a1ex: Should we implement this into the silent modul? Or are there other ideas?
https://bitbucket.org/hudson/magic-lantern/pull-request/603/dng-module-wip
-
Any chance of getting silent picture to do exposures longer than 15 seconds?
Many thanks!
-
The answer is in the first post of this thread.
-
I have some kind of problem with the full res silent pic module. It worked well before, I also used it for silent pic timelapse with the appropriate intervals, but today something happened. I haven't figured out yet, maybe you can help.
Cam: 700D 18-55 STM kit fw: latest 1.1.4
ML build: latest 02 July 2015
Settings: Manual Mode, 1/10, apr: around 3.5 iso: 100
When I start to make full-res silent pic (tried both MLV and DNG) nothing happening, it seems to be the cam is shutting down.
When I view it after the reboot in Pic Viewer it shows the actual picture.
What is the problem? I haven't modified any changes in power save module (default)
Modules on: MLV rec, Fullres Pic, File Manager, Pic viewer
And of course I shot in liveview.
side note: No crash file on the card after I taken the shot.
Thanks for the help!
-
Same with 7D, i suppose: http://magiclantern.fm/forum/index.php?topic=9848.msg150056#msg150056
Half-pressing shutter button brings back LV on 7D. Try it and report back.
-
I tried it and it brings back but still I can't see the picture I've taken after pressing the shutter. Never had this kind of problem with FRSP before..
-
Have you set the 'Image review' in CANON menu to 'Off'?
In this case you do not see the picture after taking a picture.
Short half-pressing the shutter button brings you back to LV,
long half-pressing the shutter button takes the next FRSP.
-
oh i forgot that! thank you, problem solved!
-
Hi all and especially a big thanks you to the team of Magic Lantern for the precious contribution with their work.
I recently installed the module for Full Silent Pictures and i experiencing a problem with ACR,
can't denoise the dng extracts from .mlv FRSP.
Can I fix all the other parameters but the denoise filter by ACR on those files doesn't work at all.
Sequences of images are taken with 5DMK III ef 16-35 f/4 IS iso 3200 converted with raw2cdng. version 1.7.4
magic lantern is Nightly.2015Apr28.5D3123, ACR 7,8 or 9 same issue.
Here a link of a sample dng made with FRSP http://www.flli-baccino.com/djwNGTRE/images/dng/2982000000000.dng (http://www.flli-baccino.com/djwNGTRE/images/dng/2982000000000.dng)
Extracts files from .MLV or .RAW shot in video can be denoised from ACR the issue it's only with FRSP.
Thanks in advance for any suggestions.
-
e.g. MLV file takes 400mb, and the same one converted to DNGs takes 300mb.
The same info, but 100MB less? Is it better to use DNGs insted of MLV to save space on CF card.
Am I missing smth?
-
Do you want to add some infos about your workflow, cam used, ML version? Are we talking about FRSP at all? And does mb mean megabytes or megabits?
-
Did you convert to DNG with a tool that compresses DNGs (like MLRawViewer)? In camera DNGs are not compressed, so they will be the same size as MLV. Both MLV files and DNG files can be compressed on a computer, but in camera processing would be too slow (unless we were to reverse engineer the hardware Canon uses to compress CR2s or JPEGs and figure out how to repurpose it, which may or may not even be possible/practical)
-
1. Sorry, I meant megabytes.
2. And yes, I've tested the size on recorded MLV (FRSP) and then I've converted them into DNG with MLRawViewer.
So, DNG's recorded by FRSP and DNG's converted from MLV - will have different compression?
- I tried to convert MLV file (112 MB) to DNG = DNG files (80,4 MB) then RAR them = dngfolder.rar (67 MB)
- If I compress MLV file (112 MB) to WinRar file = mlvfile.rar (87,8 MB)
I'm just trying to figure it out how it's better to store HUGE files.
-
So, DNG's recorded by FRSP and DNG's converted from MLV - will have different compression?
Yes, but only if you use MLRawViewer to convert to DNG, or if you use another tool to compress the DNG after conversion (like SlimRaw, Adobe DNG Converter, etc.). Most other MLV to DNG converters do not compress the DNG output.
It's important to note that this is lossless compression, so there will be no difference when viewing or processing the files.
Like I said, it's easy to apply compression on a powerful general purpose CPU, it's almost impossible on the dinky little embedded ARM processor in the camera (would take way too long), so we (ML) can't really apply compression in-camera. Canon compresses CR2s somehow, AFAIK we don't know much about the particular hardware that does that.
The MLV format itself supports lossless compression, which can be applied by mlv_dump. Depending on the particular data and compression scheme used (there is a newer one that hasn't been merged yet), you might see better compression ratios than with simply applying something like rar or zip to the MLV file like you did. You can also probably get away with reducing the bit depth to 12 or maybe even 10 without much noticeable change, which would technically be a form of lossy compression.
-
The MLV format itself supports lossless compression, which can be applied by mlv_dump. Depending on the particular data and compression scheme used (there is a newer one that hasn't been merged yet), you might see better compression ratios than with simply applying something like rar or zip to the MLV file like you did.
Yes, but this not works for me :(
I try to compress about 6 GB file:
mlv_dump.exe -o compress.mlv -v -e -c -b 16 -l 9 -x big.mlv
and I get about 4 GB file, good.
Than, i try to extract dng from that file:
mlv_dump.exe --dng --no-cs compress.mlv -o
I get about 2 GB of dngs and mlv_dump.exe crashes having about 2 GB memory allocated according to Task manager. My PC is 64 bit with 24 GB memory.
-
Yes, but this not works for me :(
The new compression scheme works much better, but hasn't been merged yet. You might get the current one to work better if you don't use the frame delta option.
-
Looking forward to the new compression scheme to be merged into the nightlies!
-
Due to higher compression ratio for backup purposes i would prefer original to be fixed...
-
I'm pretty sure the new scheme has a better compression ratio. It's also many times faster.
-
so.. I just have to ask here.. so , someone might send me to right place
after some time I decided to install ML on 550D.. only interest at this moment is silnet pictures for timelapse
after whole day watching youtube, reading forum and wiki and who knows what.. I am totally confused
so, got ML, and its working, 550D with sigma 30mm 1.4.. no matter what I do, it always says that I have to switch to manual.. it is.. and still it says the same.. ok. .i switch the lens, 50mm 1.8 canon
ok.. now its working.. sometimes.. and for some reason it stops or say raw error or something like that.. its fast I cant see.. then.. got few crash reports.. and finally managed to take xxx pictures in slinet.. live view.. and I had to set my camera to 1/3000 f22 to be able to get normal picture ( so, there is no much use for me, if its like that.. cant take any serious timelapse without results or normal results or to see what I am doing ) .. yes I can preview picture in camera.. great.. but then.. for some reason when I go back I have to beg it to work and to take pictures, and still.. this is no way of taking pictures.. at least nothing serious.. or I am doing something wrong.. please point me into right direction
ok.. so.. after I managed to make mlv.. I cant read it from my camera.. ok. never mind that, but its problem for me.. anyways.. I got all this files.. I cant do anything with them
after reading this forum I got mlrawviewer.. and it crashes when I start it.. i get a glimpse of a pic.. I can see its set to 1/3 sec and it crashes
got mlv_dump something.. no gui.. what to do with it ?? any clear tutorial or instructions ? :) link please
conclusion: so , basically after beging camera to take pictures ( yeah, had problems with internal intervalometer also and half press to take pictures, found out only way it would work if I set it to start after menu exit ) , pictures I cant change settings, as its over exposed, I get some files I dont know what to do with them, or its not working
ps.. so many info on this forum, some are old things some new, and I just need some help
so... if anyone is willing to step in and help, it would be nice :)
or is this normal and just have to accept it ? :D
-
so...looks like you missed some things...so you didn't read maybe carefully all posts.
So to sum it up. With manual mode better try the M on your cam and not Av / Tv / S modes....so M in this case doesn't refer to your M / AF switch on your lens. AF is supported with frsp. Try to set your shutter speed not faster as ~1/30. Compensate with ISO or take a longer shot (1/15 or 1/8 or 1/2 or 1" etc...)...1/3000 like you settled-in will never ever work. So re-read the 1st post again but this time carefully. Read it twice or even thrice until you understand how frsp works. Maybe check your image review settings in canon menu too :D I would stay away from MLV and instead use DNG option for the beginning (no need to hassle with mlvdump-questions and asking therefore for links). DNG should be clear what it is and how to open / edit them...
I am quoting a1ex from 1st post:
The fastest shutter speed I've got is around 1/10 seconds
Once you still get strange results come back and write down your detailed steps / settings so we can try to reproduce- maybe that time with not so much so's. May I ask if you get same problems on your 6D (signature)?
-
I didnt install it on 6D.. I use it for work and dont want to mess with it :)
550D has around 160 000 clicks.. so its ok if something happens to it :D
-
after some time I decided to install ML on 550D.. only interest at this moment is silnet pictures for timelapse
I have to disappoint you but 550D does not work good with full res silent pictures. The problem is with shutter speed. From below you are limited with 0.5 seconds. Silent pictures can go as fast as 1/10 secs (not my data, based on a1ex feedback), but usable pictures start from 0.5 secs because of the gradient (http://www.magiclantern.fm/forum/index.php?topic=12523.msg120750#msg120750).
From above full res silent pictures can't take exposures longer than 0.8 seconds (http://www.magiclantern.fm/forum/index.php?topic=12523.msg143510#msg143510) with your camera.
In the end with 550D you are limited to exposure interval between 0.5 secs and 0.8 secs.
I recommend you to read the whole thread, especially posts this (http://www.magiclantern.fm/forum/index.php?topic=12523.msg120497#msg120497) and this (http://www.magiclantern.fm/forum/index.php?topic=12523.msg143510#msg143510).
-
You could try using a variable neutral density filter to give you longer exposure times.
-
-
-
My little tests with FULL resolution silent mode timelapse video
Canon 6D, ML Nightly.2015Aug18.6D116
DNG , f/10 , 1/2sec, resize to 4k + adobe after effects + adobe premiere
-
When attempting to do full res silent pics on 50d using the may or june nightlies using "take pics like crazy" I also get individual mlv files per frame, and it cannot be stopped without taking out of battery.
Has there been any progress on this?
-
The simplest solution to avoid long exposure problem on 500D, 550D, 600D.
http://www.magiclantern.fm/forum/index.php?topic=12523.msg129874#msg129874
silent.c
cleanup:
call("FA_DeleteTestImage", job);
if (copy_job)
{
call("FA_DeleteTestImage", copy_job);
}
+ long_exposure_fix();
gui_uilock(UILOCK_NONE);
static void long_exposure_fix()
{
unsigned shutter_old = lens_info.raw_shutter;
if ((cam_500d || cam_550d || cam_600d) && shutter_old < SHUTTER_0s8)
{
unsigned shutter = SHUTTER_1_500;
prop_request_change_wait( PROP_SHUTTER, &shutter, 4, 100);
void* job = (void*) call("FA_CreateTestImage");
call("FA_CaptureTestImage", job);
call("FA_DeleteTestImage", job);
prop_request_change_wait( PROP_SHUTTER, &shutter_old, 4, 100);
}
}
-
FRSP continuous :
You need nd filter simulation?
How does it work?
The camera take silent pictures in continuous mode, for example, Tv 0.5s, 4 frames :
0.5 + 0.5 + 0.5 + 0.5 = 2s
We can average frames in mlv_dump.
The movement of water/cloud will be like two seconds of exposure.
The image will 1EV more DR.
4 frames -> 1EV
16 frames -> 2EV
64 frames -> 3EV
Writing speed must be shorter than the exposure time.
(http://s2.postimg.org/peowxz1rt/menu.gif)
one vs 20 frames :
(http://s27.postimg.org/silu76rxf/longexpo.jpg)
Dual ISO alternately (100/1600, 1600/100, 100/1600...) :
I've never been convinced by the dual iso (loss of detail).
I think it should be a good solution, but I'm not 100% sure about because I do not tested in the landscape.
(http://s18.postimg.org/ahv6mn961/dual_iso.jpg)
So in theory we get a huge DR.
100/1600 on the 500D give 2.2EV more.
If you averaged 16 frames, 2EV more DR.
Dual iso + 16 frames, give 4.2EV more for 500D :o
Tree :
(http://s2.postimg.org/mvrs4h12x/dualiso.jpg)
Interior :
(http://s7.postimg.org/me3xmz2ln/dualiso2.jpg)
-
Wow 8)
Very interested in both features. How to get it for 5D MkIII?
-
Here is the code :
https://bitbucket.org/Gr3g01/magic-lantern-frsp/commits/branch/unified
It still requires many improvements :
Lag between shots :
- ML code lag 50ms - 80ms,
-- call("FA_CreateTestImage"); //4ms
-- raw_update_params(); //17ms
# raw.c
# 721 autodetect_black_level //3ms
# 744 autodetect_white_level //14ms
-- task_create(silent_writer_task) //50-9ms, mostly 20ms
- FA_CaptureTestImage code lag 40ms ? look -> http://www.magiclantern.fm/forum/index.php?topic=14363.0
The writing speed is unstable
-
Yeah, well...
If noone compile and share this in the near future... I should master it myself...
with blackjack and hookers :)
-
Excellent Stuff, Guys!!!
Will dig into this some more later on when timing persist.
Thanks for sharing, @Greg!
-
Can you compile your Nd filter simulation features for 600D please ? :D
-
FRSP continuous :
Nice stuff! It's been awfuly quiet on this forum lately, almost no significant updates or new features, nice to see someone's have new awesome ideas.
I believe your previous long exposure patch made into official nightly builds, congrats on that! What about all that FRSP features, any chance they will appear in the official builds someday?
-
I believe your previous long exposure patch made into official nightly builds
Long exposure patch for (500D, 550D, 600D) is in the official nightly builds.
What about all that FRSP features, any chance they will appear in the official builds someday?
I do not know, it works but requires improvements.
Preparation tools to build ML on Windows is just 3 minutes -> http://www.magiclantern.fm/forum/index.php?topic=15894.0
-
@greg
[dual iso] from my tests the detail loss on +2ELV is neglible (https://www.flickr.com/photos/chmee/16694204503/in/datetaken-public/), but visible with +3elv (https://www.flickr.com/photos/chmee/16855058769/in/datetaken-public/). dont use 100/1600, but ie 100/800. and picture stacking has its own limitations, so i dont really see the benefits of your code.. my(!) main benefit for dual-iso is photographing dynamic motives, therefore stacking cant help.
regards chmee
-
@chmee:
It's probably just you :)
Sometimes DR more important than details.
Breaking 1 FPS limit is a godsend for me and stacking is very handy.
-
Hello, I met Santa Claus, he told me how to make the bulb FRSP.
FRSP bulb :
It does not work on cameras with SHOOTMODE_BULB, we need SHUTTER_BULB in Manual mode.
So it probably will work only with 500D, 550D, 600D, 650D, 700D.
I tried (500D) 15 minutes exposure, it works.
How to use it?
- Set shutter speed to "bulb",
- Go to the ML menu -> Shoot -> Bulb timer (not enabled) -> Set Exposure duration (0s - 15m00s),
- Take FRSP Bulb! :)
Code - https://bitbucket.org/Gr3g01/magic-lantern-frsp-long-expo/commits/a5af9a0a3602aeb746fb2fc14dc06eb6fc2c0d47
Use at your own risk
Thanks for your help Alex!
-
Thats great! Did santa tell you if there was any hope to break the 15 sec limit on other cameras too? ;)
Its on my 7d's wishlist 8)
-
Ok, my first post.. here we go..!
Is it possible to shoot full-resolution silent pictures in crop-mode? Thought I saw something here about that. Choose MLV as format perhaps?
-
Full-resolution means that you are using the whole sensor, and all the pixels. So there's no crop at all in this mode.
Crop mode only makes sense when you shoot at lower resolutions, like the ones used for video recording (1024p, 720p, etc.)
-
I don't know ig this has been asked before, I've tried searching and found nothing. Can Silent Pictures be used together with Focus Stackiing module? This would be a killer combination!
-
@leocallejas:
Advanced Intervalometer (http://www.magiclantern.fm/forum/index.php?topic=8431.0)
-
Hi, everybody.
I include intervalometr and Silent Picture, an interval 0 (automatically to make it the shortest), exposure1/125, the mode of shooting M. I start shooting. Real exposure~ 0.3 s. The interval between shots at first 1.5 s (shortest), then through one - two hundred shots starts changing (can reach to 6 s, changing both in big and in the smaller direction. Is it normal? How to stabilize an interval? I have Canon 6D 1.1.6.
-
MLV? DNG?
-
MLV
-
In MLV some data of EXIF register, in DNG isn't present.
-
In MLV some data of EXIF register, in DNG isn't present.
Yes, this will fix that IIRC: https://bitbucket.org/hudson/magic-lantern/pull-requests/603/dng-module-wip/diff
-
Hi guys,
I also have a 550D but never really got on with the Silent Pictures on that camera (hard to get anything usable and the noise was too much) ... is it a lot easier on the 5D MKII and now get better results with a 5D MKII? ...
I want to replace my trusty 550D now and it's time to upgarde ... I used ML on the 550D for a lot of other stuff which is great btw ...
I have recently just got hold of a nice Canon 5D MKII and just need to ask a (simple?) question ...
The question is:
I require, for the 5D MKII, the FRSP function that can take JPGs & RAW photos for either Timelapse in Daytime and night time Astro work and also for Focus Stacking ... I'm so confused at what builds have what functions/options ...
I do not need MLV or RAW video capabilities (yet) just the options for taking Photos only ...
Will the old 2.3 Stable edition be enough or has FRSP advanced that much that I would need to go for a nighlty build? ... if so what edition (old or new) would give me these capabilities? ...
Thanks,
cheers,
Gem
-
Support for v2.3 has expired.
-
FRSP are only avail in the latest nightlies whereas it isn't in the old (very old) v2.3 as Walter mentioned.
-
Just a quick question I can't seem to find the answer to. Is it possible to use this feature and or the (raw) video recording features on a camera with a broken/worn out shutter? I ask since in the first post there is mention of err20. Thanks!
-
As long as you can enter LiveView, yes.
If you can't, but you are able to remove the shutter mechanically, you only need minimal code changes. From my past experiments, something like this should do the trick:
call("lv_start"); /* this enables LiveView feed without actuating the shutter */
lv = 1; /* this tells ML we are in LiveView (not sure if needed, since we are not entering LiveView as usual) */
-
Removing the shutter would be a little scary but then maybe your camera can live on!!! That would be wild!
-
Very interesting, thanks very much! Even with my poor coding skills this shouldn't be an issue I suspect.
-
:D
Hi ,
Thanks for all the great work :-X
I use ML for years for video on 550D,
now I started doing timelapses of the Dutch cloudy skies.
The silent.mo works perfectly, when using a canon lens,
but not when I use my Samyang 14mm without chip.
Is there a work around for that?
This is with the intervalometer, but with clicks:
( I started using the raw ml video to at a very low frame rate 1 per second,
but that drives the shutter speed to much up.)
Greetings Arthur
-
What problem are you getting with the manual lens?
-
Hi Alex,
Thanks for the relpy.
You are right it works normally. :D :) ;) :P
I have tested it again.
I dont know what I did do wrong, but now it is working perfectly.
Timelapse and silent.mo and ettr.
Is there some minimum slutterspeed.
Sorry to have bothered you.
Arthur
-
Hello,
I just discovered that ML now has silent full-resolution pictures ability (thanks a1ex for the great work!). These days I am into extreme macro focus stacking - I designed and built an Arduino based automated focus stacking rail, "Fast Stacker" (http://pulsar124.wikia.com/wiki/Fast_Stacker), and with my new macro "lens" - Nikon M Plan 10x/0.25 microscope objective - I will be routinely doing 300-1000 shots focus stacks, so the limited shutter life of my 50D is becoming a serious concern.
I tried the newest nightly yesterday on my 50D, and the full-rez silent pic feature seems to work as it should. One observation is that apparently DNG is much faster than MLV for silent pics - I get 320ms vs. ~1500 ms respectively, so I think I'll stick with DNGs. But is the difference normal? Perhaps 50D's ancient CPU struggles with MLV packing?
But flash doesn't work with the silent pic feature, as my testing and google searching showed. Flash lighting is very critical for extreme macro (magnifications 10:1 and up), as it helps to freeze the unavoidable environmental vibrations. I couldn't quite understand why it is not possible to make flash work with silent pictures - I think it was something about not knowing when exactly to trigger flash.
My Arduino rail can control two separate relays - for now they are used for AF (half-press) and shutter (full press). I can quite easily add a new mode, when the rail would first trigger a half-press with one relay, and then after some delay - trigger an off-camera flash using the other relay. I'd also need to modify the cable connecting the rail to the camera accordingly.
Will this work? Is it possible to reliably take silent pics with a flash when it is triggered a constant delay after camera's half-press? I'd like to understand this better before I start messing up with my rail. It looks like using a flash would solve the gradient issue, as all rows would get exactly the same (very short: <1ms) exposure from the flash.
How often can I take silent pics with my 50D? The first post here mentions "at least every 10s", which is kind of slow - I normally take shots every 2s for studio macro stacking. From the data I saw here it looks like my 50D has the shortest readout time - at 0.14s - so perhaps I can achieve more usable frame rate (ideally 0.5 fps)?
-
One observation is that apparently DNG is much faster than MLV for silent pics - I get 320ms vs. ~1500 ms respectively, so I think I'll stick with DNGs. But is the difference normal? Perhaps 50D's ancient CPU struggles with MLV packing?
I think maybe you are confusing "capture time" with "save time". "Capture time" is the time to capture the frame (sensor readout), not the time it actually takes to save it to the SD/CF card. It roughly corresponds to the effective shutter speed. 320ms is impossibly fast for the time it takes to save a FRSP (near 100MB/s write would be required, IIRC the 50D maxes out at around half that). Perhaps you changed the shutter speed when you tried MLV and saw a different "capture time"?
DNG saving is considerably slower than MLV b/c MLV is allowed to be little endian (which is how the image data comes off the sensor), DNG spec requires image data to be big endian, so we have to flip every other byte in the raw image data, which takes a significant amount of time. With MLV we just write some headers/metadata and then a straight dump of the raw buffer.
I take silent pics with my 50D? The first post here mentions "at least every 10s"
- If you use the intervalometer, I recommend taking a picture every 10 or 15 seconds (not faster). Saving DNGs from the camera is slow.
The 10 second limitation is actually from the slowness of DNG saving time, this is why you should use MLV (and it's one of the reasons MLV was implemented for FRPS), it's much faster to actually save.
-
Thanks for the reply! The timings I am talking about are those displayed on the camera screen right after the shot is taken. I understand that these timings are not just the capture time (which I know from a post here to be 140ms for 50D), but also include writing time.
I am pretty positive that these timings were ~350ms for DNG and much longer for MLV, but I will double check that.
I have a pretty decent CF card - Lexar Pro 1000x, and from RAW video experiments I know I can have a sustained write speed around 84 MB/s. So perhaps the ~350ms result is not so surprising?
Do you know anything about the usability of a flash with FRSP? Will it work in principle (e.g. are there any rolling shutter etc. artifacts when using a flash)?
-
Indeed, my numbers were not right. I redid the test today, and with 0.3s exposure and DNG format I got two timings - 550ms for capture, then 3200ms (I guess total). With MLV the capture timing is not shown (or shown too briefly to be read) - that was the source of my confusion before. The total timing with MLV is not fixed - it floats around 1300-1900ms. So now it does make sense.
I also tested triggering silent picture using a wired remote (the AF switch) - it does work, for multiple shots.
Finally, I set exposure to 1s and then manually triggered an external flash, after half-pressing the shutter button. It does work, but I have to wait until the blue LED lights up (takes ~1s), and then a bit more (~0.5s). If I press the flash earlier it doesn't show in the shot, but if I do it ~1.5s after half-press, the flash works as expected - no artifacts (gradients etc.).
So it does look like the silent picture feature can be used with my Arduino macro rail together with an external flash. The sequence of events should be like this:
- the rail triggers the AF (half-press) relay for a specified time (~1s);
- after that it waits for another fixed delay (~0.5s ?) and then triggers the second relay, connected to the flash
- then it waits for a third specified delay (~2s?), and goes back to the step 1.
The big question is whether three fixed delays will result in a reliable (no skipped shots) long (~300 shots) focus stacking sequences. I think I am motivated enough at this point to start tinkering with my rail's software to test this out.
-
@pulsar124:
You cannot rely on any fixed delays, as capturing code can delay waiting buffers to flush, for example.
And if you search this forum thoroughly, you will find that devs advised many times to use LED just like that TV IR remote for signaling to external devices just before it really start to capture or at any event you need.
And, finally, you can fully control your rig from within ML, shooting with intervalometer for example and just signaling when to move/flash/etc.
I have a dream to make DIY slide/pano, so it would be great if you succeeded and share your experience :)
-
Thanks for the info! I did see LED feedback suggested as a means to use silent pictures with remote triggers, but I'm still hoping that under certain (well controlled) circumstances fixed delays will do the job. For example, using a fast card + shooting at low enough fps should reduce or eliminate write buffer related uncertainty. And it sounds like I'll need a lot of hacking to my rail to enable an LED feedback. I'll try my simple idea first. For studio focus stacking, everything can be controlled very well - I can always use the same exposure, the same fps; my rail would allow me to fix precisely all the timings - how long the half-press is etc. We'll see.
I noticed there are two ways to trigger a sequence of silent pictures - one by using one long half-press per photo, the other one using two short presses per photo. (The first one would be easier to implement in my rail). Do you know which approach results in faster framerate for actual photos?
I wouldn't use ML as a focus stacking controller - I tried it initially, before building my Arduino rail, and didn't like it (mostly because of the need to use LV - meaning very slow frame rate). With my Arduino rail I can reliably do 4 fps (RAW images) for at least 30 shots, with external flash - which is perfect for focus stacking of live insects. This is not possible with ML.
-
Yes, LED feedback probably too excessive for you. I always shoot silent pictures with intervalometer, not manually, I don't know specifics of triggering silent shots with remote. 4 fps- great results, intervalometer can't shot faster than 1 fps, but this is a limitation of intervalometer itself.
-
I modified my macro rail code to use half-press instead of full press, and did some testing. When camera exposure is set to 0.1s, half-press should be at least 0.8s long to reliably take a silent picture. And I can reliably take a long sequence (at least 100) silent pics if the interval between pics is 4s (MLV format). My camera is 50D, the card is Lexar Pro 1000x.
So up to now it seems like it might work with my focus stacking rail. The critical test will be (after a bit of soldering) to connect both camera and external flash to my rail, and to see if I can come up with a fixed delay (plus play with different exposures) for the flash to work reliably.
It is a good timing, as I just (finally) received the RMS-EOS adapter for my new microscope objective, which will give me 10:1 macro magnification.
-
I've spent half a day today trying to figure out shortest timings which would enable flash use with FRSP. I used my modified Arduino rail for that, with two circuits controlling separately camera's half-press and flash. As expected, flash worked reliably once you make exposure very long (say 5s), and trigger the flash half way through exposure. Then I tried to reduce exposure as much as possible, and arrived at the following timings which seem to work well on my 50D (using DNG format; my card is Lexar 1000x):
Exposure: 0.8s;
1) t=0s: enable half-press;
2) t=0.9s: trigger flash
3) t=1s: release flash and half-press;
4) t=6s: go back to 1st step.
The 0.8s exposure happens somewhere between steps (1) and (4). The exposure is long enough to absorb any variations in the delays between the half-press and the actual capture. It needs at least 6 seconds between shots for reliability, which is fine as this is a normal delay used in focus stacking to let the camera vibrations from the rail motions to settle down.
I ran a long test with the above timings - 283 shots (almost 30 minutes), and all the shots where perfectly exposed by the flash except for a single black shot. The timings will be different for different cameras, and likely different for different memory cards.
But I think overall this is a good news - it looks like the full resolution silent picture feature is totally usable for macro focus stacking photography, with and without a flash. One needs fairly long exposures for this to work reliably (0.8s for my 50D), which will require a fairly dark studio environment (extreme macro is done at effective apertures f/20 or smaller, which helps). Also I need to check if noise becomes a problem - in the past I saw quite a bit more noise with exposures of a few seconds, compared to exposures 1/100s or shorter.
I plan to release soon the new version of my Arduino macro rail software (http://pulsar124.wikia.com/wiki/Fast_Stacker) with the support for the FRSP feature. (It already works, just needs to be thoroughly tested.)
This was all done with DNG format. For some reason MLV didn't work for me - perhaps I just need to spend more time on that.
For some reason I cannot see DNG shots inside my camera (they are totally invisible) - can anyone tell me if I am doing something wrong here? These are the modules I loaded: mlv_play, mlv_rec, pic_view, silent. The ML is the nightly from a few days ago.
-
This is the picture I have about FRSP, which suggests the best way to trigger the flash. Please let me know if you find serious flaws with this picture.
(https://farm2.staticflickr.com/1559/25198792185_a9ca009b96_c.jpg) (https://flic.kr/p/EoJp1e)FRSP + flash (https://flic.kr/p/EoJp1e) by First Last (https://www.flickr.com/photos/99745838@N03/), on Flickr
Horizontal line is the time axis. Large red rectangular curve is the half-press button - zero when it is not pressed, at a high position when pressed. The duration of the press is dt_AF - it should be long enough for ML to interpret this as a silent picture (not as a command to switch to Live View). In my tests dt_AF=0.8s or more for Canon 50D.
I am assuming that the time from initiating a shot (the rise of the red curve) to the time when light capturing starts, simultaneously by all pixel rows, is variable, with sort of normal (Gaussian) probability distribution (the blue bell curve). dt_exp after the light gathering started, the very top pixel row stops gathering light (followed later by the rows below). dt_exp=top_row_exposure_time (measured to be ~1/30s for my 50D by people in this thread) + the camera exposure time, and should have a fixed (not variable) value. (Or perhaps it is the maximum of the two values, not their sum?) So the end of light capture will have the same bell shape as the blue line, just shifted to the right by dt_exp.
The top panel shows the situation when camera exposure is short (say 0.1s or less), resulting in the blue and green bell curves partially overlapping. Now you can see there is no perfect spot to trigger the flash; the best spot (thick black vertical line) is half-way between the bell curves, but even there there will be some shots (represented by the green filled area) where the light capture of the top row ended before the flash - resulting in some (or all) of the top rows being dark. For a similar fraction of shots (represented by solid blue area) flash goes off even before the capture started, which will always result in all rows being black.
So let's increase the camera exposure! (Bottom panel). Now the two bell curves are well separated, so one can choose such a time to trigger the flash (at a later time, compared to the top panel) when neither "capture ended before the flash" nor "flash goes off before the capture" problems ever happen. (Well, if the distributions are truly Gaussian - which I doubt - there still will be a very small chance of the either problem happening; but this will affect only a tiny fraction of all shots).
I think these plots (if they indeed capture the essence of what's going on) give a good idea regarding how to choose the three time delay parameters involved - dt_AF, dt_exp, and dt_flash. In particular, camera exposure should be comparable or larger than the total width of either of the bell curves. (From my measurements, it is ~0.8s for 50D). It is also obvious that dt_flash is a function of exposure - the larger the exposure is, the larger dt_flash becomes (it always tracks the half-way point between the two bell curves.)
I hope this will help other people interested in using a flash with FRSP, for macro focus stacking.
-
Great info, thanks. Regarding saving format - saving to DNG is slow and drains battery, as it involves some data manipulations while MLV simply dumps sensor output.
Yes, there is no in-camera dng viewer, you can try activate mlv_play module for MLV, but i'm not shure if it can render so big frames.
What exactly your problem with MLV?
-
I think I just didn't spend much time trying to find good timings for MLV. I tried to use the DNG optimal timings with MLV, and all but first frames were black, so some more tinkering is needed.
Too bad that I cannot see DNG files inside the camera. For extreme macro focus stacking (typically 300 shots or more for a single stacked photo) I need a solution where I can pause stacking if something goes wrong (e.g. flash gets overheated, or battery dies), check inside the camera how many recent shots are bad (black), and then rewind the corresponding number of frame positions on my rail, and restart stacking.
I don't really have experience with MLV format - will it allow me to see recent individual shots inside camera easily? If yes, how to do that?
-
Do you have image review enabled in Canon menu?
I don't see why MLV would give different times - the saving process is done after the image was fully captured (no pipelining or parallel tricks).
-
^ Yes I do have image review enabled - is it a problem? I actually need it to see live if the shot I just made was properly exposed by the flash (when testing), and to see if my stacking is progressing well (when doing focus stacking).
I am puzzled myself about MLV not working with flash - I need to do more testing to figure out what's going on.
-
You need it enabled to see the previews. Do you get a preview when taking a silent picture manually?
-
Yes I do see preview. I only take silent pics manually (from my Arduino macro rail, via camera shutter cable).
-
Then... the issue is?
Too bad that I cannot see DNG files inside the camera.
-
I don't really have experience with MLV format - will it allow me to see recent individual shots inside camera easily? If yes, how to do that?
Interesting question, as i never tried to watch my recorded timelapses on camera - i simply have no reason for that, as it's usually to late to fix anything when it done :) I just take MKII wich i use for timelapses, shot some silent MLVs, activated mlv_play, press play... and nothing :( Then I activated file_man, opened folder (It's in Debug menu), choose "View" - and there it works :)
-
You can view DNG files in the same way, with the pic_view module (just not as animation).
-
a1ex: I need to see a few last shots I took, not just the last one, and not just for a second. When a flash dies e.g., by the time I paused the rail could already 3-5 shots behind.
mothaibaphoto: The only modules I loaded were mlv_play, mlv_rec, pic_view, silent. So you are suggesting I also need to load file_man, and the look for the recent photos in the Debug/Folder section?
My other grip with MLV is that it seems to always adding new pics to the same MLV file, even after I leave LV and re-enable it, so it ends up merging totally unrelated focus stacking sequences. Is there a way to start new MLV file when I want?
-
To start a new MLV file, turn off the intervalometer, then turn it back on.
Creating a new MLV file when exiting LiveView could be a nice enhancement.
-
But I don't use intervalometer! It is fully externally operated (from my macro rail). So it looks like I need to enable and then disable intervalometer to start a new MLV file?
Another question (sorry could find the answer in this thread): do silent pics get any long exposure noise reduction inside camera? I suspect noise will be the biggest issue, when comparing regular shots with a flash (exposure 1/160s) vs silent pics with a flash (exposure 0.8s).
-
Just pressed halfshutter twice and get one MLV file, but expected two, strange. mlv_play won't play it: "Error: GUID withing the file chunks mismatch!"
bugs... :(
-
I didn't have issues reading MLV files on a PC (I used Mystic soft), except for the fact that different focus stacks were merged in a single huge MLV file.
I think this post by g3gg0 is relevant:
http://www.magiclantern.fm/forum/index.php?topic=12523.msg138135#msg138135
In particular,
updated silent.mo with this stuff:
- allow user to choose between DNG, Single-Frame-MLV and Multi-Frame-MLV (disable and re-enable "Silent Pic" from menu to start a new file in Multi-Frame-MLV mode)
So the way to start a new MLV file is to disable and re-enable "Silent Pic" from menu - I wonder if it is still the case?
Also, it is interesting that there used to be a Single-Frame-MLV option - I think that would work better for macro focus stacking. Any chance it could be resurrected?
-
But I don't use intervalometer! It is fully externally operated (from my macro rail). So it looks like I need to enable and then disable intervalometer to start a new MLV file?
In this case, simply opening ML menu and closing it should do the trick. Look for "mlv_file_frame_number = 0" in silent.c and check the comments.
do silent pics get any long exposure noise reduction inside camera?
If you are referring to subtracting a dark frame taken at the same exposure settings (like Canon does), that will actually multiply the noise by 1.41x.
Instead of doing that, I'd recommend averaging at least 16 dark frames. If sensor heating up is an issue, you could take 16 frames at the beginning of the experiment, then 16 at the end, and interpolate between them.
Here's why I recommended 16 (and not 2 or 300): https://wiki.apertus.org/index.php/Black_Calibration#How_many_dark_frames.3F
Or, there is a very nice idea here (http://www.photonics.com/Article.aspx?AID=44298): you could measure the hot pixels to estimate the dark current (so, you can just sit down, take a series of dark frames at different exposures after the timelapse, and then compute a dark frame fine-tuned for each particular image from your timelapse, using those hot pixels). I actually have a proof of concept code based on this idea here (https://github.com/apertus-open-source-cinema/misc-tools-utilities/commit/891e1b80db69f1998993a62bc4509190496787e0), but it needs some tweaking in order to make it compatible with Canon files.
-
Creating a new MLV file when exiting LiveView could be a nice enhancement.
+1
-
a1ex: Thanks, lots of useful info!
I was actually hoping that with the exposures I need for focus stacking + flash (~0.8s at ISO100) noise will not be an important issue. I will do some testing.
So here is a summary of pluses and minuses of FRSP + flash used for macro focus stacking:
+ Mechanical parts (shutter and mirror) are not wearing off (with 300+ shots per single macro photo this could be huge cost saving);
+ Much less vibrations (=sharper photos), especially for extreme macro stacking (10:1 and up), when camera movements are small (<10 um), so shutter and mirror movements become the dominant source of vibrations;
- Shots are noisier (to be tested how seriously)
- Frame rate is limited to one shot per 6s (on my 50D) - so not suitable for live insects
- Requires a dark studio (because of the 0.8s exposures; probably not so bad with typical extreme macro effective apertures f/20 or less and ISO 100)
-
I am happy to report here that after doing more testing of FRSP + flash (for macro focus stacking purposes) I got much better timings. Specifically, I managed to reduce the camera exposure from 0.8s down to 0.25s, with the same level of reliability (only one black frame out of 284 shots - similar to my previous best case scenario with 0.8s exposure). I actually did a few changes compared to my previous setup, not sure which of them was the main culprit for much better timings. In particular, I switched to MLV from DNG; I put to "Auto" long exposure noise reduction in my camera (it was "Always on"); and I significantly extended the shutter half-press time (from ~1s to ~2s). I am still using the same 1 shot every 6s frame rate. (Will try to reduce it in future tests.) By the way, I didn't realize that the timing of when you depress half-press also matters (before I assumed only the timing of engaging the half-press matters).
The new setup has the following sequence of events (camera: 50D; exposure: 1/4s; MLV format; Lexar 1000x card):
1) 0.0s: the half-press is enabled
2) 1.1s: external flash is triggered
3) 2.0s: the half-press is disengaged
4) 6.0s: going back to step (1)
A small caveat: the first shot is always black with the above settings, if you start from the Live View screen. There is a simple workaround for that: before starting focus stacking, briefly press the camera's half-shutter: the camera will take one shot (dark; one can use it later to fix hot pixels in your stack) and will exit LV (black screen). Now if you initiate focus stacking with the above timings, all the frames - including the first one - will be flash exposed.
Second important finding: this morning I made a number of dark frame shots at different exposures (from 1/160s to 0.8s), using both regular shutter and FRSP. When I processed them in the same fashion (using command line dcraw utility: dcraw -T -6 -W -b 500 file_name ; this command increases the brightness of dark shots by a factor of 500x, to make noise much more obvious), I didn't see a significant difference in the noise levels of all these shots, made both with shutter and FRSP.
Specifically, I wanted to compare the situation when I am doing focus stacking using shutter with 1/160s + external flash versus FRSP at 1/4s + flash. Be the judge: here are the two corresponding dark frames, brightened by the same factor (500x), and the noise seems to be pretty much at the same level in both cases:
(https://farm2.staticflickr.com/1541/25239292375_c1a4612f0a.jpg) (https://flic.kr/p/EsiYin)Noise test: FRSP at 1/4s (https://flic.kr/p/EsiYin) by First Last (https://www.flickr.com/photos/99745838@N03/), on Flickr
(https://farm2.staticflickr.com/1695/24871621569_5fd92fc022.jpg) (https://flic.kr/p/DTPyzx)Noise test: shutter at 1/160s (https://flic.kr/p/DTPyzx) by First Last (https://www.flickr.com/photos/99745838@N03/), on Flickr
This alleviates the biggest concern I had with using FRSP + flash for focus stacking - the noise level (because of the longer exposure).
So now, with significantly shorter exposures (1/4s - meaning your studio doesn't have to be very dark) and the quality of the shots being the same or even better (same noise levels; mirror/shutter caused vibrations are eliminated), FRSP seems to be a great tool for macro focus stacking with an external flash - if you have the proper gadget (like my Fast Stacker (http://pulsar124.wikia.com/wiki/Fast_Stacker)) to trigger both camera and flash with specified time intervals, ans also to move the camera between shots. I will be releasing very soon the next public version of my rail's software (v1.14) which adds the FRSP support for Canon cameras.
-
Well, holding the shutter halfway a little more will simply delay the preview (and also the file saving process, which happens after that). It should not affect the capture timing.
It may be helpful to make a small change: to wait for half-shutter release before capturing the image (right before the call to FA_CaptureTestImage). This should give the minimal variation between your external signal (half-shutter release) and the actual capture time.
For even more precise timing, it's much harder, but doable: one needs to add a hook right into Canon's picture taking code, before initiating the exposure. But reducing the exposure below 0.25s is not going to improve the noise, so I don't think it's worth the trouble.
-
My speculation is that extending half-shutter separates well the two points in time when camera's cpu gets very busy: around the time when the capture takes place, and when the captured image gets processed and written to the card. Because they are well separated, there is enough of time for the cpu to "settle down" between the events, which is perhaps why timings become more predictable.
I agree that trying to make timings much better than 1/4s is probably not worth the efforts - no advantage in terms of noise, and in terms of how dark the studio should be (because FRSP cannot have effective exposure shorter than ~0.14ms - capture time for 50D). I think it is already very good as is.
-
Has anyone tried the new Burst mode? I've gos some nice results but I can't figure out how to increase the buffer from 15 frames to more. Would be nice to have some slow-motion footage done this way.
Even with Burst-End trigger i still get 15 frames.
-
Well this is OT b/c there is no burst mode for FRSP, only simple silent pics, but: you can get a little more memory by using SRM job memory in addition to the shoot malloc. The memory suites work the same way and there's already code to allocate the shoot malloc suite, so it should be straight forward to add SRM.
hSuite = srm_malloc_suite(0);
Of course there's not much real difference between doing this and just shooting raw video.
-
Has anyone tried the new Burst mode?
FYI, "the new Burst mode" is around since 2013 (http://www.magiclantern.fm/forum/index.php?topic=5240).
-
FYI: I just released the newest public version (s1.14) of my Arduino focus stacking macro rail software, "Fast Stacker" (http://pulsar124.wikia.com/wiki/Fast_Stacker), which (among other things) adds support for FRSP + external flash. The feature seems to be stable and fully usable now - I used it to generate a few 300-shots focus stacks (using an external flash), for example (ugly bug alert!): https://www.flickr.com/photos/99745838@N03/25384340795 . More details here:
http://pulsar124.wikia.com/wiki/Whats_new
I'll probably make a short youtube video demonstrating FRSP + flash + Fast Stacker in action.
a1ex and other contributors: thanks a lot for this very useful feature!
-
I've been experimenting with Full Res Silent Picture, using DNG, on my EOS-M.
So far all looks fine. I've been using a shutter of about 2 secs and all seems to come out OK in LR.
The 'problem' I've encountered is that the camera screen goes blank and I've no idea when the silent mode picture taking is complete. Obviously, I've left things for many seconds beyond the shutter time, but the screen remains blank.
However, as soon as I do another half press, the camera returns to normal.
Can someone suggest what I'm 'doing wrong', or is this how silent mode works?
-
Is image review enabled in Canon menu?
-
@garry23 Is this behaviour: http://www.magiclantern.fm/forum/index.php?topic=12523.msg145189#msg145189 what you mean? See @a1ex response post there too.
-
@a1ex/@Licaon_Kter
Yes.
I other words, with the Canon review on, say, 2s, I get the review screen and the ML feedback (top left) about the silent picture that was taken. Then the screen goes blank.
Without the Canon review on, the screen is 'just' blank and, of course, no silent feedback.
What I would suggest should be an option that silent should return the camera to the state before the silent half shutter initiation. At the moment the user (me) has no feedback that the camera is ready for taking the next image. That is, silent shouldn't 'just' be for timelapsers ;)
BTW I have tried using both DNG and MLV and both behave the same, ie the camera goes to a blank screen state after the silent image capture and only returns to its pre-silent state after I do another half shutter press.
-
That's it - after the screen goes blank, it's ready.
Actually, it's ready a little earlier - as soon as it prints "Saved" on the screen.
Press the shutter halfway to return to LiveView, or try a long half-shutter press to take another picture right away.
-
Ok A1ex thanks. Now I know how it works I'll work around this.
I'm looking to see how FRSP works in a Lua environment and will post some feedback soon.
Cheers
Garry
BTW I note the spam delay is on, even for trusted members, ie we all have to wait 900 sec between post. I hope we move to a trusted user list soon ;) Strange this post, posted straight away
-
An update: I've been using FRSP + external flash (for extreme macro stacking; ~200-300 shots in a stack) successfully with Canon 50D and my DIY Arduino stacking rail Fast Stacker (http://pulsar124.wikia.com/wiki/Fast_Stacker), for some time now. The good timing parameters (using Lexar 1000 card) are: camera exposure 1/4s, flash delay (after initiating the shot) 1.1s, minimum delay between shots 5.5s. The FRSP is fully supported in my most recent rail software version, s1.14. For this to work you need an adapter like this:
(https://farm2.staticflickr.com/1510/25251015024_78bca1b90d_o.png) (https://flic.kr/p/Etm431)FRSP adapter (https://flic.kr/p/Etm431) by First Last (https://www.flickr.com/photos/99745838@N03/), on Flickr
I just finished writing a detailed tutorial on how to find proper values of the three timing parameters, for any camera model:
http://pulsar124.wikia.com/wiki/User_guide#Electronic_shutter
-
How do I get the menu from the picture below that was posted by Greg (http://www.magiclantern.fm/forum/index.php?topic=12523.msg156393#msg156393) some time ago? The Start, Shots, Delay and Dual ISO are not in my menu, I only get the first 3 entries. I use the latest nightlies on my 50D and 60D.
Should I compile Greg's fork (https://bitbucket.org/Gr3g01/magic-lantern-frsp)? Or should I get a custom silent.mo module from somewhere? Or is this some unfinished work?
(http://s2.postimg.org/peowxz1rt/menu.gif)
-
How do I get the menu from the picture below that was posted by Greg (http://www.magiclantern.fm/forum/index.php?topic=12523.msg156393#msg156393) some time ago? ]
better ask @Greg directly... and do comeback with the answer and a Pull Request too :P
-
Currently, I do not have Canon camera, so it will not be possible.
-
My understanding is that when FRSP is enabled the shutter control (full-pressed shutter trigger) serves no useful purpose, and in fact is harmful (if you accidentally trigger it it will mess up with FRSP picture taking) - correct?
Is it possible then to disable the shutter control in Live View when FRSP is enabled? Only half-press (AF control) would be left operational.
-
IIRC, it does take a *normal* picture, as expected.
-
I thought I was reading somewhere in this thread that this (taking a "normal" picture when FRSP is on) can lock your camera, and at the very least it wasn't recommended.
-
To block the shutter button, take a look at srm_shutter_lock / srm_shutter_unlock from exmem.c.
However, these also block the half-shutter event, not just the full shutter press.
The only method I know that blocks just the full press, not the half press, would be to allocate the entire SRM memory - that way, Canon code would print BUSY on the screen and refuse to take a picture. This memory would have to be freed before calling FA_CreateTestImage. Not very nice.
The current method is to allow both events, and indeed, there is a race condition between them. If you press the shutter button quickly, it takes a normal picture (and the full-res silent code gives up). If you press the shutter halfway and hold it for a while, the shutter button actually gets blocked (right after pausing LiveView). As soon as you release it, the full-res picture is taken.
It's not perfect, but I wasn't able to crash it by pressing full-shutter, after implementing this workaround. But I didn't try too hard :D
-
Hi,
is there a way to take night stars silent full res MLV pictures with the ML intervalometer ?
I'm using a 11mm f2.8 lense, so it gives me a 30ish sec exposure if I want to avoid stars motion.
I read in the 1st post that taking picture > 15sec is not OK
is it still true ?
thanks
-
I am on manual mode, manual focus, shutter speed slower than 1/10 but the full resolution option is not working. Every option is working (SImple, burst, etc) except the full resolution mode. Am I missing something? I am using 50D Nightly.2016Apr28.50D109
-
Have you selected MLV format? Then you need to load the mlv_rec module to get full res silent pictures working.
-
@Josevpm
Thanks for the reply. Found out that I need to change LV settings on the canon menu.
-
Updated ML, but seems like one problem still there. Or maybe I just doing something wrong. Every time, dose not matter what aperture I will set, it will all the the time be wide open. Are there any option to control aperture shooting full res. silent photos? Thanks for help.
-
Please go to first page of this thread and read first post.
-
Maybe someone will be interested.
FRSP Burst code:
static void frsp_burst()
{
msleep(500);
PauseLiveView();
gui_uilock(UILOCK_EVERYTHING);
clrscr();
vram_clear_lv();
struct JobClass * job1 = (void*) call("FA_CreateTestImage");
struct JobClass * job2 = (void*) call("FA_CreateTestImage");
struct JobClass * job3 = (void*) call("FA_CreateTestImage");
struct JobClass * job4 = (void*) call("FA_CreateTestImage");
void* buf1 = (void*) call("FA_GetCrawBuf", job1);
void* buf2 = (void*) call("FA_GetCrawBuf", job2);
void* buf3 = (void*) call("FA_GetCrawBuf", job3);
void* buf4 = (void*) call("FA_GetCrawBuf", job4);
info_led_on();
call("FA_CaptureTestImage", job1);
call("FA_CaptureTestImage", job2);
call("FA_CaptureTestImage", job3);
call("FA_CaptureTestImage", job4);
info_led_off();
int new_gui = GUISTATE_QR;
prop_request_change_wait(PROP_GUI_STATE, &new_gui, 4, 1000);
gui_uilock(UILOCK_EVERYTHING);
raw_set_dirty();
raw_update_params();
clrscr();
raw_preview_fast();
raw_info.buffer = buf1;
silent_pic_save_file(&raw_info, 0);
raw_info.buffer = buf2;
silent_pic_save_file(&raw_info, 0);
raw_info.buffer = buf3;
silent_pic_save_file(&raw_info, 0);
raw_info.buffer = buf4;
silent_pic_save_file(&raw_info, 0);
call("FA_DeleteTestImage", job1);
call("FA_DeleteTestImage", job2);
call("FA_DeleteTestImage", job3);
call("FA_DeleteTestImage", job4);
gui_uilock(UILOCK_NONE);
}
-
FRSP full speed burst - rolling shutter, delay
(camera 500D, shutter values Canon menu)
HTML test code :
<!doctype html><html><head><meta charset="utf-8"><style>body{background-color:#ddd;margin:0;padding:0}@keyframes example{0%,100%{left:20px}50%{left:calc(100% - 70px)}}.zxz{width:50px;height:100%;position:absolute;background-color:#000;animation-name:example;animation-duration:40s;animation-timing-function:linear;animation-iteration-count:infinite}</style></head><body><div class="zxz"></div></body></html>
A 1/500, B 1/500, C = A+B
(http://s33.postimg.org/fjfj1m1q7/1_500a.jpg) (http://s33.postimg.org/vkcpsbozj/1_500b.jpg) (http://s33.postimg.org/lln5s3q67/1_500ab.jpg)
A 1/100, B 1/100, C = A+B
(http://s33.postimg.org/4cq9tuzvj/1_100a.jpg) (http://s33.postimg.org/r2pemuj33/1_100b.jpg) (http://s33.postimg.org/m5bu1qh3z/1_100ab.jpg)
A 1/50, B 1/50, C = A+B
(http://s33.postimg.org/gm4p6ruov/1_50a.jpg) (http://s33.postimg.org/thha79zbz/1_50b.jpg) (http://s33.postimg.org/9k6rkkr33/1_50ab.jpg)
A 1/25, B 1/25, C = A+B
(http://s33.postimg.org/ef0giupen/1_25a.jpg) (http://s33.postimg.org/icnq89c7z/1_25b.jpg) (http://s33.postimg.org/k1wtgbrxb/1_25ab.jpg)
A 1/4, B 1/4, C = A+B
(http://s33.postimg.org/q1kkjzcpr/1_4a.jpg) (http://s33.postimg.org/jlbltw467/1_4b.jpg) (http://s33.postimg.org/lr5woe7mn/1_4ab.jpg)
A 1s, B 1s, C = A+B
(http://s33.postimg.org/klcxmktun/1sa.jpg) (http://s33.postimg.org/wbqv3ymn3/1sb.jpg) (http://s33.postimg.org/kb5f38f8f/1sab.jpg)
A 2s, B 2s, C = A+B
(http://s33.postimg.org/syimh8t27/2sa.jpg) (http://s33.postimg.org/r5fpsx7vj/2sb.jpg) (http://s33.postimg.org/at5o36tjz/2sab.jpg)
Simulation of the profit when rewrite FA_CaptureTestImage
(500D 20ms delay, newer cameras 40ms)
averaged 3 frames 1/500s
(http://s33.postimg.org/51sdu515r/1_500_3frames.jpg) (http://s33.postimg.org/752t1t0yn/1_500_3frames_20ms.jpg)
For faster cameras it might make sense.
-
I'm trying to remove Canon msleep in FA_CaptureTestImage without rewriting function.
500D
cache_fake :
0xe3a0000b (2 x 11 msleep) 1/4000s 338ms
0xe3a0000a (2 x 10 msleep) 1/4000s 329ms //default
0xe3a00000 (2 x 0 msleep) 1/4000s 329ms
0xe3a00001 (2 x 1 msleep) 1/4000s 329ms
0xe3a00004 (2 x 4 msleep) 1/4000s 329ms
0xe3a00032 (2 x 50 msleep) 1/4000s 396ms
0xe3a03000 (2 x 0 msleep) 1/4000s 321ms //other variable, work but profit only 8ms
-
Hi,
First thing:
Thanks for the hard work that you have done on the FRSP!!! Very cool feature.
It looks like a great job and very interesting take on taking 500 images or so with a single shatter use.
I am new to ML, and might ask some stuff that was answered already, I spent about a day searching the forum in order to find some answers, but I still have some unresolved issues...
I do have one question, I want to try and see the image on my pc, that is connected to my camera. Until now I used the canon sdk in order to save the image directly to the pc. Can I do that with this feature? Can I see "Live Video" of FRSP on my pc? Will the canon sdk will work with ML?
Thanks, Asi.
-
FA_CaptureTestImage hack - https://bitbucket.org/Gr3g01/frsp-research/commits/0f35a12e5218da431ad901608d54b9c5fcf4315c
500D
without hack - 329ms
with hack - 321ms
550D, mk11174
without hack - 281ms
with hack - 261ms
700D, mk11174
without hack - 250ms
with hack - 232ms
-
If I set the Intervalometer to the lowest interval possible I do not get one MLV file. The camera is writing one MLV file per image.
Is that behavior intended?
My camera is the 650D
-
My first test using FRSP (on Canon 50D) with my robotic Celestron 6" telescope. I did twenty 15-seconds exposures, and then stacked them using DeepSkyStacker software.
I wish there was a way to go beyond the 16s limit of FRSP; one could get much more spectacular deep sky photos with exposures 1-2 minutes.
(https://c1.staticflickr.com/8/7450/27588618176_87429bf2ce_b.jpg) (https://flic.kr/p/J2UT1C)Space fluorescent bulb (https://flic.kr/p/J2UT1C) by SyamAstro (500,000 views - thank you!) (https://www.flickr.com/photos/syamastro/), on Flickr
-
It's easy to patch Canon code to get 32 seconds, but not so easy to enable bulb mode.
I don't see much point in researching this though, since those very long exposures are unlikely to be shutter killers IMO.
-
Thanks Alex - do you mind providing a reference for the 32s patch? That already would be quite helpful.
In astrophotography, the main advantage of electronic shutter is not shutter life saving, but reducing camera vibrations. (It takes a long time for vibrations to taper off for a camera attached to a telescope.) Basically, you can do 2x more targets per night when you don't have to wait for the vibrations to die off after each shot in a stack.
-
If vibrations are a problem at these long exposures, then yes, it's a valid reason.
There is a semaphore in FA_CaptureTestImage that times out after 20 seconds. Just change the value with cache_fake (or patch_memory on patchmgr branch), similar to the dialog refresh timer hack used in raw_rec.
Maybe fiddling around with bulb mode and the SCS state object routines could give some clues.
-
I've never looked closely at the code yet, but hopefully I will figure it out. Thanks for the info.
-
How exactly would a silent picture cause mechanical vibrations? :P
Topic split to here (http://www.magiclantern.fm/forum/index.php?topic=17423.0).
-
500D FRSP Bulb - http://www.magiclantern.fm/forum/index.php?topic=12523.msg158347#msg158347
-
Alex: I don't think you wanna deal with my raw data. It's 3GB, and needs lots of processing to become meaningful. (E.g. it needs registration - alignment; also dark frame subtraction - I shot 20 dark frames at the same time, same ISO and exposure.)
I just tried different fancy ways to do stacking inside DeepSkyStacker, and in terms of noise patterns Kappa-Sigma looks much nicer than the default Mean. (Mean produces ugly streaks in the noise floor.) But once you adjusted black/white points and gamma to the point when the noise is not obvious (like in my original photo above), all of them look almost identical; no real advantage in terms of faint stars visibility. So it does look like longer exposures are the answer (and likely switching to ISO 1600 from 3200).
Greg: an interesting patch. It looks like my 50D is not supported? Does it work with intervalometer?
I really have to (re-)learn to compile the code myself. I think I did it long time ago, but forgot the details.
-
(and likely switching to ISO 1600 from 3200).
On a 50D?
ISO 3200 is useless unless you like brightened images on the LCD. All it does is throw away one full stop of dynamic range. You loose one full stop of highlights but gain nothing in the shadows.
http://www.magiclantern.fm/forum/index.php?topic=10111.msg117963#msg117963
http://www.magiclantern.fm/forum/index.php?topic=10111.msg98051#msg98051
-
It looks like my 50D is not supported?
Just find capture_err_time_addr and 50D will take 30 seconds of exposure.
Bulb mode, I don't know, without a camera (50D, 60D, 70D, 7D, 6D, 5D2, 5D3) finding a solution will not be possible.
I checked it two years ago so I could be wrong, but I think 4 x 15s will be like 1 x 30s.
4 frames = 1EV
-
I tinkered a bit with my own 5-years old instructions, and finally managed to compile the Unified ML on my Fedora 22 distro using the following commands:
dnf install gcc-arm-linux-gnu.x86_64 gcc-c++-arm-linux-gnu.x86_64
dnf install arm-none-eabi-gcc-cs-c++.x86_64 arm-none-eabi-gcc-cs.x86_64 nacl-arm-gcc.x86_64
dnf install arm-none-eabi-newlib.noarch
hg clone -r unified https://bitbucket.org/hudson/magic-lantern
cd magic-lantern
make 50D
The last dnf install line was a tricky one - initially I was getting errors about stdint.h, and after some googling I learned that I needed the newlib package to fix that, and it worked.
Now I can try the longer FRSP mods...
-
Hmm, I'm not quite sure how to do the 32s mod.
Alex: I found a couple of "call("FA_CaptureTestImage", job)" lines in silent.c, long_exposure_fix, but I don't see the 20s timeout. I do see this line right before the function:
static uint32_t SLOWEST_SHUTTER = SHUTTER_15s;
which I guess I also have to modify?
Greg: I can't find any reference to capture_err_time_addr in the unified official ML source code...
-
Alex: I found a couple of "call("FA_CaptureTestImage", job)" lines in silent.c, long_exposure_fix, but I don't see the 20s timeout. I do see this line right before the function:
This is a fix for 500D/550D/600D - https://bitbucket.org/hudson/magic-lantern/commits/e5cc80ddd2f4304c1f6481955c83109ccd3bcada
Greg: I can't find any reference to capture_err_time_addr in the unified official ML source code...
Because it never been in official ML source code.
http://www.magiclantern.fm/forum/index.php?topic=12523.msg168411#msg168411
-
FA_CaptureTestImage is a function in Canon firmware.
http://www.magiclantern.fm/forum/index.php?topic=12177.0
capture_err_time_addr from Greg's code is the address of the 20s timeout I was talking about (in Canon firmware).
-
Thanks! Now the million dollar question is how to find the value of capture_err_time_addr for my Canon 50D. Unfortunately my friend google is helpless here (I was looking for an instruction on how to find the value, got zero hits.)
Greg, how did you get the addresses for the cameras you have (500D, 550D, 5D2)? Can I just put a printf statement somewhere to see it on my camera's screen? Or saved to the card as a text file?
-
Tutorial: finding stubs - will be helpful.
You need to find "FA_CaptureTestImage(hJob:%#lx)"
Then find the value of 0x4E20 (20000 ms).
-
Thanks, will look into this.
-
Other discussion moved to here (http://www.magiclantern.fm/forum/index.php?topic=17423.0).
-
Greg and Alex: I disassembled the ROM1, found the line:
ff085a50: e28f209c add r2, pc, #156 ; ff085af4: (435f4146) *"FA_CaptureTestImage(hJob:%#lx)"
but I can't find 0x4E20 (or 0x4e20, 0x04e20, 0x004e20) anywhere. Does it mean my camera uses a different timing parameter (not 20000 ms)? What else can I do here?
EDIT: Okay, I think I have to search for 00004e20. Its first instance is found 20 lines below the above line (FA_CaptureTestImage(hJob:%#lx)):
ff085aa0: e59f106c ldr r1, [pc, #108] ; ff085b14: (00004e20)
and then 30 lines below the previous one:
ff085b14: 00004e20 andeq r4, r0, r0, lsr #28
So which of the two addresses (if any) should be used for capture_err_time_addr - ff085aa0 or ff085b14?
-
0xff085b14 ;)
If this does not work, try 0xff885b14
-
Thanks Greg - I'll give it a try.
EDIT: Actually I didn't realize that "make 50D" doesn't compile modules. Now I did "make all_modules" after "make 50D"; some modules compiled fine, but for silent I got these errors:
silent.c: In function 'silent_pic_take_lv':
silent.c:969:9: error: implicit declaration of function 'PauseLiveView' [-Werror=implicit-function-declaration]
PauseLiveView();
^
silent.c:1014:24: error: implicit declaration of function 'ResumeLiveView' [-Werror=implicit-function-declaration]
if (LV_PAUSED) ResumeLiveView();
^
silent.c: In function 'display_off_if_qr_mode':
silent.c:1083:13: error: implicit declaration of function 'display_off' [-Werror=implicit-function-declaration]
display_off();
^
silent.c: In function 'silent_pic_take_fullres':
silent.c:1228:9: error: implicit declaration of function 'display_on' [-Werror=implicit-function-declaration]
display_on();
^
cc1: some warnings being treated as errors
Should I just remove -Werror-implicit-function-declaration and recompile? Or something is broken here?
-
Something is broken (try "hg diff" to see what changes you have done).
-
The only changes shown by hg diff are the Makefile customizations, and a bunch of changes in silent.c . I just replaced the official silent.c with the Greg's version - I guess that wasn't the appropriate way, and I should have checked out his branch? How can I do that (I am not familiar with hg; I know svn and git).
-
Greg: I did "hg clone -r unified https://bitbucket.org/Gr3g01/magic-lantern-frsp-long-expo", and it compiles okay for 50D (make 50D and make all_modules work okay), without the error messages I saw with the official version, but running "make" or "make install" fails because of some issues with 7D and 1100D branches.
Is it possible to run make install for a specific model (50D)? I guess I can just run "make 50D; make all_modules" and then collect the files I need by hand, but perhaps there is an easier way?
-
make 50D
cd modules
make
cd ..
cd platform/50D.109
make zip
Then you will find a file "magiclantern-Nightly.2016Jun17.50D109.zip" on platform/50D.109 directory.
Unzip this file and copy content to your CF card
-
You can insert the SD card and use: make install -C platform/<cam directory>
This will build the core for the specified platform and all the modules and copy them all and other support files directly to the SD card.
-
josepvm : Thanks! That did the trick!
dmilligan: Thanks. I wasn't sure how to provide the "cam directory" (/media/EOS_DIGITAL), but after some tinkering I simply added it to the Makefile.user.default file, and ran
make install -C platform/50D.109
without issues.
-
No, it doesn't work for me. Summary:
a) When I simply copied the Greg's silent.c to official magic lantern nightly source, added my fix for 50D, and then compiled, everything worked fine (e.f. FRSP at 15s), but when I use FRSP at 30s, it does the 30s exposure, then I get error message "RAW error, falling back to YUV overlays", and them my display dies (I have to remove battery to bring it back to life).
b) When I cloned the whole Greg's branch and compiled for 50D, it kills my camera instantly, the moment I turn the power on - camera shows no signs of life until I switch the card and remove battery.
So something is screwy here. I think I better wait until the Greg's long exposure fix makes it to nightlies.
A question: can RAW video FPS be made to go below 0.125? (That's what my 50D currently have.) Because another way to shoot these long exposure FRSP shots would be to record RAW video at very low FPS.
-
Different results for me.
Greg's branch works Ok on my 50D, no camera locks at all. I have modified silent.c (my version here (https://dl.dropboxusercontent.com/u/44995840/silent.c)) adding an entry for 50D 1.0.9 in silent_init() and assigning capture_err_time_addr = 0xff085b14;
The build works, and I can take silent pictures ... but with a maximum of 16 sec. exposure time. If I try to set a longer exposure (20 s or 30 s) I see a "raw error" message, and the picture is not recorded on CF card. The camera does not freeze, however, I can continue setting a different exposure time and taking more silent pictures.
Tested only with DNG silent pictures, MLV format not tested yet.
The same code built for my 500D works perfectly, I can get 30 sec FRSP and bulb also works with FRSP
-
For 50D, try 0xff885b14.
-
Thanks A1ex. Tested, and it works now, I can take 30 sec. silent pictures.
I have updated the link to my slient.c in my previous post with the correct value.
-
I see that 50D does not have a dedicated bulb mode, only a "Bulb" exposure setting in M mode, so I wonder if Bulb FRSP could be possible in this camera.
Any hint to find "bulb_end_addr" for 50D?
I suppose I need to find "scsBulbEnd" on Canon firmware. I have done it, and I see code like this:
ff079854: e28f20ac add r2, pc, #172 ; ff079908: (42736373) *"scsBulbEnd"
ff079858: e3a01003 mov r1, #3
ff07985c: e20000ff and r0, r0, #255 ; 0xff
ff079860: ebffa8aa bl loc_ff063b10
ff079864: e51f088c ldr r0, [pc, #-2188] ; ff078fe0: (00003208)
Is "bulb_end_addr" related to the value between parentheses (00003208) ? :-\
-
Try to see what the function does (besides printing that message). This particular function is simple enough to understand with pen and paper (for a beginner).
Hint 1: here's a good tutorial: http://www.davespace.co.uk/arm/introduction-to-arm/addressing.html
Hint 2: it's not 00003208, but it's close.
-
josepvm: Thanks for the info. My modded silent.c is exactly like yours, but I do get the RAW write error at 30s exposure. There must be some difference in either the compiling environment, or camera settings. I wonder if the ML version makes a difference? Which version are you using - is it the Greg's branch, or one of nightlies (which one?) with the silent.c replaced by the Greg's version?
EDIT: I just notice that you are using the Greg's branch. It kills my camera for some reason - it must be the compiling environment difference. Which gcc version are you using? What about the arm cross-compiler? Mine are:
gcc: 5.1.1
arm-linux-gnu-gcc: 5.3.1
I think I saw recommendation to use 4.8.x (for both?).
-
Is "bulb_end_addr" related to the value between parentheses (00003208) ? :-\
500D
0x3314 + 0x10 = 0x3324
So try 0x3218 (I'm not 100% sure I don't have 50D ROM).
You can check if the address is correct with 30s exposure and delayed_call.
-
Which gcc version are you using? What about the arm cross-compiler? Mine are:
gcc: 5.1.1
arm-linux-gnu-gcc: 5.3.1
I think I saw recommendation to use 4.8.x (for both?).
I am using gcc 4.8.2 (Ubuntu 14.04 default package, 4:4.8.2-1ubuntu6) and 4.8.4 for the ARM cross-compiler (gcc-arm-none-eabi-4_8-2014q2)
-
500D
0x3314 + 0x10 = 0x3324
So try 0x3218 (I'm not 100% sure I don't have 50D ROM).
You can check if the address is correct with 30s exposure and delayed_call.
Ok, I see, for 500D:
ff07ccf0: e28f20a8 add r2, pc, #168 ; ff07cda0: (42736373) *"scsBulbEnd"
ff07ccf4: e3a01003 mov r1, #3
ff07ccf8: e20000ff and r0, r0, #255 ; 0xff
ff07ccfc: ebffa765 bl loc_ff066a98
ff07cd00: e51f0500 ldr r0, [pc, #-1280] ; ff07c808: (00003314)
ff07cd04: e3a01001 mov r1, #1
ff07cd08: e5801010 str r1, [r0, #16] <------------------
And for 50D:
ff879854: e28f20ac add r2, pc, #172 ; ff879908: (42736373) *"scsBulbEnd"
ff879858: e3a01003 mov r1, #3
ff87985c: e20000ff and r0, r0, #255 ; 0xff
ff879860: ebffa8aa bl loc_ff863b10
ff879864: e51f088c ldr r0, [pc, #-2188] ; ff878fe0: (00003208)
ff879868: e3a01001 mov r1, #1
ff87986c: e5801010 str r1, [r0, #16] <--------------------
So can I assume that "#16" in the last lines is a decimal value, and that's why I should add 0x10 to 00003208 ?
-
Ok, tested, with bulb_end_addr = 0x3218. It works.
So FRSP in bulb mode for 50D is working.
I have updated my "silent.c" file. I repeat the link here (https://dl.dropboxusercontent.com/u/44995840/silent.c)
Update:
----------
It works using Greg's branch. If I put the modified "silent.c" file in the current "unified" branch, the silent module fails to build:
Building module silent...
Updated HGVERSION
[ README ] module_strings.h
[ CC ] silent.o
silent.c: In function 'silent_pic_take_lv':
silent.c:969:9: error: implicit declaration of function 'PauseLiveView' [-Werror=implicit-function-declaration]
PauseLiveView();
^
silent.c:1014:9: error: implicit declaration of function 'ResumeLiveView' [-Werror=implicit-function-declaration]
if (LV_PAUSED) ResumeLiveView();
^
silent.c: In function 'display_off_if_qr_mode':
silent.c:1083:13: error: implicit declaration of function 'display_off' [-Werror=implicit-function-declaration]
display_off();
^
silent.c: In function 'silent_pic_take_fullres':
silent.c:1228:9: error: implicit declaration of function 'display_on' [-Werror=implicit-function-declaration]
display_on();
^
cc1: some warnings being treated as errors
make[3]: *** [silent.o] Error 1
********************************************************
WARNING: module silent failed to build, deleting
********************************************************
-
But the shutter speed should be from M mode.
So the the maximum time 30 seconds.
Now you need to find a way to "Bulb Start" for cameras without Bulb shutter speed in M mode.
-
The 50D has a "bulb" shutter speed setting in M mode, exactly as the 500D. I have tested 45 sec. exposures (using ML bulb timer) and it works.
In other words: the 50D has not a "B" mode in the main dial. The 5D Mk II and 60D have this dedicated "B" mode.
-
I thought it was like 5D2 :o
So in this way should work on the EOSM, 50D, 500D, 550D, 600D, 650D, 700D, 1100D
This can be helpful to finding solutions for other cameras - http://www.magiclantern.fm/forum/index.php?topic=1915.0
-
Here's Greg's silent.c merged with the latest ML core: https://gist.github.com/davidmilligan/6b8f78383a1e11cbecc620874e129cbb
To do this yourself:
hg clone -r unified ssh://hg@bitbucket.org/Gr3g01/magic-lantern-frsp-long-expo
cd magic-lantern-frsp-long-expo
hg pull -b unified ssh://hg@bitbucket.org/hudson/magic-lantern
hg merge
But you get a conflict (easy to fix)
-
Thanks, David !!!
This is my modified "silent.c" based on your version, but with included support for 30 sec. and bulb mode FRSP for the 50D:
silent.c (https://dl.dropboxusercontent.com/u/44995840/ML_silent/silent.c)
Works with the latest unified branch, already tested in camera.
-
Now you need to find a way to "Bulb Start" for cameras without Bulb shutter speed in M mode.
This one is tricky, since the FA_CreateTestImage gets the shutter setting from property 0x80000005 (PROP_SHUTTER). On 60D, in BULB mode, PROP_SHUTTER has the previous value from M mode.
Once in BULB mode, the 60D no longer accepts any changes to PROP_SHUTTER.
If you try to set PROP_SHUTTER to SHUTTER_BULB = 12 from M mode, the change is refused by Canon code.
I guess the behavior is similar on other cameras that have a dedicated BULB mode.
Patching the shutter speed in the structure returned by FA_CreateTestImage might work.
run_test:ff09e1ac:90:16: hJob(0x43b00070)(tv=0x88,av=0x24,iso=0x48)
...
ShootCaptu:ff0848b4:93:16: ->FA DARK_MEM1 iso:0x48,tv:0x88,av:0x24,tp:153,po:185
-
60D:
void* job = (void*) call("FA_CreateTestImage");
ASSERT(*(uint8_t*)(job + 0x78) == prop_shutter);
*(uint8_t*)(job + 0x78) = SHUTTER_BULB;
delayed_call(bulb_time * 1000, bulb_stop, 0);
call("FA_CaptureTestImage", job);
run_test:ff09e1ac:90:16: hJob(0x43b00070)(tv=0x88,av=0x24,iso=0x48)
...
ShootCaptu:ff0848b4:93:16: ->FA DARK_MEM1 iso:0x48,tv:0xc,av:0x24,tp:153,po:185
...
ShootCaptu:ff086138:93:03: scsVdInterrupt
...
ShootCaptu:ff086138:93:03: scsVdInterrupt
...
ShootCaptu:ff086138:93:03: scsVdInterrupt
ShootCaptu:ff086188:93:03: Accumulation Stop
ShootCaptu:ff0861c4:93:03: Last VD Count
:)
-
5D2, 500D, 50D :
(job + 0x64) // not tested
Easy code to find the register if you have a camera :
static void run_test()
{
msleep(500);
console_show();
void* job = (void*) call("FA_CreateTestImage");
FILE* f = FIO_CreateFile("FRSP.LOG");
my_fprintf(f, "Tv val = 0x%x\n", lens_info.raw_shutter);
my_fprintf(f, "Av val = 0x%x\n", lens_info.raw_aperture);
my_fprintf(f, "ISO val = 0x%x\n\n", lens_info.raw_iso);
for (int i = 0; i < 1000; i++)
{
if(lens_info.raw_shutter == *(uint8_t*)(job + i))
{
printf("FA_CreateTestImage Tv Addr : 0x%x\n", i);
}
if (f)
{
my_fprintf(f, "Addr = 0x%03x Val = 0x%x\n", i, *(uint8_t*)(job + i));
}
}
if (f)
{
FIO_CloseFile(f);
}
call("FA_DeleteTestImage", job);
printf("Done.\n");
}
-
FRSP Bulb 5D2 - https://bitbucket.org/Gr3g01/magic-lantern-frsp-long-expo/commits/7099753deeed50d3c10c36029faa1303640e3943?at=unified
(not tested)
-
Hello,
Been trying the full resolution silent pictures for the 1st time and I've got few questions that I need some help with.
*1st @a1ex said in one of the comments that we can read the dng files if I remember well, but I wasn't able to do so even if the module was activated. I'm probably doing something wrong.
*I couldn't make it work with intervalometer, any help would be great! And also there was something that I didn't get well Alex advise us to do 10-15 sec of interval coz it's slow to save the photo in dng, but it doesn't take that long it takes between 2-3 seconds (Canon 6d) is it for security? The way I tried it is taking one picture after another manual by pressing the shutter twice whenever I get black screen... It that ok?
Thanks in advance for ur help
-
*1st @a1ex said in one of the comments that we can read the dng files if I remember well, but I wasn't able to do so even if the module was activated. I'm probably doing something wrong.
Link to a1ex' comment would be just fine. I have no idea what you are trying to do. Please explain in detail.
*I couldn't make it work with intervalometer, any help would be great! And also there was something that I didn't get well Alex advise us to do 10-15 sec of interval coz it's slow to save the photo in dng, but it doesn't take that long it takes between 2-3 seconds (Canon 6d) is it for security? The way I tried it is taking one picture after another manual by pressing the shutter twice whenever I get black screen... It that ok?
Which settings do you use for intervalometer? By default Intervalometer and FRSP are configured to use the same trigger (half press shutter) which won't work that well (or at all). Try using "Leave menu" Intervalometer trigger instead.
-
Which settings do you use for intervalometer? By default Intervalometer and FRSP are configured to use the same trigger (half press shutter) which won't work that well (or at all). Try using "Leave menu" Intervalometer trigger instead.
Great Yeah that worked perfectly! Thank you
Link to a1ex' comment would be just fine. I have no idea what you are trying to do. Please explain in detail.
I meant if we wanna see the dng files we took, is it possible to visualize them in file manager?
-
MLV only AFAIK.
-
MLV only AFAIK.
Yeah that's what I thought. Found the post from a1ex
http://www.magiclantern.fm/forum/index.php?topic=12523.msg162777.msg#162777
-
MLV only AFAIK.
Ah it worked it just takes a lot of time to load it. :)
Anws thanks for ur help Walter
-
Good day! I have a small question! When shooting silent pictures image badly overexposed. But the question is If it's an image directly from the sensor then on the picture, no pink dots focus 650D. To remove not very convenient, But the sun only at f/22 and 1/4000 shutter, which is not very convenient as the chapel for the 650d. Is there any ways to solve this inconvenience?!
-
I think the best solution is a variable ND filter.
-
@Dionisgr
Below are notes that I have made for myself with regard to FRSP. They work well enough for me so that I don't have to relearn the basics whenever I decide to use this function.
Also a google search will list some useful tutorial videos done by other ML users.
(F)ull (R)esolution (S)ilent (P)ictures
Notes
--------------------------
Used to take full resolution pictures without actuating the cameras' mechanical shutter mechanism. Excellent for time lapse photography using the advanced intervalometer
Only suitable for shutter speeds of 1/30 second or slower.
Exposure is a gradient i.e.: darker at the top to brighter at the bottom. This may be beneficial where there is a bright sky. Can be fixed easily using a gradient filter in Photoshop or similar application.
Capturing images into an MLV format file will require additional post processing steps vs individual DNG files.
Pre-requisites
--------------------------
A variable neutral density filter
A tripod or similar sturdy camera mount
Camera Settings
--------------------------
Camera Mode Dial: set to M
Shutter Speed: 1/30s or slower
Aperture: As required for desired depth of field
ETTR: Off
Dual_ISO: Off
Live-View: Enabled
FRSP Module: Enabled
Silent Mode: Full-res
Slit-Scan mode: Top-->Bottom (default, probably not relevant for FRSP)
File Format: DNG for individual STILL images
MLV to capture images into a raw MLV video file
Lens Setting
--------------------------
Auto Focus Switch: Set to (M)anual
Stability Control: Off
V/Neutral Density Filter: Attached and adjusted as necessary to obtain the correct exposure.
As close to 0.0ev and no clipping as possible (as per histogram post visible post shot).
Process
---------------------------
Frame the subject as required.
Via the joystick.
Toggle the square focus box over the main object to be in focus. Use 5x/10x zoom to aid in establishing a correct focus via the manual focus ring on the lens.
Take some experimental shots and after each, adjust the ND filter until the histogram displays as close to 0.0ev and zero clipping as possible.
Set the intervalometer as desired. Activated upon exiting the ML menus. Remember to allow time for the image to be saved when determining the image frequency e.g.: exposure time + 1 second minimum.
If using the advance key frames, more thought will have to go into the time between shots settings if the exposure time time is lengthened.
To assist with flicker removal in time-lapses try enabling the Post Deflicker function.
Hope it helped.
-
@Ottoga
;)Thank you so much!
-
If you read some pages behind you'll see tha some lenses don't actually close the aperture and only shoot at max aperture ( say if it can do f/2 and you setup f8, when it takes the picture it will be at f/2), hence overexposure.
Do test by looking at the lens to see if it actually closes as it should, say test with f/22.
-
These tests with the aperture I had. Like all showed the same even if you close the aperture and open the contact lens! ND 4 filter sorry one.
-
It may be that related to electric shutter :
ShootCaptu:ff07ba7c:93:03: EShutCapture
ShootCaptu:00070d90:00:00: *** SCSEshutState: (0) --3--> (1) ff07ce98 (x=781128 z=0 t=0)
ShootCaptu:ff07ced0:93:03: scsCapReadyEshut
ShootCaptu:00070f48:00:00: *** RegisterHead1InterruptHandler(0x0, 0xff07ce54 "EshutterDone(%d)", &"ShootCapture"), from ff07cf04
**INTERRUP:ff07ce78:93:03: EshutterDone(15925)
ShootCaptu:00070d90:00:00: *** SCSEshutState: (1) --12--> (2) ff07d1c8 (x=781128 z=0 t=0)
ShootCaptu:ff07d200:93:03: scsEshutDone
ShootCaptu:00070d90:00:00: *** SCSEshutState: (2) --13--> (4) ff07d2a0 (x=781128 z=0 t=0)
To force the camera to work in this mode :
*(uint8_t*)(job + 0x64 + 0x24) = 1;
*(uint8_t*)(job + 0x64 + 0x25) = 1;
Exposure looks the same gradient is slightly stronger.
-
I ran into a issue recently with doing timelapse on ML using Silent pictures feature to MLV.
I specifically use this feature as to not wear out my shutter and it reduces flicker. Its brilliant!
I use the 5dmarkIII firmware 1.2.3 I set my exposure then run the intervolameter feature.
It seems there is a coding error w/1.2.3 running the latest build. because the exposure automatically changes and the images is over exposure.
by a lot! resulting in a unusuable image.
I downgraded the firmware to 1.1.3 and use the most current ml build. and i cnat reproduce the issue. which leads me to believe there is something up with that ML build.
The reason i bring it up is sometimes i use an external recorder so i need the HDMI output that 1.2.3 offers.
If this isnt your area of expertise if you could help me get this to the right hands thatll be great.
Thanks!
-
Read the first post (esp. the "Limitations" section).
What shutter speed did you use?
Were you shooting the same scene with the same lighting with 1.1.3 and 1.2.3?
-
Any new idea regarding the "broken" lenses that don't actually trigger the correct apperture in FRSP? :(
-
Try 0xff085b14
If this does not work, try 0xff885b14
How exactly did you reach this idea?
Is the offset 0x800000 general for all cameras?
-
OK let's continue with 5D3.113. Based on the above description where to look:
ff14aab0: e28f2f86 add r2, pc, #536 ; ff14acd0: (42736373) *"scsBulbEnd"
ff14aab4: e20000ff and r0, r0, #255 ; 0xff
ff14aab8: e3a01003 mov r1, #3
ff14aabc: eb3aec33 bl loc_5b90
ff14aac0: e51f0460 ldr r0, [pc, #-1120] ; ff14a668: (00025280)
ff14aac4: e3a01001 mov r1, #1
ff14aac8: e5801014 str r1, [r0, #20]
and
ff1bf440: e28f20dc add r2, pc, #220 ; ff1bf524: (435f4146) *"FA_CaptureTestImage(hJob:%#lx)"
...
ff1bf4b8: e51f1168 ldr r1, [pc, #-360] ; ff1bf358: (00004e20)
I already tried the following with no success:
bulb_end_addr = 0x25294;
capture_err_time_addr = 0xff1bf358; // or 0xff9bf358
frsp_tv_addr = 0x64; // or 0x78 as indicated by A1ex for 60D
BTW memory locations in the code look prety similar to 60D.111
Any feedback what could be wrong?
-
5D3.123
bulb_end_addr -> 0x25190 + 0x14 = 0x251A4
capture_err_time_addr -> 0xFF1C1FACfrsp_tv_addr -> finding in the ROM may take some more time, try this - http://www.magiclantern.fm/forum/index.php?topic=12523.msg168625#msg168625
I do not have a Canon camera and that is why I can't focus on further development.
-
Is anybody successful with dedicated BULB dial?
Silent module in fullres seems to be active only in shooting_mode == SHOOTMODE_M
-
---
if (shooting_mode != SHOOTMODE_M)
{
error_msg = "Manual (M) mode is required.";
goto err;
}
+++
if (shooting_mode != SHOOTMODE_M && shooting_mode != SHOOTMODE_BULB)
{
error_msg = "Manual (M) or Bulb (B) mode is required.";
goto err;
}
-
Hi all... just started playing with this on a 7d this week. Great feature. I'm doing time lapse with it. My question is what is the maximum lens focal length folks are able to use at 1/30 with a good tripod?
My 17-55 works excellent as does my 100mm macro. My super sharp 400mm F5.6 did not work too well at 1/30. Focus is off just enough to bug me. Speaking of bugs... A gnat farting near my 400mm at 1/30 I think would cause blur.
Also wanted to add i'm able to do 6s intervals with lexar 800x ( 120mbs ). Was getting 6-8 on 533x. So this is real usable.
Thanks for ML and all its great features...
NS
-
A good tripod standing on a non-vibrating piece of ground without disturbance by wind will pretty much be stable forever (almost).
Maybe you should evaluate another tripod or add some piece to support and stabilize your lens.
Feininger been there and done this: http://66.media.tumblr.com/tumblr_lbzy6qdAf21qcqt7m.jpg
-
Dear all,
is it possible to use FRSP bulb mode with EOS 700D?
I need up to 5 minutes exp time for astrophotography
I'm able to compile but I don't know if the actual code work with this model.
Thanks a lot for your hard job.
-
Dear all,
is it possible to use FRSP bulb mode with EOS 700D?
Yes (probably), but "capture_err_time_addr" and "bulb_end_addr" addresses need to be found for 700D, disassembling a ROM dump from your camera.
See:
http://www.magiclantern.fm/forum/index.php?topic=12523.msg168467#msg168467
http://www.magiclantern.fm/forum/index.php?topic=12523.msg168553#msg168553
And: Tutorial: finding stubs (http://www.magiclantern.fm/forum/index.php?topic=12177.msg117735#msg117735)
-
I have found them for you:
700D
------
capture_err_time_addr = 0xff1e1a38
bulb_end_addr = 0x24960
Try these values. I have not checked them ( I do not own a 700D), but I think they are correct:
"FA_CaptureTestImage(hJob:%#lx)":
ff1e19f0: 435f4146 cmpmi pc, #-2147483631 ; 0x80000011
ff1e19f4: 75747061 ldrbvc r7, [r4, #-97]! ; 0x61
ff1e19f8: 65546572 ldrbvs r6, [r4, #-1394] ; 0x572
ff1e19fc: 6d497473 cfstrdvs mvd7, [r9, #-460] ; 0xfffffe34
ff1e1a00: 28656761 stmdacs r5!, {r0, r5, r6, r8, r9, sl, sp, lr}^
ff1e1a04: 626f4a68 rsbvs r4, pc, #104, 20 ; 0x68000
ff1e1a08: 6c23253a cfstr32vs mvfx2, [r3], #-232 ; 0xffffff18
ff1e1a0c: 00002978 andeq r2, r0, r8, ror r9
"sht_FA_ReleaseStart":
ff1e1a10: 5f746873 svcpl 0x00746873
ff1e1a14: 525f4146 subspl r4, pc, #-2147483631 ; 17f1e1a0b: (???)
ff1e1a18: 61656c65 cmnvs r5, r5, ror #24
ff1e1a1c: 74536573 ldrbvc r6, [r3], #-1395 ; 0x573
ff1e1a20: 00747261 rsbseq r7, r4, r1, ror #4
"sht_FA_ReleaseData":
ff1e1a24: 5f746873 svcpl 0x00746873
ff1e1a28: 525f4146 subspl r4, pc, #-2147483631 ; 17f1e1a1f: (???)
ff1e1a2c: 61656c65 cmnvs r5, r5, ror #24
ff1e1a30: 61446573 hvcvs 18003 ; 0x4653
ff1e1a34: 00006174 andeq r6, r0, r4, ror r1
ff1e1a38: 00004e20 andeq r4, r0, r0, lsr #28 < --------------
loc_ff1e1a3c:
ff1e1a3c: 0000017b andeq r0, r0, fp, ror r1
ff1e1a40: ff1e149c ; <UNDEFINED> instruction: 0xff1e149c
"FA_CaptureTestImage Fin":
So capture_err_time_addr = 0xff1e1a38
And:
ff14af18: e28f2f81 add r2, pc, #516 ; ff14b124: (42736373) *"scsBulbEnd"
ff14af1c: e20000ff and r0, r0, #255 ; 0xff
ff14af20: e3a01003 mov r1, #3
ff14af24: eb3ae28c bl loc_395c
ff14af28: e51f0b30 ldr r0, [pc, #-2864] ; ff14a400: (00024950) <--------
ff14af2c: e3a01001 mov r1, #1
ff14af30: e5801010 str r1, [r0, #16] <------------------------------------
ff14af34: e5900004 ldr r0, [r0, #4]
ff14af38: e8bd8010 pop {r4, pc}
so bulb_end_addr = 0x24950 + 0x10 = 0x24960
-
I have a 700D.114 and there the address of capture_err_time_addr is different to the value from @josepvm:
capture_err_time_addr = 0xff1e1dd8
The address of
bulb_end_addr is the same as @josepvm posted = 0x24960
In a first short test I implemented only the capture_err_time_addr
and it works. Now up to 32s are possible.
Bulb mode I have not yet tested.
The code of my ROM1 is:
"FA_CaptureTestImage(hJob:%#lx)":
ff1e1d90: 435f4146 cmpmi pc, #-2147483631 ; 0x80000011
ff1e1d94: 75747061 ldrbvc r7, [r4, #-97]! ; 0x61
ff1e1d98: 65546572 ldrbvs r6, [r4, #-1394] ; 0x572
ff1e1d9c: 6d497473 cfstrdvs mvd7, [r9, #-460] ; 0xfffffe34
ff1e1da0: 28656761 stmdacs r5!, {r0, r5, r6, r8, r9, sl, sp, lr}^
ff1e1da4: 626f4a68 rsbvs r4, pc, #104, 20 ; 0x68000
ff1e1da8: 6c23253a cfstr32vs mvfx2, [r3], #-232 ; 0xffffff18
ff1e1dac: 00002978 andeq r2, r0, r8, ror r9
"sht_FA_ReleaseStart":
ff1e1db0: 5f746873 svcpl 0x00746873
ff1e1db4: 525f4146 subspl r4, pc, #-2147483631 ; 17f1e1dab: (???)
ff1e1db8: 61656c65 cmnvs r5, r5, ror #24
ff1e1dbc: 74536573 ldrbvc r6, [r3], #-1395 ; 0x573
ff1e1dc0: 00747261 rsbseq r7, r4, r1, ror #4
"sht_FA_ReleaseData":
ff1e1dc4: 5f746873 svcpl 0x00746873
ff1e1dc8: 525f4146 subspl r4, pc, #-2147483631 ; 17f1e1dbf: (???)
ff1e1dcc: 61656c65 cmnvs r5, r5, ror #24
ff1e1dd0: 61446573 hvcvs 18003 ; 0x4653
ff1e1dd4: 00006174 andeq r6, r0, r4, ror r1
ff1e1dd8: 00004e20 andeq r4, r0, r0, lsr #28
ff1e1ddc: 0000017b andeq r0, r0, fp, ror r1
ff1e1de0: ff1e183c ; <UNDEFINED> instruction: 0xff1e183c
"FA_CaptureTestImage Fin":
For BulbEnd: (only the code addresses are different, all other is equal)
ff14b0cc: e28f2f81 add r2, pc, #516 ; ff14b2d8: (42736373) *"scsBulbEnd"
ff14b0d0: e20000ff and r0, r0, #255 ; 0xff
ff14b0d4: e3a01003 mov r1, #3
ff14b0d8: eb3ae21f bl loc_395c
ff14b0dc: e51f0b30 ldr r0, [pc, #-2864] ; ff14a5b4: (00024950)
ff14b0e0: e3a01001 mov r1, #1
ff14b0e4: e5801010 str r1, [r0, #16]
ff14b0e8: e5900004 ldr r0, [r0, #4]
ff14b0ec: e8bd8010 pop {r4, pc}
-
For EOS M:
capture_err_time_addr = 0xff1df1fc
bulb_end_addr = 0x3F300
30 sec. FRSP and bulb FRSP are working in this little cam ;)
I have updated the "silent.c (https://dl.dropboxusercontent.com/u/44995840/ML_silent/silent.c)" version I posted in this thread some time ago. Now with bulb FRSP working for 500D, 50D and EOS M. And also enabled for 700D, but not tested. This file is prepared to be used with current ML unified branch.
It's based on Greg's branch, and merged with unfied by Dmilligan (see previous posts in this thread). Now I have added the addresses I found for EOS M and 700D.
-
Thanks a lot josepvm!!
I'll try to compile and use it.
You are great guy!
-
I have a 700D.114 and there the address of capture_err_time_addr is different to the value from @josepvm:
capture_err_time_addr = 0xff1e1dd8
The address of
bulb_end_addr is the same as @josepvm posted = 0x24960
Oh sorry, my fault, the 700D ROM1 copy I was looking at is 1.1.1, I didn't notice it was not the same as current builds for 700D.
I have updated the "silent.c" file I posted before with your correct values, It should work now.
-
josepvm,
Tried the last silent.c that you share including EOS 700D ..... all is working!!
using intervalometer, bulb 60 s
FRSP BULB MODE is ok
saving DNG is ok
saving MLV is ok
This could be the best feature for astrophotography toghether intervalometer because we save the shutter a lot. We take for just 1 final picture up to 100 x 120s shots (light+ dark + flat +darkflat+bias frame).
Now I will test the reliability, especially saving in MLV format
Thanks again
-
Correct register addresses please add comment - https://bitbucket.org/hudson/magic-lantern/pull-requests/735/frsp-bulb-support/diff
This will help merge in the future.
-
I have made some more tweaking, to get the module working also in dedicated bulb mode:
@@ -145,5 +145,5 @@
MENU_APPEND_VALUE(", DNG");
}
- if (silent_pic_mode == SILENT_PIC_MODE_FULLRES && (shooting_mode != SHOOTMODE_M || is_movie_mode()))
+ if (silent_pic_mode == SILENT_PIC_MODE_FULLRES && ((shooting_mode != SHOOTMODE_M && shooting_mode != SHOOTMODE_BULB) || is_movie_mode()))
{
@@ -149,5 +149,5 @@
{
- MENU_SET_WARNING(MENU_WARN_NOT_WORKING, "Full-res pictures only work in Manual (M) photo mode.");
+ MENU_SET_WARNING(MENU_WARN_NOT_WORKING, "Full-res pictures only work in Manual (M) or Bulb (B) photo mode.");
}
silent_pic_check_mlv(entry, info);
@@ -1175,5 +1175,5 @@
char* error_msg = 0;
- if (shooting_mode != SHOOTMODE_M)
+ if (shooting_mode != SHOOTMODE_M && shooting_mode != SHOOTMODE_BULB)
{
@@ -1179,6 +1179,6 @@
{
- error_msg = "Manual (M) mode is required.";
- goto err;
+ error_msg = "Manual (M) or Bulb (B) mode is required.";
+ goto err;
}
if (prop_iso == 0 || prop_shutter == 0)
@@ -1242,7 +1242,7 @@
* and creates a "job" object (CreateSkeltonJob)
*/
void* job = (void*) call("FA_CreateTestImage");
-
+
if (prop_shutter == SHUTTER_BULB || (shooting_mode == SHOOTMODE_BULB && frsp_tv_addr))
{
/* some cameras reset the cache fake after FRSP, we need it again */
@@ -1257,8 +1257,19 @@
/* cameras with SHOOTMODE_BULB need fake SHUTTER_BULB */
if (shooting_mode == SHOOTMODE_BULB && frsp_tv_addr)
{
- ASSERT(*(uint8_t*)(job + frsp_tv_addr) == prop_shutter);
- *(uint8_t*)(job + frsp_tv_addr) = SHUTTER_BULB;
+ printf("job: %x\n", job);
+ printf("prop_shutter: 0x%x\n", prop_shutter);
+
+ for (int i = 0; i < 256; i++)
+ {
+ if(prop_shutter == *(uint8_t*)(job + i))
+ {
+ printf("FA_CreateTestImage Tv Addr : 0x%x\n", i);
+ }
+ }
+
+ ASSERT(*(uint8_t*)(job + frsp_tv_addr) == prop_shutter);
+ *(uint8_t*)(job + frsp_tv_addr) = SHUTTER_BULB;
}
delayed_call(bulb_time * 1000, bulb_stop, 0);
@@ -1281,7 +1292,7 @@
* and available from RAW_PHOTO_EDMAC (defined in raw.c)
*/
call("FA_CaptureTestImage", job);
-
+
int t1 = get_ms_clock_value();
int capture_time = t1 - t0;
@@ -1481,5 +1492,5 @@
if (!silent_pic_enabled)
return 0;
- /* fullres silent pics only work in M mode,
+ /* fullres silent pics only work in M or B mode,
* and they may screw up things if triggered while recording. */
@@ -1485,5 +1496,5 @@
* and they may screw up things if triggered while recording. */
- if (silent_pic_mode == SILENT_PIC_MODE_FULLRES && (shooting_mode != SHOOTMODE_M || is_movie_mode()))
+ if (silent_pic_mode == SILENT_PIC_MODE_FULLRES && ((shooting_mode != SHOOTMODE_M && shooting_mode != SHOOTMODE_BULB) || is_movie_mode()))
return 0;
static int silent_pic_countdown;
@@ -1664,6 +1675,14 @@
frsp_tv_addr = 0x64; // cameras with SHOOTMODE_BULB need fake SHUTTER_BULB
}
+ if (is_camera("5D3", "1.1.3"))
+ {
+ bulb_end_addr = 0x25294;
+ capture_err_time_addr = 0xFF9BF358;
+ frsp_tv_addr = 0x78; // cameras with SHOOTMODE_BULB need fake SHUTTER_BULB
+ }
+
+
/* cache fake "ERROR Take Semaphore" time in "FA_CaptureTestImage" */
/* 20 seconds to (15 + 1) minutes */
if (bulb_end_addr && capture_err_time_addr)
But on my 5D3.113, it fails to find (http://www.magiclantern.fm/forum/index.php?topic=12523.msg168625#msg168625 (http://www.magiclantern.fm/forum/index.php?topic=12523.msg168625#msg168625)) correct frsp_tv_addr (both bulb timer ON and OF).
Therefore it always ends up with ASSERT.
-
Correct register addresses please add comment - https://bitbucket.org/hudson/magic-lantern/pull-requests/735/frsp-bulb-support/diff
This will help merge in the future.
Added addresses for EOS M and 700D:
https://bitbucket.org/Gr3g01/magic-lantern-frsp-long-expo/pull-requests/1/silentc-added-addresses-for-bulb-frsp-on/diff
-
josepvm,
Tried the last silent.c that you share including EOS 700D ..... all is working!!
Ibirru, I have updated the file again. Please, download the new version and try it again.
Previously I enabled "long_exposure_fix_enabled" for the new cams, and I see now that this is needed only for 500D, 550D and 600D.
EOS M works fine with this option disabled.
-
It works also in 700D. Just compiled and running. :)
-
Some progress with dedicated BULB dial like 60D, 5D3 etc...with help of Greg.
Extending search range for frsp_tv_shutter to 1000 instead of 256 shows two offsets for 5D3.113 - 0x280 and 0x282.
Therefore:
-static uint8_t frsp_tv_addr = 0;
+static uint16_t frsp_tv_addr = 0;
Using 0x280 enables the bulb exposure (3 min max tested), but the image does not get saved onto the card, for some reason.
-
Updated easy code to find registry tv addr - http://www.magiclantern.fm/forum/index.php?topic=12523.msg168625#msg168625
0x0 // Tv1
0x1 // Av1
0x2 // Tv2
0x3 // Av2
0x4 // ISO
You can try to use Tv1 and Tv2.
(0x280 and 0x282)
FRSP related infos - http://www.magiclantern.fm/forum/index.php?topic=14363.0
Look at struct shootParm.
-
ok, solved.
Image did not save due to "stdev too large" message (failed autodetect_black_level()), for which I have no clue. Dark images do not have this problem.
Finally working bulb FRSP 5D3.113:
bulb_end_addr = 0x25294;
capture_err_time_addr = 0xFF1BF358;
frsp_tv_addr = 0x280;
Entire DIFF you find on https://bitbucket.org/milank/ml-frsp-long-expo/branch/BULB%20dial%20test#diff (https://bitbucket.org/milank/ml-frsp-long-expo/branch/BULB%20dial%20test#diff).
-
In raw.c, you can define RAW_DEBUG for more verbose messages, and RAW_DEBUG_DUMP to save the raw file that's causing issues.
May be related to this: www.magiclantern.fm/forum/index.php?topic=17579
-
I have put raw debug on:
#define RAW_DEBUG /* define it to help with porting */
#define RAW_DEBUG_DUMP /* if you want to save the raw image buffer and the DNG from here */
#define RAW_DEBUG_BLACK /* for checking black level calibration */
The console.log after two BULB shots (1min and 25s):
...
raw update from shoot_task
Photo raw buffer: 86028f8 (5936x3950)
Skip left:138 right:2 top:80 bottom:0
Resolution changed: 0x0 -> 5936x3950
active area: x=138..5934, y=80..3950
lv2raw sx:8203 sy:8221 tx:152 ty:88
raw2lv test: (-1,-1) - (722,482)
should be: (0,0) - (720,480)
raw2bm test: (-1,-1) - (722,482)
should be: (0,0) - (720,480)
bm2raw test: (152,88) - (5919,3941)
should be: (138,80) - (5934,3950)
Black check 1/5: 8316…0.00, ref 2047…6.75, delta=6269
Black 1/5: mean too different (8316, ref 2047…6.75)
Save configs...
raw update from shoot_task
Photo raw buffer: 86028f8 (5936x3950)
Skip left:138 right:2 top:80 bottom:0
active area: x=138..5934, y=80..3950
lv2raw sx:8203 sy:8221 tx:152 ty:88
raw2lv test: (-1,-1) - (722,482)
should be: (0,0) - (720,480)
raw2bm test: (-1,-1) - (722,482)
should be: (0,0) - (720,480)
bm2raw test: (152,88) - (5919,3941)
should be: (138,80) - (5934,3950)
Black check 1/5: 7980…382.40, ref 2047…6.77, delta=5933
Black 1/5: mean too different (7980, ref 2047…6.77)
Save configs...
If I try to save the DNG for debug purposes (using if(0) => if(1)), I receive Error 70.
-
Ah, SRM memory issues. The other dumping routine does not use an extra copy, so that one should be fine. If it still doesn't work, I'll look into it.
BTW, in console.log, the "…" is actually the +/- sign (ML uses a non-standard character set).
-
the same test with MLV is similar:
....
raw update from shoot_task
Photo raw buffer: 86028f8 (5936x3950)
Skip left:138 right:2 top:80 bottom:0
active area: x=138..5934, y=80..3950
lv2raw sx:8203 sy:8221 tx:152 ty:88
raw2lv test: (-1,-1) - (722,482)
should be: (0,0) - (720,480)
raw2bm test: (-1,-1) - (722,482)
should be: (0,0) - (720,480)
bm2raw test: (152,88) - (5919,3941)
should be: (138,80) - (5934,3950)
Black check 1/5: 8173…347.29, ref 2047…6.87, delta=6126
Black 1/5: mean too different (8173, ref 2047…6.87)
Save configs...
Enabled DNG diag output results in the same error 70:
ASSERT: GetMemoryAddressOfMemoryChunk( GetFirstMemChunk( pMem1AllocateListItem->hMemSuite ) ) == pMessage->pAddress
at SrmActionMemory.c:1505, task RscMgr
lv:0 mode:4
....
srm_malloc_suite(1)...
srm buffer #1: 42000064
srm_malloc_suite => 10edb0
srm_free_suite(10edb0)
srm_malloc_suite(0)...
-
Hoping someone can tell me what I'm doing wrong. I've read through several pages of this thread and some others but no luck. I've got a Canon 6D on the latest nightly (Nightly.2016Sep16.6D116). I've enabled silent pictures, mlv_rec, have a interv. of 15s, and outputting full res to MLV, shutter of 1s, shooting in live mode. It seems that the files are getting corrupted as MLVMystic, mlv_dump, MLVBrowseSharp are unable to read them. MLVViewSharp is able to but periodically crashes trying to read them (also I've noticed the brightness increasing from one image to the next when it does work - might be a separate issue). I tried choosing DNG in Silent Picture (with the same settings as above) and that had no issue (all were of the same brightness level as well). Am I missing something about the MLV container or a setting perhaps?
-
Felt this was worth noting in regards to FRSP from a 1200D -- http://www.magiclantern.fm/forum/index.php?topic=12627.msg173256#msg173256
-
Hi! My 5D3 with fw 1.1.3 /latest nightly keep failing on raw when making Silent pictures with lenght more than approx 1,5 -> 16 seconds (varies a bit). Message is "Raw error, falling back to YUV overlays". Bug or me? ;)
-
Likely a hot pixel, see http://www.magiclantern.fm/forum/index.php?topic=17579.0.
A DNG might help diagnosing it.
-
One white and one black picture - Don't know what's best :)
https://1drv.ms/f/s!AoqojSQR7nORjmAwLqgQp3NIwj7O
-
Hi,
when I shoot silent MLV with intervalometer, every picture is in individual MLV file.
How to shoot silent with intervalometer into one mlv file?
It's easier to decompress to dng files.
(shooting mlv without intervalometer save every frame in one mlv)
-
Why not shooting DNG in the first place?
-
When I shooting in DNG, it take some time to convert picture in camera.
MLV save frames faster.
-
when I shoot silent MLV with intervalometer, every picture is in individual MLV file.
Steps to reproduce?
(just tried on latest nightly, on both simple and full-res modes - each timelapse sequence is saved in a single MLV file)
-
I copy silent.mo and adv_int.mo from nightly 30 march to sd card and problem is still.
My build is raw_video_10bit_12bit_02apr.
Maybe i'ts bug of this build.
-
I'm surelly missing something so bear with me. When I select the experimental full res mode the half shutter press does nothing. How do I take the photo? I've tried the other buttons but no luck.
-
Took a look at the code and the only code path that could result in "does nothing" would be if you start from some Canon dialog that does not go away on half-shutter (for example, the card full message) - very unlikely. Or, the trivial solution - if the silent pic option is turned off.
All other cases (incorrect shooting mode, incorrect settings, out of memory, autofocus and so on) should result in some error message (either in menu or on the screen), or at least some sort of screen activity.
That means... http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
-
Sorry A1ex, I was trying to solve different raw workflow things when I decided to try the silent module. I never thought it was a bug, just a stupid mistake of mine that someone else could catch fast, and it fact it is. I’m still not very familiar with the 5d3, the live view options confuse me, I was not in “photo mode”. It works perfectly.
Was this discovered recently with the 4k advancements? Or do we had this for a long time? Incredible feature for stills on set and a lot of other situations. It’s not easy to find a silent camera out there even mirrorless.
-
In this case, you should get a warning message in the menu (so the behavior should be different from "does nothing").
The post dates appear to be valid. The 4K branch enables short exposures, but the regular version (at long exposures) was there since... the first post on this thread.
-
FRSP continuous :
You need nd filter simulation?
How does it work?
The camera take silent pictures in continuous mode, for example, Tv 0.5s, 4 frames :
0.5 + 0.5 + 0.5 + 0.5 = 2s
We can average frames in mlv_dump.
The movement of water/cloud will be like two seconds of exposure.
The image will 1EV more DR.
4 frames -> 1EV
16 frames -> 2EV
64 frames -> 3EV
Writing speed must be shorter than the exposure time.
(http://s2.postimg.org/peowxz1rt/menu.gif)
one vs 20 frames :
(http://s27.postimg.org/silu76rxf/longexpo.jpg)
Dual ISO alternately (100/1600, 1600/100, 100/1600...) :
I've never been convinced by the dual iso (loss of detail).
I think it should be a good solution, but I'm not 100% sure about because I do not tested in the landscape.
(http://s18.postimg.org/ahv6mn961/dual_iso.jpg)
So in theory we get a huge DR.
100/1600 on the 500D give 2.2EV more.
If you averaged 16 frames, 2EV more DR.
Dual iso + 16 frames, give 4.2EV more for 500D :o
Tree :
(http://s2.postimg.org/mvrs4h12x/dualiso.jpg)
Interior :
(http://s7.postimg.org/me3xmz2ln/dualiso2.jpg)
Hi Greg,
Do this work on 5D3? I can't find anything in the forum...
-
Sorry for the repost (was trying to find this thread earlier, but only found the 14bit silent picture thread, so I started my own thread, here: http://www.magiclantern.fm/forum/index.php?topic=19679.msg185345#msg185345 (http://www.magiclantern.fm/forum/index.php?topic=19679.msg185345#msg185345))
But this is what I was driving at:
is it possible to to separate the functionality of the liveview feature into "that which enables silent picture" and "that which must move the mirror away from the eyepiece?" eyepiece?"
Thanks.
-
Guys, I'm sorry for being obviously dumb or something like that, but I don't understand why I can't take silent pics with exposure time longer than 16s with the nightly build from builds.magiclantern.fm (https://builds.magiclantern.fm) (700D.114) when it seems to be possible according to this thread.
The link from @josevpn (https://dl.dropboxusercontent.com/u/44995840/ML_silent/silent.c) doesn't work anymore, https://bitbucket.org/Gr3g01/magic-lantern-frsp-long-expo/ is gone, and the PR (https://bitbucket.org/hudson/magic-lantern/pull-requests/735/frsp-bulb-support/diff) is declined - because of "monkey patching"??
However, I found it here (https://bitbucket.org/milank/ml-frsp-long-expo/raw/54405eda319ccd751d0f885f4e0d6c04ffd3d1d5/modules/silent/silent.c), updated it with the addresses from @hillibilli
I have a 700D.114 and there the address of capture_err_time_addr is different to the value from @josepvm:
capture_err_time_addr = 0xff1e1dd8
The address of
bulb_end_addr is the same as @josepvm posted = 0x24960
Aaaand now my first 5 minute test-exposure worked very well :)
This is my compiled build: https://arxius.io/f/110e49fb (https://arxius.io/f/110e49fb)
My question is: if this is possible, and working, why is it not merged? To me it is more important to have a feature that works rather than it being a "clean" solution.
Also, I think that I read somewhere (this forum and it's thread's are faar to huge IMO, to figure something out the first thing I have to do is sit down for two hours and read the forum), that somebody has found a workaround for the faster-than-~300ms-problem. If so, can somebody point me in the right direction?
And maybe we can do a list of features being implemented, but not currently in the nightly builds, and features declined? Like, things for testing, funny things nobody wants, etc.
Well, maybe there already is. Sorry for being dumb and not reading it all (the overview of all threads, and also all those 40 pages of this thread), I don't have the capacity for it IMO.
PS: Just noticed the code also still is here (https://bitbucket.org/Gr3g01/magic-lantern-frsp-long-expo/pull-requests/1/silentc-added-addresses-for-bulb-frsp-on/diff), it's @milank's version with support for the cams with bulb dial mode - I think?
-
The approach was, indeed, a bit of a maintenance burden, as different camera models use different offsets (so it's easy to make mistakes). However, it is something that can be validated in recent QEMU (which, back then, wasn't advanced enough).
I'd also prefer to have it on top of the patch manager (https://bitbucket.org/hudson/magic-lantern/pull-requests/687/patch-manager-wip/diff) backend - which works pretty well, with one exception: when I take it outside, it gives ERR70. When I get back inside to track the error, it works fine.
For the above reasons, I did not decline the PR, but preferred to wait. Unfortunately, the PR was declined by the author.
Having a test suite would greatly help with reviewing such changes (for example, QEMU has a pretty good one, so I often do changes without fear of breaking things). It's a bit harder on the camera, where tests usually require user interaction (therefore time-consuming). Most of the recent QEMU progress is directed towards this; however, at the time of writing, the emulation is not yet able to pass the tests from selftest.mo or from api_test.lua.
Regarding the ~300ms problem - see http://www.magiclantern.fm/forum/index.php?topic=19300.msg183286#msg183286 (and first post from that thread). Integrating the change into crop_rec is an easy coding task; making the other modules play nice with it (such as ETTR or advanced intervalometer) may be more difficult. I might take a look at it later this summer, if I'll get a second chance to play with a 700D for a week or so, but can't really promise anything.
-
Here is a new interesting application for the FRSP feature: 3D scanning of real objects, via the method of photogrammetry (https://en.wikipedia.org/wiki/Comparison_of_photogrammetry_software). Basically, one has to take hundreds of pictures of the object from different angles, and use a smart software which would find and match features across the photos, and fit a model to it (3D model of the object + the camera positions + the model of the camera and lens).
Here is my simple setup for taking pictures (of small objects; the purpose is to reproduce objects using my 3D printer):
- a rotating platform driven by a stepper motor (1600 steps per full rotation);
- home photostudio lighting (two large softboxes and reflectors) using speedlights triggered by a single RF controller;
- camera (Canon 6D) on a tripod pointing at a small object sitting in the middle of the rotating platform, taking photos of the object at regular intervals (say every 2s - using the intervalometer feature of ML).
It all works pretty well, except that I don't wont to burn the shutter of my 6D for this stuff. It takes at least ~50 shots per object to build a model, and likely a few times more to also incorporate focus stacking into this (so probably ~250 shots per scan). FRSP would fit nicely here - if I could make it work with my setup.
At the very least, I need to have my flashes go off every time the intervalometer takes a FRSP photo. I saw reading the light from the camera LED suggested in this thread as the solution for this problem - can anyone give a reference to a page where this is discussed in detail? I couldn't find details in this thread. Specifically, I need to know if there is a lag between the LED flash and the actual FRSP exposure. If there is no lag, I can use a simple photodiode circuitry to do the trick, but with a lag I'll likely resort to using a microcontroller.
The first post in this thread mentions that when FRSP is used with intervalometer, the shortest possible time interval is ~10 seconds. Is it still the case, specifically for 6D? Ideally, I'd like to use a 2s interval.
Has anyone tried Advanced Intervalometer module with FRSP? Will it work? My idea is to take continuous photos of the rotating object over the course of a few full rotations, while slowly shifting the focus from the foreground to the background of the object. My hope is that one doesn't need to do a bunch of focus stacking before running the photogrammetry software (this will significantly complicate the process); instead, one would just slowly vary the focal point while taking hundreds photos of the rotating object, and let the photogrammetry software find and match all the sharp features of the photos, which at the end should recover the whole extent of the object.
-
I couldn't find details in this thread. Specifically, I need to know if there is a lag between the LED flash and the actual FRSP exposure.
You can turn on the LED whenever you need - even from a Lua script. However, turning it exactly in the middle of the exposure would require a background task (or polling) to check some low-level registers and figure out when the exposure started. Or, placing some hook (https://www.magiclantern.fm/forum/index.php?topic=2388.0) in Canon's photo capture task (https://www.magiclantern.fm/forum/index.php?topic=1915.0). You may also have some luck with a fixed delay (trial and error).
The first post in this thread mentions that when FRSP is used with intervalometer, the shortest possible time interval is ~10 seconds. Is it still the case, specifically for 6D?
You tell me.
The easiest way to reduce the file saving time is to port the lossless compression routines (http://www.magiclantern.fm/forum/index.php?topic=18443.0) to 6D (easy coding task (http://www.magiclantern.fm/forum/index.php?topic=18443.msg188721;topicseen#msg188721)).
If you need even more speed and/or short exposure times without gradient, port the full-res LiveView (hint for 700D) (http://www.magiclantern.fm/forum/index.php?topic=19300.msg182818#msg182818) and use mlv_lite (which is pipelined and optimized for fast writes).
-
Thanks! It does sound that a simple photodiode circuit will not do the trick. I have a few Arduino Nano lying around, will be playing with different lags and logics (if I recall correctly there is more than one LED flash per shot).
-
Here is a new interesting application for the FRSP feature: 3D scanning of real objects, via the method of photogrammetry (https://en.wikipedia.org/wiki/Comparison_of_photogrammetry_software).
yep. tried VisualSfm (years ago) several times using handheld shots. but most of the time the problem wasn't the amazing resolution you get using FRSP or MLV in general, but the fact that the items i scanned didn't have ideal textures for the SFM algos to recover the structure.
so it ended in giving up :)
maybe i am just too impatient...
-
Did a very hackish fix to get lossless compressed Full Resoution Silent Pictures DNG files working with the EOSM and 700D without breaking it on the 5D3. Put up test builds on my bitbucket download page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) and submitted a pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/858/fix-lossless-compression-on-frsp-for-eosm/diff).
Not the ideal solution, basically it just uses the newer version of save_lossless_dng for the 5D3 and the older version of that function for all other cameras. The "RAW error, falling back to YUV overlays" warning has returned to the EOSM and 700D but the current version of silent.mo doesn't save the DNGs and gives no warning on these cameras.
-
Success! I managed to use an external flash with FRSP on my 6D, using pretty much the same setup as when I used my Arduino focus stacking macro rail with 50D. I just ran a 100-shots test, and there were no issues (black or partially exposed frames). This will be used to do photogrammetry (3D scanning from multiple images).
Here is my setup:
(https://farm5.staticflickr.com/4427/37414853585_2fd47ce516_z.jpg) (https://flic.kr/p/Z1dUsv)Untitled (https://flic.kr/p/Z1dUsv) by First Last (https://www.flickr.com/photos/99745838@N03/), on Flickr
The core is Arduino UNO running my simple code. It drives both the stepper motor via the stepper driver (which rotates the scanning platform, not shown here), and the small breadboard I just put together, with two optocouplers (PC817 - got 50 of them for 1$ from China), and two limiting resistors (220 Ohm). Also on the photo you can see one of my RF flash remote triggers Yongnuo (I have a bunch of Yongnuo 560III flashes in my home studio which can be triggered simultaneously with this trigger). The two connectors are to the stepper motor (white) and camera (black). The whole thing (including the stepper motor) is powered by a single 12V power adapter.
As an initial guess I tried exactly the same timing settings which worked well on my old camera (50D), and surprizingly they worked perfectly on 6D, despite 6D having twice slower write speed (40 MB/s vs 50D's 80 MB/s), and slower sensor read speed (0.3s vs 0.15s -ish). I used shutter speed 0.3s.
t=0.0s: shutter half-press initiated
t=1.1s: flash is triggered (for 0.1s)
t=2.0s: shutter half-press released
t=6.0s: end of the cycle
As I speculated before, perhaps it is the fact that I am (half)pressing the shutter for quite a while (2s) that stabilizes the system, and results in highly accurate timings for the images. (SO that a constant delay works perfectly fine for the flash.)
Now back to the interesting stuff - making 3D scanning work...
-
My setup for 3D scanning using FRSP (see above) seems to work well, but one important feature is missing. For this kind of shooting (object size between 2-20 cm), DoF is fairly narrow, so one has to gradually shift the focus while shooting, and have a few full rotations of the object, to have between 2 to 10 focus positions for each full rotation. (So the 3D reconstruction software will be effectively doing focus stacking while reconstructing). To make it repeatable and automatic, a ML script would be needed which (a) detects when a FRSP picture has been taken, and (b) after each N such shots, it moves the focus by a predefined number of steps.
I've never done ML scripting (I am looking into it now), but it looks like a combination of custom_picture_taking() and focus() functions should do the trick - am I right? I can't find much documentation on custom_picture_taking() - can you point to any, or perhaps to some example scripts? Thanks!
-
Ideally, camera.shoot() should take a silent picture if enabled (just like the intervalometer does, for example).
It's not covered by API tests though, so YMMV.
The CUSTOM_PICTURE_TAKING hook is meant for modules or scripts that can implement some custom photo capture modes (like silent.mo does). These custom modes would be used by intervalometer and other ML tools (such as focus stacking), if enabled.
-
In my case, silent pictures are triggered by an external switch (optocoupler connected to Arduino). I thought CUSTOM_PICTURE_TAKING can help me to detect these events - was I wrong? Perhaps key() function is the one I need to use here?
Pressing full-shutter while taking FRSP still results in a "normal" picture taken, as it used to be? It just occurred to me that I could use one more optocoupler (connected to the SHUTTER pin of the camera) to let my arduino rig communicate to camera when it has to move focus. But I suspect I'd have to be careful with timings - perhaps moving focus can only be done at certain times (e.g. not when FRSP image is recorded).
-
Full-shutter was a black box to us, until very recently (http://www.magiclantern.fm/forum/index.php?topic=17596.msg189358#msg189358). Now I'm starting to understand how it works, thanks to some notes from Leegong (from NikonHacker).
I still don't know enough to override this event, but at least now I know where to look. I'm not yet sure whether the MPU initiates the photo capture and the mirror movement (if that's the case, we'd have to block it somehow, and in this case, I don't know whether the MPU would still send the shutter event, or just a generic BUSY message), or maybe the main CPU has to request all this stuff (in this case it should be easier to override this event).
edit: selftest.mo - fault emulation - lock-up ARM CPU, press full-shutter, mirror doesn't move it moves, just not consistent :(
Half-shutter is much easier to catch, as it doesn't have too many side effects (metering and maybe autofocus). However, when the GUI is locked, good luck detecting this event (http://www.magiclantern.fm/forum/index.php?topic=19300.msg189561#msg189561)...
Yes, focus has to be done while the camera is in LiveView (and the LiveView must be actively refreshing; reading its state from Canon properties is not enough).
-
Thanks for the details, things are quite a bit more complicated than I imagined!
-
After playing a bit with selftest.mo - fault emulation - lock-up ARM CPU (which does nothing more than cli(); while(1); on the ARM processor, thus blocking all the processes running there), the mirror still moves when pressing the shutter fully. That means the decision to move the mirror is taken on the MPU (a processor not under our control). Therefore, overriding it from photo mode is not going to be easy.
The behavior in LiveView is a little different, but I'm still not sure the full-shutter event gets communicated by the MPU in a way we can use to override it. On PowerShot firmware (CHDK), this event is handled like any other button, so they have no trouble overriding it (they use full-shutter press to start Lua scripts, for example).
-
I realize the talk is way over technical but been trying to get full res silent pictures for awhile using the crop_rec module on the 5dmk3 and haven't been able to get the settings right:
Manual Mode: shutter 400, f/4.0, iso 8000. Back button focus enabled with the *
Live view Mode
Silent Pictures Enabled: Burst MLV
Crop mode: 3.5K 1:! centered 5x
shoot preferences: off
When I half press the shutter I only get 1932x1290 pictures. I'm pretty sure my settings aint right, would somebody please point me on the right direction?
thank you
-
Any warnings in menu on the selected options?
-
One more reason to love the FRSP feature - I recently designed and built a 3D scanning assistant (for photogrammetry processing). It rotates a platform while triggering FRSP shots with external flash(es). The full description is here:
http://pulsar124.wikia.com/wiki/3D_Scanner
It works great. FRSP really saves the shutter life of my Canon 6D, as one needs hundreds of shots for a quality scan.
Here is my first test scan, made out of 150 FRSP shots from 3 different camera angles (Canon 6D + 50mm f1.8 STM lens + two YN560III flashes inside softboxes), of a 20cm tall statue - no artifacts, high 3d resolution. (But it took many hours to process on my PC):
(https://c1.staticflickr.com/5/4674/38727801025_355ed493e2_d.jpg)
-
Moving this here from the 100D topic.
I also have a question to А1еx regarding the silent module on the 100D that I have been using a lot for timelapse work. I have been investigating the possibility for using it with stabilized lenses for shooting single full-resolution silent pictures in the Life View mode without actuating the mechanical shutter. This is one of my favorite ML features since it allows taking single DNG photos at the highest sensor resolution, also in the Dual ISO mode, at locations where shutter noise is highly undesirable (churches, museums, lectures, etc.). An additional bonus is the fact that pictures are taken in the mirrorless mode, so vibrations due to mirror flipping are avoided. Thus sharp handheld pictures are possible at shutter speeds as low as 1/25-th down to 1/4-th of a second with stabilized lenses.
There is one problem, however. I usually use the back button for precise focusing at 5x or even 10x-magnification. In this process, the image stabilizer (IS) of the lens is active and a very precise focus can be adjusted even at low light. When I am ready with focusing and metering and want to take the picture by pressing halfshutter, the IS continues working only for about 1 s. after I release the back button and then it stops working. It does not get activated when I press halfshutter to take the picture. This means that at the moment I take the photo, I have no image stabilizer engaged and the picture turns out blurry due to camera shake. Sometimes I manage to press halfshutter very quickly, within this 1 s. after I release the back button hoping that the IS is still working during the actual photo taking but the time is too short to avoid camera shake. Moreover, in this short time it is impossible to go back to full-screen LifeView for proper framing and or leveling.
So, my question is: Is it somehow possible to increase the IS time from 1s. to 3 or even 5 s. after the back button is released? An even better option would be to reengage the IS upon halfshutter press and holding down and the picture is taken only in the moment, half shutter is released. In this way, the photographer would have enough time for proper framing and taking a deep breath during IS operation, before the actual photo is taken.
Thank you.
The IS is controlled by the MPU (http://www.magiclantern.fm/forum/index.php?topic=17596.0), and when exactly is enabled and when it's not, is unclear to me. In movie mode, if I'm not mistaken, it's always enabled, even in standby, but I'm not sure what happens once ML pauses LiveView in order to take the full-res silent picture.
When AF is enabled, there is a small delay before the half-shutter press, until the picture is taken (for the purpose of detecting autofocus). This delay should be enough to enable IS, but my gut feeling says it probably stops as soon as the LiveView is paused.
Do you have a sure way to tell whether IS is working, even without seeing the LiveView (such as, lens making noise, or by checking the captured images) ?
To test whether IS stays on while pausing LiveView, in movie mode, remove these checks:
diff -r 1dbb29d3cc6d modules/silent/silent.c
--- a/modules/silent/silent.c
+++ b/modules/silent/silent.c
@@ -1172,6 +1171,0 @@
- if (shooting_mode != SHOOTMODE_M)
- {
- error_msg = "Manual (M) mode is required.";
- goto err;
- }
-
@@ -1448,2 +1441,0 @@
- if (silent_pic_mode == SILENT_PIC_MODE_FULLRES && (shooting_mode != SHOOTMODE_M || is_movie_mode()))
- return 0;
The feature is disabled in movie mode because you can't really adjust the shutter speed - no matter what you dial there, the full-res exposure will end up a lot brighter.
Triggering on half-shutter release is easy.
-
Thanks for your reply, A1ex,
Yes, I have two ways of telling if the IS is on or off:
1) By listening to the noise of the lens I can tell exactly when the IS engages and when it stops working;
2) By looking at the image on the screen. When the IS stops working, the image becomes shaky. The longer the focal length of the lens, the larger the shakyness.
In the movie mode, the IS stays engaged all the time - extremely useful for having stabilization in hand held video shooting.
-
Alright, stopped all the noise sources (turned off fan, closed doors/windows), placed the lens on my ear and I could hear the IS noise (a continuous hum). That way, I could unambiguously tell the IS remains active when entering PLAY mode starting from movie mode (something I didn't expect, given that Canon code turns off the sensor and the image pipeline in this mode). That was on 60D, and my IS lens is an APS-C one, so I can't test this on a DIGIC 5 model - can you confirm the behavior on 100D (IS always active in PLAY mode when entering from movie mode) ?
In photo mode, the same hum noise is triggered by half-shutter press and stays there for ~ 1 second, even outside LiveView or if triggered from Canon menu. So, it's not affected by the camera GUI mode - that's good.
Triggering a software half-shutter press also activates IS - also good.
Included the IS feature and some delayed trigger options in the latest lua_fix build.
-
Thank you A1ex,
I will test your January 20-th build for the 100D as soon as possible.
-
A1ex,
I tested again with the Oct. 23-rd build on the 100D with the EF 70-300/4.0-5.6 IS. Here is what I confirm:
1) In the Movie mode, the IS stays on all the time but I don't like shooting single FRSPs in this mode because it is very hard to control the shutter speed. If I need a shutter speed of 1/4 s. for example, I have to reduce FPS override to 4 fps which makes focusing a pain.
2) When I switch from Movie mode to Play mode (Power switch to ON and Live View activated), the IS stays off. It engages only if I press the back button for focusing but when I release the back button again, IS stops working within about 1 s. When I now press half shutter to take the picture, IS starts working again but the picture is already taken before stabilization is good enough to minimize blur due to camera shake. So, the picture comes out blurry most of the time. I will check out the delay options on your latest build to see how it works now.
-
A1ex,
I have just tested your new January 20-th build. Single FRSP works very well now. I love the "Half-shutter release" option for the trigger mode. This is exactly what I wanted! I can now shoot handheld FRSPs even at 300 mm focal length with quite usable results. Here is one, shot at 0.3s shutter speed:
(https://thumb.ibb.co/bCDpob/100_D_EF_70_300_IS_ISO1600_F5_6_0_3s.jpg) (https://ibb.co/bCDpob)
Thank you so much, A1ex! I was wondering if you may be able to implement this feature also in my favorite build from Oct. 23-rd which I use for shooting losslessly compressed RAW video with sound. This one here:
https://bitbucket.org/ehoutsma/magic-lantern/downloads/
Thank you in advance!
-
Hi guys,
I read this topic and found my problem here.
I was not the only one who encountered black frames in silent mode for 550d.
Tell me, please, does this problem somehow be solved?
Thank you in advance.
-
I have no idea what you are talking about. Searching for "black 550D" in this thread points to a very old issue that was not about black frames in the first place, and was resolved a long time ago. Searching for "black frames" does not reveal anything interesting either.
https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
-
I spent again some tests I can report some information.
I used silent.mo in symple mode, dng.
Intervalometer 300 frames every 60 seconds.
The output received 207 frames (the battery was exhausted), of which 14 frames are black. Each file had a size of 3847kb. The frequency of black shots is not justified. There were two at once, some with an arbitrary interval.
The next day I used full-res, dng. Received 236 frames of this size (3847kb). There were no black frames. I'm surprised at the size of the file in the FULL-RES mode, usually the file size is about 31MB.
ETTR was used in both cases.
Canon 550d, firmware 1.0.9, magiclantern-Nightly.2018Feb04.550D109.
On this forum, I saw references to this problem:
https://www.magiclantern.fm/forum/index.php?topic=14979.0
https://www.magiclantern.fm/forum/index.php?topic=12523.msg120661#msg120661
I ask to help you figure it out.
Thank you in advance
(https://thumb.ibb.co/e47HF7/00000199.jpg) (https://ibb.co/e47HF7)
-
Today's test confirmed my theory.
We start the intervalometer in the mode SILENT.MO, simlpe-dng. We are waiting for 1 frame.
Go to the menu ML, change to FULL-RES.
We return to LiveView, we are waiting for the shot.
This results in 1 white frame and RAW ERROR.
Again we change FULL-RES on the simple and during the session there is not a black frame.
-
Hey! I got a question. I just recently started using silent pics and I love it so far. I think that you obviously wouldnt shoot sports with it, 1/30th of a second isnt too shaby - very useful for ceremonies or other kind of event where shutter noise is a no no as others have noted. I just wondered if it is possible/feasible to impement a mode that tells the cam to set the shutter speed to 8000 automatically AFTER the half shutter was pressed. This way one could use the Live view for normal preview (bc it darkens when you choose the higher shutter speeds) but ensure that the picture is taken at the maximum allowed shutter speed. Is this an idea even worth pursuing or are there simpler in-camera tricks to achieve this? Thanks in advance!
-
What do you want to achieve? According to the actual knowledge, you can't shorter the exposure time below 1/30s without actuating the shutter. This is the reason why the shutter is built-in. And as soon as you actuate the shutter, you are not silent anymore. So, live with the 1/30s limitation and don't hope for a simple hack.
Only loose thoughts: I believe the mirrors are significantly contributing to the overall noise, so the possibility to keep the mirrors up but activate the shutter only, could lead to a still quite silent trigger enabling all exposure times. But this rather won't be possible without having a control over MPU and probably never possible, as the mechanics of the shutter might be directly coupled with the mechanics of the mirror (just a guess, I believe there is a reason why taking a picture in LV is always moving the mirror down and up again as well).
-
I dont think you understand my question correctly. I am NOT searching for a simple fix to make the shutter speed faster - I read quite a bit of this thread, enough to understand that 1/30th is the current limit. However (and here's the correct me if I'm wrong part again) I seem to recall that a1ex achieved 1/30 with a shutter speed setting of 8000 on the camera. When you set your shutter to 8000, liveview darkens siginificantly. My question was aiming at a possible solution like tricking the module into "always" selecting the highest possible shutter speed without the need to set it to 8000 on cam.
-
Actually it's closer to about 1/10 in the middle of the frame on 5D3 (see the timing analysis (http://www.magiclantern.fm/forum/index.php?topic=12523.msg121962#msg121962)) and 1/2 on 6D (theory, not confirmed experimentally, but this model is the closest to 70D).
These will help with the slow shutter speed:
- full-res LiveView (http://www.magiclantern.fm/forum/index.php?topic=19300) (only 5D3 for now, but there is a PoC for 700D (https://www.magiclantern.fm/forum/index.php?topic=19300.msg197697#msg197697) with adtg_gui); this can reach shutter speeds as fast as 1/15000, with a rolling shutter of 128ms on 5D3
- this proof of concept (https://www.magiclantern.fm/forum/index.php?topic=21852) (use aperture to simulate a mechanical shutter, much quieter, compatible with all models, just need a couple of hours to make sure it actually works as advertised, then it will be live)
To select 1/8000 quickly, try the exposure presets feature. A Lua script can be used to sketch the half-shutter workaround, too. Disabling exposure simulation might be also helpful (yet another workaround).
-
I dont think you understand my question correctly.
Correct, I didn't, sorry.
-
Ha! Yes, disabling the exposure simulation was something along the lines of what I was thinking about. However, the solutions you suggested are obviously a lot more elegant. Can't wait to see how the mechanical shutter simulation by way of the aperture works out! Thanks for answering the question and also grant us a look into the future ;).
-
Hi! I didn't use silent picture FullRess for a year or so and forgot how to make exposure longer than 1/33. With expo override ON - I still can get only 1/25. My ExpSim seems to be locked to Movie mode. I don't remember if it always was locked..
But I'm sure I've made time lapses with 5-10 seconds exposure FRSP without any problems and now I'm stucked in settings. Please give me a hint (5d3).
-
@Dmytro_ua: you should be in photo mode.
In video mode FRSP works too(and you even can manage aperture of STM lenses!!!), kinda not documented " full-res LiveView", but with video limitations on exposure.
-
@Dmytro_ua: you should be in photo mode.
Wait a minute, now I'm even more confused..
In the Silent Picture description is said that "This feature only works in LiveView". When I'm in photo mode the mirror is down and for take a picture it should go up, so it couldn't be a silent picture anymore.
I'm sure I'm missing something stupidly simple :-[
-
Photo mode refers to "normal" stills camera operation (mirror down, shutter closed, framing using eye piece) *and* liveview using display for framing.
Liveview is not exclusive to movie mode.
And of course there is no way entering liveview without mirror going up and shutter opening. But in Silent Pic mode your shutter won't close after taking pic and mirror would not be actuated.
-
Liveview is not exclusive to movie mode.
Oh, thanks! Now I remember that I did my last FRSP shoot with 5d2 and workflow was a little bit different. On my "new" 5d3 to go to live view in photo mode I have to press "Start/Stop" button :) It was not obvious for me. Thanks for help ;) ;) ;)
-
Hi,
i´d like to use the silent Picture for Electronically Assisted Astronomy. for this it is necessary to Transfer the Pictures live to the PC for live-stacking. if i connect the camera through an usb cable i can´t see the dng/mlv files stored on the Card, only raw or jpg. only if i put the Card direct into the pc´s Reader i see them stored in the dcim Folder.
is there a way to Access These Pictures live from a PC?
thanks, markus
-
Patching the code to save .JPG instead of .DNG should do the trick.
Having a Lua script running in background to do these renames might work too, but I'm unsure about thread safety (need to check what happens if some task tries to rename a file while some other task is modifying it). There might be an API to tell whether a file is "in use", or it might just work out of the box, but this needs some reverse engineering to find out.
-
Hi a1lex,
thx for the quick Reply. i have edited the silent.mo with Notepad++. now the Images are saved as jpg, but the Canon tool still not recognize it. i also test with Extension cr2, still no luck. i think it is the filename also. "IMG_9133.CR2". Maybe i have to add "IMG" to the Image file, but i don´t know how to do this. any help will be welcome. and also only 4 Digits in filename.
"save_mlv MLV CR2 %s/%%08d.%s %s/%04d%%04d.%s %s"
regards, markus
-
In this case, it's probably not the file name, but the image catalog. When taking a picture, Canon code not only saves the image to card, but also adds it to this catalog (some sort of index stored in the RAM). How exactly this catalog works, in particular how to add files to it, is not yet understood.
If you restart the camera, do the files appear on the remote computer?
The renaming trick is known to work on Eye-Fi cards, btw. Some cards other than Eye-Fi may be able to transfer arbitrary files out of the box.
-
Hi,
an hour ago i had the same idea About the WiFi Card (before i read your post). in Germany we say "zwei dumme, ein gedanke" - "two stupid, one thought"
i will try a toshiba WiFi sd Card. hope this will work.
the silent files do not appear after restart the camera.
thx again!
-
That will work. Make sure you get the W-04 version; reviews say it's much faster than W-03.
-
@ All Who Refer to Stills Mode as Photo Mode
"Photo mode refers to "normal" stills camera operation" > But Probably Really Shouldn't !
No idea Whom, When, Why "Photos Mode" started being used to refer to "Stills Mode".
Since Everything our cameras do Visually is Photo Capturing, Our Cam's are in "Photos Mode"
whenever they are "On". Since those Photos can be Captured as Still Photos or Moving Photos,
the 2 Main Photo Capture Modes should be referred to as Stills & Movies.
Which is actually the way Canon does it in their Manuals .
ORR ~ DeanB
Sorry Walter > Not trying to pick on You here, You just happened to be the 1 who
Poked My Button on this when I had time to do a Post I've been wanting to do for
quite some time ~
-
Small question, I've tried silent pictures after a long time, just to be sure I've got it right. Full res is still limited to 1/10 right? I tested it and it looks like it.
-
Hi,
Is FRSP should give the same color and exposure results as in a regular Photo mode with cr2?
I tried the same setting and opened pics in ACR (sorry for poor quality).
With 0,3", f16, iso 320 - FRSP captures picture twice longer (about 600 ms) = 0,6".
My camera is 5d3 with expo override enabled. Should I change some settings to match closer?
(https://thumb.ibb.co/eACzNo/cr2vsdng.jpg) (https://ibb.co/eACzNo)
Thanks
-
Hi,
an hour ago i had the same idea About the WiFi Card (before i read your post). in Germany we say "zwei dumme, ein gedanke" - "two stupid, one thought"
i will try a toshiba WiFi sd Card. hope this will work.
the silent files do not appear after restart the camera.
thx again!
Hi mash.m
Where you able to transfer file from your camera to the PC using FRSP? I stumbled upon the same scenario, trying to use a EOS 50D to digitize Super 8 and a 400 Ft reel is about 28800 images so using the shutter will kill the camera.
I hex edited the silent.mo and changed dng to CR2 extention and all files are saved as CR2 file but nothing shows up. In ML they are visible but not in EOS menu/software on the camera so same thing happens in gphoto2 so this is as a1lex say most probably the image catalog on the memory that is not updated.
If anyone got the WFT-E3A, I am wondering if the WFT-E3A would work with FRSP, dose the EOS write directly to a usb attached disk or does it write to the memory card first and then copy to the external media. with 28800 images on 400Ft reel a CF card or SD card would be to small we are talking 100's of GB before post processing :-)
regards,
GM
-
It will be possible allow take photo during recording MLV-lite without affect to recording output?
-
Yes, as long as photo resolution is not (much) higher than video resolution.
Changing LiveView resolution on the fly might be possible; I had some half-successful attempts at that; however, capturing a full-res image takes time, so the video stream would be interrupted (you will lose a few frames, depending on how fast the resolution can be switched; rolling shutter time for a full-res image is about 130ms on 5D3).
One way to approximate full-res capture without interrupting the video stream would be to shift the "phase" in the 3x3 pixel binning (the initial row and column of each 3x3 pixel group). That might be doable from ADTG and/or CMOS registers. If you have the patience to adjust these in adtg_gui and notice sub-pixel image movements, or maybe write a script to automate that process, you may find that register (assuming it exists). If you can also find a way disable the column binning, i.e. read out one single pixel out of 3 horizontal ones, on cameras other than 5D3 you would need 9 video frames to "assemble" one full-res image. Of course, that would only work for static scenes.
Without a way to disable the line/column binning, even if you can shift the initial line/column, recovering a full-res image is going to be difficult. Some deconvolution or super-resolution techniques might help, in particular if the scene is not exactly static when you take the picture.
Difficulty: give me 5 years and a team of researchers (https://xkcd.com/1425/) ;)
-
I was interested in long exposure fix some time ago, but wasn't able to understand how to work on this module and dig manually into commit's history to make Greg code works on update codebase.
So I remembered about this and managed to update FRSP Bulb code with latest changes in ML repository.
Here is the diff for unified branch (test also in lua-fix, not tested on top of crop_rec_4k)
# HG changeset patch
# User Alessandro Profiti <aprofiti@users.noreply.github.com>
# Date 1535128403 -7200
# Fri Aug 24 18:33:23 2018 +0200
# Branch frsp_bulb
# Node ID 77ea846906c328eaf10c71a0050f8cf6ea2b7780
# Parent 7a3b5fa3f4c6f085e5bb9d58ab4da0002c01e4a3
silent.c: Add FRSP support to longer exposure up to 15 minutes. Credits to Greg for original code and dmilligan for gist: https://gist.github.com/davidmilligan/6b8f78383a1e11cbecc620874e129cbb
diff --git a/modules/silent/silent.c b/modules/silent/silent.c
--- a/modules/silent/silent.c
+++ b/modules/silent/silent.c
@@ -17,6 +17,7 @@
#include <powersave.h>
#include "../lv_rec/lv_rec.h"
#include "../mlv_rec/mlv.h"
+#include <cache_hacks.h>
static uint64_t ret_0_long() { return 0; }
@@ -69,6 +70,8 @@
static int mlv_file_frame_number = 0;
static int long_exposure_fix_enabled = 0;
+static uint32_t bulb_end_addr = 0;
+static uint32_t capture_err_time_addr = 0;
/* forward reference */
static struct menu_entry silent_menu[];
@@ -1153,6 +1156,11 @@
}
}
+static void bulb_stop()
+{
+ MEM(bulb_end_addr) = 1;
+}
+
static int
silent_pic_take_fullres(int interactive)
{
@@ -1224,6 +1232,19 @@
* and creates a "job" object (CreateSkeltonJob)
*/
struct JobClass * job = (void*) call("FA_CreateTestImage");
+
+ unsigned shutter_old = lens_info.raw_shutter;
+ if (shutter_old == SHUTTER_BULB)
+ {
+ int bulb_time = menu_get_value_from_script("Bulb Timer", "Exposure duration");
+
+ if(bulb_time > 900) //15 minutes limit
+ {
+ bulb_time = 0;
+ }
+
+ delayed_call(bulb_time * 1000, bulb_stop, 0);
+ }
lens_info.job_state = 1;
info_led_on();
@@ -1520,6 +1541,23 @@
silent_pic_take(1);
}
+ /* some cameras (5D2) reset the cache fake after FRSP, we need it again */
+ if (bulb_end_addr && capture_err_time_addr)
+ {
+ if ((*(uint32_t*)capture_err_time_addr) != 960000)
+ {
+ cache_fake(capture_err_time_addr, 960000, TYPE_DCACHE);
+ }
+ }
+
+ if (!bulb_end_addr && capture_err_time_addr)
+ {
+ if ((*(uint32_t*)capture_err_time_addr) != 35000)
+ {
+ cache_fake(capture_err_time_addr, 35000, TYPE_DCACHE);
+ }
+ }
+
return 0;
}
@@ -1608,6 +1646,36 @@
long_exposure_fix_enabled = 1;
}
+ if (is_camera("500D", "1.1.1"))
+ {
+ bulb_end_addr = 0x3324;
+ capture_err_time_addr = 0xff08afb8;
+ }
+ /*if (is_camera("550D", "1.0.9"))
+ {
+ bulb_end_addr = 0x31D8; // not tested please confirm
+ capture_err_time_addr = 0xFF090174; // not tested please confirm
+ }*/
+ if (is_camera("5D2", "2.1.2"))
+ {
+ //bulb_end_addr = 0x3174; // cameras with SHOOTMODE_BULB not support FRSP bulb
+ capture_err_time_addr = 0xFF88DB68;
+ }
+
+ if (!bulb_end_addr && capture_err_time_addr)
+ {
+ SLOWEST_SHUTTER = SHUTTER_30s;
+ cache_lock();
+ cache_fake(capture_err_time_addr, 35000, TYPE_DCACHE); // 30 + 5 seconds
+ }
+
+ if (bulb_end_addr && capture_err_time_addr)
+ {
+ SLOWEST_SHUTTER = SHUTTER_BULB;
+ cache_lock();
+ cache_fake(capture_err_time_addr, 960000, TYPE_DCACHE); // 15 + 1 minutes
+ }
+
menu_add("Shoot", silent_menu, COUNT(silent_menu));
return 0;
}
# HG changeset patch
# User Alessandro Profiti <aprofiti@users.noreply.github.com>
# Date 1535191697 -7200
# Sat Aug 25 12:08:17 2018 +0200
# Branch frsp_bulb
# Node ID bb91393123dd016c4497a12379b7041d4b4b5a73
# Parent 77ea846906c328eaf10c71a0050f8cf6ea2b7780
silen.c: Add FRSP support for dedicated BULB mode (SHOOTMODE_BULB). Credit milank https://bitbucket.org/milank/ml-frsp-long-expo/branch/BULB%20dial%20test#diff
diff --git a/modules/silent/silent.c b/modules/silent/silent.c
--- a/modules/silent/silent.c
+++ b/modules/silent/silent.c
@@ -72,6 +72,7 @@
static int long_exposure_fix_enabled = 0;
static uint32_t bulb_end_addr = 0;
static uint32_t capture_err_time_addr = 0;
+static uint16_t frsp_tv_addr = 0;
/* forward reference */
static struct menu_entry silent_menu[];
@@ -147,9 +148,9 @@
MENU_APPEND_VALUE(", DNG");
}
- if (silent_pic_mode == SILENT_PIC_MODE_FULLRES && (shooting_mode != SHOOTMODE_M || is_movie_mode()))
+ if (silent_pic_mode == SILENT_PIC_MODE_FULLRES && ((shooting_mode != SHOOTMODE_M && shooting_mode != SHOOTMODE_BULB) || is_movie_mode()))
{
- MENU_SET_WARNING(MENU_WARN_NOT_WORKING, "Full-res pictures only work in Manual (M) photo mode.");
+ MENU_SET_WARNING(MENU_WARN_NOT_WORKING, "Full-res pictures only work in Manual (M) or Bulb (B) photo mode.");
}
silent_pic_check_mlv(entry, info);
@@ -1156,6 +1157,7 @@
}
}
+/* scsBulbEnd - it will stop Bulb exposure */
static void bulb_stop()
{
MEM(bulb_end_addr) = 1;
@@ -1177,10 +1179,10 @@
char* error_msg = 0;
- if (shooting_mode != SHOOTMODE_M)
+ if (shooting_mode != SHOOTMODE_M && shooting_mode != SHOOTMODE_BULB)
{
- error_msg = "Manual (M) mode is required.";
- goto err;
+ error_msg = "Manual (M) or Bulb (B) mode is required.";
+ goto err;
}
if (prop_iso == 0 || prop_shutter == 0)
@@ -1218,6 +1220,18 @@
goto err;
}
+ int bulb_time = menu_get_value_from_script("Bulb Timer", "Exposure duration");
+
+ /* Maximum Bulb time with FRSP (I think we don't need more than 15 minutes) */
+ if (prop_shutter == SHUTTER_BULB || (shooting_mode == SHOOTMODE_BULB && frsp_tv_addr))
+ {
+ if(bulb_time > 900) //15 minutes limit
+ {
+ error_msg = "FRSP Bulb - 15 minutes limit.";
+ goto err;
+ }
+ }
+
display_off();
/* we'll need these later */
@@ -1231,16 +1245,36 @@
* reads PROP_ISO, PROP_SHUTTER and PROP_APERTURE,
* and creates a "job" object (CreateSkeltonJob)
*/
- struct JobClass * job = (void*) call("FA_CreateTestImage");
+ void* job = (void*) call("FA_CreateTestImage");
- unsigned shutter_old = lens_info.raw_shutter;
- if (shutter_old == SHUTTER_BULB)
+ if (prop_shutter == SHUTTER_BULB || (shooting_mode == SHOOTMODE_BULB && frsp_tv_addr))
{
- int bulb_time = menu_get_value_from_script("Bulb Timer", "Exposure duration");
-
- if(bulb_time > 900) //15 minutes limit
+ /* some cameras reset the cache fake after FRSP, we need it again */
+ if (bulb_end_addr && capture_err_time_addr)
{
- bulb_time = 0;
+ if ((*(uint32_t*)capture_err_time_addr) != 960000)
+ {
+ cache_fake(capture_err_time_addr, 960000, TYPE_DCACHE);
+ }
+ }
+
+ /* cameras with SHOOTMODE_BULB need fake SHUTTER_BULB */
+ if (shooting_mode == SHOOTMODE_BULB && frsp_tv_addr)
+ {
+ printf("job: %x\n", job);
+ printf("prop_shutter: 0x%x\n", prop_shutter);
+
+ for (int i = 0; i < 1000; i++)
+ {
+ if(prop_shutter == *(uint8_t*)(job + i))
+ {
+ printf("FA_CreateTestImage Tv Addr : 0x%x\n", i);
+ }
+ }
+
+ ASSERT(*(uint8_t*)(job + frsp_tv_addr) == prop_shutter);
+ *(uint8_t*)(job + frsp_tv_addr) = SHUTTER_BULB;
+ //*(uint8_t*)(job + frsp_tv_addr + 2) = SHUTTER_BULB;
}
delayed_call(bulb_time * 1000, bulb_stop, 0);
@@ -1464,9 +1498,9 @@
if (!silent_pic_enabled)
return 0;
- /* fullres silent pics only work in M mode,
+ /* fullres silent pics only work in M or B mode,
* and they may screw up things if triggered while recording. */
- if (silent_pic_mode == SILENT_PIC_MODE_FULLRES && (shooting_mode != SHOOTMODE_M || is_movie_mode()))
+ if (silent_pic_mode == SILENT_PIC_MODE_FULLRES && ((shooting_mode != SHOOTMODE_M && shooting_mode != SHOOTMODE_BULB) || is_movie_mode()))
return 0;
static int silent_pic_countdown;
@@ -1541,23 +1575,6 @@
silent_pic_take(1);
}
- /* some cameras (5D2) reset the cache fake after FRSP, we need it again */
- if (bulb_end_addr && capture_err_time_addr)
- {
- if ((*(uint32_t*)capture_err_time_addr) != 960000)
- {
- cache_fake(capture_err_time_addr, 960000, TYPE_DCACHE);
- }
- }
-
- if (!bulb_end_addr && capture_err_time_addr)
- {
- if ((*(uint32_t*)capture_err_time_addr) != 35000)
- {
- cache_fake(capture_err_time_addr, 35000, TYPE_DCACHE);
- }
- }
-
return 0;
}
@@ -1649,26 +1666,35 @@
if (is_camera("500D", "1.1.1"))
{
bulb_end_addr = 0x3324;
- capture_err_time_addr = 0xff08afb8;
+ capture_err_time_addr = 0xFF08AFB8;
}
/*if (is_camera("550D", "1.0.9"))
{
bulb_end_addr = 0x31D8; // not tested please confirm
capture_err_time_addr = 0xFF090174; // not tested please confirm
}*/
+ if (is_camera("50D", "1.0.9"))
+ {
+ bulb_end_addr = 0x3218;
+ capture_err_time_addr = 0xFF885B14;
+ }
if (is_camera("5D2", "2.1.2"))
{
- //bulb_end_addr = 0x3174; // cameras with SHOOTMODE_BULB not support FRSP bulb
+ bulb_end_addr = 0x3174;
capture_err_time_addr = 0xFF88DB68;
+ frsp_tv_addr = 0x64; // cameras with SHOOTMODE_BULB need fake SHUTTER_BULB
}
- if (!bulb_end_addr && capture_err_time_addr)
+ if (is_camera("5D3", "1.1.3"))
{
- SLOWEST_SHUTTER = SHUTTER_30s;
- cache_lock();
- cache_fake(capture_err_time_addr, 35000, TYPE_DCACHE); // 30 + 5 seconds
- }
-
+ bulb_end_addr = 0x25294;
+ capture_err_time_addr = 0xFF1BF358;
+ frsp_tv_addr = 0x280; // cameras with SHOOTMODE_BULB need fake SHUTTER_BULB
+ }
+
+
+ /* cache fake "ERROR Take Semaphore" time in "FA_CaptureTestImage" */
+ /* 20 seconds to (15 + 1) minutes */
if (bulb_end_addr && capture_err_time_addr)
{
SLOWEST_SHUTTER = SHUTTER_BULB;
# HG changeset patch
# User Alessandro Profiti <aprofiti@users.noreply.github.com>
# Date 1535191978 -7200
# Sat Aug 25 12:12:58 2018 +0200
# Branch frsp_bulb
# Node ID 50d24ac04eea9e6bda683c249791bf6c87fa9f65
# Parent bb91393123dd016c4497a12379b7041d4b4b5a73
silent.c: Add FRSP Bulb support to 700D, 550D and EOS M
diff --git a/modules/silent/silent.c b/modules/silent/silent.c
--- a/modules/silent/silent.c
+++ b/modules/silent/silent.c
@@ -1668,11 +1668,11 @@
bulb_end_addr = 0x3324;
capture_err_time_addr = 0xFF08AFB8;
}
- /*if (is_camera("550D", "1.0.9"))
+ if (is_camera("550D", "1.0.9"))
{
bulb_end_addr = 0x31D8; // not tested please confirm
capture_err_time_addr = 0xFF090174; // not tested please confirm
- }*/
+ }
if (is_camera("50D", "1.0.9"))
{
bulb_end_addr = 0x3218;
@@ -1684,7 +1684,16 @@
capture_err_time_addr = 0xFF88DB68;
frsp_tv_addr = 0x64; // cameras with SHOOTMODE_BULB need fake SHUTTER_BULB
}
-
+ if (is_camera("700D", "1.1.4"))
+ {
+ bulb_end_addr = 0x24960;
+ capture_err_time_addr = 0xff1e1dd8;
+ }
+ if (is_camera("EOSM", "2.0.2"))
+ {
+ bulb_end_addr = 0x3F300;
+ capture_err_time_addr = 0xff1df1fc;
+ }
if (is_camera("5D3", "1.1.3"))
{
bulb_end_addr = 0x25294;
# HG changeset patch
# User Alessandro Profiti <aprofiti@users.noreply.github.com>
# Date 1535194347 -7200
# Sat Aug 25 12:52:27 2018 +0200
# Branch frsp_bulb
# Node ID 8ee5b34a8aa81b5a4196a90ca22d17f3f90336db
# Parent 50d24ac04eea9e6bda683c249791bf6c87fa9f65
silent.c: FRSP moved cache_fake hack to original position. Fix exposure time bug in 20-32s range introduced from milank code
diff --git a/modules/silent/silent.c b/modules/silent/silent.c
--- a/modules/silent/silent.c
+++ b/modules/silent/silent.c
@@ -1249,15 +1249,6 @@
if (prop_shutter == SHUTTER_BULB || (shooting_mode == SHOOTMODE_BULB && frsp_tv_addr))
{
- /* some cameras reset the cache fake after FRSP, we need it again */
- if (bulb_end_addr && capture_err_time_addr)
- {
- if ((*(uint32_t*)capture_err_time_addr) != 960000)
- {
- cache_fake(capture_err_time_addr, 960000, TYPE_DCACHE);
- }
- }
-
/* cameras with SHOOTMODE_BULB need fake SHUTTER_BULB */
if (shooting_mode == SHOOTMODE_BULB && frsp_tv_addr)
{
@@ -1574,7 +1565,16 @@
silent_pic_take(1);
}
-
+
+ /* some cameras reset the cache fake after FRSP, we need it again */
+ if (bulb_end_addr && capture_err_time_addr)
+ {
+ if ((*(uint32_t*)capture_err_time_addr) != 960000)
+ {
+ cache_fake(capture_err_time_addr, 960000, TYPE_DCACHE);
+ }
+ }
+
return 0;
}
The approach was, indeed, a bit of a maintenance burden, as different camera models use different offsets (so it's easy to make mistakes). However, it is something that can be validated in recent QEMU (which, back then, wasn't advanced enough).
I'd also prefer to have it on top of the patch manager (https://bitbucket.org/hudson/magic-lantern/pull-requests/687/patch-manager-wip/diff) backend - which works pretty well, with one exception: when I take it outside, it gives ERR70. When I get back inside to track the error, it works fine.
For the above reasons, I did not decline the PR, but preferred to wait. Unfortunately, the PR was declined by the author.
Apart from patching bulb address, how to patch cache? Do refactoring this to use patch manager would require much time?
Maybe I can looks how to use it in the free time.
Submitted PR #941 (https://bitbucket.org/hudson/magic-lantern/pull-requests/941/frsp-bulb-mode/diff) to main repo to have it as reference (Greg PR was discontinued and code can only be found digging deep into this thread).
I hope that is still interesting to someone :)
-
Not had any luck making this module work. Read the Help files – but can't see anything relevant to my problem.
Using Danne's crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Apr02.5D3123.zip build https://bitbucket.org/Dannephoto/magic-lantern/downloads/
Once module is enabled, half-press shutter has message on liveview screen: Preparing… then I get a Canon black screen with a white BUSY. Sometimes also a Canon spinning laser-disc gif (never seen this ever before) 'Saving' . Camera then locks up and requires battery pull. No image saved to card.
Also, can a 5D3 user please share exactly how to set up the correct Canon Custom Function for the half-press shutter capture?
Many thanks.
-
Try with regular builds, or with those from the Experiments page.
Default Canon settings should be OK. If using AF, you may want to enable back button focus in Custom Controls, but ML help already tells you to do that. Or, if there are any other settings you need to change - that I'm aware of - ML menu will tell you so.
-
@a1ex Righto, I see. Thanks! Couldn't find anything about setting the CFN buttons on the HELP wiki. Was I looking in the right place?
-
Loaded the experiments page Jul22_2018 4K build.
Still not working as expected: :(
Pressing the back focus button now produces: 'Preparing' message top left Liveview … then 'Hold On'. Then 'Preparing' stays on the screen.
No lock ups. But no images on any card. File manager > view of any image on card produces black screen with what looks like random white characters.
Still can't get CFN to set trigger correctly!
-
The "Hold on" message means it's waiting to see whether the camera is going to autofocus, or not. Keep the button pressed for a little longer, or try MF.
The help is shown in ML menu, at the bottom of the screen (the fine print). What does it say? It's dynamic (i.e. not a fixed text).
-
Help text: Says 'assign AF to * button' (done)
Still get 'Hold on' during any length of hold of trigger. Now it locks up again with strange messages (see images). Batt pull resets. No image saved. All imaged viewed are scrambled text (see image).
(https://i.ibb.co/pbYsJz2/IMG-3051.jpg) (https://ibb.co/pbYsJz2)
(https://i.ibb.co/yQzPNKM/IMG-3052.jpg) (https://ibb.co/yQzPNKM)
(https://i.ibb.co/jwdjxJS/IMG-3053.jpg) (https://ibb.co/jwdjxJS)
-
Small steps required, timbytheriver!
JPG? Set image quality to RAW only. Review time 5 seconds. Make sure powersave is > 1 minutes. And set color space to sRGB. Make sure to use cam's M mode. For starters: ISO 200-800, Tv = 1/30, open aperture. Lens AF off. Single picture mode.
Restore ML default settings, reboot. Enable silent.mo, reboot. Enter Shoot tab, enable Silent pics with default settings. Enter LiveView mode and press half-shutter.
If it works (check pic on computer) enable FRSP and retry. Report back.
-
@Walter Schulz Thanks for the tips. Dashing out now – but will pick this up again tomorrow.