Jump to content


  • Content Count

  • Joined

  • Last visited

  1. ... or as useful as Lightroom still is. Both have their advantages. My dream is to have best of both worlds in one application and with network-abillity.
  2. And it´s going on: In this case I have to digitalize several negatives for a customer. Because exporting Tiffs out of C1and editing them in AP doesn´t work right now (see above), I did it directly. I opened the raw-files (scans of negatives with D800e) in AP 1.6, edited them and exported as AP-file with layers and as grayscale-Tiff 8bit. But even AP has problems with it´s own from origin-raw generated tiff-files! They will be opened in AP like above, no profile will be recognized, so the RGB-profile will be assigned. But the file still remains as grayscale file (?)! Opening these tiff-files in PS, the profile will be defined as not readable and will be ignored, the file will be opened as grayscale with Gamma 2.2 profile. In Lightroom and in C1 these files (Original NEF-RAW, edited in AP, exported as 8bit Tiff, Gamma 2.2 Profile) will be imported but no preview can be developed. One exception: I scanned one negative with the Coolscan and NikonScan4. This file, edited in AP and exported like the others, has no problems being opened and shown in AP, PS, LR and C1. Good news: this means processing the files in AP 1.6. I tested some of the photos by opening the saved .afphoto-files in AP1.7beta and exporting them as tiffs like above. These files from AP1.7beta don´t make problems any more with being opened in all other applications. mikelike
  3. Horrible news in the morning :-( One thing is better: The scanned Tiff with Nikon Coolscan and SilverFast8.8 now will be opened correctly. BUT: Opening the CaptureOne exported TIFF from the D800E AP1.7Beta still assignes the RGB-working-profile and shows a file much too bright an meanwhile fully magenta. Opening the new CaptureOne exported TIFF from an OM-D E M1 MKII AP1.7Beta also assignes the RGB-working-profile and shows a file much too bright an a colorful chaos. The new OMD-File and a screenshot is attached. GoodMorningGreetings mikelike AP_Test_OMD_C1_Gamma22_16bi.tif
  4. OK, I will check this case with the 1.7 Beta tomorrow. I will tell you! Mikelike
  5. Nothing happened. In my case with the too bright opened and in RGB converted file, I can check the box for profiles, but can only choose all RGB profiles in my system an only one wrong Grayscale-Profile (Epson Standard 1.8). At this point I can set how the files will be developed for further processing in the photo-persona but NOT how AP opens 16bit-Tiff-b&w-file correctly mikelike
  6. Hi! I digitalized the original 35mm-b&w-negative with a Nikon D800e, tethered with CaptureOne. Because of the hint of walt.farell about VueScan I tested scanning a slide with a Nikon Coolscan 8000 in b&w-mode and the scan-applications NikonScan4 and Silverfast 8.8. The results: D800 file, developed in C1, exported as sRGB-JPEG, opening in Afinity Photo (AP) is ok. D800 file, developed in C1, exported as Gamma 2.2-JPEG, opening in AP is ok. D800 file, developed in C1, exported as Gamma2.2-16bit-Tiff, opening in Photoshop is ok. same file, opening in AP converts to RGB-working-profile, too bright!!! same file, opening in PS, saved as Gamma 2.2-Tiff, opening in AP is ok. Scanned with NikonCoolscan 8000ED, NikonScan4, as Gamma 2.2-16bit-Tiff, opening in AP is ok!!! Scanned with NikonCoolscan 8000ED, SilverFast8.8, as Gamma 2.2-16bit-Tiff, opening in AP converts to RGB-working-profile, too bright!!! The original files are attached. Mikelike AP_Test_ND800_C1_eciV2_16bit.tif AP_Test_ND800_C1_Gamma22_16bit.tif AP_Test_ND800_C1_Gamma22_16bit_SavedPS.tif AP_Test_NikonScan_16bit_Gamma22.tif AP_Test_SilverFast88_16bit_Gamma22.tif
  7. Hello! First to introduce me: I´m a professional photographer for 35 years, with experience in many cases of professional photography, developing b&w, color negative, color positive processes, digital photography from its beginning, colormanagement. Meanwhile I work in a public photo archive with 100.000´s of photos from historical until now. About 90% are b&w photos. Digitalization of these photos and managing them in a DAM is my main work here. Right now I try to get a workflow with applications out of Adobe. But there seems to be a bug on the interface between CaptureOne and Affinity Photo. In CaptureOne 10 I export a b&w-file with embedded profile Gray Gamma 2.2. In Affinity Photo (V1.6.5.123) the settings for colormanagement is Gray Gamma 2.2 for b&w-files. When I open the exportet b&w-TIFF with embedded Profile, AP opens it in the Develpo Persona, shows the file extremely bright an assigns the profile for RGB to the photo because AP couldn´t recognize any embedded profile. I can´t rescue the file by assinig other profiles or by developing the file to what it should look like. If I open the same file in Photoshop with the same colormangement-settings, the file will be opened correctly without any profile-warnings. If I "save under..." this file without any changes, but with a new name in Photoshop and open this in AP, it will be opened correctly with the right profile an the right brightness. Any hints for wrong settings or steps in my workflow? Greetings Mikelike
  • 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.