PSP2018: File corruption bug

[md12]

I've come across a possible bug with PSP 2018 and support says they cannot reproduce the problem, despite the detailed steps and videos I created for them to show how to replicate the problems. Either they are not performing the steps correctly or they are using a different setup than I am.

The bug is related to copying a layer group from a 16-bit/channel image over to an 8-bit/channel image.

Resetting the application to default settings, as support suggested, does not work. I've managed to replicate this problem on two different computers, both from fresh installs of PSP2018. I played around with different compatibility modes to no avail.

I was wondering if any of you are able to replicate the issue using my reproductive steps below. I'd like to know if this occurs on Windows 7, 8 and 10, or is it possibly just a Windows 10 related issue.


My environment:
* OS: Windows 10 Pro (v10.0.16299 Build 16299)
* Software: PaintShop Pro 2018 Ultimate (v20.2.0.1 x64) <-- This is latest version at the time of this post.
NOTE: I can reproduce the same behavior with the 32-bit version of PSP too.


Reproductive Steps:
1. Create two new projects: Project-A set to RGB 16 bits/channel, and Project-B set to RGB 8 bits/channel. Canvas size and resolution do not matter.
2. In Project-A, add a new layer group and add an image to a rasper layer (e.g. use picture tube tool).
3. Save Project-A.
4. For Project-B, just save it as is with the default blank canvas. Adding something first does not matter.
5. Save Project-B.
6. Go to Project-A, select the layer group, and press CTRL-C.
7. Go back to Project-B and press CTRL+V. The group pastes just fine.
8. Save Project-B again and close it.
9. Try opening Project-B again and you'll receive the following message:
"Unable to open the file. Please verify that the file is valid."

Copying just the rasper layer (not the group) from 16-bit to 8-bit image (or vise-versa) works fine and does not cause any corruptions. So far, I've only been able to replicate this when copying the layer group.

There is another closely related bug that actually makes PSP freeze, and that's to do the reverse operation. Copy the group from the 8-bit image over to the 16-bit, save and close the 16-bit image, then try to reopen it. The app hangs loading the image.

I've uploaded two videos showing both issues (link below). The first one (PSP-2018_Bug-01.mp4) produces the corrupt file problem. The second (PSP-2018_Bug-02.mp4) shows the app freezing when trying to load the image. In the latter video, pressing ESC to abort does not work and the only way to end PSP is to use Task Manager.

Here's the link to the videos: https://www.dropbox.com/sh/hhszggwt3ebs ... Nf9ya?dl=0

I believe these to be bugs, but I would like your help to confirm this. Any help in testing this is greatly appreciated.


Thanks.

[airshac]

I am having the exact same issue. I did notice that it occurred after they asked me if I wanted to upgrade and I declined. Files that are pspimage I created a few weeks ago open fine but the file I created two days ago and yesterday have the "Unable to open..."

[md12]

I am having the exact same issue. I did notice that it occurred after they asked me if I wanted to upgrade and I declined. Files that are pspimage I created a few weeks ago open fine but the file I created two days ago and yesterday have the "Unable to open..."

Yep. Just don't copy any grouped layers from a 8-bit/channel project to 16-bit or vise-versa. I'd suggest backing up of your important image project files prior to working on them, just in case you run into this problem and lose you work. I have a development server with VisualSVN, so I just use that to keep mine backed up and versioned. This way, I can go back and revert to a previous version if needed. Works out well for me.

[hartpaul]

I was able to duplicate your bug on Win 10 version 1607 and PSP 2018 ver20.0.0.132. However I experimented a bit more
- after copying and pasting the 16 bit group to the 8 bit image do Image > Increase Color Depth > RGB - 16 bits per channel and then save that as the PSPimage file. That file should reload correctly and also can then be converted to a color depth of RGB 8 bits per channel
It would seem that the bug project has a 16 bit / channel image on top of an 8 bit / channel image yet Information ( Shift I ) shows only the 8 bit component. The image saves , but when PSP tries to reload it the 16 and 8 bit parts confuse it so it gives up and says it cannot load it.

The question now becomes do you really want an image where parts are 16 bits and parts are 8bit

Just another thing I found - If as you go to save your image you select Options and set it as PSP8 (Jasc PSP8) compatible then there is no problem and it saves and can be reloaded. I have not tried with later version.
Also works with PSP9 compatible and problem only starts with PSPX /PSP10 version.

[JoeB]

Good find, @hartpaul. So does it actually constitute a bug? That is, is a graphic program expected not to be confused when opening an image with both an 8 bit and 16bit layer in the group? I wonder how Photoshop handles it, assuming it has the same type of grouping abilities so that the comparison would be relevant.

