What do you like in PSPX9?

[Cassel]

Did you try PSPX9 yet?
Did you play with it?
What do you like about it?

If you want to complain, this is not the place. If you want to post your wishlist for more tools/features, there is another thread for that here:
http://forum.corel.com/EN/viewtopic.php?f=56&t=60016

Tell us what tool/ feature you like, enjoy, or use that are available in X9.

[Joelle]

I like the new way to use the Text Tool

Joëlle

[trueblue]

Definately a lot more stable than previous versions.
I like the new gradient tool and text.

What I don't like and feel Corel are going a bit too far is the cost for templates. People pay enough for the software without having to pay for templates.

[Bonjovicrzy]

will I have been testing this thing like crazy I am testing the 64 bit out found two bugs having problems with the text tool hanging a little bit it opens but waits to think I guess to make its mind up and the Free Rotate I have X8 but I absolute love the SPEED ! of program opening and handling large files ...

[hartpaul]

Absolutely love the correction to the Save command (which corrected the problem from X8) such that if you have a session of processing a number of images the first save goes through the Save as so that the compression is checked / shown. Thereafter the Save acts immediately so long as the program remains open.

[MarkZ]

Absolutely love the correction to the Save command (which corrected the problem from X8) such that if you have a session of processing a number of images the first save goes through the Save as so that the compression is checked / shown. Thereafter the Save acts immediately so long as the program remains open.

Yes, the save function is improved in this version. But it is still a crude, jury-rigged amateurish effort.

I've done a bit of testing - after the first save it no longer invokes "save as" so subsequent saves are faster. As far as I can tell, saving an image previously saved uses the same compression as the last save for that image. But I still have no idea what compression value is used if compression is not specified.

Make copies of an image so that all start the same size. On the first save, save as tells me the compression for that image. Go to the next image and save. For the third image use save as with a vastly different compression from the first image. Then save the fourth image just using save. Now compare the size of the files.

From this test it appears that save uses a default compression of about 20. Compression used in save as is not used in subsequent saves. If you care about the compression of your image you need to use save as each time. For the first image I used c=30, file size=1.22 MB; second save fs=1.87; third, c=1, fs=7.64; fourth save fs=1.89.

We've been asking for this to be implemented properly for years, many people have made many suggestions but the developers ignore it all. Is this a case of NIH? I submitted a suggestion for the logic shown in the attachment, which should be no more difficult to implement than what is used now and received no response.

Save logic.pdf

Proposed logic for save function

(22.81 KiB) Downloaded 504 times

Perhaps if this develops into another longer discussion it should be a new thread.

Yes, Cassel, we're not to complain here, sorry about this - I like the stability, the changes to text entry and gradient fill.

[Cassel]

It might be a hidden detail, but i love the fact that script execution mode is set to silent by default. Being a scripter, i found that scripts run interactively often confuse new users who try to change settings which then cause the scripts to fail, and they don't understand why. Now, they will run silently, and users will get the fastest execution.

[JoeB]

It might be a hidden detail, but i love the fact that script execution mode is set to silent by default.

By this do you mean that when you record a script the execution mode is automatically recorded as silent rather than default, regardless of the execution mode you may have set on your scripts toolbar when you started the recording?

[JoeB]

It might be a hidden detail, but i love the fact that script execution mode is set to silent by default.

By this do you mean that when you record a script the execution mode is automatically recorded as Silent rather than Default? If so then that is generally useful if you are creating a script to achieve a particular effect and don't want to have to edit the script to change Default to Silent. Of course, if there is something in the script you want to give people control over then you do have to edit that step to Interactive.

[Cassel]

By this do you mean that when you record a script the execution mode is automatically recorded as Silent rather than Default?

No, it means that the user who will be USING my scripts (or any script) will run them silently by default. It does not change the way the script is coded or recorded.

[LeviFiction]

No, scripts are still recorded at "default." 'Default' matches the little toggle on the script toolbar. By default that toggle is 'on' for interactive. Now it's defaulted to 'off' for silent. You can still toggle that button and the scripts will obey. If you want to force silent, then you will still have to edit the script and set them to silent. If you want to force interactive then you edit the script and change it from default to interactive same as before. It's just that one toggle that the average user has no clue exists.

[JoeB]

No, scripts are still recorded at "default." 'Default' matches the little toggle on the script toolbar. By default that toggle is 'on' for interactive. Now it's defaulted to 'off' for silent. You can still toggle that button and the scripts will obey. If you want to force silent, then you will still have to edit the script and set them to silent. If you want to force interactive then you edit the script and change it from default to interactive same as before. It's just that one toggle that the average user has no clue exists.

Thanks for that info. Definitely the info a person needs to know depending on if/how they want a user to interact with the script whether they like it or not.

[TonyP]

I am a novice with the program. When shooting stills, I really get what I want from the original image. But there are times when things need to be slightly adjusted.
What I really like is the batch processing capabilities since I have to batch process lots of images to smaller jpg's or whatever.

[Jan Shim]

I have PSP X9 (SP3) configured to launch in Edit workspace as default. Here, I have a customized menu bar that includes various scripts shortcuts on the same tool bar to launch Nik and Topaz plugins. This morning, I accidentally clicked the Manage tab which immediately changed to the Manage workspace. No problems there, except when I changed back to Edit, all my scripts shortcuts that are text labelled all turned into their default buttons! My custom toolbar also got reset to default toolbar. In order to have everything back to how it was, I had to close the program and relaunch. Has anyone had this happen to them too? In all the years I've used PSP this is the first time this particular anomaly has happened.

[Cassel]

I have PSP X9 (SP3) configured to launch in Edit workspace as default. Here, I have a customized menu bar that includes various scripts shortcuts on the same tool bar to launch Nik and Topaz plugins. This morning, I accidentally clicked the Manage tab which immediately changed to the Manage workspace. No problems there, except when I changed back to Edit, all my scripts shortcuts that are text labelled all turned into their default buttons! My custom toolbar also got reset to default toolbar. In order to have everything back to how it was, I had to close the program and relaunch. Has anyone had this happen to them too? In all the years I've used PSP this is the first time this particular anomaly has happened.

Since this thread is about "what do you like in PSPX9", you would likely get more help by creating a separate thread.