Show Posts

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

Messages - g3gg0

Pages: 1 [2] 3 4 ... 112
Reverse Engineering / Re: Sensor Factory Calibration
« on: December 14, 2018, 09:53:19 PM »
The module requires code cleanup and some work, currently it is only a tool that is not good for official publication.

i would head towards reading and writing the properties if i were you.
this makes the code more robust and then would be an equivalent to the SPT tool.
but that requires thorough testing of course.

We can also use something like two_add engine to speed up the processing. But is it necessary?
nah, if you update properties you wont run it every day.

Current limitation - I can change the black level of the column by 1. So some of the columns still have 1024.5 or 1023.5.
as the offsets are integer, odd numbers aren't possible. at least in-camera ;)
would have to use float-files which are a bit overkill.

Reverse Engineering / Re: Sensor Factory Calibration
« on: December 14, 2018, 09:36:31 PM »
on 5D3 the properties with size 0x5E0 are being read by function "GetHivshdIRparameter(Po=%ld[%ld])"
it is later written to HIV by first writing this engio list: (0xBC * 8 = 0x5E0)

and then copied there:

and the 0x5CC0 sized ones are used for
stru_45294.edmac_0x18_address_HivShd = get_dark_offset(param_iso, v4);

Reverse Engineering / Re: Sensor Factory Calibration
« on: December 13, 2018, 01:28:55 AM »
doing a quick analysis on 5D3.113, it is the TUNE property table, starting at 0xF8B20000

you can dump it like that:
    PropertyEditor.exe 0xF8000000-0xF8FFFFFF.BIN 0xB20000 0x2E0000

and it will spit out a property dump like this:

where you can see that this memory location is for properties 0x0101004D-0x0101007C with 5936 uint32 values.
before them there are properties 0x0101007E-0x0101008F with 376 uint32 values also looking like a offset table.

getting their value is as simple as reading a property. no need for memory locations.
modifying them, well, i would stick to patching it in-memory :)

good find!

would really be interesting if this is the FPN compensation table we could simply pass to MLV files.
(well not simply, a dark frame must be calculated from these values)

Reverse Engineering / Re: Sensor Factory Calibration
« on: December 13, 2018, 01:08:02 AM »
1) so you found the location where the vertical ADC offset tables for FPN correction are?
2) these probably were calibrated in factory and written into the flash only once?
3) you updated values in RAM to achieve better FPN reduction - for CR2? or did it even affect raw video?

would be interesting to use these tables into a MLV and creating the DARK frame from it :)

General Help Q&A / Re: Unknown Block errors PLEASE HELP
« on: November 29, 2018, 08:05:50 PM »
a 83 minute movie shot with ml raw?

General Development Discussion / Re: What more can/should we do with ML?
« on: November 28, 2018, 11:16:10 PM »
OK then, here's my wish list.

Dear Santa,

...give me three clones of myself.
one for taking care of my family.
one for doing my main work.
another one for working on ML again.

so i can finally relax and enjoy life :)

short: he cant keep up maintaining the german translation of the ML manual.
the site is still up, but wont be updated.
finally some people said thanks for his effort.

vielen dank für die arbeit die du da reingesteckt hast!

General Help Q&A / Re: Magic Lantern Logo
« on: October 14, 2018, 08:19:24 PM »
or use inkscape. works like a charm.

Raw Video Postprocessing / Re: Broken MLV file
« on: September 21, 2018, 09:53:30 PM »

a) your .idx is defect - delete the .idx file before running mlv_dump
b) your mlv_dump is very old - get a recent version of mlv_dump

should look better then :)

General Help Q&A / Re: Unknown Block errors PLEASE HELP
« on: September 21, 2018, 06:54:08 PM »
@g3gg0 - No, that build doesn't work with this file:

Code: [Select]
./mlv_dump.osx -F 3 --dng M15-0904.MLV
FIX BUG #3 [active]

 MLV Dumper

Mode of operation:
   - Input MLV file: 'M15-0904.MLV'
   - Decompressing before writing DNG
   - Enforcing 14bpp for DNG output
   - Using output path 'M15-0904_' for DNGs
   - Convert to DNG frames
   - Output into 'M15-0904_'
File M15-0904.MLV opened
File M15-0904.M00 not existing.

Vertical stripes correction:
  1.00000  1.00290  0.99698  1.00259  0.99626  1.00102  0.99782  0.99646
Cold pixels : 0                             
Unknown Block: %%, skipping
[ERROR] Invalid block size at position 0x7dd46afe
Processed 777 video frames at 24.00 FPS (32.38 s)

General Help Q&A / Re: Unknown Block errors PLEASE HELP
« on: September 21, 2018, 12:16:33 PM »

