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.

Search the Community

Showing results for tags 'performance'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer V2
    • Report a Bug in Affinity Photo V2
    • Report a Bug in Affinity Publisher V2
    • Report a Bug in Affinity Version 1 applications
  • Beta Software Forums
    • macOS Beta Forums
    • Windows Beta Forums
    • iPad Beta Forums
    • [ARCHIVE] Reports from Affinity Version 1 Betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


Skype


Facebook


Twitter


Location


Interests


Member Title

  1. Hello: On Windows 7 when I try to check the Hardware Acceleration option under Performance in Preferences, it tell me, Unsupported Machine Configuration, with the following msg: Well, I upgrade to Windows 10, to be able to use this option, I updated every single driver, and still don't letting me mark this option. As u can see, it require "Windows 10.0.19042" the same Windows version I have, I updated the direct X, openGL, everything, and still don't let me mark the option. My video card is "Nvidia GeForce GTX 760" with Adapter RAM of "20488 MB (2GB)". Here is more info: Idk if there any another thing I have to do... Thanks ahead!!
  2. This was discussed in another related thread and tested by a number of users using the “unzip to desktop” unofficial install method for the MSIX package in order to negate sandbox. It was learned that there is a significant performance increase when using the same package un-sandboxed versus sandboxed. (i.e. sandboxed == slower) It seems to impact higher end hardware more, but it isn’t clear for sure without more machines being tested. I tested an AMD card in the other thread and it showed a hit, but that card is not that powerful compared to the others. (Feel free to add your own tests below with higher end AMD cards) These tests are using the official 2.0.4.1701 MSIX installation vs MSI installations. 230127_2.0.4.1701_Sanded-vs-Unsanded-Benchmarks_ALL-MACHINES.zip I tested with 3 machines using 3x benchmarks for averaging each installation method: Machine 1 (Main): Microsoft Windows 10 Home (Build 19045) AMD Ryzen 7 5800X @ 3.8Ghz (-30 all core +200mhz PBO); Mobo: Asus X470 Prime Pro 32GB DDR4 (3600Mhz) EVGA NVIDIA GeForce GTX 3080 X3C Ultra 12GB Monitor 1&2 4K @ 150% Perf Variance: 16 ~ 20% Sanded: Unsanded: Machine 2 (Hub’s): Microsoft Windows 10 Home (Build 19044) AMD Ryzen 5 5600X 6 core @ 3.7Ghz Asus ROG Strix B450-F Gaming 16GB DDR4 (3200Mhz) Gigabyte RTX 3070 Gaming OC 8GB Rev 2.0 Monitor 1 1440p @ 225% Perf Variance: 15 ~ 21% Sanded: Unsanded: Machine 3 (Living Room): Microsoft Windows 10 Home (Build 19045) AMD Ryzen 7 3600 6-core @ 3.8Ghz (-30 all core +200mhz PBO) ASRock A520M-HDV 32GB DDR4 (3000Mhz) Asus TUF GTX 1660 TI Monitor 1 4K @ 225% Perf Variance: 12 ~ 14% Sanded: Unsanded:
  3. Split from here by moderator funny but the kepler range has always had OpenCL vulkan and Cuda support in the past. It just seems for some reason that 700 series variants and some M mobile variants have just been dropped by nvidia in the drivers package, and thus for no reason, devs and affinity also no longer allows cuda and openCL hardware improvements - even on win 11. Rendering your system useless if its a AIO unit or a m variant not in the list for 500 onwards drivers. shame - why can't we just force hardware acceleration?? its a tick in a box. There must be a way. I have cuda, i have vulkan and i have openCL. i mean the clue is n the 'open' bit!!! its opensource!! My current error (reason for suddenly no longer supporting my mobile variant of a GPU since v2 came out) in Affinity photo is that i'm running an old operating system so I cant use GPU acceleration. I'm on windows 11 won't be getting v2 until this is fixed or we can just enforce it. There is no valid reason for not supporting even a 7 series card when it clearly has over 1300 cuda cores, more than capable of accelerating the suite. if only i could just tick the box that thinks win 11 is older than win 10.
  4. I was checking the Affinity performance, and I realized that the process priority is set to normal, so basically it will use as less possible CPU. It should be great that the processor could set the priority of their processes to high. I didn't found something to make this not versatile but this command that you can use in a batch file can help with this : wmic process where name="Photo.exe" CALL setpriority "128" Give a try it seems to me, that the performance of the tone mapping as for example increased dramatically
  5. Hi, I was working on someting simple when the updates came through today and after applying the update and opening the same files I was working on in AD again I noticed straight away a performance issue I had not seen before. The update felt a lot worse than my experience with AD since the start. I've attached a screen recording which show the difference clearly. I have two identical groups, the have a layer [same in each group] with fx applied to it. When the layer with the fx is turned off, the performance is fine, dragging the group around is smooth enough. When I do turn on the layer with the fx the performance is basically non-workable for me. You'll notice it in the video. The fx layer isn't antyhing heavy, just a bevel as a test, I've attached a screenshot of the fx. I've also attached the actual file if anyone would like to try. Also attached a screenshot of the peformance settings in the app preferences. System info: System Version: macOS 10.13.6 (17G5019) Model Name: MacBook Pro Model Identifier: MacBookPro13,3 Processor Name: Intel Core i7 Processor Speed: 2.7 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 8 MB Memory: 16 GB I have a Wacom Cintiq 21UX and an old 27" iMac attached as extra screens unplugging them doesn't make a difference. Bert Affinity_Designer_performance_with_layer_fx.mp4 Affinity_Designer_performance_with_layer_fx.afdesign
  6. Pretty much whenever I attempt to use Brushes in pixel mode, I get major major lag in performance, like 5 or more seconds sometimes, between when I draw and when the results appear on the screen. The problem seems to be more severe when using custom brushes, or the default included brushes when the width is increased to very large. I also get performance issues when I switch the blend mode from "Normal" to something like "Multiply". As far as I know, I have a pretty good computer - I've attached a few screenshots of the specs. I've also tried changing the "Performance" configurations but have yet to improve this lag. I've also tried closing running processes and applications. Am I missing something here. My computer is super fast with regards to software development but I'm new to doing graphics related things so I'm uncertain if there's hardware that I'm lacking. Thanks, Andrew
  7. Something I don't really understand is setting the maximum RAM usage etc in Preferences. Having done a search it would seem that the maximum amount shown should be the RAM that you have installed. I have 32GB of RAM installed, bur the maximum setting is shown as 65536 MB. I have no idea how these figures relate to each other! I wonder if anyone could tell me what I should set the maximum to in each app, assuming I may have all three open at the same time, (possibly plus a web browser,) for best performance. Thanks for any advice.
  8. If I have only 8GB RAM and I am working on a large, image-heavy file, how should I set "RAM usage limit" to give me the best performance? At 8GB? At something lower? Or would this setting make any difference to performance?
  9. Hello, I just opened this publicly available PDF file which is ~10 MB in size, yet consumes over 24 GB of memory at times. Illustrator couldn't handle removing the brown hatch, whereas Affinity Designer could. 😃 However, Illustrator only consumes slightly over 5 GB of ram upon opening for the same file, which dropped to 4 GB once Illustrator was recognised as process within the Task manager (Windows 10). Whereas Affinity had been over 20 GB while loading the file and over 24GB when actually working in the file (after having removed the brown hatch and having rotated the file by 90 degrees. Values are CPU % | RAM usage | Disk write speed, it was at 96% so Designer had to use my SSD. I would expect this to be a good file for the team to look at to see whether there are additional performance gains to be had from CAD exports. I really have to praise the development team's efforts, because once open, the navigation is still buttery smooth compared to slow dinosaur that is Illustrator! I was septic at first seeing the 1.9 release video, but now I am impressed. 👍 I do hope this RAM issue could be sorted out. 06_3-5-6-2_PropVar_L3_2004A_P03.pdf
  10. To Serif team. May we please know, in the end of 2021, why canvas rendering algorithms are still so terrible in all Affinity apps? 