EDIT: Just a thought, but perhaps when working with images of different bit depths where the user wishes to group the layers it would make sense to simply convert all to the same bit depth before working with them. As for PSP itself - and while I doubt we'd see this added - it wouldn't hurt if there was a warning that one was placing images with different bit depths into layer groups, or alternatively PSP would automatically increase bit depth of all layers to the highest bit depth with a window reminding the user that would happen. I'm not sure either is really worth Corel's effort given this is the first post I've seen in all my years here regarding the subject.

[md12]

The question now becomes do you really want an image where parts are 16 bits and parts are 8bit

Thanks for the feedback and advise. Most of the time, I'm working with 16-bit RGB and to answer your question (which was probably a rhetorical one, but I'll answer anyway), is normally no, I usually work in 16-bit RGB. However, this bug first happened to me right after installing 2018 and I created a new 8-bit file (not realizing it) and was copying a set of grouped layers from an older 16-bit image file to my new one. If I had realized it before saving and closing it, I would have increased the color depth and it would have been fine, as you stated. Lesson learned. But... that's what happens when PSP spoils you on remembering your settings from the last created image. Since I usually create 16-bit, I'm not used to always having to change that setting.

Anyways, after going back and forth with support, I finally convinced them that this isn't a settings problem but a bug, they pushed it over to the development team (supposedly) to investigate. Maybe we'll see a fix for it within this decade.

[JoeB]

[ Maybe we'll see a fix for it within this decade.

I am wondering, based on @hartpauls addition to his post about saving in PSP8 compatibility, whether the older Jasc versions either did change the bit depth of layers when added to a group or if it actually would open the image regardless of the different bit depths. He didn't say whether or not the layers retained their respective bit depths. Not a biggy - just a niggle.

[md12]

Good find, @hartpaul. So does it actually constitute a bug? That is, is a graphic program expected not to be confused when opening an image with both an 8 bit and 16bit layer in the group? I wonder how Photoshop handles it, assuming it has the same type of grouping abilities so that the comparison would be relevant.

JoeB - If you were to copy a 16-bit rasper or vector layer to an 8-bit (or vise-versa), the conversions are done with no problem and saving it doesn't corrupt the file. BUT, if you take that same layer and put it in a layer group then copy the group over, that's were the bug comes into play. So why does this problem occur only with the group copy/paste? Because of that scenario and question, I still believe it to be constituted as a bug.

[JoeB]

Good find, @hartpaul. So does it actually constitute a bug? That is, is a graphic program expected not to be confused when opening an image with both an 8 bit and 16bit layer in the group? I wonder how Photoshop handles it, assuming it has the same type of grouping abilities so that the comparison would be relevant.

JoeB - If you were to copy a 16-bit rasper or vector layer to an 8-bit (or vise-versa), the conversions are done with no problem and saving it doesn't corrupt the file. BUT, if you take that same layer and put it in a layer group then copy the group over, that's were the bug comes into play. So why does this problem occur only with the group copy/paste? Because of that scenario and question, I still believe it to be constituted as a bug.

I get your point.

[flagpole]

This comes up sufficiently often that it seems beyond coincidence.

[hartpaul]

[ Maybe we'll see a fix for it within this decade.

I am wondering, based on @hartpauls addition to his post about saving in PSP8 compatibility, whether the older Jasc versions either did change the bit depth of layers when added to a group or if it actually would open the image regardless of the different bit depths. He didn't say whether or not the layers retained their respective bit depths. Not a biggy - just a niggle.

Back in PSP 8 these were the choices for a new document.

So as can be seen there would be no 16 bit / channel available.
I am guessing that PSP8 would automatically convert any oddity to a uniform 16 million colors (8 bits / channel).

[JoeB]

Thanks hartpaul. I had a sneaking suspicion that was the case. So it seems that the image can then be opened everywhere because it no longer contains a mix of 16 bit and 8 bit layers in the group. If that's actually what happens with PSP 8 then perhaps it would be easy enough for Corel to make the save/save as functions upscale the color depth of all layers in the image group to the highest color depth of any particular layer. But I'm not a programmer so maybe not so easy?

[md12]

For those interested in knowing, Corel has verified this as a bug and the latest response I received from them is as follows:

The issue that you contacted us about has already been directed to our engineering team to look into and hopefully get resolved in a timely fashion. The earliest a fix is possible is in a future service pack or new version. We cannot comment on what may (or may not) be in as yet unreleased software. This includes both features and fixes.

Regards,
Cho
Corel Technical Support Services