Hello,
Ive seen a similiar complaint in X8 forums but no resolve.
Windows 10
i7 930 @2.8
AMD Radeon 5900 2Gig dedicated
12Gig of Ram
file size has been less than a gig to large photos.
I have tried to use the cutout lab, but after previewing and cleaning up the edges, as soon as i hit ok, it crashes the program. The error says the program has stopped working, and only gives me the option of closing the program. I have been playing around and found that if I don't clean up the edges it won't crash. However, without being able to clean up the edges, the cutout tool is useless to me. Does anyone have a resolve for this?
I had exactly the same problem. I know this question is 3 years old, but I'm visiting in January 2021. Every time I tried using cutout lab in PhotoPaint 2017, I could preview it just fine, but as soon as I hit "OK", the program would crash. I was very frustrated, as that particular feature is very useful (I do graphic design) and online free versions don't do as good a job...as they're automated, and you can't clean them up when necessary.
Anyway, I repaired my .net framework (I don't think that was the problem, but Microsoft has a free repair tool on their site called .net framework repair tool. It required me to reinstall .NET version 4.8. Again, I don't think that was the problem, but it certainly didn't hurt. I should've tested cutout lab after making that one fix, but I did the next step too, so I can't be sure which one fixed the problem.) The second step was I used CCleaner to repair my registry (which is what I believe fixed the problem!) In CCleaner from Piriform (it's free)...click "Registry", then scan your system. Check all boxes on the left to scan ALL registry errors, then click fix. It will ask you if you want to make a backup, and YES, ABSOLUTELY MAKE A BACKUP in case something changes in your registry that breaks something else.
After fixing the registry, I rebooted and my computer was wayyyyyyyyy faster!!! I thought "Oh well, it probably still won't work, but I'll try cutout lab again" just to see if anything changed. The first thing I noticed, is that Corel loaded much, much faster than it has in over two years...and <drumroll>......
It works perfectly!!!!! Lightning fast, and no errors whatsoever!
I feel like such an idiot for not having tried this solution earlier. Instead, I did what everyone's probably doing...searching forum after forum, although there aren't a TON of viable solutions, and when you read about Corel's horrible tech support, I didn't feel like burdening myself with THAT whole process.
So, for anyone still searching the internet for solutions with Corel PhotoPaint crashing whenever trying to use cutout lab, I hope this works for you too!!! It took all of five minutes, and I'm totally back up and running, faster than ever!!!!! Woohoo!!!
Good luck!
Dave
Update to my last post. I'm afraid i was wrong. When I originally tested it, I used a very small PNG file, and yes, it worked perfectly. So I was excited and came back here to share the good news! However, I then tried the cutout lab on a larger image. Fail. Then on a different large image. Again, fail (i.e. program crashed). Soooo, I'm back to the drawing board. In the meantime, I found a site online that offers a free online tool, and I used it last night to cut out a boring white sky on a photo of a home (replace with a beautiful twilight sky.) For those that are interested, the site I used is:Remove Background from Images | InPixio Photo Cutout Tool
Hope that helps those of you who are still experiencing problems, and haven't gotten a resolve from Corel.Dave
Another Update (I found a way to make it work...and tested it over and over). This is what I sent to tech support:
I've been experimenting with cutout lab and discovered something interesting. If you only use cutout lab on an object layer, it seems to work fine. In other words, if there's a photo of a house with a sky that's very washed out, and I want to cut the sky out, and put a nice blue sky behind it instead...there are two ways of accomplishing it. One, is to use cutout lab on just the original image, however that seems to crash the program every time I try. BUT...I discovered tonight that if I copy and paste the original image on top of itself, so that it becomes a separate object layer, I can use cutout lab on the layer successfully. It doesn't work on the background (the original image), but it works on the duplicate image when layered on top as a new object.
I don't know why that is, but it's a relief to have found a workaround for the time being. Maybe that also helps tech support figure out what's causing the program crashes when trying to use cutout lab on the background (which used to work, but now doesn't).
Raja from Corel support responded in less than 24 hours when I filed a support ticket (THANK YOU!) and now cutout lab is working PERFECTLY again!!! Here's what was in his email:Please try the following suggestions below:1. Delete Temporary Files•Click on the Windows Start menu at the bottom left side of your screen.•Type into the search box: %temp% (or type the %temp% RUN command window).•Hit Enter and the Temp directory will open.•Hit Ctrl+A on the keyboard to Select All.•Hit the Delete key and then press OK or hit Enter to the message asking if you are sure you wish to delete.•Skip all files that cannot be deleted (there will usually be about 3 to 5 temp files in use by windows at any giventime which cannot be deleted).•Closeout of the temp directory.2. Clear the contents of the messages folder.Steps to delete the files in the Corel messages folder.• Close all programs• Click on the start button• Go to the search box and type Run• Click on the Run program.• In the Open: text box type: %appdata% and press Enter• Locate and open the Corel folder.• Locate and open the folder named: Messages.• Click one file to select it then press CTRL+A to select all• Press Delete on your keyboard to delete the files. Click Skip if you get warnings that certain files may be in use.• Close the window.• Launch CorelDRAW.I hope that helps someone else who's experiencing the same issue!!!Dave