Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for 'non destructive RAW'.

  • 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 (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.5 Beta New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

  1. Non-destructive edit works only with raw files in the develope persona! All other formats are as they are, developed!
  2. Why are you working in the develop persona for a jpeg? That's for RAW files. Do all your adjustments in the photo persona and then they're non-destructive, unless you paint directly on the layer or use one of the tools on the left toolbar
  3. Once you make the initial decision that you want to work non-destructively (by choosing embedded or linked) maybe they remove that option so that you can't accidentally select "Pixel" in a future tweaking of the Raw file thus making future work destructive
  4. This is how I do it in Photo: After doing the adjustments to the raw file, I use that result as a base layer and do not make destructive adjustments to it. I try to do as much as possible non-destructive when I am not sure about having to re-do the raw adjustments. In case that I need to make re-edits to the raw file, I do so and just swap out the base layer (which is the developed tif file). All the adjustment layers on top remain in place. However, there are limits to this approach. If you do some massive changes to the previous raw edit, you might have to re-do most of your edits any way. But if you only make some local changes in the raw edits, this method works just fine. But to be honest, If you get the raw adjustments at least roughly in to the ball park, you should be able to do even major adjustements in the developed tif file.
  5. Yeah - the example I gave was a little contrived, just to illustrate that there are some tools that can't be used in a non-destructive workflow even with an embedded RAW file.
  6. Dear @MEB, As you seem to be following this thread, do you have any news about this "bug". I just bought Affinity Photo V2, and the problem is not solved. But now, if you don't use the Serif engine, you lose the non-destructive raw processing feature, so the workaround based on the Apple engine is not so convincing. Cheers Eric
  7. When you cropped your developed raw file, you obviously brought the left border of your photo in (effectively chopping off some pixels on the left side). The thing of it is that cropping on Affinity Photo is non-destructive; the cropped pixels are still there, but are hidden by the current size of the canvas. When you expanded your canvas, you effectively revealed some of your previously cropped pixels. The way to do what you want is to (i) crop the developed image; (ii) choose “Rasterize and Trim” by right clicking on the layer; and (iii) then increasing the size of the canvas. The Rasterize and Trim command is destructive (there’s no getting the trimmed pixels back). You could, if you want, duplicate the cropped layer, turn off visibility on the original, and Rasterize/Trim the copy. The cropped pixels should still exist on the hidden layer, if you ever need them.
  8. I have been using Affinity Photo at work for a while now, and I have a couple of questions as to a non-destructive workflow. It is pretty good so far, although the overall workflow feels a tad destructive to me. I am used to both Photoshop and Photoline. 1) after developing a RAW file in the Developer Persona, the changes are applied to it destructively, correct? In Photoshop we have the smart object approach to keep things "live", and in Photoline the RAW file is inserted as a regular layer in the layer stack, with live adjustments and settings. Any way to work non-destructive so as to keep the RAW processing live? 2) similarly, is it possible to non-destructively use the liquify persona? In Photoshop we again have smart objects to accomplish this, and in Photoline the liquify tool adds a liquify layer which can be edited directly at all times (even possible to add as many liquify layers as you like, and stack those). 3) after typing text, or creating a vector shape, when I apply a mesh warp or perspective tool edit, the layer is converted to pixels, and I can no longer edit the text. Other effects and distortions also rasterize the text layers. Is there a way to avoid this, and keep the text live? 4) embedded and linked placeholder layers (PL) or smart objects (PH) are missing in Photo. Clipping layers can use smart objects in Photoshop, making it possible to re-use these masks (not very elegant, though). In Photoline and Krita it is possible to clone layers, and re-use them in the layer stack. I am wondering whether a similar feature (SOs and/or virtual layers) is planned at some point? Especially external linked placeholder layers are very useful - when used in combination with non-destructive tools. 5) no fill patterns in Photo yet? 6) I noticed it is possible to have masks within masks, and apply live effects to these masks. The trouble is, once these layer masks are dropped on a layer, the embedded masks and effect layers become inaccessible: the layer stack hides them, and seemingly there is no method to twirl down the contents. Is a setting available to gain access to these embedded layers? Thanks.
  9. Well... when I first saw "non-destructive raw editing" I got a little too excited: I thought Serif had developed the Holy Grail of photo editing, the one app to rule them all. Now I see that this is an incremental improvement that might be useful, if I work in a certain order, and stay aware of what operations aren't undoable (i.e. are still pixel-based). It comes down to things like the clone brush, as it always has. That's where you cross the Great Divide in photo editing applications. Capture One has a clone brush that's nondestructive - totally parametric - but it doesn't work very well, and that's probably why.
  10. We also got a truly non-destructive RAW development process, which was something else we were asking for.
  11. Non-destructive RAW editing Drag-n-Drop Image files into color wells Shape Builder Tool
  12. Afaik a exr is not a raw format, I end up in Photo. It is funny, that we can use any image in Develop Persona, but we cannot keep it non-destructive. If this is a very confusing feature. 😭
  13. 1. AP: Non-destructive RAW development (did someone mentioned the Ger..., DAM? 😁) 2. AD: Measurement tools (addition of document persistency would be highly welcome, though) 3. Universal license (even though this requires online activation)
  14. 1. For workflow, the enhanced layers panel in both Designer & Photo. 2. For drawing, the knife/scissors tool in Designer. 3. Non-destructive raw development.
  15. Modifying pixels is destructive, why not clone on a new pixel layer. The original raw can still be edited non destructively in the Develop Persona... but depending on these new edits your cloned pixel layer could look a bit strange because it will not get the same edits
  16. LOL! Wow, I can't believe some of the petty complaints here. I'm very happy with it so far, especially the non-destructive raw editing.
  17. Hi Billbir, I am more a Designer user than a Photo user. The user interface of V2 is much more logical organized than V1. What I also like is importing assets in Affinity Designer and they appear also in Photo and Publisher. The same is also true for Brushes, importing once, use in all 3 applications. Maybe as a Photo user it has no interest but in Designer the Shape Builder is great. I have to add, while I have both AD and AP, and switch regularly between the two, if you do not use AD then the Shape Builder is of no use to you. I agree with Lizod, the non-destructive RAW is priceless. Probably a lesser reason; you can now upgrade with a lovely discount which let your favourite applications remain up-to-date for probably a very long time. Chris
  18. Hi, thanks for the response. Yeah, I found where the propcol files are stored, but the file sizes are so much larger for the V2 versions, so I think I might just start again with V2.. In the attached screenshot the V1 is on the left and V2 on the right with adjustments highlighted. I think it may be a bad idea to copy the V1 files over. Oh well, just a few hours work to mimic some presets and re-save I guess to be safe. Mostly for me it's some film stock specific colour adjustments I have created for processing film scans that I will have to recreate - as they were a lot of work to get right! Everything else seems fine as I said before, assets, styles, macros, LUTs, brushes all moved over - so just the studio & any adjustments and develop presets for people to manually sort out. V2 seems to have some great improvements, and I am very happy with it so far, in Photo I find the export panel much better - it seems much faster, and obviously non destructive RAW is a massive improvement. Designer V2 has some great upgrades too, the shape builder and knife tool are a huge deal. Thanks again!
  19. Does Affinity use a copy of the RAW file for editing and is it non destructive?
  20. The are useful shape builder, vector warp and new knife & scissor tools in Designer but in Photo not much innovation yet. Alt least there is some non destructive raw development now.
  21. When I develop a raw file (dng), it appears in Persona as a .dng layer. I developed the file as an embedded, non-destructive layer. No background layer shows up. Is this to be expected and the .dng layer to be treated as a background layer as in V1? Did I do something wrong?
  22. I don't see this issue with .cr2 files from my EOS 7D. But I see that this is not a new issue, it's the same in AP 1.10.5 (Didn't notice it before, because AP raw processing just wasn't that attractive to me until now that it's non-destructive)
  23. Hey KyleCrotts, The raw file you've developed should still be non-destructive if you chose Embedded or Linked. It's just that macOS is showing the dropdown greyed out because you seemingly cannot change it from whatever embedded setting you made back to Pixel Layer. I've just checked Windows and once you've chosen Embedded or Linked, this setting is then removed. I need to find out which one is correct.
  24. You can do non-destructive inpainting on a seperate pixel layer, by setting mode to „current and below“. This will stay in place no matter if you change the RAW layer below. Of course, if the layers below are changed in a way that impacts the unpainted area, the inpainting needs to be re-done. you can simply „select from layer“ (the extra inpaint pixel layer) and „inpaint“ again with a very big brush (covering selected area completely). This should be ok as workaround. I don’t think a „live inpaint“ layer would make sense, as inpaint intentionally is varying its result if you use multiple strokes over the same area, and the result are content-aware.
  25. Did you watch the official video about non-destructive RAW development? If so, what happens when you follow the instructions?
×
×
  • Create New...

Important Information

Terms of Use | 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.