Just to confirm, it works *without* the ui_raw_hook_sleep modification?
Honestly, seeing people do cool things with it is the best reward for working on this stuff.
Very nice. Have you thought about posting these outside IG?
The moon + clouds definitely gets bright at the end. May be able to offer suggestions if you post the log file.
clock -sync luar set_lcd_display(0) --switch of display during taking photosluar set_mf(1) --set focus to manualluar set_focus(1495) --set focus distanceluar set_capture_mode(4) --set to AV modeluar set_user_av96(320) --set AV value #AV modes: 3.2 3.5 4.0 4.5 5.0 5.6 6.3 7.1 8.0# 320 350 380 410 440 470 500 530 560luar set_ev(-96) --set EV value#EV modes: -192 -160 -128 -96 -64 -32 0 32 64 96 128 160 192# -2 -12/3 -11/3 -1 -2/3 -1/3 0 1/3 2/3 1 11/3 12/3 2luar set_iso_mode(80) --set ISOluar set_raw_nr(0) --auto dark framers "D:/sunset/input/" -script=D:/sourcecode/rawopint_rs.lua -shots=600 -int=15luar sleep(2000)d A/rawopint.csv D:/sunset/
clock -sync luar set_lcd_display(0) --switch of display during taking photosluar set_mf(1) --set focus to manualluar set_focus(1495) --set focus distanceluar set_capture_mode(5) --set to manual modeluar set_user_av96(320) --set AV value #AV modes: 3.2 3.5 4.0 4.5 5.0 5.6 6.3 7.1 8.0# 320 350 380 410 440 470 500 530 560luar set_tv96_direct(-256) --set TV value to 6.3sluar set_iso_mode(200) --set ISOluar set_raw_nr(0) --auto dark framers "D:/sunrise/input/" -script=D:/sourcecode/rawopint_rs.lua -shots=600 -int=15luar sleep(2000)d A/rawopint.csv D:/sunrise/
I have two G1x and no cap. But I bought them used.The original cap of my M3 has a notch so that the switch is not switched.I don't think your cap originally belongs to the G1x. It makes no sense for me to removing the cap when using the internal flash.
I actually don't like the facebook company... I don't use Whatsapp or Facebook nor have a private IG account but I found a cool python Instagram Private API (https://github.com/adw0rd/instagrapi) and so I started with IG. What other platforms would you suggest?
Yes I will post the log.
Hmm, youtube would let people see full resolution, without the square letter box. Even 4k once you get the g1x set up. But probably not something people would regularly watch unless it was embedded somewhere else.
Despite that big blown-out looking area around the moon at the end, the over_weight column is all zero, so overexposure as measured by the script never got to the point where it influenced exposure. The highest over exposure was at the very end, around 0.17%. If I've done the math right that would be about ~120 pixels square, or roughly 3x the size of the moon at the reported 43.8 EFL.If you want the moon to trigger overexposure protection, you'd need a much lower over_thresh_frac, 0.1% or lower. Beware that setting this very low can trigger oscillations and run into precision issues. And of course, if you did correctly expose the moon at night, the rest would get very dark.
If you want more of the bright area to be considered overexposed, you could increase over_margin_evExposure was mostly driven by underexposure, with under_frac ranging from 8% to 40%, and under_weight never below 65. Given that the bottom ~half of your scene is going to be very dark a lot of the time, you probably want to keep the influence of underexposure fairly low. You could turn it off completely by setting under_thresh_frac to 0, or some combination of increased under_margin_ev and under_thresh_frac.For a scene like this, it might be nice to have the meter not measure the bottom, to bias the exposure for the sky and snowy peaks, but the script currently only allows setting size, not position.
-- meter rectangle, centered in active area self.meter_left = rawop.get_active_left() + rawop.get_active_width()/2 - self.meter_width/2 self.meter_x_count = self.meter_width/self.meter_step self.meter_top = rawop.get_active_top() + rawop.get_active_height()/2 - self.meter_height/2 self.meter_y_count = self.meter_height/self.meter_step/3 --only upper 2/3 counts
Updated notebook and htmlized output for the sunset log attached.
I don't think it is a good idea to trigger overexposure in this situation as the rest would get very dark. I think this is the limit of my setup at the moment...
Since three exposure times (inkl dark frame) would get too long for HDR, I think it is good enough for the moment.
The real problem I see is (since the over_weight parameter always remains the same.) in daylight condition the overexposure could trigger too easily with some bright clouds or snow reflection.Maybe the highlight clipping in clouds and snow are a better way to define over_thresh_frac and over_margin_ev.
hmm.. I already did that: the time lapse in the final videos includes only the upper 2/3 of the frame. (I cut the village out of the picture.) And because the missing part did influence too much the metering I excluded it.line 703ffCode: [Select] -- meter rectangle, centered in active area self.meter_left = rawop.get_active_left() + rawop.get_active_width()/2 - self.meter_width/2 self.meter_x_count = self.meter_width/self.meter_step self.meter_top = rawop.get_active_top() + rawop.get_active_height()/2 - self.meter_height/2 self.meter_y_count = self.meter_height/self.meter_step/3 --only upper 2/3 counts
I'm not sure I follow. over_weight was 0 in the sunset run because of the particular conditions. It was triggered quite a bit in the sunrise (https://www.instagram.com/p/CPUtoF8HpuA/ i think), but underexposure still pushed the exposure quite high.
1148 -- smooth out rapid changes1149 -- TODO smoothed fraction should be configurable
930 local last_ev_change931 local last_ev_change_decimal932 local median_filter_intensity = 5 -- this is a magic number!! it has to become an input parameter933 -- allowed values: 0: no filter, 9: max filter (>10 and <0 not allowed here) expample:934 -- 1: ev_change = 10% * last_ev_change + 90% * ev_change -> low moving average filter intensity935 -- 8: ev_change = 80% * last_ev_change + 20% * ev_change -> high moving average filter intenisty
940 last_ev_change = self.ev_change941 last_ev_change_decimal = self.ev_change_decimal
949 last_ev_change = 0950 last_ev_change_decimal = 0
1126 -- smooth out rapid changes exponential moving average implemented1127 if self.smooth then1128 local ev_change_smooth = (last_ev_change * 10 + last_ev_change_decimal) * median_filter_intensity + (10 - median_filter_intensity) * ev_change * 101129 ev_change = ev_change_smooth / 1001130 last_ev_change_decimal = ev_change_smooth % 100 / 10 -- not sure if modulo works this way in lua1131 end1132 self.ev_change = ev_change1133 self.ev_change_decimal = last_ev_change_decimal
Started by rosspian
Started by reyalp
Completed and Working Scripts
Started by Stephan
« 1 2 »
General Help and Assistance on using CHDK stable releases