Aftemplate
-
Posts
262 -
Joined
Everything posted by Aftemplate
-
DJV(open source)Viewer supports viewing multi-layer openEXR. -
Current affinity photo do not support multi-layers and multi-channel, (OpenEXR supports up to dozens of channels). OpenEXR supports many advanced features, and this format is excellent. Supports lossless with loss mix. Efficient lossy compression. NUKE supports this format well.(Correct recognition of multi-layer multi-channel)
-
I bet he's implementing Vulcan. When I said that I thought he was incapable of driving Vulcan, he strongly contradicted me. MacOS Metal has the available information for api-converting Vulcan. This is the easiest starting point. For these two points, I analyze that he is implementing Vulcan. I'm a fishing guru.😂
-
Under my repeated inquiries, it does have the latest news. It is always listed as the High priority task. Mark Ingram didn't forget it! Predictably, the future is bound to be supported.
-
You can have high hopes for this. It will give you a 10x performance leap. In the near future.
-
What is the size of your brush?
-
This is distinguishable. You can use this utility to test.keyboardTESTutility.exe
-
You may need the Smart Similarity Selection feature.
-
Moving of selections during creation no longer possible
Aftemplate replied to Michail's topic in V1 Bugs found on Windows
This seems to be an interesting question... -
I think you should be interested in this feature. @DavidDoesAffinity ☺️
-
This question is very important to me and I will pay attention to it.
-
Do you have any comments on this feature? I think this feature is cutting-edge. For the future development of affinity photo, it means a lot. @walt.farrell
-
If this is the case (orange), then your suggestion is reasonable, I accept your suggestion!
-
I agree with some of your views. However, if better, the choice should be preferred. Windows lnk cannot beat WinTab at 1%. If reversed, it is possible. So I reminded him to try to avoid lnk. @LCamachoDesign
-
I use AutoHotKey to solve this problem perfectly. My keyboard has two win keys. I replaced the right win key with the right mouse button. (using AutoHotKey) AutoHotKey is free and open source. Highly optimized modern 64 bit multithreading. Less than 0.1% of CPU resources and 1MB of memory are used. The relevant codes are as follows: RWin::RButton Far better than your solution. I hope you like it! ☺️ (This is the standard method for MacOS versions of affinity photo) You can download AutoHotKey from many places. (they have official websites and programs with digital signatures (secure) @Frozen Death Knight
-
I believe that the debate should stop. It's no use continuing to argue.
-
Keep in mind that you can never complete 100% of the operation in a single program. Affinity photos currently have some of the most basic export formats. Not 0. I tend to use multiple programs, And you tend to do your thing in as few programs as possible. This is the difference between you and me.
-
I export using the following format: PNG (non-destructive) JPG (lossy) SVG (Universal Vector) EPS (Universal Vector) EXR (advanced, non-destructive or lossy) If I want to use any other format, Then I'll use XnViewMP. In some cases for JPG, I'll use MozJpeg (bitrate super optimized) XnViewMP supports a number of features, Allows you to calculate the maximum number of colors for a picture. Affinity photos do not support this feature. I use XnViewMP to do this (no need Affinity photo supports it)
-
"core function" Affinity Photo is a picture editing program, Not a universal picture format converter.
-
Change the tool at each time(The price paid is negligible) Core features are clearly particularly important. (Especially in the current affinity photo growth and evolution)
-
You are absolutely objective. (Orange) gives you a round of applause.
-
Webp will undoubtedly damage the development resource budget for core features. That's why I object to adding it (at least for now) With the third-party tool, XnViewMP has no such concern. You'll have a stronger core feature and webp at the same time. Just pay a little: Change the tool at each time.
-
Development resources are limited... If the development resources are unlimited, I'll agree to add this feature. Adding this feature to limited development resources will no doubt stifle the core features of affinity photos. I am willing for change the tool every time Pay the price. in exchange for stronger core features. On the premise of limited development resources, I am firmly opposed to adding this feature. (Not now)
-
Your persistence is correct! I support you. Affinity photos are the Most stunning program I've ever seen, created by you.
-
We don't like to remove features which we have added This reason is persuasive enough. XnViewMP can import and export hundreds of formats (including webp) And it's free, and it supports macos and windows. XnViewMP features extremely powerful, highly optimized 64-bit modern instruction set, and excellent performance. Bulk import export and bulk tuning are supported. It is sufficient for such tasks. This is a very good alternative solution. Affinity photos should focus on the development and repair of core functions. I don't want to waste development resources on import exports. (By the way, thank you very much for fixing LabL Channel 0 Change 128 issue)
