EOS M3 porting - page 37 - DryOS Development - CHDK Forum supplierdeeply

EOS M3 porting

  • 657 Replies
  • 230044 Views
Re: EOS M3 porting
« Reply #360 on: 16 / June / 2017, 09:48:41 »
Advertisements
Hi everybody!
I'm really happy to see a port of CHDK for EOS M3. This is my first camera and I tried to find a solution for intervalometer without success, until I find CHDK. I'm using the 1.2 firmware version and I could use intervalometer scripts successfuly!

Thank you so much for everyone involved in this port! :)

I would like to point that when the camera is in the "scene intelligent auto", the CHDK elements blinks a lot on the screen, and is almost impossible to use. Is this happens to you too? Is there a way to avoid this?

Thank you!!

*

Offline reyalp

  • ******
  • 12537
Re: EOS M3 porting
« Reply #361 on: 17 / June / 2017, 00:14:08 »
I would like to point that when the camera is in the "scene intelligent auto", the CHDK elements blinks a lot on the screen, and is almost impossible to use. Is this happens to you too? Is there a way to avoid this?
Unfortunately, it's normal for the CHDK UI to flash every time the Canon UI updates. If you need to use the CHDK menus, your best option for now is probably to switch to playback mode or a shooting mode like M that doesn't update so much.

If you have the 120f firmware, a firmware dump would be appreciated. You can use the Canon Basic dumper: http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper
Don't forget what the H stands for.

Re: EOS M3 porting
« Reply #362 on: 24 / June / 2017, 07:15:39 »
Hi reyalp, I've just upgraded my M3 to 120f. I followed the instructions on the dumper page (copied both files onto the SD Card, made it bootable and set the script flags) but I don't know how to execute the script - so nothing is written to the card.

Does CHDK support firmware 120f - or only 1.0.0?

*

Offline Ant

  • ****
  • 436
Re: EOS M3 porting
« Reply #363 on: 24 / June / 2017, 10:57:39 »
but I don't know how to execute the script - so nothing is written to the card.
Switch to playback mode and press "Set" button.

Quote
Does CHDK support firmware 120f - or only 1.0.0?
Why you don't read the first message in this topic?


Re: EOS M3 porting
« Reply #364 on: 25 / June / 2017, 15:33:41 »
« Last Edit: 25 / June / 2017, 15:40:09 by erspark2002 »

Re: EOS M3 porting
« Reply #365 on: 27 / June / 2017, 13:21:30 »
I made a sunset time-lapse test Video with Canon EOS M3. Unfortunately, the SD card was at the end so full that the sunset is not complete. Script works very well with M3. I set the ev_shift to -1/4. Lens was EFM 15-45mm. Next time I will run the script to high ISO values to see if the M3 has same problems as my other cams.

M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline lapser

  • *****
  • 1093
Re: EOS M3 porting
« Reply #366 on: 27 / June / 2017, 16:28:20 »
I made a sunset time-lapse test Video with Canon EOS M3. Unfortunately, the SD card was at the end so full that the sunset is not complete. Script works very well with M3. I set the ev_shift to -1/4. Lens was EFM 15-45mm. Next time I will run the script to high ISO values to see if the M3 has same problems as my other cams.
WOW! That's incredibly beautiful. What aperture did you use? Did you use a filter?

I've attached a copy of rawopint.lua with set_sv96(sv) replaced (at line 1055) by the code I've been using for years without problems. Will you see if it fixes the ISO problem on the G1X if you have time? Run the script in continuous mode.
Code: [Select]
-- *****lapser sv test
--   set_sv96(self.sv96)
  set_prop(props.DELTA_SV,self.sv96-get_prop(props.SV)+get_prop(props.DELTA_SV))
  set_prop(props.SV,self.sv96)
-- *****lapser sv test
I did my first time lapse with the EOSM. The script just holds the shutter down in continuous mode with 20 second exposures at night, but it works. I'm working on other scripts too, using reyalp's fantastic hook code.
/>
« Last Edit: 27 / June / 2017, 16:34:00 by lapser »
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

Re: EOS M3 porting
« Reply #367 on: 28 / June / 2017, 04:22:32 »
WOW! That's incredibly beautiful.

Thanks.
I only used the RAW from the cam, developed with DPP and made the video with VirtualDub. No farther processing on this video.

What aperture did you use?

I used f5.6. All parameter can be seen in the log file in Reply #365 and the AV value also in the plot (OK, the scale is bad for this information).
This is another great think about rawopint. Everything gets logged for later investigation. Ok I added the temperature of battery.

My plan was to run the script into darkness but I forgot that the size of RAW Data was about double as on my G1x so I run out of memory with my 32G Card.

I have one 128G Card but if I want to use it on M3, I have to format the card into FAT32 (If I understand correctly).

Did you use a filter?

No. I was already afraid to use no ND filter. With my G1x it is always switched on when I photographed against the sun. But the sun was already very low. In a higher sunshine I would not do it with the M3. The sensor temperature remained below 45 degrees Celsius (I know the temperature is an average and not a spot). At the G1x I had runs that went up to 80 degrees Celsius with no problems.
Have you ever changed the ND filter of the G1x with your time-lapse in the script?

