Should native RAW support be discontinued?

Posting rules: It shouldn't need saying, but... play nice. Please keep your discussions civil. You can disagree, just don't be disagreeable. And, of course, all of the usual stuff like no spamming. Tex adds: I'll be rigorously enforcing this as we go along. We're probably going to be a small community in a little lifeboat, so we can't have members at each others' throats. This is for the sake of the project as a whole. So when you post, pretend you're speaking in person with your very wealthy auntie who has always treated you wonderfully and currently lists you prominently in her will. I won't be tossing anyone out of the forums because we are all in this together (except spammers: immediate membership cancelation), but I'll delete suspect posts right away.

24 posts / 0 new
Last post
Should native RAW support be discontinued?

RAW conversion isn't a core part of LightZone and doesn't really add any value to its core purpose of image editing. Dropping support for RAW would free up the developers to focus on important things.

So what to do about RAW handling? "Outsource" it to RawTherapee. When you double click on a RAW file, have RT open with that file selected. When the file is saved, have RT set to send the file back to LZ for editing.


The latest version of the above app does not work on OSX 10.10 Yosemite.

raw processing is already outsourced

outsourced to DCraw already, so that is taken care of.


And by the way, what is important to me is the raw conversion coupled with the "different" image processing.


So, i don't agree.

I'd have to agree with

I'd have to agree with hcremers on this.

