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 - Levas

Pages: [1] 2 3 ... 38
Camera-specific discussion / Re: Canon 6D
« on: December 05, 2017, 04:25:16 PM »
Only for those who bought a 6D and can't get the right firmware because it isn't on Canon's website and the repository we've come to rely on has gone offline -- like now.

Probably a good idea if a moderator can put up a link to the 1.1.6 firmware file on my google drive in the first post on the first page of this topic ?
Or put a link to the firmware on the downloads page ?

Camera-specific discussion / Re: Canon 6D
« on: December 04, 2017, 10:21:05 AM »
Firmware update could be interesting, but I'd rather spend my time on adding audio recording option to the lossless recording.
I know some started out making MLV_lite recording audio.

I'm not sure what my approach would be, adding sound recording to MLV_lite or adding lossless recording to MLV_rec module.
The info and the code is all there, MLV_snd, MLV_lite and MLV_rec module.
Probably takes a lot of time to read the code, understand the code and combine the code  :P
I'm also not sure if firmware updating magic lantern from 1.1.6 to 1.1.8 is worth the time for the 6d.
1.1.7 Seems to fix lens corrections to jpg's made in camera for one lens, EF 70-300mm f/4-5.6 IS II USM
1.1.8 Seems to fix auto exposure in silent live view modus for these tilt and shift lenses: TS-E 50mm f/2.8L MACRO, TS-E 90mm f/2.8L MACRO and TS-E 135mm f/4L MACRO.

Camera-specific discussion / Re: Canon 6D
« on: December 02, 2017, 07:54:41 PM »
ML users are paying 10 times the original price for the free update.

10 times free is still for free, right  :P

Camera-specific discussion / Re: Canon 6D
« on: December 02, 2017, 07:52:18 PM »
Still have the official 1.1.6 firmware for Canon 6d:

Camera-specific discussion / Re: Canon 6D
« on: December 02, 2017, 06:26:06 PM »
I think I have the 6d 1.1.6 firmware, not at home now, will check later.
In the earlier days it was also available on the official canon website in Canada, not sure if they still have it available over there.

Camera-specific discussion / Re: Canon 6D
« on: December 02, 2017, 04:29:26 PM » is the build with lossless.

1824x924 lossless should work, 1824x1024 lossless doesn’t work.
Somehow some resolutions don’t work on the 6d.
In zoom mode you can go as far as 2688x960.

There is however one thing, you need to use exiftool to get the blacklevels right, see posts in this thread.

And ofcourse there is no audio/sound with MLV_lite.

Camera-specific discussion / Re: Canon 1000d / Rebel XS
« on: November 30, 2017, 07:13:18 PM »
There is little to none for the 1000d.
Syscal did some important first steps, but nothing near a working port.
There is nothing yet, no Magic Lantern menu not a single Magic Lantern function etc.

Best way to make use of Magic Lantern is to buy another Canon DSLR which is compatible with Magic Lantern.
Click the 'Downloads' button at the top of this page and go to the 'Nightly builds' here you can see which camera's are supported.
Many of them are released many years ago, second hand they're really affordable.
Some are better supported then others (depending on the user base and if active developers support them) I believe the Classic Canon EOS-M is one of the better supported cheap cams.


You have to import the wav files in the media tab, just as you did with the dng-sequence.
Then you have to drop the wav files on the timeline, below the videoclip, and line them out with the beginning and end of the clip.


Tested out median, I think it has a little edge compared to average, you get some fine noise/grain in the frame which gives it a little more sharpness perception.

I have uploaded all the 16 aligned PNG files, and the original PPM file for this particular frame on google drive:
Just in case you come up with some other methods of combining those 17 frames ;)
I've also included the average and the Median files on google drive


Got a averaged frame too, frame 9 averaged with 8 previous and 8 next.
Can't hardly see the difference with the TIF I got with RawTherapee.
For the pixelpeepers, 3 files on google drive, original DNG, the Rawtherapee TIF and the averaged DNG files:

That one was rather easy  8)

The optical flow script wasn't even needed for this, only RawTherapee was used:
See this post for a youtube link to see the workflow:

Just to see what happens, I'm going to use the optical flow script on frame 9 too.
But that's gonna take a while, will upload it when its done.

