Messages

How do you test Canon basic scripts?
Is there a syntax check or debug facility?
Or do you have to take out the card every time and try again?

On my M100, the basic scripts only start every second time (on average).
There has to be some kind of temporal behavior.

Unfortunately nothing happens. Have I made a mistake or are we out of luck? Maybe there's a different combination required to trigger the script?

Sure the SD Card is not exfat?
You need FAT.

Unfortunately v1.1 means that 1.0 is probably lost for now, considering how many of those were shipped / people wanting to upgrade.
I keep my R v1.0 backup as a relic

I'm not very familiar with ML yet. But from CHDK I know that you can do a dump of the firmware in the camera. Isn't that possible with ML?
If the camera supports Canon Basic, it should be possible ...

Does the R5 support Canon Basic? 

Mystery: the BOARD temperature appears closer to the value ending up in EXIF, at least in the first tests, but since it's not reported during photo capture (on 60D I've had two instances where the indicator showed -128 before and after taking a picture), that gives me some doubts.

On my EOS M3 I have 3 temperature values with CHDK. They are named Optical, Sensor and Battery. But also without any lens I got an optical temperature. Maybe the optical is the board temperature. The Sensor temperature is always much higher than the optical temperature so I expect that is really the sensor. I had max sensor temperature from around 70 degree.
The EXIF temperature matches exactly with the optical temperature. I'm wondering, why Cannon reports this lower value and not the sensor temperature in the EXIF data.

As long Canon Basic is available...
https://chdk.setepontos.com/index.php?topic=13489.10

and the camera takes shot after shot perfectly with only 1sec between images,

I think that's the problem. 1s between images is not always enough. You should compare all EXIF timestamps from your images. May be the first and last is enough.

Not sure if this problem still happens
https://www.magiclantern.fm/forum/index.php?topic=21617.msg203896#msg203896

Seems to be normal at Samyang....
I had the Walimex Pro (same as Samyang) 14mm f2.8 AE three times. It was exchanged twice. Then I had one with another controller (recognizable by the serial number). But this was decentrally. Now I have the manual one.

I have now managed to port the script to MATLAB. Quite a few changes are necessary. Especially in the operations of 2-dimensional and 3-dimensional matrices. The most important thing was that I learned a lot about the algorithm.

I am really impressed about the script. It works much better than CS6. 
Maybe I made a mistake with the porting. So far I have not carried out an algin. I'll port that next week.

Here is the MATLAB version of the script and the result from 70 images
https://drive.google.com/open?id=1qaQAEvg7g_Zllbq7BDPHxjgqIYSj3zJB

This is the result from HeliconFocus. HeliconFocus crops very strongly and the viewing angle is different

Well, assuming you are using Windows, Octave can be simply unzipped and ran; no need to install it system-wide.

Nothing is simply at beginning

Code Select Expand


E:\New\Stack_Test\M3_100mm_Stack_Test\LR>C:\Tools\octave\mingw64\bin\octave-cli focus_stack.m IMG_5051.jpg IMG_5052.jpg IMG_5053.jpg
warning: addpath: __OH__/share/octave/packages/image-2.10.0: No such file or directory
warning: called from
    load_packages_and_dependencies at line 48 column 5
    load_packages at line 47 column 3
    pkg at line 461 column 7
    focus_stack at line 12 column 1
Processing IMG_5051.jpg .error: could not find any INDEX file in directory __OH__/share/octave/packages/image-2.10.0, try 'pkg rebuild all' to generate missing INDEX files
error: called from
    describe>parse_pkg_idx at line 94 column 5
    describe at line 59 column 40
    pkg at line 555 column 43
    __unimplemented__>check_package at line 540 column 15
    __unimplemented__ at line 321 column 11
    focus_stack at line 44 column 7


I comment that out

Code Select Expand

   
# pkg load image


Code Select Expand


E:\New\Stack_Test\M3_100mm_Stack_Test\LR>C:\Tools\octave\mingw64\bin\octave-cli focus_stack.m IMG_5051.jpg IMG_5052.jpg IMG_5053.jpg
warning: function name 'show' does not agree with function filename 'E:\New\Stack_Test\M3_100mm_Stack_Test\LR\focus_stack.m'
error: 'im' undefined near line 16 column 10
error: called from
    focus_stack at line 16 column 3

   

Haven't touched Matlab in years, but you might be able to run the scripts by commenting any "pkg load" lines, converting comments from # to % and fixing up stuff as you go.

That was the first thing what I did...

But I'm not sure how to use it in MATLAB (Pass the image to the script)

Code Select Expand

Usage: octave-cli focus_stack.m foo.png bar.png baz.png

When I do similar thinks in MATLAB (like Median over Images), I only give a path to the script. Then the script processes every image in this folder.