Raw (it's not RAW in all caps) is an essential part of LightZone for me. The fact that I can process my Raw images and make other image editing adjustments with in the one application makes for a great workflow.





LZ always was, primarily, a Raw converter doing its own thing in conjunction with dcraw basic decoding.


If you drop the Raw conversion part  ... well, you may as well go elsewhere for all editing since you will have abandoned the most important part of what the product should be about.


What part of your suggestion am I misunderstanding?







Not up to par anymore

The problem is that LZ's RAW conversion isn't top of the line. Where's highlight recovery? What about a choice of demosaicing algorithms? One size doesn't fit all pictures. Lens and camera profiles? RT can use Adobe's. 

Gave Up Using RT

I had to give up using RT because it crawled to a halt when using some of the features you mentioned on my less then stellar resource device.


As for highlight recovery, you can do that in LZ using zonemapper by selecting the zone that need highlight recovery and slide the sliders down as appropriate.  It may not always work out great by it does work with careful use of the tool.


Raw Tone Curve is, in affect, camera profiles and works fine for the cameras I have.  I'm considering a purchase of a fairly newly released camera, the Canon 7D MkII that I know hasn't been added to the library of cameras yet but I expect it will be added hopefully by early 2015.

Raw conversion

Can anyone tell a layman what lightzone really does to a Raw image? I see that there are 2 tools on the right if I open a NEF Raw file- Tone curves, and Adjustments (Exposure, Noise, Temperature and Tint.

The Tone curve is greyed out- I cant do anything there so I can only experiment with the Adjustments. Does this mean that there is a basic conversion carried out automatically by LZ from Raw to JPEG, which utalizes the superior information in the Raw package and (supposedly) turns it into a better image? Or am I supposed to experiment with the 4 above controls to see what happens? And then to convert to JPEG and "play" with the great set of tools there too (relight etc. etc.)?

I am dying to surround myself with this amazing program (I take hundreds of photos a month)because I see the huge potential, but for the life of me I cannot understand how to develop a workflow with LZ.


I'm far from an expert but I believe some of it starts with DCRAW, see one discussion on the topis here -->


Without getting to deep into the weeds, demosaic comes into play, see -->


The greyed out tone curve tool is designed for the camera you are using.  There is a discussion video somewhere in the forums explaing how to create a tone curve for yourself.  


As for the Tone Curve being greyed out, you can turn on any greyed out tool including the Tone Curve tool.  Simply right click on the orange part of the tool, after opening it and find the unlock feature.  Left click on that and you can work on the tone curve.  Be careful when doing so that you don't save over the correct tool already completed for your camera.  If you decide to save it give it a new name.


I'm sure others can be even more helpful,



Dropping Raw format support- please don't

I use and recommend Lightzone in my teaching as a way to get people new to digital photography over their fear of raw files, and having Lightzone easily handle Raw makes the transition and their workflow a lot simpler and more powerful. I would hate to see it go away, and I believe it is one of the prime reasons many folks like Lightzone in a world with a lot of alternatives.


Drew Webb



It's Raw capabilities are what drew me to LightZone in the first place.


As already said, Raw handling

As already said, Raw handling is already, partially at less, "outsourced" with the use of DCRaw.


As Grant, may be I misunderstood something, but... what ?

One "great" thing with LZ, is it bring its own DCRAW, so I can use my Fuji X-trans earlier than with other editing tools in my Linux OS, so I thing tight relation between LZ and Raw processing is important.


Yes, raw support is

Yes, raw support is outsourced to dcraw and multi-threading the dcraw is already done, so keeping our dcraw_lz updated is easy task now. Creating Tone Curves for new cameras also became easy, thanks to a ruby script written by Doug:


In fact, the greatest problem for the dev-team is that currently there is only one developer who actively commit the code. Localization project also has been inactive for months. I would be greatly appliciated if someone help the development or translation.


Masahiro from dev-team

Help for Dutch translation

Dear Masahiro,


While i cannot do any coding, i could help out in translating. I'm Dutch, so i could create/update/improve the Dutch localization for LZ. I'd be happy to, as long as someone guides me on the technical bits.

I've done translations before, for Photivo.

Please let me know in case you want to take me up on my offer, we'll arrange some way to connect.

Help for Danish Tranlatio

Dear Mashiro


First a BIG THANK YOU for all your contribution and effort.


I will offcource help with translation into Danish, if you give instructions and permission to do so. I am very gratefull to help. I am not a developer, but will offcourse help in any way I can.


Have nice day

Lars Henrik Ørn

@hcremers and @Lars,

@hcremers and @Lars,

Thank you for your offers! Well, the localization (l10n) team use OmegaT to make it easier to translate source files that contain a bunch of duplicated sentences. I had written an instruction on how to use OmegaT:

and created github repositories for your languages:

You'll need to create a github account and send me a request for collaborator access permission before starting translation.


Alternatively, if it is hard to use OmegaT you can use normal editor like Notepad to edit the source files. The source file is available from "Download ZIP" link in the repo pages.






P.S. There is a l10n-team forum on google group, though I'm not a maintainer:!forum/lightzone-l10n

please add me

Dear Masahiro,


Please add me for the Dutch translation, i'm hcremers on github.



Thank You

Thank You


I am registered at as larshenrikoern. Please add me for danish translation. Since I am using Linux using OmegaT is a no brainer.


Happy to help


Have a nice day

I'm interrested too,

I'm interrested too, unfortunately not for code, but for translating in french if needed.


But, I'm not familiar with GitHub, so How to request you to add me in the french repository's contributors ?

Tell me your username on

Tell me your username on github so that I can add you as a collaborator. Thank you. :)

It's Photonoxx on GitHub too

It's Photonoxx on GitHub too


I look at files in OmegaT, can you confirm I have to let the filename as they are (like filename.css, or something-else.htm...) ?

If you go without OmegaT,

If you go without OmegaT, please keep the source filenames and their folder structure as they are.

If you use OmegaT with github, you need to do nothing special. OmegaT will upload your changes as a translation memory file ("omegat/project_save.tmx"), without uploading translated files. The .tmx file is a kind of database to create translated files from source files. When you or other users need the translated files, they can be created under target/ folder using "Project" > "Create Translated Documents".

I create a new topic for

I create a new topic for translating question under the Git hub section. It may be more convenient...

Translation priority

Hello new translators,

I forgot to tell you, but priority of source files under "lightcrafts/locale/com/lightcrafts/image/metadata/" folder are not high, since their contents are meta-tag names used by EXIF or maker specific image tags. Translate other files first, then work on the metadata later when you have enough time.