|
|
Hi Pix,
This only happens when scrolling through the thumbnails of a large PD3 project that has just been upgraded to PD4, the thumbnails are apparently regenerated "on demand" by PD4 when you scroll through them for the first time.
No such problems when importing new images into a PD4 project (upgraded project or not).
Danny
|
|
|
|
Quote:
Once PD4 has been restarted enough times to generate all the thumbnails the problem is gone.
I discovered that it's not really a memory leak but a problem in the way the thumbnail generation is implemented.
If I scroll through the thumbnails faster than PD4 can generate them, it tries to generate so many at once that it runs out of memory.
But if I wait until all visible thumbnails are generated and displayed (when the busy cursor disappears), PD4 releases all the memory again and I can scroll to the next page, wait until those are generated (memory again going up to the max 32 bit limit), and so on...
So the fix would be to limit the number of thumbnails that PD4 tries to generate at the same time (by not trying to keep up with the scrolling), I think this would actually speed up the process....
|
|
|
Hello Pix,
I can confirm that it only happens while PD4 is building and displaying the thumbnails for the converted project for the first time. You see the memory use of PD4 grow to over 2 GB with full CPU and at that moment it stops displaying new thumbnails and after some time says that "not enough memory is available".
No issue at all while importing new pics in the same converted project.
Once PD4 has been restarted enough times to generate all the thumbnails the problem is gone.
Danny
|
|
|
Thanks Pix, I've had no trouble with new projects so far, only with this converted project...
Danny
|
|
|
A project converted from PD 3, never had any problems with PD3.
Now PD4 (4.0.3419) hangs and gives an out of memory error (black box with the text "not enough memory") when I want to scroll through the thumbnails of a folder containing more than 50 canon raws (CR2, 7D). I can still close PD4 and restart it, and if I repeat this long enough eventually it manages to get them all loaded (each time I restart PD4 it adds about 50 new thumbnails I guess).
Obvious memory leak. There are tools for developers that detect this kind of bug, so this shouldn't happen on a released product.
Danny
|
|
|
Although I have not tried it, is "Find Missing Folder" (right click menu on the folder) not what you need?
|
|
|
I've had problems caused by relics (saved presets) of the Beta and/or PD 2011.
I removed all traces of the beta and all saved presets and so far no more crashes with the release version...
Danny
|
|
|
- If I understand your first question correctly: you can tick the checkbox "Add exported photo's to current project" in the Photo Export dialog.
I use Faststone as an excellent and very fast universal image browser.
Danny
|
|
|
Got the mail today.
Danny
|
|
|
|
Quote:
I see no indication of a need for periodic compaction of PhD3's database. Does this mean that the application's performance will not suffer as more folders are added?
The database format is SQLite, should need no maintenance unless you do massive deletions, and there are tools available for rebuilding SQLite databases in case it would be necessary (unlikely in my opinion).
It's best to keep the preview size set to minimum in the "File Handling" preferences, otherwise importing 1000's of images might become slow.
Danny
|
|
|
|
Quote:
There's no choice on changing the quality option on a JPG export, for example. Based on what I have seen other programs doing, I'm guessing the JPG export quality for PhD3 is 95%.
You have to scroll down in the export window (there is a scrollbar), you can then select the output format (JPEG or TIFF) and the corresponding options (quality, compression, color space, 8 or 16 bits) for each format.
Danny
|
|
|
Especially the fact that all adjustments can now be applied to selected regions.
I asked for this during the beta and hey presto there it is! But I suspect I was not the only one asking for that feature.
|
|
|
It records all changes in it's "project" database, where it also keeps the catalog of all the pictures in the project. You can have multiple projects but this is not obvious and not implemented very well.
You can "reset" all your adjustments (and clear the adjustment history too if you like) for a picture, this allows you to start from scratch.
You can also revert to any stage in your adjustment history.
I don't know if all this is documented, as out of principle I never RTFM.
Danny
|
|
|
I installed the patch (running version 2.0.1928 on Windows 7 ultimate 32 bit fully patched)
I attach the raw image.
I didn't see this on any other image before with PD2011, but I haven't been using it all that long...
Danny
---
|
|
|
I include 3 ca. 200 % crops of the same part of an image, one processed with PD2011, one processed with Raw Therapee 4.01 and one processed with Canon DPP 3.10.1.
The photodirector one has a strange hotizontal line that I have not seen before in any image, and the other raw convertors do not show it either when converting the same raw image.
The PD2011 image shows the same line in other parts of the foliage, on exactly the same horizontal position.
As PD2011 uses the Canon SDK it's strange that Canon DPP does not show the problem when converting the same raw image.
Anyone else seeing this?
|
|
|
|
Quote:
There is no information for this patch, what does it do?
No idea. I didn't check if it solves the "save as" problem. And the crash didn't happen again.
|
|
|
I just updated a 32-bit and a 64-bit windows without trouble (using the patch procedure: Help -> Check for updates -> Update -> Download Now -> run Patch.exe), but it was the English version.
After installing the patch the 64 bit windows version crashed after about 1 minute of adjusting an image (adjust some stuff -> reset -> add area mask -> adjust exposure -> crash).
|
|
|
If you have the preview quality in the File Handling options set on standard or 1:1 instead of minimal, it will still be a problem.
Use minimal and you won't have the problem of the import process taking ages in the rendering stage.
You can also use a few different projects to split your library in more managable chunks, I did that.
The project management feature is still rudimentary (hint hint Cyberlink), but it works and does the job.
|
|
|
Hi Brandon,
The crash may not be directly related to exporting at all.
I can now more or less consistently reproduce it by continually adjusting the same picture (using every possible adjustment and perhaps clearing the history once or twice in the process). If I persist long enough Photodirector will eventually crash in CLImageRetouch.dll:
Exception: 0xc0000005
Fault offset: 0x000444af
Faulting Application: C:\Program Files\CyberLink\PhotoDirector\PhotoDirector.exe
Faulting Module: C:\Program Files\CyberLink\PhotoDirector\Kernel\ImageRetouch\CLImageRetouch.dll
Crashes at the same address in the same dll each time.
If you have a debug version of the application (one that can produce a stack trace when it crashes, and that comes with the .pdb files, and perhaps a tracing facility) I'd be happy to test it for you.
Best regards,
Danny
---
|
|
|
Additional information on export problems:
- adjust a picture (in my case RAW Canon D7 .CR2)
- export the picture
- immediately click in the lower pane on several thumbnails while exporting is going on
You may notice one of the following:
- a crash
- an error message saying that an error occurred during the export (no further explanation)
- an error message saying that "Photodirector can not decode the master"
|
