Is ASP ready for prime-time? Tiling & other issues.

[tomsi42]

I've been led to the same conclusion as you guys : ASP cannot be used for serious work for now. So I went back to Bibble 5.2.3...

Personally, I had as many problems with 5.2.3, so I ain't going back. The things that are fixed in ASP compared to Bibble makes it worthwhile to switch to ASP now as it is. If ASP had not appeared, I would probably moved to something else.

I think the problem is purely commercial : Corel wanted to announce their new product at the CES in january 2012 even if they knew the product was not finished. This is completely counter productive because I saw many reviews on the net that are not very enthousiastic (the most positive appreciation was often that it is not so bad for its price!).

Or it could be that they wanted to get more people to use it than the group of beta testers ... And the negative comments usually comes from people deep into Adobe userland - we who use something other than Canon/Nikon get the same crap.

Anyway, I talked with some darktable devs and they said they are currently implementing layers and local adjustements. So perhaps we will have at last a free good raw processor under Linux and Mac by the end of the year...
RB

I think that they should coencentrate on improving speed first - darktable is so slow it's unusable on computers that runs Bibble/ASP fine.

[afx]

Anyway, I talked with some darktable devs and they said they are currently implementing layers and local adjustements. So perhaps we will have at last a free good raw processor under Linux and Mac by the end of the year...
RB

Well, first those guys need to learn how to do CM properly.
and then they need a usable UI instead of style statement.

cheers
afx

[ferdinand-paris]

Just to repeat, I am keen to start using the program, not to bag it. My list is only of those things that are sufficiently broken that they stop me or others from doing so. It's not a general bug list nor a feature request list.

I could add the file deletion "bug" if I understood it better to be sure that it wasn't just user error. I need precise steps, rather than "I think". Pointers to other threads may help.

F_P

[Tadjio]

I could add the file deletion "bug" if I understood it better to be sure that it wasn't just user error. I need precise steps, rather than "I think". Pointers to other threads may help.
F_P

I have had this hit me a few times, but I don't delete very often.
The last time I know I worked on one image, clicked on another and pressed DEL. The first image disappeared

[roland65]

Well, first those guys need to learn how to do CM properly.
and then they need a usable UI instead of style statement.

Yes, it's not perfect I know. But first, darktable is very young and second it's open source : if there are bugs, you can correct them. You can look at the internals and propose improvements, you can report bugs and also fix them yourself.

I liked Bibble because it was very fast and was usable with my Canon EOS 5D (good image quality) and there was an active community of users and devs . But ASP is a nightmare... The worst for me : no communication from the devs. We don't know when they will fix all these issues, and we paid for that situation...
RB

[maggus]

I could add the file deletion "bug" if I understood it better to be sure that it wasn't just user error. I need precise steps, rather than "I think". Pointers to other threads may help.
F_P

I have had this hit me a few times, but I don't delete very often.
The last time I know I worked on one image, clicked on another and pressed DEL. The first image disappeared

Hi F_P,

asking for pointers ....
Some time ago I hit this bug and already reported it here in the forum and also via surveymonkey (b.t.w., is it normal that there is NO feedback like "you submitted sometghing ..." ?).
Yesterday I hit "the same bug again", but now with the <INS> key to create a new version of a file. So it´s not just about <DEL> .... but more general !

best regards
Markus

[ferdinand-paris]

I've added them to the list, but I can't replicate them.

F_P

[Tadjio]

Some time ago I hit this bug and already reported it ... via surveymonkey (b.t.w., is it normal that there is NO feedback like "you submitted sometghing ..." ?)Markus

It is 'normal' practice for Corel not to acknowledge such bug reports both here for ASP and for some time now with PSP.
We have complained, to no avail

[FrankX]

If you read this forum then you could get the feeling that ASP is not ready for prime-time

[Zarastro]

My issues:

1. JPEGs are rendered differently than shown on ASP's UI. This should happen for all JPEGs, but I've clearly noticed the differences when processing images took on an overcast day. The UI insisted presenting the sky with light cyan tones on the UI, while in the processed JPEGs it is shown as it should: gray. This happens both for the Maxxum 5D and the A700.

2. UI sometimes does not update correctly and then the settings of the tool panels disappear. When I minimize/maximize ASP then the UI is correctly redrawn. Happens more when I use the plug-ins, normally zPerspector.

3. Colors are over-saturated when opening in-camera processed JPEG files (A700 and Maxxum 5D). I must turn the saturation slider to -30 to get a normal look on the images, and sometimes not even this makes the images look normal.

4. Rendering of a Maxxum 5D 6MP RAW on the UI is much more slower than the rendering of an A700 12MP RAW. However, when writing the actual processed files on the disk, the rendering time is as it "should be" - that is, 6MP is much more faster than 12MP.