Had to search for an avi without relatives in it, found one  :D
I think this is a good example of what aligning and averaging can do.
Before (upscaled tif from 320x240 to 960x720 with Lightroom

Same frame, but averaged with 8 previous and 8 next frames:

Not very detailed, but much better then the original.
Think median will give more detailed results, will check out the links you send.

Using the optical flow script, first post this topic, to enhance some old 320x240 motion jpg avi files.
upscaled the resolution 3 times each dimension, so 960x720 and then run the optical flow script, altered it to let it average out 17 frames (8 previous, 8 next).
The result is actually not bad. It still lacks some detail of course, but shadow noise and jpg blocking artifacts are all gone.

In the makefile I see the average frame is made by the command convert.
But when I type convert in terminal, I don't see an option for average ?
I'm curious if there are more options instead of average, maybe median or something ?

Curious how this script is in aligning the images, did you test it against the optical flow script ?
The optical flow script is good, but when much movement is involved you get contrasty lines around object edges.
But the more frames you combine, the better it gets.

Probably gonna test your build too, but maybe you already tested it against the script in Alex post ?

Thanks, works  :D

(Had deleted all unused functions in the makefile, the 'all:' function was already deleted   :-[, my fault  :P)

Are you sure 14bit lossless looks not as good as 14 bit ?

Because lossless means, lossless as in no quality loss...
For compression with quality loss the therm 'lossy' is used.
I think the 14 bit lossless files should be identical to the normal 14 bit files.
As far as I know it uses an non destructive algorithm to make file size smaller.


Now I'm trying to average out a whole batch of ppm files with

I thought, the command
Code: [Select]
make j8
would do batch process, but it does only the clean operation in the makefile  :P
So the number behind the j is just the number of CPUjobs it starts ?

I have a sequence of files with the following name ' Test_000000.ppm' to 'Test_000121.ppm'
So the prefix should be according to the rules _6digits
What command will make all average files for the whole sequence ?


Never would have guessed this one:
Code: [Select]
for f in *.tif; do  echo "Converting $f"; convert "$f"  "$(basename "$f" .tif).ppm"; done

Sorry for asking here and not googling  :P

But is there an easy command line option, with convert, for converting all tif's in one direcory to ppm files ?

If this effort succeeds, does that mean that expensive VAF filters will no longer be necessary for the cropped Canon models?  If that is the case, then this is really a big thing and I keep my thumbs pressed for all developers involved.  Good work, guys!

For as far as I can tell, VAF filters where never necessary  :P

That's the beauty of raw, many options in post proces  ;D

Anybody already find out how to do more then one previous and one next frame ?
Alex is using 3 previous/next frames here:

Knew about the LMMSE method controlling color moire really good, THE reason I've learned to use RawTherapee  ;)

But I'm wondering, how to convert the images to ppm  :-[  (it's mentioned in your workflow as if every photo/videographer uses the ppm format  :P)
And is there a way to export the final; image as tif file instead of jpg ?

When you install opencv with brew, it will tell you to run some commands if you want to develop with it (or something along these lines). Once you do that, it should be able to find cv2 (aka OpenCV). At least that's how it worked here.

Found the command you're talking about, it works now.

Time to do some testing with it  :D

Interested in making this work, curious what it can do with high iso noise  8)

For as far I can tell, you're using pyflow to align images and once aligned, your averaging the frame with previous and next frame.
Is that what's happening ?

Read that the first time  :P
Thought I got it right with using existing makefile from magic lantern and selecting the lines manually etc...
But now that I have copied the tekst of code with using the quote button on your post, to see plain tekst of your message, it works.

It does a lot, takes about 1 minute to calculate stuff for only averaging frame 2.
But at the end I get an error, no module CV2.

make -j2 M27-1337_frame_000002-a.jpg
python ~/pyflow/ M27-1337_frame_000002.ppm M27-1337_frame_000003.ppm M27-1337_frame_000002-n.png
python ~/pyflow/ M27-1337_frame_000002.ppm M27-1337_frame_000001.ppm M27-1337_frame_000002-p.png
M27-1337_frame_000002.ppm M27-1337_frame_000003.ppm -> M27-1337_frame_000002-n.png
M27-1337_frame_000002.ppm M27-1337_frame_000001.ppm -> M27-1337_frame_000002-p.png
Constructing pyramid...done!
Constructing pyramid...done!
Pyramid level 14
Pyramid level 14
Pyramid level 13
Pyramid level 13
Pyramid level 12
Pyramid level 12
Pyramid level 11
Pyramid level 11
Pyramid level 10
Pyramid level 10
Pyramid level 9
Pyramid level 9
Pyramid level 8
Pyramid level 8
Pyramid level 7
Pyramid level 7
Pyramid level 6
Pyramid level 6
Pyramid level 5
Pyramid level 5
Pyramid level 4
Pyramid level 4
Pyramid level 3
Pyramid level 3
Pyramid level 2
Pyramid level 2
Pyramid level 1
Pyramid level 1
Pyramid level 0
Pyramid level 0
Time Taken: 55.16 seconds for image of size (1026, 1824, 3)
Time Taken: 55.17 seconds for image of size (1026, 1824, 3)
Traceback (most recent call last):
Traceback (most recent call last):
  File "/Users/magic_lantern/pyflow/", line 45, in <module>
  File "/Users/magic_lantern/pyflow/", line 45, in <module>
    import cv2
ImportError: No module named cv2
    import cv2
ImportError: No module named cv2
make: *** [M27-1337_frame_000002-n.png] Error 1
make: *** Waiting for unfinished jobs....
make: *** [M27-1337_frame_000002-p.png] Error 1

Sorry for all, probably noob, questions  :P

Wow, lots of information.
Ok, installed all the packages, did the following commands in terminal:

sudo easy_install pip
sudo pip install Cython

cd pyflow/
python build_ext -I

sudo pip install Pillow
brew install opencv3
brew install dcraw imagemagick

Now when I use the command:
make -j2 M27-1337_frame_000002-a.jpg
I get an error message:
Makefile:12: *** missing separator.  Stop.

I'm not sure about my makefile, I assume I needed to make a file in Pyflow directory with the name 'makefile' (no extension) with the code you had in your first post.
To be sure the makefile is not in a wrong text format, rich tekst or something, I copied one from the Magiclantern directory and replaced the tekst with the tekst in your post.

I have Pyflow in my user home directory,
So this alteration should do ?
# replace with path to pyflow repository
FLOW=python ~/pyflow/

Pages: [1] 2 3 ... 38