hy13
-
Posts
66 -
Joined
-
Last visited
Posts posted by hy13
-
-
Hello Chris B,
this happens just after loading a *.afphoto file before doing anything else. After doing some other action the shortcut is working from that point on.
But there is other problems on shortcuts. For that I will post a new issue.
-
After opening a *.afphoto file via drag and drop CTRL+U does nothing. After some other action CTRL+U is working. This is valid for AP V2.0
-
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.
-
@GarethCallanMeanwhile there is V22 from Portrait Pro out and as it looks like, the former issue is no longer there. It works perfect together with AP 1.10.4 from the beginning. Both packages were installed on a new built Win 10. But I do not know what and who has made it working. Perhaps Serif talked to Anthropics or vice versa.
-
@Andreas DAs far as I got to know there is no reaction from Serif to that request so far. I followed the update messages until 1.10.5 and it looks like there were no new features during the Corona period based on user requests. Listed were mainly bug fixes.
-
@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.
-
As mentioned above this requests exists for a long time already and one cannot understand that this might be an issue for Serif. Therefore let me ask the question different: Can it be that Mac Users do not need that? And is this perhaps the reason why windows users did not get it til now? Does anyone know this in detail?
-
Hi SansRT,
I agree to your request but I fear, that you will not get it solved soon. See the macro functionality, as it is at present, is very limited. Would be better to expand macro functionality first to a higher level. Perhaps it will help when requesting macro functions first and later on the shortcuts feature.
-
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.
-
-
Thanks for the hint. I will try this in the near future.
But why is there no subject about it inside FAQ? There is no need to cover everything out there in the market, but for sure, it would be a good help to give information about plugins which are inside Serif known as "working" with AP on the FAQ page. -
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.
-
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.
-
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.
- Karen12345 and John Rostron
-
2
-
@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.
-
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.
-
@Old Bruce:
How can I speed up save & close with File --> New Batch Job ? I do not understand your hint.
-
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.
-
@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 ....
-
When doing mass editings on lots of files after a holiday or a shooting one could profit from the ability of automating save and close operations.
Therefore I request to include macro functionality in AP which enables to save and close an edited document in one macro operation using provided default settings.
-
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.)
-
-
A lot of us moved to Affinity Photo because they do not like to stay online all the time. It is already a mess that Win 10 itself permanently disturbs work by its unwanted updates several times per week. I do not like that and therefore switch off Internet most of the time on my production machine. Who asked for that new feature? There are so many other asked features not done so far. Just remember of including save and close functionality within the macro recorder functionality which is open since years already. This would for sure be a useful thing which could speed up work a lot for those using a structured storage principle. And do not hesitate to charge in between for good new features. That is no problem, but keep on track please.
- Mystical and PaulAffinity
-
2
-
As it seems to work for me those who have V17 and V18 available could try the following when Windows is the OS:
Install v17, then install v18 as upgrade. Do not uninstall v17 before. In Windows I see then two versions in two different paths in C:/programs, one for v17 and one for v18. In Affinity Photo then go to Preferences/Plugins dialogue and choose the path where v17 *.8bf file sits to be referenced. To be safe, rename the 32-Bit version of *.8bf file before using the interface. On my computer V18 starts then, using the *.8bf of v17. In case, that AP has already a reference to Portrait Pro, shown in its Preferences/plugins dialogue window, then clear that reference first before referencing v17 *.8bf files. This may happen when you use AP Release and Beta versions in parallel or so. Mind that AP needs a restart after each change in these preferences to make it working.
If your v17 program path was destroyed on installation of v18 (what normally should not happen when upgrading) one could try: uninstall v18 complete, reinstall v17 afterwards. Perhaps it is not necessary to activate v17 when you find it in the c:/programs path together with its *.8bf files after installation. Nevertheless, when you have no v18 installed, the activation of v17 should work. Then reinstall v18 and activate it. Finally, reference in AP preferences/plugins the *.8bf files of v17. Do not use plugin installation routines, but reference *.8bf file via AP preferences dialogue only. As above, make sure that AP has no earlier reference to v18 *.8bf stored when making the reference to v17 *.8bf files.
Good luck!
For the long term usage I think it makes sense that everyone needing that interface working should tell this to Anthropics as well. If there is enough interest shown then ... who knows we may get a better solution in the future.
View --> Grid on/off not working
in V2 Bugs found on Windows
Posted
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