(by Hans Loepfe, HALO Photographs, Switzerland)
This Report has been submitted to SIGMA by means of my distributor in late summer 2007 short after purchasing the new SIGMA SD14.
In early 2008 SIGMA has released Photo Pro 2.5 and it runs stable.
Hence this report renders oblivious.
My personal assumption is that SIGMA tried to write the RAW-Conversion Software on their own. As a result SIGMA released SPP3.0 and then upon major customer complaints SIGMA was forced to obtain the stable version SPP2.5 from FOVEON Inc..
There are two major advantages using SIGMA Photo Pro 3.0 instead of SIGMA Photo Pro 2.1.
- Especially the strong noise in dark images sections (taken with long
exposures) have been taken care of.
- Also it is a great advantage to be able to use the Arrow-Keys for adjustments
in the colour-balance wheel.
- There are many more advantages which I do appreciate.
SIGMA Photo Pro 2.1 shall serve as level of programming quality. SIGMA Photo Pro 3.0 certainly needs major improvements.
To me it seems that the issues and problems related to SIGMA Photo Pro 3.0 are mainly caused
by an insufficient quality of Memory Management by SIGMA Photo Pro 3.0.
Below I am going to list such occurrences. Cases 1 through 9 can be reproduced.
The cases 10 -13 though appear infrequently and probably depend on the current
state of the system.
Some of the issues (10 -13) may or may NOT occur when running SIGMA Photo Pro 3.0 as the
only application currently active.
The moment a user has one or more applications active then SIGMA Photo Pro 3.0 most likely
will run into some or most of the issues listed below. Most certainly when Adobe
Photoshop CS2 and/or (in my case) iView Media Pro 3.1 are concurrently active.
The simplest and only work-around until SPP 3.x will be released is as follows:
When encountering any problems or misbehaviour of SIGMA Photo Pro 3.0, close and restart SPP
3.0.
If that does not help close all other running applications and restart SIGMA Photo Pro 3.0
or then even restart your PC and run SIGMA Photo Pro 3.0 as the only application.
Before the listing of the problematic issues begins, I’d like to make a few
suggestions hopefully to be implemented in future releases of SPP 3.x.
There is no application covering proper image conversion, editing and
management. Hence SPP 3.x should take into account that users normally have
several applications active in order to manage their digital imaging assets in
an efficient manner.
I believe most of the issues can be resolved when SPP 3.x receives the following
important enhancements:
- Enable proper Memory Management (for PC and MAC).
Many examples below illustrate such ‘memory related’ problems.
- Enable split processing:
The process of actually converting and saving one or more files should be
separated from the main set of code.
This would allow a user to continue image adjustments in SPP 3.x while the
actual conversion of selected X3F files occurs in a separate program.
Currently SIGMA Photo Pro 3.0 does not allow further image adjustments while the sub-process
(in SIGMA Photo Pro 3.0) of converting and saving images is active.
- Display a processing indicator
In the X3F image overview window should be an indicator showing whether SIGMA Photo Pro 3.0
is currently processing.
- Improve the reading of the X3F files like in SIGMA Photo Pro 2.1.
It seems as if SIGMA Photo Pro 3.0 renders each image fully before it can be displayed in
the main window. SIGMA Photo Pro 2.1 has the ability to read preview or thumbnail images off
the X3F file much faster.
- Enable the Enter Key (as in SIGMA Photo Pro 2.1)
When pressing the Enter Key, SIGMA Photo Pro 3.0 does not react (at any instance).
The user must click the OK-button and cannot press Enter manually.
- Let the user predefine a starting folder as an option in user preferences.
SPP3.0 remembers the last used working folder and upon start-up reads from the
SPhotoPro.ini-File and goes back to that folder loading all these images first.
Normally this is not the intention of a user.
SIGMA Photo Pro 3.0 starts in the last used folder. There should be options to be set as
follows:
• Current default: starting folder is where user left-off during last use
• option1: starting folder is user defined (user has to set a folder)
• option2: Current folder. Start in folder where user double-clicked a X3F image
file
The same applies for the save options (described below in the ‘experienced
problems’ section, case 3)
- Resetting the White-Balance
It would be convenient to also have a reset button for the White Balance.
Resetting the image back to the X3F setting does not include the resetting of the
white balance.
The reset buttons only change the value for Tone- and Colour Adjustments to zero
(0).
There is no reset button for the White Balance.
The Information Panel indicates the original WB-setting in parenthesis.
In case one wishes to reset the White Balance one must check the Information
Panel and manually adjust the WB-setting to the value in parenthesis (the
ex-value). (please refer to Illustration A)
Illustration A
- Allow the White Balance calculation to take current adjustments into account.
While an image is being adjusted (to whatever a user might adjust it to), it
would be a great advantage when at any stage the automatic White Balance
function would take into account the currently set adjustments.
As of now the White Balance function relies solely on the unadjusted image
information of a X3F file.
Upon changing values in an image, consequently the histogram changes hence the
white-balance changes as well.
It would be very useful the have a function available that re-calculates the
white-balance based on the changed histogram of the image that is currently
being edited. (same as above)
Of course there should be something like a preview and step-back toggle switch.
- Let the user predefine a global template that can be added to the ‘auto’ mode
function.
(This in addition to the useful templates).
For example: when converting images in 'auto' mode, about 80% of the images get
the X3F-Fill value set to +0.3. This new template would now enable the user to
say, yes keep all values calculated by the ‘auto’-mode, but in addition to the
results of the ‘auto’- mode function, change the saturation value by +0.2 and
change X3F Fill value by -0.1 (or whatever values the user might want to have
changed by the ‘auto’-mode function).
This becomes useful for example with images shot with a lot of bright background
and with the object exposed properly. The ‘auto’-mode function cannot know that
such a bright background is wanted by the user and adjust the image histogram
optimally from a mathematical point of view. The result though may be unwanted
and manual adjustments need to be applied for each single image. This global
template would allow the user to change the Highlight value to +0.2 to
compensate for all further ‘auto’-mode calculation of selected images.
There is similar partial approach possible by setting some values in the camera.
But these are treated like one template and not as a combination.
The moment the ‘auto’-mode function is applied these values are set back to
zero.
What is needed is a combination of at least one (or more) global template, that
adds (or subtracts) the values given in X3F or the values that are calculated by
the 'auto' function. Consequently this global template should then also be
applied to the templates saved by the user.
In order to let the user choose the desired working mode (with or without global
templates) this option should be set in user preferences.
Also when in 'edit' mode there should be a switch allowing the user to enable or
disable the global template for the image(s) currently being adjusted.
All experiences and issues described below were encountered on a Windows XP
machine with HT Technology active by Microsoft XP. (HT = Hyper-Threading /
splitting CPU Power among applications)
Illustration B
All of the PCs hardware have been verified and checked for proper functionality
before I released this report.
The order of case listing below does not reflect importance or relevance. It’s
simply a listing of experiences of which many (not all) can be recreated for the
improvement of the code from SIGMA Photo Pro 3.0.
SIGMA Photo Pro 3.0 does not properly interact with the Operating System. Instead SIGMA Photo Pro 3.0
loads the needed information into its own memory space.
For example: when deleting a X3F file SPP 3.0 must 'reread' the whole currently
open folder in order to continue. This results in consuming unnecessary time.
When SPP 3.0 is loading AND the user start to scroll down to look at some images
(SPP 3.0 is still loading) then after an image is selected for applying
adjustments, SPP 3.0 may throw an error. In this case simply restarting SPP 3.0
does NOT help.
If there are other open applications these have to be closed or the PC must be
rebooted.
This issue is most likely directly related to the previously described problem.
(see Illustrations 1, 2 & 3)
SPP 3.0 stopped processing to display images, see the time at bottom right
Illustration 1
3 Minutes later, SPP 3.0 still does not continue, see time bottom right and next
screen shot of Task Manager
Illustration 2
Depending on available RAM SPP 3.0 limits itself reading the amount of X3F
Files.
Windows Task Manager shows SPP 3.0 as ‚idle’ (CPU usage = 0)
Illustration 3
Solution:
Kill SPP 3.0 by means of the task manager and restart.
SPP 3.0 eats up all available processing power
When starting up SPP 3.0 the Task Manager shows CPU usage near to 52% (this
value includes the Task Manager).
Illustration 4
Illustration 4 shows that at start-up SPP 3.0 is processing each file in the
current folder. SPP 3.0 probably reads the whole content of the current folder
into memory and hence cannot properly interact with the operating system.
Starting folder
SPP 3.0 does not know where it started. When saving a file SPP 3.0 proposes the
last used drive/folder a file has been saved to instead of proposing at least
the drive/folder of where the currently opened file is located.
Save options should always be at the drive/folder level of the currently opened
image file and not at the last used full path to save an image file.
(Illustration 5)
Saving to a previously existing folder ‘P1’ (that has been deleted meanwhile)
results in the following (correct) message (Illustration 6). This to proof that
SPP 3.0 keeps its previous information from the last session. This information
is stored in the SPhotoPro.ini located in the Programs folder.
At least the setting for ‚LastBrowsePath=K:\IMAGES\2007\07_05 Il
Pirata\P1\converted’ should be a user defined option. So SPP 3.0 always starts
at the same point (ok only for those who wish it to be that way).
Illustration 5
Illustration 6
A X3F file has been opened in Folder K:\IMAGES\2007\08_07\P1\Test.
Upon saving the file (‘Save Image as…) SPP 3.0 is not capable of remembering
where from the file was opened.
SPP 3.0 even suggest another drive ‘J:’. (Probably because SPP 3.0 reads that
information from the SPhotoPro.ini-File.)
(pls refer to Illustration 6a)
Illustration 6a
Refresh Function
When creating a new Folder, the REFRESH function does not work.
The Illustrations 7 – 10 clearly show that. Please compare the time indications
of the time when the folder was created and the systems time (the systems time
is properly and externally synchronized)
This case illustrates that SPP 3.0 does not properly interface with the
operating system (OS).
Situation:
SPP 3.0 is open and running idle. By means of the Filemanager I created a folder
named ‘Test’ at 06:26. The System time is 06:31 when the screenshot was taken.
The Refresh Button (F5) has not been pressed (please refer to Illustration 7)
After pressing the Refresh Button (F5) / System Time 06:36 (please refer to Illustration 8)
Only after restarting SPP 3.0 / Folder ‘Test’ shows properly (please refer to Illustration 9)
Illustration 7
Illustration 8 - After pressing the Refresh Button (F5) / System Time 06:36
Illustration 9 - Only after restarting SPP 3.0 / Folder ‘Test’ shows properly
Memory Management
Apparently SPP 3.0 cannot handle all the images taken on one 4GB CF-Card at once
and throws the (wrong) error below.
(I would assume this is part of the whole memory management problem).
Folder ‘Test’ contains 343 X3F files from one 4GB CF-Card.
SPP 3.0 complains that there are too many files in the current folder (Illustration 10)
Illustration 10
SPP 3.0 claims that there are too many pictures in the current folder !!
This clearly indicates that SPP 3.0 has a memory management problem. It cannot
properly manage its own assets (the images)!
In this situation clicking onto an image for conversion SPP 3.0 throws the
following (wrong) error message:
This error is NOT due to an error in the X3F File! This error is due to poor
memory handling capacities.
Solution:
Find out how many X3F files SPP 3.0 can handle on the current system and split
them up into sub-folders.
(In my case with 2 GB of RAM some 100 images per folder named P1 - Px mostly
works fine).
The error message above seems to be somewhat a standard message as it is thrown
very often even if it is unrelated to the issue (please refer to the following
cases below).
In this case SPP 3.0 does not carefully handle a user activity.
For example:
A user applies adjustment to an X3F file and clicks the button ‘Save image as…’.
Then SPP 3.0 correctly warns the user if such a file with the same name already
exists - so far so good.
In case the user selects and clicks ‘Yes’, then everything is fine.
In case the user selects and clicks ‘No’, then SPP 3.0 overwrites the X3F
template (it should not as the user selected ‘No’)!
The warning comes one step too late (or SPP 3.0 is one step ahead) as the
template is already overwritten with the unwanted new adjustments.
This happens only when the option to save the X3F settings is enabled.
Illustration 10 shows the Information panel with values in the template of the
file to be saved (after it has been reset).
Illustration 11 shows the same Information panel with values already changed in
the template but the user has not yet answered the question to overwrite or not.
SPP 3.0 just overwrites – no matter what the user decides.
This does not correspond to the intention of the user. When the user presses
cancel NOT one value or file shall be changed – neither in the X3F nor in the
TIF file.
The way it is implemented now does not allow the user to revert to the previous
state of the X3F file (remember the user pressed ‘Cancel’).
Illustration 11
Illustration 12
Indicator for Processing status
In the X3F image overview window should be an indicator showing whether SPP 3.0
is currently processing.
It takes about 0.64 seconds processing time per X3F (*1) image to be shown in
the main window. For 120 X3F images this calculates to some 48 seconds until the
user can start with single image processing. Starting any earlier with single
image processing may (not always) result in a (wrong) error message.
In any case single image processing start only after all images are shown in the
main window.
(*1) this number depends on the processing power (CPU and RAM)
available.
Footprint
It is very inconvenient that the user cannot align two (2) X3F images side by
side without overlapping them.
The adjustment of the converter window width is limited even the display size is
reduced to 16.7% for both images.
This applies for both image orientations (portrait and landscape).
(The screen size in this example is 1280 x 1024)
Illustration 13
(This occurs infrequently and cannot be reproduced at all times.)
When using the adjustment controls with two different images open then SPP 3.0
may (*2) stop processing after switching from one image window to another and
applying adjustments after 3-4 times. There is no error message displayed, SPP
3.0 just freezes.
(*2) this again probably depends on the processing power (CPU and RAM)
available.
Illustration 14
Closing and reopening those images creates again the (wrong) error Message:
Solution: Close and restart at least SPP 3.0 or in the worst case restart the
PC.
(This occurs infrequently and cannot be reproduced at all times.)
Two images in two converter windows are opened and adjusted. First one image is
converted and saved with save setting to X3F source file enabled. Then after
changing the saturation in one image to ‘– 2.0’and saving this file without
enabling safe setting to X3F source file the image remains displayed correctly.
Clicking now onto the X3F option (auto / custom) SPP 3.0 throws a (wrong) error
message.
Note: take note that in the Control panel the saturation is set to ‘0.5’ while
the image (SDIM0520.X3F) is still displayed totally desaturated.
It seems this happens randomly and not only when two images are displayed
simultaneously but also with one image open only. I was not able to reproduce
this error precisely.
Note: take note that in the Control panel the saturation is set to ‘0.0’ while
the image (SDIM0532.X3F) is still displayed totally desaturated.
Illustration 15
Illustration 16
An observation
The standard error message
It seems as the message above is displayed whenever SPP 3.0 encounters some
problems to properly accessing data stored in memory.
The best remedy is to simply shot-down SPP 3.0 and restart it (somewhat equal to
rearranging the memory allocation SPP 3.0 is using).
(This occurs infrequently and cannot be reproduced at all times.)
Sometimes SPP 3.0 simply stops to respond.
No error message, nothing.
In this case even restarting SPP 3.0 does not help. Only a restart of the PC
resolves the issue until it occurs again.
I have no idea about the reason that might cause this – but I assume memory
management.
Illustration 17
(This occurs infrequently and cannot be reproduced at all times.)
For Images (X3F form SD10) that have been rotated in SIGMA Photo Pro 2.1 previously SIGMA Photo Pro 3.0
may throw the usual (wrong) error.
To prevent this simply restart SIGMA Photo Pro 3.0 and DO NOT convert X3F images from an
SD14 just go to the folder with the images of the SD10 and it mostly works fine.
SIGMA Photo Pro 3.0 is able to process X3F files form a SD10, provided that image has NOT
been rotated.
One can rotate the image back to its original position and SIGMA Photo Pro 3.0 will process
the file.
Thus one can assume a limited backwards compatibility of SIGMA Photo Pro 3.0 to SIGMA Photo Pro 2.1.
I have expressed my opinion and posted this Report on DPreview.com, but they have blanked out the URI leading to this page.
My opinion on DPreview
In case you would like to contact me please use this Contact form: Contact & Anfragen