PicToPainting with Paint Shop pro 2019

[iraisok]

Levi,

All acknowledged ... and I did notice the fuction calls that you made and commented out. I'll look for your next update.

Thanks,

[LeviFiction]

This version starts the strength at zero, and reset changes the strength back to zero so at least the button looks like it's doing something.

I also fixed a few small bugs with the send and close command. It will now do nothing if the preset image isn't available for sending back. And will only create the blended version if the blended version doesn't already exist.

[iraisok]

Levi,

Wonderful! The only very minor [don't care] quirk is if all you do when entering PTP is press Send and Close, you need to click Send and Close a 2nd time for it execute. I believe same is true if you had pressed only Reset then Send and Close. But, normally, you will have loaded a Painting. If so, 1st click of Send and Close and you return to PSP Editor. Looking at the PTP folders. Everything is cleared out.

It's simply fantastic now. I felt it safe to delete updates 1 and 2. Running with update 3.

We are alike in some ways. Always finding ways to improve s/w.

Thanks much,

[bobbyb]

Downloading tensorflow15 did the trick. Seems strange to have to do all these "tricks" with an out-of-the-box software. Does Corel seem to think it works out-of-the-box? Don't they test?

[LeviFiction]

They do test, and then put a list of compatible hardware and minimum requirements.

The fact that we can make it work on machines they didn't intend, is just an unexpected boon for us.

[bobbyb]

So I did a test and set everything to default and gave it a try. It worked. I also discovered, by watching the output folder in my temp space, all the intermediate files created. Some are really interesting. I presume they represent the different strength levels.

[bobbyb]

For anyone interested, I found an application which is about the same. Search for fotosketcher in your favourite search engine. It is from fotosketcher dot com. It has interesting results.... and it is gratis $0.0 but you can donate.

Disclaimer: I have no connection to that site or product.

[taramisu]

I, also, put in a ticket for the same stalling issue. The response was to reset my preferences. Seriously? After all the people who have opened tickets for the same issue? Also, I only purchased this version for the Pic to Paint. I downloaded the plugin immediately and tried it. I altered NOTHING. I'm finding every company's customer service to be worse than nothing at all these days.

[rljk]

For what it is worth, I just upgraded from PSP 2018 to PSP 2020 and had the same problem with Pic to Painting that has been discussed in this thread. For me, downloading the tensorflow 1.5 library and using it in place of the one supplied with the plugin appears to have solved the problem for me.

It was mentioned earlier in the thread that the issue might be related in part to older CPU's not being able to deal with the newer library, and that certainly could be the problem in my case. While I'm running an "Intel i5", it is an older model that I believe predates the "sandybridge" architecture.

I would like to thank all of the people that worked so hard to solve this issue. Because of your efforts, I had to suffer with this problem for only a few days.

Thanks again

[iraisok]

LeviFiction:

You saved me AGAIN with Pic-To-Painting here in Win 7. We know it does not run on [some] Win 7 PC's. Your discovery to replace TensorFlow 1.7 with 1.5 package and the Slider update got me back after having to reinstall PTP. Still don't know why ...

For some explainable reason, I just tried to get into PTP from PSP2019U and it could not load suggesting I reinstall it. I am very aware of what I do on my PC and absolutely have not touched PTP folder or the plugin and saw them there. ALL 61 files in the root of Pic-to-Painting folder in Program Files were MISSING. I can not explain how they disappeared.

I was able to select install from the PSP2019U Welcome Screen. It said "updated." I chuckled. Yep, it reinstalled it. I had to replace TensorFlow 1.7 with 1.5 and the two Slider updates you provided and for my PTP to work properly.

I made sure to capture an Acronis image of my C drive.

Thank you again ... and again!

[RafaelLVX]

While working with Iraisok we found that replacing the tensorflow library with an older one worked for him. No guarantees but here is a download and instructions for trying that.

Tensorflow 1.5 Library - https://drive.google.com/open?id=1b4yV3 ... r0tK2PijkB

Navigate to C:\Program Files (x86)\Pic to Painting\resources\app\app\nnart\lib

rename the tensorflow folder to something like tensorflow-old

copy the tensorflow folder from the zip file into the lib folder

Then try running PicToPainting again.

It's been over a year and two editions of Paintshop Pro and apparently the problem remains. I'm just so happy to say this saved me too.

I'm running a very old Core2Quad machine. This is consistent with what some reported, that the problem would be with be with the minimum hardware requirements. Paintshop Pro 2020 Ultimate works fine but Pic-to-Painting refuses to preview any of the styles (it loads the preview forever and doesn't allow me to move forward at all).

After replacing Tensorflow now it just took me about a minute loading the first preview for a full HD image, then it starts moving quite quickly from preview to preview and also strength (though the strength selector is kinda irresponsive).

Is there a place where we can download Tensorflow 1.5 officially? I suppose it's suboptimal that Levifiction has to host the files, and right now if his mirror dies, everyone is out of luck.

Also, did anyone try a newer version of Tensorflow instead of an older one (2.1 stable for instance)? Could it be a bug in Tensorflow 1.7? I understand it's freely available and open source but I don't know how to get the library as Levifiction got it.

[LeviFiction]

Here is a full listing of all versions of Tensorflow - https://www.tensorflow.org/versions

Following the links will take you to github. I did not get the version of Tensorflow that I'm using this way, I used Python's PIP (package manager) to download the version of Tensorflow that I wanted and then I copied that from the site packages folder and uploaded it to Google Drive. So I don't know what differences there may be downloaded directly from github if any.

The recommendation to use an older version was found online and confirmed through testing. Tensorflow has a lot of low-level code that supports certain processor architectures and commands. So I cannot tell you if it's a bug, or just that it stopped supporting certain hardware architectures. I did have Ira test newer versions beyond 1.7 and those failed for him. We have not tested 2.1. Or, more specifically, I have not. And both of my computers fully support 1.7 so I have no means of properly testing them. If you want to download 2.1 I can probably upload that as well for simplicity and you can test it.

[RafaelLVX]

Here is a full listing of all versions of Tensorflow - https://www.tensorflow.org/versions

Apparently these links are for API documentation (I did see this page while looking for the "official" package you got).

I'm not familiar with Python PIP. I found releases on Github ( https://github.com/tensorflow/tensorflow/releases ), but I assume the source and the library are very different from one another. Between your zip and the official 1.5 source, the folder structure is somewhat similar but ultimately different (not to mention your package has a considerably larger filesize). I'll try to download the 1.5 source release and replace it on my Pic to Painting folder as an experiment but won't hold my breath. Edit: Yeah, that didn't work.

[LeviFiction]

Alright, I went ahead and downloaded 2.1 and it errored out. Which, I suppose, I'm not actually surprised by as Tensorflow 2 was the next big release. So I'm going to start going through the different versions starting with 1.15 and see which is the highest version we can run the current P2P plugin with.

[LeviFiction]

The latest version I was able to get working without issue was version 1.9. Anything after that complained of an unexpected argument. And I don't have time to investigate that. Do you want to try 1.9?