search

ggolggoli / delaboratory

Automatically exported from code.google.com/p/delaboratory
GNU General Public License v3.0
0 stars 0 forks source link

Exporting final image failed #45

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Import TIFF file (originally a Nikon D7000 NEF)
2. Process about 3 stacks
3. Can't save - Exporting final image failed error

What is the expected output? What do you see instead?
JPEG

What version of the product are you using? On what operating system?
0.7

Please provide any additional information below.
I have a 64-bit Windows machine, but can only use the 32-bit build.  I am 
wondering if it is running out of memory since it can only use the 32-bit 
application.  Wonder if there is some workaround.

Original issue reported on code.google.com by sbre...@gmail.com on 14 Jul 2012 at 6:33

GoogleCodeExporter commented 8 years ago 
I saved a half sized tiff and was able to process and save in Delab.  Is there 
some sort of Delab trick (outside of figuring out what would allow me to 
install the 64-bit version) that would allow me to save an image created using 
a full sized tiff?

Thanks

Original comment by sbre...@gmail.com on 14 Jul 2012 at 7:18

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
please try to export all layers, then you will find which layer output is 
broken, also please attach debug.log so we could trace what's going on

it's known issue that huge files may extend 32-bit memory, but I don't think 
Nikon D7000 NEF with 3 layers will be a problem

Original comment by jacekpop...@gmail.com on 15 Jul 2012 at 2:54

GoogleCodeExporter commented 8 years ago 
BTW please use latest development version 0.7.4 and attach debug log from your 
run

Original comment by jacekpop...@gmail.com on 15 Jul 2012 at 2:54

GoogleCodeExporter commented 8 years ago 
Can you also send your installation log? What kind of errors you get? Are there 
any Windows logs you can send that point to why you cannot use the 64-bit 
builds? 

I am still at a loss to explain why you have never been able to use the 64-bit 
build.

Original comment by parth...@gmail.com on 15 Jul 2012 at 2:58

GoogleCodeExporter commented 8 years ago 
@jacekpop - I didn't use the NEF files directly.  I created some tiffs in 
Photivo when I did the bulk of the processing, and used the outputs.  Those are 
large files to begin with, maybe 70MB or so.  When I saved the tiff @ half size 
and then used those much smaller files, there was no problem.  I should try a 
NEF directly in Delaboratory and see what happens given those files are much 
smaller than the TIFFs that were directly opened.

@partha - It is an interesting issue that I cannot use the 64-bit build.  
Someone on the wxWidgets board noted that there is no 'manifest in the 
executable' and suggested the possibility that that may have something to do 
with it.  But, that was speculation.  Too bad, this looks like a great program. 
 I have worked on a few images in Photivo and Delab looks like an excellent 
tool for fine tuning.  I had never worked with CYMK before and have been really 
impressed with its possibilities.

I'll download the 0.7.4 build and give it a try.

Thanks.

Original comment by sbre...@gmail.com on 16 Jul 2012 at 11:56

GoogleCodeExporter commented 8 years ago 
It doesn't matter what is the image format, I just mean that resolution of 
D7000 is not huge enough to produce this kind of problems. I am aware of such 
problem with D800 file and old dodge/burn layer (which was removed later), you 
are talking about D7000 with 3 layers so I don't see how it can extend 2GB.

Please attach debug log from your run.

Original comment by jacekpop...@gmail.com on 16 Jul 2012 at 12:49

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I was able to save a file created directly from a D7000 NEF with create 3 
layers.  I wonder if it was because before this I used TIFF outputs from 
Photivo as the Delab inputs which were about 70MB.

I can try a TIFF again and see what the log says, but when I cd to the Delab 
directory and enter delatoratory-with-logs.exe nothing happens.  When I enter 
delaboratory.exe, it launches.

Thanks.

Original comment by sbre...@gmail.com on 19 Jul 2012 at 1:08

GoogleCodeExporter commented 8 years ago 
OK...we can kill 2 birds with one stone....

What a surprise!

I downloaded 0.7.4 and the 64-bit version works on my machine!!!

And, I opened the TIFF that caused the last version (32-bit) to crash, and was 
able to save after adding 4 layers!

Forgive me if I am a little excited....

:)

Original comment by sbre...@gmail.com on 19 Jul 2012 at 1:34

GoogleCodeExporter commented 8 years ago 
I also wanted to mention another problem cleared up with this implementation 
(that I had not mentioned).  I was not able to export from another program to 
Delab  before.  I created TIFFs and opened them in Delab.  Now, with this build 
I can have the output directly sent to and open in Delab....which is nice as I 
don't have to create TIFFs as an intermediary step, which was time consuming 
and inconvenient.

Original comment by sbre...@gmail.com on 19 Jul 2012 at 1:43

GoogleCodeExporter commented 8 years ago 
To make any serious test you need to compare same TIFF file. Try it in both 
versions of delaboratory, then old version should crash and fresh version 
should be OK. If not then you made something wrong and you need to start over.

Original comment by jacekpop...@gmail.com on 19 Jul 2012 at 11:43

GoogleCodeExporter commented 8 years ago 
Jacek - It was the same TIFF file, and it turned out the file was about 100MB.  
However, since downloading 0.7.4 yesterday, I am not experiencing the issues I 
saw before (not being able to use the 64-bit implementation, crashing on save 
when starting with a large TIFF, and being unable to import an image from 
another program into Delab).  The same TIFF that crashed the older version 
multiple times (every attempt with 3 layers), worked fine on the newer one with 
the same number of layers.  Plus I opened another TIFF of similar size and with 
an additional layer or two, and was able to save it without an issue.

So, from my perspective, things are looking good.  If there is some sort of 
test you would like me to do if you feel it would be beneficial to the project, 
please let me know.  Otherwise, as long as I am getting the behavior I am 
seeing with the latest release, there is no longer an issue from my side.

Thanks.

Original comment by sbre...@gmail.com on 19 Jul 2012 at 1:32

GoogleCodeExporter commented 8 years ago 
In that case we are not able to fix or trace anything, we have no info to 
perform any actions.

Please also notice that the application is called "delaboratory" not "delab" 
just like there is "Gimp" and not "gi" or "photivo" and not "pho".

Original comment by jacekpop...@gmail.com on 19 Jul 2012 at 1:50

GoogleCodeExporter commented 8 years ago 
Thanks for your help.  I don't think there is anything to fix any more since 
the new version seems to be performing well, without any of the prior issues I 
experienced.  I've only played a little with the program so far, but it seems 
like a wonderful tool.  Sorry about playing fast and loose with the name.

Original comment by sbre...@gmail.com on 19 Jul 2012 at 2:40

GoogleCodeExporter commented 8 years ago 
We will reopen in case the problem appears again in new builds.

Original comment by jacekpop...@gmail.com on 19 Jul 2012 at 3:01