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

Search the Community

Showing results for tags '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 (Serif 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.3 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. The problem has been present since the release of the V2 version. MacBook Air M1 macOS Sonoma (also happened on Ventura). Only happens if I close the window before developing the photo. If I develop a photo and after developing I go back to Develop Persona and close the window the app does not crash. This happens every time with both hardware acceleration enabled and disabled. I recorded a short video. Nagranie z ekranu 2023-12-2 o 11.27.57.mov
  2. Attached is Revision A of my Tutorial on how I process and edit color negatives using Affinity Photo. My original tutorial generally resulted in good conversions, but sometimes the deep shadows took on a blue cast. That could be corrected during editing, but was not ideal. Rev. A corrects this problem entirely and results in better, more accurate conversions. The process in Rev A is different, but is simpler to implement. I do not own a dedicated slide scanner, negative conversion software or plug-ins. Instead of scanning, I used my DSLR, a 100mm macro lens and an LED backlight to photograph color negatives, which I brought into Affinity Photo in their original negative form. I shot RAW, but full sized TIFFs work equally well. The approach described in this tutorial works with any brand color negative film and preserves the color relationships in the original negative. No special negative film profiles are required. This method works well for me and I hope others find it useful. There are many ways to process color negatives and convert them to positives, but this works reliably for me and yields an image that is easy to edit. Best, Lou Dina Processing Color Negatives in Affinity Photo-Rev A.pdf
  3. Hi there, Affinity photo 2 is for some reason is not handeling the RAW "lossless comp" files properly. It seems that the lens correction is inverted and it makes blackbars around the image. When I use a compressed RAW image it is working properly. I tried resetting settings affinity photo 2 (no changes) Opend in ACDSee working properly Opend in Sony Imaging Edge working properly Opend in Windows photo working properly Test raw images added and jpegs all directly from the camera Specs: Camera: Sony A6700 All lenses when RAW compression setting is in "lossless comp" PC: Windows 11 32 gb ram Nvidea geforce RTX 4090 Affinity photo 2.2.1.2075 DSC02821 compressed.ARW DSC02822 lossless comp.ARW
  4. This has probably been suggested already, but I really wish Affinity Photo could add a method of saving RAW edits using a xmp sidecar file (or other non destructive way like how Adobe Camera Raw remembers edits to dng files) so that I can re-open edited raw files a later date. An option to reset edits back to original settings of the RAW file should be included too. The current method of having to bake edits after developing and to save as an .afphoto file is a pain, due to making another large file or having to re-edit the RAW again.
  5. Dear Community! Shooting RAW files in cropped format (e.g. 4:3 instead of the default 3:2) can be very helpful for framing (knowing that one needs a ration of 4:3 later on anyway). Even though a non-standard aspect ratio (i.e. other than 3:2) has been set, the raw files will always be stored in full resolution of 6000x4000px, ratio 3:2. Opening DNG-files in Adobe Bridge will show the images as expected in the cropped ratio, the way I framed it and the way I want to export my edits as well. (The standard aspect ratio and image resolution, of course, do depend on one's camera model.) --> Question: Is it possible to apply the cropped aspect ratio according to the file's metadata in the "Develop Persona"? When opening Affinity Photo and loading the DNG file into the Develop Persona, the full RAW image of 3:2 with 6000x4000px will be shown, instead of the desired 4:3 with 5328x4000px. So far I was not able to find this option somewhere in the "Crop Tool [C]" or else where! Thanks in advance for any tips/links/hints/help!
  6. Hello everyone. I have a question about what I'm doing wrong. I develop RAW files and I already have photos in Develop Persona that I am happy with, then when I press "Develop" my image looks completely different - it is much brighter. Do you have any idea what to do or maybe there is a tutorial about it? Thank you in advance Jurand Do
  7. On my Mac desktop affinity photo doesn't open my RAW files in develop persona, instead opens in photo persona. why? I don't know and need desperately to know why. thanks
  8. Just got AP and first impressions are v good (previously years of Photoshop use). Tried processing my first raw file however and the image has a dark vignette at the corners. Never had this problem in Photoshop so am initially surprised and at a loss as to what is causing it. Previews ok on my mac. Any help would be greatly appreciated. Apologies if this is posted in wrong section - am first time poster. Also am I correct in assuming there's no direct support, as I just got directed to the forums when I clicked on the support tab? I've attached a small jpeg of the file in question.
  9. First of all, thanks for these updates, excited to try out the tools! I do have some issues that I've found after an hour of trying to use this as an alternative to other photo editors that I'd hope to see addressed: 1. A way to save raw edits as XMP instead of requiring the saving of an .afphoto file, the idea of closing down in an ecosystem, particularly with the lack of a DAM, doesn't sound appealing. It sounds like that's kind of what the Embedded and Linked options do, however the Linked option did not actually add any files to my system (I kept watch on any files with the same file name as the photo), so I'm unsure what the difference between the two is. 2. Global presets for RAW edits, instead of one per page. It's a bit confusing as is. Also a way to edit existing presets and save it as such, instead of deleting a preset, remaking it from scratch and saving that. Also this is likely a bug, but when opening a new raw file to edit, the settings are set to Default, but the "selected" preset is the last used one, requiring switching to Default and back to the saved preset to actually change things, sometimes even doing it multiple times, the feature seems quite buggy. Also, ideally a Preset Manager would also be present, to be able to see exactly what each preset does, and potentially tweak from there. 3. Non-destructive cropping is a must. Honestly just something similar to the artboards, so if you crop an image you can adjust the crop later. I could just open the file in ADesigner, but that's an extra step that could be avoided. 3.1. Keep a strict ratio for cropping, but allow to rotate the crop based on mouse position when dragging the crop selection around (see how cropping operates in other apps like Lightroom and Capture One). 4. Split view of photo without edits, or just being able to toggle the raw edits on and off for preview purposes. 5. It's not clear enough that a photo is a RAW file, a button similar to the FX one would work wonders and make it much clearer what it does. 6. There's something about the Overlays panel that feels incomplete, I think it should be closer in look and feel to the Layers panel but then again, how is this better than just duplicating the layer, making the adjustments in that raw layer, and applying a mask to that? Even more powerful then because you can use images and the like. I might add more to the list once I spend more time on this, but so far I'm somewhat disappointed. Non destructive raw editing was a highlight of the announcement, so I thought it's finally a good standalone photo editor. It is clear however that the app development is still walking in the shadow of CameraRaw and while there have been some improvements and additions that are much welcome, I'm sad to say that I'll likely be sticking with Capture One, despite my wishes for that to not be the case, not because of the lack of a DAM (just making that clear), but because of the lack of a good, non destructive, open photo editing flow.
  10. Could someone at affinity please send an update on why the ability to open a raw file from Apple photos app on iPad M1 Pro no longer works in v2.1? It worked in the previous version so surely it’s not too difficult to compare the coding.
  11. When batch job exporting RAW to JPEG resulting pictures are too dark. Please help.
  12. Affinity Photo v2.0.4 on macOS v13.3.1 – can't open Nikon .nef RAW files made with a Z9. Please advise. File appended. DSC_6063.NEF
  13. There's countless threads in this forum where people ask for a DAM. Serif confirms that there's some plans, but so far they didn't reveal what they are working on. Reading the requests brought up by users I see that they ask for very different things: Some want a straightforward viewer app, others even request complex database driven software with nifty filtering options to handle huge asset collections. The term DAM unfortunately isn't very clearly defined. Hence my question: Do you need a DAM-program by Serif? And what should it be like? [Edit: Unfortunately I can not do anything about the terrible Poll formatting. Maybe staff can add an empty line between the questions?]
  14. I can not open RAW files from my Panasonic GH6 camera. See attached file. This is not due to any issues with memory cards, computers, operating systems, or the camera. Here is the reply from Panasonic. Will you be providing support for RAW photo files from the Panasonic GH6 camera soon? Thank you. Dear Mr. Steven Cleghorn, I hope this email finds you well. In regards to your query and following further investigation on your case, we would like to advise you that the reported issue is not a fault with the unit as the supplied/compatible software recommend by Panasonic works and that means that the unit is functioning within its specifications. That being said, you may contact the Adobe affinity team for support and help regarding this to confirm if the camera is compatible or not as we are not able to guarantee the functionality since it is a third party software. I trust that the above information will be of assistance to you, however, if you should have any further queries, please do not hesitate to contact us. Kind Regards, Eva Panasonic Customer Care Team
  15. Hi, Recently, I have been experimenting with using RAW files in Publisher. I have 6 RAW images loaded which have a gradient map adjustment layer applied on top of them. But loading the particular pages (FHD resolution for a presentation) really bog down the entire file. Are there any speed improvements possible still? Windows 10.0.19045, i7 7820HK, GTX 1070, 32 GB RAM
  16. I have a Canon EOS R8 and am having a problem. When I try and preview the .cr3 raw files on my Mac which is running iOS Ventura 13.3.1 affinity nor Mac will show me a preview of the the photo. Instead it only shows me the affinity file icon. This makes it near impossible for me to know which photo I want to edit without opening each photo up separately in affinity photo. Affinity photo does open the .cr3 file, however I am opening them blind and do not know which photo I'm opening since I can't preview them. I am using V2.
  17. Whenever I apply my master page that has a RAW image (developed in Publisher, default linked setting), to another master page, the app crashes. I have tried to go back to a simple and clean file, it still crashes. I went to the release version and the software crashed before I could even develop the RAW image, so I am reporting this with a Beta build. Cut out the part where it crashed: 2023-05-16 07-57-08_Trim.mp4 Steps to reproduce Create two master pages, one with a text frame for a title and one with an image frame. Place a RAW image in the image frame. Click on the RAW image and go to Develop it (e.g. change the exposure) When done, apply the master with the RAW image to the master with the text The software crashes This is on Windows 10.0.19045, using Publisher 2.1.0.1790. Hardware acceleration on. Also, it appears that if I change the way the image is developed (from linked to pixel layer) it works as expected. However, there seems to be no way to revert back to the linked file nor to replace the image like you would with any regular image.
  18. I've been encountering a recurring issue with RAW development, but the issue happens inconsistently and seemingly at random. After loading a RAW file, I make some of the color and lighting adjustments I want to make to the file. But then I click "develop" and the edits are not preserved, leaving me with a developed image without any of the RAW edits I made. I use the same process for developing images every time, but the results have been inconsistent. Perhaps I'm experiencing a PEBCAK problem, but I'm not sure what exactly I would be doing wrong that causes inconsistent development results.
  19. When importing DNG RAW files from a DJI Mavic Drone, Affinity does not recognize the built- in lens profile for lens correction. The profile is there, Lightroom and other programs recognize and use it to correct distortion. The drone is the very well known Mavic 2, the profile name is DJI FC2204
  20. I recently sent a JPG file to a friend of mine and he opened the file in Photoshop. The JPG was exported from AP v2.0.4 (Mac Ventura). When he opened the file in Photoshop, it automatically opened the file in Adobe Camera RAW instead of opening it normally, as if the file I sent him was a RAW file instead of a JPG. I tried it myself on another computer I own that has Photoshop installed and got the same result. It launches Adobe Camera RAW, with a lot of crazy slider settings in the Basic Tab. The original file was a RAW DNG file from my Canon DSLR. I processed the original RAW DNG file in AP v2.0.4 (Develop Persona) and I chose to import it into the Photo Persona with the RAW file (linked or embedded, I forget which). I wanted to retain the ability to go back and forth between AP and the Develop Persona so I could make adjustments in the Develop Persona. That all worked fine, as designed. When I exported the file from AP to JPG, I suspect AP must have written something in the metadata so the JPG looks like a RAW file, which is what caused Photoshop to launch Camera Raw. To me, JPG is an industry standard file format and should not look or open as a RAW file in any program (even AP). The original AfPhoto file format is a different matter, since you want to retain that active link to the original raw file (if linked). Is this a bug? If intended, should it be changed? I suspect so. I don't want my JPG files sent to others opening as RAW files. I exported the file from AP to JPG twice, and will attach both files. One has sRGB embedded and the other is Adobe RGB.
  21. Hello. I would like to propose a feature that would allow the user to copy and paste raw adjustments to multuiple RAW files from develop persona. I believe currently this is not possible. This feature will make the applying adjustments much faster and easier for many kinds of workflow including timelapse. And additionally an option to export multiple selected RAW images at once. This two features will be a game changer for affinity as a whole. I believe this could be a great direction for the software. This could increase the interest of lot of people considering RAW editing is now considered a standard for most. I hope affinity will place this higher in the priority if possible. Thanks.
  22. Hello, I am new to Affinity and a bit confused to how to save DNG edits in Affinity Photo. My workflow when I was using Photoshop was to first convert my raw Nikon images in Adobe DNG Converter, open the dng file into Adobe Camera Raw to edit, then open into Photoshop. If I was to close that photoshop file without saving, I could re-open the dng file (back into Camera Raw and my previous edits would be saved. So I have opened a dng file into Affinity Photo 2 on iMac, it opens up in develop persona and I make my edits. I then click develop (raw layer embedded) and if I close the file without saving, and re-open that dng file again, the edits aren't saved. Is this normal behaviour? Is there a way to save the dng edits without making an affinity save file? Lee.
  23. The last thing I do in the raw-conversion part of development (i.e. in Adobe Camera Raw or in AP's Develop module) is capture sharpening. My experience has been that the precise amount of capture sharpening within modest limits isn't critical to the final result. So I just eyeball the result, starting from some slider-values (my own pre-sets in ACR) that have worked in the past. But I'm a bit puzzled by AP's use of a percentage in the Radius slider of Detail Refinement. If this is a USM routine, I'd expect the value in "radius" to be the number of pixels surrounding detected edges where contrast will be increased (by the "amount"). What does a percentage radius measure? Percent of what? (Or am I wrong to assume that this is a USM routine? Is it, instead, some form of de-convolution?) Thank you.
  24. Personally, I have been having a hard time accepting AP as a replacement for PS. There is a performance issue and quality issue. I have attached a side-by-side example of a NEF image taken with my D750, both zoomed too 100% . The image were processed similarly, or as best I could. You can PS did a much better job, especially in regards to sharpeness. Has anyone else done this comparison? If so, what were your results?
  25. The choice in developer is grayed. Input files are from a canon EOS R5 .CR3 file. I used to work in HDR, for getting better results in backlight with pictures of birds in a bush. Worked fine for me in photo 1. I recently stopped doing that, to give the RAW embedded function a chance. I am an amateur photographer. I made some changes to the settings of Affinity Photo 1 using information provided. Something seems to have created a problem!
×
×
  • 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.