Version 4.1.5 (bd557dc) - bug report ?


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.


8 posts / 0 new
Last post
EdisLZ
Version 4.1.5 (bd557dc) - bug report ?

Hi,

first of all, I'm not sure if I'm right here, please move thread if incorrect.

I have used Version 4.0.0 before and I don't had problems at all. I have now changed to version 4.1.5, which has a much better start point (after starting editing, the file is no more dark and in wrong colors). But I have very very often new errors:

See here:

http://www.bilder-upload.eu/show.php?file=27a615-1453580452.jpg

http://www.bilder-upload.eu/show.php?file=8689d7-1453582337.jpg

("Ungültige Bilddatei" means: Invalid picture file [hope you can deal with my translation] )

The error occurs every 2-3 pictures - I cannot work this way. After restart it works fine again, the picture files are not invalid! The other features are excellent.

An other thing is, Lightzone seems to be slow. I have a new PC, AMD FX-6350 CPU (*) - the updating prozess if I make changes in a lower layer should be much faster. Do you work on this?

(*) Machine is: Windows 8.1, Gigabyte board, AMD FX-6350 (6 cores), 8GB DDR3 RAM, SSD, plenty of disk space left on all drives. Camera: Nikon D7100

[I cannot attach a media file, access denied - why?]

Edi

EdisLZ
Update: I have removed

Update: I have removed lightzone completely from the disk, using geek uninstaller. Then I installed it again. Unfortunately the effect is the same.

What about this JAVA memory thing? I have read that other software programs have this problem too, which is not a problem of JAVA, but of the software itself. Why not increasing the memory significantly?

 

EdisLZ
Color temperature

Hi,

 

another thing is that the color temperature is not correct, most of the time. It's way to high. I have tested it with Nikon ViewNX2 as reference. Grey card tested: Nikon ViewNX2 says 6500k (which is the correct color temperature of the used lamp). Lightzone says 9400k (same area of the picture) - way to high. This is a minor problem, because the number of the color temperature is not so important than my visual impression.

Edi
 

EdisLZ
changes made - but not saved

Hi,

another thing is:

If I reedit a file and make minor changes, e.g. I change only the "value" (not the arrow) of the exposure (in raw adjustments) and I press the save button, nothing is saved!

Edi
 

Doug
UI Bug?

If I understand what you're saying -- you adjusted the exposure by typing in a new value, rather than moving the arrow -- yes, that's a long-standing bug. For some reason you have to do something else before the typed-in value takes effect. I usually give a light click on the arrow, trying not to move it. Most of the time, though, there are other edits I want to make and as soon as I do those, the typed-in value seems to work.

Photonoxx
Additionally, the bug affect

Additionally, the bug affect the history function. If just value is changed you make something else and go back in the modification historythe value change will not be took into account if I remember well.

EdisLZ
#1 is major problem

Hi Doug,

thank you for your answer. O.k. #4 was a know problem. It's a minor problem, I agree. But what about #1 - do you work on this? Is it a problem of my PC settings? Should I have more RAM memory? 16GB?

Edi
 

EdisLZ
#1 problem solved

Hi,

after changing the version from ...x86 (32 Bit) to ...amd64 (64 Bit) it works well on Windows 8.1 - 64 Bit.

Wondering why nobody thaught about that, anyway now "we" have a solution for this issue.

The problem occured, because I haven't downloaded the version 4.1.5 from here. The other server only offered x86 version.

Edi