Camera Emergency Department / Re: Canon 5d Mark II Bricked?!?!
« on: August 16, 2018, 11:55:30 PM »
first of all - you never installed ML onto your camera or replaced your firmware.
ML only enables a "boot from card" flag in the camera and enables a "boot flag" on the card where ML binaries are installed.
your camera's flash doesnt contain any code from ML.

did you use a new card?
can you make a video?

In mlv 2.0 specifications, lens name is a optional null terminated string, so maybe option number 2 is to be preferred to avoid interference with other processing tools?

absolutely. this is my recommendation.
in MLV strings dont *have to* be null terminated as you pointed out correctly.

Share Your Videos / Re: Lunar Eclipse, 3K RAW and ETTR
« on: July 30, 2018, 10:39:30 AM »
cool video, i like the whole composition :)

Share Your Photos / Re: Mars
« on: July 29, 2018, 06:03:33 PM »
Than I export to uncompressed avi, which is 8 Bit. That´s what I stack with autostakkert.

any reason why to switch to 8 bits alreary there? i directly used TIFF files to keep most information for autostakkert

Share Your Photos / Re: Mars
« on: July 29, 2018, 10:32:03 AM »
Could you share you camerasettings, please? I had the best results with ISO6400 F 1/5.6 2s on my 6D with 300mm-lens (CR2). Video was not possible.

1. MLV, 1920x1080, ISO200, 1/33, Maksutov MTO-11CA
2. mlvfs -> lightroom -> TIF (without editing)
3. ~4200 frames into autostakkert 3.0.14 to stack 60% of the images
4. used fitswork to apply a handcrafted deconvolution filter
5. applied some gamma correction

my first real try of this toolchain.

the total lunar eclipse was close to impossible to shoot properly.
had to use FPS override to 500ms exposure time to see a faint image of the moon with ISO3200.
then shot a MLV with 1000ms exposure time, but with the moon being imaged only partially (crop_rec)
but autostakkert has trouble detecting the motion properly :(

Share Your Photos / Re: Mars
« on: July 28, 2018, 10:43:24 PM »
didnt have much luck either.
could see the moon the last 30 minutes, but with my gear it was all too dark to capture properly.

here a 2500-image merge of the moon right after it left the umbra

ive just seen that there is some again fixed-length implementaition in manual_lens_info_64byte branch and manual_lens_info.

is there any tool yet that processes the ELNS block?
i still want the name to be dynamic - just like some other blocks are.

Share Your Photos / Re: Mars
« on: July 22, 2018, 03:04:20 PM »
this is so impressive. wow. then i might try my cassegrain and see what i can get with it.
any idea/estimation if the MTO-11CA (russentonne) is capable of getting something useful?
or is its 1000mm focal length lost hope and i do better saving the time?

Share Your Photos / Re: Mars
« on: July 22, 2018, 02:45:01 PM »
holy crap. this singe MLV and the resulting picture right next to it blew my mind.
didnt expect that someone could recover so much detail from such single frames...

Share Your Photos / Re: Mars
« on: July 20, 2018, 01:50:54 PM »
how do you compensate the atmospheric turbulences?
when i look through my maksutov mto-11ca i quickly tend to forget all ideas about shooting photos of planets.

Raw Video Postprocessing / Re: Debayer without interpolation?
« on: July 18, 2018, 11:07:44 AM »
as far i can understand these fragments, the idea is to
 - shoot [n] images
 - detect motion between them (optical flow)
 - overlay the raw images accordingly

if you have some motion now, due to vibration etc, different bayer pixels overlay now and you have a good estimate what R, G and B is at a specific "image" location.
wonder if it was meant to shift the sensor automatically (didnt hasselblad do this already using piezo?) or if the unsteady hands would deliver the required motion.
latter makes sense if you have motion *estimation* because with piezo you already know the motion.
we could capture "short 4-frame MLV files" like with silent picture and the post can be done on the pc, but...

*AFTER* someone has proven that it makes sense ;)

Hehe, it probably can't. Question. Cr2 metadata. Is that all gathered after a picture is taken? Is that also the case with mov recordings? I mean, the wb state in liveview will record mov files with awb as seen I suppose so where is that info pending before pressing record button? Aewb task as a1ex says?

i remember that i somewhen looked into this code, but hardly can remember anything.
had some stuff in the register map on wikia, but this was just the engine registers that calculated WB data.

i am still confused how an algorithm could reliably detect the white balance, not knowing
if the image contains a blue-ish picture on a ivory colored wall, or a window on a bright white wall where you can see the blue sky through :)

Pages: 1 [2] 3 4 ... 112