Jump to content

Search the Community

Showing results for tags 'aw-3715'.

  • 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


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 6 results

  1. Running Windows 10 64-bit and Affinity Photo ver 1.7.3.481 Until a couple of days ago I could open RAW files (from Pentax K3 camera) and develop without problems, now, both new and previously processed RAW files now appear as very dark and underexposed, The attached files show a dark image that previously was fine when processed, along with Preferences and Assistant settings that I haven't changed in months, and a screen shot of the RAW file as shown in Picasa. As far as I know there have been no changes to my Windows system etc., it just seems that Affinity Photo is no longer opening the RA
  2. Hi there, With the new version of Affinity Photo (1.8.2) I've experienced a weird behavior of the software when importing raw files (RW2, Panasonic format). The colors appears darker, but only while developing the raw, and this makes almost impossible to work on them...Anyone has experienced it? Is there a fix? For now I've switched back to 1.8 in order to keep on working. Cheers!
  3. I have been testing the AP beta (build 526) CR3 to TIFF batch conversion and then comparing the result to three other program conversions: Luminar 4, v4.1.0 (5191) Digital Photo Professional 4, v4.11.0.2 FastStone Image Viewer, v7.4 I ran a library of 56 CR3 files from my Canon 90D for a rough conversion timing: DPP - approx. 12 min. Luminar 4 - approx. 13 min. AP Beta 526 - approx. 7 min. FastStone IV - approx 1.25 min. Using one files as an example,these are the converted sizes: (orig. CR3 file: 10,387KB) AP Beta: 190,738KB D
  4. Hello, after developing RAW images (CR2), they are displayed much darker than in development. This is not a good thing because it means a lot of additional work. For this reason I only use the 1.7.3 version although the 1.8 would otherwise be better.
  5. When developing a RAW file (I have tried DNG and RW2 with same results), the images look completely different after clicking the Develop button in the Develop Persona. The image looks completely washed out. See the before and after attached. Using Windows 10, Affinity Photo version 1.7.3.481. Problem started recently, I have not changed any settings, same video card, display, color profile, etc.
  6. Hi! I have some issue with Affinity Photo when editing RAWs and was trying to open RAWs in every possible way to edit it, but it no matters how I load files it'll be like this – Opening file -> Editing in Develop Persona -> Clicking "Develop" -> Waiting for finishing develop process in Photo Persona -> Weird and not accurate look of my edited photo. I have this problem since updated to 1.7.3, but after that I had uninstalled AfPh and then downloaded 1.7.2, but it does not help. Please watch video until end, because I'm waiting there for finishing of Developing process, but the dial
×
×
  • 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.