Menu

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

#1
Hi David,

I'm having trouble with using your script in lightroom 6 (version - 2015.6.1).  I've used it before in Bridge but it takes forever and sometimes just doesn't work (too many images at once?).  My friend installed djpeg after compiling it with brew and we've put it in the plugins folder but I'm getting the same error message as a previous user when I try to run the script "Unsupported PPM format -> Expected a binary RGB (P6)".  Can you help? I'd love to use this plug in in Lightroom (mainly as I think it'd be quicker?)

Thanks in advance

James
#2
QuoteCan someone tell me how/if I can run the LrRamp and LrDeflick scripts in Lightroom 5.6?  I downloaded the .lua files, but I can't run them as a plugin and I don't know how to just run them as a script.  Is there someway to convert the .lua files into a proper plugin?  I also don't know how to "compile" djpeg?  Anyone got some tips for a sad total newb?

Thanks

according to dmulligan it doesn't work in light room 5

QuoteLR6 only. LR5 API does not have the requisite functions.
#3
QuoteHello!

I just saw that dmilligan ported the deflickering script to Lightroom. My question is: is there any advantage in running it instead of using the Bridge version? The main one I can think of would be speed: is the Lua engine in Lightroom multithreaded? (Watching the deflickering script using just one core in my CPU gets kinda old...)

Me too, any news?

Cheers
#4
Amazing, I wish A1ex would have added add this to the description in the original thread.  Many thanks
#5
Okay so thanks all, 3 days getting my head around this bit the results are great here the full run down of my de-flickered time-lapses from my last shoot.


I thought I'd compile some of the advice that helped me get my head around this:

@classicbs: Maybe this workflow will help for you. I could get the best results till now:
1. Delete your old XMP-s (or save them somewhere as backup).
2a. In LR read in the metadatas for your sequence. Select all files on the library tab (ctrl + a) -> right click metadata -> read metadata.
2b. In LR set custom whitebalance for your files + crop for 16:9. Select all files on develope tab -> switch on autosync -> basic settings: wb custom + crop overlay: aspect 16:9. -> save metadatas (ctrl + s)
2c. In LR set 1 star for your keyframes + adjust the settings for them. Rightclick on the selected images -> set rating: 1 star (switch off autosync!) + filter for 1 star -> adjust the settings for the keyframe as you wish (don't touch the shadows, highlights, blacks, whites) -> save metadatas again.
3a. In BR select all files and right click -> purge cache for selections. Now you will see the settings, what you did in LR.
3b. In BR select all files and run David's awesome ramp multiple script (check all), wait till the process ends.
4a. Before you deflicker the sequence I suggest you to download the visionlog raw camera profile (read the installation guide) and apply it. This will help the deflicker script to work more properly.
5. In LR setup the visionlog raw profile for you sequence. Read in the metadatas for your full sequence (filters off) on the develope tab -> switch on autosync -> camera calibration, profile: visionlog -> save metadatas.
6a. In BR select all files and right click -> purge cache for selections. Now you will see very flat images.
6b. Run deflicker.
7. In LR read metadatas for your sequence and swicth back your camera profile to adobe standard -> save metadatas.
8. In BR select all files and right click -> purge cache for selections. Now you will see everywhere the final multi ramped deflickered sequence.

Maybe it's too long to read and every settings could be done in BR + ACR, but I like the LR's layout.

D-milligan's words of wisdom

------------------------------------

When you make a keyframe its like telling the script "don't touch this frame", it becomes the target for what frames around it to look like. By default the first frame and last frame are keyframes.

So, pick a couple a frames that represent important sections of your time lapse. Then simply adjust them (along with first and last frames) to look however you like. If you modified settings besides exposure, then first do a "ramp multiple" this will make all settings smoothly ramp from one keyframe to the next (if you change WB, make sure all frames are set to Custom WB). Then run the deflicker. It will adjust exposure, making all the frames smoothly transition from one keyframe to the next.

If you want to adjust exposure after the deflicker, you can use the "ramp" in additive mode. It should be easy to avoid that though. Simply make sure your keyframes look like what you want for you final output before running the deflicker.

---------------------------------

It's usually best to do these edits before deflickering in case they introduce any extra flicker themselves, the deflicker will help take care of it somewhat. (ACR has a lot of settings that are 'image adaptive' and they can have a different effect on different source material, causing flicker; the worst offenders are: clarity, highlights, shadows). Of course there are things that are not going to cause extra flicker (like WB, noise reduction, lens corrections), so it doesn't really matter when you do them.

Because of the image-adaptive nature of some of these settings, even the deflicker script won't be able to fully fix the flicker introduced because for example highlights, midtones, and shadows may be affected differently, and the deflicker can only match overall exposure. So you have to be careful when using these settings, there will be limits to the values you can "safely" use (without introducing too much additional flicker).

-----------------------------------

The preview should show you the analysis area and it will highlight the percentile you selected.

Analysis size refers to how big the image is scaled down to before computing the histogram. The smaller you make it the faster the script but the histogram will be less accurate. (the reason for this setting is that the rescale operation is native and very fast, however computing the histogram is done in JavaScript which is very very slow, so rescaling the image down makes the histogram calculation much faster)



My Hint's and tips.


If you're not happy with the de-flicker of a particular section then an easy workflow is to just re-keyframe that section and only select the photos in the section you want to re-de-flicker so you don't have to wait for the whole time-lapse to run again.  Just remember to uncheck any previous keyframes you may have set so as to not affect the behaviour of the new keyframes in the section you are modifying.  Otherwise you might experience some unwanted behaviour

If you want to ramp some other settings after the de-flicker then be sure to uncheck exposure in the Ramp Multiple check box otherwise it will mess up your de-flickering

When de-flickering, if you "select all" in Bridge be sure to uncheck the undoDatoa.jdon file otherwise it will hang the de-flickering and you'll have to force quit bridge (at least I had to) and run it again

I found that often more than 3 passes were necessary before the script was happy so I just set it to 10 passes every time then let it run so I wouldn't have to do it twice every time

Use the percentile measure to fine tune areas that aren't de-flickering well by changing where the de-flickering occurs (but be careful as of you change one area another may get worse best to stick with the sky
#6
Okay great many thanks @dmilligan.

Do you have an opinion on the following statement?

Quote4a. Before you deflicker the sequence I suggest you to download the visionlog raw camera profile (read the installation guide) and apply it. This will help the deflicker script to work more properly.
#7
Okay great many thanks @deafeyejedi, @Surami, @dmilligan.  I'm really getting into this now.  I'm still a bit unsure as to when the best time to do batch post processing is?  For the nighttime star time lapses it really helps to adjust some settings on all the photos to make the stars really pop in the sky.  If one knows they will change all the photos  (i.e. no need to ramp) then are these edits best left to after the de-flicklering?  Can I ramp after de-flickering?  Do I need to run de-flickering again if I keep ramping.

Here's my first three efforts using this amazing script in 4k should you have a great monitor.  You can see the great wall of china time-lapse has progresses.  Would anyone care to criticise my exposure ramping and WB tramping, how does it look I'd be interested to know, the original un-ramped version is above.

Cheers

p.s. please don't share this YouTube link anywhere else as I'm not supposed to be making these images public yet

#8
Also just my tuppence worth, I do really appreciate the effort that has gone into this but a couple of comments.  I keep selecting the undo log thing when I deflicker and it hangs my computer and I have to force quit bridge.  It'd be better without that being there somehow (although it is useful).  Also is it possible to make it run until it doesn't need to anymore.  At the moment I'm just selecting it to run 10 times so it stops itself eventually .  Is there a reason why one might want to deflicker less than what the script thinks?

Clip imminent of several day to night lapses from China shot for National Geographic.  Once I've nailed this I'll donate something on the PayPal,  much appreciated!
#9
Hi Surami,

That's great I think I've nailed it now everything seems to work as expected.  I have two questions.

2c, why do you say (don't touch the shadows, highlights, blacks, whites)?  At what point can I adjust these in your workflow and why.

Do you know about changing Lightroom's catalog settings in the preferences: Lightroom>Prefrences>Go To Catalog Settings>Metadata>Automatically write changes to XMP

Should I use this or not and if not why not.

Also more generally how do I get notified in this forum if someone replies to my post?

Mant thanks and I'll post the time-lapse and some others once they are done,

James

#10
Thanks David, that's great so I really get it now one can just edit a few photos and everything will RAMP.  My problem now is that the keyframes don't seem to work.  I'll try again but say I set a keyframe in the middle and one at each end it only rams to the middle keyframe and not all the way.  It's fine as I can do it in two batches but I wonder what I'm doing wrong to have it stop in the middle at the one I gave one start rating to, this has happened twice now.  Also separate issue I can't seem to flip between bridge (and camera raw) and light room.  They photos seem to have there own settings and the edits don't seem to be carried over even though (as far as I can tell) they are referencing the same cr.'s and XMP's?  Any Ideas?
#11
Hi There, loving the script.  I've just been doing loads of testing with ETTR and now I'm testing the processing.  I have a few questions that will help me understand this better and also help other people understand it.  I will go and test it myself but I think it wold be valuable if anyone was prepared to walk me through how they would approach the post processing of a time-lapse I shot.  It was shot overnight on the Great Wall of china in early Nov as I froze my ass of off camera.  It looks amazing but due to the cloud cover and the full moon it looks like day time.  Also due to my settings in ETTR (percent of highlights to ignore) once the moon comes into frame the exposure changes dramatically.  Have a look and if some one could give me a rough outline of how they would approach this using the script and roughly where they would place the keyframes and for what values (WB, Exposure etc) that would be amazing.  I'll do my own tests and post the results but it'd be great to get your opinions.   

A few specific questions.  If i want to reduce the exposure of everything can I do this at anytime or only at the beginning?
Why would I want to keyframe the de-flickering process I'm not clear on why I'd want to do this or in what situation?

#12
I'm on mac osx 10.9.5 btw
#13
Hi there I'm sure this is a real simple fix and apologies for my complete nobleness.   I'm trying to use exiftool to reduce exposure on all the photos in a time-lapse sequence shot with ETTR.  I've worked out how to get the de flicker working in light room but I want to also batch reduce exposure.

Quote
On mac put all your images and xmps in one folder.
open up terminal, enter this, exiftool -Exposure2012+=+*.** /drag folder here containing cr2's and .xmp's

Where the *.** is enter the amount you want to set, eg 0.05, next to the number you have chosen, too the left is +, +=over expose for under add -

I tried this but I just get an error saying "no file specified"

Any ideas?
Any ideas?  Many thanks
#14
Installation
============
(If building from CVS rather than a release see also "Building UFRaw
from CVS", below.)

Building UFRaw requires development packages for GLib >= 2.12 and lcms >= 1.14
(lcms 2.x is used if found). There are many optional dependencies which enable
building additional programs and adding features to existing programs.

The UFRaw build process expects Perl to be present (for pod2man). It is
needed only if you are changing ufraw.pod or if you are building from CVS.

A modern make is required. GNU make and BSD make both work currently.
In case of trouble, try GNU make.

Building UFRaw on the PowerPC platform requires GCC version 3.4 or newer.

The first step of the installation is to run the configure script:

./configure

At the end of the configuration you will get a summary of the
installation settings. If all optional dependencies are present it
will look like this:

configure: ====================== summary =====================
configure: color management support: lcms 2.x
configure: build GTK GUI: yes
configure: build GIMP plug-in: yes
configure: EXIF support using exiv2: yes
configure: JPEG support: yes
configure: JPEG2000 (libjasper) support: yes
configure: TIFF support: yes
configure: PNG support: yes
configure: FITS support: yes
configure: gzip compressed raw support: yes
configure: bzip2 compressed raw support: yes
configure: lens defects correction support using lensfun: yes

If some of the lines end with 'no' instead of 'yes', UFRaw can still
be built, but the named option will be disabled.

Development packages for GTK+ version 2.12 or higher and
GtkImageView version 1.6 or higher are required for the GUI.

Development packages for GIMP version 2.2 or higher is required to build
the GIMP plug-in.

The development package for exiv2 version 0.20 or higher is required for
reading the EXIF data. Among the supported formats are Canon (CRW, CR2),
Fuji (RAF), Minolta (MRW), Nikon (NEF), Pentax (PEF), Samsung (PEF),
Sony (SR2, ARW) and Adobe's DNG. If the configuration script does not find
this package EXIF support will be omitted.

The libjpeg development package is required for saving image in the
JPEG format in the stand-alone tool. It is also needed to support
Kodak DC120 and Adobe's lossy DNG. If the configuration script does not
find this package JPEG support will be omitted.

The libjasper development package is required to support image files from
Red movie cameras. If the configuration script does not find this package
support for such image files will be omitted.

The libtiff development package is required for saving images in the
TIFF format. If the configuration script does not find this package
TIFF support will be omitted.

The zlib development package is required for saving images in the TIFF
format with lossless compression. If the configuration script does not
find this package compressed TIFF support will be omitted. This pacakage
also enables loading of raw files compressed with gzip.

The libbz2 development package is required for loading of raw
files compressed with bzip2.

UFRaw is written in both C and C++, so if you set CFLAGS you should
also set CXXFLAGS. If you do not set them, then the default for
GNU C is "-W -Wall -g -O3 -fomit-frame-pointer".

Other options for the configuration script are:

--disable-openmp: don't try to use OpenMP support even if it is
        apparently present.

--enable-extras: build the extra binaries - dcraw, nikon-curve.

--enable-mime: install mime files (see mime section later on).

--enable-dst-correction: enable DST correction for file timestamps.

--enable-contrast: enable the contrast setting option.

--enable-interp-none: enable 'None' interpolation (mostly for debugging).

--enable-valgrind: enable debugging with valgrind

--with-prefix=PREFIX: use also PREFIX as input prefix for the build.

--enable-no-cygwin: add the -mno-cygwin flag to CFLAGS and CXXFLAGS
                    (only in Windows).

--with-dosprefix=PREFIX: PREFIX is the prefix in DOS format
                         (needed only in Windows).

To build UFRaw:
  make

To make a system wide installation:
  make install

Note that the GIMP plugin, if built, will be installed into UFRaw's prefix.
Thus, if UFRaw's prefix is different from GIMP's prefix, you may have to add
the plugin directory to the search path, add a symbolic link, or something
similar.

To use the UFRaw GIMP plugin, ensure that other raw converters
(e.g. rawphoto) are not installed because they may claim the raw file
first, preventing UFRaw from running.

If one of the packages (lcms, libjpeg, libtiff, zlib etc.) is not installed
on your system, and you can not install it using the normal packaging
system, you can build it locally and use UFRaw's configuration option
--with-prefix to point to its location.  To build any of the above
packages download the package and type:
  ./configure --prefix=$PREFIX
  make
  make install
If zlib is built only locally you will have to configure libtiff with
the command:
./configure --prefix=$PREFIX --with-zlib-include-dir=$PREFIX/include --with-zlib-lib-dir=$PREFIX/lib

Finally, you should configure UFRaw with the command:
./configure --prefix=$PREFIX --with-prefix=$PREFIX

Install mime files
==================
Your desktop can automatically generate thumbnails to raw files and
associate them with UFRaw by installing some mime file. To enable this
option you need to use the configuration option '--enable-mime'.
This options is limited to the GNOME desktop at the moment.

The file ufraw-mime.xml is already part of shared-mime-info 0.21.
If you are using an older version of this package, you should:

cp ufraw-mime.xml /usr/share/mime/packages/

To finish the installation you should use the following
(assuming you are using --prefix=/usr):

# Associate mime type to raw images:
$ (only needed if you are using shared-mime-info < 0.21)
update-mime-database /usr/share/mime
# Install UFRaw's thumbnails generator:
GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source` gconftool-2 --makefile-install-rule /usr/share/gconf/schemas/ufraw.schemas
# Associate UFRaw with the raw images mime types:
update-desktop-database

More information can be found at:
http://www.chauveau-central.net/page/c_raw.html
http://www.penguin.cz/~utx/gnome-dcraw
#15
Hi so i've been using ETTR for time-lapse on a recent shoot for National Geographic.  I've kind of got my head around the XMP post de-flickering workflow but for my first time lapse of the shoot I accidentally created UFRAW side car files. I need to de-flicker this time-lapse as it looks amazing!  I have downloaded UFRAW version 0.20 from here: http://sourceforge.net/projects/ufraw/files/latest/download?source=files

I have unzipped (is that the right term?) the package and I now have a folder called ufraw-0.20 which contains lots of different files.  There is a 'read me' which to me is serious gobbledegook.  I really can't understand it, I'll reproduce the text below but could anyone walk me through instillation on a mac (OSX 10.9.5).  And then if you are super kind explain how to

(1)  De flicker the time-lapse
(2)  Batch reduce the exposure
(3)  Export to Jpeg

Many thanks and any replies in layman's terms would be much appreciated!
#16
Hi there I'm trying to use exiftool to reduce exposure on all the photos in a time-lapse sequence

QuoteOn mac put all your images and xmps in one folder.
open up terminal, enter this, exiftool -Exposure2012+=+*.** /drag folder here containing cr2's and .xmp's

Where the *.** is enter the amount you want to set, eg 0.05, next to the number you have chosen, too the left is +, +=over expose for under add -

I tried this but I just get an error saying "no file specified"

Any ideas?  Many thanks