Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.


  • Posts

  • Joined

  • Last visited

Everything posted by hy13

  1. When saving a processed file as *.afphoto document one can close the still open document afterwards immediately (of course). The default for the file name on "save under" operation is taken from the input file with the appropriate ending automatically added. When additionally exporting that file e.g. as *.jpeg without changing anything in the document, AP requests an additional save operation for the already saved *.afphoto file before allowing to close the file. 1. For efficiency reason (save extra time for unnecessary save operation and extra click on unnecessary dialog) I request to change that behavior to "do not request extra save after export when the AP document remained unchanged since last save operation before export". 2. When multiple files, e.g. for a Panorama, are processed, the default file name for the following "save under" operation is not taken from anyone of the input files, instead the string "unnamed" is provided as the default. When working in a sequence on a bunch of panoramas, then it often happens that you miss to rename the file before saving it and consequently overwrite it with the next "unnamed" default and thus loose your work. For efficiency and safety reason I request therefore to use the first filename of the processed panorama input files as the default instead of "unnamed". This makes sense of course as well for other operations on multiple files (stacks etc.)
  2. I fully agree to that above request. That is why I still use 1.7.x for production and load the later versions only for test purpose. AP started in their first versions with the stress on efficiency and this was even an advantage over PS. Meanwhile that advantage faints piece by piece.
  3. @Gregory St. Laurent UPDATE: Things proceeded much faster than I expected because I had the old *.8bf files from V17 sitting somewhere on my computer as I made experiments with Photoshop at that time. The solution was to delete the *.8bf files dated from 2018 from the AP plugin directory and reference the old ones from April 2017 (V17) instead via additional path in AP preferences/Plugins. There was no need to uninstall V18 for me. I guess if we had some old *.8bf files from Portrait Body we could make this one work as well. What a pity that I startet with V2 which had the *.8bf files from 2018 already. Perhaps you know someone who could test that for us and give us the proof.
  4. @Gregory St. Laurent Thanks for returning on that issue. And of course your experience is not unvalid. As I understood, you had V17 working and when V18 arrived you lost that functionality after installation. Well the difference to me is, as I understand it now, that you uninstalled V18, reinstalled V17 and then upgraded to V18 again. What I did was only upgrading V17 to V18 and then there was no function. I will try now to uninstall V18 first and then do your sequence. I will be back to report what happened the next days. Meanwhile I got a response from Anthropics: They state only that there is no interest by Anthropics to support that interface to AP. Well, I think that I should inform them now that I lost interest in Anthropics products further on and will close down the news channel. As I am informed there are other products available which do a very good job on that task and I will have a look to those products now.
  5. Thanks to all for your information. Perhaps that mentioned extension will arrive some time.
  6. As I read somewhere in the beta forums, the functionality of macro in AP was extended. Where can I find the description of those new functions? And in addition to that I will ask why there is no capability of macro recording for "save" and "close" documents operations. When doing mass editings this would be a great help. Thanks in advance for your reply.
  7. @Gregory St. Laurent Thanks for your reply. Your discussion is known to me, but my first attempt to use Portrait Pro as plugin was in AP 1.7.2 where I assumed that it should do because of some positive news found in the release discussion.I fear, that your experience is not valid in general. My Portrait Pro 18 is an upgrade to V17 and with Body Pro V2 it is the same issue, but it was no upgrade. Even worse: I made the rollback to AP 1.7.1 release version and there is no function as well. As recommended, I deinstalled AP 1.7.2 first, but was astonished then, that all my 1.7.2 stuff (own macros and filter plugin links) was available in new 1.7.1 as well without any action needed. And there was no requirement to input license code during 1.7.1 installation. That is why I rechecked the 1.7.1 version number on startup, but it is as expected shown on the splash screen. Meanwhile I have the suspicion that behind such things there is a lack of cooperation will between serif and other software companies (see as well the comments from Mark Ingram towards AcdSee). Nevertheless I addressed the problem as well towards Anthropics and will see if there is an answer the next days.
  8. Installed Release Version 1.7.2. of AP today. Afterwards configuration of Portrait Pro 18 as plugin. Plugin did show up then under Filter --> Plugins -->"PortraitPro..." Pixel layer containing Picture with a face was marked in Photo Persona. After clicking "Portrait Pro" AP hangs and must be killed by task manager. Task manager did not show a process in that state where Portrait Pro could be assumed behind. Same happened after configuring Pro Body 2. What I should mention is that all NIK Filters are working. As various users in AP forums give different experiences with the plugin interface, could you please inform if this is an acknowledged error or what state that topic has inside Serif meanwhile. Is there an official howto (besides that of 2016) available about the configuratio of that interface? Thanks in advance.
  9. Congratulations to the team who convinced so many users to give AP a try. Purchased immediately my own copy for windows after first viewing all the demo videos. What I like is the bunch of ideas which improve workflow so much compared to the most referenced PS product. Especially the multiple "merge file" operations are convincing (HDR,stacking, etc.). As there are tons of database and picture file administration tools it would be a nice "roundup" when the workflow: File viewer-->AP-->Merge to HDR or other would be supported by a functionality like "collect all open files to a merge list" and select from there. But in general I think it is a good procedure to not try to copy too much functionality from existing software products because the good ideas will get lost.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.