I've attached a copy of rawopint.lua with set_sv96(sv) replaced (at line 1055) by the code I've been using for years without problems. Will you see if it fixes the ISO problem on the G1X if you have time? Run the script in continuous mode.
Code: [Select]
-- *****lapser sv test
--   set_sv96(self.sv96)
  set_prop(props.DELTA_SV,self.sv96-get_prop(props.SV)+get_prop(props.DELTA_SV))
  set_prop(props.SV,self.sv96)
-- *****lapser sv test

I always run in continuous mode…
I think this is what we have discussed here https://chdk.setepontos.com/index.php?topic=11081.100
and have tested here https://chdk.setepontos.com/index.php?topic=12165.msg123576#msg123576
But I will try it on the weekend with your modifications again. Do you use only RAW or the JPG from the cam?

I did my first time lapse with the EOSM. The script just holds the shutter down in continuous mode with 20 second exposures at night, but it works.
It is really great. I'm really jealous about these…
Unfortunately I live in a region with a lot of light pollution. Have to do long trips.
Which ISO do you use?
You used the EFM 22mm. I would prefer wider angle. I have an EFM 15-45 and an EFS 10-18mm. But both lenses have a great initial aperture. I’m thinking about Walimex/ Samyang 12mm F2.0 or 14mm manual lenses.


I'm working on other scripts too, using reyalp's fantastic hook code.
Interesting.  Hope we hear more about this.
Basically I am very satisfied with rawopint. Sometimes it gets in oscillation (especially with waves). In this case, I am able to fix it https://chdk.setepontos.com/index.php?topic=12790.0
I think it is possible to fix it in the script but I haven’t found the time to go deeper into it.

Perhaps interesting information of the M3. In fast mode (stay in half press) the aperture can be changed (not in continuous mode). This could be used especially with time-lapse in the transitions day to night and vice versa. I wanted to try out a long time, in which steps the aperture can be changed. Probably but not as with the ISO in 1 / 96EV steps.
 

How do you power the M3?
https://chdk.setepontos.com/index.php?topic=13164.msg133204#msg133204
https://chdk.setepontos.com/index.php?topic=13056.20
« Last Edit: 28 / June / 2017, 04:28:09 by c_joerg »
M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd


*

Offline lapser

  • *****
  • 1093
Re: EOS M3 porting
« Reply #368 on: 28 / June / 2017, 12:52:01 »
Don't want to clutter the EOSM topic too much with scripting stuff. I'll start a new topic soon.

Yes, you need to format with FAT32. I use a block size of 32,768 for my 128 and 256 gb SD cards.

I always use the max aperture on the G1X for sunsets, because it gets dark at the end! I also find that when you reduce the G1X aperture, the sun shows radial diffraction spikes, and doesn't look round. Hopefully, that will be better with M3 lenses.

My script does switch the ND filter in and out automatically based on brightness level. A script input parameter specifies the ND filter density, around 294 on my G1X. I adjust the exposure by this amount, and adjust the next shot to match the brightness before the filter switch.

I always save RAW files, if possible, and process with Lightroom.

I've used a fish eye lens with an adapter on the EOSM, but haven't tried it with the M3 yet. Here's a a time lapse with that lens, which will give you the idea of how it looks:
https://www.youtube.com/watch?v=O7s6p-p1mas

I haven't worked with aperture changes yet. The G1X ND filter switching works pretty well instead. But I may want to look into changing the aperture with the M3. I may just do one large change at sunset (or sunrise), simulating an ND filter switch. It's good to know it works in half press.

I did a script that zoomed the SX50 a specific amount with a full press. It might be interesting to change the zoom during a time lapse if it works with half press.

I noticed those small oscillations in brightness and fixed them in the script. Basically, I don't adjust exposure until it's around 5 ev96 off. I gradually increase the amount of each adjustment from 0 to 3 ev96 until I'm 48 ev96 off, then adjust to 48 off after that. It's like driving a car. You turn the wheel more and more towards the center of the road as you near the edge. Then you turn the wheel as much as needed to keep from going off the road.

See you in another topic soon!
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

Re: EOS M3 porting
« Reply #369 on: 28 / June / 2017, 13:49:29 »
I always use the max aperture on the G1X for sunsets, because it gets dark at the end! I also find that when you reduce the G1X aperture, the sun shows radial diffraction spikes, and doesn't look round. Hopefully, that will be better with M3 lenses.
I notice this as well on the G1x.
I adjust the exposure by this amount, and adjust the next shot to match the brightness before the filter switch.
But this doesn’t work on continuous mode or?

I noticed those small oscillations in brightness and fixed them in the script. Basically, I don't adjust exposure until it's around 5 ev96 off. I gradually increase the amount of each adjustment from 0 to 3 ev96 until I'm 48 ev96 off, then adjust to 48 off after that. It's like driving a car. You turn the wheel more and more towards the center of the road as you near the edge. Then you turn the wheel as much as needed to keep from going off the road.
Interesting! I tried something similar some time ago. I didn't Change anything between -2 and 2.
https://chdk.setepontos.com/index.php?topic=11081.msg124334#msg124334
I then gave up, because I still missed many of the foundations.
Maybe you could post your changes here.
https://chdk.setepontos.com/index.php?topic=12697.0
It would certainly be an improvement.
See you in another topic soon!
Definitely....

M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

 

Related Topics