5. Images processed in ASP for A700 feel more brighter than B5 (see item 1). I feel that I'm more compelled to use HR or reducing exposure more frequently on ASP than in B5. This also happens with the Maxxum 5D.

[afx]

1. JPEGs are rendered differently than shown on ASP's UI. This should happen for all JPEGs, but I've clearly noticed the differences when processing images took on an overcast day. The UI insisted presenting the sky with light cyan tones on the UI, while in the processed JPEGs it is shown as it should: gray. This happens both for the Maxxum 5D and the A700.

What are you using to view the JPGs?

2. UI sometimes does not update correctly and then the settings of the tool panels disappear. When I minimize/maximize ASP then the UI is correctly redrawn. Happens more when I use the plug-ins, normally zPerspector.

The joys of video drivers on Linux....

3. Colors are over-saturated when opening in-camera processed JPEG files (A700 and Maxxum 5D). I must turn the saturation slider to -30 to get a normal look on the images, and sometimes not even this makes the images look normal.

Hmm, unless you did something to change the defaults for rendered images, this sounds like a color management problem?
Do you have a calibrated screen and have AS set to use the Monitor profile?

4. Rendering of a Maxxum 5D 6MP RAW on the UI is much more slower than the rendering of an A700 12MP RAW. However, when writing the actual processed files on the disk, the rendering time is as it "should be" - that is, 6MP is much more faster than 12MP.

Check again. I bet you are doing something else that triggers this, like crop or regions. Yet another issue that typically points to a video driver problem.

5. Images processed in ASP for A700 feel more brighter than B5 (see item 1). I feel that I'm more compelled to use HR or reducing exposure more frequently on ASP than in B5. This also happens with the Maxxum 5D.

Yup, AS is generally brighter than B5.

cheers
afx

[spoilerhead]

my experience with colors in ASP looking strange where all very similar and easy to sum up:

* i used the wrong screen profile

when i used the same profile as in Gimp (as my reference CM Viewer) results where virtually identical. Make sure soft-proof is off, too

[Fraenzken]

... one question to afx and the other beta testers (concerning the hopefully forhcoming new version): Are you still smiling?
Cheers
Frank

[thufor]

...one question to Corel: is a release with fixes coming? Current one has some serious flaws... :(

[Zarastro]

1. JPEGs are rendered differently than shown on ASP's UI. This should happen for all JPEGs, but I've clearly noticed the differences when processing images took on an overcast day. The UI insisted presenting the sky with light cyan tones on the UI, while in the processed JPEGs it is shown as it should: gray. This happens both for the Maxxum 5D and the A700.

What are you using to view the JPGs?

Geeqie, GIMP and B5. I used to use Gwenview for viewing images, but as I've started to use ProPhoto RGB I've learned that Gwenview doesn't do CM and thus changed to Geeqie.

2. UI sometimes does not update correctly and then the settings of the tool panels disappear. When I minimize/maximize ASP then the UI is correctly redrawn. Happens more when I use the plug-ins, normally zPerspector.

The joys of video drivers on Linux....

Maybe, but this never happened in B5 for any of the plugins I had. And now it's happening on ASP.

3. Colors are over-saturated when opening in-camera processed JPEG files (A700 and Maxxum 5D). I must turn the saturation slider to -30 to get a normal look on the images, and sometimes not even this makes the images look normal.

Hmm, unless you did something to change the defaults for rendered images, this sounds like a color management problem?
Do you have a calibrated screen and have AS set to use the Monitor profile?

Yes, monitor is calibrated and is set up to use the System Default. I've double checked it some time ago since I found the colors of ASP a tad different from those of B5.

Here's how the color anomaly appears in ASP. I made sure that no settings have been changed using the "Reset Everything" preset in ASP and B5. And since this is a JPG coming straight from the camera, Geeqie should take care of it without problems.



Notice that the histogram of this picture is not normal, and the same happens with every JPEG I throw at ASP - please click the image to see it since it will not be show on its entirety in this forum. OTOH, here's how the image is displayed on B5:



And here's how it's displayed by Geeqie:

4. Rendering of a Maxxum 5D 6MP RAW on the UI is much more slower than the rendering of an A700 12MP RAW. However, when writing the actual processed files on the disk, the rendering time is as it "should be" - that is, 6MP is much more faster than 12MP.

Check again. I bet you are doing something else that triggers this, like crop or regions. Yet another issue that typically points to a video driver problem.

I don't think so. This happens for every MRW file I open on ASP (and B5). Sometimes I shoot RAW+JPEG and then the JPGs appear instantaneously. MRWs on the other hand just appear with the [X] box in the thumbnail view and take long seconds to finally appear on the thumbnail viewer and in the image canvas. And anyway, I'm using the official NVidia drivers on my system - the latest release, 295.17.