It's just not pleasant to see at all. Lots of glitches, fps drops, screen tearing, jumping objects and visible tiling/blocky artefacts during any changes being made. While searching here on forums, I found lots of topics covering all these issues.
 Some of them are five or six years old. But some of these topics are much more recent. Various configurations, pretty good CPUs and GPUs of all sorts.
 But same screen tearing, artefacts and visible tiles. For a such long period of time. And there are still no fixes for that. In some of those topics I've found official responses, that "this is done by design", "it's the way our apps render the canvas".
 Well, it's not a good design then. And certainly not a good way to render the canvas. How you, at Serif, find it acceptable? Are you ok with seeing canvas rendering like that in your apps? How it passes QA and being shipped to your customers? Why there are headlines on Affinity website: "fast and glorious", "pan and zoom at 60fps", "handle 1000s of objects with no lag", "optimized for documents of any complexity"? When it is simply not true, but rather false statements. At least it is not true as long, as such core performance problems still persist for so many people, including myself. Why not consider implementing something like v-sync in your canvas rendering pipeline? Or something else that will prevent visible artefacts appearing during canvas updates. So it will wait for all the tiles to finish calculating their image data and then the whole visible part of the canvas will be composited and painted in a single (at least on the visible to user level) draw event. It will significantly reduce overall performance? Well, maybe, but then you'll need to find a solution for this as well.
 Now it looks like the best idea for you was to throw all these tiles at your customer's screen as fast as possible. Because who notice that mess? They'll be fine with that. But I do notice that. And I want to avoid any screen tearing and tile artefacts in my experience with apps even on the most basic and simple tasks.
