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

Posts posted by hy13

  1. @Miguel del Rio

    As we got to know in between, Serif changed the behavior of the grid function. Automatic mode in V2 now shows the new "pixel grid" which is so tiny that you don't recognize it in a normal zoom state. This pixel grid did not exist in V1. OK so far. But what does not work properly on my computer is the "Basic" mode. In this mode you can define your own grid spacing and color. But Photo V2 does not keep this setting. When you load another picture, than Photo V2 automatically sets the mode back to "automatic" which is again the not wanted pixel grid.

    At present, the only solution for those who want to use the V1 grid function as known before is to write a macro which sets the "basic" mode each time you need it on a one click basis. V2 can keep the user defined color and spacing values, but not the mode setting, what I classify as a bug because it hinders the workflow.

  2. @walt.farrell

    general statements: V1 and V2 share the same computer and operating system and no change in hardware so far.

    further test results:

    1. changing the key table entry from CTRL+' to CTRL+# makes the key mechanism work. This results from the fact, that one needs to press the SHIFT key, which is not indicated in the dialog text. There is written CTRL+' and not CTRL+SHIFT+'. Different software behaves different at that point, but OK.

    2. In V1 the grid mode is set to "automatic" mode as default and switching grid from on to off and vice versa works fine in that mode.

    3. in V2 the grid mode is set to "automatic" mode as default and switching grid from on to off and vice versa does not work.

    4. changing the grid mode from "automatic" to "basic" while file remains open makes grid --> on/off work via menu and as well via shortcut

    5. the "basic" mode setting gets lost after changing to another picture file even when AP 2 stays open in between.

    6. when you save the picture file after having grid mode set to "basic", the grid mode "basic" is back on reopen of that same file. Thus any other opened picture file is opened in state "automatic" again until you save it in "basic" mode, too.

    7. Changed grid colors however are memorized until you change them. Even when AP 2 was closed in between.

    Is there some other parameter or operation which makes AP 2 to memorize grid mode once it was changed? I do not think, that Serif intended to let me open some 10.000 files in order to save grid mode inside those picture files.

  3. 1. From the beginning, after loading a file for edit, the menu item View -->Grid on/off is not working. The hook is set or reset, but no grid to be seen in either state. The same with key shortcut CTRL+'

    2. After configuring under "View-->Grid and axes..." it is possible to switch grid on and off via View-->Grid menu item, but key shortcut CTRL+' is still not working.

    3. Zooming in, like described in help file, does not show grid either

    4. After closing the modified file and loading another file for edit the situation is again like under 1.

    5. Configuring "View-->Grid and axes ..." and saving the configuration under a new name is memorized, but not loaded when opening another file for edit. This means: for every new file to edit a reload of the stored configuration is necessary before one can switch the grid. Mind: Shortcut CTRL+' never worked as expected.

    AP V 2.0 under Win 10 Pro

  4. It was the "new" license model of Adobe that made me look into Affinity Photo. After a short time of trying out I found a lot of workflow improvements over PS and consequently changed to that new product. And this was not a bad decision. The other Apps I purchased mainly in order to support Serif because I hardly need and use them. However, nothing is perfect, and so I, too, have some wishes towards Serif regarding AP as the focus:

    1. Stay with your actual license model and ask for extra money on updates when needed. On machines in production use, internet is a risk and costs performance. As we all are forced by leading companies to change hardware from time to time, it is convenient to keep internet on the "old" hardware separated.

    2. Solve annoying bugs in acceptable time and reduce number of beta versions in return if that helps

    3. Look more into workflow subjects (e.g. macro) than into new (Pro) features. Increase that intelligent little things that make it smart and fast to use

    4. A DAM from Serif would be nice but is not the urgent thing. There are products like AcdSee in the market which are sufficient in their features and ultra fast when using two screens for photo work.

    BTW: I am not a Pro, but working speed is a must for me. Its often that I have appr. 2000 shots per Event on my storage card with resulting 50 to 100 photos to develop and process. And then its a real difference if you need 5 hours for that or 5 days. At present that is my most important feature of AP when I compare to other products.

  5. @photoShooterYour question is well understood because no one ever knew exactly where to Affinity Apps are heading or not. On the other side: they did not request any money for years to pay their development (besides the low application cost for the first license fee). For most users, I assume, it will be more important to get the workflow streamlined inside the existing apps because they came from PS, etc. and were looking for an alternative offer without cloud, without monthly paying, without ...

    If it helps: there are other good offers in the market which provide that DAM functionality together with a certain "adaption" to Affinity Apps (show .afphoto thumbnails, drag and drop to AP Editor) together with a fast response in large photo assets. If you are lucky and own a 2 screen working environment or a wide screen that workflow is even more efficient than with that famous bridge.

  6. Same, because no one remembers the folder one saved exports two weeks ago.

    Furthermore, when you save an .afphoto and export afterwards, e.g. an jpeg, then you have to save the .afphoto again even when you did not change anything in between. So I normally change that sequence and export first and save .afphoto after that. There it happens often that the files go to the wrong folder. Please improve that.

  7. @R C-R

    Well, I did not say that 8bf has been replaced, or did I? I recognized, that Adobe has changed/further developed the interface and software manufacturers followed them. I could experience myself, that a plugin manufacturer changed his 8bf interface file together with a new version of his product and AP could further on not work with that "new" 8bf file at all. The advice given by the plugin manufacturer was: You can use it standalone. Similar with the "new" NIK 3 version by DXo. While the "old" Google version worked pretty in AP the new DXo version did run only part of the interface functionality as an AP plugin.

    What is the conclusion from that? I would like to use AP in the future, too. But when I loose my most frequently used plugins as time progresses, then I will be forced some time in the future to return to PS or some other product which might offer that functionality then. It is not my intent to debate 8bf file development details any longer. I just wanted to give a hint to Serif to keep an eye on that and perhaps find ways to overcome the problems behind.

  8. @R C-R

    I use AP already for a long time on a regular basis. And my experience during that time was, that more and more plugins did not work any longer when there was a new version issued by the plugin manufacturer. And even the latest NIK 3 by DXo runs only with part of its functionality, while portraiture does not at all. So for the moment you can still use the old NIK 3. But what will be the solution when a next NIK 5 will offer great new features?

    When single users contact third party producers they normally are not heard (except from AcdSee as one positive example) and instead get the hint to use the product standalone. Therefore I think it might be of interest to Serif to improve that situation by mutual agreements with some important plugin manufacturers at least. One solution for instance could be that the ancient 8bf structure is offered to AP users in parallel to the new interface for PS. I myself follow the strategy to "freeze" certain versions in order to keep my working environment stable for as long as possible. But some time this will come to an end of course.

  9. @John Rostron

    Thanks for your detailing. But this is not the case which I want to speed up. I prepared for my work already some macros which do things like sharpen in one step instead of 3 or 4 steps. So I use 2 or three different macros and when I need sharpening I just start one out of those three, let it do its job and then next action. The same I want to achieve with save & close. Instead of save and ok and close I want to call a macro which does all in one call. That is not an important thing when you work on single pics only, but when you edit 30 or 40 in a sequence then it saves a lot of time. For example, when edit work is done, then an  export shall be done, then the save of the *.afphoto file and finally the document shall be closed. If one could do that using just one macro call this would speed up things a lot.

    At present, AP macro does not support file operations at all, that is why I asked for such a feature.

  10. @R C-R:

    It is a pity, but meanwhile we know that Adobe changed a lot in PS Interface and plugin vendors followed them. The 8bf still exists, but hardly works as before. Portrait Pro, Portraiture and NIK for example, are no longer fully compatible. You can only use them standalone. What a progress! In the music software industry however, VST is a standard which still works very good, and all software vendors profit from that, but 8bf is dead in the meantime. And therefore there will be a need for Serif with AP to look for agreements with plugin vendors, at least the most important ones, when AP shall further grow in the market.

  11. Thanks for the hint. It is better than nothing to follow secondary sources. But why is there no statement from serif inside the FAQ? There is no doubt, that this subject is addressed quite a lot. I can understand that Serif is not able to guarantee for external companies products. On the other side when there is no multilateral interest in cooperating, users will go back to PS after a while because they do not want to fail repeatedly instead of working on their projects.

  12. Hi there, I found lots of questions about plugins and their possible use with AP in that forum. But I did not find that subject inside the FAQ pages. Consequently my question:

    Is there a page or a list which gives an overview of plugins usable with AP?

    Well, of course everyone can ask the software vendor of his desired plugin for compatibility issues. But as we all know, we would not get an answer in most cases.

  13. @walt.farell:

    extra save operation: Well, other software products can handle that as requested. And when doing it vice versa, what I normally do, then you have the optimal result. But when working partly in panoramas e.g. that is misleading because there you have to supply the "save under " filename twice (one for the export and one for the normal document save. Would be nice when a newly developed product like AP could assist users in that. And of course such things are not a must, but they are smart and support smooth operation.

    overwrite errors: Well, when I work slow and carefully I can avoid that because I know that this will happen. Nevertheless, during mass work, and that is my normal workload, this happens repeatedly. And you will not see a warning in every case. Otherwise this would not happen. Finally, this too is not a must, but ....

    file name default: I don't think so as stated in your example. When you make a panorama from Tiffs the first result is a *.afphoto document that will not overwrite an original file at all because of the different file name ending. And that is why I am saving back always to the source folder as suggested in your example. The only case where the overwrite could happen is when you do an additional export as *.tiff. But there you get in every case a warning for sure. And using the "unnamed" string for everything is of course more dangerous than anything else and causes more dialog work to do. And as written above this is not a must, but ....

  • 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.