Recent Posts

Pages: [1] 2 3 ... 10
Seems there are more ways to play with this. By using enblend-enfuse and hugin(align image tool) one can elmininate aliasing and moiré. Inspired by a1ex post I did following.

brew install dcraw
brew cask install hugin
brew install enblend-enfuse

In a folder place two files let´s say for instance(skip one file in between):

Then run following command inside the folder containing the two dng files:
Code: [Select]
dcraw +M -6 -W -q 3 -T *.dng && /Applications/Hugin/ -C -a aligned.tiff $(ls *.tiff | awk 'FNR == 1 {print}') $(ls *.tiff | awk 'FNR == 2 {print}') && enfuse -o enfused_aligned.tiff aligned.tiff0000.tif aligned.tiff0001.tif && rm aligned.tiff0000.tif aligned.tiff0001.tif
The final file will be called enfused_aligned.tiff and should be sharp and clean from aliasing and moiré.



One side note, the dual ISO feature, i've tested this, Loaded dual ISO file (11-8bit lossless), raw corrections D_ISO enabled, everything is fine lines gone etc, However once i click on export, the alternating lines re-appear, and the final exported dual iso file is with the line's, exported un proccessed it would seem, i'm not sure whether you guy's are aware of this, or whether the dual iso feature is a work in progress, just thought i'd share my experiance with using it,

I think I also found this one. All RAW corrections settings were at default when exporting. In many clips we did not see this error. But now I had the same with bad pixels... :-D
Bouncyball implemented Cinema DNG export. We need some more testing and then I think it is time for v0.11...
On the .MOV export not working (MacOS X) from a built version of  MlRawViewer, I found the following glitch: if ffmpeg is updated on your machine (I use MacPorts), the old binary copied into the path for some reason no longer works. In mlrawviewer.log I get
Code: [Select]
Traceback (most recent call last):
  File "", line 796, in stdoutWriter
IOError: [Errno 32] Broken pipe
repeated 11 times. The export process stops after showing 0.00% for a couple of seconds. I think this means that the dynamic libraries and ffmpeg executable somehow go together, and also that a distributed version of the with ffmpeg inside not necessarily works.
This problem is not related (I think) to the 'ffmpeg doesn't get data' problem where the export process stops at a couple of percent and then stalls.
The saga continues...
ffmpeg has a very fast averaging filter. Here´s an example using the tblend filter averaging consecutive frames. Obviously it will produce a slight blur but maybe one can use something like minterpolate filter to build some in between frame.

You need ffmpeg and dcraw and then you can run the following command directly on two dng files to output highres tif files:

Averaged output
Code: [Select]
find . -maxdepth 1 -iname '*.dng' -print0 | xargs -0 dcraw +M -c -6 -W -q 3 | ffmpeg -f image2pipe -vcodec ppm -i pipe:0 -y -pix_fmt rgb24 -t 2 -vf tblend=all_mode=average AVERAGED%03d.tif

Unaveraged output
Code: [Select]
find . -maxdepth 1 -iname '*.dng' -print0 | xargs -0 dcraw +M -c -6 -W -q 3 | ffmpeg -f image2pipe -vcodec ppm -i pipe:0 -y -pix_fmt rgb24 NOTAVERAGED%03d.tif



ffmpeg tblend filter:

Reverse Engineering / Re: Reverse EFS Lens firmware
« Last post by leegong on Today at 04:34:35 AM »
On mainboard of Sigma 24-105 f4.0 EF lens , there is a MCU marked "EIS 944A" ,
Does anybody have more info of this MCU ?
Camera-specific discussion / Re: Canon 70D
« Last post by ShootMeAlready on Today at 02:39:52 AM »
In the latest nightlies there was only 14 bit raw. That is ok if you need 720p, but if you want to shoot 2.2k raw or FHD raw you need 10bit raw with for display.  Is that available anywhere?
A integration of it on HDRMerge would be cool...
Camera-specific discussion / Re: Canon 60D
« Last post by Exo on Yesterday at 11:48:09 PM »
Okay, this is the closest i got: 40D


But don't count on me putting any credit card infos in that king of a website.
Raw Video Postprocessing / Re: Strong artifacts
« Last post by Ilia3101 on Yesterday at 11:17:04 PM »
Ah yes, thanks for the white balance idea. I really must try that out.
And wow, that somebody really does make AMaZE sound particularly good (maybe its the original creator :)) )
Raw Video Postprocessing / Re: Strong artifacts
« Last post by a1ex on Yesterday at 10:35:11 PM »
Unable to answer without sitting down to debug it, but from what I remember since I've used AMaZE in cr2hdr, it seemed to prefer white balanced data as input (so it could know what's grayscale and handle aliasing better in these areas). At least that was my understanding (or maybe my implementation is also broken). I don't really understand how it works (tried to ask somebody who seemed to know), only figured out how to call it.
Pages: [1] 2 3 ... 10