So, where is mine "smooth and glorious 60fps experience"? I'm not even starting doing any serious graphic design work because I don't like your canvas in its current state. Sorry. Second, why mouse polling rate plays such significant role in your apps canvas performance? Recently I discovered this myself, and it was confirmed with your team members, that reducing mouse polling rate to default 125Hz significantly improves screen canvas performance. Significantly, but still not perfect yet. So why not restrict any user input events and sync them with dispay refresh rate / gpu redraw cycle? Just an example. The latest Safari has new option in their Debug menu: "Prefer Page Rendering Updates near 60fps". It ignores the display's refresh rate and throttle all in-window paint events down to commonly safe and achievable 60fps. So why not consider something like this and limit overall fps and user input event processing for the sake of overall performance improvement? Maybe then we'll get a better canvas? My main question is: is it an absolutely impossible to seamlessly refresh the canvas without all these tiles flickering around constantly once anything is changed in the viewport? I'm just wondering why it is still being considered as normal in Affinity apps to have a canvas behaving this way? Sorry if my post seems to be a rant or offended you in some way. I had no intent of doing that. 
I'm really wondering if Affinity suite can be made better for all of us. Or we shouldn't expect anything better being done in this direction. Maybe it's really a one big "pain in the a.s" problem for any software developers to make CPU and GPU properly talk to each other? 
Maybe there are lots of problems with major OS developers ditching OpenGL and moving towards Metal/DirectX? Also, we've seen this recent Apple's movement from separate CPU and GPU with dedicated memory to SoC solutions with unified, shared memory.
 Yes, I can understand that your apps should greatly benefit from that. Obviously, lower latencies, less memory copy operations, overall faster access to data.
 All things being done in one place. But... But at the same time I feel that it's just wrong to keep telling anyone on Twitter how good and fast your apps perform on those recent Apple SoCs, while its canvas (which is the main working and the most important area) lags and glitches in general for anyone with more traditional system configuration, even on the most simple scenarios like moving an artboard or a single layer around. I couldn't be the one who notices that. And my system is pretty powerful and it's clear that it deserves better performance and smoother visual response. What I see now is simply unacceptable for me. To be completely honest, I must say that I love your apps. Overall, they are much, much better for me than anything I've seen in this field. There are so many great features and innovative decisions, little details, that make it truly great.
 Every time I discovered these in your apps I was so excited and happy, because I remembered how bad the same thing was in Adobe's products. I remember lots of annoying, terrible things that made me leave Adobe's universe once and forever.
 Vast majority of these things remain unchanged for many years. Because they don't care about their software and customers at all. I found your company and your products to be a complete opposite. Small and passionated company with people really interested in their products. 
