Jump to content

Search the Community

Showing results for tags 'nef'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

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

Found 21 results

  1. Hello support, I am encountering a problem in Affinity Photo 1.9.2.1035 in Windows 10 20H2 x64. I want to process a batch of 245 RAW-files made with my Nikon Z6 (.NEF with a file size of 28-32 MB per file) with the following options: - Save file to a different folder - convert to JPEG using standard settings (quality 100) As long as I do not activate the "parallel processing" option, everything runs fine, but somewhat slow since the pictures are processed one by one. As soon as I activate the option, 32 files will be processed simultaneously (32 CPU Threads), but no picture will be saved. Every file will have the "I am working" animation (see marker in example image attached), but it will run forever. The RAM usage is approx. 43GB then. My machine contains the following parts: - AMD Ryzen 9 5950X (16 Cores / 32 Threads) - 64GB DDR4-3600 CL16 - Gigabyte X570 Mainboard - AMD Radeon RX6900XT 16GB - source disc: Samsung 1TB 980 Pro SSD (NVME) - target disc: Corsair MP510 1TB SSD (NVME) - newest drivers and Windows updates Is the "parallel processing" not working a normal behaviour? Is this option designed for machines with far more CPU cores (e.g. workstations with 64C/128T) or is this a probably a buggy behaviour? Thank you very much for your answer and your investigation. Regards from Germany!
  2. Hello, I am having problems working with a specific set of NEF files I shot using my Nikon D610 SLR. The other night I shot some photos of Comet Neowise. I planned to use stacking, and shot 9 photos in a series. I can bring most of these images into Affinity Photo and either develop them or create a new stack without a problem. All but this one set of stacked images. This set of photos is unique from the others in that they were all shot at very high ISO (25,600), where all my other NEF images are much lower (3000 or less). I can view these images in the MacOS Finder, in Preview, in GraphicConverter, and in other applications, and they are rendered fine, even in GraphicConverter's RAW processor (which is inferior to Affinity Photo's). But if I try to open one of these RAW files for developing in Affinity Photo, I get a display of random RGB noise. The first few lines of pixels in the image show normal, but the rest is noise. And when I create a stack of these in Affinity Photo, the top band of the image is fine, but the area of random noise is evident, although greatly reduced due to the stack mean. Affinity Photo does report the correct photo data (ISO, camera, lens, etc.). Attached is one of these NEF RAW images, a screenshot of what I see in Affinity Photo when I load one of these images (mostly random noise), and a screenshot showing what MacOS Preview displays for the same file (a bit faint, but fine). I have not altered the files in any way; I've only download them from the camera. Since my other applications can open/display the file, It seems to me this is a problem with how Affinity is handling the files, as if at a certain point in the file it is interpreting the data incorrectly. I think this set of files might generate a decent image of the comet, if I can load them properly in Affinity Photo. Does anyone have any suggestions? Thank you. 20200724-Nikon-RKL_0353.nef
  3. See video attached, the only difference between the technicals of the two images I tried are the lenses used and the date/time taken, my camera is in NZST and iPad is on EST, other than that there’s no technical difference between the raw files. They both open and edit normally using the Apple’s CIR engine. IMG_0174.MP4
  4. Affinity Photo version 1.9.2.1035 on Windows 10 : the devellop function crops NEF File . D4#5296.afphoto D4#5296.NEF
  5. Hello, if a nef-file is imported the colors shown are not the one in the file. Her is an example. The Capture NX is a NIKON Software. But also in othe Software like XnViewMP the colors are like in the Nikon Software. Only Affinity shows this colors.. Something wrong in the setting of then Program?
  6. No matter how hard I try, I am still not able to edit NIKON Z6 II RAW files in the Affinity Photo. Exactly the same problem with NIKON Z50 RAW files. Already installed the Nikon NEF codec pack from the official website and also tried the Adobe DNG Converter. Still no luck. With the DNG plugin other software such as Zoner Photo Studio, XnView or Nikon Capture-NX can display and edit the Z50 RAW files, but the images are so hideous - under exposed, very grey and strangely coloured. Any idea how to fix this? All kinds of help heavily welcomed - thank you !!! OS Windows 10 Pro 64bit / latest 20H2 build Affinity Photo / latest build 1.8.5.703 Adobe DNG Converter / latest build 12.2.0.387 NIKON NEF Codec / latest build 1.31.0
  7. Hello I recently switched to Affinity photo, currently on the latest version 1.8.4, been using it for like a year and so far loving it. except the following issue. I am using Nikon Z50 camera, and set my camera to take photos in RAW + JPEG whenever I shoot a photo, then copy the sd card contents to my mac 1. The JPEG taken by the camera has correct colors / white balance / exposure. 2. Opening the NEF file in Affinity photo develop persona, and change nothing, click develop then export the resulted image to JPG looks so flat, no vibrant enough, and it's really really hard to match the exact white balance i saw or the exact white balance of the original JPEG mentioned in point #1 3. Opening the same NEF on Capture One 20, and also changning nothing and export the image to jpg, gives way better image, comparable to #1 but not exactly 4. Opening the same NEF on FastRawViewer then taking a screenshot of the view also gives a good result, comparable to #1 but not exactly For comparison, i did the same for photos taken with my old Nikon D3400, and surprisingly the resulted image from Affinity photo NEF -> Export is not far from the original JPEG from camera. See d3400 original: vs d3400 processed in affinity photo (NEF -> Develop -> Export) I am wondering what might be causing Affinity photo to be off this much when processing NEF files especially for Nikon Z50 ? does any one with Nikon Z50 faces the same problem? Thanks
  8. So I've read through the forums, and see that the Nikon D610 is listed under the supported RAW cameras. I've also seen several posts where people are having issues opening multiple nef files. Since nef is Nikon's raw format, I'm curious as to whether or not it is actually supported. I recently deployed AP to my end users, and have been getting feedback that the application is constantly freezing and crashing. After speaking with them, I've discovered that the files they process come from Nikon D610's and that they must be in a RAW format. Well, the only RAW format that these cameras can capture in is nef. Again, reading through other posts, it seems that nef is not currently working as intended. However, the D610 is listed under the supported RAW formats. If you could please clarify if this does or does not work, and if it does, any help to address the situation would be appreciated.
  9. Hello- I am a new Affinity user (got the program this January.) I have questions about the Develop persona. I shoot with a Nikon D7000 and use a Dell laptop running Windows 10. I find that NEF RAW files usually display as very dark in the Develop persona and lighten significantly when I hit "Develop" and move to the regular Photo persona. Then I have to re-adjust the levels if I want to get it back to how the photo appeared after edits in Develop. The confusing thing is, this does not happen with every image, and I can't figure out which variables differ between the photos that preview accurately in Develop and the photos that do not. It might have to do with which specific edits I applied in Develop, and this issue may come up more with photos that were already on the darker end of the spectrum. I have checked my monitor display settings and they seem to be OK. Is there something I can do to make the Develop persona provide a more accurate preview of how the photo will appear in the main Affinity Photo Persona? Is there something basic I am missing? Thanks, Alexis
  10. Hi, Affinity Photo reads the message "the file type is not supported". System Windows 10 Affinity photo : 1.8.3.641 File : see attached file In the folder only few files are unreadeabled. All the file are read without problem with ViewNX. Best Regards. Yves POUJOL. DSC_4762.NEF
  11. I’m absolutely puzzled and surprised. So many people rave about Affinity Photo being better than Photoshop but at least photoshop can open and edit raw files. I have spent the last hour staring at the screen with a RAW file loaded and I cannot fathom what (if anything) I can do with it. Maybe I’m wrong but I’m guessing Affinity Photo is not capable of working with RAW files? Hope I’m wrong. Martin
  12. I used my DSLR Nikon D7200 for the fist time since installing .258, when I try to open the file Affinity goes so far then just shuts down, I tried files from last year which previous builds had opened, same effect. I have 112 Gig of free disc space, I use windows 7 and have 8 gig of ram. one time I had the error message below. can you help please.
  13. I’m a newbie with very basic question. I have many NEF raw photos with associated sidecar file containing changes to the raw file. Must all the photos be saved as a combined file, such as tif, before importing? Or can the NEF raw file with associated sidecar file be imported?
  14. Hello, A rather strange thing's happening when opening raw files with affinity! I have a Canon 60D, a canon 200D and a Nikon D850. I shoot mainly raw and am used to make some minor editing of my photos. Most of the times I'm already satisfied with the "in camera" result and just make some minor adjustments later on in my computer. So, I use the camera profiles to adjust parameters (like contrast, saturation, ecc) and then export the raw (or nef) files to my computer. When opening (with affinity) the files from my 60D, there are no differences between the osx preview software and the image I see in Affinity; meaning that Affinity can, at least to a certain degree, read the profiles and adjustments the user makes in a canon 60D. But when I open my files from the canon 200D or from the Nikon D850, the raw files are simply flat, with no customization what so ever (in the preview software they look just like in the camera or if they were jpegs)! You'll probably answer me by explaining that a raw file is "raw", etc, anf I know that, but it's very useful to have a software that can read the changes you make "in camera", otherwise you're throwing a big and beautiful part of your work in the bin. What can I do to solve this problem? Am I doing something wrong? Thank you in advance for your attention, Simão
  15. What are everyone's thoughts on how Affinity processes RAW files (v 1.6.6). Are you happy with the output? I continue to be challenged with the perfect software for my needs so I thought I would start with highlight recovery and create a comparison file using the same photo in a number of different applications. Note that this is far from a scientific study. What are you all thoughts on which is best? Again, this is only the highlight recovery and I know there are other factors involded in development. RawDevelopmentComparison_highlightRecovery.pdf
  16. When I open a NIKON NEF raw picture in Affinity photo the color space and the dimensions are wrong. Affinity shows sRGB instead of RGB / 3900x2613px instead of 3872x2592px / see attached screenshots
  17. I am interested in finding out the ramifications of trying to import and export raw photos from Apple Photos program given that NEF files are not listed as one of the formats to use for export on the Affinity program. I use my Nikon camera to shoot raw exclusively and wonder if this is the best photo processing program for me to use.
  18. Hello, I hope this is solved now also the problem of slow opening of RAW (NEF) files in Windows 10.
  19. Hello, I have the beta version of Affinity Photo 1.5.1.52 installed. Opening an NEF file still takes too long - 28 seconds (Windows 10, 64 bit). Greetings
  20. Have opened Nikon RAW file, NEF, from an older digital camera, E5700. While in RAW editor, prior to pressing develop, if i click on the White Balance option I get a messed up result. When I click off the WB option it goes to normal. using the sliders has no effect. All the other options appear to be working just fine. However, once I develop the photo I can use the WB adjustment layer and it works just fine. TIA, UltraRed
  21. Afinity Photo: Importing RAW images are being changed and turning very yellow. This has been happening since the update because I have our companies head shots that had the same issues but couldn't put my finger on it why they were coming out very yellow. I was thinking it was the white balance issue with my camera and the muslin blue background but its not. Attached is an image of the original nef file and the uploaded one with nothing done do it. The photo's are really unusable even when edited. Please help to address this. If there isn't a fix, I won't be able to use AFphoto for any of my editing needs.
×
×
  • 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.