Well, assuming you are using Windows, Octave can be simply unzipped and ran; no need to install it system-wide. Therefore, as long as you are allowed to use a web browser and a zip extractor, I expect it to work.

https://wiki.octave.org/Octave_for_Microsoft_Windows

I think I will try this....

If you decide to try these scripts, please share the results.

I'd like to try it...
I tried MATLAB but the differences are too big. It is already failing

Code Select Expand

pkg load image
I am not allowed to install Octave on my company computer ..

If you start to learn now we may have a beta around 2023.
Because if someone listened 2 years ago we may have an alpha now.

Is that an optimistic estimate?
I probably would have the skills but not the time.
Maybe one first project when I retire in 10 years...

Yes, I use the 9V directly.
The original power supply delivers approximately 8.4V.
The 9V are no problem for Canon. If in doubt, you could connect a diode in series.

My currently preferred solution for powering my camera is a power bank with quick charge and a quick charge USB tester. This tester then simulates a quick charge device.

I then operate the camera directly with the 9V and have an output power of 18W (9V / 2A). Alternatively, I could also operate a slider with 12V and a maximum of 1.5A.

Since there is only one DC / DC converter in this chain, the total power loss is about 15% lower. There is also no influence on two DC / DC converters.
Powerbanks with QC are available from € 10, which is significantly cheaper than powerbanks with 9V or 12V output.

Similar testers are also available for PD (Power Delivery). With the testers you should make sure that there is a slide switch and no buttons. Those with the buttons must be reprogrammed after each switch on.

https://www.ebay.de/itm/QC3-0-QC2-0-USB-Trigger-Tester-Induction-Quick-Charge-Voltage-Detector-5V-9V-12V/264365621372?hash=item3d8d6b407c:g:X8wAAOSwT8ZdB0cj

To my knowledge, when using FPS override, the gaps between shots can be very very small. I've hardcoded a limit of 10 units (FPS timer B units) without thinking too much about it; on 5D3's full-res LV, one unit is exactly 33 microseconds (timer A = 792, main clock = 24 MHz), and it's actually the time required to read out one line. At 5 FPS, a gap of 10 units will give an exposure time of 0.19967 seconds (0.165% gap), and this gap can probably be made even smaller. This is pure theory; I did not run any tests to confirm the actual shutter speed or gap size.

TLDR: you can prevent these gaps, at the expense of rolling shutter

Then it's time to try it out...
So far I have only done this with Canon RAW.

I have been using this technique for a long time with my time lapse recordings to get more motion blur. LRTimelapse also has this feature. That's called 'Motion Blure'.
I usually use the combination of median and mean.

However, this method only works very well in very few cases. Simple waves can be smoothed out quite well.
But if the waves break with a white spray, then it will not look so nice anymore. The problem is the gaps between the individual shots that you cannot prevent.
Even objects that move slowly and are always overlapped a bit, look very choppy.
If in your example the branches would move through the wind, then that would not look so nice. I always separate through a mask the water surfaces of the rest of the scene.

https://www.youtube.com/watch?v=fyYJ3PRhlc0

What housing do you use?

I only use my S110 with a Meikon housing at the moment.
The great depth of field offers some advantages underwater...

That "scientist" seems just reinvent auto white balance.
I've shot a lot of photo/video underwater professionally, so i'm know, what i'm talking about.

I played a lot with the white balance. I never got to the results of "Auto Color Corrections" in CS6.
It looks like, that it works also with videos.

Just the "Auto Color Corrections" in CS6 fits mostly the Problem
https://www.dslr-forum.de/showpost.php?p=13050490&postcount=37

My Underwater pictures:
https://www.flickr.com/photos/136329431@N06/albums/72157675078738938

It appears to use the same file format as EOS R/RP and 250D. That means, I'm unable to look inside without physical access to the camera (such as the UART interface).

Does that say that it is an EOS firmware?

Thanks. That means, reversing the new format will be mandatory before any serious development effort on these new (and future) models.

Would a firmware dump in the camera bring more?

Ok, I'm surprised I did not find anything about it with Google ...

I can not add files to a post anymore. It used to work for me. Has anything changed on the forum?

It seems continuous mode in M50 produces 14 bits, sorry.

Sure?
I also looked at the RAW data of the M50 some time ago. The data in continuous mode looked like the histograms of the previous posts. There is definitely a lack of information. Maybe the result will only be shifted to 14bit.

Anyone have experience processing DNGs recorded underwater? It's a challenge perfecting the white balance, color, exposure while

I'm doing only still images...
But I don't care about color and white balance underwater anymore. As long I use RAW, I use the Auto Color Corrections" in CS6.
https://www.dslr-forum.de/showpost.php?p=13050490&postcount=37