I don't want to be disappointed with you guys. I believe in you. I believe in Serif. Just can't stand this canvas tiles flickering and tearing. Sorry.
  11. Hi everyone. For some reason, moving even a single artboard around with a couple of shapes and text layers in it is pretty slow and lags a lot. My system specs are the following: Intel Core i9-9900K, AMD RX 580 8GB, 32GB RAM, NVMe SSD 512GB, running macOS Catalina 10.15.7 and Affinity 1.10.1. Metal acceleration is fully supported and I’m getting good numbers in all kind of benchmarks and other apps, but artboards in Affinity Designer seem to be very slow for me. Tried all settings, Metal, OpenGL, OpenGL (Basic). Metal seems to be the fastest out of all (as it should be I suppose), but still not acceptably fast. It feels like 5-10 fps which is strange to me. Situation shown on video became even worse when moving group of artboards. I should mention that any other actions I do in Affinity Designer are remarkably fast and smooth (after many years of using Adobe apps). Color corrections, transforms, vector tools all of these are just flying. But artboards... Here’s a quick screen recording I made. You can also see detailed CPU and GPU load during performing this operation. I’m also attaching project file. Appreciate your thoughts and opinions. Artboards.mov Performance Analysis.afdesign
  12. Hello, I am experiencing 3 major issues, I forgot to mention the crashing in the video but here it is, briefly showing the weird brush strokes and buggy brushes: https://www.youtube.com/watch?v=-cTpklaQUFk 1: Affinity Photo frequently crashes. 2: Weird performance issue with brushes. 3: Brushes start with paint residue which increases work time and is a mess to clean when working with transparent material. After getting a new boot drive, I created a fresh install of Affinity Photo and all other programs I use. These issues are exclusive to Affinity Photo but have been a huge hinderance because AP is at the centre of my workflow for a long time now. I have checked existing threads regarding the crashes but haven't found similar reports to the other two listed problems. I've checked if there are interfering processes through TM but haven't found any that match the list found in the forums here. I have hardware acc. enabled and have set RAM usage to just over 20GB and in all fairness I don't understand how it could be related to my hardware if that was the case. PC Info: R7 3700X 32GB 3000MHz mem RTX 3080 Huion Inspiroy Q11K v2 graphics tablet HuionTablet drivers 14.8.137.1273 (There is an updated version, but that has not resolved either of the issues, so I downgraded in hopes that this would resolve something - it hasn't.) Windows 10 v. 2004 Affinity Photo v1.10.1 (up to date at present) Please let me know if you need more details. I would genuinely appreciate some help right now. Thank you.
  13. Since the release of 1.9.0, we have become aware of performance problems for owners of AMD Radeon RX graphics cards. This is due to the new hardware acceleration feature which is enabled by default in 1.9.0. We are actively investigating this problem, but while we do this, we recommend trying Photo with Hardware Acceleration disabled (in Preferences | Performance). We apologise for the inconvenience, and thank you for your patience while we investigate. If you are experiencing these performance problems, and you do have an AMD Radeon RX graphics card, please could you go to Help | Benchmark, then press Run Benchmark, and take a screenshot of the results, and post them to this thread (there is no need to record a benchmark with OpenCL disabled). Alternatively just reply with the exact model of graphics card that you're using. There is no need to make additional threads in the forum describing performance problems if you have an AMD Radeon RX, and you still have Hardware Acceleration enabled. Any descriptions of the performance problems that you are seeing would also be useful. Thanks again.
  14. I just purchased a Mac Mini M1 computer. I'd like to know if I should change the Affinity Photo performance settings in the preferences, specifically the RAM usage limit and the disk usage warning. I think they're set to the defaults -- 56320 MB for the RAM usage and 32768 MB for the disk usage warning. My ancient 2014 Mini struggled to keep up with AP so I'm looking forward to a much faster performance on the M1 but I'm wondering if adjusting these settings would make a difference. Thanks for any advice.
  15. Hi, I have downloaded the new 1.7.0 version and followed by 1.7.1. The performance is a disaster and a real workstopper. Drawing something with any Brush tool is the worse I have encounter anytime (no matter if Healing, Brush or Clone....). I have a new top series NTB and Wacom Pro..... but I feel like working with old 486 PC :( I have been using AP for about the time of the first official release, but never saw anything like this :( This had not been a case of 1.6. version that one worked fine for me, but now I do draw something on Wacom and have to wait around 2 to 5 seconds till I see it on the screen, which makes any realtime drawing impossible I have tried restarting many times..... sometimes it works most time not...... It does not seem to be problem of Wacom as it looks the same working with touchpad or a mouse. Do not tell me I am the only one with this problem...... Please let me now ASAP as I am a professional and this makes my job unable...... Thanks Jindra
  16. Hi there good folks in the Affinity forums, first of all, I want to say, that I do like the software very much and I really try to find a solution for my problem here. I've seen variations of this issue in other threads before, but but it seemed, that there is no solution to this. Here are my problems: In Affinity Photo and Designer (Pixel and Designer Persona) I experience serious brush lag and all in all performance issues. This happens with brushes in all sizes and complexities, even with the standard default pixel brush. When I rotate my canvas, raster based areas are victim to very terrible anti aliasing problems. Here you can see an example of the anti-alias problem, you can see it in my red and green sketches especially, but also in the photo reference on the canvas. This happens with all kinds of brushes: Here is a video from AP (happens in AD in the same manner), where the brush lag is visible very clearly. I realize, that in this instance the lag is connected to fast and short brush strokes, but this happens no matter what brush type or size I use: Affinity Photo 2021-03-10 17-16-13.mp4 My specifics: I am using a Wacom Intuos Pro M on Win10 CPU:Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz 2.59 GHz GPU: GeForce RTX2070 32GB RAM I also permitted the software to use more RAM and set the Geforce GPU as default. I really wonder, what the issue is here, since the PC should be more than able to run AP+AD without any performance issues. But when using the software I can clearly detect spikes in CPU and GPU usage in my Task Manager. I'd really love to use Photo and Designer as my dedicated painting software. But as it is right now, I'm having trouble to perform very simple tasks with it. Thanks in advance for your support, I really hope there is a solution to this:) Best, Garf
  17. Hello all, Apologies if I am posting this in the section For some my GPU spikes up to 93-100% usage when I use select all (ctrl+A) within a document even if it is a fresh document with nothing in it (screenshot attached). Affinity Photo Version: 1.8.5.703 PC Specs: Display: Dell U2713H (2560x1440) GPU: 8GB Nvidia RTX 2060 Super CPU: Intel i5-10600K Is there any way to fix this? Any and all help is much appreciated
  18. Hi, I want to purchase Affinity Photo on my 7th generation iPad (2019) or in my macbook air 2020 (i3 10th generation processor 1,1 GHz with turbo boost up to 3,2 GHz, 8GB RAM). Which one would work better? (In terms of performance) And just to be sure, both the ipad and the mac version are a one time purchase without any subscription? Thanks in advance Alexander Geisse
  19. I am currently layouting a photo book (330x240mm) with 500-600 pages in Affinity Publisher on my Mac. Unfortunately, the memory consumption of Publisher is huge. I set the memory limit in Publisher to 28 GB (out of 32 GB I have in total) and disk warning to 64 GB. I have 500GB free space on my SSD and Publisher takes about 351GB while saving the document. Sometimes while moving pictures it crashes (but luckily keeps a backup file) and saving the file takes ages. The pictures are all linked and do have less than 10GB in total in full resolution. Is this a common behavior or is there anything I can do to fix this. Really looks like kind of a memory leak and is not fun working at all. Maybe you do also have some performance recommendations for my 15inch 2018 MacBook Pro with Radeon Pro 560X 4 GB, 2,9 GHz 6-core i9, 36 GB RAM and 1TB SSD? Thank you so much in advance! I really would love to do this project with Publisher and not go back to InDesign.
  20. Hi! Thanks to the developer for their contribution. Merry Christmas! In most cases, the performance of affinity photo is excellent. But I noticed that in some cases it is slow I used a 100 million pixels Lab/16 canvas to create twenty layers. The save of large-area modifications is extremely slow or even horrible. This is not a bug or a computer problem. Large-size (1000+) brushes are slow. Because of the lack of hardware acceleration At the same time I use the macos version, the speed after 1.7 is amazing, the filter responds in time without any lag, and everything is attributed to metal acceleration (in macos 1.7 metal) Please consider adding Lab/8 support to provide a faster preview than lab/16, especially in the current missing gpu acceleration. I will continue to use affinity photos in macos mojave (metal2 api)
  21. Hello team, is the ARM technology of the new macs an improvement in the Affinity suite? what are the advantages of this change?
  22. Hi, I do a lot of photo editing in Affinity Photo and Capture One. I also do a lot of vector editing in Affinity Designer. Last year, to speed up workflow, I bought a new Apple iMac Pro 3 GHz 10-Core Intel Xeon W, 64GB memory, Radeon Pro Vega 64X 16 GB graphics card and 2 TB SSD. This machine did cost me 8500€! This is very very expensive for me, but previously I had a MacBook Pro (2016) that was too slow for my graphics editing. So I thought to me let's spend a little more money to get a really powerful and fast machine, so my graphics editing will be in realtime without waiting time at all. At least that was what I wished and thought. But I have to say that neither Affinity Photo nor Affinity Designer have become much faster with the new computer. Both programs often have very long waiting times when working. I always watch the CPU usage and see that no core is ever used to its maximum. Let alone that all cores are used. It is absolutely incomprehensible to me that I have waiting times in the programs if there are enough performance resources available but they are not being used. For example, I like to work with the Inpainting Brush in Affinity Photo. Sometimes I really have to wait about a minute for it to finish calculating. It is very annoying. During this time, my computer has enough resources that Affinity does not use to calculate it faster. It may take advantage of 2-3 cores in half and the GPU by a quarter. But the rest of the cores do almost nothing. And we're not talking about huge photos here. I recently edited a 12MP iPhone photo. Or I work in Affinity Designer with graphics that consist of approx. 2000 elements. It is almost impossible to select all of these elements and move them around. It is so jerky that the graphics are rendered here and there and lag behind. It is impossible to work with. Here too it can be observed that perhaps two of the CPU cores do something, but are also underutilized. The rest does nothing. The GPU doesn't do anything either. Believe me, I've tried every combination of performance settings in Affinity Photo and Designer. Because it really annoys me that everything is so slow! But it only got slower than faster. I would understand that there is a waiting period if all resources are used to the maximum and there are no resources left. But because the CPU and GPU of my machine are mostly idle while I see slow process bars and long waiting and reaction times, I wonder if something is wrong? My question is, can I do something about it e.g. use certain special settings or is Affinity Photo and Designer not developed for using the performance of my machine? I've already spoken to Apple Support who checked my machine. But everything is normal and fine. I have reinstalled macOS and every app. But it hasn't changed. I mean a year ago this machine was advertised as "Power for Pros" or as "the fastest Mac every build". It would only have been faster with the 18 cores version with 256GB memory. So I ask myself, what machine do I need to buy from Apple to have a noticeable speed advantage? Best regards, Christoph
  23. Hej there, I am using an i7 Skylake with an GTX950M and 16GB RAM, still I get very very slow panorama and HDR renderings from Canon CR2 files. At the same time, very little CPU capacity is used (~15-20 %). Tonemapping panoramas takes easily a complete afternoon! I would love to see an performance upgrade in future versions (even if I have to pay for it). Otherwise, Affinity Photo is close to irreplacable as the generated images are excellent. Even the output using the default settings is much better than for example Aurora HDR, imho. Sincerely, Benedikt
  24. I work on a illustration with a huge number of small dot that i start on Illustrator and i work fine ; but when i change to Affinity, everytime i duplicate an element (and i do that a lot) my computer freeze for a few second. I loose a lot a time. Then i notice that the time my computer freeze was the same for one or multiple duplicate elements. And when i move a element, my PC doesn't freeze. So all i have to do was duplicate a lot of element and move them where i want.It's save me a lot of time. Hope that can help someone in the same situation (and sorry for my bad english).
  25. Hi, I have a iMac Pro 2017 with 3 GHz 10-Core Intel Xeon W, 64 GB 2666 MHz DDR4, 2 TB SSD and Radeon Pro Vega 64X 16 GB graphic card. I use Capture One to develop my 61MP Sony A7rIV photos. Some of the photos need to be edited in Affinity Photo and I use a TIFF 8bit uncompressed AdobeRGB as format. The image has 9504x6336px size. Saving the picture after edit in Affinity Photo takes a lot of time. It takes ~14 seconds for every photo!!! Is that normal for such a high performance machine? The Activity View does not show any heavy consumption of resources while saving in that 14 seconds. Greetings, Christoph
×
×
  • 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.