Another Milestone

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.

Today we cross another threshold.  We now have more than 25,000 registrations at the LightZone Project.  A few of you have complained about our sign up process---and it is clunky and has even failed us a couple of times when we had a flood of new registrations.  Some of you who are coming to the site for the first time may be wondering about it.  We know it can be a little annoying, but we still think it's a minor annoyance in the grand scheme of things.  And the benefit to all of us will become plain as we move forward.  Please read on...

Besides the security issues, since we instituted our new policy we have seen an incredible jump in registrations.  This was also an important goal.  Because, even though we can track hits on our pages, and have used Google Analytics since mid-summer past,  hits can be bots and somewhat random searches.  Actual registrations, however---now that is another story entirely.  Registrations represent real people.  Being able to show the open source development community that we have this many people who have been willing to go through the registration process is very significant indeed.  In a conversation I had with Anton Kast, one of LZ's original developers,  yesterday, he initially expressed a little dismay that we were forcing people to register as members to get the software.  Then he heard the numbers....and that changed the situation for him a little bit.  He agreed that numbers like these are significant, and will be a draw for developers of all sorts.  And numbers like these will also bring new members---after all, how could all 25,000 of you be wrong?

So, there's some method to our madness, and we thank all of you for putting up with it.  And it has also helped bring in a larger pool of people with post processing experience who can offer needed criticism about LZ---what it needs to do better, and we are finding those things out, now.  A case in point: recently we had an example of a direct comparison between LZ and LR4 on the specific issue of (somewhat extreme) highlight recovery.  This was not something on my radar, because of the way I shoot and what I shoot I almost never need this---so I hadn't ever run a comparison between the programs for just this purpose.  Now I have and indeed we have a bit of development work to do in this area---- really no surprise considering LZ hasn't upgraded this part of itself for years, now.  Another case involves a new member's suggestion about Lensfun which may offer us a way to finally incorporate lens corrections into LZ.  I know there will be more examples.  Those are 2 more great examples of why a bigger community of members and users helps us all.

4.1.0 AMD 64 vs x 86?

Sorry to ask likely a stupid question...but what is the difference in the above? Thanks.

gusmur.  64 is 64-bit and 86

gusmur.  64 is 64-bit and 86 is 32-bit.  Check your version of linux, mac, or windows.  If in doubt, 32-bit is usually safe, but you could find yourself limited on file size of what you're working on.  In windows, you can right-click on My Computer and go to Properties.  In linux a uname -a, lscpu, or cat /proc/cpuinfo from shell.  Not sure about Mac.

Thanks for listening :-)

Thanks for listening :-)

thanks a lot for LZ4

Very happy to hear these good news. I perfectly understand the registration process, it's a clever step. About the lens corrections, have you a deadline we'll see it incorporated in LZ? Thanks a lot for your efforts :)

There are no deadlines here

There are no deadlines here at the all-volunteer LightZone project.  I can only say that this has been on the wish list for years, going back to when LZ was a commercial product.  I think mainly we try to do things we can, and the order we do them has to do with 1. absolute necessity---the program won't run without this thing.  This is usually some unseen (to the users) code issue, 2. something that's relatively easy to do.

After we release v4.1 as a release candidate, then we move into some unknown territory.  There is some extra stuff we got from Fabio, new stuff that was being worked on when the company folded,  which Anton pulled out so we could get a clean re-compile.  I just spoke to him last week by phone and we will be now getting that stuff to look at and see what's there---we don't even know but had some hints: NR improvements and some browser improvements, maybe more.  Depending on the difficulty we'll work that into the next release(s).

After that we have the wish list.  Lens corrections are top of that list.  Another priority, however, has become an upgrade of the raw adjustments tool to do better highlight recovery, if possible.

We'll waiting patiently,

We'll wait patiently, anyway there is enough stuff already to learn for months or years, depends how much time and skills we have... Again thanks for this devoted fantastic work!

Sourceforge can help, perhaps

I can't wait for my download link to appear. I have version 3.8 but it's unlicensed and it runs in demo mode only.

I too fight the good fight against spambots, etc. I gave up actually(!) and required anyone joining my site to sign up via Facebook. I'm not suggesting you do that (LOL!).

Just curious if you have considered using a 3rd party repository for downloading the program, and why you may have apparently ruled that out. It could be a better experience for everyone, and you'd be able to track downloads and stop spam.

Agree on SF or Github

Both of those can really help invigorate a community. Personally, I find git easier to manage multiple developers submitting patches, but I don't want to start a comment war :-) whatever works for you!

Very happy to help, particularly with beta testing and the occasional patch.


Log in or register to post comments