Show posts

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

Show posts Menu

Messages - josepvm

Your request is not possible. If ML is not loaded, it cannot monitor a button press to activate itself.  And no option in stock Canon menus allows you to load ML on demand.
HTP reduces exposure (by lowering ISO) in one stop to preserve highlights.  I you shoot raw, this is the only effect you see, a reduced exposure. If you shoot jpg the camera also pushes the shadows (using a modified tone curve to develop the jpg in camera), but, as a side effect, the shadow noise gets pushed, too. There is no improvement in dynamic range.

So yes,  If you shoot raw you can do the same reducing the exposure to avoid clipping highlights (Magic Lantern's AutoETTR module is a highly accurate tool to do this) and pushing the shadows in post.
That's not the way it works. Canon"s HTP does not blend exposures, it makes a single shot, but lowers the exposure value to preserve highligths, at the expense of having more noise in the shadows.

And it has been explained many times in this forum that the postprocessing of DualISO images cannot be done in camera, because it requires intense computation, and that's too much work for the tiny embedded ARM processors our cameras have.
As far as I know, ML provides unix style shell scripts (saved in the memory card along with the image files) to make easier the postprocessing of EV bracketed series with Enfuse in your computer. But I have not heard before anything about generating enfused previews in camera.
General Chat / Re: I'm just curious
September 08, 2017, 09:57:45 PM
5D3 sensor is a pure analog device, that feeds analog image data to an external chip that converts it to digital data.

But 5D MkIV sensor has on-chip A/D converters, so the output is digital data.

Conclusion: you can't use a 5D MkIV sensor in a 5D MkIII camera.

If you want to use a hand held meter with Dual ISO, disable Auto-ETTR (or set it to be manually triggered only when you want it, with the "set" button, or a double press in the shutter button). And manually adjust your exposure, according to your hand held meter,  in order to not clip highlights for the lower ISO.  The higher ISO value of DualISO will take care of the shadows.
Raw Video / Re: Need help with Good Raw
April 07, 2017, 05:11:24 AM
@ josepvm
you did not understand me correctly i said i want exactly this quality of this guy
and i have the same camera also i should get the same result..... how did he do it?

He did it linking multiple very short shoots, each one with a lenght of only few seconds. This way he is recording using only the camera's memory buffer, that is a lot faster than the SD card interface, but has a very limited capacity, only a few seconds of Full HD raw video.

If you want to shoot with the same quality for longer times, you cannot do it with the slow card interface your camera has. You need a camera with a CF card interface.

50D, 5D MkII and 7D MkI have a CF card interface capable of raw recording at 80 MB/s if you use a very fast CF card. This allows continuous Full HD 14 bit raw recording at 20 FPS.
The 5D Mk III has an even faster CF interface, capable of 100 MB/s. This allows continuous raw recording at Full HD 25 FPS
Raw Video / Re: Need help with Good Raw
April 06, 2017, 10:30:50 PM
You can not record Full HD raw continuosly with a 600D, no matter how fast your SD card is. The SD bus in this camera is limited to 21 MB/s, and Full HD raw requires at least 80 MB/s. There's nothing you can do to change this fact.
With a 600D you will be able to record Full HD raw only for a few seconds, until the camera buffer gets full of data.    After that point the recording will fail.

Quote from: dfort on March 07, 2017, 01:18:22 AM
While doing this video I discovered that a 50mm prime lens was showing a dramatically different exposure from a 17-55mm zoom even though both lenses were set at the same focal length and f/stop. Not really a part of this test but worth showing--hope I didn't open up yet another can of worms.

Perhaps related to this old issue?

General Chat / Re: Focus issues with canon 50d and ML
February 24, 2017, 09:22:52 AM
50D cannot film video without ML. But in liveview this cam has only contrast-detect AF, and this method is slow and not well suited for video, it cannot keep in focus a moving object. So you will need to focus manually.
Camera-specific Development / Re: Canon EOS M
February 22, 2017, 08:14:31 PM
Use a recent ML build for EOS M. A workaround for this problem was implemented in nightly builds months ago.

So, for 50D:

loc_ff8166b4: ; 14 refs     <  -------------------- (get_current_task)

ff8166b4: e59f0020 ldr r0, [pc, #32] ; ff8166dc: (00001a74)
ff8166b8: e5900000 ldr r0, [r0]
ff8166bc: e3500000 cmp r0, #0
ff8166c0: 059f001c ldreq r0, [pc, #28] ; ff8166e4: (00001a70)        <--------
ff8166c4: 05900000 ldreq r0, [r0]
ff8166c8: 05900040 ldreq r0, [r0, #64] ; 0x40

Can I assume that current_task = 0x1A70 ?
Camera-specific Development / Re: Canon 7D Mark II
November 08, 2016, 10:20:06 AM
hesham007 is probably talking about this:

That is not an ML official release announcement, and does not show ML running on 5D Mk IV.  It only shows the portable binary test, that runs on many cameras that do not have a ML port for them.

And as A1ex said, the first ML port for Digic 6/6+/7 cameras probably will be the 80D port. Porting ML to 7D Mk II is a lot more challenging, because of the dual Digic.

Camera-specific Development / Re: Canon 50D
October 21, 2016, 11:41:54 PM
Yes, it's a known issue of recent nightly builds for 50D:
Camera-specific Development / Re: Canon EOS M
October 06, 2016, 07:59:58 AM
Not in Av mode. But you can do that in Auto ETTR module, using M mode.

ETTR exposure calculation is slower than Canon autoexposure, but much more precise.
Quote from: xorpi on October 03, 2016, 03:27:24 PM

My recommendation:

Optimize and finalize dual-iso (without loosing resolutions and details) as format for ML platform with dynamic range boost.
With that use AutoETTR system for dual-iso  (as replacement for HDR Bracketing) - Dual-iso as native format of the Magic Lantern firmware.

That's impossible.  Dual-ISO uses half of the sensor rows to capture extreme shadows and highlights. And this produces an unavoidable loss of resolution on those areas. There's no way to optimize anything to change this fact.

You are asserting that Dual-ISO is not optimized and not prepared for serious work, but you don't have any idea of how Dual-ISO works, and It seems that you don't care at all of trying to understand it.
Dual-ISO is optimized and finished enough for a lot of users here, we use it frequently, and take great advantage of it.  But Dual-ISO is not a replacement for bracketing when you need to use the full resolution of your camera sensor.   

And you are not providing any data and any help to the developers to improve the flaws you say Dual-ISO has.

Integrate various modules from other developers on the forum directly to the Magic Lantern - great one is Focus Stacking + Autofocus + Intervalometer.

Experimental modules need to be tested and fully implemented for all ML supported cameras, before being added to nightly builds.  Otherwise there is a big risk of bricking cameras. And I suppose you will not be happy if you see your camera bricked...

But you have said in another thread that you don't care at all about helping the ML community with programming, building, and testing experimental code, you only want a finished product, for free, and in less than a year ...

So the conclusion is: you are a troll, and with your posts you are only making the developers to waste their valuable time. And you are using this forum to insert links to your photo galleries, advertising yourself for free.
You are not apporting anything good to this comunity, so don't expect to receive any consideration or any help here. 

This is the last time that I waste my time also, replying to your messages.

Chromatic aberration is a defect of the lens. How could Dual-ISO introduce chromatic aberration?

And some loss of vertical resolution in extreme shadows and highligths is an unavoidable tradeoff of the Dual-ISO method. But the loss is not very high, and the overall result is a lot better than having all the shadow's noise that you get without Dual-ISO.

But if you need maximum detail, the solution is simple: don't use Dual-ISO and shoot bracketed exposures instead.
Using a card reader in your computer, delete "autoexec.bin", and the ML folder on your CF card. Then download the latest "nightly build" for 50D, extract all the content from the file and copy it to your CF card. And try to start the camera with that CF card.

If the first boot warns you about ML missing files, power off the camera and try to start again.

Once you have ML running, you can uninstall it if you want, launching the "firmware update" from Canon's menu, and following the instructions on the screen.
So what are you doing here in ML forums?  Your camera already allows you to take photos without having ML installed.
Modules Development / Re: Full-resolution silent pictures
September 01, 2016, 11:27:15 PM
Quote from: IBIRRU on September 01, 2016, 09:15:49 PM
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.
Quote from: hillibilli on August 31, 2016, 08:00:19 PM
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.
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" 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.

I have found them for you:


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:

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
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
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                                < --------------
ff1e1a3c: 0000017b andeq r0, r0, fp, ror r1
ff1e1a40: ff1e149c ; <UNDEFINED> instruction: 0xff1e149c
"FA_CaptureTestImage Fin":

So capture_err_time_addr = 0xff1e1a38


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