Jump to content

hifred

Members
  • Content Count

    398
  • Joined

Everything posted by hifred

  1. In my opinion it alone in terms of marketing is silly not to support basic animated GIFs from Layers and from File history. Knitting a few frames together should be trivial to hook up and would spark tons of cool user generated content. Programs like Zbrush even let you film your entire 3D modelling session and YouTube is full of such clips. Also Support would profit when users were able to export the editing sequence - here one obviously also needed dialogue boxes showing in history snapshots. I have created countless quick animated GIFs directly in Photoshop and not a single one in those often proposed 3rd party tools.
  2. I can confirm that the file isn't crazy complex and that it takes minutes to switch over to Tonemapping. I canceled out at some point. The app gets very slow all all over, it clearly can't handle the file. I tested the shared file in the most recent Beta. The thread-title is an accurate description. Win10 | i7 6850k | GTX1070 | 32GB RAM
  3. That's should not be a reason to make modern machines unresponsive. Here's a folder view with a few of my Photoshop files, none of them is slow or makes PS unresponsive. There's really no need to defend bad performance, it doesn't help anybody and surely not Serif.
  4. Which would mean that one could not browse images without having Affinity Photo open...Not a solution I personally wanted to use. Also the DAM being a part of Affinity Photo meant that it wasn't a separate product Serif could sell and make money with.
  5. Thanks for the explanation. I have to admit, that I got extremely used to the editing freedom coming along with embedded RAWs. I enjoy not having to declare an image readily developed and not having to deal with interim tifs ever - in return I gladly give these files a bit more space on disk :o).
  6. Interesting. I personally very much like that one can embed edited RAWs in Photoshop files. That way you can always return to the RAW workspace to fix stuff with a couple of strokes which in a layer based app would take a stack of several layers. You do that on the downmost file – anything you did on the file with layers accomodates the new development status. How do you with Capture One and Affinity Photo deal with this topic? Have you created a template with your Raw size and place a tif? How do you then update the externally referenced file – or do you simply live with the status you picked up with Affinity Photo?
  7. Thanks for your input! Of your processed RAW files – how many of them do you usually bring to Affinity Photo?
  8. I agree that creating a DAM with advanced RAW editing capabilities is likely a lot of work – but I personally consider such at least as vital in a 2D graphics suite of programs as a Page Layout app. Nobody questions the necessity of Publisher though. RAW shooting has long become the standard camera output, even in amateur photography (heck, even my Phone shoots RAW) and it has become very common to work on large amounts of images at a time. Further people have gotten used to multi-tool eding (raise black point, sharpen and remove colour cast in one brush stroke). A classic photoshopesque workspace has no suitable answer to any of these demands, but it's great for post-processing: For combining various shots, for special effects, for adding text etc. A lot of us need both – that's why one needs an integrated solution. You mean Lightroom, right? Bridge is Adobe's Image Browser, without RAW editing capabilties. I personally would consider Affinity for daily editing if the already existing Develop persona was moved over to a relatively simple browsing application, if one would write settings to sidecars and could open the file with its settings in Affinity Photo (as an encapsulated file – image layer which one could send back over to the DAM for further tweaking).
  9. I just don't see value in having this (new from clipboard) a separate command. Many of your users totally expect to get offered creation of a new file from clipboard bitmaps and won't even look for an alternative implementation. Such is not only a source of error but also of avoidable support requests. Breaking something into a command of its own only makes sense if one can't reach a particular goal with a single command. That does not apply here: Ctrl/CMD + N should do just fine.
  10. I believe the fault #1 is actually on Serifs side here and that it will remain a needless trap for likely anyone new to this program. There's implementations of encapsulated, non-rasterized layers in programs such as Photoshop which don't pull your leg. One can select portions and mask Smart Objects and copy stuff out of them - the only thing one cannot do is edit the pixels on that very layer directly.
  11. Affinity sliders also lack another awesome feature: Drag (way) beyond the bounds of the slider to reset the slider to either it's last used value (either last custom value or its default value). Super helpful when playing around yet some more - nah, that doesn't look better - no need to memorize previous settings then. I love nifty little helpers like these, because they do not interfere with the workflow of anyone who doesn't use that feature.
  12. There's no known fixes unfortunately. Affinity Photo in the current state of development is no suitable tool to edit series of RAWs. Maybe leave your opinion here.
  13. Thank you Mark, I appreciate that you tested this yourself. Also in your case this operation only evaluated a few hundred pixels at best - I feel such simply had to work faster to leave a snappy impression. Also while I like that you show that the program is thinking - I find that progress bar popping up after each single stroke way too intrusive. The status bar would work for this as well...
  14. I can't follow your reasoning. I only compare Affinity Photo to Designer because I expected Vectors to display at the same visual quality as inside Designer. I further don't see a good reason to display pixelated Vectors inside the graphics creation app Affinty Photo – while the Page Layout program (Publisher) shows nice vectors. Result of the current choice: The work file inside Affinity Photo looks – a lot – worse than an exported pdf of the same file.
  15. A small example of many. Just look how long it takes to refine the selection on that tiny edited portion. With my Photoshop background I would expect this to get processed in realtime and not to see the loader gif ever. The machine is an i76850K with a GTX1070, fast SSDs and 32GB RAM... Only one layer in this file.
  16. Batch processing is indeed unavailable in APhotos Develop persona. But silly batch processing was way too unflexible for RAW processing anyway + running batch operations would needlessly take ages, – as Affinity needs to open and embed RAWs while other RAW processors simply add settings files to the RAW (in miliseconds). Presently Affinity can only develop in a lossy fashion, whereas practically any other RAW Editor works losslessly. If want you may have a look here...
  17. Mark, there have been numerous threads like this one - they pop up nearly on a daily basis (also today). The overall slowness on even pretty beefy Win 10 machines should really be known by now. Do you really still need samples because on your machines everything works perfectly snappy and you have difficulties to reproduce what users experience? This appears hard to believe to me... I don't mean to sound nasty but I perceive Affinity Photo slow in just about everything - it should get apparent to anyone doing a few basic operations – no need for fancy non standard settings and colour profiles.
  18. This thread is about vector display inside Affinity Photo. Unfortunately Affinity Photo rasterizes all vectors for display, see MEBs answer.
  19. There's a huge variety of nice RAW processors, with or without database. All of them (in contrast to Affinity) load RAWs pretty much instantly + let you very easily transfer settings from one image to any number of other images. Some RAW processors support layer based editing and complex masking, even compositing several images together and basic text overlays. Just have a look yourself and try out what seems interesting to you.
  20. Thank you all! I grant everyone a little laugh – but I hope you don't mind that I still raise a feature request :o) If it wouldn't come across so terribly unpolite I sometimes would like to add "I'm really asking exactly this question*, no workarounds please". To me that's just another nuance in the long list of areas where I find APhotos Layer Editor inferior to the one I'm used to. Many people have complained already – hopefully the developers have another serious look and then I rather throw this one onto the heap. My personal experience whenever I tinker a bit in Aphoto is that it only takes seconds and I start missing things. Not because they are hooked up slightly different, but because they simply don't exist. These tiny and not at all tiny things (such as missing context menus) really add up and in team play with overall tool + screen redraw slowness seriously spoil my editing experience. *In that case the precise question would have been: Does the 'Create Pixel Layer Button' Photo use an alternative keymapping to toggle the location of a newly created layer relative to the active layer? Please let me know. :o)
  21. Thank you MEB, I was not aware of that. While don't understand why one doesn't utilize the ( existing) vector display pipeline for vector shapes and only rasterizes at export time that's at least an explanation. What I can say is that things don't look pretty on a screen with already quite small pixels on 2560x1440 25 inch displays (yeah, worse than PS). Oddly, Publisher uses Designers vector engine and renders nice and crisp vectors: I hope, we can agree that it is the program in the Affinity-suite which serves least graphics creation demands. That may make sense programmatically, as Publisher is closely related to Designer in its core, but certainly makes zero sense from the user-perspective.
  22. It would remain a two step operation though ;o) Seriously – the way this works in Aphoto is less elegant. I rather open a wishless item.
  23. At random magnification At 100% (Things look better on screen than in this screen grab)
  24. I see a great discrepancy between the vector rendering quality in APhoto and Designer. While things look crisp at all Zoom levels in Designer (as one would expect), all roundish Vector shapes created with its native tools show aliasing (stairstepping) here – unless the document is displayed at 100%. It appears to me as if Vectors were rendered on screen as bitmaps here – is this a special display mode I have activated by error? Sending a file would be pointless – I see this in every empty document, as soon as I draw a circle.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.